Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 29341 โ Information Technology โ UPnP Device Architecture Series
Information Technology โ UPnP Device Architecture (2015 edition family)
๐ BS ISO/IEC 29341 is the British Standard family published by BSI adopting the ISO/IEC 29341 series on the UPnP (Universal Plug and Play) device architecture. This batch collects six documents, developed with participation from BSI Technical Committee IST/6 (Data communications). UPnP is a plug-and-play device interconnection architecture for home and small-office networks: devices interconnect “zero-configuration” through automatic discovery, description, control and event notification. The ISO/IEC 29341 series standardizes the device types and service specifications of UPnP in the form of Device Control Protocols (DCPs), covering media servers/renderers, remote user interfaces, content directory, AV transport, connection management, network devices and security. The series is one of the foundational standard families for interoperability in the digital home, audio-visual sharing and smart home.
๐ก Some parts of this series are archived as scanned images; the related technical content in this article is compiled from public-domain knowledge. Always verify against the current BSI edition before citing.
1. Series Overview and Positioning ๐
The core of the UPnP system is the four-step “discovery โ description โ control โ event” interaction model: after power-on, a device announces itself via SSDP multicast; a Control Point learns the device’s capabilities (services and state variables) from the description document; SOAP actions perform control; and GENA events notify state changes. The ISO/IEC 29341 series standardizes this system and the DCP specifications of each device type (media server, media renderer, remote UI client/server, etc.), enabling interoperability across vendors. The files in this batch focus on the UPnP Remote User Interface (RUI) and related services, reflecting the evolution of UPnP from simple AV control toward multi-screen interaction. BS ISO/IEC 29341 is the official UK implementation of the series.
โ ๏ธ By design UPnP trusts devices on the local network and lacks strong built-in authentication; it has historically been exploited in attacks. It is recommended to isolate UPnP traffic at the network boundary during deployment and to monitor firmware security updates.
2. Series Structure and Technical Content ๐
The six documents of the BS ISO/IEC 29341 series in this batch (2015 editions) form the UPnP remote user interface and related service system:
| Part | Subject | Main Content | Year |
|---|---|---|---|
| BS ISO IEC 29341-12-1 | Remote User Interface client device | RUI client device definition and discovery/control flow | 2015 |
| BS ISO IEC 29341-12-2 | Remote User Interface server device | RUI server device definition and presentation/transport flow | 2015 |
| BS ISO IEC 29341-12-10 | Remote User Interface client service | RUI client service interface, state variables and actions | 2015 |
| BS ISO IEC 29341-12-11 | Remote User Interface server service | RUI server service interface and transport-protocol support | 2015 |
| BS ISO IEC 29341-3-10 | Basic device services | UPnP basic device management services (scanned, from public-domain knowledge) | 2015 |
| BS ISO IEC 29341-7-11 | Media/network related services | Media and network device related services (scanned, from public-domain knowledge) | 2015 |
The internal logic of the series: the Remote User Interface (RUI) mechanism lets a “thin client” (e.g., a TV or projector) display UI content from a “rich server” (e.g., a phone or PC); Parts 12-1/12-2 define the client and server devices, Parts 12-10/12-11 define the corresponding services (including UIListing, Session and Input services); Parts 3-10 and 7-11 cover basic device and media/network services. In engineering, the appropriate DCP specification is selected by device role.
โ
Parts 12-1, 12-10 and 12-11 of the series are available as full readable text; Parts 12-2, 3-10 and 7-11 are scanned versions and are summarized here on the basis of general knowledge in the field.
3. Key Technical Requirements ๐ฌ
3.1 Remote User Interface client device (Part 12-1)
Part 12-1 specifies the RUI client device: as a UPnP device it is discovered on the network and hosts the RUI client service, receiving UI descriptions pushed by servers and rendering them for the user. The part defines the device description, embedded services and event behaviour, so that “display devices” such as TVs and set-top boxes can host interactive interfaces from mobile devices.
3.2 RUI client service (Part 12-10)
Part 12-10 specifies the interface details of the RUI client service: state variables (such as UIListingUpdate, A_ARG_TYPE_DeviceProfile, the list of compatible UIs, etc.) and actions (browsing available UIs, starting/stopping sessions, handling user input, etc.). The service notifies control points of changes to the list of available UIs via events, and manages sessions and input channels with the remote server.
3.3 UPnP device architecture and DCP framework
The UPnP device architecture consists of the common framework (discovery, description, control, event) overlaid with device types (DCPs); the files in this series standardize the specification text of each DCP as a part of ISO/IEC 29341. Implementations must follow the unified description format (XML), SOAP actions, SSDP discovery and GENA events to ensure cross-vendor interoperability.
โ ๏ธ RUI sessions involve the transport and display of UI content; attention is needed to the timing consistency of input return and UI update. In weak-network or long-session scenarios, session keep-alive, timeout handling and graceful exit should be implemented to avoid UI state drift.
4. Engineering Practice ๐ ๏ธ
- ๐ Multi-screen interaction: a phone/PC acts as an RUI server, projecting its UI to a TV/set-top box for “one application, multi-screen presentation”.
- ๐ง Smart home integration: use UPnP DCPs to achieve discovery and coordinated control among lighting, AV and sensor devices.
- ๐ Compatibility validation: run interoperability tests across vendors against the unified DCPs, verifying consistency of discovery, control and events.
- ๐ Security hardening: isolate the UPnP broadcast boundary, close internet-facing UPnP exposure, and track firmware security advisories.
5. Frequently Asked Questions โ
โ Q: What is the relationship between UPnP and DLNA?
A: DLNA is a media-interoperability guideline based on UPnP media DCPs, specifying media servers/renderers and playback flow; the ISO/IEC 29341 series is the international-standard source of these DCPs.
A: DLNA is a media-interoperability guideline based on UPnP media DCPs, specifying media servers/renderers and playback flow; the ISO/IEC 29341 series is the international-standard source of these DCPs.
โ Q: What problem does the Remote User Interface (RUI) solve?
A: RUI lets devices with limited display capability (TVs, projectors) present UI from content-rich devices (phones, PCs), avoiding duplicating applications on each device and enabling “content at home, interface anywhere”.
A: RUI lets devices with limited display capability (TVs, projectors) present UI from content-rich devices (phones, PCs), avoiding duplicating applications on each device and enabling “content at home, interface anywhere”.
๐ Q: Why are some parts marked as “scanned”?
A: In this batch of archive material, those parts exist as scanned images; the technical content is summarized from public-domain knowledge. Verify against the current BSI edition before formal citation.
A: In this batch of archive material, those parts exist as scanned images; the technical content is summarized from public-domain knowledge. Verify against the current BSI edition before formal citation.
โ Q: How does UPnP compare with modern IoT protocols such as MQTT/HTTP?
A: UPnP targets LAN plug-and-play and media control, has a long history and mature ecosystem but a simpler security model; modern IoT protocols target cloud and cross-network scenarios with stronger security and scalability. The choice depends on the deployment scenario.
A: UPnP targets LAN plug-and-play and media control, has a long history and mature ecosystem but a simpler security model; modern IoT protocols target cloud and cross-network scenarios with stronger security and scalability. The choice depends on the deployment scenario.