ETSI TS 103 544-22-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 22 Android Specific Specifications enabling AIDL-based MirrorLink_1.pdf

1、 ETSI TS 103 544-22 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 22: Android Specific Specifications enabling AIDL-based MirrorLinkApplications floppy3CAUTION The present document has been submitted to ETSI as a PAS produced by CCC an

2、d 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

3、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. TECHNICA

4、L SPECIFICATION ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)2 Reference DTS/ITS-88-22 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 lucr

5、atif enregistre la Sous-Prfecture 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 p

6、resent 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 only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network

7、 drive within ETSI Secretariat. 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 i

8、n 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 a

9、s 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 2017. Car Connectivity Consortium 2011-2017. All rights reserved. ETSI log

10、o 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 UPnP Forum. Other names or abbreviations used in the present document

11、may be trademarks of their respective owners. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protect

12、ed for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2

13、 Informative references 6g33 Abbreviations . 7g34 Platform-Specific Specification Concept Overview 7g35 Application Identifier . 8g35.1 General . 8g35.2 Format 8g35.3 Calculation . 8g35.3.1 General 8g35.3.2 Shared UIDs 10g35.3.3 ROM applications . 10g35.4 APK Validation 10g36 Application Information

14、 . 11g36.1 General . 11g36.2 Self-Signed Application Certificates 11g36.2.1 General 11g36.2.2 Application Certificate Self-Signing Process 11g36.2.3 Self-Signed Application Certificate Installation . 11g36.3 Alternative to Self-Signed Application Certificates . 11g36.4 Particulars of Android Applica

15、tion Certificates . 11g36.4.1 General 11g36.4.2 Platform version 11g36.4.3 Icon URLs. 12g36.5 Localized strings for the entries in the application certificate 12g37 Development Certificates . 12g37.1 General . 12g37.2 Device ID . 12g37.3 Manual Developer ID Certificate Revocation Checks . 13g38 Mirr

16、orLink API Implementation 13g38.1 General . 13g38.2 API Overview . 13g38.2.1 General 13g38.2.2 Android MirrorLink Server Requirements . 14g38.2.3 Application Requirements 15g38.3 MirrorLink API Library Definition 17g38.3.1 Data Type Definitions . 17g38.3.2 Data Structure Definitions 17g38.3.3 Mirror

17、Link API Elements accessible from the Service 17g38.3.4 MirrorLink API Elements accessible from the Content Provider . 18g38.3.4.1 General 18g38.3.4.2 0xF0xx MirrorLink API Information mapping . 18g38.3.4.3 0x02xx Certification Information mapping . 19g38.3.4.4 0x03xx Connection Information mapping

18、. 19g38.3.4.5 0x0Cxx Actions mapping 19g38.3.5 Modules dependencies 20g38.3.5.1 General 20g38.3.5.2 General Android MirrorLink Service access . 20g3ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)4 8.3.5.3 General Android Content Provider Service access . 20g38.3.5.4 Actions Module write access. 20g38.3.5.5

19、 DataService Module Source Service Access . 20g38.3.5.6 Launch of Actions . 20g38.3.5.7 MirrorLink Actions . 21g38.3.6 Context Information Lifetime . 22g38.3.7 Return values outside of a MirrorLink session . 22g39 MirrorLink Events 22g39.1 General . 22g39.2 Touch Events Injections . 22g39.3 Key Even

20、ts Injections . 22g39.4 Key Event Mapping 22g39.5 Virtual Keyboard 24g310 Platform Limitations. 24g310.1 CCC-TS-010-VNC Based Display and Control . 24g310.1.1 Server Event Configuration Message . 24g310.1.2 Handling of Overlays 24g310.1.3 Handling of Applications Seeking Foreground Status 24g310.1.4

21、 Removal of audio from non-certified applications . 25g3Annex A (informative): App ID Generation Code 26g3Annex B (informative): Authors and Contributors . 30g3History 31g3ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)5 Intellectual Property Rights Essential patents IPRs essential or potentially essential

22、 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 t

23、o 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

24、 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. ET

25、SI 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 organizat

26、ions 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

27、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 allow

28、ed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)6 1 Scope The present document is part of the MirrorLinkspecification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is

29、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 An

30、droid MirrorLink Server devices. The API javadoc files contained in the archive Mirrorlink_API-Level2-AIDL-files.zip, contained in ts_10354422v010300p0.zip, are an integral part of the present document. 2 References 2.1 Normative references References are either specific (identified by date of publi

31、cation 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 i

32、n 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 do

33、cument. 1 IETF RFC 3281: “An Internet Attribute Certificate Profile for Authorization“, April 2002. NOTE: Available at http:/www.ietf.org/rfc/rfc3281.txt. 2 ETSI TS 103 544-14 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 14: Application Cer

34、tificates“. 3 ETSI TS 103 544-15 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink ; Part 15: Application Programming Interface (API) Level 1 Intelligent Transport Systems (ITS); MirrorLink; Part 16: Application Developer Certificates“. 5 IETF RFC 464

35、8: “The Base16, Base32, and Base64 Data Encodings“, October 2006. NOTE: Available at http:/www.ietf.org/rfc/rfc4648.txt. 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, onl

36、y 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 referenc

37、ed 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.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 1: Connectivity“. ETSI ETSI TS

38、103 544-22 V1.3.0 (2017-10)7 i.2 Android package documentation. NOTE: Available at http:/ i.3 Android android:versionCode documentation. NOTE: Available at http:/ i.4 JAR File Specification. NOTE: Available at http:/ i.5 Signing Your Applications. NOTE: Available at http:/ i.6 Car Connectivity Conso

39、rtium: “Android Application ID Generator“. i.7 Common Intents. NOTE: Available at https:/ i.8 Managing audio focus. NOTE: Available at https:/ 3 Abbreviations For the purposes of the present document, the following abbreviations apply: ACMS Application Certification Management System AIDL Android In

40、terface Definition Language ML MirrorLink OCSP Online Certificate Status Protocol UPnP Universal Plug and Play 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

41、 to the MirrorLink Servers 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 fo

42、r 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 MirrorLin

43、k-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 requi

44、rements 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. ETSI ETSI TS 103 544-22 V1.3.0 (2017-10)8 5 Application Identifier 5.1 General As described in the App

45、lication Certificate Handling specification 2, 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

46、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 enc

47、oding 5 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

48、 identical application ID and prevents the need to escape any characters when querying the Application Certificate Management System (ACMS). 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.