1、 ETSI TS 103 544-29 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 29: Schedule 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 Trans
2、port Systems (ITS). CCC is owner of the copyright of the document CCC-TS-091 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 i
3、ncluding 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-29 V1.3.0 (2017-10)2 Reference DTS/ITS
4、-88-29 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
5、 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 authorizati
6、on 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 awa
7、re 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 following se
8、rvices: 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
9、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. Mirror
10、Link 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, UMTSTMan
11、d 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 regi
12、stered and owned by the GSM Association. ETSI ETSI TS 103 544-29 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 6
13、g34.1 Schedule Data Service Version 1.0 6g35 SBP Binding . 8g36 Theory Of Operations . 8g36.1 Getting Schedule Information 8g3Annex A (informative): Authors and Contributors . 10g3History 11g3ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)4 Intellectual Property Rights Essential patents IPRs essential or p
14、otentially 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 Essent
15、ial, 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, including IPR searches, has been carried out by ETSI. No guarantee ca
16、n 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 trademarks and/or tradenames which are asserted and/or registered
17、 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 document does not constitute an endorsement by ETSI of products, s
18、ervices 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 29 of a multi-part deliverable. Full details of the entire series can be found in part
19、 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 interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “mus
20、t not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 544-29 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
21、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 mechanisms. The present document specifies schedule data service based on SBP (Service B
22、inary Protocol) framework. The service is used to provide schedule data in car environments. 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 versi
23、on 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 hyperlinks include
24、d 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-27 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems
25、(ITS); MirrorLink; Part 27: Basic Meta Data Service“. 2 ISO 8601:2004: “Data elements and interchange formats - Information interchange - Representation of dates and times“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version
26、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 cannot guara
27、ntee 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 particular subject area. i.1 ETSI TS 103 544-1 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (I
28、TS); MirrorLink; Part 1: Connectivity“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: EMail Electronic Mail SBP Service Binary Protocol ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)6 4 Data Service Definition 4.1 Schedule Data Service Version 1.0 /* This spe
29、cification defines data objects for the Schedule data * service to be carried over by SBP. By receiving this data, the * schedule data sink can provide schedule information to the * driver through instrument cluster display panel. The Schedule * Source may be implemented in a Mirrorlink Client or a
30、Mirrorlink * Server. * version 1.0 */ SERVICE com.mirrorlink.schedule : com.mirrorlink.meta.basic version 1.0 /* High-level schedule object */ STRUCTURE Schedule /* The type of event: 0x0000 Event; 0x0001 Task; * 0x0002 Anniversary * optional, uid 0x554fb7af */ SHORT eventType; /* The name of the ev
31、ent * mandatory, uid 0x32525e60 */ STRING eventName; /* Date expressed according to ISO 8601 2. * mandatory, uid 0x144a7773 */ STRING date; /* Server Local Time Zone as difference from UTC which takes both * “+“ and “-“ values. * mandatory, uid 0x2d64662d */ SHORT ltz; /* Event time in UTC (from whe
32、n to when) structure * mandatory, uid 0xafe05520 */ STRUCTURE timeInfo; /* Location information * optional, uid 0x7d1eda7a */ STRING location; /* Event Description * optional, uid 0xebdc4037 */ STRING description; /* Contacts structure * optional, uid 0x3881ad06 */ STRUCTURE_ARRAY contactsInfo; ; ET
33、SI ETSI TS 103 544-29 V1.3.0 (2017-10)7 /* STRUCTURE holding event time details. Schedules are notified * 15 mins prior to from by default. * version 1.0, optional */ STRUCTURE Time /* From time in UTC * mandatory, uid 0x79b21f4f */ TIME from; /* To time in UTC * mandatory, uid 0x5a2fff80 */ TIME to
34、; ; /* STRUCTURE holding contact details * version 1.0 * optional * UID: TBD */ STRUCTURE Contacts /* First name * mandatory, uid 0x0c921876 */ STRING firstName; /* Last name * optional, uid 0x48217786 */ STRING lastName; /* Phone Number * optional, uid 0x57fb2cd2 */ STRING phoneNumber; /* EMail * o
35、ptional, uid 0xdead6817 */ STRING email; ; /* The ScheduleConfig object is set from data sink, to configure the * behavior of data source * mandatory, writable, uid 0x7772b4fe */ OBJECT ScheduleConfig /* Maximum number of items to be returned ranging from 14. * Default value is 1. * optional, uid 0x
36、577142c9 */ INT maxNoOfItems; /* UTC start time of event * optional, uid 0x92b68a6a */ TIME startTime; /* UTC end time of event * optional, uid 0xa9a217e3 */ TIME endTime; ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)8 ; /* The ScheduleList object contains a list of schedules currently * stored. * mandat
37、ory, readable, uid 0x2a28f5ba */ OBJECT ScheduleList /* List of Schedule Items ranging from 04. * mandatory, uid 0x844c24cd */ STRUCTURE_ARRAY scheduleItemList; ; ; 5 SBP Binding A SBP Sink endpoint shall be able to access the schedule object using SBP Subscribe and Get commands. A SBP Source endpoi
38、nt shall support the ON_CHANGE SBP subscription type. The schedule object stores the next upcoming schedule and is updated 15 minutes before the actual schedule time. If the SBP Source endpoint is not able to retrieve schedule information temporarily, the SBP Source endpoint shall have the following
39、 behavior within the SBP protocol: The SBP Source endpoint shall return an SBP response message with a “Not available“ SBP error code in response to a SBP Get command to the schedule object. The SBP Source shall provide a valid schedule object, as soon as the schedule information becomes available a
40、gain. The SBP Source endpoint shall send an SBP response message with a “Not available“ SBP error code in response to a SBP Subscribe command to the schedule object. The SBP Sink endpoint should then send a new Subscribe command again not earlier than 5s and not later than 30 s to receive notificati
41、ons. The Schedule Meta Data Service uses the following objects and their access capabilities, as defined in 1: name / uid accessType subscriptionType minIntervalTime MaxIntervalTime Schedule READABLE ON_CHANGE NA NA ScheduleConfig WRITABLE NONE NA NA ScheduleList READABLE NONE NA NA 6 Theory Of Oper
42、ations 6.1 Getting Schedule Information The following sequence diagram shows how a schedule data sink retrieves metadata about the current schedules from the schedule data source. ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)9 Figure 1: Message Sequence Diagram Retrieve Schedule metadata It consists of t
43、he following steps, after the data service has been setup as defined in 1: 1) User wants to know schedules currently stored. Schedule Sink sends SBP: SET message to the ScheduleConfig object to set filtering conditions on retrieved data. The Schedule Source responds with an SBP: Response message con
44、firming the setting. 2) Schedule Sink sends SBP: GET message to the ScheduleList object. The Schedule Source responds with the SBP: Response message, containing all the stored schedule objects (limiting to 4 schedules only). 3) After sometime, one of the schedules is about of become active, then Sch
45、edule Source sends an SBP: Response message for the Schedule, containing the Schedule object. ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)10 Annex A (informative): Authors and Contributors The following people have contributed to the present document: Rapporteur: Dr. Jrg Brakensiek, E-Qualus (for Car Connectivity Consortium LLC) Other contributors: Kiran Vedula, Samsung Electronics Lee Poong-Seok, Samsung Electronics ETSI ETSI TS 103 544-29 V1.3.0 (2017-10)11 History Document history V1.3.0 October 2017 Publication
