1、 ETSI TS 103 544-1 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 1: Connectivity CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Technical Committee Intelligent Transport System
2、s (ITS). CCC is owner of the copyright of the document CCC-TS-008 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 bu
3、t 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-1 V1.3.0 (2017-10)2 Reference DTS/ITS-88-1 Keywor
4、ds interface, ITS, PAS, smartphone, USB 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 Important notice The pre
5、sent 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 ET
6、SI. 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 should be aware that
7、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:
8、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 no
9、t 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. MirrorLink is
10、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, UMTSTMand the ET
11、SI 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 trademarks registered a
12、nd owned by the GSM Association. ETSI ETSI TS 103 544-1 V1.3.0 (2017-10)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33
13、.2 Abbreviations . 7g34 Physical 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, incl
14、uding 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
15、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 d
16、ocument 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 1 of a multi-part del
17、iverable for the Mirrorlink Specifications: Part 1: “Connectivity“; Part 2: “Virtual Network Computing (VNC) based Display and Control“; Part 3: “Audio“; Part 4: “Device Attestation Protocol (DAP)“; Part 5: “Common Data Bus (CDB)“; Part 6: “Service Binary Protocol (SBP)“; Part 7: “GPS Data Service“;
18、 Part 8: “Location Data Service“; Part 9: “UPnP Application Server Service“; Part 10: “UPnP Client Profile Service“; Part 11: “UPnP Notification Server Service“; Part 12: “UPnP Server Device“; Part 13: “Core Architecture“; Part 14: “Application Certificates“; Part 15: “Application Programming Interf
19、ace (API) Level 1 Part 16: “Application Developer Certificates“; Part 17: “MirrorLink over Wi-Fi Display (WFD)“; Part 18: “IEEE 802.11 Car Connectivity Consortium (CCC) Information Element“; ETSI ETSI TS 103 544-1 V1.3.0 (2017-10)5 Part 19: “Network Information Data Service“; Part 20: “Internet Acce
20、ssibility“; Part 21: “High Speed Media Link (HSML)“; Part 22: “Android-Specific Specifications“; Part 23: “Bluetooth Out-of-Band Pairing Data Service“; Part 24: “Media Meta Data Service“; Part 25: “Navigation Meta Data Service“; Part 26: “Consumer Experience Principles and Basic Features“; Part 27:
21、“Basic Meta Data Service“; Part 28: “Weather Data Service“; Part 29: “Schedule Data Service“. 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 th
22、e 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 ETSI TS 103 544-1 V1.3.0 (2017-10)6 1 Scope The present document is part of the MirrorLinkspecification which specifies an inter
23、face 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 mec
24、hanisms. The connectivity between the MirrorLink Server and Client is the basis to provide interoperability between both. The Connectivity stack is specified in the following, starting from the low layer and going up the protocol stack. It is not the objective of the present document to provide a de
25、tailed overview of the different protocols. Instead the present document highlights the components and parameters required to ensure proper connectivity. The connectivity solution is built purely on existing wireless and wired standards. Therefore, detailed information is available in the respective
26、 documents. 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 doc
27、ument (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 the
28、ir long-term validity. The following referenced documents are necessary for the application of the present document. 1 USB 2.0: “Universal Serial Bus Specification“, Revision 2.0, April 27, 2000. 2 USB-IF: “Universal Serial Bus Communications Class Subclass Specifications for Network Control Model D
29、evices“, Revision 1.0 April 30, 2009. http:/www.usb.org/developers/docs/devclass_docs/. 3 Wi-Fi Alliance Technical Committee, P2P Task Group: “Wi-Fi Peer-to-Peer (P2P) Technical Specification“, Revision 1.1, October 4, 2010. 4 IETF RFC 791: “Internet Protocol - DARPA Internet Program Protocol Specif
30、ication“, September 1981, https:/tools.ietf.org/html/rfc791. 5 IETF RFC 2131: “Dynamic Host Configuration Protocol“, May 1997, https:/tools.ietf.org/html/rfc2131 . 6 IETF RFC 826: “An Ethernet Address Resolution Protocol - or - Converting Network Protocol Addresses to 48.bit Ethernet Address for Tra
31、nsmission on Ethernet Hardware“, November 1982. https:/tools.ietf.org/html/rfc826 . 7 IETF RFC 5227: “IPv4 Address Conflict Detection“, July 2008, https:/tools.ietf.org/html/rfc5227. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or
32、 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 can
33、not guarantee their long-term validity. ETSI ETSI TS 103 544-1 V1.3.0 (2017-10)7 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. Not applicable. 3 Definitions and abbreviations 3.1 Def
34、initions For the purposes of the present document, the following terms and definitions apply: pointer event: used to describe 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 sc
35、reen with two or more separate fingers at different locations NOTE: Touch 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: AP Access Point ARP Address Resolution Proto
36、col CDC Communications Device Class NOTE: Specified from USB Device Working Group. CE Consumer Electronics NOTE: CE devices are referred to as mobile devices within the present document. DHCP Dynamic Host Configuration Protocol HMI Human Machine Interface HU Head-unit NOTE: This term is used interch
37、angeably with the MirrorLink Client. HS Head-Set IP Internet Protocol NCM Network Control Model NOTE: Part of the CDC device class. RFB Remote Framebuffer RTP Real-time Transport Protocol TCP Transmission Control Protocol UDP User Datagram Protocol UI User Interface UPnP Universal Plug and Play USB
38、Universal Serial Bus VNC Virtual Network Computing ETSI ETSI TS 103 544-1 V1.3.0 (2017-10)8 4 Physical or b) the MirrorLink Server manufacturer has set a different default preference. In latter case, the consumer shall be able to change that preference. The USB device shall allow for manual or semi-
39、manual selection of the USB CDC/NCM profile and start of the SSDP:alive advertisements. The MirrorLink specification does not specify, whether USB CDC/NCM is provided as an individual device class or within a USB personality. In latter case, it is up to the USB device implementation, which other USB
40、 device classes may be available under the same personality, where USB CDC/NCM is provided. The USB Host shall support CDC/NCM within a USB personality and as an individual device class. 4.2.3 Managing USB Personalities using the MirrorLink USB Command If a MirrorLink Client wants to use MirrorLink
41、immediately upon physical connection of the USB port, the client should send the MirrorLink USB command before the end of the USB enumeration, to ask the MirrorLink Server to provide a USB personality supporting MirrorLink (i.e. allowing a USB-CDC/NCM). If a MirrorLink Client wants to change to Mirr
42、orLink from other USB personalities later, the MirrorLink Client should send the MirrorLink USB command at a later time. Alternatively, the MirrorLink Client may reset the USB connection. NOTE: Resetting the USB connection does not inform the MirrorLink Server, that the MirrorLink Client supports Mi
43、rrorLink. If the MirrorLink Server is not able to switch to USB CDC/NCM functionality in response to the MirrorLink USB command, e.g. as the user has a different preference, the USB device shall respond with a STALL PID. If the MirrorLink Server responds with a STALL PID (refer to 1, clause 9.2.7),
44、it shall provide a mechanism for the user to switch to MirrorLink. Using the MirrorLink USB command, the MirrorLink Client can detect an operating MirrorLink Server connected to it, if all the following conditions are true: 1) The MirrorLink USB command does not return with STALL PID; 2) The USB dev
45、ice descriptor has USB CDC/NCM; and 3) A MirrorLink device is advertised over UPnP. If the MirrorLink Client wants to switch from MirrorLink to another USB personality or device class, it shall reset the USB connection. It will be up to the MirrorLink Server to select a different USB personality; th
46、erefore, the MirrorLink Server may still provide MirrorLink functionality. If the MirrorLink Server wants to switch from MirrorLink to another USB personality or device class, it shall reset the USB connection and provide a new USB personality or device class. ETSI ETSI TS 103 544-1 V1.3.0 (2017-10)
47、10 4.2.4 Interoperability Issues using the MirrorLink USB Command USB devices, not supporting MirrorLink USB command, will return STALL PID in compliance with USB 2.0 core specification 1. Nevertheless, the MirrorLink Client may recognize that a connected USB device is not working, after sending the
48、 MirrorLink USB command, e.g. the USB host is not able to read the USB device descriptor. This might be the case, if the connected USB device has not been certified from USB-IF. To resolve this issue, the MirrorLink Client should reset the USB connection and should not send the MirrorLink USB comman
49、d again after reset. 4.3 Wireless Local Area Networks (WLAN) 4.3.1 General Support for Wireless LAN is optional. MirrorLink WLAN connectivity shall be implemented using Wi-Fi Alliances Wi-Fi technology. The physical IEEE 802.11x transport layer should be selected to meet the bandwidth needs of the framebuffer transfer as described in Table 1. 4.3.2 Wi-Fi Access Point based Connection Both, MirrorLink Server and MirrorLink Client can be Access Point (AP) and Client. Which entity is taking which role, depends on the configuration of the Mirr
