ISO/IEC 29341-28-1:2017

Information technology — UPnP Device Architecture — Part 28-1: Multiscreen device control protocol — Multiscreen architecture

Today multi-screen/second-screen solutions are proliferating. However, each is a proprietary vertical for particular vendor(s). Therefore users expectations aren't being met: - Seamless interoperability across vendors. - Ability for second screen integrated usages rather than 100s of different apps. The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open interface to enable this interoperability between devices and applications, i.e. enable time-sensitive and interactive services, including implementation-specific applications, among various display devices. ISO/IEC 29341-28-1:2017 describes the overall Multi-Screen Architecture, which forms the foundation for the UPnP Multi-Screen Device and Service templates. The Multi-Screen Architecture defines the general interaction between UPnP control points and UPnP devices defined by the UPnP Multi-Screen DCPs.

Technologies de l'information — Architecture de dispositif UPnP — Partie 28-1: Protocole de contrôle de dispositif multi-écran — Architecture multi-écran

General Information

• Status: Published
• Publication Date: 12-Sep-2017
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9060 - Close of review
• Start Date: 03-Mar-2028

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 29341-28-1
First edition
2017-09
Information technology — UPnP
Device Architecture —
Part 28-1:
Multiscreen device control protocol —
Multiscreen architecture
Technologies de l'information — Architecture de dispositif UPnP —
Partie 28-1: Protocole de contrôle de dispositif multi-écran —
Architecture multi-écran
Reference number
ISO/IEC 29341-28-1:2017(E)
©
ISO/IEC 2017

---------------------- Page: 1 ----------------------
ISO/IEC 29341-28-1:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO/IEC 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 29341-28-1:2017(E)

CONTENTS

1  Scope . iv
2  Normative references . 1
3  Terms, definitions, symbols and abbreviations . 2
4  Notations and Conventions . 3
4.1  Notation . 3
4.1.1  Data Types . 3
4.1.2  Strings Embedded in Other Strings . 4
4.2  Derived Data Types . 4
4.2.1  CSV Lists . 4
4.2.2  XML Document . 5
4.2.3  XML Fragment . 6
4.3  Management of XML Namespaces in Standardized DCPs . 6
4.3.1  Namespace Prefix Requirements . 7
4.3.2  Namespace Names, Namespace Versioning and Schema Versioning . 8
4.3.3  Namespace Usage Examples . 10
4.4  Vendor-defined Extensions . 10
4.4.1  Vendor-defined Action Names . 10
4.4.2  Vendor-defined State Variable Names . 11
4.4.3  Vendor-defined XML Elements and attributes . 11
5  Multi-Screen Architectural Overview . 11
5.1  Screen Device . 11
5.2  Screen Control Point . 12
Table 1 — CSV Examples . 5
Table 2 — Namespace Definitions . 7
Table 3 — Schema-related Information . 7
Table 4 — Default Namespaces for the Multi-Screen Specifications . 8


 ISO/IEC 2017 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 29341-28-1:2017(E)


Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
National bodies that are members of ISO or IEC participate in the development of
International Standards through technical committees established by the respective
organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations,
governmental and non‐governmental, in liaison with ISO and IEC, also take part in the
work. In the field of information technology, ISO and IEC have established a joint technical
committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further
maintenance are described in the ISO/IEC Directives, Part 1. In particular the different
approval criteria needed for the different types of document should be noted. This
document was drafted in accordance with the editorial rules of the ISO/IEC Directives,
Part 2 (see http://www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be
the subject of patent rights. ISO and IEC shall not be held responsible for identifying any
or all such patent rights. Details of any patent rights identified during the development of
the document will be in the Introduction and/or on the ISO list of patent declarations
received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users
and does not constitute an endorsement.
For an explanation on the voluntary nature of Standard, the meaning of the ISO specific
terms and expressions related to conformity assessment, as well as information about
ISO’s adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the
following URL: Foreword – Supplementary information
ISO/IEC 29341‐28‐1 was prepared by UPnP Forum and adopted, under the PAS
procedure, by joint technical committee ISO/IEC JTC 1, Information technology, in
parallel with its approval by national bodies of ISO and IEC.
The list of all currently available parts of ISO/IEC 29341 series, under the general title
Information technology — UPnP Device Architecture, can be found on the ISO web site.
iv   ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 29341-28-1:2017(E)
Introduction
ISO and IEC draw attention to the fact that it is claimed that compliance with this document may
involve the use of patents as indicated below.

ISO and IEC take no position concerning the evidence, validity and scope of these patent rights. The
holders of -these patent rights have assured ISO and IEC that they are willing to negotiate licenses
under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In
this respect, the statements of the holders of these patent rights are registered with ISO and IEC.

Intel Corporation has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Intel Corporation
Standards Licensing Department
5200 NE Elam Young Parkway
MS: JFS-98
USA – Hillsboro, Oregon 97124
Microsoft Corporation has informed IEC and ISO that it has patent applications or granted
patents as listed below:
6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US;
7069312 / US; 10/783 524 /US
Information may be obtained from:
Microsoft Corporation
One Microsoft Way
USA – Redmond WA 98052
Philips International B.V. has informed IEC and ISO that it has patent applications or granted
patents.
Information may be obtained from:
Philips International B.V. – IP&S
High Tech campus, building 44 3A21
NL – 5656 Eindhoven
NXP B.V. (NL) has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
NXP B.V. (NL)
High Tech campus 60
NL – 5656 AG Eindhoven
Matsushita Electric Industrial Co. Ltd. has informed IEC and ISO that it has patent
applications or granted patents.
Information may be obtained from:
Matsushita Electric Industrial Co. Ltd.
1-3-7 Shiromi, Chuoh-ku
JP – Osaka 540-6139
 ISO/IEC 2017 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 29341-28-1:2017(E)


Hewlett Packard Company has informed IEC and ISO that it has patent applications or
granted patents as listed below:
5 956 487 / US; 6 170 007 / US; 6 139 177 / US; 6 529 936 / US; 6 470 339 / US; 6 571 388 /
US; 6 205 466 / US
Information may be obtained from:
Hewlett Packard Company
1501 Page Mill Road
USA – Palo Alto, CA 94304
Samsung Electronics Co. Ltd. has informed IEC and ISO that it has patent applications or
granted patents.
Information may be obtained from:
Digital Media Business, Samsung Electronics Co. Ltd.
416 Maetan-3 Dong, Yeongtang-Gu,
KR – Suwon City 443-742
Huawei Technologies Co., Ltd. has informed IEC and ISO that it has patent applications or
granted patents.
Information may be obtained from:
Huawei Technologies Co., Ltd.
Administration Building, Bantian Longgang District
Shenzhen – China 518129
Qualcomm Incorporated has informed IEC and ISO that it has patent applications or granted
patents.
Information may be obtained from:
Qualcomm Incorporated
5775 Morehouse Drive
San Diego, CA – USA 92121
Telecom Italia S.p.A.has informed IEC and ISO that it has patent applications or granted
patents.
Information may be obtained from:
Telecom Italia S.p.A.
Via Reiss Romoli, 274
Turin - Italy 10148
Cisco Systems informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA – USA 95134
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights other than those identified above. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.

vi   ISO/IEC 2017 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 29341-28-1:2017(E)
Original UPnP Document
Reference may be made in this document to original UPnP documents. These references are
retained in order to maintain consistency between the specifications as published by ISO/IEC
and by UPnP Implementers Corporation and later by UPnP Forum. The following table
indicates the original UPnP document titles and the corresponding part of ISO/IEC 29341:
UPnP Document Title ISO/IEC 29341 Part
UPnP Device Architecture 1.0 ISO/IEC 29341-1:2008
UPnP Device Architecture Version 1.0 ISO/IEC 29341-1:2011
UPnP Device Architecture 1.1 ISO/IEC 29341-1-1:2011
UPnP Device Architecture 2.0 ISO/IEC 29341-1-2
UPnP Basic:1 Device ISO/IEC 29341-2
UPnP AV Architecture:1 ISO/IEC 29341-3-1:2008
UPnP AV Architecture:1 ISO/IEC 29341-3-1:2011
UPnP AVTransport:1 Service ISO/IEC 29341-3-10
UPnP ConnectionManager:1 Service ISO/IEC 29341-3-11
UPnP ContentDirectory:1 Service ISO/IEC 29341-3-12
UPnP RenderingControl:1 Service ISO/IEC 29341-3-13
UPnP MediaRenderer:1 Device ISO/IEC 29341-3-2
UPnP MediaRenderer:2 Device ISO/IEC 29341-3-2:2011
UPnP MediaServer:1 Device ISO/IEC 29341-3-3
UPnP AVTransport:2 Service ISO/IEC 29341-4-10:2008
UPnP AVTransport:2 Service ISO/IEC 29341-4-10:2011
UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11:2008
UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11:2011
UPnP ContentDirectory:2 Service ISO/IEC 29341-4-12
UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:2008
UPnP RenderingControl:2 Service ISO/IEC 29341-4-13:2011
UPnP ScheduledRecording:1 ISO/IEC 29341-4-14
UPnP ScheduledRecording:2 ISO/IEC 29341-4-14:2011
UPnP MediaRenderer:2 Device ISO/IEC 29341-4-2
UPnP MediaServer:2 Device ISO/IEC 29341-4-3
UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4:2008
UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4:2011
UPnP DigitalSecurityCamera:1 Device ISO/IEC 29341-5-1
UPnP DigitalSecurityCameraMotionImage:1 Service ISO/IEC 29341-5-10
UPnP DigitalSecurityCameraSettings:1 Service ISO/IEC 29341-5-11
UPnP DigitalSecurityCameraStillImage:1 Service ISO/IEC 29341-5-12
UPnP HVAC_System:1 Device ISO/IEC 29341-6-1
UPnP ControlValve:1 Service ISO/IEC 29341-6-10
UPnP HVAC_FanOperatingMode:1 Service ISO/IEC 29341-6-11
UPnP FanSpeed:1 Service ISO/IEC 29341-6-12
UPnP HouseStatus:1 Service ISO/IEC 29341-6-13
UPnP HVAC_SetpointSchedule:1 Service ISO/IEC 29341-6-14
UPnP TemperatureSensor:1 Service ISO/IEC 29341-6-15
UPnP TemperatureSetpoint:1 Service ISO/IEC 29341-6-16
UPnP HVAC_UserOperatingMode:1 Service ISO/IEC 29341-6-17
UPnP HVAC_ZoneThermostat:1 Device ISO/IEC 29341-6-2
 ISO/IEC 2017 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO/IEC 29341-28-1:2017(E)


UPnP BinaryLight:1 Device ISO/IEC 29341-7-1
UPnP Dimming:1 Service ISO/IEC 29341-7-10
UPnP SwitchPower:1 Service ISO/IEC 29341-7-11
UPnP DimmableLight:1 Device ISO/IEC 29341-7-2
UPnP InternetGatewayDevice:1 Device ISO/IEC 29341-8-1
UPnP LANHostConfigManagement:1 Service ISO/IEC 29341-8-10
UPnP Layer3Forwarding:1 Service ISO/IEC 29341-8-11
UPnP LinkAuthentication:1 Service ISO/IEC 29341-8-12
UPnP RadiusClient:1 Service ISO/IEC 29341-8-13
UPnP WANCableLinkConfig:1 Service ISO/IEC 29341-8-14
UPnP WANCommonInterfaceConfig:1 Service ISO/IEC 29341-8-15
UPnP WANDSLLinkConfig:1 Service ISO/IEC 29341-8-16
UPnP WANEthernetLinkConfig:1 Service ISO/IEC 29341-8-17
UPnP WANIPConnection:1 Service ISO/IEC 29341-8-18
UPnP WANPOTSLinkConfig:1 Service ISO/IEC 29341-8-19
UPnP LANDevice:1 Device ISO/IEC 29341-8-2
UPnP WANPPPConnection:1 Service ISO/IEC 29341-8-20
UPnP WLANConfiguration:1 Service ISO/IEC 29341-8-21
UPnP WANDevice:1 Device ISO/IEC 29341-8-3
UPnP WANConnectionDevice:1 Device ISO/IEC 29341-8-4
UPnP WLANAccessPointDevice:1 Device ISO/IEC 29341-8-5
UPnP Printer:1 Device ISO/IEC 29341-9-1
UPnP ExternalActivity:1 Service ISO/IEC 29341-9-10
UPnP Feeder:1.0 Service ISO/IEC 29341-9-11
UPnP PrintBasic:1 Service ISO/IEC 29341-9-12
UPnP Scan:1 Service ISO/IEC 29341-9-13
UPnP Scanner:1.0 Device ISO/IEC 29341-9-2
UPnP QoS Architecture:1.0 ISO/IEC 29341-10-1
UPnP QosDevice:1 Service ISO/IEC 29341-10-10
UPnP QosManager:1 Service ISO/IEC 29341-10-11
UPnP QosPolicyHolder:1 Service ISO/IEC 29341-10-12
UPnP QoS Architecture:2 ISO/IEC 29341-11-1
UPnP QosDevice:2 Service ISO/IEC 29341-11-10
UPnP QosManager:2 Service ISO/IEC 29341-11-11
UPnP QosPolicyHolder:2 Service ISO/IEC 29341-11-12
UPnP QOS v2 Schema Files ISO/IEC 29341-11-2
UPnP RemoteUIClientDevice:1 Device ISO/IEC 29341-12-1
UPnP RemoteUIClient:1 Service ISO/IEC 29341-12-10
UPnP RemoteUIServer:1 Service ISO/IEC 29341-12-11
UPnP RemoteUIServerDevice:1 Device ISO/IEC 29341-12-2
UPnP DeviceSecurity:1 Service ISO/IEC 29341-13-10
UPnP SecurityConsole:1 Service ISO/IEC 29341-13-11
UPnP ContentDirectory:3 Service ISO/IEC 29341-14-12:2011
UPnP MediaServer:3 Device ISO/IEC 29341-14-3:2011
UPnP ContentSync:1 ISO/IEC 29341-15-10:2011
UPnP Low Power Architecture:1 ISO/IEC 29341-16-1:2011
UPnP LowPowerProxy:1 Service ISO/IEC 29341-16-10:2011
viii   ISO/IEC 2017 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 29341-28-1:2017(E)
UPnP LowPowerDevice:1 Service ISO/IEC 29341-16-11:2011
UPnP QoS Architecture:3 ISO/IEC 29341-17-1:2011
UPnP QosDevice:3 Service ISO/IEC 29341-17-10:2011
UPnP QosManager:3 Service ISO/IEC 29341-17-11:2011
UPnP QosPolicyHolder:3 Service ISO/IEC 29341-17-12:2011
UPnP QosDevice:3 Addendum ISO/IEC 29341-17-13:2011
UPnP RemoteAccessArchitecture:1 ISO/IEC 29341-18-1:2011
UPnP InboundConnectionConfig:1 Service ISO/IEC 29341-18-10:2011
UPnP RADAConfig:1 Service ISO/IEC 29341-18-11:2011
UPnP RADASync:1 Service ISO/IEC 29341-18-12:2011
UPnP RATAConfig:1 Service ISO/IEC 29341-18-13:2011
UPnP RAClient:1 Device ISO/IEC 29341-18-2:2011
UPnP RAServer:1 Device ISO/IEC 29341-18-3:2011
UPnP RADiscoveryAgent:1 Device ISO/IEC 29341-18-4:2011
UPnP SolarProtectionBlind:1 Device ISO/IEC 29341-19-1:2011
UPnP TwoWayMotionMotor:1 Service ISO/IEC 29341-19-10:2011
UPnP AV Architecture:2 ISO/IEC 29341-20-1
UPnP AVTransport:3 Service ISO/IEC 29341-20-10
UPnP ConnectionManager:3 Service ISO/IEC 29341-20-11
UPnP ContentDirectory:4 Device ISO/IEC 29341-20-12
UPnP RenderingControl:3 Service ISO/IEC 29341-20-13
UPnP ScheduledRecording:2 Service ISO/IEC 29341-20-14
UPnP MediaRenderer:3 Service ISO/IEC 29341-20-2
UPnP MediaServer:4 Device ISO/IEC 29341-20-3
UPnP AV Datastructure Template:1 ISO/IEC 29341-20-4
UPnP InternetGatewayDevice:2 Device ISO/IEC 29341-24-1
UPnP WANIPConnection:2 Service ISO/IEC 29341-24-10
UPnP WANIPv6FirewallControl:1 Service ISO/IEC 29341-24-11
UPnP WANConnectionDevice:2 Service ISO/IEC 29341-24-2
UPnP WANDevice:2 Device ISO/IEC 29341-24-3
UPnP Telephony Architecture:2 ISO/IEC 29341-26-1
UPnP CallManagement:2 Service ISO/IEC 29341-26-10
UPnP MediaManagement:2 Service ISO/IEC 29341-26-11
UPnP Messaging:2 Service ISO/IEC 29341-26-12
UPnP PhoneManagement:2 Service ISO/IEC 29341-26-13
UPnP AddressBook:1 Service ISO/IEC 29341-26-14
UPnP Calendar:1 Service ISO/IEC 29341-26-15
UPnP Presense:1 Service ISO/IEC 29341-26-16
UPnP TelephonyClient:2 Device ISO/IEC 29341-26-2
UPnP TelephonyServer:2 Device ISO/IEC 29341-26-3
UPnP Friendly Info Update:1 Service ISO/IEC 29341-27-1
UPnP MultiScreen MultiScreen Architecture:1
ISO/IEC 29341-28-1
UPnP MultiScreen Application Management:1 Service
ISO/IEC 29341-28-10
UPnP MultiScreen Screen:1 Device
ISO/IEC 29341-28-2
UPnP MultiScreen Application Management:2 Service
ISO/IEC 29341-29-10
UPnP MultiScreen Screen:2 Device
ISO/IEC 29341-29-2
UPnP IoT Management and Control Architecture Overview:1
ISO/IEC 29341-30-1
 ISO/IEC 2017 – All rights reserved ix

---------------------- Page: 9 ----------------------
ISO/IEC 29341-28-1:2017(E)


UPnP DataStore:1 Service
ISO/IEC 29341-30-10
UPnP IoT Management and Control Data Model:1 Service
ISO/IEC 29341-30-11
UPnP IoT Management and Control Transport Generic:1
Service ISO/IEC 29341-30-12
UPnP IoT Management and Control:1 Device
ISO/IEC 29341-30-2
UPnP Energy Management:1 Service ISO/IEC 29341-31-1

x   ISO/IEC 2017 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 29341-28-1:2017(E)

1 Scope
Today multi-screen/second-screen solutions are proliferating. However, each is a proprietary
vertical for particular vendor(s). Therefore users expectations aren’t being met:
 Seamless interoperability across vendors.
 Ability for second screen integrated usages rather than 100s of different apps.
The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open interface to enable
this interoperability between devices and applications, i.e. enable time-sensitive and
interactive services, including implementation-specific applications, among various display
devices.
This document describes the overall Multi-Screen Architecture, which forms the foundation for
the UPnP Multi-Screen Device and Service templates. The Multi-Screen Architecture defines
the general interaction between UPnP control points and UPnP devices defined by the UPnP
Multi-Screen DCPs.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
[1] – UPnP Device Architecture, version 1.0, UPnP Forum, October 15, 2008.
Available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf.
Latest version available at: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-
v1.0.pdf.
[2] – ApplicationManagement:1, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/specs/ms/UPnP-ms-ApplicationManagement-v1-Service-
20140930.pdf.
Latest version available at: http://www.upnp.org/specs/ms/UPnP-ms-ApplicationManagement-
v1-Service.pdf.
[3] – ApplicationManagement:2, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/specs/ms/UPnP-ms-ApplicationManagement-v2- Service-
20140930.pdf.
Latest version available at: http://www.upnp.org/specs/ms/UPnP-ms-ApplicationManagement-
v2-Service.pdf.
[4] – ScreenDevice:1, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/specs/ms/UPnP-ms-ScreenDevice-v1-Device-20140930.pdf.
Latest version available at: http://www.upnp.org/specs/ms/UPnP-ms-ScreenDevice-v1-
Device.pdf.
[5] – ScreenDevice:2, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/specs/ms/UPnP-ms-ScreenDevice-v2-Device-20140930.pdf.
Latest version available at: http://www.upnp.org/specs/ms/UPnP-ms-ScreenDevice-v2-
Device.pdf.
[6] – XML Schema Part 1: Structures, Second Edition, Henry S. Thompson, David Beech,
Murray Maloney, Noah Mendelsohn, W3C Recommendation, 28 October 2004.
Available at: http://www.w3.org/TR/2004/REC-xmlschema-1-20041028.
[7] – XML Schema Part 2: Data Types, Second Edition, Paul V. Biron, Ashok Malhotra, W3C
Recommendation, 28 October 2004.
Available at: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028.
[8] – The “xml:” Namespace, November 3, 2004.
 ISO/IEC 2017 – All rights reserved  1

---------------------- Page: 11 ----------------------
ISO/IEC 29341-28-1:2017(E)


Available at: http://www.w3.org/XML/1998/namespace.
[9] – Namespaces in XML, Tim Bray, Dave Hollander, Andrew Layman, eds., W3C
Recommendation, January 14, 1999.
Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114.
[10] – XML Schema for FeatureList XML Structures, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/ schemas/ms/FeatureList-v1-20140930.xsd.
Latest version available at: http://www.upnp.org/ schemas/ms/FeatureList.xsd.
[11] – XML Schema for AppInfoList XML Structures, UPnP Forum, September 30, 2014.
Available at: http://www.upnp.org/ schemas/ms/AppInfoList-v2-20140930.xsd.
Latest version available at: http://www.upnp.org/ schemas/ms/AppInfoList.xsd.
3 Terms, definitions, symbols and abbreviations
For the purposes of this document, the terms and definitions given in [1] and the following
apply.
3.1 Provisioning terms (abbreviated forms are used only in tables)
3.1.1
allowed
A
The definition or behavior is allowed.
3.1.2
conditionally allowed
CA
The definition or behavior depends on a condition. If the specified condition is met, then the
definition or behavior is allowed, otherwise it is not allowed.
3.1.3
conditionally required
CR
The definition or behavior depends on a condition. If the specified condition is met, then the
definition or behavior is required. Otherwise the definition or behavior is allowed as default
unless specifically defined as not allowed.
3.1.4
required
R
The definition or behavior is required.
3.1.5
R/A
Used in a table column heading to indicate that each abbreviated entry in the column declares
the provisioning status of the item named in the entry's row.
3.1.6
X
Vendor-defined, non-standard.
3.1.7
-D
Declares that the item referred to is deprecated, when it is appended to any of the other
abbreviated provisioning terms.
3.1.8
Screen Device
A UPnP component used to provide various interactive services with other display device(s)
which is (are) implemented with Screen Control Point(s). Designed to be controlled by and
interact with Screen Control Point(s). See subclause 5.1 for details.
2   ISO/IEC 2017 – All rights reserved

---------------------- Page: 12 ----------------------
ISO/IEC 29341-28-1:2017(E)
3.1.9
Screen Control Point
A UPnP component used to provide various interactive services with other display device(s)
which is (are) implemented with Screen Device(s). Designed to control and interact with
Screen Device(s) with direct input from end-users. See subclause 5.2 for details.
3.1.10
Multi-Screen Service
Time-sensitive and interactive services, including implementation-specific applications, among
various display devices. The display devices can be categorized into the main screen device
and companion screen device by the roles and usages of the specific applications.
3.1.11
Main screen device :
Usually the main screen device is assumed as a lean-back display device such as a TV or set-
top box which is controlled by companion screen devices. But any display device such as a
smart phone, tablet, etc. can be a main screen device depending on usage scenarios.
3.1.12
Companion screen device
Usually the companion screen device is assumed as a lean-forward & handheld display device
such as a smart phone or tablet which controls main screen devices. But any display device
such as a TV or set-top box, etc. can be a main screen device depending on usage scenarios.
3.1.13
CSV list (or CSV)
comma separated value list
list—or one-dimensional array—of values contained in a string and separated by commas
3.2 Symbols
3.2.1
::
signifies a hierarchical parent-child (parent::child) relationship between the two objects
separated by the double colon. This delimiter is used in multiple contexts, for example:
Service::Action(), Action()::Argument, parentXMLElement::childXMLElement.
4 Notations and Conventions
4.1 Notation
 UPnP interface names defined in the UPnP Device Architecture specification [1] are
styled in green bold underlined text.
 UPnP interface names defined outside of the UPnP Device Architecture specification
[1] are styled in red italic underlined text.
 Some additional non-interface names and terms are styled in italic text.
 Words that are emphasized are also styled in italic text. The difference between italic
terms and italics for emphasis will be apparent by context.
 Strings that are to be taken literally are enclosed in “double quotes”.
4.1.1 Data Types
Data type definitions come from three sources:
 All state variable and action argument data types are defined in the UPnP Device
Architecture specification [1].
 Basic data types for properties are defined in the XML Schema Part 2: Data Types [7].
 Additional data types are defined in the XML schema(s) (see [10], [11]) for their
associated service(s).
 ISO/IEC 2017 – All rights reserved 3

---------------------- Page: 13 ----------------------
ISO/IEC 29341-28-1:2017(E)


For UPnP Device Architecture defined boolean data types, it is strongly recommended to use
the value “0” for false, and the value “1” for true. However, when used as input arguments, the
values “false”, “no”, “true”, “yes” may also be encountered and shall be accepted.
Nevertheless, it is strongly recommended that all boolean state variables and output
arguments be represented as “0” and “1”.
For XML Schema defined Boolean data types, it is strongly recommended to use the value “0”
for false, and the value “1” for true. However, when used as input properties, the values
“false”, “true” may also be encountered and shall be accepted. Nevertheless, it is strongly
recommended that all Boolean properties be represented as “0” and “1”.
4.1.2 Strings Embedded in Other Strings
Some string variables and arguments described in this document contain substrings that shall
be independently identifiable and extractable for other processing. This requires the definition
of appropriate substring delimiters and an escaping mechanism so that these delimiters can
also appear as ordinary characters in the string and/or its independent substrings. This
document uses embedded strings in two contexts – Comma Separated Value (CSV) lists (see
subclause 4.2.1) and property values in search criteria strings. Escaping conventions use the
backslash character, “\” (character code U+005C), as follows:
a) Backslash (“\”) is represented as “\\” in both contexts.
b) Comma (“,”) is
1) represented as “\,” in individual substring entries in CSV lists
2) not escaped in search strings
c) Double quote (“"”) is
1) not escaped in CSV lists
2) not escaped in search strings when it appears as the start or end delimiter of a
property value
3) represented as “\"” in search strings when it appears as a character that is part of the
property value
4.2 Derived Data Types
This subclause defines a derived data type that is represented as a string data type with
special syntax. This specification uses string data type definitions that originate from two
different sources. The UPnP Device Architecture [1] defined string data type is used to define
state variable and action argument string data types. The XML Schema namespace is used to
define property xsd:string data types. The following definition applies to both string data types.
4.2.1 CSV Lists
The UPnP Multi-Screen DCPs use state variables, action arguments and properties that
represent lists – or one-dimensional arrays – of values. The UPnP Device Architecture,
Version 1.0 [1], does not provide for either an array type or a list type, so a list type is defined
here. Lists may either be homogeneous (all values are the same type) or heterogeneous (all
values can be of different types). Lists may also consist of repeated occurrences of
homogeneous or heterogeneous sub
...