ETSI TS 103 544-7-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 7 GPS Data Service (V1 3 0).pdf

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

2、stems (ITS). CCC is owner of the copyright of the document CCC-TS-020 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 includin

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

4、ywords 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 pres

5、ent 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 ETS

6、I. 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 t

7、he 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: h

8、ttps:/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 not

9、 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 a

10、 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 ETS

11、I 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 an

12、d owned by the GSM Association. ETSI ETSI TS 103 544-7 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 Data Service Definition 6g34.1 GPS

13、Data Service Version 1.0 6g34.2 GPS Data Service Version 2.0 7g35 SBP Binding . 8g3Annex A (informative): Authors and Contributors . 9 g3History 10g3ETSI ETSI TS 103 544-7 V1.3.0 (2017-10)4 Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document

14、 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 to ETSI in respect of ETS

15、I 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

16、 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. ETSI claims no ownership o

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

18、se trademarks. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 i.1. Modal verbs terminology In the presen

19、t 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 e

20、xcept when used in direct citation. ETSI ETSI TS 103 544-7 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 document is written having a vehicle h

21、ead-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 specifies GPS service based on SBP (Service Binary Protocol) framework. The service is used to provid

22、e better GPS data in car environments. The present document is based on NMEA specification 0183 1 as bearer of GPS. 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 reference

23、s, 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 in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: Whil

24、e 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 document. 1 NMEA 0183 version 3.01 (January 2002): “Standard For Interfacing Marine Elec

25、tronic Devices“. NOTE: Available at http:/www.plaisance- 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 la

26、test 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 application of the presen

27、t 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, the following abbre

28、viations apply: GPS Global Positioning System NMEA National Marine Electronics Association ETSI ETSI TS 103 544-7 V1.3.0 (2017-10)6 4 Data Service Definition 4.1 GPS Data Service Version 1.0 /* The purpose of GPS service is to provide better GPS data in car * environments. The specification relies o

29、n NMEA as bearer of GPS * data. * version 1.0 */ SERVICE com.mirrorlink.GPS /* SUPPORTED_SENTENCES */ ENUM SUPPORTED_SENTENCES /* SUPPORT_GGA */ SUPPORT_GGA = 0x01, /* SUPPORT_GLL */ SUPPORT_GLL = 0x02, /* SUPPORT_GSA */ SUPPORT_GSA = 0x04, /* SUPPORT_GSV */ SUPPORT_GSV = 0x08, /* SUPPORT_RMC */ SUP

30、PORT_RMC = 0x10, /* SUPPORT_VTG */ SUPPORT_VTG = 0x20, /* SUPPORT_GST */ SUPPORT_GST = 0x40 ; /* NMEA object carrying NMEA sentence * This Object delivers NMEA-0183 v3.0 1 compatible NMEA strings * included in the “data“ member variable. Among all NMEA messages, * only following 7 messages are suppo

31、rted. * - GGA: Global Positioning System Fixed Data * - GLL: Geographic Position - Latitude/Longitude * - GSA: GNSS DOP and Active Satellites * - GSV: GNSS Satellites in View * - RMC: Recommended Minimum Specific GNSS Data * - VTG: Course Over Ground and Ground Speed * - GST: GPS Pseudo Range Noise

32、(PRN) statistics * As some NMEA sentences are delivering the same information * redundantly, it is not necessary to support all NMEA sentences. * It is up to the server implementation to decide necessary * combinations. As the Object can be used even for non-GPS-based * positioning method, minimum s

33、et of messages can be, for example, GLL * only. The client for the service can Get NMEA_description object to * check which sentences are supported. * NMEA object shall support the subscription type of regular interval. * The minimum subscription interval of NMEA Object supported by the * service se

34、rver shall be less than or equal to 1 second. In some server * implementation, server may decide to send each NMEA sentence as * separate SBP message rather than combining them into one message. * In that case, subscription interval is not the interval between * each sentence, but it should be the i

35、nterval where the same sentence * is repeated. And depending on the situation, some NMEA sentences may * NOT be available for some time. For example, if location fix-up is * not available yet, server may send only GSV sentence. * Note that getting NMEA object may return just one NMEA sentence * whic

36、h does not necessarily include positioning data. NMEA object * is intended for being used with Subscribe command, and sequences * of NMEA sentences should be monitored to get meaningful information. * mandatory, readable, version 1.0, uid 0x0aac4540 */ Object NMEA /* NMEA sentences * NMEA messages a

37、s byte array. Multiple NMEA sentences can be * combined into single array. * mandatory, uid 0x144a776f */ ETSI ETSI TS 103 544-7 V1.3.0 (2017-10)7 BYTES data; /* UTC time of data * Time stamp of the NMEA data embedded. It is a UTC time associated * with the NMEA sentences contained. * In case UTC ti

38、me associated with the NMEA sentence is unknown, the * GPS Data Source shall set the timestamp value to zero (0). * mandatory, uid 0x59413fd1 */ TIME timeStamp; ; /* Provides configuration information of NMEA object * The NMEA_description should be accessed before NMEA object is * subscribed. Access

39、ing NMEA_description object while NMEA object is * accessed may fail depending on servers resource status. * mandatory, readable, version: 1.0, uid 0x9d08b19d */ Object NMEA_description /* bit wise OR of supported sentences, as defined in the enumeration * ENUM. * The data source implementation shal

40、l support at least one active * command. * mandatory, uid 0x6e72b167 */ INT supportedSentences; ; ; 4.2 GPS Data Service Version 2.0 SERVICE com.mirrorlink.GPS : version 1.0 ENUM definedCoordinateSystem /* WGS-84 coordinate system * mandatory */ CS_WGS84 = 0x00000001; /* GCJ-02 coordinate system * o

41、ptional */ CS_GCJ02 = 0x00000002; /* GCJ-02 coordinate system * optional */ CS_Proprietary = 0x80000000; ; /* This object returns bit flags of supported coordinate systems * from the Location Data source. * mandatory, readable, version 2.0, uid 0x6f1c2428 */ Object availableCoordinateSystems /* Bit

42、wise OR of all supported coordinate systems by the data * source. Possible coordinate systems are defined in the * definedCoordinateSystem enumeration. * This object should be accessed before accessing any of the other * objects. A location data source shall support WGS-84, unless the * device is op

43、erating in China. * mandatory, uid 0x0885cf07 */ int coordinateSystems; ; /* This object contains the currently used coordinate system from the * Location Data source. The object can be set from data sink to * change the coordinate system. * It should be accessed before subscribing to the NMEA * obj

44、ect. The objects default value should be cs_WGS-84, unless the * device is operating in China, where it may be cs_GCJ02. * If the object is set to a coordinate system, unknown or not * supported, the location data source shall indicate the location * as not being available. * The coordinate system s

45、hall not be changed, after subscription * to the NMEA object. The location data sink may change the * coordinate system if it has not subscribed to the NMEA * object. * The data source shall honor the selected coordinate system. * mandatory, configurable, version 2.0, uid 0x17ab51db */ Object curren

46、tCoordinateSystem ETSI ETSI TS 103 544-7 V1.3.0 (2017-10)8 /* Provide coordinate system, the source is currently using * mandatory, uid 0xd2394c6c */ ENUM coordinateSystem; ; ; 5 SBP Binding The GPS Data Services uses the following objects and their access capabilities: Object Name Access Type Subsc

47、ription Type NMEA READABLE ON_CHANGE, REGULAR, or AUTO NMEA_description READABLE NONE availableCoordinateSystems READABLE NONE currentCoordinateSystem CONFIGURABLE NONEIf the GPS receiver is not available, the SBP source endpoint shall return “Not available“ error code. This applies to the case when

48、 the GeoLocation Object is subscribed. Then SBP sink endpoint should send Subscribe command again not earlier than 5s and not later than 30s to get notification again. If the GPS receiver has only lost satellite reception, it should encode this into to NMEA sentences and should not return a “Not ava

49、ilable“ error code. The MirrorLink Client should not provide map-matched coordinates. If available, the MirrorLink Client should use a dead-reckoned position. The version 2.0 of the GPS service adds a set of new objects, which are not available in version 1.0 version of the service. The SBP protocol is able to handle this. The following items, describe the possible behavior: A version 2.0 sink may try to subscribe or access a version 2.