ISO/IEC 29341-28-10:2017
(Main)Information technology — UPnP Device Architecture — Part 28-10: Multiscreen device control protocol — Application management service
Information technology — UPnP Device Architecture — Part 28-10: Multiscreen device control protocol — Application management service
ISO/IEC 29341-28-10:2017 specifies the characteristics of the UPnP networked service named ApplicationManagement, version 1. This service definition is compliant with UPnP Device Architecture 1.0 [1]. This service type enables to manage applications and the communications between applications providing various time-sensitive and interactive services including implementation-specific applications among various display devices, that is, Screen Devices [3] and Screen Control Points. Screen Devices shall implement this service [3], but this service is allowed to be implemented for any UPnP devices as an add-on service.
Technologies de l'information — Architecture de dispositif UPnP — Partie 28-10: Protocole de contrôle de dispositif multi-écran — Service de gestion des applications
General Information
Standards Content (Sample)
INTERNATIONAL
ISO/IEC
STANDARD
29341-28-10
First edition
2017-09
Information technology — UPnP
Device Architecture —
Part 28-10:
Multiscreen device control protocol —
Application management service
Technologies de l'information — Architecture de dispositif UPnP —
Partie 28-10: Protocole de contrôle de dispositif multi-écran —
Service de gestion des applications
Reference number
©
ISO/IEC 2017
© 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. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved
CONTENTS
Foreword . v
1  Scope . 1
2  Normative references . 1
3  Terms, definitions, symbols and abbreviations . 2
3.1.1  SECURITY feature . 2
3.1.2  AM Roles . 2
3.1.3  Application . 2
3.1.4  Native Application . 2
3.1.5  Web Application . 2
4  Notations and Conventions . 2
5  Service Modelling Definitions . 2
5.1  Service Type . 2
5.2  Key Concepts . 2
5.2.1  SECURITY feature . 2
5.3  State Variables . 4
5.3.1  A_ARG_TYPE_AppIDs . 4
5.3.2  AppInfoList . 5
5.3.3  A_ARG_TYPE_AppInfo . 7
5.3.4  SupportedTargetFields . 8
5.3.5  A_ARG_TYPE_Target . 8
5.3.6  A_ARG_TYPE_TargetFields . 8
5.3.7  RunningAppList . 8
5.3.8  A_ARG_TYPE_URI . 8
5.3.9  A_ARG_TYPE_Parameters . 8
5.4  Eventing and Moderation . 9
5.5  Actions . 9
5.5.1  GetAppInfoByIDs() . 10
5.5.2  GetSupportedTargetFields() . 10
5.5.3  GetAppIDList() . 11
5.5.4  GetRunningAppList() . 12
5.5.5  GetRunningStatus(). 12
5.5.6  StartAppByID() . 13
5.5.7  StartAppbyURI() . 14
5.5.8  StopApp() . 15
5.5.9  GetAppConnectionInfo() . 16
5.5.10  Non-Standard Actions Implemented by a UPnP Vendor . 17
5.5.11  Common Error Codes . 17
6  XML Service Description . 17
7  Test . 21
Table 1 — Error Codes for Action Level Access . 3
Table 2 — ApplicationManagement Roles . 3
Table 3 — Action to Role Permission Mapping . 4
 ISO/IEC 2017 – All rights reserved iii
Table 4 —State variables . 4
Table 5 — Allowed values for function element . 6
Table 6 — Allowed values for connectionAddress element . 6
Table 7 — Required fields for SupportedTargetFields . 8
Table 8 — Event moderation . 9
Table 9 — Actions . 9
Table 10 — Arguments for GetAppInfoByIDs() . 10
Table 11 — Error Codes for GetAppInfoByIDs() . 10
Table 12 — Arguments for GetSupportedTargetFields() . 11
Table 13 — Error Codes for GetSupportedTargetFields() . 11
Table 14 — Arguments for GetAppIDList() . 11
Table 15 — Error Codes for GetAppIDList() . 11
Table 16 — Arguments for GetRunningAppList() . 12
Table 17 — Error Codes for GetRunningAppList() . 12
Table 18 — Arguments for GetRunningStatus() . 12
Table 19 — Error Codes for GetRunningStatus() . 13
Table 20 — Arguments for StartAppByID() . 13
Table 21 — Error Codes for StartAppByID() . 13
Table 22 — Arguments for StartAppByURI() . 14
Table 23 — Error Codes for StartAppByURI() . 15
Table 24 — Arguments for StopApp() . 15
Table 25 — Error Codes for StopApp() . 16
Table 26 — Arguments for GetAppConnectionInfo() . 16
Table 27 — Error Codes for GetAppConnectionInfo() . 16
Table 28 — Common Error Codes . 17
iv   ISO/IEC 2017 – All rights reserved
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‐10	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.
 ISO/IEC 2017 – All rights reserved v
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
vi   ISO/IEC 2017 – All rights reserved
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
 ...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.