1、 ETSI TS 103 544-11 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 11: UPnP Notification Server Service CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Technical Committee Intell
2、igent Transport Systems (ITS). CCC is owner of the copyright of the document CCC-TS-028 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
3、otherwise 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-11 V1.3.0 (2017-10)2 Refere
4、nce DTS/ITS-88-11 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 Impor
5、tant 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
6、authorization 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 sh
7、ould 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 f
8、ollowing 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 P
9、DF version 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 Memb
10、ers. 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, PLUGTESTST
11、M, UMTSTMand 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 trad
12、emarks registered and owned by the GSM Association. ETSI ETSI TS 103 544-11 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 abbreviati
13、ons . 6g34 Service Modeling Definition 7g34.1 Service Type . 7g34.2 TmNotificationServer Service Architecture . 7g34.3 State Variables 7g34.3.1 State Variable Overview . 7g34.3.2 ActiveNotiEvent . 7g34.3.3 NotiAppListUpdate . 8g34.3.4 A_ARG_TYPE_Notification 8g34.3.5 A_ARG_TYPE_AppID 10g34.3.6 A_ARG
14、_TYPE_ProfileID 11g34.3.7 A_ARG_TYPE_ActionID 11g34.3.8 A_ARG_TYPE_NotiID 11g34.3.9 A_ARG_TYPE_String . 11g34.3.10 A_ARG_TYPE_URI 12g34.3.11 A_ARG_TYPE_INT 12g34.3.12 A_ARG_TYPE_Bool . 12g34.4 Eventing and Moderation . 12g34.5 Supporting Multiple Client Profiles . 12g34.6 Actions . 12g34.6.1 General
15、 12g34.6.2 GetNotification . 13g34.6.2.1 General 13g34.6.2.2 Arguments. 13g34.6.2.3 Effect on State . 13g34.6.2.4 Errors . 13g34.6.3 GetSupportedApplications 13g34.6.3.1 General 13g34.6.3.2 Arguments. 14g34.6.3.3 Effect on State . 14g34.6.3.4 Errors . 14g34.6.4 SetAllowedApplications . 14g34.6.4.1 G
16、eneral 14g34.6.4.2 Arguments. 15g34.6.4.3 Effect on State . 15g34.6.4.4 Errors . 15g34.6.5 InvokeNotiAction . 15g34.6.5.1 General 15g34.6.5.2 Arguments. 16g34.6.5.3 Effect on State . 16g34.6.5.4 Errors . 16g34.6.6 Error Code Summary 16g35 Theory of Operation . 17g35.1 Initialization steps. 17g35.2 H
17、andling of notification . 18g35.2.1 Not using Head Unit UI for notification . 18g35.2.2 Using Head Unit UI for notification . 19g3ETSI ETSI TS 103 544-11 V1.3.0 (2017-10)4 5.3 Displaying a notification message 21g35.4 XML Signature Minimum Set 22g36 A_ARG_TYPE_Notification XSD Schema . 22g37 XML Ser
18、vice Description 24g3Annex A (informative): Authors and Contributors . 26g3History 27g3ETSI ETSI TS 103 544-11 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 t
19、o 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 ETSI standards“, which is available from the ETSI Secretariat. L
20、atest 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 not referenced in ETSI SR 000 314 (or the updates on the ETS
21、I 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 these except for any which are indicated as being the prope
22、rty 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 trademarks. Foreword This Technical Specification (TS) has
23、 been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). The present document is part 11 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“, “ma
24、y“, “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 except when used in direct citation. ETSI ETSI TS 103 544-11
25、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 head-unit to interact with the mobile device in mind, but it
26、 will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The TmNotificationServer service is an UPnP service that allows control points to receive diverse notifications from the devices that support the TmNotificationServer service. The T
27、mNotificationServer service enables the following features to: send a notification to the head unit get an action described in the notification 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-spec
28、ific. For specific references, 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.ets
29、i.org/Reference/. 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 necessary for the application of the present document. 1 UPnPTMForum: “UPnPTMDevice Architecture 1.1“, 15
30、 October 2008. NOTE: Available at http:/www.upnp.org. 2 W3C Recommendation, 10 June 2008: “XML Signature Syntax and Processing (Second Edition)“. NOTE: Available at http:/www.w3.org/TR/xmldsig-core/. 2.2 Informative references References are either specific (identified by date of publication and/or
31、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 any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publ
32、ication, 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 particular subject area. i.1 ETSI TS 103 544-1 (V1.3.0): “Publicly Available Specification (PAS); Intell
33、igent Transport Systems (ITS); MirrorLink; Part 1: Connectivity“. 3 Definitions, symbols and abbreviations Not applicable. ETSI ETSI TS 103 544-11 V1.3.0 (2017-10)7 4 Service Modeling Definition 4.1 Service Type The following service type identifies a service that is compliant with the present docum
34、ent: urn:schemas-upnp-org:service:TmNotificationServer:1 TmNotificationServer defined in the present document refers to the same service type. The TmNotificationServer service shall follow defined UPnP behaviour within the UPnP Device Architecture 1.1 1. 4.2 TmNotificationServer Service Architecture
35、 This service provides the features for a MirrorLink UPnP Control Point to receive notifications from a MirrorLink UPnP Server Device. Based on information of the notification evented to the MirrorLink UPnP Control Point, the MirrorLink UPnP Control Point may launch the applications to bring it to f
36、oreground on the MirrorLink Server or may create its own native user interface. In both cases, this does allow the end-user to act on the given notification. 4.3 State Variables 4.3.1 State Variable Overview Table 4-1: Service State Variables Variable Name Req. or Opt. Data Type Allowed Value Defaul
37、t Value Eng. Units ActiveNotiEvent R string Undefined Empty string N/A NotiAppListUpdate string Undefined Empty string N/AA_ARG_TYPE_Notification R string Undefined Empty string N/A A_ARG_TYPE_AppID R string Undefined Empty string N/AA_ARG_TYPE_ProfileID R ui4 Undefined 0 N/A A_ARG_TYPE_ActionID R s
38、tring Undefined Empty string N/A A_ARG_TYPE_NotiID R string Undefined Empty string N/AA_ARG_TYPE_String R string Undefined Empty string N/A A_ARG_TYPE_URI R string Undefined Empty string N/AA_ARG_TYPE_INT R ui4 Undefined 0 N/A A_ARG_TYPE_Bool R string true | false false N/A1R = REQUIRED, O = OPTIONA
39、L, X = Non-standard 4.3.2 ActiveNotiEvent ActiveNotiEvent is an evented state variable of type A_ARG_TYPE_NotiID, which contains the most urgent notification that needs to be handled from the MirrorLink UPnP Control Point. ActiveNotiEvent shall originate from an application (as given in appID), whic
40、h has been set using the SetAllowedApplications actions. It is the responsibility of the MirrorLink UPnP Server to decide on the most urgent notification. If a notification event A gets overloaded by another notification event B, the notification event A may become pending again, once notification e
41、vent B is cleared and A is still pending. In that case the MirrorLink UPnP Server shall again provide an event update for the notification event A. ETSI ETSI TS 103 544-11 V1.3.0 (2017-10)8 If the state variable is an empty string, no notification is available on the MirrorLink UPnP Server to be han
42、dled from the MirrorLink UPnP Control Point. On receiving an AcitveNotiEvent event, the MirrorLink UPnP Control Point can query specific notification by invoking the GetNotication action. The MirrorLink Client shall immediately respond to an incoming notification, unless safety related or other high
43、er priority tasks currently require the users attention. Notifications from unsupported applications shall be immediately cleared, sending an InvokeNotiAction with ActionID set to “0x00“. Implementation Note: A MirrorLink 1.1 Client may not immediately respond to an incoming notification. The Mirror
44、Link UPnP Server shall clear the active notification if the MirrorLink UPnP Control Point has responded to the notification by either using the InvokeNotiAction action or by launching the respective application using TmApplicationServer:1 service LaunchApplication action. The MirrorLink UPnP Server
45、shall clear the active notification if the notification is not available on the MirrorLink UPnP Server anymore. When the event is issued the first time, the ActiveNotiEvent value shall contain either a single value of type A_ARG_TYPE_NotiID, in case a notification is available, or of an empty string
46、, in case no notification is available. 4.3.3 NotiAppListUpdate NotiAppListUpdate is an evented state variable of type A_ARG_TYPE_String, which contains a comma separated list of applications identifiers of applications, supporting notifications. Each application identifier is of type A_ARG_TYPE_App
47、ID. The 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 application identifiers of those applications, whose entries in su
48、pported applications list have changed since the last time an event notification was sent out (i.e. applications which either have added or removed notification support). On receiving a NotiAppListUpdate event, a MirrorLink UPnP Control Point can retrieve the supported application list by invoking t
49、he GetSupportedApplications action, to validate, whether an application has removed or added notification support. NotiAppListUpdate value shall consist of a comma separated list of all application identifiers from applications supporting notification, when the event is issued by the TmNotificationServer service for the first time. 4.3.4 A_ARG_TYPE_Notification The format of the A_ARG_TYPE_Notification state variable is an XML document. It includes detailed information about a notification. Table 4-2: Structure of the A_ARG_TYPE_Notification Element D
