1、 ETSI TS 103 544-2 V1.3.0 (2017-10) Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 2: Virtual Network Computing (VNC) based Display and Control CAUTION The present document has been submitted to ETSI as a PAS produced by CCC and approved by the ETSI Tec
2、hnical Committee Intelligent Transport Systems (ITS). CCC is owner of the copyright of the document CCC-TS-010 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,
3、 implied, statutory or 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-2 V1
4、.3.0 (2017-10)2 Reference DTS/ITS-88-2 Keywords interface, ITS, PAS, smartphone, USB 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 G
5、rasse (06) N 7803/88 Important 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
6、without the prior written 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
7、of the present document should 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 yo
8、ur comment to one of the following 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
9、ETSI. The content of the PDF 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 f
10、or the benefit of its Members. 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 this document may be trademarks of their respective owners.
11、 DECTTM, PLUGTESTSTM, 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 th
12、e GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 103 544-2 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 7g33 Definitions and a
13、bbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Introduction 8g35 Managing a VNC session . 8g35.1 Identifying Remote Applications and the VNC Server 8g35.2 Launching the VNC Session 8g35.3 Intentionally Terminating the VNC Session. 9g35.4 Unintentionally Terminating the VNC Session 10g
14、35.5 Testing Considerations . 10g36 Traditional VNC Protocol Phases 10g36.1 General . 10g36.2 Handshaking Phase. 10g36.3 Initialization Phase . 11g36.4 Framebuffer Update and Event Phase 13g37 VNC MirrorLink Extension Messages . 16g37.1 General . 16g37.2 ByeBye Message 17g37.3 Display Configuration
15、Messages 18g37.3.1 General 18g37.3.2 Framebuffer Scaling (VNC Server) 22g37.3.3 Framebuffer Scaling (VNC Client) . 23g37.3.4 Handling of Different Framebuffer Aspect Ratios 23g37.3.5 Handling of Server Pixel Aspect Ratios . 23g37.3.6 Handling of Application, Framebuffer and Display Orientation 24g37
16、.4 Event Configuration Messages . 24g37.5 Event Mapping Messages . 29g37.6 Device Status Messages . 30g37.7 Content Attestation Messages 33g37.8 Framebuffer Blocking Notification 36g37.9 Audio Blocking Notification 42g37.10 Touch Event . 45g38 Additional Encodings and Pseudo Encodings 47g38.1 Genera
17、l . 47g38.2 MirrorLink Pseudo Encoding . 47g38.3 Context Information Pseudo Encoding . 47g38.4 Desktop Size Pseudo Encoding 49g38.5 Scan Line based Run-Length Encoding . 49g38.6 VA H.264 Encoding . 51g38.6.1 Overview 51g38.6.2 Theory of operation 52g3Annex A (normative): Knob Configuration . 57g3Ann
18、ex B (normative): Key Event Mapping . 58g3ETSI ETSI TS 103 544-2 V1.3.0 (2017-10)4 Annex C (normative): Language Sets . 61g3C.1 Basic Set Latin-1 61g3Annex D (informative): Authors and Contributors . 62g3History 63g3ETSI ETSI TS 103 544-2 V1.3.0 (2017-10)5 Intellectual Property Rights Essential pate
19、nts 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 non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential
20、, 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/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out b
21、y 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 document. Trademarks The present document may include trademarks and/or tradenames which are ass
22、erted 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 tradename. Mention of those trademarks in the present document does not constitute an endorsement
23、 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). The present document is part 2 of a multi-part deliverable. Full details of the entire serie
24、s 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 as described in Clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provis
25、ions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 544-2 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
26、 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 colour display, audio input/output and user input mechanisms. The contents of the MirrorLink Server devices screen ar
27、e transferred to the MirrorLink Client device. The control inputs are transferred from the MirrorLink Client to the MirrorLink Server. Screen copy methods can be used to copy the content of the MirrorLink Servers framebuffer to the MirrorLink Clients display. The copy operation can include rotation
28、or colour conversion. The frame buffer is used as an abstraction layer, allowing any changes to the applications and services running on the mobile device to be avoided. For this purpose, the Virtual Networking Computing (VNC) protocol is used. 2 References 2.1 Normative references References are ei
29、ther 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 referenced document (including any amendments) applies. Referenced documents whic
30、h 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 guarantee their long-term validity. The following referenced documents are neces
31、sary for the application of the present document. 1 IETF RFC 6143: “The Remote Framebuffer Protocol“, March 2011, https:/tools.ietf.org/html/rfc6143. . 2 BluetoothSpecification: “Hands-free Profile 1.5“, Car Working Group, Revision V10r00, November 25, 2005. 3 ETSI TS 103 544-3 (V1.3.0): “Publicly A
32、vailable Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 3: Audio“. 4 ETSI TS 103 544-9 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 9: UPnP Application Server Service“. 5 ETSI TS 103 544-10 (V1.3.0): “Publicly Av
33、ailable Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 10: UPnP Client Profile Service“. 6 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“.
34、7 X Consortium Standard: “X Window System Protocol“, X Version 11, Release 6.9/7.0; ftp:/ftp.x.org/pub/X11R7.0/doc/PDF/proto.pdf. 8 Recommendation ITU-T H.264 (04-2017): “Advanced video coding for generic audiovisual services“, https:/www.itu.int/rec/T-REC-H.264-201704-I/en. 9 ISO 639-1: “Codes for
35、the representation of names of languages - Part 1: Alpha-2 code“. 10 ISO 3166-1: “Codes for the representation of names of countries and their subdivisions - Part 1: Country codes“. ETSI ETSI TS 103 544-2 V1.3.0 (2017-10)7 2.2 Informative references References are either specific (identified by date
36、 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 this clause were va
37、lid 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): “Publicly Available Spec
38、ification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 1: Connectivity“. i.2 US Department of Homeland Security: “Emergency Alerts“, https:/www.ready.gov/alerts. i.3 IANA, Protocol Registries, Remote Framebuffer (RFB) assignments, https:/www.iana.org/assignments/rfb/rfb.xhtml. . i.4
39、ISO/IEC 10646:2014: “Information technology - Universal Coded Character Set (UCS)“. i.5 ETSI TS 103 544-22 (V1.3.0): “Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink; Part 22: Android Specific Specifications enabling AIDL-based MirrorLink Applications“. 3 Defi
40、nitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: pointer event: touch screen action in which the user touches the screen with one (virtual) finger only at a single location touch event: touch screen action in which the use
41、r touches the screen with two or more separate fingers at different locations NOTE: touch events are used to describe more complex touch action, like pinch-open or pinch-close 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: A2DP Bluetooth Advanced Audio
42、 Distribution Profile ARP Address Resolution Protocol BT Bluetooth CDC Communications Device Class; specified from USB Device Working Group CE Consumer Electronics; CE devices are referred to as mobile devices within the present document DHCP Dynamic Host Configuration Protocol ECM Ethernet Control
43、Model; part of the CDC device class HFP Bluetooth Hands-free Profile HSP Bluetooth Headset Profile HMI Human Machine Interface HU Head-unit (this term is used interchangeably with the MirrorLink Client) HS Head-set IP Internet Protocol NCM Network Control Model; part of the CDC device class RFB Remo
44、te Framebuffer RTP Real-time Transport Protocol ETSI ETSI TS 103 544-2 V1.3.0 (2017-10)8 TCP Transmission Control Protocol UDP User Datagram Protocol UI User Interface UPnP Universal Plug and Play USB Universal Serial Bus VNC Virtual Network Computing 4 Introduction The Virtual Networking Computing
45、(VNC) uses the Remote Framebuffer Protocol (RFB) as a simple protocol for remote access to any sort of framebuffer-based user interface. The remote endpoint is called the VNC Client, whereas the endpoint driving the framebuffer is called the VNC Server. In the MirrorLink context, the VNC Client resi
46、des in the vehicle head-unit (MirrorLink Client) and the VNC Server is in the mobile device (MirrorLink Server). The VNC Client will show the remote display either on the entire local display or on a subset of it, as shown in Figure 1. Figure 1: MirrorLink VNC Setup The command and control input is
47、handled as part of the VNC protocol by key and pointer events. A key or pointer event on the MirrorLink Client will be signalled to the MirrorLink Server via a specific key symbol value, which uniquely identifies the event. The mobile device and/or its application will not necessarily support all po
48、ssible keys defined. Some applications may even have a dynamic behaviour on the selection of key inputs they expect. The RFB protocol originates from the desktop computing world and has been designed as a thin client protocol, i.e. it assumes a VNC Client with only a few requirements, and a VNC Serv
49、er having access to more processing capabilities. The protocol allows the VNC Client to be as simple as possible. In the MirrorLink context this assumption needs to be reconsidered, as mobile devices are experiencing performance limitations as well. The MirrorLink Client shall implement the VNC Client functionality. The MirrorLink Server shall implement the VNC Server functionality. 5 Managing a VNC session 5.1 Identifying Remote Applications and the VNC Server The identification of remote VNC based applications and o
