1、 ETSI TS 103 544-4 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 4: Device Attestation Protocol (DAP) CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Technical Committee Intelli
2、gent Transport Systems (ITS). CCC is owner of the copyright of the document CCC-TS-014 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 o
3、therwise 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. TECHNICAL SPECIFICATION ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)2 Referenc
4、e DTS/ITS-88-4 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Importan
5、t 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 aut
6、horization 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 drive within ETSI Secretariat. Users of the present document shoul
7、d 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 foll
8、owing 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
9、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 logo is a Trade Mark of ETSI registered for the benefit of its Members
10、. 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 may be trademarks of their respective owners. DECTTM, PLUGTESTSTM,
11、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 protected for the benefit of its Members. GSM and the GSM logo are tradema
12、rks registered and owned by the GSM Association. ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1
13、Definitions 6g33.2 Abbreviations . 6g34 Managing a DAP Session . 7g34.1 Bindings . 7g34.1.1 TCP Binding . 7g34.1.1.1 Identifying DAP Server . 7g34.1.1.2 Device Attestation Launch 7g34.1.2 Intentionally Terminating the DAP Session . 7g34.1.3 Unintentionally Terminating the DAP Session . 8g34.2 Other
14、Bindings . 8g34.3 Testing Considerations . 8g35 Device Attestation Protocol 9g3Annex A (normative): XSD Schema . 17g3Annex B (informative): Authors and Contributors . 19g3History 20g3ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)4 Intellectual Property Rights Essential patents IPRs essential or potentially
15、 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
16、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
17、 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
18、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
19、 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 4 of a multi-part deliverable. Full details of the entire series can be found in part 1 i.1. Mod
20、al 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
21、NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)5 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 docu
22、ment 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 term “device attestation“ in this context refers to the MirrorLink client verifying t
23、hat the MirrorLink server is from a compliant manufacturer and running approved software. The attestation will be based on standard X.509 certificates 2 and attestation mechanisms defined by Trusted Computing Group. 2 References 2.1 Normative references References are either specific (identified by
24、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 publicl
25、y 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
26、the present document. 1 XML Signature Syntax and Processing, http:/www.w3.org/TR/xmldsig-core/, W3C Recommendation 10 June 2008. 2 IETF RFC 5280: “Internet X.509 Public Key Infrastructure Certificate“, May 2008. http:/tools.ietf.org/html/rfc5280. 3 IETF RFC 3279: “Algorithms and Identifiers for the
27、Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile“, April 2002.http:/tools.ietf.org/html/rfc3279. 4 Trusted Platform Module (TPM) specifications, Version 1.2. http:/www.trustedcomputinggroup.org/resources/tpm-main-specification. 5 Trusted Computing Gr
28、oup. Mobile Trusted Module Specification. Version 1.0. April 2010. Available at: http:/www.trustedcomputinggroup.org/. 6 Recommendation ITU-T X.690 (07/2002): “Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished
29、 Encoding Rules (DER)“. 7 ETSI TS 103 544-12 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 12: UPnP Server Device“. 8 ETSI TS 103 544-9 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part
30、9: UPnP Application Server Service“. 9 ETSI TS 103 544-10 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 10: UPnP Client Profile Service“. 10 ETSI TS 103 544-2 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (
31、ITS); MirrorLink; Part 2: Virtual Network Computing (VNC) based Display and Control“. ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)6 11 ETSI TS 103 544-3 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 3: Audio“. 12 Trusted Computing Group, “Credent
32、ials Profiles Specification 1.1“, May 2007. http:/www.trustedcomputinggroup.org/resources/infrastructure-work-group-tcg-credential-profiles-specification 13 ETSI TS 103 544-5 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 5: Common Data Bus (
33、CDB)“. 14 ETSI TS 103 544-17 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 17: MirrorLink over Wi-Fi Display (WFD)“. 15 ETSI TS 103 544-21 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Pa
34、rt 21: High Speed Media Link (HSML)“. 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
35、 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
36、 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“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the fo
37、llowing terms and definitions apply: pointer event: touch screen action in which the user touches the screen with one (virtual) finger only at a single location touch event: touch screen action in which the user touches the screen with two or more separate fingers at different locations NOTE: Touch
38、events are used to describe more complex touch action, like pinch-open or pinch-close. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: A2DP Bluetooth Advanced Audio Distribution Profile ARP Address Resolution Protocol BT Bluetooth CDC Communications Dev
39、ice Class; specified from USB Device Working Group CE Consumer Electronics; CE devices are referred to as mobile devices within the present document DAP Device Attestation Protocol DHCP Dynamic Host Configuration Protocol HFP Bluetooth Hands-free Profile HMI Human Machine Interface HS Head-set ETSI
40、ETSI TS 103 544-4 V1.3.0 (2017-10)7 HSP Bluetooth Headset Profile HU Head-unit (this term is used interchangeably with the MirrorLink client) IP Internet Protocol NCM Network Control Model; part of the CDC device class RFB Remote Framebuffer RTP Real-time Transport Protocol TCP Transmission Control
41、ProtocolUDP User Datagram Protocol UI User Interface UPnP Universal Plug and Play USB Universal Serial Bus VNC Virtual Network Computing 4 Managing a DAP Session 4.1 Bindings 4.1.1 TCP Binding 4.1.1.1 Identifying DAP Server The identification of the DAP server is described in 8. 4.1.1.2 Device Attes
42、tation Launch The DAP server start-up is facilitated via the UPnP TmApplicationServer:1 service LaunchApplication action, as defined in 8. The LaunchApplication action shall return with a URL to the DAP server. If the returned URL is already used from any established DAP session, this session will c
43、ontinue without any change. Otherwise a new DAP session shall be established, given the following steps: a) DAP server shall listen for the DAP client to make TCP connection at the provided URL for at least 10 s. b) DAP client shall make a TCP connection to the provided URL. c) DAP server and client
44、 shall start DAP according to the steps defined in Clause 5. 4.1.2 Intentionally Terminating the DAP Session The DAP server shall not intentionally terminate a DAP session. The DAP client shall intentionally terminate a DAP session, using the following steps: 1) UPnP Control Point uses TmApplication
45、Server:1 services TerminateApplication SOAP action to send termination request. 2) DAP client shall disconnect the TCP connection. 3) DAP server should disconnect the TCP connection on detection of the client TCP disconnect or 5 seconds after responding to the TerminateApplication SOAP action, which
46、ever comes first. The DAP client shall wait for any outstanding Device Attestation Response messages, for at least 10 s, prior to terminating the DAP session. The DAP Server shall provide a DAP response to any DAP request within 10 s. ETSI ETSI TS 103 544-4 V1.3.0 (2017-10)8 4.1.3 Unintentionally Te
47、rminating the DAP Session Unintentional termination of the DAP session may happen at any time due to error conditions. In the case of unintentional termination of the DAP session, the respective DAP server or client shall disconnect the TCP connection. The respective counterpart should disconnect as
48、 well. If the MirrorLink Client decides to re-establish the DAP session, it shall follow the steps given in clause 4.1.1.2. To avoid the DAP server or client being in a TCP TIME-WAIT time-out loop as a result of an unintentional active disconnect, the TCP socket should be established using the SO_RE
49、USEADDR option (or similar platform specific variant), allowing the operating system to reuse a port address, even it is currently in the TIME-WAIT state or the DAP server should use a different, unaffected port number. 4.2 Other Bindings Besides TCP/IP, it will be possible to run MirrorLink Device Attestation Protocol on top of other protocols like Bluetooth RFCOMM, but how to discover and establish connection for such configuration is outside the scope of the present document. 4.3 Testing Considerations If the
