Intelligent Transport Systems (ITS); Security; Security management messages communication requirements and distribution protocols

DTS/ITS-00550

General Information

Status
Not Published
Technical Committee
Current Stage
12 - Completion
Due Date
28-Sep-2020
Completion Date
16-Oct-2020
Ref Project

Buy Standard

Standard
ETSI TS 103 601 V1.1.1 (2020-10) - Intelligent Transport Systems (ITS); Security; Security management messages communication requirements and distribution protocols
English language
44 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 103 601 V1.1.1 (2020-10)






TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
Security;
Security management messages communication
requirements and distribution protocols

---------------------- Page: 1 ----------------------
2 ETSI TS 103 601 V1.1.1 (2020-10)



Reference
DTS/ITS-00550
Keywords
ITS, protocol, security
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 2020.
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

---------------------- Page: 2 ----------------------
3 ETSI TS 103 601 V1.1.1 (2020-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 8
3.4 Notation . 8
4 Services description: use cases and requirements . 9
4.1 Certificate provisionning service . 9
4.1.1 Service description . 9
4.1.1.1 Overview . 9
4.1.1.2 UC-SEC-01: EC initial request or re-keying . 10
4.1.1.3 UC-SEC-02: AT reloading . 10
4.1.1.4 Use cases and communication profiles mapping. 11
4.1.2 Requirements . 11
4.1.2.1 Security requirements. 11
4.2 CTL distribution service . 12
4.2.1 Service description . 12
4.2.1.1 Overview . 12
4.2.1.2 UC-SEC-03: On demand request of a FullCTL . 12
4.2.1.3 UC-SEC-04: On demand request of a DeltaCTL . 13
4.2.1.4 UC-SEC-05: ITS-S based DeltaCTL distribution . 14
4.2.1.5 UC-SEC-06: Delay-tolerant peer-2-peer DeltaCTL distribution . 15
4.2.1.6 Use cases and communication profiles mapping. 16
4.2.2 Requirements . 16
4.2.2.1 System requirements . 16
4.2.2.2 Security requirements. 17
4.3 CRL distribution service . 17
4.3.1 Service description . 17
4.3.1.1 Overview . 17
4.3.1.2 UC-SEC-07: On demand request of a CRL . 17
4.3.1.3 UC-SEC-08: ITS-S based CRL distribution . 18
4.3.1.4 UC-SEC-09: Delay-tolerant peer-2-peer CRL distribution . 19
4.3.1.5 Use cases and communication profiles mapping. 20
4.3.2 Requirements . 20
4.3.2.1 System requirements . 20
4.3.2.2 Security requirements. 20
5 Use cases specific protocols description . 21
5.1 Enrolment Management with repetition mechanism . 21
5.1.1 EC retry overview . 21
5.1.2 EC retry protocol . 21
5.1.3 Message and version . 21
5.1.4 EC retry requirements . 22
5.1.5 Service communication parameter . 22
5.2 Authorization Management with repetition mechanism . 23
5.2.1 AT retry overview . 23
5.2.2 AT retry protocol . 23
5.2.3 Message and version . 24
5.2.4 AT retry requirements . 24
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 601 V1.1.1 (2020-10)
5.3 Peer-to-peer CRL/CTL distribution protocol . 25
5.3.1 Overview . 25
5.3.2 Peer-to-peer CRL/CTL request/response protocol . 25
5.3.3 Message and version . 26
5.3.4 Peer-to-peer CRL/CTL request message . 26
5.3.4.1 General . 26
5.3.4.2 Generation of a Peer-to-peer CRL request . 27
5.3.4.3 Generation of a Peer-to-peer CTL request . 27
5.3.5 Peer-to-peer CRL/CTL response message . 28
5.3.6 P2P CRL/CTL request message trigger, repetition and termination . 28
5.3.7 Protocol communication parameter . 29
5.4 ITS-S based CRL/CTL broadcast protocol . 29
5.4.1 Overview . 29
5.4.2 CRL/CTL broadcast protocol . 29
5.4.3 Message and version . 30
5.4.4 Protocol communication parameter . 32
6 Communication profiles . 33
6.1 CPS_001 . 33
6.2 CPS_002 . 33
6.3 CPS_003 . 34
6.4 CPS_004 . 34
Annex A (normative): PICS pro forma . 35
A.1 The right to copy . 35
A.2 Guidance for completing the PICS pro forma . 35
A.2.1 Purposes and structure . 35
A.2.2 Abbreviations and conventions . 35
A.2.3 Instructions for completing the PICS pro forma. 36
A.3 Identification of the Equipment . 37
A.3.1 Introduction . 37
A.3.2 Date of the statement . 37
A.3.3 Equipment Under Test identification . 37
A.3.4 Product supplier . 37
A.3.5 Client . 38
A.3.6 PICS contact person . 38
A.4 Identification of the protocol . 39
A.5 Global statement of conformance . 39
A.6 PICS pro forma tables . 39
Annex B (informative): EC Retry scenario examples . 42
B.1 EC Request lost . 42
B.2 EC response lost . 42
History . 44


ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 601 V1.1.1 (2020-10)
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.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 601 V1.1.1 (2020-10)
1 Scope
The present document defines communication requirements and profiles to support communications from/to ITS-S
stations (e.g. fixed road side ITS-S, mobile ITS-S) for the support of security management services specified in ETSI
TS 102 941 [2] (i.e. certificate management, trust and revocation lists distribution).
The present document also defines the related protocol handling for the selected messages as well as the requirements
for the lower layer protocol stacks and for the Security Management entity in order to support message dissemination
and reception.
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 102 940 (V1.3.1): "Intelligent Transport Systems (ITS); Security; ITS communications
security architecture and security management".
[2] ETSI TS 102 941 (V1.3.1): "Intelligent Transport Systems (ITS); Security; Trust and Privacy
Management".
[3] ETSI TS 103 097 (V1.4.1): "Intelligent Transport Systems (ITS); Security; Security header and
certificate formats".
[4] ETSI TS 103 248 (V1.3.1): "Intelligent Transport Systems (ITS); GeoNetworking; Port Numbers
for the Basic Transport Protocol(BTP)".
[5] 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".
[6] ETSI TS 102 965: "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID);
Registration".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 601 V1.1.1 (2020-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.
[i.1] IEEE 802.11™: "IEEE Standard for Information technology - Telecommunications and
information exchange between systems - Local and metropolitan area networks-Specific
requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[i.2] ETSI EN 302 890-1: "Intelligent Transport Systems (ITS); Facilities layer function;
Part 1: Services Announcement (SA) specification".
[i.3] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 102 940 [1] , ETSI TS 102 941 [2] and the
following apply:
CTL/CRL Distribution Application: software application supported by an ITS-S that enables a relay service for
storing and distribution of CTL/CRL to other ITS-S
3.2 Symbols
For the purposes of the present document, the following symbols apply:
N1 number of attempts that an ITS-S is authorized to do after the sending of the EC request. Note that
N1 is a non-negative integer (N1 ≥ 0).
N1 = 0 means that no EC retry is possible
N1 = 1 means that after sending the EC request and not having received the response (because of EC
request loss or EC response loss), the ITS-S can use the EC retry service only one time
N2 it is the number of attempts that an ITS-S is authorized to do after the sending of the AT request.
Note that N2 is a non-negative integer (N1 ≥ 0).
N2 = 0 means that no AT retry is possible
N2 = 1 means that after sending the AT request and not having received the response (because of AT
request loss or AT response loss), the ITS-S can use the AT retry service only one time
T1 time interval between two successive repeated EC requests that are performed by an ITS-S
T2 life-time duration of the created EC request by the requesting ITS-S
T3 time interval between the reception/storage of the context information of the initial EC Request
and the last incoming/repeated EC request received by an EA
T4 time interval between two successive repetitions of the same AT request that are performed by an
ITS-S
T5 life-time duration of the created AT by the requesting ITS-S
T6 time interval between the reception/storage of the context information of the initial AT Request
and the last incoming/repeated AT request received by an AA
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 601 V1.1.1 (2020-10)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
5G-NR 5G New Radio
AA Authorization Authority
AES Advanced Encryption Standard
AT Authorization Ticket
BTP Basic Transport Protocol
CA Certification Authority
CAM Cooperative Awareness Message
CCMS Cooperative-ITS Certificate Management System
CP Certificate Policy
CPOC C-ITS Point Of Contact
CRL Certificate Revocation List
CTL Certificate Trust List
CXLDA CRL/CTL Distribution Application
DC Distribution Centre
EA Enrollment Authority
EC Enrollment Credential
ECTL European Certificate Trust List
EN European Norm
GBC GeoBroadCast
GN GeoNetworking
GN_SAP GeoNetworking_Service Access Point
GUC GeoUniCast
HTTP Hyper Text Transfer Protocol
IP Internet Protocol
ITS Intelligent Transport System
ITS-G5 5 GHz wireless communication
ITS-S Intelligent Transport System - Station
P2PCXLD Peer-to-peer CRL/CTL Distribution service
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PKI Public Key Infrastructure
RA Router Advertisement
RAN Radio Access Network
RCA Root Certification Authority
R-ITS-S Roadside ITS-S
RSU Road Side Unit
SAM Service Advertisement Message
SCH Service CHannel
SHB Single Hop Broadcast
SLAAC StateLess Address Auto-Configuration
SM-PDU Security Management PDU
TA Trust Anchor
TCP Transmission Control Protocol
TLM Trust List Manager
TS Technical Specification
UC Use Case
URL Uniform Resource Locator
V-ITS-S Vehicle ITS-S
WLAN Wireless Local Area Network
3.4 Notation
For the purposes of the present document, the notations given in ETSI TS 102 940 [1] apply.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 601 V1.1.1 (2020-10)
4 Services description: use cases and requirements
4.1 Certificate provisionning service
4.1.1 Service description
4.1.1.1 Overview
The certificates reloading service consists for an ITS-S to request EC/AT to the PKI in an online and automatic manner.
EC requests are not frequent as an ITS-S usually requests one EC at the beginning of its lifecycle and then renews its EC
in advance before the end of its key validity period [2]. However, AT are requested much more often. Indeed when an
ITS-S has only a few remaining Ats it requests new ones to the PKI.
Figure 1 depicts the service from a V-ITS-S and a R-ITS-S point of view:
1) (Green arrow) - A V-ITS-S is within the radio coverage of a RAN access point that provides Internet
connectivity (e.g. cellular base station, Wi-Fi hotspot, R-ITS-S, etc.). The V-ITS-S thus sends its EC/AT
request to the PKI via the RAN access point and the Gateway. The PKI processes the request and sends back
immediately its response to the V-ITS-S.
2) (Orange arrows) - A R-ITS-S is connected to the Internet either wired (e.g. optical fiber, Ethernet, etc.) or
wirelessly via a RAN access point (e.g. cellular base station, Wi-Fi hotspot, etc.). The R-ITS-S thus sends its
EC/AT request to the PKI directly (wire) or via the RAN access point and the Gateway. The PKI processes the
request and sends back immediately its response to the R-ITS-S.
NOTE: In the present document, the RAN Access Point and the Gateway are differentiated. The RAN Access
Point is hardware that provides radio access and the Gateway is the relaying software that links the local
network with the Internet. However the Gateway may be integrated in the RAN Access Point.

Figure 1: Example of certificates reloading service for a V-ITS-S (green) and a R-ITS-S (orange)
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 601 V1.1.1 (2020-10)
4.1.1.2 UC-SEC-01: EC initial request or re-keying
Use Case ID: UC-SEC-01
Use Case Name: Enrolment credential initial request or re-keying.
Priority: Mandatory.
Related
ITS-S is registered in the PKI.
Requirement: ITS-S has Ipv6 connectivity.

Primary Actor ITS-S.
Description ITS-S requests an EC to the EA. After verification, the EA replies positively by
sending back the requested EC to the ITS-S.
Preconditions ITS-S has its canonical key pair, a canonical identifier, the URL of the EA and the EA
certificate.
ITS-S is already registered in EA database.
ITS-S has Ipv6 connectivity.
If using wireless connectivity, the ITS-S shall be under the radio coverage of an
access point that provides Ipv6 connectivity.
Success End Condition ITS-S receives its EC from the EA.
Failed End Condition ITS-S does not receive its EC.
Involved components Security layer.
Main Success Scenario 1) ITS-S creates the EC request and sends it to the EA.
2) The EA verifies the EC request (as specified in ETSI TS 102 941 [2]) and sends
the EC response to the ITS-S.
3) ITS-S receives its EC delivered by the EA.
Extensions
None.
Variations (Alternatives) If the ITS-S does not receive a response from the EA, it
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.