SIST EN 302 895 V1.1.1:2014

SLOVENSKI STANDARD
SIST EN 302 895 V1.1.1:2014
01-november-2014

,QWHOLJHQWQLWUDQVSRUWQLVLVWHPL.RPXQLNDFLMDPHGYR]LOL2VQRYQLQDERUDSOLNDFLM

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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 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 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

If you find errors in the present document, please send your comment to one of the following services:

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

The content of the PDF version shall not be modified without the written authorization of ETSI.

DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.

3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

Intellectual Property Rights ................................................................................................................................ 5

Foreword ............................................................................................................................................................. 5

Modal verbs terminology .................................................................................................................................... 5

Introduction ........................................................................................................................................................ 5

1 Scope ........................................................................................................................................................ 7

2 References ................................................................................................................................................ 7

2.1 Normative references ......................................................................................................................................... 7

2.2 Informative references ........................................................................................................................................ 7

3 Definitions and abbreviations ................................................................................................................... 8

3.1 Definitions .......................................................................................................................................................... 8

3.2 Abbreviations ..................................................................................................................................................... 8

4 General description of a LDM .................................................................................................................. 9

4.1 Functionality provided by the LDM ................................................................................................................... 9

5 LDM functional specification .................................................................................................................. 9

5.1 LDM requirements ............................................................................................................................................. 9

5.1.1 LDM functional requirements....................................................................................................................... 9

5.1.2 LDM other requirements ............................................................................................................................ 10

5.2 The LDM within the ITS-S communication architecture ................................................................................. 10

5.3 LDM functional architecture ............................................................................................................................ 11

5.3.1 Function FN.LDM.1 - LDM Service .......................................................................................................... 11

5.3.2 Function FN.LDM.2 - LDM Maintenance .................................................................................................. 12

5.4 Interfaces of the LDM ...................................................................................................................................... 12

5.4.1 Interface IF.LDM.1 - management layer .................................................................................................... 12

5.4.2 Interface IF.LDM.2 - security layer ............................................................................................................ 13

5.4.3 Interface IF.LDM.3 - LDM Data Providers ................................................................................................ 13

5.4.4 Interface IF.LDM.4 - LDM Data Consumers ............................................................................................. 13

6 LDM Interfaces ...................................................................................................................................... 14

6.1 Interface IF.LDM.2 to the security layer .......................................................................................................... 14

6.1.1 Authorization .............................................................................................................................................. 14

6.1.1.1 Authorize messages ............................................................................................................................... 14

6.1.2 Revocation .................................................................................................................................................. 15

6.1.2.1 RevokeAuthorization messages ............................................................................................................ 15

6.2 Interface IF.LDM.3 to LDM Data Providers .................................................................................................... 16

6.2.1 Registration ................................................................................................................................................. 16

6.2.1.1 RegisterDataProvider messages ............................................................................................................ 16

6.2.2 Deregistration ............................................................................................................................................. 17

6.2.2.1 DeregisterDataProvider messages ......................................................................................................... 17

6.2.2.2 RevokeDataProviderRegistration message ........................................................................................... 17

6.2.3 Maintenance of Provider data ..................................................................................................................... 18

6.2.3.1 AddProviderdata messages ................................................................................................................... 18

6.2.3.2 UpdateProviderdata messages ............................................................................................................... 19

6.2.3.3 DeleteProviderdata messages ................................................................................................................ 19

6.3 Interface IF.LDM.4 to LDM Data Consumers ................................................................................................. 20

6.3.1 Registration ................................................................................................................................................. 20

6.3.1.1 RegisterDataConsumer messages ......................................................................................................... 20

6.3.2 Deregistration ............................................................................................................................................. 21

6.3.2.1 DeregisterDataConsumer messages ...................................................................................................... 21

6.3.2.2 RevokeDataConsumerRegistration message ......................................................................................... 22

6.3.3 Data Request ............................................................................................................................................... 22

6.3.3.1 RequestDataobjects messages ............................................................................................................... 22

6.3.4 Subscription ................................................................................................................................................ 23

6.3.4.1 SubscribeDataConsumer messages ....................................................................................................... 23

6.3.5 Cancel subscription ..................................................................................................................................... 25

6.3.5.1 UnsubscribeDataConsumer messages ................................................................................................... 25

Annex A (normative): Data request filtering ..................................................................................... 26

A.1 Minimal syntax of data request filtering ................................................................................................ 26

A.1.1 Filter ................................................................................................................................................................. 26

A.1.2 Filter Statement ................................................................................................................................................ 26

A.1.2.1 Comparison Operator .................................................................................................................................. 27

A.1.2.2 Reference Value .......................................................................................................................................... 27

A.1.3 Logical operators for combining Filter Statements .......................................................................................... 27

A.2 Ordering Data Request Results .............................................................................................................. 28

Annex B (normative): ITS LDM Interface messages specified in ASN.1 ....................................... 29

Annex C (informative): Bibliography ................................................................................................... 35

History .............................................................................................................................................................. 36

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

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

This European Standard (EN) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS).

In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "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

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

In cooperative Intelligent Transport Systems (ITS), the Local Dynamic Map (LDM) is a key facility supporting various

ITS applications by maintaining the information on objects influencing or being part of ITS. The Local Dynamic Map

therefore is relevant to the development of technical standards and specifications in order to ensure deployment and

interoperability of cooperative systems and services described in the EC's ICT Standardization Work Programme [i.7].

The LDM is a facility within the ITS station facilities layer as defined in the ITS communication architecture given in

EN 302 665 [i.1]. Cooperative Awareness Messages (CAMs) as defined in EN 302 637-2 [4] and Decentralized

Environmental Notification Messages (DENMs) as defined in EN 302 637-3 [5] are important sources of data for the

Moreover the LDM will support the Basic Set of Applications (BSA) outlined in TS 102 637-1 [i.2] by providing

plausible authorized, area related information in a time relevant manner. The BSA provides the application specific

The present document defines functional behaviour associated with a Local Dynamic Map (LDM) for usage in an ITS

station unit (ITS-SU). It specifies functions and interfaces supported by a LDM. These functions and interfaces provide

secure access to the LDM to manage LDM data objects stored in a LDM. It defines LDM data objects for safety-related

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 documents which are not found to be publicly available in the expected location might be found at

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

The following referenced documents are necessary for the application of the present document.

[1] ETSI TS 102 860 (V1.1.1) (2011-05): "Intelligent Transport Systems (ITS); Classification and

[2] ISO/IEC 8824-1:2008: "Information technology - Abstract Syntax Notation One (ASN.1):

[3] ETSI TS 102 894-2: "Intelligent Transport Systems (ITS); Users and applications requirements;

[4] ETSI EN 302 637-2 (V1.3.1) (2014-09): "Intelligent Transport Systems (ITS); Vehicular

Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic

[5] ETSI EN 302 637-3 (V1.2.1) (2014-09): "Intelligent Transport Systems (ITS); Vehicular

Communications; Basic Set of Applications; Part 3: Specifications of Decentralized

The following referenced documents are not necessary for the application of the present document but they assist the

[i.1] ETSI EN 302 665 (V1.1.1) (2010-09): "Intelligent Transport Systems (ITS); Communications

[i.2] ETSI TS 102 637-1 (V1.1.1) (2010-09): "Intelligent Transport Systems (ITS); Vehicular

[i.3] ETSI TS 101 539-1 (V1.1.1) (2013-08): "Intelligent Transport Systems (ITS); V2X Applications;

[i.4] ETSI TS 102 723-5 (V1.1.1) (2012-11): "Intelligent Transport Systems (ITS); OSI cross-layer

[i.5] ETSI TR 102 863 (V1.1.1) (2011-06): "Intelligent Transport Systems (ITS); Vehicular

Communications; Basic Set of Applications; Local Dynamic Map (LDM); Rationale for and

[i.6] ISO/IEC 19505-2:2012(E): "Information technology - Object Management Group Unified

[i.7] European Commission: "2010-2013 ICT Standardisation Work Programme for industrial

NOTE: Available at: http://ec.europa.eu/enterprise/sectors/ict/files/ict-policies/2010-

For the purposes of the present document, the following terms and definitions apply:

area of interest: geographical area specified by data consumer limiting the LDM to satisfying the data consumers'

LDM area of maintenance: geographical area specified by the LDM for LDM maintenance

LDM data consumer: facility or an application that is authorized to request data from the LDM

LDM data object: object with attributes that can be accessed by the LDM Interfaces

LDM data object identifier: unique identifier within the LDM for a LDM Data Object added by a LDM Data Provider

LDM data provider: facility or an application that is authorized to provide the data to the LDM

Local Dynamic Map (LDM): facilities layer data store for storing LDM Data Objects that are timestamped and

A Local Dynamic Map (LDM) is a facility in cooperative Intelligent Transport Systems (ITS). It supports ITS

applications by maintaining information on objects influencing or influenced by road traffic. ITS applications require

information on moving objects such as vehicles nearby or on stationary objects such as traffic road signs. Information

The LDM is a conceptual data store located within an ITS-S as outlined in EN 302 665 [i.1] containing information

which is relevant to the operation of ITS applications and related road safety and traffic efficiency. Data can be received

from a range of different sources such as vehicles, infrastructure units, traffic centres, personal ITS stations, and

on-board sensors and applications. The LDM offers mechanisms to grant secure access to the data that it holds. For

example, the LDM can provide information on the surrounding vehicles and Road Side Units to any authorized

The information stored in the LDM can be accessed in the form of objects called LDM Data Objects. LDM Data

Objects are provided from for example basic services for ITS Message Sets such as those defined in EN 302 637-2 [4]

and EN 302 637-3 [5]. LDM Data Objects can be composed of sub objects, similar to the hierarchical structure of data

frames in messages, and the objects contain attributes representing data elements from TS 102 894-2 [3]. Information

on a vehicle or road side ITS-S for example is provided by a cooperative awareness basic service as defined in

EN 302 637-2 [4] and is accessed from the LDM as a LDM Data Object with sub-objects representing the information

from the CAM Basic Container. Information on an event for example is provided by a distributed environmental

notification basic service as defined in EN 302 637-3 [5] and is accessed from the LDM as a LDM Data Object with

The LDM can also store LDM Data Objects from applications and other facilities. For example, the LDM may maintain

The LDM does not modify the data provided by LDM Data Providers. No permanent, static information is required to

The basic functionality of the LDM is to provide a repository of information for facilities and applications. Facilities

such as the CA and DEN basic services can store information into the LDM. Applications can retrieve information from

and store information into the LDM. Additional functionality of the LDM includes:

• Registration/Deregistration of facilities and applications as LDM Data Providers/sinks to the LDM via the

• Information retention by applying rules, e.g. based on time and/or location (see clause 5.3.2).

A LDM may communicate with other entities within the ITS-S architecture outlined in EN 302 665 [i.1] in order to:

• receive incoming information such as decoded CAMs in accordance with EN 302 637-2 [4] and DENMs in

• store and protect information according to constraints of time and LDM Area of Maintenance;

• provide a mechanism for facilities and applications to register and deregister as LDM Data Providers;

• provide a mechanism for applications to register and deregister as LDM Data Consumers;

In addition to the functional requirements listed in clause 5.1.1, a LDM may be constrained by a range of other

requirements such as reliability (system maturity, fault tolerance and restorability) and scalability. However, within

communications systems such requirements are normally considered to be related to procurement and, consequently,

The LDM collects, qualifies (ensures that it is valid and from an authorized source) and stores data received from other

ITS-Ss. The LDM may also collect, qualify and store information from other sources such as traffic information

As shown in Figure 1, the LDM receives data from other ITS-Ss through a common interface which is available to all

message services such as CA and DEN within the ITS-S Facilities layer. Information is exchanged with other services

or applications by invoking functions located at the FA-SAP as outlined in EN 302 665 [i.1]. Security and management

permissions are provided by functions which are located at the SF-SAP and the MF-SAP respectively.

The rationale for and guidance on standardization of the LDM outlined in TR 102 863 [i.5] specify two main

components of the LDM; the LDM Maintenance component and the LDM Service component (see clause 5.3.1).

Figure 2 shows these two components of the LDM and its main interfaces in a Unified Modelling Language (UML)

component diagram in accordance with ISO/IEC 19505-2 [i.6]. The interfaces are separated into those required by the

LDM (IF.LDM.1 and IF.LDM.2) and those exposed to other facilities and applications (IF.LDM.3 and IF.LDM.4).

The LDM shall provide the functions defined in Table 1 and illustrated in Figure 2.

FN.LDM.1 The LDM Service component (see clause 5.3.1) is responsible for providing functionalities to

authorized LDM Data Providers for LDM data manipulation (such as adding new data, modifying

existing data, delete existing data), direct access to data (query data) and a publish/subscribe

mechanism for data access by LDM Data Consumers. It also provides registration and deregistration

FN.LDM.2 The LDM Maintenance component (see clause 5.3.2) is responsible for storing and maintaining the

data and its integrity as well as for the garbage collection of persistent data held within the LDM.

The LDM is connected to authorized LDM Data Providers and LDM Data Consumers. LDM Data Providers provide