1、 ETSI TS 103 544-12 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 12: UPnP Server Device CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Technical Committee Intelligent Transpor
2、t Systems (ITS). CCC is owner of the copyright of the document CCC-TS-030 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 incl
3、uding 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-12 V1.3.0 (2017-10)2 Reference DTS/ITS-88
4、-12 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 Th
5、e 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 authorization
6、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 aware
7、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 servi
8、ces: 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 sha
9、ll 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. MirrorLin
10、k 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, UMTSTMand t
11、he 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 registe
12、red and owned by the GSM Association. ETSI ETSI TS 103 544-12 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 Definitions, symbols and abbreviations . 6g34 Dev
13、ice Definitions 6g34.1 Device Type . 6g34.2 Device Model . 6g34.2.1 General 6g34.2.2 Relationship Between Services . 6g34.3 Theory of Operation . 7g34.3.1 General 7g34.3.2 XML Signature Minimum Set 11g35 XML Device Description . 11g36 Test . 13g3Annex A (normative): XSD Schema . 14g3A.1 XSD Schema f
14、or UDA 1.1 . 14g3A.2 ml1-0.xsd 18g3A.3 ml1-1.xsd 19g3A.4 ml1-2.xsd (MirrorLink 1.2) 19g3A.5 ml1-3.xsd (MirrorLink 1.3) 20g3Annex B (informative): Authors and Contributors . 21g3History 22g3ETSI ETSI TS 103 544-12 V1.3.0 (2017-10)4 Intellectual Property Rights Essential patents IPRs essential or pote
15、ntially 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 Essential
16、, 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 can b
17、e 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 by
18、 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, serv
19、ices 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 12 of a multi-part deliverable. Full details of the entire series can be found in part 1
20、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 “must n
21、ot“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 544-12 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 pre
22、sent 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 input/output and user input mechanisms. The present document defines the device: urn:schemas-upnp-org:device:TmServerDev
23、ice:1. This device can be a UPnP root device or embedded within a different device. The TmServerDevice encapsulates all services for the MirrorLink UPnP Server Device Control Protocol (DCP). 2 References 2.1 Normative references References are either specific (identified by date of publication and/o
24、r 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. Referenced documents which are not found to be publicly available in the expect
25、ed 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 guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. 1 UP
26、nPTM Forum: “UPnPTM Device Architecture 1.1“, 15 October 2008. NOTE: Available at http:/www.upnp.org. 2 ETSI TS 103 544-26 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 26: Consumer Experience Principles and Basic Features“. 3 W3C Recommenda
27、tion, 10 June 2008: “XML Signature Syntax and Processing (Second Edition)“. NOTE: Available at http:/www.w3.org/TR/xmldsig-core/. 4 Unicode Consortium: “Unicode 7.0 Character Code Charts“. NOTE: Available at http:/www.unicode.org/charts/. 2.2 Informative references References are either specific (id
28、entified 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks included in thi
29、s 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 present document but they assist the user with regard to a particular subject area. i.1 ETSI TS 103 544-1 (V1.3.0): “Publicl
30、y Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 1: Connectivity“. ETSI ETSI TS 103 544-12 V1.3.0 (2017-10)6 3 Definitions, symbols and abbreviations Not applicable. 4 Device Definitions 4.1 Device Type The following device type identifies a device that is compl
31、iant with this template: urn:schemas-upnp-org:device:TmServerDevice:1 We herein refer to this device in the present document as TmServerDevice. The TmServerDevice device shall follow defined UPnP behaviour within the UPnP Device Architecture 1.1 1. 4.2 Device Model 4.2.1 General The following table
32、briefly describes the services used in TmServerDevice. Table 1: TmServerDevice Service Descriptions Service Name Service Description TmApplicationServer Allows for discovery and remote control of applications. TmClientProfile Allows MirrorLink UPnP Control Point to specify its preferences, settings
33、and capabilities. TmNotificationServer Allows MirrorLink UPnP Server to send notification events Products that expose devices of the type urn:schemas-upnp-org:device:TmServerDevice:1 shall implement minimum version numbers of all required embedded devices and services specified in the table below. T
34、able 2: Device Requirements for TmServerDevice DeviceType Root Req. or Opt.1ServiceType Req. or Opt.1Service ID2TmServerDevice:1 Yes R TmApplicationServer:1 R TmApplicationServer TmClientProfile:1 R TmClientProfile TmNotificationServer:1 O TmNotificationServer1R = Required, O = Optional. 2Prefixed b
35、y urn:upnp-org:serviceId: . 4.2.2 Relationship Between Services Figure 1 shows the logical structure of the device and the encapsulated services which provide MirrorLink capabilities. The TmClientProfile service provides a way for the MirrorLink UPnP Control Point to notify the MirrorLink Server dev
36、ice about its preferences, capabilities and desired settings (i.e. client profile). This information can then be utilized by other services hosted by the MirrorLink Server device such as the TmApplicationServer service. The TmApplicationServer service provides a way for the MirrorLink UPnP Control P
37、oint to remotely control and access applications on the MirrorLink Server device. ETSI ETSI TS 103 544-12 V1.3.0 (2017-10)7 The TmNotificationServer service provides a way for the MirrorLink UPnP Server to notify the MirrorLink UPnP Control Point on application notification events. Figure 1: Relatio
38、nship between TmServerDevice and Services 4.3 Theory of Operation 4.3.1 General TmServerDevice provides mechanisms which enable MirrorLink UPnP Control Points to discover and access MirrorLink services. Table 3 lists the attributes which are part of the TmServerDevice and specified as extensions to
39、the standard UPnP Device XML schema. Table 3: Extended Attributes for TmServerDevice Element Description Parent Availability X_mirrorLink Version MirrorLink Server Version Note: If the version information is missing, the MirrorLink Client shall assume a version 1.0 MirrorLink Server. device Mandator
40、y majorVersion MirrorLink Server Major Version A_ARG_TYPE_Int X_mirrorLink Version Mandatory minorVersion MirrorLink Server Minor Version A_ARG_TYPE_Int X_mirrorLink Version Mandatory X_connectivity Connectivity settings device Conditional bluetooth Bluetooth settings of device X_connectivity Condit
41、ional bdAddr Bluetooth MAC address (BD_ADDR). Indicates device support for Bluetooth on the device. (A UTF-8 encoded string representing an unsigned 48-bit integer in hexadecimal format (without any 0x prefix).) bluetooth Conditional ETSI ETSI TS 103 544-12 V1.3.0 (2017-10)8 Element Description Pare
42、nt Availability startConnection A_ARG_TYPE_Bool Bluetooth Connection will be initiated from device. Default: true bluetooth Optional clientBdAddr Bluetooth MAC address (BD_ADDR) of the connected Bluetooth device. (A UTF-8 encoded string representing an unsigned 48-bit integer in hexadecimal format (
43、without any 0x prefix).) Shall be included, if bdAddr is not provided and a Bluetooth connection exists. bluetooth Conditional wifi WiFi settings of the device X_connectivity Optional macAddr WiFi MAC address (A UTF-8 encoded string representing an unsigned 48-bit integer in hexadecimal format (with
44、out any “0x“ prefix, and without any grouping using “:“, “.“ or “-“) wifi Mandatory ssid Service Set Identifier (SSID), Base64 encoded (A_ARG_TYPE_String) wifi Optional roles Comma separated list of supported roles. Allowed values are AP (Access Point role) Client (Client role) P2P (Infrastructure-l
45、ess) (A_ARG_TYPE_String) Default: AP,Client,P2P wifi Optional protectionList List of WiFi access protection wifi Optional protection* Access protection protectionList Optional protocol Security protocol used to protect WiFi access. Allowed values are WEP WPA WPA2 WPS NOTE: WEP/WPA is listed for lega
46、cy reasons, and should not be used (A_ARG_TYPE_String) protection Mandatory passkey Passkey/Shared key, Base64 encoded Shall be left empty, if transmitted over an unprotected or shared transport channel (e.g. WiFi) (A_ARG_TYPE_String) protection Mandatory X_deviceKeys Device specific physical hard k
47、eys Deprecated device Deprecated key* Defines a device specific key Deprecated X_deviceKeys Deprecated name Short name (A_ARG_TYPE_String) Deprecated key Deprecated mandatory Flag (A_ARG_TYPE_Bool) Deprecated key Deprecated symbolValue Keys symbol hexadecimal value Deprecated key Deprecated icon* De
48、scribes an icon representing the key Deprecated key Deprecated ETSI ETSI TS 103 544-12 V1.3.0 (2017-10)9 Element Description Parent Availability mimetype Type of icon image Deprecated icon Deprecated width Width of icon (A_ARG_TYPE_INT) Deprecated icon Deprecated height Height of icon (A_ARG_TYPE_IN
49、T) Deprecated icon Deprecated depth Icon color depth (A_ARG_TYPE_INT) Deprecated icon Deprecated url Url to icon (A_ARG_TYPE_URI) Deprecated icon Deprecated X_Signature XML signature over entire contents of the root element. This is done as specified in 3. The key used in calculating the signature shall be the private part of the application-specific key which public part was bound to the attestation of UPnP-Server component. (The public part can be used to verify the signature.) The Reference element of the XML signature shall
