Overview
ISO/IEC 29341-12-1:2015 specifies the UPnP device template for a Remote User Interface (Remote UI) Client Device. It is part of the UPnP Device Architecture series and defines the device type urn:schemas-upnp-org:device:RemoteUIClientDevice:1. The standard is compliant with UPnP Device Architecture v1.0 and describes how a RemoteUIClientDevice can be implemented either as a UPnP root device or embedded inside another device. The device encapsulates services required by the Remote UI Device Control Protocol (DCP), enabling discovery, control and optional secure operation of remote user interface clients on a local network.
Key Topics and Requirements
- Device type and model
- Defines the RemoteUIClientDevice device URN and recommended implementation models.
- Two service deployment models: DeviceSecurity inside the RemoteUIClientDevice, or DeviceSecurity outside (shared with another device in the same physical product).
- Required and optional services
- RemoteUIClient (required): supports UI connection management, optional availability management and basic user interaction features.
- DeviceSecurity (optional but recommended): supports device ownership, access control, secure sessions and secure actions to protect UPnP operations.
- Security and access control
- Recommends use of the UPnP DeviceSecurity service to secure actions; normative Annex A defines Access Control elements (permissions, profiles, ACL entries).
- XML device description
- Specifies metadata and XML description elements used for UPnP discovery and service binding.
- Conformance and testing
- Includes device requirements tables and test guidance to validate interoperability with the UPnP Remote UI Client DCP.
Applications and Who Uses It
- Device manufacturers and firmware developers building:
- Smart TVs, set‑top boxes, media renderers and consumer devices that host or render remote UIs.
- IoT devices and kiosks that expose or consume remote user interfaces over LANs.
- System integrators and platform vendors implementing UPnP-based remote-control ecosystems.
- Security architects and test labs validating UPnP device behavior, access control and secure session handling.
- Software developers implementing RemoteUIClient service stacks or embedding Remote UI functionality into larger UPnP devices.
Related Standards
Keywords: UPnP, Remote UI, RemoteUIClientDevice, Device Control Protocol, ISO/IEC 29341-12-1:2015, DeviceSecurity, access control, XML device description, UPnP device template.
Open preview (PDF)Information technology — UPnP Device Architecture — Part 12-1: Remote User Interface Device Control Protocol - Remote User Interface Client Device