Overview
ISO/IEC 29341-18-1:2011 - “Information technology - UPnP Device Architecture - Part 18-1: Remote Access Device Control Protocol - Remote Access Architecture” defines an architecture and infrastructure to enable UPnP devices, services and control points deployed on remote physical devices to interact with UPnP devices on a home network as if they were on the same LAN. The standard describes how to logically extend a home network to include remote devices using established mechanisms while preserving consistent behavior across different bridging models.
Key topics and technical requirements
- Remote Access Paradigm: Defines the overall architecture that connects remote and home network segments and allows multiple bridging models to be plugged into a consistent interface.
- Functional components: Describes components such as the Remote Access Client (RAC), Remote Access Server (RAS), Remote Access Discovery Agent (RADiscoveryAgent), Remote Access Transport Agent, and RADA (Remote Access Device Agent) and their roles in discovery, synchronization and transport.
- Phased operation: Specifies Setup, Operational and Management phases - including configuration, connection establishment, discovery synchronization, heartbeat, timeout and administrative shutdown behaviors.
- Inbound connection configuration: Addresses the mechanisms for enabling inbound access into the home network (references InboundConnectionConfig service).
- Network considerations: Discusses IPv4/IPv6 addressing, NAT traversal issues, STUN-like configurations, server name resolution and detection of NAT type on the server side.
- Behavioral requirements: Uses RFC 2119 keywords (MUST/SHOULD/MAY) to define required, recommended and optional behaviors for interoperability and security.
- Interoperability constraints: The architecture enforces uniform behavior but explicitly does not define interfaces for non‑UPnP “service” gateways.
Practical applications
- Remote control and monitoring of home IoT devices and media devices from cloud-hosted or mobile control points.
- Extending home automation systems to include devices located off‑site (e.g., sensors in a vacation home).
- Remote diagnostics and device management by service providers through a logically extended UPnP domain.
- Enabling media streaming and UPnP AV scenarios where sources or control points are outside the local network.
Who should use this standard
- Consumer router and residential gateway manufacturers implementing UPnP Remote Access features.
- IoT device makers and UPnP device developers requiring standardized remote interaction.
- Network architects and service providers designing remote management, NAT traversal and discovery mechanisms.
- Systems integrators building home automation and remote control solutions.
Related standards
- UPnP Device Architecture (UDA)
- UPnP RA parts and services: InboundConnectionConfig, RAClient, RADAConfig, RADASync, RADiscoveryAgent, RAServer, RATAConfig
- IPv6/IPv4 IP support references (UPnP annexes) and NAT/STUN traversal techniques
Keywords: ISO/IEC 29341-18-1:2011, UPnP Remote Access, Remote Access Architecture, Remote Access Device Control Protocol, UPnP, home network, NAT traversal, IPv6, device discovery.
Open preview (PDF)Information technology - UPnP Device Architecture - Part 18-1: Remote Access Device Control Protocol - Remote Access Architecture
