Overview

ISO/IEC 29341-28-1:2017 - "Information technology - UPnP Device Architecture - Part 28-1: Multiscreen device control protocol - Multiscreen architecture" defines the foundational Multi‑Screen Architecture for UPnP Multi‑Screen Device Control Protocols (DCPs). Adopted from UPnP specifications, this standard establishes an open interface and interaction model between UPnP control points and UPnP screen devices to enable interoperable multi‑screen and second‑screen experiences across vendors.

Key topics and technical scope

The standard addresses the architecture-level requirements needed to implement UPnP Multi‑Screen solutions. Primary technical topics include:

Interoperability model for control points and screen devices to support multi‑vendor ecosystems.
Message, data and XML notations including data types, CSV lists, XML fragments and namespaces used across Multi‑Screen DCPs.
Namespace and schema management, versioning and recommended namespace prefixes for consistent implementation.
Vendor‑defined extensions guidance (action names, state variables, XML elements) to allow implementation‑specific features while preserving compatibility.
Definitions of roles such as Screen Device and Screen Control Point and their general interactions.
Normative references and conventions that form the basis for the companion device and service templates.

(ISO/IEC 29341-28-1:2017 is an architecture-level document; specific service templates and APIs are defined in related parts of the ISO/IEC 29341 series.)

Applications and practical value

ISO/IEC 29341-28-1:2017 is designed to support real-world multi‑screen and second‑screen use cases:

Seamless content sharing and playback control across TVs, tablets and mobile devices without vendor‑locked apps.
Second‑screen interactive services (synchronized supplementary content, real‑time controls, multi‑display storytelling).
Time‑sensitive and interactive applications such as live event synchronization, multiroom displays and companion experiences.
Platform and device interoperability, reducing fragmentation for manufacturers, app developers and service providers.

Who should use this standard

Device manufacturers building UPnP‑compliant displays and media renderers.
Platform vendors and app developers creating second‑screen or multiscreen applications.
System integrators and OEMs seeking cross‑vendor interoperability.
Standards implementers and test labs validating UPnP Multi‑Screen conformance.

Related standards and notes

Related UPnP/ISO parts: ISO/IEC 29341-28-2 (UPnP MultiScreen Screen device) and ISO/IEC 29341-28-10 (Application Management service).
Note: The UPnP Multi‑Screen specifications were adopted into ISO/IEC and some technologies may be subject to patent declarations; implementers should review the standard’s patent and licensing notices.

Overview

Key topics and technical scope

The standard addresses the architecture-level requirements needed to implement UPnP Multi‑Screen solutions. Primary technical topics include:

Interoperability model for control points and screen devices to support multi‑vendor ecosystems.
Message, data and XML notations including data types, CSV lists, XML fragments and namespaces used across Multi‑Screen DCPs.
Namespace and schema management, versioning and recommended namespace prefixes for consistent implementation.
Vendor‑defined extensions guidance (action names, state variables, XML elements) to allow implementation‑specific features while preserving compatibility.
Definitions of roles such as Screen Device and Screen Control Point and their general interactions.
Normative references and conventions that form the basis for the companion device and service templates.

(ISO/IEC 29341-28-1:2017 is an architecture-level document; specific service templates and APIs are defined in related parts of the ISO/IEC 29341 series.)

Applications and practical value

ISO/IEC 29341-28-1:2017 is designed to support real-world multi‑screen and second‑screen use cases:

Seamless content sharing and playback control across TVs, tablets and mobile devices without vendor‑locked apps.
Second‑screen interactive services (synchronized supplementary content, real‑time controls, multi‑display storytelling).
Time‑sensitive and interactive applications such as live event synchronization, multiroom displays and companion experiences.
Platform and device interoperability, reducing fragmentation for manufacturers, app developers and service providers.

Who should use this standard

Device manufacturers building UPnP‑compliant displays and media renderers.
Platform vendors and app developers creating second‑screen or multiscreen applications.
System integrators and OEMs seeking cross‑vendor interoperability.
Standards implementers and test labs validating UPnP Multi‑Screen conformance.

Related standards and notes

Related UPnP/ISO parts: ISO/IEC 29341-28-2 (UPnP MultiScreen Screen device) and ISO/IEC 29341-28-10 (Application Management service).
Note: The UPnP Multi‑Screen specifications were adopted into ISO/IEC and some technologies may be subject to patent declarations; implementers should review the standard’s patent and licensing notices.

ISO/IEC 29341-28-1:2017 PDF

Technical details

Abstract

Overview

Key topics and technical scope

Applications and practical value

Who should use this standard

Related standards and notes

Related standards

Abstract

Overview

Key topics and technical scope

Applications and practical value

Who should use this standard

Related standards and notes

Related standards

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

Information technology. UPnP Device Architecture. Multiscreen device control protocol. Screen device.

Information technology. UPnP Device Architecture. Multiscreen device control protocol. Application management…