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

Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 22: Android Specific Specifications enabling AIDL-based MirrorLink® Applications

RTS/ITS-98-22

General Information

• Status: Published
• Publication Date: 08-Oct-2019
• Technical Committee: ITS - Intelligent Transport Systems
• Current Stage: 12 - Completion
• Due Date: 30-Sep-2019
• Completion Date: 09-Oct-2019

Standards Content (Sample)

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






TECHNICAL SPECIFICATION
Publicly Available Specification (PAS);
Intelligent Transport Systems (ITS);
®
MirrorLink ;
Part 22: Android Specific Specifications enabling
®
AIDL-based MirrorLink Applications
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-056 and CCC-TS-065 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-22 V1.3.1 (2019-10)



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

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

Tel.: [phone]  Fax: [phone]

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-22 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 . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Platform-Specific Specification Concept Overview . 8
5 Application Identifier . 8
5.1 General . 8
5.2 Format . 8
5.3 Calculation . 9
5.3.1 General . 9
5.3.2 Shared UIDs. 10
5.3.3 ROM applications . 11
5.4 APK Validation . 11
6 Application Information . 11
6.1 General . 11
6.2 Self-Signed Application Certificates . 11
6.2.1 General . 11
6.2.2 Application Certificate Self-Signing Process. 12
6.2.3 Self-Signed Application Certificate Installation . 12
6.3 Particulars of Android Application Certificates . 12
6.3.1 General . 12
6.3.2 Platform version . 12
6.3.3 Icon URLs . 12
6.4 Localized strings for the entries in the application certificate . 12
7 Development Certificates . 13
7.1 General . 13
7.2 Device ID . 13
7.3 Application Development Certificates . 13
7.4 Developer ID Entry . 13
7.5 Manual Developer ID Certificate Revocation Checks . 14
8 MirrorLink API Implementation . 14
8.1 General . 14
8.2 API Overview . 14
8.2.1 General . 14
8.2.2 Android MirrorLink Server Requirements . 14
8.2.3 Application Requirements . 16
8.3 MirrorLink API Library Definition . 17
8.3.1 Data Type Definitions . 17
8.3.2 Data Structure Definitions . 17
8.3.3 MirrorLink API Elements accessible from the Service . 18
8.3.4 MirrorLink API Elements accessible from the Content Provider . 19
8.3.4.1 General . 19
8.3.4.2 0xF0xx ' MirrorLink API Information mapping . 19
8.3.4.3 0x02xx ' Certification Information mapping . 19
8.3.4.4 0x03xx ' Connection Information mapping . 20
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 544-22 V1.3.1 (2019-10)
8.3.4.5 0x0Cxx ' Actions mapping . 20
8.3.5 Modules dependencies . 20
8.3.5.1 General . 20
8.3.5.2 General Android MirrorLink Service access . 20
8.3.5.3 General Android Content Provider Service access . 21
8.3.5.4 Actions Module write access. 21
8.3.5.5 DataService Module Source Service Access . 21
8.3.5.6 Launch of Actions . 21
8.3.5.7 MirrorLink Actions . 21
8.3.6 Context Information Lifetime . 22
8.3.7 Return values outside of a MirrorLink session . 22
9 MirrorLink Events . 23
9.1 General . 23
9.2 Touch Events Injections . 23
9.3 Key Events Injections . 23
9.4 Key Event Mapping. 23
9.5 Virtual Keyboard . 24
10 Platform Limitations. 25
10.1 CCC-TS-010-VNC Based Display and Control (ETSI TS 103 544-2) . 25
10.1.1 Server Event Configuration Message . 25
10.1.2 Handling of Overlays . 25
10.1.3 Handling of Applications Seeking Foreground Status . 25
10.1.4 Removal of audio from non-certified applications . 25
Annex A (informative): App ID Generation Code . 26
Annex B (informative): Authors and Contributors . 30
History . 31


ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 544-22 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 22 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-22 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 colour display, audio
input/output and user input mechanisms.
The present document provides the elements of the MirrorLink specification that apply only to Android MirrorLink
Server devices.
The API javadoc files contained in the archive CCC-TS-065_Mirrorlink_API-Level2-AIDL-files__v138.zip, contained
in ts_10354422v010301p0.zip, are an integral part of the present document.
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.
[1] ETSI TS 103 544-14 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 14: Application Certificates".
[2] ETSI TS 103 544-15 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink® ; Part 15: Application Programming Interface (API) Level 1 & 2".
[3] ETSI TS 103 544-16 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 16: Application Developer Certificates".
[4] IETF RFC 4648: "The Base16, Base32, and Base64 Data Encodings", October 2006.
NOTE: Available at http://www.ietf.org/rfc/rfc4648.txt.
[5] ETSI TS 103 544-9 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 9: UPnP Application Server Service".
[6] ETSI TS 103 544-2 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 2: Virtual Network Computing (VNC) based Display and
Control".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 544-22 V1.3.1 (2019-10)
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".
[i.2] Android package documentation.
NOTE: Available at http://developer.android.com/guide/topics/manifest/manifest-element.html#package.
[i.3] Android android:versionCode documentation.
NOTE: Available at http://developer.android.com/guide/topics/manifest/manifest-element.html#vcode.
[i.4] JAR File Specification.
NOTE: Available at http://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html.
[i.5] Signing Your Applications.
NOTE: Available at http://developer.android.com/tools/publishing/app-signing.html.
[i.6] Car Connectivity Consortium: "Android Application ID Generator".
[i.7] Common Intents.
NOTE: Available at https://developer.android.com/guide/components/intents-common.html.
[i.8] Managing audio focus.
NOTE: Available at https://developer.android.com/guide/topics/media-apps/audio-focus.html.
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACMS Application Certification Management System
AIDL Android Interface Definition Language
API Application Programming Interface
APK Android PacKage
CDB Common Data Bus
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 544-22 V1.3.1 (2019-10)
CDMA Code-Division Multiple Access
HTTP HyperText Transfer Protocol
IMEI International Mobile Equipment Identity
IPC Inter-Process Communication
JAR Java ARchive
ML MirrorLink
OCSP Online Certificate Status Protocol
OS Operating System
ROM Read-Only Memory
RSA Rivest–Shamir–Adleman
SBP Service Binary Protocol
SDK Software Development Kit
UID Unique IDentifier
UPnP Universal Plug and Play
URL Uniform Resource Locator
UUID Universally Unique IDentifier
VNC Virtual Network Computing
4 Platform-Specific Specification Concept Overview
In order to support third-party applications within a MirrorLink session, the MirrorLink protocols require certain
information be provided to the MirrorLink Server's software (the MirrorLink "Stack") and to the Application
Certification Management System (ACMS), and that certain functionality be exposed to those applications (the
MirrorLink API). In order to prevent fragmentation of the application ecosystem, simplify implementation for
MirrorLink Server Device developers, and to increase the number of devices that a given application can be run on,
these systems should be common to a given mobile device platform. The goal being that a MirrorLink application
written for Android, for example, should be able to run on all MirrorLink-certified Android devices. It is understood
that differences of versions and hardware capabilities limit the ability to ensure cross-device compatibility however the
intent is that MirrorLink should not create additional barriers to such cross-compatibility.
The present document contains the requirements for MirrorLink Server devices that utilize the Android OS. MirrorLink
Server devices that use the Android Operating System shall comply with the requirements listed in the present
document.
5 Application Identifier
5.1 General
As described in the Application Certificate Handling specification [1], each application shall have a unique application
identifier (App ID) that is provided to the Application Certification Management System (ACMS) via the HTTP GET
and OCSP requests sent to it by the MirrorLink Server device. This AppID needs to be unique for that application, and
change whenever the application is modified. For Android devices, the App ID is generated using the below method.
Source code that implements the below algorithm is provided in Annex A.
5.2 Format
The application ID for an Android application shall be a URL-safe base-64 encoding [4] of a SHA-256 digest. As the
digest of SHA-256 is 32 bytes long the application ID will therefore be a string of 43 URL-safe base-64 characters.
The application ID shall not place any padding characters at the beginning or end of the encoding. This ensures all
implementations will generate an identical application ID and prevents the need to escape any characters when querying
the Application Certificate Management System (ACMS).
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 544-22 V1.3.1 (2019-10)
5.3 Calculation
5.3.1 General
The data to be hashed shall be the concatenation of the following in the order specified:
1) String encoding of Android package name provided in AndroidManifest.xml [i.2].
2) Big endian 8-byte integer representing the version code provided in AndroidManifest.xml [i.3].
3) The string "startManifestMain".
4) For each attribute in the main section of the APK manifest (META-INF/MANIFEST.MF), sorted
lexicographically by unicode code point of the attribute name:
a) String encoding of the full attribute name.
b) String encoding of the attribute value.
5) The string "endManifestMain".
6) For each file named in the main section of the APK manifest (META-INF/MANIFEST.MF), sorted
lexicographically by unicode code point of the file path:
a) The string "startFile".
b) Skip this file if the path is "assets/self-signed.ccc.crt".
c) String encoding of the file path.
d) For each attribute in the file section of the APK manifest, sorted lexicographically by unicode code point
of the attribute name:
i) String encoding of the full attribute name.
ii) String encoding of the attribute value.
e) The string "endFile".
The encoding of strings shall be a big-endian 8-byte integer specifying the length in bytes followed by the UTF-8
encoding of the string.
Example: The string "Hi Σ" would be encoded as the following bytes:
0x00 0x00 0x00 0x05 (Length of UTF-8 string, 5 bytes)
0x48 0x69 0x20 0xCE 0xA3 (UTF-8 encoding of string)
Therefore, an example APK for an application with the following properties:
• Package name of "com.example.a".
• Version code of 124.
• Containing the following files:
- assets/image.png.
- assets/self-signed.ccc.crt.
- META-INF/CERT.RSA.
- META-INF/CERT.SF.
- META-INF/MANIFEST.MF.
- AndroidManifest.xml.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 544-22 V1.3.1 (2019-10)
- classes.dex.
- resources.arsc.
• A META-INF/MANIFEST.MF containing the following:
Manifest-Version: 1.0
Created-By: 1.0 (Android)

Name: classes.dex
SHA1-Digest: eEcd5Q6I3GDCkZ7gAAsC0dB8KxU=

Name: resources.arsc
SHA1-Digest: IEBCJEW4Ws8uS/ML7RgEqwGYvtU=

Name: assets/image.png
SHA1-Digest: gHoXviEAT+JdNMqsvo/vERe231Y=

Name: assets/self-signed.ccc.crt
SHA1-Digest: r/HlpR8FRHOKcsF4o5PFSeV32yk=

Name: AndroidManifest.xml
SHA1-Digest: /czwhhK4YJmcwq9E/qHoB26/K90=

Would have an application ID which is the SHA-256 digest of the concatenation of the following data where the strings
are encoded using the method described above:
"com.example.a"
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x7C
"startManifestMain"
"Created-By"
"1.0 (Android)"
"Manifest-Version"
"1.0"
"endManifestMain"
"startFile"
"AndroidManifest.xml"
"SHA1-Digest"
 "/czwhhK4YJmcwq9E/qHoB26/K90="
"endFile"
"startFile"
"assets/image.png"
"SHA1-Digest"
 "gHoXviEAT+JdNMqsvo/vERe231Y="
"endFile"
"startFile"
"classes.dex"
"SHA1-Digest"
 "eEcd5Q6I3GDCkZ7gAAsC0dB8KxU="
"endFile"
"startFile"
"resources.arsc"
"SHA1-Digest"
 "IEBCJEW4Ws8uS/ML7RgEqwGYvtU="
"endFile"

The quotation marks are not included in the calculation, they are here just to indicate the exact string which is going to
be hashed.
To see a working example for calculating the AppID please check the Android Application ID Generator [i.6], which
contains a sample APK. The README file provided contains the expected application ID.
The Mirror Link Server should reject any APK which contains the same filename twice. An APK with the same
filename multiple times could be used to mask some unwanted data, therefore the Server shall treat it as untrusted.
5.3.2 Shared UIDs
In Android APKs are allowed to share UIDs. Each APK shall be treated as an application as a whole and if two or more
APK use the same shared UID, each of them will be considered an application in its own right. Each of those APKs
shall be certified independently and each of them will have a un
...