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.

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
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
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
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
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
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
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, specifically for drive-certified applications, will take immediate effect. Additionally, newly installed
applications or applications for which an application certificate has been successfully downloaded from the ACMS, are
immediately available, without reconnecting the MirrorLink session.
Implementation Note:
Older MirrorLink 1.1 Clients may either ignore AppListUpdate events or do not subscribe to them. Consumers
will need to reestablish a MirrorLink session, in order to see a MirrorLink application available on the
MirrorLink Client, if it has been installed from within a MirrorLink session.
The MirrorLink Server shall send an AppListUpdate event only in case a change to an application entry or to the
certification status happened. The MirrorLink Server should combine changes to multiple applications into a single
event.
Implementation Note:
Older MirrorLink 1.1 Servers may send an AppListUpdate, even in case nothing has changed in the application
list. It is recommended, that MirrorLink Clients check the application listing as they cannot distinguish the
MirrorLink Server's behavior.
ETSI
9 ETSI TS 103 544-9 V1.3.1 (2019-10)
4.2.4 A_ARG_TYPE_AppStatus
A string formatted as UTF-8 XML represents the status of a specific application or alternatively providing the status of
all applications, which can be controlled remotely. Its structure is given in Table 4-2.
Table 4-2: Structure of A_ARG_TYPE_AppStatus
Element Description Parent Availability
appStatusList Indicates list of application status updates - Required
appStatus* Indicates status record corresponding to an application appStatusList Required
Unique ID of the application
appID appStatus Required
(A_ARG_TYPE_AppID)
Entry corresponding to an instance of the application
status* appStatus Required
running under a specific client profile
Profile Identifier of the client profile
profileID status Required
(A_ARG_TYPE_ProfileID)
String representing status of application: {Foreground |
statusType Background | Notrunning} status Required
(A_ARG_TYPE_String)
The elements marked with a (*) can have multiple instances.
4.2.5 A_ARG_TYPE_AppID
A UTF-8 encoded string represents an unsigned 32-bit integer in hexadecimal format (with '0x' prefix) which denotes
the unique application identifier.
The MirrorLink Server shall use the unsigned integer value of a variable of this type within any action. I.e. comparing
the values of two A_ARG_TYPE_AppID variables shall be done based on the unsigned integer value and not based on
a specific character representation.
Therefore, the following two A_ARG_TYPE_AppID values are identical:
• 0x45ab and 0x45AB (case insensitivity of the hexadecimal numbers).
• 0x45ab and 0X45ab (case insensitivity of the 0x).
• 0x00001234 and 0x001234 (leading zeros do not matter).
NOTE: The application identifier should be the same over time for the same application (e.g. should survive a
reboot or MirrorLink reconnect), to allow the MirrorLink Client to implement a Last-Mode behavior.
An A_ARG_TYPE_AppID value may be identical to the wildcard “*”, but it shall not be used, unless its usage is
specifically stated in the definition of the respective UPnP actions and/or events.
4.2.6 A_ARG_TYPE_ProfileID
An unsigned 32-bit integer greater than or equal to 0, represents a unique profile identifier. Its value is set equal to 0 by
default.
4.2.7 A_ARG_TYPE_AppList
A string formatted as UTF-8 XML represents the list of all applications that are available for remote control and access
through the TmApplicationServer service. Its structure is given in Table 4-3. Server devices shall be able to support
values of A_ARG_TYPE_AppList up to 10 KiloBytes in length.
ETSI
10 ETSI TS 103 544-9 V1.3.1 (2019-10)
Table 4-3: Structure of A_ARG_TYPE_AppList
Element Description Parent Availability
appList List of all available remote applications - Required
app* Entry describing one remote application appList Optional
Unique application ID. Shall be non-zero
appID app Required
(A_ARG_TYPE_AppID)
Application name
name app Required
(A_ARG_TYPE_String)
Unique application ID (appID) of the parent application,
variant presented in the UPnP application listing app Optional
(A_ARG_TYPE_String)
provider Name of the application provider
app Optional
Name
(A_ARG_TYPE_String)
URL of the application provider's website
provider URL app Optional
(A_ARG_TYPE_URI)
Text description of application
description app Optional
(A_ARG_TYPE_String)
List of available application icons.
First icon shall be either mimetype=image/png,
width=128, height=128 and depth=24 (default), or
identical to values set in the client icon preferences as
iconList app Optional
specified using the TmClientProfileServer:1 service's
SetClientProfile action
The MirrorLink Client shall support displaying icons with
mimetype=image/png, width=128, height=128 and
depth=24
Describes an application icon.
The MirrorLink Server shall include an icon for all
applications with the following values:
icon* iconList Optional
• VNC
• WFD (MirrorLink ≥ 1.2)
Type of icon image
mimetype icon Required
(A_ARG_TYPE_String)
Width of icon
width icon Required
(A_ARG_TYPE_INT)
Height of icon
height icon Required
(A_ARG_TYPE_INT)
Color depth of icon
depth icon Required
(A_ARG_TYPE_INT)
URL where icon is available.
If the icon of an application changes, the MirrorLink
Server should change the icon's url.
url icon Required
MirrorLink Client shall use HTTP-GET to access the icon
behind the URL.
(A_ARG_TYPE_URI)
allowed Reserved for future use
app Deprecated
ProfileIDs
Deprecated
Information about the remoting protocol used to interact
remoting Info app Required
with the application after it is launched
Protocol Identifier of the remoting protocol that will be
used to access the application (see Table 4-4 for list of
protocolID remoting Info Required
supported protocols)
(A_ARG_TYPE_String)
Format of data being transferred using the remoting
format protocol (see Table 4-5 for details) remoting Info Optional
(A_ARG_TYPE_String)
ETSI
11 ETSI TS 103 544-9 V1.3.1 (2019-10)
Element Description Parent Availability
Direction of the content stream.
A_ARG_TYPE_String with one of the following values:
• “out” - Content streaming from the MirrorLink
server device to the client
direction remoting Info Optional
• “in” - Content streaming from the MirrorLink client
to the server
• “bi” - Content streaming in both directions between
the MirrorLink server and client
Default: “out”
Audio Initial Playback Latency
audioIPL (A_ARG_TYPE_INT) remoting Info Optional
Default: “4800”
Audio Maximum Playback Length
audioMPL (A_ARG_TYPE_INT) remoting Info Optional
Default: “9600”
URL where application certificate is available. The
MirrorLink Client uses the certificate for information
purpose. The MirrorLink Client shall not validate the
app
certificate's trust chain
Certificate app Optional
URL MirrorLink Client shall use HTTP-GET to access the
certificate behind the URL
(A_ARG_TYPE_URI)
appInfo Information about the listed application app Optional
Application category
(A UTF-8 encoded string representing an unsigned
app
32-bit integer in hexadecimal format (with '0x' prefix).)
appInfo Optional
Category
Values are defined in Annex A
Default: “0x00000000”
Trust level of the contents of the appInfo element
(A UTF-8 encoded string representing an unsigned
16-bit integer in hexadecimal format (with '0x' prefix).)
trustLevel appInfo Optional
Values are defined in Annex A
Default: “0x0000”
Information about display content of the listed
displayInfo application, in case it provides a displayable user app Optional
interface
Visual content categories used
(A UTF-8 encoded string representing an unsigned
content
32-bit integer in hexadecimal format (with '0x' prefix).)
display Info Optional
Category
Values are defined in Annex A.
Default: “0x00000000”
content Visual content rules followed
display Info Deprecated
Rules
Deprecated
Display orientations supported.
orientation display Info Deprecated
Deprecated
Trust level of the displayInfo element.
trustLevel display Info Optional
Value shall match appInfo/trustLevel.
Default: “0x0000”
Information about audio content of the listed application,
(++)
audioInfo app Optional
in case it provides an audio interface
ETSI
12 ETSI TS 103 544-9 V1.3.1 (2019-10)
Element Description Parent Availability
Audio type A_ARG_TYPE_String with one of the
following values:
• “phone” - Phone call audio
audioType audioInfo Required
• “application” - Generic application audio
• “all” - Phone and application audio
• “none” - no audio
Audio content categories used
content
(A UTF-8 encoded string representing an unsigned
audioInfo Required
Category
32-bit integer in hexadecimal format (with '0x' prefix).)
Values are defined in Annex A.
Audio content rules followed
content
audioInfo Deprecated
Deprecated
Rules
Trust level of the audioInfo element
(A UTF-8 encoded string representing an unsigned
16-bit integer in hexadecimal format (with '0x' prefix).)
trustLevel audioInfo Optional
Values are defined in Annex A.
Default: “0x0000”
Application resource status
In case the remote application is using a resource, which
is subject to access control (e.g. an audio source or
sink), this element will define the current status having
one of the following values (A_ARG_TYPE_String):
“free” - Resource is free. Can be used by the
MirrorLink client
resource
app Optional
Status “busy” - Resource already used. Resource
assignment can be overridden by a client's
invocation LaunchApplication action
“NA” - Resource already used. Resource
assignment cannot be overridden by a
LaunchApplication action invoked by a client
Default: “free”
XML signature over entire contents of the appList
element. This is done as specified in [3].
The key used in calculating the signature shall be the
private part of the application-specific key which public
part was bound to the attestation of UPnP-Server
component. (The public part can be used to verify the
Signature appList Required
signature.) The Reference element of the XML signature
shall point to appList element.
The SignatureMethod shall be RSA with SHA1. The
KeyInfo element may be omitted. The mechanism for
generation, exchange and maintainance of keys is out of
scope for the present document

The elements marked with a (*) can have multiple instances.
(++)
The audioInfo element shall be included into the advertisement on any RTP Client, RTP Server, BT HFP or BT
A2DP module.
For deprecated values, the MirrorLink Server shall not include them into the UPnP application listing. The MirrorLink
Client shall ignore any content provided in deprecated elements.
Implementation Note:
MirrorLink 1.0 and 1.1 Servers may not include the Signature entry from A_ARG_TYPE_AppList. MirrorLink
1.0 and 1.1 Clients may ignore an existing Signature entry.
ETSI
13 ETSI TS 103 544-9 V1.3.1 (2019-10)
In case the advertised (child) application (e.g. "Musik") is part of a parent application (e.g. "RockScout"), the variant
element shall define the unique appID of that parent application. The parent application shall be separately present in
the UPnP application listing.
The parent's application identifier provided in the variant element, may then be announced instead of the originally
launched child's appID within in the framebuffer context information, or through the UPnP application status. This
means that a MirrorLink Client may see the parent application getting into the foreground on the MirrorLink Server,
even when one of its child applications had been initially launched. The launched (child) application is linked to the
announced (parent) foreground application via the variant field in the client's application list entry. A parent application
shall not be the child of another application, i.e. nesting is not supported.
The protocolID element in A_ARG_TYPE_AppList is a string formatted as UTF-8 XML represents the remote access
protocol of a specific application, which can be controlled remotely. Table 4-4 specifies the supported remote access
protocols, supported from the TmApplicationServer:1 service.
Table 4-4: Supported Remote Access Protocols
protocolID Protocol Name and Description
VNC Virtual Networking Computing
RTP Real Time Protocol
BTA2DP Bluetooth Advanced Audio Distribution Profile
BTHFP Bluetooth Hands Free Profile
DAP Device Attestation Protocol
CDB Common Data Bus
WFD  (MirrorLink 1.2) Wi-Fi Display
Used to indicate that application does not have any additional out-of-band
NONE
connection using a remote access protocol
ProtocolName> appended in front of the protocol name and separated by an '-' (Hyphen)

The format element in A_ARG_TYPE_AppList is a string formatted as UTF-8 XML represents additional format
information for dedicated remote access protocols. Table 4-5 specifies the Remote Access Protocol Format information.
Table 4-5: Remote Access Protocol Format
protocolID Remote Access Protocol Format description
VNC Not used
Comma separated list of supported RTP payload types.
RTP
Default: “99”
BTA2DP Not used
BTHFP Not used
MirrorLink Version number
Allowed Values: “1.0” or “1.1” or “1.2” or “1.3”
DAP
Default: “1.3”
Version number of the CDB protocol
Allowed Values: “1.1”
CDB
Default: “1.1”
WFD (MirrorLink 1.2) Not used
NONE Not used
Vendor Specific
ProtocolName>
The A_ARG_TYPE_AppList contains many optional elements. Elements, which are used for specific remote access
protocols, are given in Table 4-6.
ETSI
14 ETSI TS 103 544-9 V1.3.1 (2019-10)
Table 4-6: Used Elements in A_ARG_TYPE_AppList
Remote Access BTHFP
VNC DAP CDB RTP WFD
Protocol BTA2DP
remotingInfo Used Used Used Used Used Used
appInfo Used Used Used - Used Used
displayInfo Used - - - - Used
audioInfo Used - - Used Used Used
resourceStatus Used - - Used - Used
MirrorLink Version ≥ 1.0 ≥ 1.0 ≥ 1.1 ≥ 1.1 ≥ 1.1 ≥ 1.2

An application with a protocolID of “VNC” may use the resourceStatus value “NA” to indicate that the particular
application is accessible to launch, via a separately advertised Home Screen application.
4.2.8 A_ARG_TYPE_URI
A string encoded as UTF-8 represents a URI according to the following format, given in [2]:
foo://example.com:8042/over/there?name=ferret#nose
\_/
...