ETSI TS 103 544-9 V1.3.1 (2019-10)

ETSI TS 103 544-9 V1.3.1 (2019-10)






TECHNICAL SPECIFICATION
Publicly Available Specification (PAS);
Intelligent Transport Systems (ITS);
®
MirrorLink ;
Part 9: UPnP Application Server Service
CAUTION
The present document has been submitted to ETSI as a PAS produced by CCC and
approved by the ETSI Technical Committee Intelligent Transport Systems (ITS).
CCC is owner of the copyright of the document CCC-TS-024 and/or had all relevant rights and had assigned said rights to ETSI
on an "as is basis". Consequently, to the fullest extent permitted by law, ETSI disclaims all warranties whether express, implied,
statutory or otherwise including but not limited to merchantability, non-infringement of any intellectual property rights of third
parties. No warranty is given about the accuracy and the completeness of the content of the present document.

---------------------- Page: 1 ----------------------
2 ETSI TS 103 544-9 V1.3.1 (2019-10)



Reference
RTS/ITS-98-9
Keywords
interface, ITS, PAS, smartphone

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm
except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
©ETSI 2019.
© Car Connectivity Consortium 2011-2019.
All rights reserved.
ETSI logo is a Trade Mark of ETSI registered for the benefit of its Members.
MirrorLink® is a registered trademark of Car Connectivity Consortium LLC.
RFB® and VNC® are registered trademarks of RealVNC Ltd.
UPnP® is a registered trademark of Open Connectivity Foundation, Inc.
Other names or abbreviations used in the present document may be trademarks of their respective owners.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 544-9 V1.3.1 (2019-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Service Modeling Definitions . 7
4.1 Service Type . 7
4.2 State Variables . 7
4.2.1 State Variable Overview . 7
4.2.2 AppStatusUpdate . 8
4.2.3 AppListUpdate . 8
4.2.4 A_ARG_TYPE_AppStatus . 9
4.2.5 A_ARG_TYPE_AppID . 9
4.2.6 A_ARG_TYPE_ProfileID . 9
4.2.7 A_ARG_TYPE_AppList . 9
4.2.8 A_ARG_TYPE_URI . 14
4.2.9 A_ARG_TYPE_String . 15
4.2.10 A_ARG_TYPE_Bool . 15
4.2.11 A_ARG_TYPE_INT . 15
4.2.12 A_ARG_TYPE_AppCertificateInfo . 15
4.3 Eventing and Moderation . 18
4.4 Supporting Multiple Client Profiles . 18
4.5 Actions . 18
4.5.1 General . 18
4.5.2 GetApplicationList. 19
4.5.2.1 General . 19
4.5.2.2 Arguments . 19
4.5.2.3 Effect on State . 19
4.5.2.4 Errors . 20
4.5.3 LaunchApplication. 20
4.5.3.1 General . 20
4.5.3.2 Arguments . 20
4.5.3.3 Effect on State . 21
4.5.3.4 Errors . 21
4.5.4 TerminateApplication . 22
4.5.4.1 General . 22
4.5.4.2 Arguments . 22
4.5.4.3 Effect on State . 23
4.5.4.4 Errors . 23
4.5.5 GetApplicationStatus . 23
4.5.5.1 General . 23
4.5.5.2 Arguments . 23
4.5.5.3 Effect on State . 23
4.5.5.4 Errors . 24
4.5.6 GetApplicationCertificateInfo . 24
4.5.6.1 General . 24
4.5.6.2 Arguments . 24
4.5.6.3 Effect on State . 24
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 544-9 V1.3.1 (2019-10)
4.5.6.4 Errors . 25
4.5.7 GetCertifiedApplicationsList . 25
4.5.7.1 General . 25
4.5.7.2 Arguments . 25
4.5.7.3 Effect on State . 25
4.5.7.4 Errors . 26
4.5.8 GetAppCertificationStatus . 26
4.5.8.1 General . 26
4.5.8.2 Arguments . 26
4.5.8.3 Effect on State . 27
4.5.8.4 Errors . 27
4.5.9 SetAllowedApplicationsList . 27
4.5.9.1 General . 27
4.5.9.2 Arguments . 27
4.5.9.3 Effect on State . 28
4.5.9.4 Errors . 28
4.5.10 Relationships Between Actions . 28
4.5.11 Error Code Summary . 29
5 Theory of Operation . 30
5.1 Use of Quotation Marks . 30
5.2 Identification of Applications from A_ARG_TYPE_AppList . 30
5.2.1 Identifying the VNC Server . 30
5.2.2 Identifying Remote VNC based Applications. 31
5.2.3 Identifying Audio Links . 31
5.2.4 Identifying Common Data Bus . 32
5.2.5 Identifying Device Attestation Protocol Server . 32
5.3 Example Values of AppListingFilter . 32
5.4 Example Values of AppCertFilter . 34
5.5 Example Values of State Variables . 35
5.5.1 AppStatusUpdate . 35
5.5.2 AppListUpdate . 35
5.5.3 A_ARG_TYPE_AppStatus . 35
5.5.4 A_ARG_TYPE_AppList . 36
5.5.5 A_ARG_TYPE_AppCertificateInfo . 38
5.6 XML Signature Minimum Set . 39
5.7 Handling of Applications Available via Home Screen Application . 39
5.8 Handling of Application Status Change . 40
5.9 Handling of different Protocol IDs . 40
6 XSD Schema . 41
6.1 A_ARG_TYPE_AppStatus XSD Schema . 41
6.2 A_ARG_TYPE_AppList XSD Schema . 42
6.3 A_ARG_TYPE_AppCertificateInfo XSD Schema . 44
7 XML Service Description . 45
Annex A (normative): Application Context Information . 49
A.1 Trust Level . 49
A.2 Application Categories . 49
A.3 Content Categories . 51
Annex B (informative): Authors and Contributors . 53
History . 54


ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 544-9 V1.3.1 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS).
The present document is part 9 of a multi-part deliverable. Full details of the entire series can be found in part 1 [i.1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 544-9 V1.3.1 (2019-10)
1 Scope
®
The present document is part of the MirrorLink specification which specifies an interface for enabling remote user
interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact
with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio
input/output and user input mechanisms.
The TmApplicationServer service is a UPnP service that allows UPnP Control Points to remotely launch and terminate
applications on MirrorLink Server devices. Through this service, UPnP control points can provide more fine-grained
control and access to specific remote applications.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
TM TM
[1] UPnP Forum: "UPnP Device Architecture 1.1", 15 October 2008.
NOTE: Available at http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf.
[2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax", January 2005.
NOTE: Available at http://tools.ietf.org/html/rfc3986.
[3] W3C Recommendation 11 April 2013: "XML Signature Syntax and Processing Version 1.1".
NOTE: Available at http://www.w3.org/TR/xmldsig-core/.
[4] ETSI TS 103 544-26 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink® ; Part 26: Consumer Experience Principles and Basic Features".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TS 103 544-1 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 1: Connectivity".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 544-9 V1.3.1 (2019-10)
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
3.3 Abbreviations
Void.
4 Service Modeling Definitions
4.1 Service Type
The following service type identifies a service that is compliant with the present document:
• urn:schemas-upnp-org:service:TmApplicationServer:1.
TmApplicationServer service is used herein to refer to this service type. The TmApplicationServer service shall follow
defined UPnP behaviour within the UPnP Device Architecture 1.1 [1].
4.2 State Variables
4.2.1 State Variable Overview
Table 4-1: Service State Variables
Req. or Allowed Default Eng.
Variable Name Data Type
Opt. Value Value Units
AppStatusUpdate R string Undefined Empty string N/A
AppListUpdate R string Undefined Empty string N/A
A_ARG_TYPE_AppStatus R string Undefined Empty string N/A
A_ARG_TYPE_AppID R string Undefined Empty string N/A
A_ARG_TYPE_ProfileID R ui4 Undefined 0 N/A
A_ARG_TYPE_URI R string Undefined Empty string N/A
A_ARG_TYPE_AppList R string Undefined Empty string N/A
A_ARG_TYPE_String R string Undefined Empty string N/A
A_ARG_TYPE_Bool R string true | false false N/A
A_ARG_TYPE_INT R ui4 Undefined 0 N/A
A_ARG_TYPE_AppCertificateInfo R string Undefined Empty string N/A
R = REQUIRED.
O = OPTIONAL.
X = Non-standard.

ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 544-9 V1.3.1 (2019-10)
4.2.2 AppStatusUpdate
A string formatted as UTF-8 represents the list of application identifiers (appIDs) of applications whose status has
changed. The string consists of a comma-separated list of appIDs identifying applications whose status has changed.
Each entry in the list is of the type A_ARG_TYPE_AppID.
This state variable is evented, implying that clients can subscribe to receive notifications every time the variable
changes using UPnP standardized eventing mechanisms. It is important to note that this variable only contains the
appIDs of those applications, whose status has changed since the last time an event notification was sent out.
On receiving an AppStatusUpdate event, the MirrorLink UPnP Control Point can query the application status of specific
applications in the list by invoking the GetApplicationStatus action.
AppStatusUpdate value will consist of a comma separated list of all application identifiers (appIDs) of applications
listed in A_ARG_TYPE_AppList when the event is issued by the TmApplicationServer service for the first time.
After an application launch, the MirrorLink Server shall only send the AppStatusUpdate event, once the application is
running and in foreground. The AppStatusUpdate shall be send only after the response to the UPnP LaunchApplication
or TerminateApplication action has been sent for UI applications.
The MirrorLink Server will provide information of the current foreground framebuffer also via the VNC/WFD context
information. During an application launch or termination action, this information can be temporarily out of sync with
the UPnP application status, e.g. the UPnP information might be trailing the VNC context info in case of an application
launch. In case the framebuffer transfers have been paused, e.g. due to the MirrorLink application being in the
background on the MirrorLink Client screen, the VNC context information will not be updated until the framebuffer
transfer is resumed.
4.2.3 AppListUpdate
A string formatted as UTF-8 represents a list of application identifiers (appIDs) of applications whose entries have
changed in the application listing. The string consists of a comma-separated list of appIDs identifying applications
whose status has changed. Each entry in the list is of the type A_ARG_TYPE_AppID.
It is evented, implying that clients can subscribe to receive notifications every time the variable changes using UPnP
standardized eventing mechanisms. It is important to note that this variable only contains the appIDs of those
applications, whose entries in the application list have changed since the last time an event notification was sent out.
On receiving an AppListUpdate event, a MirrorLink UPnP Control Point can retrieve the application list by invoking
the GetApplicationList action and specifying the appropriate filter using the appListingFilter input argument.
AppListUpdate value will consist of a comma separated list of all application identifiers (appIDs) of applications listed
in A_ARG_TYPE_AppList when the event is issued by the TmApplicationServer service for the first time.
The MirrorLink Client shall follow the AppListUpdate event. This will ensure that a revocation of an application
certificate
...