ETSI TS 103 544-13 V1.3.1 (2019-10)

Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 13: Core Architecture

RTS/ITS-98-13

General Information

• Status: Published
• Publication Date: 08-Oct-2019
• Technical Committee: ITS - Intelligent Transport Systems
• Current Stage: 12 - Completion
• Due Date: 30-Sep-2019
• Completion Date: 09-Oct-2019

Standards Content (Sample)

ETSI TS 103 544-13 V1.3.1 (2019-10)






TECHNICAL SPECIFICATION
Publicly Available Specification (PAS);
Intelligent Transport Systems (ITS);
®
MirrorLink ;
Part 13: Core Architecture
CAUTION
The present document has been submitted to ETSI as a PAS produced by CCC and
approved by the ETSI Technical Committee Intelligent Transport Systems (ITS).
CCC is owner of the copyright of the document CCC-TS-032 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 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.

---------------------- Page: 1 ----------------------
2 ETSI TS 103 544-13 V1.3.1 (2019-10)



Reference
RTS/ITS-98-13
Keywords
interface, ITS, PAS, smartphone

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (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 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users 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 your 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 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 2019.
© Car Connectivity Consortium 2011-2019.
All rights reserved.
ETSI logo is a Trade Mark of ETSI registered for 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 Open Connectivity Foundation, Inc.
Other names or abbreviations used in the present document may be trademarks of their respective owners.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 544-13 V1.3.1 (2019-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Introduction to MirrorLink . 8
5 MirrorLink Architecture . 9
6 MirrorLink Features . 11
7 MirrorLink Session . 13
7.1 General . 13
7.2 UPnP Operation Start . 14
7.3 MirrorLink Session Setup . 14
7.3.1 General . 14
7.3.2 Physical Interface Selection . 15
7.3.3 Setting the Client Profile . 16
7.3.4 Executing Device Attestation Protocol . 17
7.3.5 Establishing other Connections . 17
7.4 MirrorLink Operation . 17
7.4.1 Updating the Client Profile . 17
7.4.2 Changing the Physical Interface . 17
7.4.3 Changing the Remote UI Mechanism . 17
7.4.4 Disappearing Physical Interfaces . 18
7.4.5 Legacy MirrorLink Mode . 18
7.5 MirrorLink Session Termination . 19
7.6 Interoperability with other MirrorLink Versions . 20
Annex A (informative): Authors and Contributors . 21
History . 22


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 544-13 V1.3.1 (2019-10)
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 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. 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 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 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, 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 13 of a multi-part deliverable. Full details of the entire series can be found in part 1 [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 not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 544-13 V1.3.1 (2019-10)
1 Scope
®
The present document is part of the MirrorLink specification 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
input/output and user input mechanisms.
The present document defines the core MirrorLink architecture, linking the different MirrorLink related protocols
together, and providing MirrorLink session management related information.
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
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 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] ETSI TS 103 544-1 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 1: Connectivity".
[2] ETSI TS 103 544-2 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 2: Virtual Network Computing (VNC) based Display and
Control".
[3] ETSI TS 103 544-3 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 3: Audio".
[4] ETSI TS 103 544-4 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 4: Device Attestation Protocol (DAP) ".
[5] ETSI TS 103 544-5 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 5: Common Data Bus (CDB)".
[6] ETSI TS 103 544-6 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 6: Service Binary Protocol (SBP)".
[7] ETSI TS 103 544-7 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 7: GPS Data Service".
[8] ETSI TS 103 544-8 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 8: Location Data Service".
[9] ETSI TS 103 544-9 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 9: UPnP Application Server Service".
[10] ETSI TS 103 544-10 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 10: UPnP Client Profile Service ".
[11] ETSI TS 103 544-11 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 11: UPnP Notification Server Service".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 544-13 V1.3.1 (2019-10)
[12] ETSI TS 103 544-12 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 12: UPnP Server Device".
[13] ETSI TS 103 544-14 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 14: Application Certificates".
[14] ETSI TS 103 544-15 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 15: Application Programming Interface (API) Level 1 & 2".
[15] ETSI TS 103 544-16 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 16: Application Developer Certificates".
[16] ETSI TS 103 544-17 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 17: MirrorLink® over Wi-Fi Display (WFD)".
[17] ETSI TS 103 544-18 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
TM
Systems (ITS); MirrorLink®; Part 18: IEEE 802.11 Car Connectivity Consortium (CCC)
Information Element".
[18] ETSI TS 103 544-19 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 19: Network Information Data Service".
[19] ETSI TS 103 544-20 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 20: Internet Accessibility".
[20] ETSI TS 103 544-21 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 21: High Speed Media Link (HSML)".
[21] ETSI TS 103 544-22 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 22: Android Specific Specifications enabling AIDL-based
MirrorLink® Applications".
[22] ETSI TS 103 544-23 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 23: Bluetooth ® out-of-Band Pairing Data Service".
[23] ETSI TS 103 544-24 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 24: Media Meta Data Service".
[24] ETSI TS 103 544-25 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 25: Navigation Meta Data Service".
[25] ETSI TS 103 544-26 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 26: Consumer Experience Principles and Basic Features".
[26] ETSI TS 103 544-27 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 27: Basic Meta Data Service".
[27] ETSI TS 103 544-28 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 28: Weather Data Service".
[28] ETSI TS 103 544-29 (V1.3.1): "Publicly Available Specification (PAS); Intelligent Transport
Systems (ITS); MirrorLink®; Part 29: Schedule Data Service".
TM TM
[29] UPnP Forum, "UPnP Device Architecture 1.1", 15 October 2008.
NOTE: Available at http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 544-13 V1.3.1 (2019-10)
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-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 the application of the present document but they assist the
user with regard to a particular subject area.
Not applicable.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms 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 user 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 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
A2DP Bluetooth Advanced Audio Distribution Profile
AP Access Point
API Application Programming Interface
BT Bluetooth
CDB Common Data Bus
CDC Communications Device Class
NOTE: Specified from USB Device Working Group.
DAP Device Attestation Protocol
GENA General Event Notification Architecture
GPS Global Positioning System
HFP Bluetooth Hands-free Profile
HSML High-Speed Media Link
IE Information Element
IP Internet Protocol
MAC Medium Access Control
NCM Network Control Model; part of the CDC device class
RFB Remote Framebuffer
RLE (Scan-line based) Run Length Encoding
RTP Real-time Transport Protocol
SBP Service Binary Protocol
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 544-13 V1.3.1 (2019-10)
SOAP Simple Object Access Protocol
SSDP Simple Service Discovery Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
UI User Interface
UPnP Universal Plug and Play
URL Universal Resource Locator
USB Universal Serial Bus
VA Video-Audio
VNC Virtual Network Computing
WFD Wi-Fi Display
WLAN Wireless Local Area Network
XML eXtensible Markup Language
4 Introduction to MirrorLink
MirrorLink provides a concept for integrating the mobile device (hereinafter referred to as the "MirrorLink Server") and
the vehicle head-unit (hereinafter referred to as the "MirrorLink Client"). In a MirrorLink context, the control and
interaction of applications and services running on the mobile device will be replicated into the car environment.
Diverting display and audio output to the car head-unit come together with receiving key and voice control input from it
are the main interaction streams, as shown in Figure 1.
Applications User Speaker
Content Display
& Services Input & Micro
Display Control
Consumer
Automotive
Electronics
Head Unit
Device
Audio / Voice
Internet

Figure 1: MirrorLink Concept
The result is a concept somewhere between running the applications natively in the mobile phone or in the car unit.
From the user experience point of view it can offer "the best of the both worlds" where the large variety of mobile
phone applications is complemented and enhanced by the car system providing convenient and safe means for using
(i.e. controlling) these applications.
It is easier to add new consumer electronic functionalities into the vehicle environment via a mobile device than
integrating them into the car infotainment system. In any case, the usage of those applications will become more
convenient if the same device with the same content stored in it can be used in all the different environments from home
to car, and providing Internet connectivity at the same time. On the other hand, the large displays of the car units can
enhance the user experience from what the mobile device can offer by itself.
In addition, the mobile device typically provides the latest technologies, from radio connectivity, to multimedia codecs.
At the same time, the openness of the platforms, allows delivery of new applications and services at any time.
The car systems comprise of several different methods for user interaction, like individual keys, rotating knobs, touch
screen and even voice-activated control. For proper interoperability, the control method towards the mobile device
should be the same regardless of the actual input mechanism on the car side.
The basic MirrorLink consumer experience principles and features are specified in [25].
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 544-13 V1.3.1 (2019-10)
5 MirrorLink Architecture
The MirrorLink high-level architecture is shown in Figure 2.

Figure 2: MirrorLink Architecture
MirrorLink 1.1 Architecture consists of a set of protocols, providing the following features:
1) Connectivity, as specified in [1], providing:
a) wired and wireless IP based connection-oriented and connection-less connectivity; and
b) dedicated Bluetooth connectivity.
2) UPnP based Services, providing:
a) mechanisms for advertisement of MirrorLink enabled Server devices as specified in [12];
b) mechanisms for application notifications, as specified in [11];
c) mechanisms for MirrorLink client profiles, as specified in [10]; and
d) mechanisms for advertisement and control of MirrorLink server based applications and their certification
information, as specified in [9].
3) Access to Screen and Control, as specified in [2], providing:
a) replication of the MirrorLink Server's display content to the MirrorLink Client using VNC;
b) control channel of Key, Pointer and Touch events back to the MirrorLink Client; and
c) exchanging display and event related information and notifications.
4) Audio, as specified in [3], providing:
a) RTP audio streaming, for different payload types, outputting the MirrorLink Server.
b) RTP audio streaming, for different payload types, inputting the MirrorLink Server.
c) BT HFP based legacy phone audio.
d) BT A2DP based legacy media audio.
5) Access to Data Services, providing:
a) simple multiplexed, shared bus, hosting services, as specified in [5];
b) binary protocol framework for implementing various services, as specified in [6];
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 544-13 V1.3.1 (2019-10)
c) GPS data service using the binary protocol framework, as specified in [7]; and
d) location data service, using the binary protocol framework, as specified in [8].
6) Security mechanisms, as specified in [4], providing:
a) Attestation of MirrorLink Server devices and their main MirrorLink protocol components.
7) MirrorLink API:
a) Introduced application certificates, as specified in [13].
b) Introduced application developer certificates, as specified in [15].
c) Introduced MirrorLink API Level 1, as specified in [14].
MirrorLink 1.2 Architecture is adding the following additional features:
1) Connectivity:
a) CCC specific IEEE 802.11 Information Element (OUI) as specified in [17].
b) Internet Accessibility supporting Group Ownership negotiation in Wi-Fi P2P networks, as specified in
[19].
2) UPnP based Services:
a) No additional services; some smaller additions to some of the services, as highlighted in [9], [10] and
[12].
3) Access to Screen and Control, providing:
a) Replication of MirrorLink Server's display contents to the MirrorLink Client using HSML as specified in
[20].
b) Replication of MirrorLink Server's display contents to the MirrorLink Client using Wi-Fi Display, as
specified in [16].
4) Audio:
a) No additions.
5) Data Services:
a) Network Management Data Service, providing dynamic information on network status, as specified in
[18].
6) Security mechanisms:
a) Added WFD and HSML elements as highlighted in [4].
7) Mirrorlink API:
a) No additions.
MirrorLink 1.3 Architecture is adding the following additional features:
1) Connectivity:
a) No additions.
2) UPnP based Services:
a) Deprecation of element in UPnP A_ARG_TYPE_AppList, as specified in [9].
b) Deprecation of elements in UPnP A_ARG_TYPE_ClientProfile as specified in [10].
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 544-13 V1.3.1 (2019-10)
3) Access to Screen and Control:
a) Deprecation of VNC protocol features, as specified in [2].
b) Addition of VA H.264 encoding, as specified in [2].
4) Audio:
a) Added RTP payload 100, as specified in [3].
5) Data Services:
a) Bluetooth out-of-Band Pairing Data Service, as specified in [22].
b) Media Meta Data Service, as specified in [23].
c) Navigation Meta Data Service, as specified in [24].
d) Basic Meta Data Service, as specified in [26].
e) Weather Data Service, as specified in [27].
f) Schedule Data Service, as specified in [28].
6) Security mechanisms:
a) No additions.
7) MirrorLink API:
a) Introduced MirrorLink API Level 2, as specified in [14].
MirrorLink is platform agnostic; but Android specific requirements are captured in [21].
6 MirrorLink Features
Table 1 specifies the requirements for the different MirrorLink features for the MirrorLink Server and Client and for
which version the feature has been introduced.
The version number given for a specific feature, highlights the MirrorLink version in which the feature has been
introduced. The feature is available with the same given obligation for the MirrorLink Server and Client from that
version onward. In case the obligation changes between versions, an additional entry is made, defining the new feature
obligation.
Table 1: MirrorLink Feature Requirements
MirrorLink MirrorLink
Feature Version
Server Client
USB Host 1.0 N/A Shall
USB Device 1.0 Shall N/A
USB
CDC/NCM Device Class 1.0 Shall Shall
HSML Device Class 1.2 Should Should
Connec-
tivity
Wi-Fi Access Point 1.0 Should Should
Wi-Fi Device 1.0 Should Should
WLAN
IEEE 802.11 CCC IE [17] 1.1 Conditional Conditional
Wi-Fi-Direct P2P 1.1 Should Should
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 544-13 V1.3.1 (2019-10)
MirrorLink MirrorLink
Feature Version
Server Client
Server Device 1.0 Shall N/A
UPnP
Application Server Service 1.0 Shall N/A
Server
UPnP
Services Client Profile Service 1.0 Shall N/A
based
Provided
1.1 Should
Services
Notification Server Service N/A

1.3 Shall

Server Device 1.0 N/A Shall
MirrorLink
UPnP
implements
Application Server Service 1.0 N/A Shall
Control
2-Box pull
Point
1.0 Should
model
Client Profile Service N/A
Services
1.2 Shall

Supported
1.1 Should
Notification Server Service N/A

1.3 Shall
VNC over USB 1.0 Shall Shall
VNC
VNC over Wi-Fi 1.0 May May
Screen &
Control
HSML 1.2 Should Should
Wi-Fi Display 1.2 Should Should
1.0 Shall Should
RTP Server
(6)
1.3 Shall Conditional
RTP
1.0 Should Shall
RTP Client
Audio
1.3 Shall Shall
1.0 Should Should
BT HFP
(7) (6)
BT 1.3 Conditional Conditional
BT A2DP 1.0 May May
1.1 Should N/A
Sink Endpoint
1.3 Shall Should
CDB/SBP
1.1 N/A Should
Source Endpoint
(1)
1.3 Shall Shall
Access to
Data (4) (3)
GPS Data Service 1.1 Should Should
(4) (5) (3) (5)

1.1 Should Should
Location Data Service
(4) (5) (2) (3) (5)

1.3 Shall Shall
(3) (4)

Network Management Data Service 1.2 May May
(3) (5) (4) (5)

Media Meta Data Service 1.3 Shall Should
(3) (5) (4) (5)

Navigation Meta Data Service 1.3 Shall Should
(3) (4)
Weather Data Service 1.3 Shall Should
(3) (4)
Schedule Data Service 1.3 Shall Should
(4) (3)
Bluetooth out-of-band Pairing Data Service 1.3 Should Should
1.0 Should
Server Endpoint N/A
Security 1.1 Shall
DAP
1.0 Should
Client Endpoint N/A
1.3 Shall
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 544-13 V1.3.1 (2019-10)
MirrorLink MirrorLink
Feature Version
Server Client
(1)
Shall be implemented, unless the MirrorLink Client does not implement any source data service.
(2)
Shall be implemented, unless the MirrorLink Client does not have access to GPS information.
(3)
Data Service Source.
(4)
Data Service Sink.
(5)
Reverse operation of the data service may be supported as well.
(6)
Shall be implemented, if MirrorLink Client has micro
...