Overview
ISO/IEC 29341-18-10:2011 specifies the UPnP Remote Access Inbound Connection Configuration Service (InboundConnectionConfig) as part of the UPnP Device Architecture. The standard defines a UPnP service type (urn:schemas-upnp-org:service:InboundConnectionConfig:1) that lets UPnP control points configure and verify whether a host device on a home network is reachable from the public Internet. The service relies on Dynamic DNS to manage public addresses and STUN (Simple Traversal of UDP through NATs) to assess NAT navigability and determine if the NAT behaves as full-cone. The document is compliant with UPnP Device Architecture v1.0 and includes state variables, actions, eventing rules, XML service descriptions and test definitions.
Key topics and technical requirements
- Service definition and type: Formal service model for InboundConnectionConfig, including urn identifier and XML service description.
- Dynamic DNS configuration: Methods to configure a co‑located Dynamic DNS client (state variables and SetDynamicDNSConfigInfo action) so the device can associate a public DNS name with its dynamic public address.
- STUN client configuration: Actions and state variables (e.g., STUNServerAddress) to configure and run STUN checks to detect NAT type and external reachability.
- Network topology and reachability checks: NetworkTopologyInfo state variables and GetNetworkTopologyInfo action to report whether the device is reachable from the Internet.
- Actions and eventing: Defined actions such as GetDynamicDNSSupportedProtocols(), SetSTUNServerAddress(), and eventing/moderation rules for state changes; error codes and test cases are specified.
- XML schema and data structures: Normative XML Schema (ICCDS-XSD) for configuration data structures used by the service.
- Compliance: MUST/SHOULD/OPTIONAL semantics follow RFC 2119 and UPnP Device Architecture rules; vendor extensions must follow UPnP naming conventions.
Practical applications and who uses it
- Device manufacturers and firmware developers implementing UPnP Remote Access features on gateways, routers, NAS devices, IP cameras and home gateways.
- IoT and smart‑home vendors who need standardized inbound connectivity configuration (Dynamic DNS + STUN) for remote management and services.
- Software developers building UPnP control points (mobile apps, management consoles) that configure remote access reachability for home‑network devices.
- Network integrators and test labs verifying NAT traversal, Dynamic DNS behavior and UPnP compliance using the service’s test specifications.
Related standards and references
- UPnP Device Architecture v1.0 (DEVICE)
- UPnP Remote Access Architecture and RAServer device specifications (RAArchitecture, RAServer)
- ICCDS-XSD (XML Schema for InboundConnectionConfig data)
- Relevant IETF standards: RFC 3489 (STUN) and DNS RFCs (RFC 1034/1035), RFC 2119 (requirement keywords)
- Informative: UPnP InternetGatewayDevice (IGD) specification
Keywords: ISO/IEC 29341-18-10:2011, UPnP, InboundConnectionConfig, Dynamic DNS, STUN, NAT traversal, remote access, UPnP Device Architecture.