ETSI TS 102 894-1 V1.1.1 (2013-08)

Intelligent Transport Systems (ITS); Users and applications requirements; Part 1: Facility layer structure, functional requirements and specifications

DTS/ITS-0010004

General Information

• Status: Published
• Publication Date: 31-Jul-2013
• Technical Committee: ITS WG1 - Application Requirements and Services
• Current Stage: 12 - Completion
• Due Date: 12-Aug-2013
• Completion Date: 01-Aug-2013
• Mandate: M/453

Standards Content (Sample)

Technical Specification
Intelligent Transport Systems (ITS);
Users and applications requirements;
Part 1: Facility layer structure, functional requirements
and specifications
2 ETSI TS 102 894-1 V1.1.1 (2013-08)

Reference
DTS/ITS-0010004
Keywords
application, facility, ITS
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
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the 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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2013.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 894-1 V1.1.1 (2013-08)
Contents
Intellectual Property Rights . 5
Foreword . 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 ITS application overview . 9
4.1 ITS architecture and ITS stations . 10
4.2 Application layer overview . 11
5 Facilities layer functional architecture . 11
5.1 ITS-S external gateways . 11
5.1.1 Vehicle ITS-S gateway to in vehicle network . 12
5.1.2 Road side ITS-S gateway to central ITS-Ss . 12
5.1.3 Road side ITS-S or central ITS-S gateway to road equipment . 13
5.1.4 ITS-S gateway to back end systems . 14
5.1.5 Personal ITS-S gateway to vehicle ITS station . 14
5.2 Facilities layer functional architecture . 14
5.3 List of facilities . 15
6 Common facilities functional requirements . 17
6.1 Management facilities functional requirements. 18
6.1.1 CF001: Traffic class management . 18
6.1.2 CF002: ITS-S ID management . 19
6.1.3 CF003: AID Management . 20
6.1.4 CF004: Security access . 21
6.2 Application support facilities functional requirements . 22
6.2.1 CF005: HMI support . 22
6.2.3 CF006: Time service . 23
6.2.4 CF007: Application/facilities status management . 24
6.2.5 CF008: Service announcement message (SAM) processing . 25
6.3 Information support facilities functional requirements . 26
6.3.1 CF009: Station type/capabilities . 26
6.3.2 CF010: ITS-S positioning service . 27
6.3.3 CF011: Location referencing . 29
6.3.4 CF012: Common data dictionary . 30
6.3.5 CF013: Data presentation . 31
6.4 Communication support facilities functional requirements . 32
6.4.1 CF014: Addressing mode . 32
6.4.2 CF015: Congestion control . 33
7 Domain facilities functional requirements . 35
7.1 Application support facilities functional requirements . 35
7.1.1 DF001: DEN basic service . 35
7.1.2 DF002: CA basic service . 37
7.1.3 DF003: Extended vehicle floating car data (EFCD) . 38
7.1.4 DF004: Billing and payment . 39
7.1.5 DF005: Traffic light phase and timing basic service (SPAT basic service) . 40
7.1.6 DF006: Road topology basic service (TOPO basic service) . 42
7.1.7 DF007: In vehicle signage basic service (IVS basic service) . 44
ETSI
4 ETSI TS 102 894-1 V1.1.1 (2013-08)
7.1.8 DF008: Community services user management . 45
7.2 Information support facilities functional requirements . 47
7.2.1 DF009: Local dynamic map (LDM) . 47
7.2.2 DF010: RSU management and communication . 48
7.2.3 DF011: Map service. 49
7.3 Communication support facilities functional requirements . 50
7.3.1 DF012: Session support . 50
7.3.2 DF013: Web service support . 51
7.3.3 DF014: Messaging support . 51
7.3.4 DF015: E2E (end to end) Geocasting . 52
8 Conformance . 54
Annex A (informative): Bibliography . 55
History . 56

ETSI
5 ETSI TS 102 894-1 V1.1.1 (2013-08)
Intellectual Property Rights
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 (http://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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS).
The present document is part 1 of a multi-part deliverable covering the ITS applications and facilities layer, as identified
below:
Part 1: "Facility layer structure, functional requirements and specifications";
Part 2: "Applications and facilities layer common data dictionary".
The present document has been prepared by considering feedback from the Car-to-Car Communication Consortium
(C2C-CC). The specifications of facilities layer structure and facilities layer entities are based on experience gathered
from various European Projects such as DRIVE C2X, CVIS, SCORE@F and simTD.
Introduction
The present document provides architecture and functional specifications for the facilities layer of the ITS station
(ITS-S) as defined in [1]. It is based on the previous work that has been realized within ETSI TC ITS WG1 related to
the Basic Set of Applications (BSA) [i.1].
ITS applications are distributed among multiple ITS-Ss in order to share information using wireless communications.
ITS applications provide a large diversity of customer's services. BSA has been defined by ETSI TC as a set of ITS
applications that can be deployed reasonably within a three-year time frame after its standardization completion.
Furthermore, ETSI TC ITS developed and defined functional requirements for BSA [i.2].
This previous work will allow ETSI TC ITS to identify a set of facilities in the facilities layer that are required to satisfy
some common functional requirements and operational requirements of BSA. The facilities specified in the present
document are minimum functionalities, services and data that are needed to ensure the interoperability and basic
operation of ITS applications. The architecture of the facilities layer is intended to be an open architecture, which is
available for ITS application developers to incorporate advanced proprietary facilities and different kinds of access
networks such as ITS G5 or cellular networks.
The following projects and organizations had been consulted during the preparation of the present document:
• Car to Car Communication Consortium (http://www.car-to-car.org)
• COMeSafety (http://www.comesafety.org)
• PREDRIVE C2X (www.pre-drive-c2x.eu)
• DRIVE C2X (http://www.drive-c2x.eu)
• CVIS (www.cvisproject.org)
• simTD (www.simtd.de)
ETSI
6 ETSI TS 102 894-1 V1.1.1 (2013-08)
• CoVel (www.covel-project.eu)
• SCORE@F (http://www.scoref.fr/)
ETSI
7 ETSI TS 102 894-1 V1.1.1 (2013-08)
1 Scope
The present document defines the functional architecture for the facilities layer of the ITS station as defined in [1] and
provides functional requirements and specifications for main identified facilities.
The identified facilities are required to support BSA as defined in [i.1]. Other proprietary facilities might be required to
be included in the facilities layer for BSA and other ITS applications. Such proprietary facilities are not defined in the
present document.
2 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
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://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.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".
[2] ETSI EN 302 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set
of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[3] 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.2 Informative references
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 TR 102 638 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications;
Basic Set of Applications; Definitions".
[i.2] ETSI TS 102 637-1 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications;
Basic Set of Applications; Part 1: Functional Requirements".
[i.3] CEN/TS 16157-1: "Intelligent transport systems - DATEX II data exchange specifications for
traffic management and information - Part 1: Context and framework".
[i.4] ETSI TS 102 890-2: "Intelligent Transport Systems (ITS); Facilities layer function; Part 2:
Services announcement specification".
[i.5] ETSI TR 102 893 (V1.1.2): "Intelligent Transport Systems (ITS); Security; Threat, Vulnerability
and Risk Analysis (TVRA)".
[i.6] ETSI TS 103 084: Intelligent Transport Systems (ITS); Vehicular Communications;
GeoMessaging Enabler".
ETSI
8 ETSI TS 102 894-1 V1.1.1 (2013-08)
[i.7] ETSI EN 302 636-4-1: "Intelligent Transport System (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".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] and the following apply:
application support: sub set of facilities, providing support elements for ITS applications
backend systems: system that includes middleware in the generic domain, providing back end support and functions
for BSA ITS use case
basic set of applications: group of applications, supported by vehicular communication system
NOTE: BSA definition is provided in [i.1]
CA basic service: facility at the facilities layer to support ITS applications, CAM management and CAM dissemination
communication support: sub set of facilities, providing support for communications
cooperative awareness message: ITS facilities layer PDU providing ITS-S information
decentralized environmental notification message: ITS facilities layer PDU providing event information
DEN basic service: facility at the facilities layer to support ITS applications, DENM management and DENM
dissemination
facility: functionalities, services or data provided by the facilities layer
information support: sub set of facilities, providing support for data management
ITS application: component of ITS applications layer
ITS use cases: procedure of executing an ITS application
LDM: local georeferenced database
message: facilities layer or application layer PDU
NOTE: Examples are cooperative awareness message and decentralized environmental notification message.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AID Application identifier
ALERT-C Advice and problem Location for European Road Traffic
API Application Programming Interface
ASN.1 Abstract Syntax Notation One
BSA Basic Set of Application
C2C-CC Car to Car Communication Consortium
CA Cooperative Awareness
CAM Cooperative Awareness Message
CF Common Facility
DCC Decentralized Congestion Control
DEN Decentralized Environmental Notification
DENM Decentralized Environmental Notification Message
DF Domain Facility
ETSI
9 ETSI TS 102 894-1 V1.1.1 (2013-08)
DGPS Differential Global Positioning System
DIASER DIAlogue Standard for traffic Regulation Equipment
E2E End to end
EFCD Extended vehicle floating car data
EGNOS European Geostationary Navigation Overlay Service
FA-SAP Facilities Application SAP
GNSS Global Navigation Satellite System
HMI Human Machine Interface
HTTP Hypertext Transfer Protocol
ISO International Organization for Standardization
ITS Intelligent Transport System
ITS-S ITS station
IVS In vehicle signage
LDM Local Dynamic Map
MF-SAP Management Facilities SAP
N&T Networking and transport layer
NF-SAP Networking and transport Facilities SAP
OSI Open Systems Interconnection
PDU Protocol Data Unit
PER Packed Encoding Rules
QoS Quality of Service
RSU Road side unit
SAM Service Announcement message
SAP Service Access Point
SF-SAP Security Facilities SAP
SOAP Simple Object Access Protocol
SPAT Signal Phase And Timing
TAI International Atomic Time
TMC Traffic Message Channel
TMC-LOC TMC Location Referencing
TOPO Road topology message
TPEG Transport Protocol Experts Group
TPEG-LOC TPEG Location Referencing
TVRA Vulnerability and Risk Analysis
VMS Variable Message Sign
XER XML encoding rules
XML Extensible Markup Language
4 ITS application overview
The overall ITS environment comprises ITS stations (ITS-S) that may communicate directly as follows:
• From Vehicle to Vehicle, via ad-hoc (or cellular) communication or based on Infrastructure involvement;
• From Vehicle to Infrastructure; and
• From Infrastructure to Vehicle.
ITS-Ss may communicate with each other through a local wireless access point (e.g. ITS G5 based) or a wireless wide
area network (e.g. a cellular network).
ETSI
10 ETSI TS 102 894-1 V1.1.1 (2013-08)
This is shown in simplified form in figure 4.1. The dotted lines represent the logical connections between ITS-Ss.

Figure 4.1: Simplified view of ITS environment
4.1 ITS architecture and ITS stations
Four ITS-S types are defined in [1], namely:
• Central ITS-S: A central ITS-S provides centralized ITS applications. A central ITS-S may play the role of
traffic operator, road operator, services provider or content provider. Furthermore, a central ITS-S may require
further connection with backend systems via e.g. Internet. For deployment and performances needs, specific
instances of central ITS-S may contain grouping of Applications or Facilities.
• Road side ITS-S: A road side ITS-S provides ITS applications from the road side. A road side ITS-S may
provide ITS applications independently or cooperatively with central ITS-S or other road side ITS-Ss. For
deployment and performances needs, specific instances of road side ITS-S may contain grouping of
Applications or Facilities.
• Vehicle ITS-S: A vehicle ITS-S provides ITS applications to vehicle drivers and/or passengers. It may require
an interface for accessing in-vehicle data from the in-vehicle network or in vehicle system. For deployment
and performances needs, specific instances of vehicle ITS-S may contain grouping of Applications or
Facilities.
• Personal ITS-S: A personal ITS-S provides ITS applications to personal and nomadic devices. For
deployment and performances needs, specific instances of personal ITS-S may contain grouping of
Applications or Facilities.
ETSI
11 ETSI TS 102 894-1 V1.1.1 (2013-08)
A common reference communication architecture for all ITS stations is defined in [1] and as illustrated in figure 4.2.
This architecture is an extension of the ISO 7-layer OSI model.
The present document defines the functional architecture of the facilities layer.

Figure 4.2: ITS station reference architecture
4.2 Application layer overview
ITS applications are defined within the application layer. An ITS application makes use of the underlying facilities and
communication capacities provided by the ITS-S.
The applications layer provides ITS services. Three classes of applications have been defined in [i.1]: road safety,
traffic efficiency and other applications. Each application can be assigned to one of the three identified application
classes.
The Basic Set of Applications (BSA) are applications that are considered as deployable with reasonable efforts within
3 years' time scale after the complete standardization of the system. Each application regroups a set of use cases to
realize some user benefits, including societal benefits, mobility benefits or customer benefits. The complete list of the
BSA use cases and assigned applications are provided in [i.1].
The facilities layer is a middleware composed of multiple facilities. A facility is a component that provides functions,
information or services to ITS applications. It exchanges data with lower layers and with management and security
entities of the ITS-S as defined in [1].
The present document provides specifications of the facilities layer entities in support of the BSA. Further use cases are
expected to be added in the future.
5 Facilities layer functional architecture
5.1 ITS-S external gateways
In order to connect with external systems, an ITS-S may provide gateway functions for these external systems to
exchange information with the facilities layer of the ITS-S. For BSA, one or multiple gateway functions may need to be
developed in order to satisfy the application requirements.
ETSI
12 ETSI TS 102 894-1 V1.1.1 (2013-08)
5.1.1 Vehicle ITS-S gateway to in vehicle network
For a vehicle ITS-S, the facilities layer is connected to the in-vehicle network via an in-vehicle data gateway as
illustrated in figure 5.1. The facilities and applications of a vehicle ITS-S receive from this gateway the required
in-vehicle data in order to construct messages (e.g. CAM and DENM) and for the application usage.
The implementation of the in vehicle data gateway needs to adapt to the specifications of the in vehicle network which
may be proprietary to the industry. Therefore, the specifications of this gateway are out of the scope of the present
document.
Applications
Facilities
Networking
&Transport
Access
In vehicle systems
Figure 5.1: Vehicle ITS-S in-vehicle data gateway
5.1.2 Road side ITS-S gateway to central ITS-Ss
A roadside ITS-S is in general connected to a central ITS-S e.g. traffic management centre or road operator centre. In a
possible road side ITS-S deployment scenario, road side ITS-Ss are managed by a private road infrastructure
management network. Specific protocols for the traffic management, for the roadside equipment management and
operational management are applied within such road infrastructure network. A gateway function may be equipped at
the road side ITS-S in order to provide connections between message exchanges protocols (e.g. CAM, DENM) and
these infrastructure protocols. In Europe, DATEX II protocol [i.3] is a standardized protocol deployed for exchanges of
the traffic management information between traffic management centres and between traffic management centre and
road side equipment (e.g. Variable Message Sign System). In a possible implementation, a roadside ITS-S is connected
to road infrastructure network by a DATEX II gateway as illustrated in figure 5.2. A road side ITS-S may either receive
information from central ITS-S or send information to central ITS-S via this gateway.
The DATEX II gateway of a road side ITS-S may include several functions:
• Aggregation of the received messages from vehicle ITS-Ss (such as CAM and DENM) and transmit to traffic
management centre in DATEX II messages.
• Receive and filter traffic management information from traffic management center in DATEX II protocol, then
transmit to vehicle ITS-S in messages such as CAM or DENM.
ETSI
Security
Management
Gateway
DATEX II
13 ETSI TS 102 894-1 V1.1.1 (2013-08)
Detailed specifications of this gateway is out of the scope of the present document.

Figure 5.2: Roadside ITS-S gateway to road infrastructure network
5.1.3 Road side ITS-S or central ITS-S gateway to road equipment
An ITS applications may require data related to the traffic regulation (e.g. rail-road intersection, traffic light status,
speed limit), or require support from the road side detection capacities (e.g. road side sensors). This requires that road
side equipment exchanges information with central or roadside ITS-S. For example, as specified in [i.2] in the third part
intersection collision risk warning, a road side ITS-S equipped at the intersection may detect the traffic light violation of
a vehicle by dedicated road side sensors (e.g. intersection radar, camera), then this road side ITS-S triggers a DENM
and disseminates to other oncoming vehicles in order to reduce the risk of intersection collision.
A central or roadside ITS-S may obtain traffic regulation and road side sensor data via a specific gateway to the road
side equipment as presented in figure 5.3. National or international standards may already exist, e.g. DIASER a French
standard for information exchanges between traffic light controllers and traffic light equipment. These standards are to
be taken into account when developing this gateway interface, detailed specifications of this gateway is out of the scope
of the present document.
Road equipment
Applications
Facilities
Networking
&Transport
Access
Figure 5.3: Roadside ITS-S gateway to road equipment
ETSI
Security
Management
Gateway
Backend System
14 ETSI TS 102 894-1 V1.1.1 (2013-08)
5.1.4 ITS-S gateway to back end systems
An ITS-S (e.g. road side ITS-S or central ITS-S) may need to connect to a back end system via a generic networks such
as Internet. The back end systems provide required services, service support or service content to the ITS-S in order to
satisfy the requirements of the ITS applications. In a possible implementation, an ITS-S is connected to the back end
system by a gateway as illustrated in figure 5.4. Detailed specifications of this gateway are out of the scope of the
present document.
Figure 5.4: ITS-S gateway to back end system
5.1.5 Personal ITS-S gateway to vehicle ITS station
When a personal ITS-S is located in a vehicle, this personal ITS-S may be considered as a vehicle ITS-S under the
condition that the personal ITS-S satisfies some predefined requirements. In particular for a personal ITS-S to support
the road safety applications, a connection to the vehicle electronics may be required. The personal ITS-S is connected
securely with vehicle ITS-S via a gateway to the in vehicle network or with the vehicle ITS-S to receive the in vehicle
data.
Detailed specifications of this gateway are out of the scope of the present document.
5.2 Facilities layer functional architecture
The general functional architecture of the facilities layer is illustrated in figure 5.5. A set of facilities are identified in
order to support the BSA, these facilities can be classified into two categories as below:
• Common facilities: Common facilities provide basic core services to support the reliable operation of an
ITS-S and the interoperability of the BSA applications. Common facilities are common for all ITS-Ss and all
BSA applications. Examples of the common facilities are time service, positioning service.
Detailed specifications of the common facilities are provided in clause 6 of the present document.
• Domain facilities: Domain facilities provide services and functions for one or several specific BSA
applications such as DEN basic service for cooperative road hazard warning applications. Domain facilities are
common for one or several applications. One domain facility may become optional or not used for other
applications.
Detailed specifications of the domain facilities are provided in clause 7 of the present document.
Furthermore, according to the functionalities that a facility provides, a facility as identified in the present document can
be of one of the following types:
• Application support facility: A facility that provides common services and/or functionalities for BSA
execution. Examples of the application support facilities are CA basic service and DEN basic service.
ETSI
15 ETSI TS 102 894-1 V1.1.1 (2013-08)
• Information support facility: A facility that provides common data and database management functionalities
for BSA execution. Examples of the information support facilities are Local Dynamic Map (LDM) and map
data base.
• Communication support facility: A facility that provides services for communications and session
management. Examples of the communication support facilities are addressing mode, geocasting support and
session support.
• Management facility: A facility that is interconnected with management or with security entity of the ITS-S.
S
F
-
S
A
P
M
F
-
S
A
P
Figure 5.5: Facilities layer functional architecture
As represented in figure 5.5: four Service Access Points (SAP) are connected to the facilities layer:
• The FA-SAP (Facilities/Applications - Service Access Point): A SAP that enables the full duplex exchange of
data between the applications layer and the facilities layer.
• The SF-SAP (Security/Facilities - Service Access Point): A SAP that enables the full duplex exchange of data
between the facilities layer and the security. For example, the facility layer may request the security layer for
certification of transmitted messages and the authentication of received messages.
• The MF-SAP (Management/Facilities - Service Access Point): A SAP that enables the full duplex exchange of
data between the facilities layer and the management layer. For example, the management layer will
communicate to the facilities layer the applicable management policies to optimize the global system operation
of the ITS-S and a consistent cross layer operation.
• The NF-SAP (Network - Transport/Facilities - Service Access Point): A SAP that enables the full duplex
exchange of data between the facilities layer and the network - transport layer.
NOTE: The detailed specifications of the SAPs are out of the scope of the present document.
5.3 List of facilities
Based on BSA functional requirements as provided in [i.2], a set of facilities are identified. The common facilities are
listed in table 5.1, the domain facilities are listed in table 5.2. The present document provides functional descriptions for
each of the facilities listed in table 5.1 and table 5.2, as well as the interactions with other facilities or with other layers
of the ITS-S as defined in [1].
NOTE 1: The present document does not make judgement whether a facility needs to be standardized. Some
facilities may be proprietary and implemented depending to the development strategies of industries.
NOTE 2: The present document does not specify any implementation architecture of the ITS-S facilities layer. In
one possible implementation, a facility may be grouped with other facilities into one component, or may
be implemented into multiple components.
ETSI
16 ETSI TS 102 894-1 V1.1.1 (2013-08)
The list of the common facilities is given in table 5.1. Detailed functional specifications of each common facility are
provided in clause 6 of the present document.
Table 5.1: List of common facilities
Classification Identifier Facility name Short description
Management CF001 Traffic class management Manage assignment of traffic class value for the higher
layer messages.
CF002 ITS-S ID management Manage ITS-S identifiers used by the application and the
facilities layer.
CF003 AID management Manage the application ID used by the application and
the facilities layer.
CF004 Security access Deal with the data exchanged between the application
and facilities layer with the security entity.
Application CF005 HMI support Support the data exchanges between the applications
support and HMI devices.
CF006 Time service Provide time information and time synchronization
service within the ITS-S.
CF007 Application/facilities status Manage and monitor the functioning of active
management applications and facilities within the ITS-S and the
configuration.
CF008 SAM processing Support the service management of the management
layer for the transmission and receiving of the service
announcement message (SAM).
Information CF009 Station type/capabilities Manage the ITS-S type and capabilities information.
support
CF010 ITS-S positioning service Calculate the real time ITS-S position and provides the
information to the facilities and applications layers.
CF011 Location referencing Calculate the location referencing information and
provide the location referencing data to the
applications/facilities layer.
CF012 Common data dictionary Data dictionary for messages.
CF013 Data presentation Message encoding/decoding support.
Communication CF014 Addressing mode Select addressing mode for messages transmission
support CF015 Congestion control Facilities layer decentralized congestion control
functionalities.
ETSI
17 ETSI TS 102 894-1 V1.1.1 (2013-08)
The list of the domain facilities is given in table 5.2. Detailed functional specifications of each common facility are
provided in clause 7 of the present document.
Table 5.2: List of domain facilities
Classification Identifier Facility name Short description
Application DF001 DEN basic service Support the protocol processing of the Decentralized
support Environmental Notification Message.
DF002 CA basic service Support the protocol processing of the Cooperative
Awareness Message.
DF003 EFCD Aggregation of CAM/DENM data at the road side ITS-S
and provide to the central ITS-S.
DF004 Billing and payment Provide service access to billing and payment service
provider.
DF005 SPAT basic service Support the protocol processing of the Signal Phase and
Timing Message.
DF006 TOPO basic service Support the protocol processing of the Road Topology
Message.
DF007 IVS basic service Support the protocol processing of the In Vehicle
Signage Message.
DF008 Community service user Manage the user information of a service community.
management
Information DF009 Local dynamic map Local Dynamic Map database and management of the
support database.
DF010 RSU management and Manage the RSUs from the central ITS-S and
communication communication between the central ITS-S and road side
ITS.
DF011 Map service Provide map matching functionality.
Communication DF012 Session support Support session establishment, maintenance and
support closure.
DF013 Web service support High layer protocol for web connection, SOA application
protocol support.
DF014 Messaging support Manage ITS services messages based on message
priority and client services/use case requirements.
DF015 E2E Geocasting Deal with the disseminating of information to ITS
vehicular and personal ITS stations based on their
presence in a specified Geographical area.

6 Common facilities functional requirements
Common facilities are facilities that are required by the operation of the ITS-S and/or provide support for
communication interoperability. Moreover, certain common facilities provide cross layer information to the
management and the security entities as defined in [1], therefore, these common facilities are management facilities.
For the usage in the present document, each common facility is assigned with a unique number CF#, as illustrated in
table 5.1. For each facility, a set of sub function and interfaces are defined. Each function is denoted by an identifier
[CF#_F#] where CF# indicates the ID of the common facility; F# indicates the number of the function. Each interface is
also denoted by an identifier [CF#_IN#] where CF# indicates the ID of the common facility, IN# indicates the number
of the interface.
For illustration purpose, a block diagram is defined for each common facility. This block diagram summarizes the main
functionalities of the facility and logical connections with other facilities of the facilities layer and/or with other layers
of the ITS-S, illustrated as external components in the block diagram. For simplicity reason, any external component if
not referred as one of the facilities defined in the present document, the following external components are defined for
illustration:
• N&T: it corresponds to the ITS networking and transport layer as defined in [1].
• Management: it corresponds to the ITS management entity as defined in [1].
• Security: it corresponds to the ITS security entity as defined in [1].
• ITS application: it corresponds to the ITS application layer as defined in [1].
ETSI
18 ETSI TS 102 894-1 V1.1.1 (2013-08)
• Messages: it corresponds to any facility that manages the facilities layer or ITS application layer PDU, such as
CA basic service, DEN basic service, etc.
• Other external components as defined in corresponding facility.
6.1 Management facilities functional requirements
6.1.1 CF001: Traffic class management
This facility deals with assignment of a traffic class value to each message transmitted by the applications and facilities
layer of an ITS-S. The traffic class level is used by the management layer to select the appropriate communication
protocol and access technologies to be used for the message transmission. Furthermore, the traffic class may also be
used by the ITS networking and transport layer for the packet routing.
The assignment of the traffic class is based on predefined rules and conditions. The parameters being taken into account
for the assignment may be the message type, communication requirements, QoS requirements and the priority level of
the application. The traffic class management facility implements conditions and policies to assign traffic class level to
messages.
The definition of traffic class and the assignment policies may be updated if required. If updates are required, the update
information should be provided by an authorized entity of the application management, which may be implemented in
an external system or in another ITS-S.
The functional block diagram of the traffic class management common facility is illustrated in figure 6.1.

Figure 6.1: Block diagram: Traffic Class Management
The functional requirements of this common facility are presented in table 6.1:
Table 6.1: Functional requirements: Traffic Class Management
Functions Requirement
[CF001_F1]: This function shall assign traffic class level to messages by implementing conditions and policies.
[CF001_F2]: This function shall update the definition of the traffic class and the assignment policies if required by the
application management authorities.
This function is optional.
ETSI
19 ETSI TS 102 894-1 V1.1.1 (2013-08)
The interfaces of this common facility are presented in table 6.2:
Table 6.2: Interfaces: Traffic Class Management
Interface Related component Direction Information exchanged over the interface
[CF001_IN1] Application IN Data required for the traffic class assignment:
e.g. communication requirements.
[CF001_IN2] Message IN Data required for the traffic class assignment:
e.g. communication requirements, message type, QoS
requirements etc.
[CF001_IN3] Networking and OUT Traffic class
...