ISO/IEC 29341-24-10:2017 PDF

Information technology — UPnP Device Architecture — Part 24-10: Internet gateway device control protocol — Level 2 — Wide area network internet protocol — Connection service

Первая страница стандарта ISO/IEC 29341-24-10:2017

Открыть превью (PDF)

Название (английский):

ISO/IEC 29341-24-10:2017

Information technology — UPnP Device Architecture — Part 24-10: Internet gateway device control protocol — Level 2 — Wide area network internet protocol — Connection service

Статус документа:: Действующий
Формат:: Электронный (PDF)
Количество страниц:: 65
Дата публикации:: 13 сентября 2017 г.
Издание:: ISO/IEC IS 29341 edition 1 version 1
ICS:: 35.200

Язык документа:

ruen

Срок поставки:11 раб. дн. (перевод)

Цена:975 €

Описание (английский):

ISO/IEC 29341-24-10:2017 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.

Технические детали

Технический комитет: ISO/IEC JTC 1 - Information technology
SKU: ISO/IEC 29341-24-10:2017

Abstract

Overview

ISO/IEC 29341-24-10:2017 defines the WANIPConnection v2 service for UPnP Internet Gateway Devices (IGD). Aligned with the UPnP Device Architecture 1.0, this standard specifies the network service used by a UPnP control point to configure and control IP connections and manage WAN interfaces (DSL, cable, etc.). It is a required service for a WANConnectionDevice that supports IP connections and is a component of the UPnP IGD Device Control Protocol.

Key topics and technical requirements

Service model and XML description: Formal service type, state variables and action signatures in an XML service description compliant with UPnP Device Architecture.
State variables: Definitions for connection-related variables such as ConnectionType, ConnectionStatus, ExternalIPAddress, PortMappingNumberOfEntries, NATEnabled, RSIPAvailable, Uptime, and error/state enumerations.
Actions (control API): Standard actions include SetConnectionType(), GetConnectionTypeInfo(), RequestConnection(), RequestTermination(), ForceTermination(), GetExternalIPAddress(), AddPortMapping(), AddAnyPortMapping(), DeletePortMapping(), DeletePortMappingRange(), GetListOfPortMappings(), and others for managing auto/idle disconnect and port mappings.
Port mapping and NAT control: Procedures and error codes for adding, listing, and deleting port mappings (port forwarding), lease durations, protocols, and port ranges.
Eventing and moderation: Rules for state change event notifications (e.g., ExternalIPAddress, ConnectionStatus, PortMappingNumberOfEntries) so control points can react to gateway changes.
Backward compatibility and Level 2 features: Clarifies changes from earlier WANIPConnection version(s) and compatibility behaviors.

Applications and who uses it

Home and SOHO router vendors / CPE manufacturers: Implement this service in device firmware to expose WAN configuration and NAT/port-forwarding control to UPnP control points.
Router firmware and SDK developers: Use the standard to implement compliant APIs and XML service descriptions.
Application developers and UPnP control point authors: Enable automatic NAT traversal, remote access, and port mapping for games, VoIP, remote management, NAS, and IoT devices.
Network integrators and system testers: Validate IGD behavior, eventing, and error handling against the standard to ensure interoperability.

Related standards

ISO/IEC 29341 family - UPnP Device Architecture and related Device Control Protocol parts (Internet Gateway Device specifications).
UPnP Device Architecture 1.0 (baseline architecture and requirements for UPnP services).

By following ISO/IEC 29341-24-10:2017, device makers and software developers ensure interoperable UPnP WAN IP connection control, consistent NAT/port-mapping behavior, and robust remote-access capabilities across Internet gateway devices.

Overview

Key topics and technical requirements

Service model and XML description: Formal service type, state variables and action signatures in an XML service description compliant with UPnP Device Architecture.
State variables: Definitions for connection-related variables such as ConnectionType, ConnectionStatus, ExternalIPAddress, PortMappingNumberOfEntries, NATEnabled, RSIPAvailable, Uptime, and error/state enumerations.
Actions (control API): Standard actions include SetConnectionType(), GetConnectionTypeInfo(), RequestConnection(), RequestTermination(), ForceTermination(), GetExternalIPAddress(), AddPortMapping(), AddAnyPortMapping(), DeletePortMapping(), DeletePortMappingRange(), GetListOfPortMappings(), and others for managing auto/idle disconnect and port mappings.
Port mapping and NAT control: Procedures and error codes for adding, listing, and deleting port mappings (port forwarding), lease durations, protocols, and port ranges.
Eventing and moderation: Rules for state change event notifications (e.g., ExternalIPAddress, ConnectionStatus, PortMappingNumberOfEntries) so control points can react to gateway changes.
Backward compatibility and Level 2 features: Clarifies changes from earlier WANIPConnection version(s) and compatibility behaviors.

Applications and who uses it

Home and SOHO router vendors / CPE manufacturers: Implement this service in device firmware to expose WAN configuration and NAT/port-forwarding control to UPnP control points.
Router firmware and SDK developers: Use the standard to implement compliant APIs and XML service descriptions.
Application developers and UPnP control point authors: Enable automatic NAT traversal, remote access, and port mapping for games, VoIP, remote management, NAS, and IoT devices.
Network integrators and system testers: Validate IGD behavior, eventing, and error handling against the standard to ensure interoperability.

Related standards

ISO/IEC 29341 family - UPnP Device Architecture and related Device Control Protocol parts (Internet Gateway Device specifications).
UPnP Device Architecture 1.0 (baseline architecture and requirements for UPnP services).

ISO/IEC 29341-24-10:2017 PDF

Технические детали

Abstract

Overview

Key topics and technical requirements

Applications and who uses it

Related standards

Похожие стандарты

Abstract

Overview

Key topics and technical requirements

Applications and who uses it

Related standards

Похожие стандарты

Information technology — UPnP Device Architecture — Part 4-13: Audio Video Device Control Protocol - Level 2…

Systems and software engineering — Software life cycle processes

Asset management — Vocabulary, overview and principles

Asset management — Asset management system — Requirements

Information technology — Radio frequency identification device conformance test methods — Part 2: Test method…

Information technology — Multimedia framework (MPEG-21) — Part 22: User Description

Milk — Determination of the lactoperoxidase activity — Photometric method (Reference method)

Carbonaceous materials for the production of aluminium — Cold and tepid ramming pastes — Expansion/shrinkage…