Intelligent transport systems -- Fast service announcement protocol (FSAP) for general purposes in ITS

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS. It references and supports all features of ISO/TS 16460, especially supporting the service response message (SRM) and related features in addition to the service announcement message (SAM), which enables only very basic features. FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier (ITS-AID). This document specifies message formats and related basic protocol procedures by reference to ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS station specified in ISO 21217. This document illustrates its relations to service announcement protocols specified by ETSI TC ITS and IEEE.

Systèmes de transport intelligents -- Protocole d’annonce de service rapide (FSAP)

Le présent document décrit le "protocole d'annonce de service rapide " (FSAP.), ŕ des fins générales dans ITS. Il fait référence et prend en charge toutes les caractéristiques de la norme ISO/TS 16460, en particulier le message de réponse de service (SRM) et ses caractéristiques relatives en plus des messages d'annonce de service (SAM), qui permettent uniquement des fonctions trčs élémentaires. Le protocole FSAP est mis en place, en soutien aux services ITS proposés par avertissement au niveau local et identifiés de maničre unique par un identificateur d'application ITS (ITS-AID). Ce document spécifie les formats des messages et les procédures de protocole de base liées conformément ŕ l'ISO/TS 16460, ainsi que d'autres exigences de protocole connexes pour l'exploitation du FSAP dans le contexte d'une station ITS présentée par l'ISO 21217. Ce document illustre ses relations avec les protocoles d'annonce de service spécifiés par l'ETSI TC ITS et l'IEEE.

General Information

Status
Published
Publication Date
27-May-2020
Current Stage
6060 - International Standard published
Start Date
28-May-2020
Ref Project

RELATIONS

Buy Standard

Standard
ISO 22418:2020 - Intelligent transport systems -- Fast service announcement protocol (FSAP) for general purposes in ITS
English language
55 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO 22418:2020 - Intelligent transport systems -- Fast service announcement protocol (FSAP) for general purposes in ITS
English language
55 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO 22418:2020 - Systèmes de transport intelligents -- Protocole d’annonce de service rapide (FSAP)
French language
59 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO
STANDARD 22418
Second edition
2020-05
Intelligent transport systems — Fast
service announcement protocol
(FSAP) for general purposes in ITS
Systèmes de transport intelligents — Protocole d’annonce de service
rapide (FSAP)
Reference number
ISO 22418:2020(E)
ISO 2020
---------------------- Page: 1 ----------------------
ISO 22418:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 22418:2020(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

Introduction ................................................................................................................................................................................................................................vi

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 1

4 Abbreviated terms .............................................................................................................................................................................................. 2

5 General requirements ..................................................................................................................................................................................... 2

6 Architecture ............................................................................................................................................................................................................... 4

6.1 ITS communications architecture .......................................................................................................................................... 4

6.2 Implementation architecture ..................................................................................................................................................... 4

6.3 Communication roles and entities ......................................................................................................................................... 4

6.4 Communication phases ................................................................................................................................................................... 5

6.4.1 Overview ................................................................................................................................................................................. 5

6.4.2 Service initialization phase ..................................................................................................................................... 5

6.4.3 Service operation phase ............................................................................................................................................ 8

6.5 Advertised services ............................................................................................................................................................................. 8

6.6 FSAP reference architecture ........................................................................................................................................................ 9

7 Protocol elements ............................................................................................................................................................................................10

7.1 Management service access points ....................................................................................................................................10

7.2 Protocol data units ............................................................................................................................................................................10

7.2.1 General...................................................................................................................................................................................10

7.2.2 Fast service advertisement message (FSAM) .......................................................................................11

7.2.3 Fast service response message (FSRM) ....................................................................................................11

7.2.4 Secured messages ........................................................................................................................................................11

7.2.5 Request and response messages .....................................................................................................................12

7.3 Port numbers .........................................................................................................................................................................................12

7.4 ITS application object identifier (ITS-AID) ..................................................................................................................12

8 Protocol procedures ......................................................................................................................................................................................12

8.1 General ........................................................................................................................................................................................................12

8.1.1 FSAP communication handler procedures .............................................................................................12

8.1.2 FSAP manager procedures ...................................................................................................................................13

8.1.3 Extension elements ....................................................................................................................................................13

8.2 Service provider ..................................................................................................................................................................................14

8.2.1 FSAP registration ..........................................................................................................................................................14

8.2.2 FSAP registration update .......................................................................................................................................16

8.2.3 FSAP deregistration ........................................................................................................................................... .........17

8.2.4 FSAP communication management..............................................................................................................18

8.2.5 Transmission of FSAM .................. ......................................................................................................................... ...22

8.2.6 Reception of FSRM ......................................................................................................................................................22

8.3 Service user .............................................................................................................................................................................................25

8.3.1 FSAP registration ..........................................................................................................................................................25

8.3.2 FSAP registration update .......................................................................................................................................26

8.3.3 FSAP deregistration ........................................................................................................................................... .........26

8.3.4 Reception of FSAM ......................................................................................................................................................27

8.4 Service operation phase ...............................................................................................................................................................31

8.5 ITS station-internal management communications ............................................................................................32

8.6 Duplicate service detection .......................................................................................................................................................32

8.7 System service ......................................................................................................................................................................................32

8.7.1 General...................................................................................................................................................................................32

8.7.2 Mandatory applications ..........................................................................................................................................32

9 Optionally supported features ............................................................................................................................................................33

© ISO 2020 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 22418:2020(E)

10 Conformance ..........................................................................................................................................................................................................33

11 Test methods ..........................................................................................................................................................................................................33

Annex A (normative) ASN.1 modules ................................................................................................................................................................34

Annex B (normative) Support of application requirements for communications.............................................41

Annex C (normative) Support of path and flow management .................................................................................................43

Annex D (normative) Implementation conformance statement ..........................................................................................44

Bibliography .............................................................................................................................................................................................................................55

iv © ISO 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 22418:2020(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in

collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC

278, Intelligent transport systems, in accordance with the Agreement on technical cooperation between

ISO and CEN (Vienna Agreement).

This second edition cancels and replaces the first edition (ISO 22418:2018), which has been technically

revised. The main changes compared to the previous edition are as follows:

— this document has been editorially aligned with draft ETSI EN 302 890-1 in order to make these two

standards complement each other such that both can be published as European standards;

— one minor technical detail of the ASN.1 code related to a specific extension element was harmonized

with ETSI.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO 2020 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 22418:2020(E)
Introduction

Provisioning of ITS services at specific locations on the road network requires awareness of the

availability and the purpose of such services in order to allow a road network user to make decisions

on the potential consumption of such a service. Awareness of services can be achieved by pull and push

mechanisms. Whilst pull mechanisms are well understood and deployed for non-time-critical usage,

several use cases depend on a push mechanism. Whilst pull mechanisms require a-priori knowledge

of an intended service, push mechanisms support also "mandatory services" that may be locally and

dynamically applicable and defined by local policies rather than global regulations.

This document illustrates and specifies the features of the cooperative push mechanism "service

announcement" based on the internationally harmonized message formats specified in ISO/TS 16460,

and builds on any localized ITS-S communications protocol stack (ITS-SCPS), one of which is FNTP,

specified in ISO 29281-1, which builds on the ITS-M5 access technology specified in ISO 21215. It is to

be noted that the terms "service announcement" and "service advertisement" are used synonymously.

This document complements service announcement specifications at IEEE ("WAVE Service

Advertisement" [WSA] specified in IEEE 1609.3[TM]) and at ETSI ("Service Announcement Essential

Message" [SAEM] specified in draft ETSI EN 302 890-1):

— The WSA requires normatively only a subset of the functionality specified in ISO/TS 16460. WAVE is

designed for the IEEE 802.11(TM) OCB localized communications access technology operated in the

5,9 GHz frequency bands allocated in the United States of America, also referred to as "US-DSRC".

— The SAEM, also using the message formats specified in ISO/TS 16460, is tailored in support of a

limited ITS service domain identified in ETSI as "Basic Set of Applications", using only a small sub-

set of functionality specified in ISO/TS 16460 and in this document. So far, ETSI requires usage of

the ITS-S communication protocol stack constituted by ITS-G5, GeoNetworking, the Basic Transport

Protocol and the common ETSI message header.

Using the same ITS-SCPS for transmission of the service announcement message (SAM) and the same

limited subset of service announcement functionality, FSAP, WSA, and SAEM are binary compatible

with respect to the shared service announcement features.

Understanding service advertisement and the related protocol specified in this document requires

understanding of ISO/TS 16460.
Requirements are specified in the following clauses of this document.
— Clause 5 specifies general requirements.
— Clause 6 presents a tutorial on architectural issues related to FSAP.
— Clause 7 specifies protocol elements of FSAP.
— Clause 8 specifies protocol procedures of FSAP.
— Clause 10 specifies conformance declaration.
— Clause 11 specifies test methods.
— Annex A specifies the ASN.1 module for FSAP.

— Annex B specifies details of the optional support of presenting communication requirements of

FSAP to the ITS station management in conformance with ISO 17423.

— Annex C specifies details of the optional support of path and flow management for FSAP in

conformance with ISO 24102-6.
— Annex D presents the implementation conformance statement proforma.
vi © ISO 2020 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 22418:2020(E)
Intelligent transport systems — Fast service
announcement protocol (FSAP) for general purposes in ITS
1 Scope

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS.

It references and supports all features of ISO/TS 16460, especially supporting the service response

message (SRM) and related features in addition to the service announcement message (SAM), which

enables only very basic features.

FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier

(ITS-AID).

This document specifies message formats and related basic protocol procedures by reference to

ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS

station specified in ISO 21217.

This document illustrates its relations to service announcement protocols specified by ETSI TC ITS

and IEEE.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules

(PER) — Part 2

ISO/IEC 8825-7, Information technology — ASN.1 encoding rules — Part 7: Specification of Octet Encoding

Rules (OER)

ISO/TS 16460, Intelligent transport systems — Communications access for land mobiles (CALM) —

Communication protocol messages for global usage

ISO 17419, Intelligent transport systems — Cooperative systems — Globally unique identification

ISO 17423, Intelligent transport systems — Cooperative systems — Application requirements and objectives

ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture

ISO 29281-1, Intelligent transport systems — Localized communications — Part 1: Fast networking &

transport layer protocol (FNTP)

ISO 24102-3, Intelligent transport systems — ITS station management — Part 3: Service access points

ISO 24102-4, Intelligent transport systems — ITS station management — Part 4: Station-internal

management communications

ISO 24102-6, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS

station management — Part 6: Path and flow management
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 21217 apply.

© ISO 2020 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO 22418:2020(E)

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
4 Abbreviated terms
APDU application protocol data unit
FSAM fast service advertisement message
FSAP fast service announcement protocol
FSRM fast service response message
ITS-AID ITS application identifier
ITS-SAPID ITS-S application process identifier
ITS-SCPS ITS station communication protocol stack
REQN request message PDU, no response message PDU expected
REQW request message PDU, response message PDU expected
RES response message PDU, acknowledging a REQW
SAEM service announcement essential message
SAM service announcement message
SRM service response message
S-FSAM secured FSAM
S-FSRM secured FSRM
SrvIniP service initialization phase
SrvOpP service operation phase
5 General requirements

The normative part of the specification of the service advertisement messages in ISO/TS 16460 is a

normative part of this document.

The FSAP specified in this document shall be identified in FSAP APDUs by the version number three.

APDUs specified in this document are the FSAM and the FSRM.

The messages for FSAM and FSRM shall be encapsulated by a security frame, resulting in a S-FSAM and

a S-FSRM.

Fragmented transmission of FSRMs and FSAMs is prohibited. Thus, the maximum size of S-FSAMs and

S-FSRMs is limited by the capabilities of the protocol stack used for transmission.

FSAP is identified at the ITS-S networking and transport layer by:

— the well-known registered ITS port number (ITS-PN) PORT_SAM = 1 = 0x00.01, identifying the FSAP

port that is receiving groupcasted S-FSAMs, and
2 © ISO 2020 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 22418:2020(E)
— dynamically assigned ITS-PNs:

— PORT_DYN_FSAM identifying the FSAP port that is receiving unicast S-FSAMs. The dynamic

assignment is done in the ITS-SU that is transmitting S-FSRMs;

— PORT_DYN_FSRM identifying the FSAP port that is receiving unicast S-FSRMs. The dynamic

assignment is done in the ITS-SU that is transmitting S-FSAMs;
as illustrated in Table 1; see also 7.3 on ITS port numbers.
Table 1 — FSAP ITS port numbers
Direction Source ITS-PN Destination ITS-PN MAC mode
From service PORT_DYN_FSRM PORT_SAM Groupcast
advertiser to (broadcast or multicast)
service user
PORT_DYN_FSAM Unicast
From service user PORT_SAM PORT_DYN_FSRM
to service
PORT_DYN_FSAM
advertiser

NOTE Procedures on how to perform multicast transmission of S-FSAMs are not specified in this document.

Unicast transmissions of S-FSRMs and S-FSAMs may be repeated, e.g. after timeout for a respective

acknowledgement, as defined by implementation.
Further on the FSAP is identified by:

— the ITS-AID 2.113.664; see also 7.4. The p-encoded (ASN.1 unaligned packed encoding rules)

presentation of this number of ASN.1 type ITSaid specified in ISO 17419 is 0pE0.00.00.00, i.e. fits

into a four octet field.

An implementation supporting path and flow management shall conform to ISO 24102-6.

An implementation for a distributed ITS-SU, i.e. an ITS-SU consisting of several ITS-SCUs interconnected

with an ITS station-internal network, shall conform to ISO 24102-4.

— identical message formats for service advertisement are used in IEEE 1609.3(TM) (WAVE SAM) and

ETSI TS 102 890 (SAEM), and

— the features specifications in IEEE 1609.3(TM) and ETSI TS 102 890 are sub-sets of the specification

in this document,

an implementation of FSAP optionally may support the service advertisement from IEEE WAVE devices

and the service announcement from ETSI ITS stations by considering the following:

— WSM support

1) The only supported access technology is IEEE 802.11(TM) OCB mode specified in IEEE

802.11(TM) (ISO 21215 with US frequency allocation and WAVE-specific details).

2) The only networking & transport layer protocol supported is the WAVE Short Message protocol

(WSMP) specified in IEEE 1609.3(TM), which uses the same message format as FNTP with

TPID-FS zero (ISO 29281-1).

3) Port numbers are not used. Instead, the service advertisement message SAM is identified by

the value 135 of ITS-AID, used as a transport layer destination address in WSMP (i.e. in FNTP

with TPID-FS zero [ISO 29281-1]).
4) The WAVE SAM is identical to FSAM.
© ISO 2020 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO 22418:2020(E)

5) S-FSAM (Security encapsulated FSAM) uses the same format and encoding as WAVE does.

WAVE security is specified in IEEE 1609.2(TM).

6) FSRM and other features, e.g. mandatory applications and private service channels, are not

supported.
— SAEM support

1) The only supported access technology is IEEE 802.11(TM) OCB mode (ISO 21215 with EU

frequency allocation and ETSI-specific details), referred to as ITS-G5.

2) The only networking & transport layer protocol currently supported is ETSI GeoNetworking/

ETSI Basic Transport Protocol.

3) The SAEM is identified by the BTP port number for SAM specified in ETSI TS 103 248.

4) The SAEM is SAEM preceded by the ETSI common message header.
5) Security encapsulation is not specified.

6) FSRM and other features, e.g. mandatory applications and private service channels, are not

supported.

Details of support of application requirements for communications, if supported in an implementation,

shall be as specified in Annex B. Details of path and flow management, if supported in an implementation,

shall be as specified in Annex C.
6 Architecture
6.1 ITS communications architecture

The FSAP is designed as a functionality of the ITS station and communication architecture specified in

ISO 21217.
6.2 Implementation architecture

The FSAP specified in this document supports the implementation architectures introduced in

ISO 21217.
6.3 Communication roles and entities
The FSAP distinguishes the following roles identified in ISO/TS 16460:
a) Service advertiser:
— management of advertisement requests from service providers;
— transmission of FSAMs and reception of FSRMs.
b) Service provider:
— provision of ITS services.
c) Service user:
— reception of FSAMs and transmission of FSRMs;
— consumption of ITS services.

An ITS-SU may simultaneously or sequentially act as a service advertiser, service provider, and

service user.
4 © ISO 2020 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 22418:2020(E)

This document does not explicitly consider the distinction of service advertiser ITS-SUs and service

provider ITS-SUs; for the purpose here, the two roles are assumed to be located in the same ITS-SU.

An instance of any kind of ITS station identified in ISO 21217 (roadside, vehicle, portable, centre) may

implement the FSAP.
6.4 Communication phases
6.4.1 Overview

In order to allow an ITS-SU to offer an ITS service to another ITS-SU by means of an application session,

a service initialization phase (SrvIniP) is performed by the FSAP, where the SrvIniP is based on localized

communication, e.g. applying the FNTP networking & transport layer protocol specified in ISO 29281-1.

After initialization, the application session is performed during the service operation phase (SrvOpP),

where the SrvOpP may be based on either localized communication or networking, e.g. IPv6

communication, over any kind of access technology.

During SrvIniP, handover to another protocol stack, e.g. another access technology and IPv6, may be

demanded.
The real-time SrvIniP procedures are preferably implemented in an ITS-S router.
NOTE The specification of SrvOpP is outside the scope of this document.
6.4.2 Service initialization phase

The purpose of SrvIniP is to invite a peer ITS-SU by means of a fast service announcement message

(FSAM) to use an ITS service which is uniquely identified by an ITS-AID specified in ISO 17419; ITS-AID

points to an ITS application object.
NOTE 1 Usage of some allocated ITS-AID values are not always meaningful in FSAM.

Acceptance of such an invitation typically results in a session where the two peer ITS-S applications

exchange data. However, a session is not necessarily needed, i.e. the service may be provided completely

by the FSAM. Thus, FSAM provides also the means to periodically broadcast information from ITS

broadcast services.

Three operational options of SrvIniP are specified. The distinction was originally motivated by the two

ITS application objects:
a) ITS application class (ISO 15628 ), and
b) ITS application,

and was extended to allocate private communication channels to individual ITS station units (ITS-SUs)

...

INTERNATIONAL ISO
STANDARD 22418
Second edition
2020-06
Intelligent transport systems — Fast
service announcement protocol
(FSAP) for general purposes in ITS
Systèmes de transport intelligents — Protocole d’annonce de service
rapide (FSAP)
PROOF/ÉPREUVE
Reference number
ISO 22418:2020(E)
ISO 2020
---------------------- Page: 1 ----------------------
ISO 22418:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii PROOF/ÉPREUVE © ISO 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 22418:2020(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

Introduction ................................................................................................................................................................................................................................vi

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 2

4 Abbreviated terms .............................................................................................................................................................................................. 2

5 General requirements ..................................................................................................................................................................................... 2

6 Architecture ............................................................................................................................................................................................................... 4

6.1 ITS communications architecture .......................................................................................................................................... 4

6.2 Implementation architecture ..................................................................................................................................................... 4

6.3 Communication roles and entities ......................................................................................................................................... 4

6.4 Communication phases ................................................................................................................................................................... 5

6.4.1 Overview ................................................................................................................................................................................. 5

6.4.2 Service initialization phase ..................................................................................................................................... 5

6.4.3 Service operation phase ............................................................................................................................................ 8

6.5 Advertised services ............................................................................................................................................................................. 8

6.6 FSAP reference architecture ........................................................................................................................................................ 9

7 Protocol elements ............................................................................................................................................................................................10

7.1 Management service access points ....................................................................................................................................10

7.2 Protocol data units ............................................................................................................................................................................10

7.2.1 General...................................................................................................................................................................................10

7.2.2 Fast service advertisement message (FSAM) .......................................................................................11

7.2.3 Fast service response message (FSRM) ....................................................................................................11

7.2.4 Secured messages ........................................................................................................................................................11

7.2.5 Request and response messages .....................................................................................................................12

7.3 Port numbers .........................................................................................................................................................................................12

7.4 ITS application object identifier (ITS-AID) ..................................................................................................................12

8 Protocol procedures ......................................................................................................................................................................................12

8.1 General ........................................................................................................................................................................................................12

8.1.1 FSAP communication handler procedures .............................................................................................12

8.1.2 FSAP manager procedures ...................................................................................................................................13

8.1.3 Extension elements ....................................................................................................................................................13

8.2 Service provider ..................................................................................................................................................................................14

8.2.1 FSAP registration ..........................................................................................................................................................14

8.2.2 FSAP registration update .......................................................................................................................................16

8.2.3 FSAP deregistration ........................................................................................................................................... .........17

8.2.4 FSAP communication management..............................................................................................................18

8.2.5 Transmission of FSAM .................. ......................................................................................................................... ...22

8.2.6 Reception of FSRM ......................................................................................................................................................22

8.3 Service user .............................................................................................................................................................................................25

8.3.1 FSAP registration ..........................................................................................................................................................25

8.3.2 FSAP registration update .......................................................................................................................................26

8.3.3 FSAP deregistration ........................................................................................................................................... .........26

8.3.4 Reception of FSAM ......................................................................................................................................................27

8.4 Service operation phase ...............................................................................................................................................................31

8.5 ITS station-internal management communications ............................................................................................32

8.6 Duplicate service detection .......................................................................................................................................................32

8.7 System service ......................................................................................................................................................................................32

8.7.1 General...................................................................................................................................................................................32

8.7.2 Mandatory applications ..........................................................................................................................................32

9 Optionally supported features ............................................................................................................................................................33

© ISO 2020 – All rights reserved PROOF/ÉPREUVE iii
---------------------- Page: 3 ----------------------
ISO 22418:2020(E)

10 Conformance ..........................................................................................................................................................................................................33

11 Test methods ..........................................................................................................................................................................................................33

Annex A (normative) ASN.1 modules ................................................................................................................................................................34

Annex B (normative) Support of application requirements for communications.............................................42

Annex C (normative) Support of path and flow management .................................................................................................44

Annex D (normative) Implementation conformance statement ..........................................................................................45

Bibliography .............................................................................................................................................................................................................................56

iv PROOF/ÉPREUVE © ISO 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 22418:2020(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in

collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC

278, Intelligent transport systems, in accordance with the Agreement on technical cooperation between

ISO and CEN (Vienna Agreement).

This second edition cancels and replaces the first edition (ISO 22418:2018), which has been technically

revised. The main changes compared to the previous edition are as follows:

— this document has been editorially aligned with draft ETSI EN 302 890-1 in order to make these two

standards complement each other such that both can be published as European standards;

— one minor technical detail of the ASN.1 code related to a specific extension element was harmonized

with ETSI.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO 2020 – All rights reserved PROOF/ÉPREUVE v
---------------------- Page: 5 ----------------------
ISO 22418:2020(E)
Introduction

Provisioning of ITS services at specific locations on the road network requires awareness of the

availability and the purpose of such services in order to allow a road network user deciding on the

potential consumption of such a service. Awareness of services can be achieved by pull and push

mechanisms. Whilst pull mechanisms are well understood and deployed for non-time-critical usage,

several use cases depend on a push mechanism. Whilst pull mechanisms require a-priori knowledge

of an intended service, push mechanisms support also "mandatory services" that may be locally and

dynamically applicable and defined by local policies rather than global regulations.

This document illustrates and specifies the features of the cooperative push mechanism "Service

Announcement" based on the internationally harmonized message formats specified in ISO/TS 16460:,

and builds on top of any localized ITS-S communications protocol stack (ITS-SCPS), one of which is

[6]

FNTP specified in ISO 29281-1 on top of the ITS-M5 access technology specified in ISO 21215 . It is to

be noted that the terms "service announcement" and "service advertisement" are used synonymously.

This document complements service announcement specifications at IEEE ["WAVE Service

[3]

Advertisement" (WSA) specified in IEEE 1609.3 ] and at ETSI ["Service Announcement Essential

[16]
Message" (SAEM) specified in draft ETSI EN 302 890-1 :

— The WSA requires normatively only a subset of the functionality specified in ISO/TS 16460. WAVE is

designed for the IEEE 802.11 OCB localized communications access technology operated in the 5,9

GHz frequency bands allocated in the United States of America, also referred to as "US-DSRC".

— The SAEM, also using the message formats specified in ISO/TS 16460, is tailored in support of a

limited ITS service domain identified in ETSI as "Basic Set of Applications", using only a small sub-

set of functionality specified in ISO/TS 16460 and in this document. So far, ETSI requires usage of

the ITS-S communication protocol stack constituted by ITS-G5, GeoNetworking, the Basic Transport

Protocol, and the common ETSI message header.

Using the same ITS-SCPS for transmission of the service announcement message (SAM) and the same

limited subset of service announcement functionality, FSAP, WSA, and SAEM are binary compatible

with respect of the shared service announcement features.

Understanding service advertisement and the related protocol specified in this document requires

understanding of ISO/TS 16460.
Requirements are specified in the following clauses of this document.
— Clause 5 specifies general requirements.
— Clause 6 presents a tutorial on architectural issues related to FSAP.
— Clause 7 specifies protocol elements of FSAP.
— Clause 8 specifies protocol procedures of FSAP.
— Clause 9 specifies conformance declaration.
— Clause 10 specifies test methods.
— Annex A specifies the ASN.1 module for FSAP.

— Annex B specifies details of the optional support of presenting communication requirements of

FSAP to the ITS station management compliant with ISO 17423.

— Annex C specifies details of the optional support of path and flow management for FSAP compliant

with ISO 24102-6.
— Annex D presents the implementation conformance statement proforma.
vi PROOF/ÉPREUVE © ISO 2020 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 22418:2020(E)
Intelligent transport systems — Fast service
announcement protocol (FSAP) for general purposes in ITS
1 Scope

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS.

It references and supports all features of ISO/TS 16460, especially supporting the service response

message (SRM) and related features in addition to the service announcement message (SAM), which

enables only very basic features.

FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier

(ITS-AID).

This document specifies message formats and related basic protocol procedures by reference to

ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS

station specified in ISO 21217.

This document illustrates its relations to service announcement protocols specified by ETSI TC ITS and

IEEE WG 1609.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules

(PER) — Part 2:

ISO/IEC 8825-7, Information technology — ASN.1 encoding rules — Part 7: Specification of Octet Encoding

Rules (OER)

ISO/TS 16460, Intelligent transport systems — Communications access for land mobiles (CALM) —

Communication protocol messages for global usage

ISO 17419, Intelligent transport systems — Cooperative systems — Globally unique identification

ISO 17423, Intelligent transport systems — Cooperative systems — Application requirements and objectives

ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture

ISO 21218, Intelligent transport systems — Hybrid communications — Access technology support

ISO 29281-1, Intelligent transport systems — Localized communications — Part 1: Fast networking &

transport layer protocol (FNTP)

ISO 24102-3, Intelligent transport systems — ITS station management — Part 3: Service access points

ISO 24102-4, Intelligent transport systems — ITS station management — Part 4: Station-internal

management communications

ISO 24102-6, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS

station management — Part 6: Path and flow management
© ISO 2020 – All rights reserved PROOF/ÉPREUVE 1
---------------------- Page: 7 ----------------------
ISO 22418:2020(E)
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 21217 apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
4 Abbreviated terms
APDU application protocol data unit
FSAM fast service advertisement message
FSAP fast service announcement protocol
FSRM fast service response message
ITS-AID ITS application identifier
ITS-SAPID ITS-S application process identifier
ITS-SCPS ITS station communication protocol stack
REQN request message PDU, no response message PDU expected
REQW request message PDU, response message PDU expected
RES response message PDU, acknowledging a REQW
SAEM service announcement essential message
SAM service announcement message
SRM service response message
S-FSAM secured FSAM
S-FSRM secured FSRM
SrvIniP service initialization phase
SrvOpP service operation phase
5 General requirements

The normative part of the specification of the service advertisement messages in ISO/TS 16460:2016 is

a normative part of this document.

The FSAP specified in this document shall be identified in FSAP APDUs by the version number three.

APDUs specified in this document are the FSAM and the FSRM.

The messages for FSAM and FSRM shall be encapsulated by a security frame, resulting in a S-FSAM and

a S-FSRM.

Fragmented transmission of FSRMs and FSAMs is prohibited. Thus, the maximum size of S-FSAMs and

S-FSRMs is limited by the capabilities of the protocol stack used for transmission.

2 PROOF/ÉPREUVE © ISO 2020 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 22418:2020(E)
FSAP is identified at the ITS-S networking and transport layer by:

— the well-known registered ITS port number (ITS-PN) PORT_SAM = 1 = 0x00.01 published on [10],

identifying the FSAP port that is receiving groupcasted S-FSAMs, and
— dynamically assigned ITS-PNs:

— PORT_DYN_FSAM identifying the FSAP port that is receiving unicast S-FSAMs. The dynamic

assignment is done in the ITS-SU that is transmitting S-FSRMs;

— PORT_DYN_FSRM identifying the FSAP port that is receiving unicast S-FSRMs. The dynamic

assignment is done in the ITS-SU that is transmitting S-FSAMs;
as illustrated in Table 1; see also 7.3 on ITS port numbers.
Table 1 — FSAP ITS port numbers
Direction Source ITS-PN Destination ITS-PN MAC mode
From service PORT_DYN_FSRM PORT_SAM Groupcast
advertiser to (broadcast or multicast)
service user
PORT_DYN_FSAM Unicast
From service user PORT_SAM PORT_DYN_FSRM
to service
PORT_DYN_FSAM
advertiser

NOTE Procedures on how to perform multicast transmission of S-FSAMs are not specified in this document.

Unicast transmissions of S-FSRMs and S-FSAMs may be repeated, e.g. after timeout for a respective

acknowledgement, as defined by implementation.
Further on the FSAP is identified by

— the ITS-AID 2.113.664 published on [10]; see also 7.4. The p-encoded (ASN.1 unaligned packed

encoding rules) presentation of this number of ASN.1 type ITSaid specified in ISO 17419 is

0pE0.00.00.00, i.e. fits into a four octet field.

An implementation supporting path and flow management shall conform to ISO 24102-6.

An implementation for a distributed ITS-SU, i.e. an ITS-SU consisting of several ITS-SCUs interconnected

with an ITS station-internal network, shall conform to ISO 24102-4.
[2]

— identical message formats for service advertisement are used in IEEE 1609.3 (WAVE SAM) and

[14]
ETSI TS 102 890 (SAEM), and
[2] [14]

— the features specifications in IEEE 1609.3 and ETSI TS 102 890 are sub-sets of the specification

in this document,

an implementation of FSAP optionally may support the service advertisement from IEEE WAVE devices

and the service announcement from ETSI ITS stations by considering the following:

— WSM support
[4]

1) The only supported access technology is IEEE 802.11 OCB mode specified in IEEE 802.11

[6]
(ISO 21215 with US frequency allocation and WAVE-specific details).

2) The only networking & transport layer protocol supported is the WAVE Short Message protocol

[2]

(WSMP) specified in IEEE 1609.3 , which uses the same message format as FNTP with TPID-

FS zero (ISO 29281-1).
© ISO 2020 – All rights reserved PROOF/ÉPREUVE 3
---------------------- Page: 9 ----------------------
ISO 22418:2020(E)

3) Port numbers are not used. Instead, the service advertisement message SAM is identified by

the value 135 of ITS-AID, used as a transport layer destination address in WSMP (i.e. in FNTP

with TPID-FS zero [ISO 29281-1]).
4) The WAVE SAM is identical to FSAM.

5) S-FSAM (Security encapsulated FSAM) uses the same format and encoding as WAVE does.

[3]
WAVE security is specified in IEEE 1609.2 .

6) FSRM and other features, e.g. mandatory applications and private service channels, are not

supported.
— SAEM support
[6]

1) The only supported access technology is IEEE 802.11 OCB mode (ISO 21215 with EU

frequency allocation and ETSI-specific details), referred to as ITS-G5.

2) The only networking & transport layer protocol currently supported is ETSI GeoNetworking/

ETSI Basic Transport Protocol.

3) The SAEM is identified by the BTP port number for SAM specified in ETSI TS 103 248.

4) The SAEM is SAEM preceded by the ETSI common message header.
5) Security encapsulation is not specified.

6) FSRM and other features, e.g. mandatory applications and private service channels, are not

supported.

Details of support of application requirements for communications, if supported in an implementation,

shall be as specified in Annex B. Details of path and flow management, if supported in an implementation,

shall be as specified in Annex C.
6 Architecture
6.1 ITS communications architecture

The FSAP is designed as a functionality of the ITS station and communication architecture specified in

ISO 21217.
6.2 Implementation architecture

The FSAP specified in this document supports the implementation architectures introduced in

ISO 21217.
6.3 Communication roles and entities
The FSAP distinguishes the following roles identified in ISO/TS 16460:
a) Service advertiser:
— management of advertisement requests from service providers;
— transmission of FSAMs and reception of FSRMs;
b) Service provider:
— provision of ITS services;
4 PROOF/ÉPREUVE © ISO 2020 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 22418:2020(E)
c) Service user:
— reception of FSAMs and transmission of FSRMs;
— consumption of ITS services.

An ITS-SU may simultaneously or sequentially act as a service advertiser, service provider, and

service user.

This document does not explicitly consider the distinction of service advertiser ITS-SUs and service

provider ITS-SUs; for the purpose here the two roles are assumed to be located in the same ITS-SU.

An instance of any kind of ITS station identified in ISO 21217 (roadside, vehicle, portable, centre) may

implement the FSAP.
6.4 Communication phases
6.4.1 Overview

In order to allow an ITS-SU to offer an ITS service to another ITS-SU by means of an application session,

a service initialization phase (SrvIniP) is performed by the FSAP, where the SrvIniP is based on localized

communication, e.g. applying the FNTP networking & transport layer protocol specified in ISO 29281-1.

After initialization, the application session is performed during the service operation phase (SrvOpP),

where the SrvOpP may be based on either localized communication or networking, e.g. IPv6

communication, over any kind of access technology.

During SrvIniP, handover to another protocol stack, e.g. another access technology and IPv6, may be

demanded.
The real-time SrvIniP procedures are preferably implemented in an ITS-S router.
NOTE The specification of SrvOpP is outside the scope of this document.
6.4.2 Service initialization phase

The purpose of SrvIniP is to invite a peer ITS-SU by means of a fast service announcement message

(FSAM) to use an ITS service which is uniquely identified by an ITS-AID specified in ISO 17419; ITS-AID

points to an ITS application object.
NOTE 1 Usage of some allocated ITS-AID values are not always meaningful in FSAM.

Acceptance of such an invitation typically results in a session where the two peer ITS-S applications

exchange data. However, a session is not necessarily needed, i.e. the service may be provided completely

by the FSAM. Thus, FSAM provides also the means to periodically broadcast information from ITS

broadcast services.
Three operational options
...

NORME ISO
INTERNATIONALE 22418
Deuxième édition
2020-05
Systèmes de transport intelligents —
Protocole d’annonce de service
rapide (FSAP)
Intelligent transport systems — Fast service announcement protocol
(FSAP) for general purposes in ITS
Numéro de référence
ISO 22418:2020(F)
ISO 2020
---------------------- Page: 1 ----------------------
ISO 22418:2020(F)
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO 2020

Tous droits réservés. Sauf prescription différente ou nécessité dans le contexte de sa mise en œuvre, aucune partie de cette

publication ne peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique,

y compris la photocopie, ou la diffusion sur l’internet ou sur un intranet, sans autorisation écrite préalable. Une autorisation peut

être demandée à l’ISO à l’adresse ci-après ou au comité membre de l’ISO dans le pays du demandeur.

ISO copyright office
Case postale 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Genève
Tél.: +41 22 749 01 11
E-mail: copyright@iso.org
Web: www.iso.org
Publié en Suisse
ii © ISO 2020 – Tous droits réservés
---------------------- Page: 2 ----------------------
ISO 22418:2020(F)
Sommaire Page

Avant-propos ................................................................................................................................................................................................................................v

Introduction ................................................................................................................................................................................................................................vi

1 Domaine d’application ................................................................................................................................................................................... 1

2 Références normatives ................................................................................................................................................................................... 1

3 Termes et définitions ....................................................................................................................................................................................... 2

4 Symboles et abréviations ............................................................................................................................................................................. 2

5 Dispositions générales ................................................................................................................................................................................... 2

6 Architecture ............................................................................................................................................................................................................... 4

6.1 Architecture de communication ITS ..................................................................................................................................... 4

6.2 Architecture de mise en œuvre ................................................................................................................................................. 4

6.3 Rôles et entités de communication ....................................................................................................................................... 5

6.4 Phases de communication ............................................................................................................................................................. 5

6.4.1 Vue d’ensemble ................................................................................................................................................................. 5

6.4.2 Phase d’initialisation du service ......................................................................................................................... 5

6.4.3 Phase d’exploitation du service .......................................................................................................................... 8

6.5 Services proposés par avertissement .................................................................................................................................. 9

6.6 Architecture de référence du FSAP ........................................................................................................................................ 9

7 Éléments du protocole .................................................................................................................................................................................10

7.1 Points d’accès au service de gestion ..................................................................................................................................10

7.2 Unités de données de protocole ............................................................................................................................................10

7.2.1 Généralités .........................................................................................................................................................................10

7.2.2 Message d’avertissement de service rapide ..........................................................................................11

7.2.3 Message de réponse de service rapide ......................................................................................................11

7.2.4 Messages sécurisés .....................................................................................................................................................11

7.2.5 Messages de demande et de réponse ..........................................................................................................12

7.3 Numéros de ports ..............................................................................................................................................................................12

7.4 Identificateur d’objet d’application ITS ..........................................................................................................................12

8 Procédures du protocole ...........................................................................................................................................................................13

8.1 Généralités ...............................................................................................................................................................................................13

8.1.1 Procédures du module de gestion des communications FSAP .............................................13

8.1.2 Procédures du gestionnaire FSAP ..................................................................................................................13

8.1.3 Éléments d’extension ................................................................................................................................................14

8.2 Fournisseur de services................................................................................................................................................................14

8.2.1 Enregistrement FSAP ................................................................................................................................................14

8.2.2 Mise à jour de l’enregistrement FSAP .........................................................................................................16

8.2.3 Désenregistrement FSAP .......................................................................................................................................17

8.2.4 Gestion des communications FSAP ...............................................................................................................18

8.2.5 Transmission de FSAM ............................................................................................................................................22

8.2.6 Réception de FSRM .....................................................................................................................................................23

8.3 Utilisateur du service .....................................................................................................................................................................25

8.3.1 Enregistrement FSAP ................................................................................................................................................25

8.3.2 Mise à jour de l’enregistrement FSAP .........................................................................................................26

8.3.3 Désenregistrement FSAP .......................................................................................................................................27

8.3.4 Réception de FSAM .....................................................................................................................................................28

8.4 Phase d’exploitation du service .............................................................................................................................................33

8.5 Communications de gestion interne à la station ITS ...........................................................................................33

8.6 Détection de services en double ...........................................................................................................................................33

8.7 Service système ...................................................................................................................................................................................34

8.7.1 Généralités .........................................................................................................................................................................34

8.7.2 Applications obligatoires .......................................................................................................................................34

9 Fonctionnalités supportées de manière facultative .....................................................................................................34

© ISO 2020 – Tous droits réservés iii
---------------------- Page: 3 ----------------------
ISO 22418:2020(F)

10 Conformité ...............................................................................................................................................................................................................34

11 Méthodes d’essai ...............................................................................................................................................................................................34

Annexe A (normative) Modules ASN.1 .............................................................................................................................................................36

Annexe B (normative) Support des exigences des applications en matière de communications .....44

Annexe C (normative) Support de la gestion des chemins d’accès et des flux .......................................................46

Annexe D (normative) Déclaration de conformité des mises en œuvre .......................................................................47

Bibliographie ...........................................................................................................................................................................................................................59

iv © ISO 2020 – Tous droits réservés
---------------------- Page: 4 ----------------------
ISO 22418:2020(F)
Avant-propos

L'ISO (Organisation internationale de normalisation) est une fédération mondiale d'organismes

nationaux de normalisation (comités membres de l'ISO). L'élaboration des Normes internationales est

en général confiée aux comités techniques de l'ISO. Chaque comité membre intéressé par une étude

a le droit de faire partie du comité technique créé à cet effet. Les organisations internationales,

gouvernementales et non gouvernementales, en liaison avec l'ISO participent également aux travaux.

L'ISO collabore étroitement avec la Commission électrotechnique internationale (IEC) en ce qui

concerne la normalisation électrotechnique.

Les procédures utilisées pour élaborer le présent document et celles destinées à sa mise à jour sont

décrites dans les Directives ISO/IEC, Partie 1. Il convient, en particulier, de prendre note des différents

critères d'approbation requis pour les différents types de documents ISO. Le présent document a été

rédigé conformément aux règles de rédaction données dans les Directives ISO/IEC, Partie 2 (voir www

.iso .org/ directives).

L'attention est attirée sur le fait que certains des éléments du présent document peuvent faire l'objet de

droits de propriété intellectuelle ou de droits analogues. L'ISO ne saurait être tenue pour responsable

de ne pas avoir identifié de tels droits de propriété et averti de leur existence. Les détails concernant

les références aux droits de propriété intellectuelle ou autres droits analogues identifiés lors de

l'élaboration du document sont indiqués dans l'Introduction et/ou dans la liste des déclarations de

brevets reçues par l'ISO (voir www .iso .org/ brevets).

Les appellations commerciales éventuellement mentionnées dans le présent document sont données

pour information, par souci de commodité, à l’intention des utilisateurs et ne sauraient constituer un

engagement.

Pour une explication de la nature volontaire des normes, la signification des termes et expressions

spécifiques de l'ISO liés à l'évaluation de la conformité, ou pour toute information au sujet de l'adhésion

de l'ISO aux principes de l’Organisation mondiale du commerce (OMC) concernant les obstacles

techniques au commerce (OTC), voir www .iso .org/ avant -propos.

Le présent document a été élaboré par le comité technique ISO/TC 204, Systèmes de transport intelligents,

en collaboration avec le comité technique CEN/TC 278, Systèmes de transport intelligents, du Comité

européen de normalisation (CEN) conformément à l’Accord de coopération technique entre l’ISO et le

CEN (Accord de Vienne).

Cette deuxième édition annule et remplace la première édition (ISO 22418:2018), qui a fait l’objet d’une

révision technique.

Les principales modifications par rapport à l’édition précédente sont les suivantes:

— ce document a été éditée conformément au projet ETSI EN 302 890-1 afin que ces deux normes se

complètent mutuellement et puissent être publiées comme normes européennes;

— un détail technique mineur du code ASN.1 relatif à un élément d'extension spécifique a été harmonisé

avec l'ETSI.

Il convient que l’utilisateur adresse tout retour d’information ou toute question concernant le présent

document à l’organisme national de normalisation de son pays. Une liste exhaustive desdits organismes

se trouve à l’adresse www .iso .org/ fr/ members .html.
© ISO 2020 – Tous droits réservés v
---------------------- Page: 5 ----------------------
ISO 22418:2020(F)
Introduction

La fourniture de services ITS à des emplacements spécifiques du réseau routier impose de connaître la

disponibilité et la finalité de ces services afin de permettre à un usager du réseau routier de prendre

des décisions sur la consommation potentielle d'un tel service. Cette connaissance des services peut

être assurée par des mécanismes dits pull et push. Bien que les mécanismes pull soient bien compris et

déployés pour des usages non soumis à des contraintes temporelles strictes, plusieurs cas d’utilisation

dépendent d’un mécanisme push. Même si les mécanismes pull exigent la connaissance préalable d’un

service visé, les mécanismes push supportent également les «services obligatoires» pouvant être

applicables au niveau local et de manière dynamique, définis par les politiques locales plutôt que par

des réglementations globales.

Ce document illustre et spécifie les fonctionnalités du mécanisme push coopératif «annonce de service»

basé sur les formats de message harmonisé au niveau international défini par l’ISO/TS 16460, et se

basant sur toute pile de protocoles de communication ITS-S (ITS-SCPS) dont l'une est FNTP spécifié

dans ISO 29281-1 basé sur la technologie ITS-M5, spécifiée dans ISO 21215. Il est à noter que les termes

«annonce de service» et «avertissement de service» sont utilisés comme synonymes.

Ce document complète les spécifications d'annonce de service de l'IEEE («WAVE Service Advertisement»

(WSA) spécifiées dans IEEE 1609.3 et de l'ETSI (“Annonces essentielles de service pour les messages

d'interruption” (SAEM) spécifiées dans la norme provisoire ETSI EN 302 890-1):

La compréhension de l’avertissement de service et des protocoles connexes spécifiés dans le présent

document exige la compréhension de l’ISO/TS 16460.

— L'WSA n'exige, sur le plan normatif, qu'un sous-ensemble des fonctionnalités spécifiées dans la

norme ISO/TS 16460:2016. WAVE est conçu pour la technologie d'accès aux communications

localisées IEEE 802.11 OCB fonctionnant dans les bandes de fréquences de 5,9 GHz attribuées aux

États-Unis d'Amérique, également appelées «US-DSRC».

— Le SAEM, qui utilise également les formats de messages spécifiés dans la norme ISO/TS 16460,

est adapté pour prendre en charge un domaine de service ITS limité identifié dans ETSI comme

«ensemble de base des applications», en ne faisant usage que d'un petit sous-ensemble des

fonctionnalités spécifié dans ISO/TS 16460 et dans ce document. A ce stade, l'ETSI exige l'utilisation

de la pile de protocoles de communication ITS-S constituée par l'ITS-G5, le GeoNetworking, le Basic

protocol de transport et l'en-tête commun du message ETSI.

L'utilisation du même ITS-SCPS pour la transmission du message d'annonce de service et du même

sous-ensemble limité de fonctionnalités d'annonce de service, FSAP, WSA et SAEM sont compatibles

binairement en ce qui concerne les caractéristiques des services partagés de notifications.

La compréhension de toutes les publicités de service et du protocole associé spécifié dans ce document

nécessite une compréhension de la norme ISO/TS 16460.
Les exigences sont spécifiées dans les articles suivants du présent document.
— L’Article 5 spécifie les exigences générales.

— L’Article 6 présente un tutoriel sur les questions d’architecture liées au FSAP.

— L’Article 7 spécifie les éléments de protocole du FSAP.
— L’Article 8 spécifie les procédures de protocole du FSAP.
— L’Article 10 spécifie la déclaration de conformité.
— L’Article 11 spécifie les méthodes d’essai.
— L’Annexe A spécifie le module ASN.1 pour le FSAP.
vi © ISO 2020 – Tous droits réservés
---------------------- Page: 6 ----------------------
ISO 22418:2020(F)

— L’Annexe B spécifie les détails du support facultatif de la présentation des exigences de communication

du FSAP à la gestion des stations ITS conformément à l’ISO 17423.

— L’Annexe C spécifie les détails du support facultatif de la gestion des chemins d’accès et des flux pour

le FSAP conformément à l’ISO 24102-6.

— L’Annexe D présente le formulaire de déclaration de conformité des mises en œuvre.

© ISO 2020 – Tous droits réservés vii
---------------------- Page: 7 ----------------------
NORME INTERNATIONALE ISO 22418:2020(F)
Systèmes de transport intelligents — Protocole d’annonce
de service rapide (FSAP)
1 Domaine d’application

Le présent document décrit le “protocole d’annonce de service rapide ” (FSAP.), à des fins générales

dans ITS. Il fait référence et prend en charge toutes les caractéristiques de la norme ISO/TS 16460,

en particulier le message de réponse de service (SRM) et ses caractéristiques relatives en plus des

messages d'annonce de service (SAM), qui permettent uniquement des fonctions très élémentaires.

Le protocole FSAP est mis en place, en soutien aux services ITS proposés par avertissement au niveau

local et identifiés de manière unique par un identificateur d’application ITS (ITS-AID).

Ce document spécifie les formats des messages et les procédures de protocole de base liées

conformément à l’ISO/TS 16460, ainsi que d’autres exigences de protocole connexes pour l’exploitation

du FSAP dans le contexte d’une station ITS présentée par l’ISO 21217.

Ce document illustre ses relations avec les protocoles d'annonce de service spécifiés par l'ETSI TC ITS

et l'IEEE.
2 Références normatives

Les documents suivants sont cités dans le texte de sorte qu’ils constituent, pour tout ou partie de leur

contenu, des exigences du présent document. Pour les références datées, seule l’édition citée s’applique.

Pour les références non datées, la dernière édition du document de référence s'applique (y compris les

éventuels amendements).

ISO/IEC 8825-2, Technologies de l’information — Règles de codage ASN.1: Spécification des règles de

codage compact (PER) — Partie 2

ISO/IEC 8825-7, Technologies de l’information — Règles de codage ASN.1 — Partie 7: Spécification des

règles de codage des octets (OER)

ISO/TS 16460, Systèmes de transport intelligents — Accès aux communications des services mobiles

terrestres (CALM) — Messages de protocole de communication pour une utilisation globale

ISO 17419, Systèmes intelligents de transport — Systèmes coopératifs — Identification unique au

niveau global

ISO 17423, Systèmes de transport intelligents — Systèmes Coopératifs — Exigences et objectifs de

l'application

ISO 21217, Systèmes intelligents de transport — Accès aux communications des services mobiles terrestres

(CALM) — Architecture

ISO 29281-1, Systèmes intelligents de transport — Communications localisées — Partie 1: Réseautique

rapide et protocole de la couche transport

ISO 24102-3, Systèmes intelligents de transport — Gestion des stations ITS — Partie 3: Points d'accès

au service

ISO 24102-4, Systèmes intelligents de transport — Gestion des stations ITS — Partie 4: Communications de

gestion interne à la station

ISO 24102-6:, Systèmes intelligents de transport — Accès aux communications des services mobiles

terrestres (CALM) — Gestion des stations ITS — Partie 6: Titre manque
© ISO 2020 – Tous droits réservés 1
---------------------- Page: 8 ----------------------
ISO 22418:2020(F)
3 Termes et définitions

Pour les besoins du présent document, les termes et les définitions de ISO 21217 s’appliquent.

L’ISO et l’IEC tiennent à jour des bases de données terminologiques destinées à être utilisées en

normalisation, consultables aux adresses suivantes:

— ISO Online browsing platform: disponible à l’adresse https:// www .iso .org/ obp

— IEC Electropedia: disponible à l’adresse http:// www .electropedia .org/
4 Symboles et abréviations
APDU application protocol data unit, unité de données du protocole d'application

SAEM Service announcement essential message, Service d'annonce de message essentiel

FSAM Fast Service Advertisement Message, Message d’avertissement de service rapide

FSAP Fast Service Announcement Protocol, Protocole d’annonce de service rapide
FSRM Fast Service Response Message, Message de réponse de service rapide
ITS-AID ITS application identifier, Identifiant de la demande ITS

ITS-SAPID ITS-S application process identifier, Identificateur du processus de demande ITS-S

ITS-SCPS ITS station communication protocol stack, Protocole de communication de la station ITS

REQN PDU de message de demande, pas de PDU de message de réponse attendu
REQRES PDU de message de demande ou de réponse au REQW, REQN, RES défini
REQW PDU de message de demande, PDU de message de réponse attendu
RES PDU de message de réponse, confirmant un REQW

SAEM service announcement essential message, Message essentiel de l'annonce de ser-

vice SAEM
SAM service announcement message, Message d'annonce du service SAM
SRM service response message, Message de réponse du service SRM
S-FSAM Secured FSAM, FSAM sécurisé
S-FSRM Secured FSRM, FSRM sécurisé
SrvIniP Service Initialization Phase, Phase d’initialisation du service
SrvOpP Service Operation Phase, Phase d’exploitation du service
5 Dispositions générales

La partie normative de la spécification des «messages d’avertissement de service» de l’ISO/TS 16460

est une partie normative du présent document

Le FSAP spécifié dans le présent document doit être identifié dans les unités de données FSAP APDU

par le numéro de version «trois».
Les APDU spécifiées dans le présent document sont le FSAM et le FSRM.
2 © ISO 2020 – Tous droits réservés
---------------------- Page: 9 ----------------------
ISO 22418:2020(F)

Les messages FSAM et FSRM doivent être encapsulés par une trame de sécurité pour devenir un FSAM

sécurisé (S-FSAM) et un FSRM sécurisé (S-FSRM).

La transmission fragmentée de FSRM et de FSAM étant interdite, la taille maximale des S-FSAM et des

S-FSRM est limitée par les capacités de la pile de protocoles utilisée pour la transmission.

Le FSAP est identifié au niveau de la couche réseau et de transport ITS-S par

— le numéro de port ITS enregistré connu (ITS-PN) PORT_SAM = 1 = 0x00.01, identifiant le port FSAP

recevant des S-FSAM diffusés en groupcast, et
— des ITS-PN affectés dynamiquement:

— PORT_DYN_FSAM identifiant le port FSAP qui reçoit les S-FSAM diffusés en unicast. L’affectation

dynamique est effectuée dans l’ITS-SU qui transmet les S-FSRM;

— PORT_DYN_FSRM identifiant le port FSAP qui reçoit les S-FSRM diffusés en unicast. L’affectation

dynamique est effectuée dans l’ITS-SU qui transmet les S-FSAM;

Comme l’indique le Tableau 1; voir également le paragraphe 7.3 à propos des numéros de ports ITS.

Tableau 1 — Numéros de ports ITS du FSAP
Sens ITS-PN source ITS-PN de destination Mode MAC
De l’avertisseur du PORT_DYN_FSRM PORT_SAM Groupcast
service à l’utilisateur (broadcast ou multicast)
du service
PORT_DYN_FSAM Unicast
De l’utilisateur du PORT_SAM PORT_DYN_FSRM
service à l’avertisseur
PORT_DYN_FSAM
du service

NOTE Le présent document ne précise pas les modalités de réalisation d’une transmission multicast de

S-FSAM.

Les transmissions unicast de S-FSRM et de S-FSAM peuvent être répétées, par ex. après un délai

d’expiration («timeout») pour une confirmation respective, tel que le définit la mise en œuvre.

Le FSAP est ensuite identifié par:

— l’ITS AID 2.113.664; voir également le paragraphe 7.4. La présentation en codage p-encoding (règles

de codage compact non alignées ASN.1) de ce numéro de type ASN.1 ITSaid spécifié dans l’ISO 17419

est 0pE0.00.00.00, c’est-à-dire qu’elle peut être contenue dans un champ de quatre octets.

Une mise en œuvre supportant la gestion des chemins d’accès et des flux doit être conforme à

l’ISO 24102-6.

Une mise en œuvre d’ITS-SU distribuée, c’est-à-dire une ITS-SU comprenant plusieurs ITS-SCU

interconnectées avec le réseau interne d’une station ITS, doit être conforme à l’ISO 24102-4.

Sachant que

— des formats de messages identiques pour l’avertissement de services sont utilisés dans l’IEEE 1609.3

[16]
(SAM WAVE) et l’ETSI TS 102 890 (ESAM) et que
[2] [16]

— les spécifications de fonctionnalités contenues dans l’IEEE 1609.3 et l’ETSI TS 102 890 sont des

sous-ensembles de la spécification du présent document,

une mise en œuvre du FSAP peut éventuellement supporter l’avertissement de services provenant de

dispositifs WAVE selon l’IEEE et l’annonce de services provenant de stations ITS selon l’ETSI en tenant

compte des éléments suivants:
— Support du WSM
© ISO 2020 – Tous droits réservés 3
---------------------- Page: 10 ----------------------
ISO 22418:2020(F)

1) La seule technologie d’accès supportée est le mode OCB de l’IEEE 802.11 (TM) OCB spécifié

dans l’IEEE 802.11(TM) (ISO 21215 avec allocation des fréquences en vigueur aux États-Unis et

des éléments spécifiques à WAVE).

2) Le seul protocole de la couche réseau et de transport supporté est le protocole de message

court WAVE (WSMP) spécifié dans l’IEEE 1609.3 (TM), qui exploite le même format de message

que le protocole FNTP avec TPID-FS zéro (ISO 29281-1).

3) Les numéros de ports ne sont pas utilisés. À la place, le message d’avertissement de service

SAM est identifié par la valeur 135 de l’ITS-AID, utilisée en tant qu’adresse de destination de la

couche de transport dans le WSMP (c’est-à-dire dans le FNTP avec TPID-FS zéro (ISO 29281-1).

4) Le SAM WAVE est identique au FSAM.

5) Le S-FSAM (FSAM à encapsulation de sécurité) exploite le même format et le même encodage

que WAVE. La sécurité WAVE est spécifiée dans l’IEEE 1609.2.

6) Le FSRM et les autres fonctionnalités, c’est-à-dire les applications obligatoires et les canaux de

service privés, ne sont pas supportés.
— Support de l’SAEM

1) La seule technologie d’accès supportée est le mode OCB de l’IEEE 802.11 (ISO 21215) avec

allocation des fréquences en vigueur dans l’Union européenne et éléments spécifiques à l’ETSI),

communément appelé ITS-G5.

2) Le seul protocole de couche réseau et de transport actuellement supporté est le protocole ETSI

GeoNetworking/ETSI Basic Transport Protocol (BTP).

3) Le SAEM est identifié par le numéro de port BTP pour le SAM spécifié dans l’ETSI TS 103 248.

4) Le SAEM est précédé de l’en-tête de message ETSI commun.
5) L’encapsulation de sécurité n’est pas spécifiée.

6) Le FSRM et les autres fonctionnalités, c’est-à-dire les applications obligatoires et les canaux de

service privés, ne sont pas supportés.

Les détails des exigences en matière de support des applications pour les communications, si elles

sont soutenues dans une mise en œuvre, sont spécifiés à l'annexe B. Les détails de la traçabilité et de la

gestion des flux, s'ils sont pris en charge dans une mise en œuvre, sont précisés à l'annexe C.

6 Architecture
6.1 Architecture de communication ITS

Le FSAP est conçu comme une fonctionnalité de la station ITS et de l’architecture de

...

Questions, Comments and Discussion

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