ETSI TS 103 544-9-2017 Publicly Available Specification (PAS) Intelligent Transport Systems (ITS) MirrorLink Part 9 UPnP Application Server Service (V1 3 0).pdf

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

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

3、erwise 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-9 V1.3.0 (2017-10)2 Reference

4、DTS/ITS-88-9 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

5、notice 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 autho

6、rization 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

7、be 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 follow

8、ing 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 ve

9、rsion 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.

10、MirrorLink 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, UM

11、TSTMand 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 trademark

12、s registered and owned by the GSM Association ETSI ETSI TS 103 544-9 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 Definitions, symbols and abbreviations . 7

13、g34 Service Modeling Definitions 7g34.1 Service Type . 7g34.2 State Variables 7g34.2.1 State Variable Overview . 7g34.2.2 AppStatusUpdate 7g34.2.3 AppListUpdate 8g34.2.4 A_ARG_TYPE_AppStatus 8g34.2.5 A_ARG_TYPE_AppID 9g34.2.6 A_ARG_TYPE_ProfileID 9g34.2.7 A_ARG_TYPE_AppList 9g34.2.8 A_ARG_TYPE_URI 1

14、4g34.2.9 A_ARG_TYPE_String . 14g34.2.10 A_ARG_TYPE_Bool . 15g34.2.11 A_ARG_TYPE_INT 15g34.2.12 A_ARG_TYPE_AppCertificateInfo . 15g34.3 Eventing and Moderation . 17g34.4 Supporting Multiple Client Profiles . 17g34.5 Actions . 17g34.5.1 General 17g34.5.2 GetApplicationList 18g34.5.2.1 General 18g34.5.

15、2.2 Arguments. 18g34.5.2.3 Effect on State . 19g34.5.2.4 Errors . 19g34.5.3 LaunchApplication 19g34.5.3.1 General 19g34.5.3.2 Arguments. 20g34.5.3.3 Effect on State . 20g34.5.3.4 Errors . 20g34.5.4 TerminateApplication . 21g34.5.4.1 General 21g34.5.4.2 Arguments. 21g34.5.4.3 Effect on State . 22g34.

16、5.4.4 Errors . 22g34.5.5 GetApplicationStatus 22g34.5.5.1 General 22g34.5.5.2 Arguments. 22g34.5.5.3 Effect on State . 22g34.5.5.4 Errors . 23g34.5.6 GetApplicationCertificateInfo 23g34.5.6.1 General 23g34.5.6.2 Arguments. 23g34.5.6.3 Effect on State . 23g34.5.6.4 Errors . 24g34.5.7 GetCertifiedAppl

17、icationsList 24g34.5.7.1 General 24g3ETSI ETSI TS 103 544-9 V1.3.0 (2017-10)4 4.5.7.2 Arguments . 24g34.5.7.3 Effect on State . 24g34.5.7.4 Errors . 25g34.5.8 GetAppCertificationStatus 25g34.5.8.1 General 25g34.5.8.2 Arguments. 25g34.5.8.3 Effect on State . 26g34.5.8.4 Errors . 26g34.5.9 SetAllowedA

18、pplicationsList . 26g34.5.9.1 General 26g34.5.9.2 Arguments. 26g34.5.9.3 Effect on State . 27g34.5.9.4 Errors . 27g34.5.10 Relationships Between Actions 27g34.5.11 Error Code Summary 28g35 Theory of Operation . 29g35.1 Use of Quotation Marks . 29g35.2 Identification of Applications from A_ARG_TYPE_A

19、ppList . 29g35.2.1 Identifying the VNC Server 29g35.2.2 Identifying Remote VNC based Applications. 30g35.2.3 Identifying Audio Links 30g35.2.4 Identifying Common Data Bus . 31g35.2.5 Identifying Device Attestation Protocol Server 31g35.3 Example Values of AppListingFilter 31g35.4 Example Values of A

20、ppCertFilter 32g35.5 Example Values of State Variables 33g35.5.1 AppStatusUpdate 33g35.5.2 AppListUpdate 33g35.5.3 A_ARG_TYPE_AppStatus 33g35.5.4 A_ARG_TYPE_AppList 34g35.6 XML Signature Minimum Set 36g35.7 Handling of Applications Available via Home Screen Application . 36g35.8 Handling of Applicat

21、ion Status Change . 37g35.9 Handling of different Protocol IDs . 37g36 XSD Schema 38g36.1 A_ARG_TYPE_AppStatus XSD Schema 38g36.2 A_ARG_TYPE_AppList XSD Schema . 38g36.3 A_ARG_TYPE_AppCertificateInfo XSD Schema 41g37 XML Service Description 41g3Annex A (informative): Authors and Contributors . 46g3H

22、istory 47g3ETSI ETSI TS 103 544-9 V1.3.0 (2017-10)5 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 members and no

23、n-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.org/). Pu

24、rsuant 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 present d

25、ocument. 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 and/or tr

26、adename. 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 Systems (ITS

27、). The present document is part 9 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 interpreted a

28、s 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-9 V1.3.0 (2017-10)6 1 Scope The present document is part of the MirrorLinkspecifi

29、cation 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 color display, audio i

30、nput/output and user input mechanisms. The TmApplicationServer service is a UPnP service that allows UPnP Control Points to remotely launch and terminate applications on MirrorLink Server devices. Through this service, UPnP control points can provide more fine-grained control and access to specific

31、remote applications. 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 refer

32、enced 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, ETSI cannot guar

33、antee their long-term validity. The following referenced documents are necessary for the application of the present document. 1 UPnPTMForum: “UPnPTMDevice Architecture 1.1“, 15 October 2008. NOTE: Available at http:/www.upnp.org. 2 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“,

34、January 2005. NOTE: http:/tools.ietf.org/html/rfc3986. 3 W3C Recommendation, 10 June 2008: “XML Signature Syntax and Processing (Second Edition)“. NOTE: Available at http:/www.w3.org/TR/xmldsig-core/. 4 ETSI TS 103 544-26 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Syste

35、ms (ITS); MirrorLink ; Part 26: Consumer Experience Principles and Basic Features“. 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-

36、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 guarantee their long-term validity. The following referenced documents are not necessary for th

37、e 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 (ITS); MirrorLink; Part 1: Connectivity“. ETSI ETSI TS 103 544-9 V1.3.0 (2017-10)7 3 Definit

38、ions, symbols and abbreviations Not applicable. 4 Service Modeling Definitions 4.1 Service Type The following service type identifies a service that is compliant with the present document: urn:schemas-upnp-org:service:TmApplicationServer:1. TmApplicationServer service is used herein to refer to this

39、 service type. The TmApplicationServer service shall follow defined UPnP behaviour within the UPnP Device Architecture 1.1 1. 4.2 State Variables 4.2.1 State Variable Overview Table 4-1: Service State Variables Variable Name Req. or Opt. Data Type Allowed Value Default Value Eng. Units AppStatusUpda

40、te R string Undefined Empty string N/A AppListUpdate string Undefined Empty string N/AA_ARG_TYPE_AppStatus R string Undefined Empty string N/A A_ARG_TYPE_AppID R string Undefined Empty string N/AA_ARG_TYPE_ProfileID ui4 Undefined 0 N/A A_ARG_TYPE_URI R string Undefined Empty string N/AA_ARG_TYPE_App

41、List R string Undefined Empty string N/A A_ARG_TYPE_String string Undefined Empty string N/AA_ARG_TYPE_Bool R string true | false false N/AA_ARG_TYPE_INT ui4 Undefined 0 N/A A_ARG_TYPE_AppCertificateInfo R string Undefined Empty string N/A R = REQUIRED, O = OPTIONAL, X = Non-standard 4.2.2 AppStatus

42、Update A string formatted as UTF-8 represents the list of application identifiers (appIDs) of applications whose status has changed. The string consists of a comma-separated list of appIDs identifying applications whose status has changed. Each entry in the list is of the type A_ARG_TYPE_AppID. This

43、 state variable is evented, implying that clients can subscribe to receive notifications every time the variable changes using UPnP standardized eventing mechanisms. It is important to note that this variable only contains the appIDs of those applications, whose status has changed since the last tim

44、e an event notification was sent out. On receiving an AppStatusUpdate event, the MirrorLink UPnP Control Point can query the application status of specific applications in the list by invoking the GetApplicationStatus action. AppStatusUpdate value will consist of a comma separated list of all applic

45、ation identifiers (appIDs) of applications listed in A_ARG_TYPE_AppList when the event is issued by the TmApplicationServer service for the first time. ETSI ETSI TS 103 544-9 V1.3.0 (2017-10)8 After an application launch, the MirrorLink Server shall only send the AppStatusUpdate event, once the appl

46、ication is running and in foreground. The AppStatusUpdate shall be send only after the response to the UPnP LaunchApplication or TerminateApplication action has been sent for UI applications. The MirrorLink Server will provide information of the current foreground framebuffer also via the VNC/WFD co

47、ntext information. During an application launch or termination action, this information can be temporarily out of sync with the UPnP application status, e.g. the UPnP information might be trailing the VNC context info in case of an application launch. In case the framebuffer transfers have been paus

48、ed, e.g. due to the MirrorLink application being in the background on the MirrorLink Client screen, the VNC context information will not be updated until the framebuffer transfer is resumed. 4.2.3 AppListUpdate A string formatted as UTF-8 represents a list of application identifiers (appIDs) of appl

49、ications whose entries have changed in the application listing. The string consists of a comma-separated list of appIDs identifying applications whose status has changed. Each entry in the list is of the type A_ARG_TYPE_AppID. It is evented, implying that clients can subscribe to receive notifications every time the variable changes using UPnP standardized eventing mechanisms. It is important to note that this variable only contains the appIDs of those applications, whose entries in the application list have changed since the last time an event not