ETSI TS 103 544-5-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 5 Common Data Bus (CDB) (V1 3 0).pdf

1、 ETSI TS 103 544-5 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 5: Common Data Bus (CDB) CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Technical Committee Intelligent Transpo

2、rt Systems (ITS). CCC is owner of the copyright of the document CCC-TS-016 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 inc

3、luding 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-5 V1.3.0 (2017-10)2 Reference DTS/ITS-88

4、5 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 Important notice The

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

6、f 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 should be aware t

7、hat 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 servic

8、es: 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 shal

9、l 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. MirrorLink

10、 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, UMTSTMand th

11、e 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 trademarks register

12、ed and owned by the GSM Association. ETSI ETSI TS 103 544-5 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 5g33 Abbreviations . 5g34 Common Data Bus Architecture 6

13、g34.1 General Architecture 6g34.2 Bindings . 6g34.2.1 TCP Binding . 6g34.2.1.1 Launching the Common Data Bus 6g34.2.1.2 Intentionally Terminating the Common Data Bus 6g34.2.1.3 Unintentionally Terminating the CDB Session . 7g34.2.2 Other Bindings 7g34.3 Testing Considerations . 7g35 Message Types an

14、d Format 8g35.1 Message Overview . 8g35.2 ServicesRequest . 8g35.3 ServicesSupported 9g35.4 StartService 11g35.5 StopService. 11g35.6 ServicePayload . 12g35.7 ServiceResponse . 12g35.8 ByeBye . 13g35.9 Ping 14g35.10 PingResponse . 14g36 Message Flow . 14g3Annex A (informative): Authors and Contribut

15、ors 16g3History 17g3ETSI ETSI TS 103 544-5 V1.3.0 (2017-10)4 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 membe

16、rs 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.

17、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

18、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

19、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 Sys

20、tems (ITS). The present document is part 5 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 inte

21、rpreted 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 ETSI TS 103 544-5 V1.3.0 (2017-10)5 1 Scope The present document is part of the MirrorLi

22、nkspecification 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 displa

23、y, audio input/output and user input mechanisms. The Common Data Bus (CDB) is a simple, low-bandwidth shared bus, which allows exchanging data between two CDB endpoints, residing in the MirrorLink Server and Client. The Common Data Bus is fully symmetrical, i.e. services can be provided on both endp

24、oints independently from each other. 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 vers

25、ion 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,

26、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-9 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 9: UPnP Application Server Servic

27、e“. 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 an

28、y 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

29、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 Abbreviations For the purposes of the present document, the following abbreviations apply: BT Bluetooth CDB Common Data Bus IP I

30、nternet ProtocolMMU Memory Management Unit OOB Out-of-Band TCP Transmission Control Protocol UDP User Datagram Protocol UI User Interface ETSI ETSI TS 103 544-5 V1.3.0 (2017-10)6 UPnP Universal Plug-and-Play 4 Common Data Bus Architecture 4.1 General Architecture The Common Data Bus (CDB) is a simpl

31、e, low-bandwidth shared bus, which allows exchanging data between two CDB endpoints, residing in the MirrorLink Server and Client. The Common Data Bus is fully symmetrical, i.e. services can be provided on both endpoints independently from each other. A CDB endpoint can host a CDB Sink endpoint and

32、a CDB Source endpoint. CDB Sink endpoints are subscribing to data services provided from CDB Source endpoints. A CDB source endpoint can provide multiple data services from data sources. A CDB sink endpoint can deliver data from multiple data sources to multiple data sinks. The endpoints are respons

33、ible for marshalling and de-marshalling of all the data from multiple applications passing through the common data bus. A CDB data sink subscribes to a service, provided from a data source service. For simplicity, the following figure shows two CDB services, which one data source and data sink each.

34、 Figure 1: Common Data Bus Architecture with TCP binding 4.2 Bindings 4.2.1 TCP Binding 4.2.1.1 Launching the Common Data Bus The MirrorLink Server, providing Common Data Bus functionality, shall include the Common Data Bus into its application listing as specified in 1. The MirrorLink Client shall

35、identify the Common Data Bus from the application listing as specified in 1. The Common Data Bus shall be started from the MirrorLink Client, using the UPnP TmApplicationServer:1 service LaunchApplication action 1. The MirrorLink Clients CDB endpoint shall open a TCP connection to the Servers CDB en

36、dpoint, using the returned URL from the LaunchApplication action. The MirrorLink Client should launch the MirrorLink Servers CDB endpoint not later than 10s after receiving the first A_ARG_TYPE_AppList response from the MirrorLink Server. The MirrorLink Client shall have launched the MirrorLink Serv

37、ers CDB prior starting the first VNC based remote application. 4.2.1.2 Intentionally Terminating the Common Data Bus The MirrorLink Client and Server can terminate the Servers Common Data Bus endpoint anytime, using the CDB ByeBye message and the UPnP TmApplicationServer:1 services, as defined in 1.

38、 ETSI ETSI TS 103 544-5 V1.3.0 (2017-10)7 The CDB endpoint in the MirrorLink Client shall use the following sequence to terminate the CDB operation: 1) Client CDB endpoint shall send a CDB ByeBye message. The CDB Client shall not send any further CDB messages, after sending the CDB ByeBye message. T

39、he CDB Client endpoint should ignore all incoming CDB messages, after sending a CDB ByeBye message. 2) Server CDB endpoint shall respond with a CDB ByeBye message. 3) Client CDB endpoint shall disconnect the TCP connection. The CDB Client should disconnect the TCP connection, if it does not receive

40、the CDB ByeBye message back within 5 s. 4) CDB Server should disconnect the TCP connection on detection of the Client TCP disconnect or 5s after sending the CDB ByeBye message, whatever comes first. Client CDB endpoint should send a UPnP TmApplicationServer:1 service TerminateApplication action for

41、the server CDB endpoint. The CDB endpoint in the MirrorLink Server shall use the following sequence to terminate the CDB operation: 1) Server CDB endpoint shall send a CDB ByeBye message. The Server CDB endpoint shall not send any further CDB messages after sending the CDB ByeBye message. The CDB en

42、dpoint should ignore all incoming CDB messages, after sending a CDB ByeBye message. 2) Client CDB endpoint shall disconnect the TCP connection. 3) Server CDB endpoint shall signal the CDB endpoints termination to the Client, if it has subscribed to the TmApplicationServer:1 AppStatusUpdate event. 4)

43、 Server CDB endpoint should disconnect the TCP connection on detection of the Client TCP disconnect or 5s after sending the CDB ByeBye message, whatever comes first. If the CDB is terminated prior to the establishment of the TCP connection, steps 1, 2 and 4 shall be omitted. 4.2.1.3 Unintentionally

44、Terminating the CDB Session Unintentional termination of the CDB session may happen any time in case of error conditions. In this case the respective CDB Server or Client endpoint will disconnect the TCP connection. The respective counterpart should disconnect as well. If the MirrorLink Client decid

45、es to re-establish the CDB session, it shall follow the steps given in clause 4.2.1.1. To avoid the CDB Server or Client endpoint 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_REUSEADDR option (or similar

46、platform specific variants), allowing the operating system to reuse a port address, even it is currently in the TIME-WAIT state or the CDB Server endpoint should use a different, unaffected port. 4.2.2 Other Bindings Besides TCP/IP, it will be also possible to run MirrorLink Common Data Bus on top o

47、f other protocol 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 MirrorLink Client is in a dedicated testing state (as part of the MirrorLink Certification), it shall launch a n

48、ew CDB session (either initiated automatically or manually from the user), whenever the CDB Server endpoint has intentionally terminated the CDB session. If the MirrorLink Client is in a dedicated testing state (as part of the MirrorLink Certification), it shall launch a new CDB session (either init

49、iated automatically or manually from the user), whenever the CDB Server endpoint has unintentionally terminated the CDB session. ETSI ETSI TS 103 544-5 V1.3.0 (2017-10)8 5 Message Types and Format 5.1 Message Overview The Common Data Bus (CDB) defines the following messages, which are specified in more detail in the following paragraphs. ServicesRequest: Requests the list of supported services ServicesSupported: Provide a list of supported data services StartService: Request to start a specific service StopService: Request to stop a specif