🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS ISO/IEC 29341-24-10:2017

BS ISO/IEC 29341-24-10:2017

$215.11

Information technology. UPnP Device Architecture – Internet gateway device control protocol. Level 2. Wide area network internet protocol. Connection service

Published By Publication Date Number of Pages
BSI 2017 82
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This document specifies the characteristics of the UPnP networked service named WANIPConnection, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1]. It is one component of the Device Control Protocol for the UPnP Internet Gateway Device (see [3]).

This service enables a UPnP control point to:

  • configure and control an IP connection between a LAN client on one side of an Internet gateway (see [3]) and a WAN host on the other side;

  • manage any physical WAN interface-such as DSL or cable-that supports an IP connection.

This service is a required in a WANConnectionDevice (see [5]) when the device supports an IP connection.

PDF Catalog

PDF Pages PDF Title
2 National foreword
9 Foreword
16 1 Scope
2 Normative references
17 3 Terms, definitions, symbols and abbreviated terms
19 4 Notations and conventions
4.1 Notation
4.2 Data types
4.2.1 Primary data types
20 4.2.2 Secondary data types
4.2.2.1 CSV lists
4.2.2.2 Other
21 4.3 Vendor-defined extensions
5 Service model
5.1 Service type
5.2 Changes from WANIPConnection:1
5.2.1 Backward compatibility
5.2.2 Generic requirements and other changes
5.2.3 New state variables
5.2.4 New actions
22 5.2.5 Changes in existing actions and procedures
5.3 Service Architecture
5.3.1 Introduction
23 5.3.2 Main feature sets
24 5.4 State variables
5.4.1 State variable overview
31 5.4.24.1 XML Schema Definition
5.4.24.1.1 Description of fields in the PortMappingList structure
32 5.4.24.2 Sample XML document
5.5 Eventing and Moderation
33 5.5.1 Eventing of PossibleConnectionTypes
5.5.2 Eventing of ConnectionStatus
5.5.3 Eventing of ExternalIPAddress
5.5.4 Eventing of PortMappingNumberOfEntries
5.5.5 Eventing of SystemUpdateID
5.5.6 Relationships among State Variables
34 5.6 Actions
35 5.6.1.1 Arguments
5.6.1.3 Service Requirements
36 5.6.1.4 Control Point Requirements When Calling The Action
5.6.1.5 Dependency on Device State
5.6.1.6 Effect on Device State
5.6.1.7 Errors
5.6.2.1 Arguments
5.6.2.4 Service Requirements
37 5.6.2.5 Control Point Requirements When Calling The Action
5.6.2.6 Dependency on Device State
5.6.2.7 Effect on Device State
5.6.2.8 Errors
5.6.3.1 Arguments
5.6.3.2 Service Requirements
38 5.6.3.3 Control Point Requirements When Calling The Action
5.6.3.4 Dependency on Device State
5.6.3.5 Effect on Device State
5.6.3.6 Errors
5.6.4.1 Arguments
5.6.4.2 Service Requirements
39 5.6.4.3 Control Point Requirements When Calling The Action
5.6.4.4 Dependency on Device State
5.6.4.5 Effect on Device State
5.6.4.6 Errors
5.6.5.1 Arguments
5.6.5.2 Service Requirements
40 5.6.5.3 Control Point Requirements When Calling The Action
5.6.5.4 Dependency on Device State
5.6.5.5 Effect on Device State
5.6.5.6 Errors
5.6.6.1 Arguments
5.6.6.3 Service Requirements
5.6.6.4 Control Point Requirements When Calling The Action
41 5.6.6.5 Dependency on Device State
5.6.6.6 Effect on Device State
5.6.6.7 Errors
5.6.7.1 Arguments
5.6.7.3 Service Requirements
5.6.7.4 Control Point Requirements When Calling The Action
5.6.7.5 Dependency on Device State
5.6.7.6 Effect on Device State
42 5.6.7.7 Errors
5.6.8.1 Arguments
5.6.8.3 Service Requirements
5.6.8.4 Control Point Requirements When Calling The Action
5.6.8.5 Dependency on Device State
5.6.8.6 Effect on Device State
5.6.8.7 Errors
43 5.6.9.1 Arguments
5.6.9.5 Service Requirements
5.6.9.6 Control Point Requirements When Calling The Action
5.6.9.7 Dependency on Device State
5.6.9.8 Effect on Device State
5.6.9.9 Errors
5.6.10.1 Arguments
44 5.6.10.3 Service Requirements
5.6.10.4 Control Point Requirements When Calling The Action
5.6.10.5 Dependency on Device State
5.6.10.6 Effect on Device State
5.6.10.7 Errors
5.6.11.1 Arguments
5.6.11.3 Service Requirements
5.6.11.4 Control Point Requirements When Calling The Action
45 5.6.11.5 Dependency on Device State
5.6.11.6 Effect on Device State
5.6.11.7 Errors
5.6.12.1 Arguments
5.6.12.3 Service Requirements
5.6.12.4 Control Point Requirements When Calling The Action
5.6.12.5 Dependency on Device State
5.6.12.6 Effect on Device State
5.6.12.7 Errors
46 5.6.13.1 Arguments
5.6.13.4 Service Requirements
5.6.13.5 Control Point Requirements When Calling The Action
5.6.13.6 Dependency on Device State
5.6.13.7 Effect on Device State
5.6.13.8 Errors
47 5.6.14.1 Arguments
5.6.14.3 Service Requirements
5.6.14.4 Control Point Requirements When Calling The Action
5.6.14.5 Dependency on Device State
48 5.6.14.6 Effect on Device State
5.6.14.7 Errors
5.6.15.1 Arguments
5.6.15.2 Service Requirements
49 5.6.15.3 Control Point Requirements When Calling The Action
5.6.15.4 Dependency on Device State
5.6.15.5 Effect on Device State
5.6.15.6 Errors
50 5.6.16.1 Arguments
51 5.6.16.2 Service Requirements
52 5.6.16.3 Control Point Requirements When Calling The Action
5.6.16.4 Dependency on Device State
5.6.16.5 Effect on Device State
5.6.16.6 Errors
53 5.6.17.1 Arguments
54 5.6.17.3 Service Requirements
55 5.6.17.4 Control Point Requirements When Calling The Action
5.6.17.5 Dependency on Device State
5.6.17.6 Effect on Device State
5.6.17.7 Errors
56 5.6.18.1 Arguments
5.6.18.2 Service Requirements
5.6.18.3 Control Point Requirements When Calling The Action
5.6.18.4 Dependency on Device State
5.6.18.5 Effect on Device State
5.6.18.6 Errors
57 5.6.19.1 Arguments
5.6.19.2 Service Requirements
58 5.6.19.3 Control Point Requirements When Calling The Action
5.6.19.4 Dependency on Device State
5.6.19.5 Effect on Device State
5.6.19.6 Errors
5.6.20.1 Arguments
5.6.20.2 Argument Descriptions
5.6.20.3 Service Requirements
5.6.20.4 Control Point Requirements When Calling The Action
5.6.20.5 Dependency on Device State
59 5.6.20.6 Effect on Device State
5.6.20.7 Errors
5.6.21.1 Arguments
5.6.21.3 Service Requirements
60 5.6.21.4 Control Point Requirements When Calling The Action
5.6.21.5 Dependency on Device State
5.6.21.6 Effect on Device State
5.6.21.7 Errors
5.6.22 Relationships Between Actions
5.6.23 Error Code Summary
62 5.7 Service Behavioral Model
5.7.1 Connection Initiation
63 5.7.2 Connection Termination
64 6 XML Service Description

Related products

BS ISO/IEC 29341-24-10:2017
$215.11