ETSI TS 102 723-3 V1.1.1 (2012-11)

Technical Specification
Intelligent Transport Systems (ITS);
OSI cross-layer topics;
Part 3: Interface between management entity and access layer

2 ETSI TS 102 723-3 V1.1.1 (2012-11)

Reference
DTS/ITS-0020017
Keywords
adaptation, addressing; interface, ITS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2012.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 723-3 V1.1.1 (2012-11)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Architecture . 9
4.1 General . 9
4.2 Service access point. 9
4.3 Management adaptation entity . 10
5 MI-COMMAND . 10
5.1 MI-COMMAND.request . 10
5.1.1 Function . 10
5.1.2 Semantics . 10
5.1.3 When generated . 11
5.1.4 Effect on receipt . 11
5.2 MI-COMMAND.confirm . 11
5.2.1 Function . 11
5.2.2 Semantics . 11
5.2.3 When generated . 12
5.2.4 Effect on receipt . 12
6 MI-REQUEST . 12
6.1 MI-REQUEST.request . 12
6.1.1 Function . 12
6.1.2 Semantics . 12
6.1.3 When generated . 12
6.1.4 Effect on receipt . 12
6.2 MI-REQUEST.confirm . 13
6.2.1 Function . 13
6.2.2 Semantics . 13
6.2.3 When generated . 13
6.2.4 Effect on receipt . 13
7 MI-SET. 13
7.1 MI-SET.request . 13
7.1.1 Function . 13
7.1.2 Semantics . 14
7.1.3 When generated . 14
7.1.4 Effect on receipt . 14
7.2 MI-SET.confirm . 14
7.2.1 Function . 14
7.2.2 Semantics . 14
7.2.3 When generated . 15
7.2.4 Effect on receipt . 15
8 MI-GET . 15
8.1 MI-GET.request . 15
8.1.1 Function . 15
8.1.2 Semantics . 15
ETSI
4 ETSI TS 102 723-3 V1.1.1 (2012-11)
8.1.3 When generated . 16
8.1.4 Effect on receipt . 16
8.2 MI-GET.confirm . 16
8.2.1 Function . 16
8.2.2 Semantics . 16
8.2.3 When generated . 17
8.2.4 Effect on receipt . 17
9 Management functionality . 17
10 IM-DP-COMMAND . 18
10.1 IM-DP-COMMAND.request. 18
10.1.1 Function . 18
10.1.2 Semantics . 18
10.1.3 When generated . 18
10.1.4 Effect on receipt . 18
10.2 IM-DP-COMMAND.confirm . 18
10.2.1 Function . 18
10.2.2 Semantics . 19
10.2.3 When generated . 19
10.2.4 Effect on receipt . 19
11 IM-DP-REQUEST . 19
11.1 IM-DP-REQUEST.request . 19
11.1.1 Function . 19
11.1.2 Semantics . 19
11.1.3 When generated . 20
11.1.4 Effect on receipt . 20
11.2 IM-DP-REQUEST.confirm . 20
11.2.1 Function . 20
11.2.2 Semantics . 20
11.2.3 When generated . 20
11.2.4 Effect on receipt . 21
12 IM-DP-GET . 21
12.1 IM-DP-GET.request . 21
12.1.1 Function . 21
12.1.2 Semantics . 21
12.1.3 When generated . 21
12.1.4 Effect on receipt . 21
12.2 IM-DP-GET.confirm . 21
12.2.1 Function . 21
12.2.2 Semantics . 22
12.2.3 When generated . 22
12.2.4 Effect on receipt . 22
Annex A (normative): ASN.1 module . 23
Annex B (normative): MI-COMMANDs . 24
B.1 Overview . 24
B.2 Specification . 24
B.2.1 General . 24
B.2.2 RegCmd . 24
B.2.3 CistateChng . 24
B.2.4 WakeUp . 24
B.2.5 RTScmd . 25
B.2.6 RTSackCmd . 25
B.2.7 Ricmd . 25
B.2.8 ManuCmd . 25
B.2.9 VCIcmd . 25
B.2.10 Monitor . 25
B.2.11 UnitDataCmd . 25
ETSI
5 ETSI TS 102 723-3 V1.1.1 (2012-11)
Annex C (normative): CI REQUESTs . 26
C.1 Overview . 26
C.2 Specification . 26
C.2.1 General . 26
C.2.2 RegReq . 26
C.2.3 PrioReg . 26
C.2.4 RTSreq . 26
C.2.5 RTSackReq. 26
C.2.6 Rireq . 27
C.2.7 ManuReq . 27
C.2.8 Events . 27
C.2.9 PosUpdateReq . 27
C.2.10 UnitDataReq . 27
Annex D (normative): CI parameters . 28
D.1 Overview . 28
D.2 Specification . 30
Annex E (normative): IM-DP-COMMANDs . 31
E.1 Overview . 31
E.2 Specification . 31
E.2.1 General . 31
E.2.2 Monitor . 31
E.2.3 FrameTransmissionNotification . 31
E.2.4 FrameReceptionNotification . 31
E.2.5 UpdateChannelLoadEstimate . 31
Annex F (normative): DP REQUESTs . 32
F.1 Overview . 32
F.2 Specification . 32
F.2.1 General . 32
F.2.2 Events . 32
Annex G (normative): DP parameters. 33
G.1 Overview . 33
History . 34

ETSI
6 ETSI TS 102 723-3 V1.1.1 (2012-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport System (ITS).
The present document is part 3 of a multi-part deliverable. Full details of the entire series can be found in part 1 [3].
ETSI
7 ETSI TS 102 723-3 V1.1.1 (2012-11)
Introduction
Intelligent Transport Systems (ITS) are systems to support transportation of goods and humans with information and
communication technologies in order to efficiently and safely use the transport infrastructure and transport means (cars,
trains, planes, ships). Complementary elements of ITS are standardized in various standardisation organisations such as
ISO TC204/CEN TC278 and ETSI TC ITS.
The architecture of communications in ITS (ITSC) specified in [1] and [2] introduces the ITS station reference
architecture with the internal functional blocks:
• access layer,
• networking & transport layer,
• facilities layer,
• ITS applications;
• management entity,
• security entity,
and the interfaces between these blocks.
Various general addressing mechanisms, the ITS station management information base, and the details of these
interfaces specified in this multi-part deliverable complement the general architecture of ITSC.
This multi-part deliverable partly acts as input to the standards making process for the various protocols of ITSC, but
also is built from feed-back from this process.
ETSI
8 ETSI TS 102 723-3 V1.1.1 (2012-11)
1 Scope
The present document specifies the MI interface between the management entity and the access layer of the ITS station
reference architecture.
Based on the definition of the MI interface as a service access point and the generic services and service primitives
specified in [3], the present document provides detailed specifications of possible service primitives.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture".
[2] ISO 21217: "Intelligent Transport Systems - Communications access for land mobiles (CALM) -
Architecture".
[3] ETSI TS 102 723-1: "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 1:
Architecture and addressing schemes".
[4] ETSI TS 102 723-2: "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 2:
Management information base".
[5] ETSI TS 102 723-10: "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 10:
Interface between access layer and networking & transport layer".
[6] ITU-T Recommendation X.691: "Information technology - ASN.1 encoding rules: Specification of
Packed Encoding Rules (PER)".
[7] ISO/DIS 21218: "Intelligent transport systems - Communications access for land mobiles (CALM)
- Access technology support".
[8] ISO/DIS 24102-3: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 3: Service access points".
[9] ISO 21214: "Intelligent transport systems -- Communications access for land mobiles (CALM) --
Infra-red systems".
[10] ETSI TS 102 724: "Intelligent Transport Systems (ITS); Harmonized Channel Specifications for
Intelligent Transport Systems operating in the 5 GHz frequency band".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
Not applicable.
ETSI
9 ETSI TS 102 723-3 V1.1.1 (2012-11)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] to [4], [7] and [8] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in [1] to [4], [7] and [8] apply.
4 Architecture
4.1 General
Figure 1 shows the generic architecture of the access layer and the management entity as specified in [1] and [2]. The
MI interface and parts of the layer management including the management adaptation entity (MAE) presented in
figure 1 are subject of the present document.
IN
Communication
t
n
e adaptation
r
m
I e sub-layer (CAL)
e
y
S
y
g
t
a
i
a
t
L
n
n
a
E
t m Data Link Layer
n
e
(DLL)
m
e
g
t
)
a n
n E
n
e
o
a A
i
m t
M I a M
e
(
t
g
M
p
a y
t Physical Layer (PHY)
a
i
n
t
d
a
n
a
e
M
Figure 1: Architecture
4.2 Service access point
The MI interface is specified as a service access point (SAP) in the present document.
The following generic services applicable for the MI-SAP:
• XY-COMMAND
• XY-REQUEST
• XY-SET
• XY-GET
are specified in [3].
ETSI
10 ETSI TS 102 723-3 V1.1.1 (2012-11)
Compliant with the specifications in [3], the management entity presented in figure 1 shall provide the services:
• MI-COMMAND
• MI-REQUEST
• MI-SET
• MI-GET
and the related service primitives.
In addition, the following DCC-Profile specific services shall be provided by the management entity to CIs/VCIs that
support DCC (in particular, to CIs/VCIs on G5A and G5B):
• IM-DP-COMMAND
• IM-DP-REQUEST
• IM-DP-GET
The service primitives do not operate on a CI/VCI, but on a specific (or all) DCC Profiles. DCC Profiles are maintained
by the Management Layer; therefore these services shall be offered by the Management Layer to the Access Layer. For
that reason, the order of prefix is IM instead of MI. A corresponding IM-DP-SET shall not be provided.
A service access point (SAP) not necessarily is an observable and thus testable interface. The detailed technical
specification of MI-SAP, its services and related service primitives at the level of ASN.1 thus is optional. In case this
option is selected, the implementation shall be compliant with the ASN.1 specification presented in
ISO/DIS 24102-3 [8].
Compliance with the functional specification is required in case the functional behaviour is needed in a specific
implementation
Thus the present document specifies elements of a tool-box.
4.3 Management adaptation entity
The concept of a management adaptation entity (MAE) is specified in [1] and [2].
Further details are specified in clause 9.
5 MI-COMMAND
5.1 MI-COMMAND.request
5.1.1 Function
The management service primitive MI-COMMAND.request allows the management entity to trigger an action in a
specific communication interface (CI).
5.1.2 Semantics
The parameters of the management service primitive MI-COMMAND.request shall be as follows:
• MI-COMMAND.request (
MAC-ID,
CommandRef,
MI-Command
)
ETSI
11 ETSI TS 102 723-3 V1.1.1 (2012-11)
Table 1: Parameters of the service primitive MI-COMMAND.request
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a physically
available CI or of a logical
instance of it. Logical
instances of a CI are named
"Virtual Communication
Interface" (VCI).
CommandRef INTEGER 0 to 255 Unique cyclic reference
number of request.
MI-Command.No CHOICE Integer number See annex B.1.
.Value
MI-Command.Value Depends on MI-Command.No

See ASN.1 definitions in annex A.
5.1.3 When generated
The management service primitive MI-COMMAND.request shall be generated by the management entity when the
CI / VCI shall perform an action.
5.1.4 Effect on receipt
On receipt of the management service primitive MI-COMMAND.request by a CI / VCI, the requested action shall be
performed.
5.2 MI-COMMAND.confirm
5.2.1 Function
The management service primitive MI-COMMAND.confirm reports the result of a previous MI-COMMAND.request.
5.2.2 Semantics
The parameters of the management service primitive MI-COMMAND.confirm shall be as follows:
• MI-COMMAND.confirm (
MAC-ID,
CommandRef,
ErrStatus
)
Table 2: Parameters of the service primitive MI-COMMAND.confirm
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a
CI / VCI.
CommandRef INTEGER 0 to 255 Unique cyclic reference
number of request
ErrStatus ENUMERATED Specified in [3] Indicates error status of
request
See ASN.1 definitions in annex A.
ETSI
12 ETSI TS 102 723-3 V1.1.1 (2012-11)
5.2.3 When generated
The management service primitive MI-COMMAND.confirm shall be generated by the CI / VCI upon performance of a
previous MI-COMMAND.request.
An undefined COMMAND shall be acknowledged with ErrStatus 5 "INVALID COMMAND/REQUEST NUMBER".
5.2.4 Effect on receipt
On receipt of this primitive, the management entity shall evaluate ErrStatus and act accordingly. Details are outside the
scope of the present document.
6 MI-REQUEST
6.1 MI-REQUEST.request
6.1.1 Function
The management service primitive MI-REQUEST.request allows a CI / VCI to trigger an action in the management
entity.
6.1.2 Semantics
The parameters of the management service primitive MI-COMMAND.request shall be as follows:
• MI-REQUEST.request (
MAC-ID,
CommandRef,
MI-Request
)
Table 3: Parameters of the service primitive MI-REQUEST.request
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a CI / VCI
CommandRef INTEGER 0 to 255 Unique cyclic reference number
of request
MI-Request.No CHOICE Integer number See annex C
.Value
MI-Request.Value Depends on MI-Request.No

See ASN.1 definitions in annex A.
6.1.3 When generated
The management service primitive MI-REQUEST.request shall be generated by the CI / VCI when the management
entity shall perform an action.
6.1.4 Effect on receipt
On receipt of the management service primitive MI-REQUEST.request by the management entity, the requested action
shall be performed.
ETSI
13 ETSI TS 102 723-3 V1.1.1 (2012-11)
6.2 MI-REQUEST.confirm
6.2.1 Function
The management service primitive MI-REQUEST.confirm reports the result of a previous MI-REQUEST.request.
6.2.2 Semantics
The parameters of the management service primitive MI-REQUEST.confirm shall be as follows:
• MI-REQUEST.confirm (
MAC-ID,
CommandRef,
ErrStatus
)
Table 4: Parameters of the service primitive MI-REQUEST.confirm
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a CI /
VCI.
CommandRef INTEGER 0 to 255 Unique cyclic reference
number of request
ErrStatus ENUMERATED Specified in [3] Indicates error status of
request
See ASN.1 definitions in annex A.
6.2.3 When generated
The management service primitive MI-REQUEST.confirm shall be generated by management entity upon performance
of a previous MI-REQUEST.request.
An undefined REQUEST shall be acknowledged with ErrStatus 5 "INVALID COMMAND/REQUEST NUMBER".
6.2.4 Effect on receipt
On receipt of this primitive, the CI / VCI entity shall evaluate ErrStatus and act accordingly. Details are outside the
scope of the present document.
7 MI-SET
7.1 MI-SET.request
7.1.1 Function
The management service primitive MI-SET.request allows setting of a CI / VCI parameter by the management entity.
ETSI
14 ETSI TS 102 723-3 V1.1.1 (2012-11)
7.1.2 Semantics
The parameters of the management service primitive MI-SET.request shall be as follows:
• MI-SET.request (
MAC-ID,
CommandRef,
Sequence of I-Param
)
Table 5: Parameters of the service primitive MI-SET.request
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3]. Unique identifier of a CI / VCI.
CommandRef INTEGER Integer number Unique cyclic reference number of
request
INTEGER 0 to 255 Number of subsequent I-Param
elements
I-Param.No CHOICE 0 to 255 See annex D.
I-Param.Value Depends on I-Param.No

See ASN.1 definitions in annex A.
7.1.3 When generated
The management service primitive MI-SET.request shall be generated by the management entity when CI / VCI
parameters shall be set.
7.1.4 Effect on receipt
On receipt of the management service primitive MI-SET.request by the CI / VCI, the selected parameters shall be set, if
applicable.
7.2 MI-SET.confirm
7.2.1 Function
The management service primitive MI-SET.confirm reports the result of a previous MI-SET.request
7.2.2 Semantics
The parameters of the management service primitive MI-SET.confirm shall be as follows:
• MI-SET.confirm (
MAC-ID,
CommandRef,
Sequence of Errors OPTIONAL
)
ETSI
15 ETSI TS 102 723-3 V1.1.1 (2012-11)
Table 6: Parameters of the service primitive MI-SET.confirm
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a physically
available CI or of a logical instance of it.
Logical instances of a CI are named
"Virtual Communication Interface" (VCI)
CommandRef INTEGER 0 to 255 Unique cyclic reference number of
request
INTEGER 0 to 255 Number of subsequent Errors elements
Errors.I-paramNo INTEGER See annex D See annex D
Errors.ErrStatus ENUMERATED Specified in [3] Indicates error status of request

See ASN.1 definitions in annex A.
7.2.3 When generated
The management service primitive MI-COMMAND.confirm shall be generated by the CI / VCI upon performance of a
previous MI-COMMAND.request.
A request to set a defined "read only" parameter shall be acknowledged with ErrStatus 7 "ACCESS VIOLATION".
A request to set an undefined parameter shall be acknowledged with ErrStatus 2 "INVALID PARAMETER
NUMBER".
A request to set a defined parameter with an illegal value shall be acknowledged with ErrStatus 3 "INVALID
PARAMETER VALUE".
A request to set a defined parameter with an illegal type of value shall be acknowledged with either ErrStatus 1
"UNSPECIFIED FAILURE", or with ErrStatus 3 "INVALID PARAMETER VALUE", or with ErrStatus 8 "INVALID
TYPE".
7.2.4 Effect on receipt
On receipt of this primitive, the management entity shall evaluate Errors and act accordingly. Details are outside the
scope of the present document.
8 MI-GET
8.1 MI-GET.request
8.1.1 Function
The management service primitive MI-GET.request allows retrieving actual values of CI / VCI parameters.
8.1.2 Semantics
The parameters of the management service primitive MI-GET.request shall be as follows:
• MI-GET.request (
MAC-ID,
CommandRef,
Sequence of I-Param.No
)
ETSI
16 ETSI TS 102 723-3 V1.1.1 (2012-11)
Table 7: Parameters of the service primitive MI-GET.request
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a CI / VCI
CommandRef INTEGER Integer number Unique cyclic reference number
of request
INTEGER 0 to 255 Number of subsequent I-
Param.No elements
I-Param.No INTEGER 0 to 255 See annex D

See ASN.1 definitions in annex A.
8.1.3 When generated
The management service primitive MI-GET.request shall be generated by the management entity when CI / VCI when
actual values of CI / VCI parameters shall be retrieved.
8.1.4 Effect on receipt
On receipt of the management service primitive MI-GET.request by the CI / VCI, the values of the selected parameters
shall be reported to the management entity, if applicable.
8.2 MI-GET.confirm
8.2.1 Function
The management service primitive MI-GET.confirm reports the result of a previous MI-GET.request.
8.2.2 Semantics
The parameters of the management service primitive MI-GET.confirm shall be as follows:
• MI-GET.confirm (
MAC-ID,
CommandRef,
Sequence of I-Param
)
Table 8: Parameters of the service primitive MI-GET.confirm
Name ASN.1 type Valid range Description
MAC-ID Structure as specified in [3] Specified in [3] Unique identifier of a physically
available CI or of a logical
instance of it. Logical instances of
a CI are named "Virtual
Communication Interface" (VCI).
CommandRef INTEGER 0 to 255 Unique cyclic reference number of
request
INTEGER 0 to 255 Number of subsequent I-Param
elements
I-Param.No CHOICE See annex D Sequence of CI / VCI parameters
I-Param.Value
See ASN.1 definitions in annex A.
ETSI
17 ETSI TS 102 723-3 V1.1.1 (2012-11)
8.2.3 When generated
The management service primitive MI-GET.confirm shall be generated by the CI / VCI upon performance of a previous
MI-GET.request.
A request to get the value of a defined "write only" parameter shall be acknowledged with ErrStatus 7 "ACCESS
VIOLATION".
A request to get the value of an undefined parameter shall be acknowledged with ErrStatus 2 "INVALID
PARAMETER NUMBER".
8.2.4 Effect on receipt
The management entity shall evaluate the parameter values and act accordingly. If any errors occurred in the processing
of the related MI-GET.request, the MI-GET.confirm shall contain at least the entry Param.No = 255, where I-
Param.Value shall explain the details of the error as specified in annex D.
Further details are outside the scope of present document.
9 Management functionality
The local management presented in figure 1 supports the functionality related to the MI-SAP.
This functionality shall be as specified in [7] and as further specified in the present document. A specification in the
present document shall prevail a specification in [7].
Every CI shall maintain its state according to the state diagram in figure 2.

Figure 2: CI state diagram
NOTE: This state diagram is identical to the one presented in [7] except the name of a single transition (resume).
The correct transition name is already used in [8].
ETSI
18 ETSI TS 102 723
...