Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 1: Local management

ISO 24102-1:2013 provides specifications for intelligent transport systems (ITS) station management to be compliant with the ITS station reference architecture and the set of communications access for land mobiles (CALM) related standards. Local ITS station management protocols are specified by means of management messages and data that flow between the ITS station management entity and the security entity, the application entity, and the various communication protocol layers of the ITS station reference architecture specified in ISO 21217.

Systèmes intelligents de transport — Accès aux communications des services mobiles terrestres (CALM) — Gestion des stations ITS — Partie 1: Gestion locale

General Information

Status
Withdrawn
Publication Date
23-Jun-2013
Withdrawal Date
23-Jun-2013
Current Stage
9599 - Withdrawal of International Standard
Completion Date
31-Oct-2018
Ref Project

Relations

Buy Standard

Standard
ISO 24102-1:2013 - Intelligent transport systems -- Communications access for land mobiles (CALM) -- ITS station management
English language
28 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 24102-1
First edition
2013-07-01
Intelligent transport systems —
Communications access for land
mobiles (CALM) — ITS station
management —
Part 1:
Local management
Systèmes intelligents de transport — Accès aux communications des
services mobiles terrestres (CALM) — Gestion des stations ITS —
Partie 1: Gestion locale
Reference number
ISO 24102-1:2013(E)
©
ISO 2013

---------------------- Page: 1 ----------------------
ISO 24102-1:2013(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2013
All rights reserved. Unless otherwise specified, 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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 24102-1:2013(E)

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 2
5 Requirements . 2
6 CI basic management . 3
6.1 General . 3
6.2 CI status . 3
6.3 Cross-CI prioritization . 8
6.4 VCI I-Parameters.10
6.5 Regulatory information management .11
6.6 Manufacturer access .11
7 Congestion control .11
8 Neighbour list .13
9 Paths and flows.13
10 Legacy CI .15
10.1 Registration .15
10.2 CI states .16
11 Management data elements .16
11.1 ITS-SCU list .16
11.2 VCI list .16
11.3 VCI performance parameter list .16
11.4 Cross-CI prioritization list .17
11.5 Application requirements list .18
12 Conformance
.19
13 Test methods .19
Annex A (normative) ASN.1 modules .20
Annex B (normative) Management parameters .23
Bibliography .28
© ISO 2013 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 24102-1:2013(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. 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. 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.
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
ISO 24102 consists of the following parts, under the general title Intelligent transport systems —
Communications access for land mobiles (CALM) — ITS station management:
— Part 1: Local management
— Part 3: Service access points
— Part 4: ITS station-internal management communications
— Part 5: Fast service advertisement protocol (FSAP)
The following parts are under preparation:
— Part 2: Remote management
— Part 6: Path and flow management
iv © ISO 2013 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 24102-1:2013(E)

Introduction
This International Standard is part of a family of International Standards for communications access for
land mobiles (CALM). An introduction to the whole set of International Standards is provided in ISO 21217.
This part of ISO 24102 is part 1 of a multipart International Standard which determines the intelligent
transport systems (ITS) local station management.
The ITS station management entity provides functionality related to the management of communication
protocol layers and the security entity presented in the ITS station reference architecture specified in
ISO 21217 and presented in Figure 1, and in line with the general ITS architecture specified in ISO 21217.
Applications
API
MS
Facilities
NF
Networking &
Transport
IN
Access
Communications
Figure 1 — ITS station reference architecture with named interfaces
ITS station management is specified as a distributed process, where no supervisory entity is employed.
© ISO 2013 – All rights reserved v
Management
MI MN MF
SI SN SF
Security

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 24102-1:2013(E)
Intelligent transport systems — Communications access
for land mobiles (CALM) — ITS station management —
Part 1:
Local management
1 Scope
This part of ISO 24102 provides specifications for intelligent transport systems (ITS) station management
to be compliant with the ITS station reference architecture and the set of communications access for
land mobiles (CALM) related standards.
Local ITS station management protocols are specified by means of management messages and data that
flow between the ITS station management entity and
— the security entity,
— the application entity, and
— the various communication protocol layers
of the ITS station reference architecture specified in ISO 21217.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. 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 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture
ISO 21218, Intelligent transport systems — Communications access for land mobiles (CALM) — Access
technology support
ISO 24102-3, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station
management — Part 3: Service access points
ISO 24102-4, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station
management — Part 4: Station-internal management communications
ETSI TS 102 797-1, Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT);
Test specifications for Intelligent Transport Systems, Communications access for land mobiles (CALM), ITS
station management (ISO 24102); Part 1: Protocol Implementation Conformance Statement (PICS) proforma
ETSI TS 102 797-2, Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT);
Test specifications for Intelligent Transport Systems, Communications access for land mobiles (CALM), ITS
station management (ISO 24102); Part 2: Test Suite Structure and Test Purposes (TSS & TP)
ETSI TS 102 797-3, Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT);
Test specifications for Intelligent Transport Systems, Communications access for land mobiles (CALM), ITS
station management (ISO 24102); Part 3: Abstract Test Suite (ATS) and partial PIXIT information
© ISO 2013 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 24102-1:2013(E)

3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21217, ISO 21218, ISO 24102-3,
and the following apply.
3.1
regulatory information
set of regulatory requirements for radio wave emission
3.2
ITS-S communication unit
addressable instance of the ITS station reference architecture comprising as a minimum the ITS-S router
functionality
3.3
ITS-S path
part of a communication path between a source node and an anchor node being uniquely identified by a
LinkID (identifying a CI in the source node and the next hop node) and by the anchor node
4 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21217, ISO 21218, ISO 24102-3,
and the following apply.
ITS-SCU ITS station communication unit
ITS-SSI ITS station state information
LDM local dynamic map
n.a. not applicable
PDUs protocol data units
QoS quality of service
RI regulatory information
5 Requirements
The ITS station management entity provides functionality specified in the various parts of this multipart
International Standard:
1) The functionality of local ITS station management specified in this part of ISO 24102.
2) The functionality of remote ITS station management will be specified in ISO 24103-2.
3) The functionality of management service access points specified in ISO 24102-3.
4) The functionality of ITS station-internal management communications specified in ISO 24102-4.
5) The functionality of the “Fast Service Advertisement Protocol” (FSAP) specified in ISO 24103-5.
General management functionality shall be as specified in this part of ISO 24102.
Means to secure the access to management functionality need to be specified within the global context
of CALM security. Details are outside the scope of this part of ISO 24102.
2 © ISO 2013 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 24102-1:2013(E)

Detailed mandatory requirements are specified in the following clauses of this part of ISO 24102.
— Clause 6 specifies basic management procedures related to communication interfaces.
— Clause 7 describes congestion control.
— Clause 8 specifies neighbour lists and the link to the “Local Dynamic Map” (LDM) application.
— Clause 9 describes the concept of flow and path management.
— Clause 10 specifies management of “Legacy CIs”.
— Clause 11 specifies management data elements.
— Clause 12 specifies conformance declaration.
— Clause 13 specifies test methods.
— Annexes provide further mandatory requirements.
6 CI basic management
6.1 General
Basic management procedures related to communication interfaces (CI) shall access a “(Virtual)
Communication Interface” (CI/VCI) via the MI-SAP specified in ISO 24102-3.
Any change of status of a CI/VCI shall be reported to all ITS-SCUs with ITS-SCU-Mngmt-Request “VCI-
update” specified in ISO 24102-4. Reception of such a notification shall not be acknowledged.
Management communications with CIs/VCIs in other ITS-SCUs shall be with ITS station-internal
management communication PDUs “MI-rcmd”, “MI-rreq”, “MI-rget”, and “MI-rset” specified in ISO 24102-4.
Although SAPs and the related service primitives specified in ISO 24102-3 cannot be tested and are not
mandatory, in the context of this part of ISO 24102, the elements of the service primitives may be an
integral part of PDUs exchanged between physical entities in an ITS station using “ITS station-internal
management communications” specified in ISO 24102-4. As PDUs are testable, those elements of service
primitives that are part of a PDU become testable.
6.2 CI status
6.2.1 CI state machine
Figure 2 shows the CI state machine specified in ISO 21218.
© ISO 2013 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 24102-1:2013(E)

power on /
activate
deregister
not_existent
existent
inactive
deregister
activate
register
inactivate
deregister
registered
deregister
suspended
inactivate
inactivate
delete VCI
deregister
create VCI
resume
active
disconnect
suspend
connect
connected
Figure 2 — CI state machine ISO 21218
6.2.2 Registration
Registration of a CI at the ITS station management entity is the process to make the CI known to the ITS
station management entity, and to make it addressable via a unique Link-ID (see ISO 21218).
Registration of a CI shall be done as specified in ISO 21218.
The medium identifier MedID, part of the Link-ID specified in ISO 21218, and assigned to a CI during the
process of registration shall be unique within an ITS-SCU.
Upon successful registration of a CI, the ITS station management entity shall create an entry in the VCI
list with the values specified in Table 1.
Table 1 — Entry in VCI list upon registration of CI
LocalCIID Medium CI Status ConnectMode RemoteCIID
Identifying the I-Parameter I-Parameter CIstatus I-parameter “Con- Not applicable.
CI as specified in “MedType” as speci- equal to “registered”, nect”.
Value identifying
ISO 21218. fied in ISO 21218. see ISO 21218.
the CI as specified in
ISO 21218.
4 © ISO 2013 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 24102-1:2013(E)

6.2.3 VCI creation
Creation of a VCI may be done
— upon request of the ITS station management entity, or
— by the CI on its own.
Creation of a VCI shall be done as specified in ISO 21218.
Upon successful creation of a VCI, the ITS station management entity
— shall create an entry in the VCI list with the values specified in Tables 2, 3, and 4, as applicable, and
— shall create initial entries in the forwarding tables of all supported networking protocols using MN-
COMMAND “FWTset” specified in ISO 24102-3, if applicable.
Table 2 — Entry in VCI list indicating an active CI
LocalCIID Medium CI Status ConnectMode RemoteCIID
Identifying the Set equal to I-param- Set equal to I-Param- Set equal to I-param- Not applicable.
CI as specified in eter “Medium”. See eter CIstatus. See eter “Connect”. See
Value identifying
ISO 21218. ISO 21218. ISO 21218. ISO 21218.
the CI as specified in
ISO 21218.
Table 3 — Entry in VCI List upon creation of a broadcast VCI
LocalCIID Medium CI Status ConnectMode RemoteCIID
As specified in Set equal to I-param- Set equal to I-Param- Set equal to I-param- As specified in
ISO 21218. eter “Medium”. See eter CIstatus. See eter “Connect”. See ISO 21218.
ISO 21218. ISO 21218. ISO 21218.
Table 4 — Entry in VCI List upon creation of a multicast VCI
LocalCIID Medium CI Status ConnectMode RemoteCIID
As specified in Set equal to I-Param- Set equal to I-Param- Set equal to I-param- As specified in
ISO 21218. eter “Medium”. See eter CIstatus. See eter “Connect”. See ISO 21218.
ISO 21218. ISO 21218. ISO 21218.
Upon request of an ITS-S networking and transport layer protocol to create a VCI with a specific
relation to a peer station, of which the MAC address is known a priori, and with specific settings of the
I-parameters, the ITS station management entity shall create the VCI and perform all required settings.
The state of the CI shall be set to “connected” (see Table 5). The ITS station management entity shall
update the VCI list and the forwarding tables.
6.2.4 Deregistration
Deregistration of a CI at the ITS station management entity is the process reversal to the registration
process. Successful deregistration is a prerequisite to remove a CI from the system during operation.
Deregistration of a CI may be done
— by the CI on its own,
— upon request of the ITS station management entity as specified in this part of ISO 24102.
Deregistration of a CI shall be done as specified in ISO 21218.
© ISO 2013 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO 24102-1:2013(E)

Upon successful deregistration, the ITS station management entity
— shall delete all entries of this CI and the related VCIs in the VCI list, and
— shall delete all entries of this CI and the related VCIs in the forwarding tables using MN-COMMAND
“FWTdelete” specified in ISO 24102-3, if applicable.
6.2.5 Inactivation
Inactivation of a CI is the process to reset the CI and to block all subsequent communications.
Inactivation of a CI may be done upon request of the ITS station management entity.
NOTE Conditions when a CI shall or may be inactivated are not specified in this part of ISO 24102.
Inactivation of a CI shall be done as specified in ISO 21218.
Upon successful inactivation, the ITS station management entity
— shall change the status element of this CI in the VCI list to “inactive”, and shall delete the entries of
all related VCIs in the VCI list, and
— shall change the CI state of this CI in the forwarding tables to “inactive”, and shall delete the
entries of all related VCIs in the forwarding tables using MN-COMMAND “FWTdelete” specified in
ISO 24102-3, if applicable.
6.2.6 Activation
Activation of a CI is the process to enable communications in an inactive CI. Upon successful activation,
the ITS station management entity shall change the status element of this CI to the value “registered”.
Activation of a CI may be done upon request of the ITS station management entity as specified in this
part of ISO 24102.
NOTE Requirements on events upon which a CI shall or may be activated are not specified in this part of ISO 24102.
Activation of a CI shall be done as specified in ISO 21218.
Upon successful activation, the ITS station management entity shall change the status element of this CI
in the VCI list to the value “registered”.
6.2.7 Suspension
Suspension of a CI is the process to put all communications of a CI on hold, without deleting any packets
or state variables.
Suspension of a CI may be done upon request of the ITS station management entity as specified in this
part of ISO 24102.
NOTE Requirements when a CI shall or may be suspended are not specified in this part of ISO 24102.
Suspension of a CI shall be done as specified in ISO 21218.
Upon successful suspension, the ITS station management entity shall change
— the status element of this CI and the related VCIs in the VCI list to “suspended”, and
— the CI state of this CI and the related VCIs in the forwarding tables to “suspended” using MN-
COMMAND “FWTupdate” specified in ISO 24102-3, if applicable.
6 © ISO 2013 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 24102-1:2013(E)

6.2.8 Resuming
Resuming of a CI is the process to enable communications in a suspended CI.
Resuming of a CI may be done upon request of the ITS station management entity.
NOTE 1 Conditions when a CI shall or may be resumed are not specified in this part of ISO 24102.
Resuming of a CI shall be done as specified in ISO 21218.
Upon successful resuming, the ITS station management entity shall
— change the status element of this CI in the VCI list to “active” and the status of the related VCIs in the
VCI list to “connected”, and
— change the CI state of this CI and the related VCIs in the forwarding tables to “connected” using MN-
COMMAND “FWTupdate” specified in ISO 24102-3, if applicable.
NOTE 2 This VCI state might be wrong. However, this will be resolved automatically.
6.2.9 Connection
Connection establishment of a CI is the process to initiate and maintain a relation to a specific peer
station. Distinction is made according to the CI access class.
Connection of a VCI may be done
— by the CI on its own,
— upon request of the ITS station management entity as specified in this part of ISO 24102.
Connection of a VCI shall be done as specified in ISO 21218.
Upon successful connection to a peer station, the ITS station management entity shall
— create an entry in the VCI list with the values specified in Table 5, and
— change the CI state of this VCI in the forwarding tables to “connected”, using MN-COMMAND
“FWTupdate” specified in ISO 24102-3.
Table 5 — Entry in VCI list upon successful connection of a unicast VCI
LocalCIID Medium CI Status ConnectMode RemoteCIID
As specified in Set equal to I-param- Set equal to I-Param- Set equal to I-param- Value identifying the
ISO 21218. eter “Medium”. See eter CIstatus. See eter “Connect”. See peer station as speci-
ISO 21218. ISO 21218. ISO 21218. fied in ISO 21218.
NOTE Access technologies may either be uniquely identified in the OSI MAC layer by means of a 48-bit MAC
address, or by other means. As specified in ISO 21218, RemoteCIID contains this information.
6.2.10 Disconnection
Disconnection of a VCI is the process to close relations to a peer station. Distinction is made according to
the CI access class as specified in ISO 21218.
Disconnection of a VCI may be done
— by the CI on its own,
— upon request of the ITS station management entity as specified in this part of ISO 24102.
© ISO 2013 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 24102-1:2013(E)

Disconnection of a VCI shall be done as specified in ISO 21218. Upon successful disconnection of a VCI by
the ITS station management entity or by the CI, the ITS station management entity shall
— update the entry of the VCI in the VCI list, and
— change the CI state of this VCI in the forwarding tables to “active”, using MN-COMMAND “FWTupdate”
specified in ISO 24102-3, if applicable.
6.2.11 Deletion of a VCI
Deletion of a VCI may be done
— by the CI on its own,
— upon request of the ITS station management entity as specified in this part of ISO 24102.
Deletion of a VCI shall be done as specified in ISO 21218.
Upon successful deletion of a VCI, the ITS station management entity shall delete
— the entry in the VCI list, and
— the entries of this VCI in the forwarding tables using MN-COMMAND “FWTdelete” specified in
ISO 24102-3, if applicable.
6.3 Cross-CI prioritization
6.3.1 General
Wireless TX-VCIs in an ITS station might suffer from cross-interference. This clause considers the case
that at least two local TX-VCIs, e.g. using the same medium, need to be synchronized in order to avoid
cross-interference. The procedure to synchronize transmission of multiple CIs based on user priority is
called “Cross-CI prioritization”.
The design and integration goal shall be to avoid such cross-interference as far as possible. A possible
means to achieve this is proper assignment of orthogonal wireless communication channels to the CIs.
Priority management across CIs is a somewhat slow process which requires involvement of the ITS
station management entity for every packet to be prioritized.
The procedure of cross-CI prioritization is an optional procedure. The part of it related to the CI is
specified in ISO 21218.
NOTE An implicit option of cross-CI prioritization is CI protection. A CI to be protected is a device for radio
communications such as passive transponder systems based on [2] and [3] which cannot harm other CIs.
In CI protection mode, the CI to be protected does not need to await the positive acknowledgement of a
prioritization request, but may try to perform communication at any time.
6.3.2 Registration of CI for prioritization request
Upon request of a CI to register for the cross-CI prioritization procedure by means of the MI-REQUEST
“PrioReg” specified in ISO 24102-3, the ITS station management entity shall
— create the header of the prioritization table for this CI (see Table 10) containing the Link-ID.LocalCIID
of the CI and the timeout information. The list entries “Request number”, “Priority”, and “Status”, if
already created, shall be set to zero,
— evaluate the list of MedType information contained in “PrioReg” in order to identify the LocalCIID of
all possible interferers in the ITS station, and
8 © ISO 2013 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 24102-1:2013(E)

— create an entry in the prioritization table for each identified interferer with the interferer LocalCIID
and with “Status Interferer” set to “released”.
6.3.3 Prioritization request
As specified in ISO 21218, a CI may request cross-CI prioritization by means of the MI-REQUEST “RTSreq”
specified in ISO 24102-3.
Upon reception of such a request, the ITS station management entity shall compare the pres
...

Questions, Comments and Discussion

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