ETSI TS 103 152 V2.1.1 (2019-11)

TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
V2X Communications;
Multimedia Content Dissemination (MCD)
Basic Service specification;
Release 2
2 ETSI TS 103 152 V2.1.1 (2019-11)

Reference
DTS/ITS-00135
Keywords
application, information model, ITS, multimedia
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 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.
All rights reserved.
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
3 ETSI TS 103 152 V2.1.1 (2019-11)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
Introduction . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 9
4 MCD basic service introduction . 9
4.1 Background . 9
4.2 Services provided by the MCD basic service . 11
5 MCD basic service functional specification . 11
5.1 MCD basic service in the ITS architecture . 11
5.2 MCD basic service functional architecture. 12
5.3 Interfaces of the MCD basic service. 13
5.3.1 Interface to the ITS-S application layer . 13
5.3.2 Interface to the ITS-S network and transport layer . 14
5.3.2.1 General requirements . 14
5.3.2.2 Interface to the BTP over GeoNetworking stack . 15
5.3.2.3 Interface to the IPv6 stack and the combined IPv6/GeoNetworking stack . 16
5.3.3 Interface to the ITS-S management entity . 16
5.3.4 Interface to the ITS-S security entity . 16
6 Multimedia Content Dissemination . 16
6.1 Multimedia content dissemination concept . 16
6.1.1 Introduction. 16
6.1.2 Request / Event Identification . 17
6.1.3 Repetition of the MCDM . 17
6.1.4 Update of the MCDM . 17
6.1.5 Segmentation . 17
6.2 MCDM dissemination constraints . 18
6.2.1 General confidence constraints . 18
6.2.2 General security constraints . 18
6.2.3 General priority constraints. 18
7 MCDM format specification . 18
7.1 General structure . 18
7.1.1 Overview . 18
7.1.2 ITS PDU header . 19
7.1.3 MCDM management container. 19
7.1.4 MCDM situation container . 19
7.1.5 MCDM location container . 19
7.1.6 MCDM application container . 20
7.1.7 MCDM multimedia container . 20
7.2 MCDM format and decoding rules . 20
7.2.1 Common data dictionary . 20
7.2.2 MCDM data presentation . 20
8 Protocol operation of the MCD basic service . 20
8.1 Introduction . 20
ETSI
4 ETSI TS 103 152 V2.1.1 (2019-11)
8.2 Originator ITS-S operation . 21
8.2.1 Protocol data setting rules . 21
8.2.1.1 General requirements . 21
8.2.1.2 actionID . 21
8.2.2 General protocol operation . 21
8.3 Receiver ITS-S operation . 22
8.3.1 Protocol data setting rules . 22
8.3.2 General protocol operation . 22
8.3.3 Exception handling . 23
8.3.3.1 General requirements . 23
8.3.3.2 MCDM decoding exception . 23
Annex A (normative): ASN.1 specification of MCDM . 24
Annex B (normative): Description of the Data Elements (DE) / Data Frames (DF) . 26
B.1 ack . 26
B.2 actionID . 26
B.3 application . 26
B.4 authorizedPercentageLoss . 26
B.5 detectionTime . 27
B.6 endingMDU . 27
B.7 eventPosition . 27
B.8 eventType . 27
B.9 header . 27
B.10 informationQuality . 28
B.11 linkedCause . 28
B.12 linkedDenm . 28
B.13 location . 28
B.14 management . 28
B.15 mcdmInfo . 28
B.16 mediaType . 29
B.17 mediaTypes . 29
B.18 mediaContentUTF8 . 29
B.19 mediaContentOctet . 29
B.20 multimedia . 29
B.21 numberOfMDUs . 30
B.22 numberOfPDUs . 30
B.23 pduSequenceNumber. 30
B.24 realTime . 30
B.25 referenceTime . 30
B.26 request . 31
B.27 situation . 31
B.28 size . 31
B.29 startingMDU . 31
ETSI
5 ETSI TS 103 152 V2.1.1 (2019-11)
B.30 stationType . 31
B.31 url . 31
B.32 urls . 32
B.33 validityDuration . 32
History . 33

ETSI
6 ETSI TS 103 152 V2.1.1 (2019-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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).
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.
Introduction
ITS stations (ITS–Ss) exchange information with each other to satisfy a large diversity of customers' services.
Multimedia information provides enriched information to enhance the perception of the road users as well relatively to
their mobility environment as to the products and services being locally available. Multimedia information may also be
used to enhance the communication between individuals and communities during their mobility.
The exchange of multimedia information needs the specification of messages supporting multimedia such as pictures,
video clips, audio associated with data elements enabling their use.

ETSI
7 ETSI TS 103 152 V2.1.1 (2019-11)
1 Scope
The present document specifies the basic service of the facilities layer supporting Multimedia Content Dissemination
(MCD). It also specifies the Multimedia Content Dissemination Message (MCDM) being used for the multimedia
content dissemination.
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 EN 302 637-3: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set
of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic
Service".
[2] ETSI EN 302 931: "Intelligent Transport Systems (ITS); Vehicular Communications;
Geographical Area Definition".
[3] ETSI TS 102 894-2: "Intelligent Transport Systems (ITS); Users and applications requirements;
Part 2: Applications and facilities layer common data dictionary".
[4] Recommendation ITU-T X.691/ISO/IEC 8825-2 (2015): "Information technology - ASN.1
encoding rules: Specification of Packed Encoding Rules (PER)".
[5] ETSI TS 103 248: "Intelligent Transport Systems (ITS); GeoNetworking; Port Numbers for the
Basic Transport Protocol (BTP)".
[6] ETSI EN 302 636-4-1: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-
multipoint communications; Sub-part 1: Media-Independent Functionality".
[7] ETSI EN 302 636-5-1: "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol".
[8] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types",
November 1996.
NOTE: Available at https://tools.ietf.org/html/rfc2046.
[9] ETSI EN 302 663 (V1.2.1): "Intelligent Transport Systems (ITS); Access layer specification for
Intelligent Transport Systems operating in the 5 GHz frequency band".
[10] ETSI TS 103 613: "Intelligent Transport Systems (ITS); Access layer specification for Intelligent
Transport Systems using LTE Vehicle to everything communication in the 5,9 GHz frequency
band".
[11] IETF RFC 1738: "Uniform Resource Locators (URL)", December 1994.
NOTE: Available at https://www.ietf.org/rfc/rfc1738.txt.
ETSI
8 ETSI TS 103 152 V2.1.1 (2019-11)
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.
[i.1] ISO/TS 17419:2018: "Intelligent Transport Systems - Cooperative Systems - Classification and
management of ITS applications in a global context".
[i.2] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture".
[i.3] ETSI EN 302 636-3: " Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 3: Network Architecture".
[i.4] ETSI TS 102 723-11: "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 11:
Interface between networking and transport layer and facilities layer".
[i.5] ETSI TS 102 723-5: "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 5: Interface
between management entity and facilities layer".
[i.6] ETSI TS 101 539-1: "Intelligent Transport Systems (ITS); V2X Applications; Part 1: Road Hazard
Signalling (RHS) application requirements specification".
[i.7] ETSI TS 101 556-1: "Intelligent Transport Systems (ITS); Infrastructure to Vehicle
Communication; Electric Vehicle Charging Spot Notification Specification".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
event: object described by Multimedia Content Dissemination Message(s)
NOTE: E.g. road hazard, driving environment, traffic condition, or Point of Interest.
MCD protocol: facilities layer protocol to control the dissemination of multimedia data such as photos/pictures, video
clips, audio
Multimedia Content Dissemination (MCD): facilities layer function that operates the MCD protocol
Multimedia Content Dissemination Message (MCDM): one or more facilities layer PDUs that contain multimedia
content data
originator ITS-S: ITS-S that generates and transmits Multimedia Content Dissemination Messages
receiver ITS-S: ITS-S that receives and processes Multimedia Content Dissemination Messages
3.2 Symbols
For the purposes of the present document, the following symbols apply:
IF.Mng Interface between MCD basic service and ITS management entity
IF.N&T Interface between MCD basic service and ITS networking & transport layer
IF.SEC Interface between MCD basic service and ITS security entity
ETSI
9 ETSI TS 103 152 V2.1.1 (2019-11)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
API Application Program Interface
ASN.1 Abstract Syntax Notation 1
BTP Basic Transport Protocol
DE Data Element
DEN Decentralized Environmental Notification
DENM Decentralized Environmental Notification Message
DF Data Frame
FA-SAP Facilities/Applications Service Access Point
GN GeoNetworking
HMI Human Machine Interface
IANA Internet Assigned Numbers Authority
ISO International Organization for Standardization
ITS Intelligent Transportation System
ITS-S ITS Station
LDM Local Dynamic Map
MCD Multimedia Content Dissemination
MCDM Multimedia Content Dissemination Message
MF-SAP Management/Facilities Service Access Point
MTU Maximum Transmit Unit
MTU_AL Maximum Transmit Unit of Access Layer
NACK Negative ACKnowledgement
NF-SAP Networking & Transport/Facilities Service Access Point
OSI Open System Interconnection
PCI Protocol Control Information
PDU Protocol Data Unit
PER Packet Error Rate
POI Point Of Interest
RFC (IETF) Request For Comments
RT Repetition Timer
SAP Service Access Point
SF-SAP Security/Facilities Service Access Point
UTF Unicode (or Universal Coded Character Set) Transformation Format
V2X Vehicle-to-Everything
4 MCD basic service introduction
4.1 Background
Multimedia Content Dissemination Messages (MCDMs) contain multimedia content describing events for various
applications. MCDMs can be broadcasted to reach all users being in the coverage of the used communication
technology. They can also be broadcasted in geographical area. MCDMs can be targeted to a particular user or to a
community of users using multicast. Finally, MCDMs can be addressed to a particular user through an established peer
to peer session. MCDMs may incorporate several multimedia containers including pictures, video clips, audio and data.
They may constitute long messages requiring segmentation to ensure their complete consistent transfer respecting the
order of transmitted segments in spite of some possible losses. Received MCDMs need to be filtered according to their
use context and user preferences.
Multimedia Content Dissemination (MCD) is a facilities layer function which is mainly used by ITS applications to
control the dissemination of pictures, video clips, audio and data using ITS communication technologies. Applications
classes to be supported by MCD can be listed as follows:
• Road safety, e.g. signalling some obstacle on the road as specified in ETSI TS 101 539-1 [i.6] or some
dangerous traffic situations using pictures or video clips.
ETSI
10 ETSI TS 103 152 V2.1.1 (2019-11)
• Traffic management, e.g. providing pictures or videos of the current traffic situations.
• Mobility e.g. providing some multimedia description of POI availability, e.g. parking, electric vehicle charging
spots [i.7], rest areas, etc.
• National patrimony information, e.g. monuments, local specialties, arts, etc.
• Commercial information, e.g. products/services advertisement, special sales, open days, etc.
• Personal and Communities information, e.g. hitchhiking request, community concerted mobilities, etc.
The dissemination of MCDM among ITS-Ss is operated by the MCD protocol. Example processing procedures of an
ITS use case that is supported by the MCD protocol are as follows:
• Applications activate the MCD basic service either on user request or automatically when detecting a
particular situation.
• The application specifies the dissemination rules of the multimedia content which is provided at the same time.
• An MCDM is generated and transmitted according to the provided dissemination rules. In case of geo-
addressing, the MCDM can be relayed by one or more relevant network forwarder ITS-Ss.
• An ITS-S that receives an MCDM processes the contained information and provides it or not to the user
according to contextual constraints, e.g. driving state and preference criteria.
A general inter-layer and inter-ITS-Ss dataflow for the MCDM exchange is provided in Figure 1. The solid lines
illustrate the dataflow that is mandatory for all ITS applications supported by MCD basic service.
An MCDM may be forwarded by intermediate ITS-Ss in order to disseminate it from the originating ITS-S to the
receiver ITS-S, if the receiver ITS-S is not located in the direct communication range of the originating ITS-S. This
forwarding is realized by the ITS networking and transport layer.

Figure 1: General data flow for ITS-S application supported by MCD basic service
ETSI
11 ETSI TS 103 152 V2.1.1 (2019-11)
4.2 Services provided by the MCD basic service
The MCD basic service is a facilities layer entity that operates the MCD protocol. It provides services to entities at the
ITS applications layer. At the originator ITS-S, it triggers and maintains the transmission of MCDMs according to
dissemination rules as set by the ITS-S application. At the receiver ITS-S, the MCD basic service processes the received
MCDM and makes the content available for usage at ITS-S applications if relevant.
The MCD basic service uses the services provided by the protocol entities of the ITS networking and transport layer to
disseminate the MCDM. Dissemination rules are provided by the requesting ITS-S application. It may be:
• Broadcast.
• Geographical broadcast.
• Multicast, using a group address, e.g. community name, or a personal logical name.
• Peer to Peer.
An MCDM contains management information, and one or several multimedia containers being characterized in the
management field. Other information such as situation and/or location information may be added according to the
application purpose.
An MCDM can be repeated by the originating ITS-S when using broadcast and/or multicast in order to increase the
reception probability of at least one exemplary in spite of packet lost.
An MCDM can be split into several units by the MCD basic service when this service is not available at the network
and/or transport layer level, e.g. BTP/GeoNetworking. In such case, the MCD basic service needs to ensure the integrity
of received messages. If one unit is lost and it exists no possibility to recover it at the network and/or transport layer, the
whole message may be discarded by the MCD basic service of the receiver that detected the message integrity loss.
An MCDM can be associated to a DENM, e.g. "obstacle on the road" or "hazardous location". In such case the receiver
ITS-S application needs to ensure a consistent user interface.
The MCD basic service of the originator ITS-S shall construct the MCDM according to the application request.
An MCDM may contain several multimedia containers of different natures, e.g. pictures, video clips, audio, text.
5 MCD basic service functional specification
5.1 MCD basic service in the ITS architecture
The MCD basic service interfaces with ITS-S applications in order to receive the request for the MCDM dissemination
and to provide the received multimedia content to the ITS-S applications. Furthermore, the MCD basic service may
interact with other facilities layer entities, in particular the LDM which is a facilities layer database containing local
dynamic data elements. At the receiver ITS-S, the LDM may be updated with a received MCD and ITS-S applications
may retrieve information from the LDM database for further processing.
NOTE: The specification of the LDM is out of scope of the present document.
Figure 2 presents the MCD basic service in the ITS-S architecture defined in ETSI EN 302 665 [i.2] and ETSI
EN 302 636-3 [i.3] as well as its logical interfaces with other entities and layers.
ETSI
12 ETSI TS 103 152 V2.1.1 (2019-11)
Figure 2: MCD basic service and logical interface
5.2 MCD basic service functional architecture
The MCD basic service shall provide the following sub-functions:
• Encode MCDM:
- This sub-function constructs an MCDM according to the format specified in Annex A of the present
document.
• Decode MCDM:
- This sub-function decodes the received MCDM.
• MCDM transmission management:
- This sub-function implements the MCD protocol operation of the originator ITS-S as specified in
clause 8.2, including in particular the generation of a new MCD as requested by the ITS-S application at
the originator ITS-S.
- Optionally, this sub-function segments the MCDM into multiple PDUs according to rules defined by the
selected access technology, e.g. maximum packet size at the physical layer. This function is needed when
the segmentation is not covered by a lower communication layer or it does not intend to rely on the lower
layer for the segmentation.
• MCDM reception management:
- This sub-function implements the MCD protocol operation of the receiver ITS-S as specified in
clause 8.3, in particular:
 The optional reassembly of received MCD units if not achieved by a lower communication layer.
 The optional verification of received message integrity after reassembly and discarding of
incomplete messages.
 Elimination of repeated messages after the reception of a complete message.
 The provisioning of received messages to relevant ITS-S applications and/or to other facilities layer
entities of the receiver ITS-S.
ETSI
13 ETSI TS 103 152 V2.1.1 (2019-11)
Figure 3 illustrates sub-functions and interfaces of the MCD basic service in a component diagram.
Figure 3: MCD basic service component diagram
5.3 Interfaces of the MCD basic service
5.3.1 Interface to the ITS-S application layer
An ITS-S application is a function of the ITS application layer that implements the application logic of one or more use
cases. It initiates the generation of MCDMs as introduced in clause 4.2, according to some pre-defined conditions
provided by the applications.
The MCD basic service provides the interfaces to the ITS-S applications for the MCD protocol operation of the
originator ITS-S and receiver ITS-S. As illustrated in Figure 3, the interface IF.MCD.1 is for the MCDM transmission.
At the originator ITS-S, the ITS-S application sends a request to the MCD basic service to start the MCDM
transmission. This request may be acknowledged by the MCD basic service according to the dissemination mode being
used. The interface IF.MCD.2 is for the MCDM reception.
The generic data passed via the IF.MCD.1 between the MCD basic service and ITS applications shall be as specified in
Table 1.
Table 1: Data passed via IF.MCD.1
Category Data Data Requirement Remarks
Data passed from Information contained in As specified in Annex A and
application to the MCD basic the management clause B.14.
service container
Information contained in As specified in Annex A and Optional
the situation clause B.27.
container
Information contained in As specified in Annex A and Optional
the location clause B.13.
container
Information contained in As specified in Annex A and Optional
the application clause B.3.
container
Information contained in As specified in Annex A and Optional
the multimedia clause B.20.
container
Repetition interval Repetition interval between two Optional
consecutive transmissions of the (see note 2)
same MCDM in units of milliseconds.
Maximum repetition time Duration of the MCDM repetition in Optional
units of milliseconds. (see note 2)
ETSI
14 ETSI TS 103 152 V2.1.1 (2019-11)
Category data Data Requirement Remarks
Dissemination mode One of the following modes:

• General broadcast
• Geographical broadcast
• Multicast
• Peer to Peer
Destination area Destination area for MCDM Required if
dissemination as specified in ETSI geographically
EN 302 931 [2]. broadcasted
Logical address A personal or community logical Required if
name. multicasted
IPv6 address The IPv6 address of the Required if peer-to-
communication peer. peer
ACK timeout Value of the timer being triggered for Required if peer-to-
the reception of an peer
acknowledgement from peer.
Traffic class GN traffic class as defined in ETSI
EN 302 636-4-1 [6] if
GeoNetworking/BTP is used.
Data returned from the MCD actionID or other As specified in Annex A and
basic service to the application identifier clause B.2
requesting application (see note 1) The MCD basic service returns the
actionID or other applicable identifier
created by the MCD basic service to
the requesting application, in case
the request was successfully
handled.
Failure notification The MCD basic service returns a Optional
failure notification to the requesting (see note 3)
application under the conditions as
specified in clause 8.
NOTE 1: An applicable identifier is associated to the actionID as created by the MCD basic service, it may be used for
the interaction between the ITS-S application and DEN basic service.
NOTE 2: Applicable if the application requests the MCDM repetition.
NOTE 3: Applicable as specified in clause 8.
NOTE 4: Data format is up to implementation and it is possible to exchange additional information depending on the
implementation.
The generic data passed via the IF.MCD.2 from the MCD basic service are identified in Table 2.
Table 2: Data passed via IF.MCD.2
Category Data Data Requirement Remarks
Data passed from MCD basic Received MCDM In whole or in part as specified in Optional (see note 1)
service to application Annex A
NOTE 1: Applicable if ITS-S application of the receiving ITS-S requests the content of received MCDM.
NOTE 2: Data format is up to implementation.

NOTE: The interface to the ITS application layer may be implemented as API and data are exchanged between
the MCD basic service and ITS applications via this API. In another possible implementation, the
interface to the application layer may be implemented as FA-SAP. Specifications of the FA-SAP and the
corresponding protocols and APIs are out of scope of the present document.
5.3.2 Interface to the ITS-S network and transport layer
5.3.2.1 General requirements
The MCD basic service exchanges information with the ITS networking and transport layer via the interface IF.N&T.
The interface IF.N&T may be realized as NF-SAP as defined in ETSI TS 102 723-11 [i.4].
ETSI
15 ETSI TS 103 152 V2.1.1 (2019-11)
For ITS-S applications identified in the present document, several dissemination modes are possible:
• Broadcast.
• Geographical broadcast.
• Multicast.
• Peer to Peer.
At the originator ITS-S, the MCD basic service delivers the MCDM or the segmented units to the ITS-S networking and
transport layer. The MCD basic service shall provide at least the protocol control information (PCI) specified in Table 3
to the ITS-S networking and transport layer. At the receiver ITS-S, if this ITS-S is considered as one destination of the
MCDM dissemination, the ITS-S networking and transport layer shall pass the received MCDM to the MCD basic
service.
Table 3: Data exchanged between the MCD basic service and the ITS-S networking
and transport layer
Category Data Data Requirement Remarks
Data passed from the MCD MCDM As specified in Annex A.
basic service to the ITS-S
Destination area Destination area for MCDM Required if
networking and transport dissemination as specified in ETSI geographically
layer
EN 302 931 [2]. broadcasted
Repetition interval Repetition interval between two
Optional
consecutive transmissions of the (see note 1)
same MCDM in units of milliseconds.
Maximum repetition time Duration of the MCDM repetition in Optional
units of milliseconds. (see note 1)
Data passed from the ITS-S Received MCDM As specified in Annex A. Optional (see note 2)
networking and transport
layer to the MCD basic
service
NOTE 1: Applicable if the ITS-S application requests the MCDM repetition by the ITS networking & transport layer. The
repetition may also be performed by the MCD basic service at the facility layer.
NOTE 2: Applicable of the receiving ITS-S is considered by the ITS networking & transport layer as inside the
destination area.
NOTE 3: Data format is up to implementation.

The network and transport protocol that may be used depending on the dissemination mode is as defined in ETSI
EN 302 636-4-1 [6] and ETSI EN 302 636-5-1 [7].
5.3.2.2 Interface to the BTP over GeoNetworking stack
The GeoNetworking/BTP protocol stack is adapted to the two dissemination modes:
• Broadcast
• Geographical Broadcast
Data being passed between the MCD basic service and the GeoNetworking/BTP stack shall be as specified in Table 3
and in Table 4.
Table 4: Data passed from the MCD basic service to the BTP stack
Category Data Requirement (see note 3) Remarks
Data passed from BTP type BTP header type B (ETSI EN 302 636-5-1 [7], Optional (see note 1)
the MCD basic clause 7.3).
service to the ITS-
Destination port As defined in ETSI TS 103 248 [5] (see note 2). Optional (see note 1)
S networking and Destination port info As specified in ETSI EN 302 636-5-1 [7]. Optional (see note 1)
transport layer
GN Packet transport GeoNetworking GeoBroadcast protocol. Optional (see note 1)
type
GN Destination Specified as Destination are in Table 3.
address
ETSI
16 ETSI TS 103 152 V2.1.1 (2019-11)
Data Requirement (see note 3) Remarks
GN communication As defined in ETSI EN 302 636-4-1 [6]. Optional (see note 1)
profile
GN security profile SECURED or UNSECURED. Optional (see note 1)
GN Traffic class As defined in ETSI EN 302 636-4-1 [6].
GN Maximum packet Shall not exceed validityDuration. Optional (see note 1)
lifetime
GN Hoplimit The number of hops a packet is allowed to have in Optional (see note 1)
the network.
Length Length of the MCDM.
NOTE 1: Applicable if the value is not provided or different from
...