ETSI TS 103 544-6-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 6 Service Binary Protocol (SBP) (V1 3 0).pdf

《ETSI TS 103 544-6-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 6 Service Binary Protocol (SBP) (V1 3 0).pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 544-6-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 6 Service Binary Protocol (SBP) (V1 3 0).pdf（31页珍藏版）》请在麦多课文档分享上搜索。

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

2、 Transport Systems (ITS). CCC is owner of the copyright of the document CCC-TS-018 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 other

3、wise 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-6 V1.3.0 (2017-10)2 Reference DT

4、S/ITS-88-6 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 no

5、tice 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 authori

6、zation 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 should be

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

8、g 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 vers

9、ion 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. Mi

10、rrorLink 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, UMTS

11、TMand 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 trademarks

12、registered and owned by the GSM Association. ETSI ETSI TS 103 544-6 V1.3.0 (2017-10)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Abbreviations . 6g34 MirrorLinkData Service

13、 Architecture . 7g34.1 Overall Architecture . 7g34.2 Version convention. 8g34.3 Starting Data Service 8g34.4 Data Service Security with Device Attestation Protocol 8g35 Service Framework: Service BINARY Protocol (SBP) . 8g35.1 Introduction 8g35.2 Service Description Example . 9g35.3 Data representat

14、ion . 10g35.4 Command representation 12g35.5 Command Sequences . 14g35.5.1 General 14g35.5.2 Get, Response-Continue, Response 15g35.5.3 Set, Response-Continue, Response 15g35.5.4 Subscribe, Response-OK/NOK, Response . 16g35.5.5 Cancel, Response 16g35.5.6 AuthenticationChallenge, AuthenticationRespon

15、se 17g35.5.7 AliveRequest, AliveResponse. 17g35.6 Hash as UID . 18g35.7 Error handling 18g35.7.1 General 18g35.7.2 Irrecoverable error 18g35.7.2.1 Introduction . 18g35.7.2.2 Unknown data type . 18g35.7.2.3 Wrong END: END check failure for form 4, 5 or command 19g35.7.3 Recoverable error 19g35.7.3.1

16、Introduction . 19g35.7.3.2 Unknown Object UID . 19g35.7.3.3 Unknown command type 19g35.7.3.4 Unsupported feature 19g35.7.4 Error to ignore . 19g35.7.4.1 General 19g35.7.4.2 Unknown UID for member variable . 19g35.7.5 Error code definition . 19g35.8 Authentication mechanism . 20g35.9 Support of optio

17、nal Objects 21g35.10 Version listing and selection 21g35.11 Initialization Sequence . 21g35.12 Other topics 22g35.12.1 Extending a service . 22g35.12.2 Payload fragmentation 22g35.12.3 Inheritance 22g35.12.4 Shutdown clean-up and reconnection . 22g3Annex A (informative): BINARY Representation (data_

18、With_UID) Example 23g3ETSI ETSI TS 103 544-6 V1.3.0 (2017-10)4 Annex B (informative): Data Service Grammar (EBNF) . 26g3B.1 Introduction 26g3B.2 Basic Definitions 26g3B.3 Numbers, Words, Names, and Text 27g3B.4 Properties Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI

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

20、ot 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

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

22、 trademarks. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). The present document is part 6 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

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

24、ept when used in direct citation. ETSI ETSI TS 103 544-6 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 written having a vehicle hea

25、d-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 Service Binary Protocol (SBP) is a simple, low-bandwidth data service framework, enabling a CDB data service provider an

26、d subscriber to utilize common functions like reading, writing or subscribing to objects of a data service. 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

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

28、erlinks 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-13 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Tra

29、nsport Systems (ITS); MirrorLink; Part 13: Core Architecture“ . 2 ETSI TS 103 544-5 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 5: Common Data Bus (CDB)“. 3 ETSI TS 103 544-9 (V1.3.0): “Publicly Available Specification (PAS); Intelligent T

30、ransport Systems (ITS); MirrorLink; Part 9: UPnP Application Server Service“. 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-specif

31、ic 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 appl

32、ication 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“. 3 Abbreviations For the purposes of the present document

33、, the following abbreviations apply: CDB Common Data Bus HU Automobile Head-Unit (this term may be used interchangeably with the term “MirrorLink Client“) IP Internet Protocol ETSI ETSI TS 103 544-6 V1.3.0 (2017-10)7 SBP Service Binary Protocol TCP Transmission Control Protocol UDP User Datagram Pro

34、tocol UI User Interface UPnP Universal Plug-and-Play 4 MirrorLinkData Service Architecture 4.1 Overall Architecture MirrorLink Data service is composed of CDB, service framework and service provider / subscriber. CDB is the underlying multiplexing layer which also provides service discovery feature.

35、 On top of it, service framework layer allows implementing a new service in easier way by providing common abstraction for service provider / subscriber. Figure 1 Top level architecture of MirrorLink data service Figure 1 shows the top level architecture of MirrorLink data service. Underlying connec

36、tivity can be a TCP/IP session on top of physical connectivity like USB, WLAN, and Bluetooth. Besides TCP/IP, it will be also possible to run MirrorLink data service on top of other protocol like Bluetooth RFCOMM, but how to discover and establish connection for such configuration is outside the sco

37、pe of the present document. On top of the connectivity layer, the CDB layer is located. CDB relies on the connectivity layer to provide TCP like connection oriented session, and all other layers above rely on the CDB to provide communication interface. Above the CDB can be the service framework laye

38、r or data source (service provider) / data sink (service subscriber) layer depending on the data service used. Service framework layer implements common features for individual data services to allow creating a new service easier. Some data service may decide not to use the service framework to re-u

39、se existing protocols or to reduce the additional overhead caused by the framework. It is highly recommended for any new data service to consider using the service framework first. If that approach does not work, accessing directly to CDB layer can be considered. Some data service may open its own T

40、CP/IP session, but such use case is outside the scope of the present document. On top of data service framework can be service provider (data source) or service subscriber (data sink). Each data source can support up to one data sink: Zero data sink means the service is not used. As there can be onl

41、y one data sink for each data source, it is up to each side of MirrorLink connection (MirrorLink Server and MirrorLink Client) to make sure that the service can be shared across multiple applications if necessary. Depending on the implementation, there can be one system component which can work as a

42、 data sink and can provide received data to all interested applications. Another implementation may allow only one application to get the data. How such access control is implemented is outside the scope of the present document, but it is recommended to allow multiple applications to access the data

43、 unless that data is meaningful only for selected applications. MirrorLink Server MirrorLink Client Connectivity CDB Service Framework Data Sink Data Source Data Sink Data Source Connectivity CDB Service Framework Data Source Data Sink Data Source Data Sink ETSI ETSI TS 103 544-6 V1.3.0 (2017-10)8 4

44、.2 Version convention CDB and service framework layers are bound under the same version number provided from CDB. In other words, the service framework layer does not have separate version number. CDB version number will be updated when there is an update in CDB or service framework layer. This pres

45、ent document, goes together with the CDB version 1.1 specification, defined in 2. All version numbers in MirrorLink data service are composed of major version number and minor version number. A change in the major version number means incompatibility with the previous major version. A change in the

46、minor version guarantees compatibility with the previous minor version. This policy should be maintained across all the layers of MirrorLink data service. 4.3 Starting Data Service MirrorLink data service requires CDB as underlying layer. And to use data service, CDB should be launched by via UPnP a

47、pplication launch mechanism 3. Note that there is no separate application for data service, and launching CDB is enough. More details on discovering CDB services can be found from clause 2.2 of CDB specification 2. Note that MirrorLink Client needs to launch the CDB with right version number. Once C

48、DB is started, all available services can be discovered by using CDB ServicesRequest and ServicesSupported messages. Then service client, either from MirrorLink Client or Server side, can ask service server to start the service via CDB StartService message. For details, check the CDB specification.

49、4.4 Data Service Security with Device Attestation Protocol CDB can support payload encryption by using a pre-arranged session key. In the current MirrorLink architecture, the session key can be acquired after attestation of CDB in MirrorLink Server side by utilizing Device Attestation Protocol 1. The application public key generated from the attestation of CDB is the session key used for encrypting CDB payload in MirrorLink Client side. MirrorLink Server will use matching private key to decrypt CDB payload. Note that this key can b