ETSI TS 102 797-2 V1.2.1 (2014-06)

Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 2: Test Suite Structure and Test Purposes (TSS & TP)

RTS/ITS-00267

General Information

• Status: Published
• Publication Date: 11-Jun-2014
• Technical Committee: ITS WG2 - Architecture and Cross Layer
• Current Stage: 12 - Completion
• Due Date: 04-Jul-2014
• Completion Date: 12-Jun-2014

Standards Content (Sample)

ETSI TS 102 797-2 V1.2.1 (2014-06)






Technical Specification
Intelligent Transport Systems (ITS);
Communications Access for Land Mobiles (CALM);
Test specifications for ITS station management (ISO 24102);
Part 2: Test Suite Structure and Test Purposes (TSS & TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 797-2 V1.2.1 (2014-06)



Reference
RTS/ITS-00267
Keywords
CALM, ITS, testing, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

Important notice
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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 or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
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

---------------------- Page: 2 ----------------------
3 ETSI TS 102 797-2 V1.2.1 (2014-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 5
4 Test suite structure . 6
5 Test purpose basics . 7
5.1 TP definition conventions . 7
5.2 TP identifier naming conventions . 7
5.3 Rules for behaviour description . 7
5.4 Sources of TP definitions . 7
5.5 TP proforma . 8
5.6 PICS mnemonics . 8
6 TPs for IICP . 9
6.1 Management . 9
6.1.1 Valid behaviour tests . 9
6.1.2 Invalid behaviour tests . 11
6.2 Communications . 12
6.2.1 Valid behaviour tests . 12
6.2.2 Invalid behaviour tests . 20
7 TPs for FSAP . 22
7.1 Service provider . 22
7.1.1 Combined ITS-S host and ITS-S router . 22
7.1.1.1 Valid behaviour tests . 22
7.1.1.2 Invalid behaviour tests . 25
7.1.2 ITS-S host only . 26
7.1.2.1 Valid behaviour tests . 26
7.1.2.2 Invalid behaviour tests . 28
7.1.3 ITS-S router only . 29
7.1.3.1 Valid behaviour tests . 29
7.1.3.2 Invalid behaviour tests . 31
7.2 Service user . 32
7.2.1 Combined ITS-S host and ITS-S router . 32
7.2.1.1 Valid behaviour tests . 32
7.2.1.2 Invalid behaviour tests . 34
7.2.2 ITS-S host only . 34
7.2.2.1 Valid behaviour tests . 34
7.2.2.2 Invalid behaviour tests . 34
7.2.3 ITS-S router only . 35
7.2.3.1 Valid behaviour tests . 35
7.2.3.2 Invalid behaviour tests . 35
History . 36

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 797-2 V1.2.1 (2014-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS).
The present document is part 2 of a multi-part deliverable covering Communications Access for Land Mobiles
(CALM); Test specifications for ITS station management (ISO 24102), as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) specification";
Part 2: "Test Suite Structure and Test Purposes (TSS & TP)";
Part 3: "Abstract Test Suite (ATS) and partial PIXIT proforma".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 797-2 V1.2.1 (2014-06)
1 Scope
The present document provides the test suite structure and test purpose specification for the ISO protocols specified in
ISO 24102-4 [1] and ISO 24102-5 [2] in compliance with the relevant requirements, and in accordance with the relevant
guidance given in EG 202 798 [i.1].
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] ISO 24102-4:2013: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 4: Station-internal management communications".
[2] ISO 24102-5:2013: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 5: Fast service advertisement protocol (FSAP)".
[3] ETSI TS 102 797-1 (V1.2.1): "Intelligent Transport Systems (ITS); Communications Access for
Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102);
Part 1: Protocol Implementation Conformance Statement (PICS) specification".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and
interoperability testing".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO 24102-4 [1], ISO 24102-5 [2] and
EG 202 798 [i.1] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO 24102-4 [1], ISO 24102-5 [2] and
EG 202 798 [i.1] apply.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 797-2 V1.2.1 (2014-06)
4 Test suite structure
In general, the conformance test system architecture presented in the ITS testing framework EG 202 798 [i.1] extended
as illustrated in figure 1 applies.
c
e
d
o
C

Figure 1: General conformance test system architecture for SUTs
Such SUTs which support the "ITS station-internal Management Communications Protocol" (IICP) ISO 24102-4 [1]
may benefit from the conformance test system architecture illustrated in figure 2, where the access to the IUT is
performed via remote access to the management SAPs applying IICP. This may be applied in general for all three ports
(utPort, ltPort, cnPort). In case of testing IICP itself, the ITS lower layers end up in the ITS station-internal network.
ITS test system SUT
Upper tester
Test control
application
Upper tester
and
configuration /
TTCN-3 test components
notification
IUT
transport
ITS lower
ltPort utPort cnPort
Protocol in ITS
layers
Protocol stack management entity
Test adapter
for access to
Configuration
ITS station-
ITS lower Upper tester
/ notification
internal
layers transport
transport
network
Dispatcher
Upper tester and configuration / notification
transport link
ITS station-internal network
Lower layers link
(maybe the ITS station-internal network)

Figure 2: Conformance test system architecture for SUTs compliant with ISO 24102-4 [1]
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 797-2 V1.2.1 (2014-06)
Testing a protocol which resides inside the ITS management entity does not follow strictly the illustrations given in the
ITS testing framework EG 202 798 [i.1]. Nevertheless the principles outlined there apply also. The essential difference
is, that the access from the "upper tester application" and from the "ITS lower layers" to the IUT is via the management
SAPs.
Note that for testing of FSAP and IICP, the ITS lower layers connect to the IUT via MF-SAP only.
5 Test purpose basics
5.1 TP definition conventions
The TP definition is built according to the guidelines provided in the ITS testing framework EG 202 798 [i.1], applying
a formalized language with pre-defined keywords for the behaviour description.
5.2 TP identifier naming conventions
The identifier of the TP is built according to tables 1 and 2 as recommended in the ITS testing framework
EG 202 798 [i.1].
Table 1: TP naming convention for the ITS station-internal management communications protocol
(IICP) specified in ISO 24102-4 [1]
TP////
= root IICP ITS station-Internal management
Communication Protocol
= group MGM Management
COM Communication
= type of testing BV Valid Behaviour tests
BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99

TPs for the IICP are specified in clause 6.
Table 2: TP naming convention for the Fast Service Advertisement Protocol (FSAP)
specified in ISO 24102-5 [2]
TP/////
= root FSAP Fast Service Advertisement Protocol
= group SP Service provider
SU Service user
= sub-group HR Combined ITS-S host and ITS-S router
HO ITS-S host only
RO ITS-S router only
= type of testing BV Valid Behaviour tests
BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99

TPs for FSAP are specified in clause 7.
5.3 Rules for behaviour description
The description of the TP is built according to the guidelines provided in the ITS testing framework EG 202 798 [i.1].
5.4 Sources of TP definitions
All TPs are specified according to ISO 24102-4 [1] and ISO 24102-5 [2].
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 797-2 V1.2.1 (2014-06)
5.5 TP proforma
EG 202 798 [i.1] proposes a TP proforma which is used in the present document. The fields of this proforma as used in
the present document are explained in table 3.
Table 3: TP proforma field description
TP Header
TP ID The TP ID is a unique identifier according to the TP naming conventions in tables 1 and
2.
Test objective Short description of test purpose objective according to the requirements from the base
standard.
Reference The reference indicates the clauses of the reference standard specifications in which the
conformance requirement is expressed.
PICS selection
Reference to the PICS statement involved for selection of the TP. Contains a Boolean
expression. May contain PICS acronyms specified in tables 4 and 5.
This section is only used in case an optional or conditional behaviour needs to be
selected. Mandatory behaviour is identified by an empty field.
TP Behaviour
Initial conditions The initial conditions define in which initial state the IUT has to be to apply the actual TP.
(optional) In the corresponding "Test Case" (TC), when the execution of the initial condition does
not succeed, it leads to the assignment of an Inconclusive verdict.
Expected behaviour Definition of the events, which are parts of the TP objective, and the IUT are expected to
(TP body) perform in order to conform to the base specification. In the corresponding TC, "Pass" or
"Fail" verdicts can be assigned there.

5.6 PICS mnemonics
The PICS mnemonics presented in tables 4 and 5 are used in the TP proforma.
Table 4: PICS mnemonics for FSAP
Mnemonic PICS item
PICS_FSAP_ROLE_SP TS 102 797-1 [3] B.2/1
PICS_FSAP_ROLE_SU TS 102 797-1 [3] B.2/2
PICS_ITS_S_INW TS 102 797-1 [3] B.6/1
PICS_ROLE_HONLY TS 102 797-1 [3] B.5/1
PICS_ROLE_RH TS 102 797-1 [3] B.5/3
PICS_ROLE_RONLY TS 102 797-1 [3] B.5/2
PICS_SIP_N_CTX TS 102 797-1 [3] B.4/2
PICS_SIP_W_CTX TS 102 797-1 [3] B.4/1
PICS_SUT_AT_CHG TS 102 797-1 [3] B.1/2
PICS_SUT_CH_CHG TS 102 797-1 [3] B.1/1

Table 5: PICS mnemonics for IICP
Mnemonic PICS item
PICS_IICP_MGM TS 102 797-1 [3] A.8/1
PICS_ROLE_HONLY TS 102 797-1 [3] A.1/1
PICS_ROLE_RH TS 102 797-1 [3] A.1/3
PICS_ROLE_RONLY TS 102 797-1 [3] A.1/2

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 797-2 V1.2.1 (2014-06)
6 TPs for IICP
6.1 Management
6.1.1 Valid behaviour tests
TP Id IICP/MGM/BV/01
Test objective Generation of ITS-SCUalive message after power on - no other ITS-SCU in the SUT
Reference
ISO 24102-4 [1], clauses 9.1 and 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having no knowledge about other ITS-SCUs in the SUT
}
Expected behaviour
ensure that {
when {
the IUT starting
}
then {
the IUT generates an ITS-SCUalive (new) message with DestinationITS-SCU-ID=65535 and with SourceITS-
SCU-ID equal to the own ITS-SCU ID, indicating its IST-SCUtype, and forwards this with MF-COMMAND
IICrequestTX to the IICA
}
}

TP Id
IICP/MGM/BV/02
Test objective Reception of ITS-SCUalive (new) message with no address conflict
Reference ISO 24102-4 [1], clauses 9.1 and 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive (new) message without address conflict
}
then {
the IUT shall acknowledge this with ErrorStatus = 0 using MF-COMMAND IICresponseTX
}
}

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 797-2 V1.2.1 (2014-06)
TP Id IICP/MGM/BV/03
Test objective Reception of ITS-SCUalive (new) message with address conflict
Reference ISO 24102-4 [1], clauses 9.1 and 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive (new) message with address conflict, i.e. from an ITS-SCU having the
same ITS-SCU-ID
}
then {
the IUT shall acknowledge this with ErrorStatus = 2 using MF-COMMAND IICresponseTX for transmission to all
ITS-SCUs
}
}

TP Id IICP/MGM/BV/04
Test objective Reception of ITS-SCUalive (alive) message with no address conflict
Reference
ISO 24102-4 [1], clauses 9.1 and 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive (alive) message without address conflict
}
then {
the IUT does not show any visible reaction
}
}

TP Id IICP/MGM/BV/05
Test objective
Periodic transmission of ITS-SCUalive (alive) message
Reference
ISO 24102-4 [1], clauses 9.1 and 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having transmitted an ITS-SCUalive (alive) message with DestinationITS-SCU-ID=65535 and with
SourceITS-SCU-ID equal to its own ITS-SCU ID, which does not result in an address conflict
}
then {
the IUT transmits the next ITS-SCUalive (alive) message after the time span given in parameter Talive.
}
}

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 797-2 V1.2.1 (2014-06)
TP Id IICP/MGM/BV/06
Test objective Transmission of ITS-SCUalive (delete) message
Reference ISO 24102-4 [1], clauses 9.1 and 9.4
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT wants to shut down and stop operation
}
then {
the IUT transmits an ITS-SCUalive (delete) message with DestinationITS-SCU-ID=65535 and with SourceITS-
SCU-ID equal to its own ITS-SCU ID using MF-COMMAND IICrequestTX
}
}

6.1.2 Invalid behaviour tests
TP Id
IICP/MGM/BI/01
Test objective
Reception of ITS-SCUalive (alive) message with address conflict
Reference ISO 24102-4 [1], clauses 9.1 and 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive (alive) message with address conflict , i.e. from an ITS-SCU having the
same ITS-SCU-ID
}
then {
the IUT shall acknowledge this with ErrorStatus = 2 using MF-COMMAND IICresponseTX for transmission to all
ITS-SCUs,
the IUT shall delete its own ITS-SCU-ID and shall register newly by sending an ITS-SCU (new) message
indicating a new ITS-SCU-ID with MF-COMMAND IICrequestTX to the IICA for transmission to all ITS-SCUs
}
}

TP Id IICP/MGM/BI/02
Test objective Reception of ITS-SCUalive message with unknown AliveMessage
Reference
ISO 24102-4 [1], clause 9
PICS Selection
PICS_IICP_MGM
Initial conditions
with {
the IUT having own ITS-SCU-ID
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive message with unknown AliveMessage
}
then {
the IUT acknowledges the message with ErrorStatus 3
}
}

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 797-2 V1.2.1 (2014-06)
TP Id IICP/MGM/BI/03
Test objective Reception of ITS-SCUalive message with unknown ITS-SCU type
Reference ISO 24102-4 [1], clause 9
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received an ITS-SCUalive message with unknown ITS-SCU type
}
then {
the IUT acknowledges the message with ErrorStatus 4
}
}

6.2 Communications
6.2.1 Valid behaviour tests
TP Id IICP/COM/BV/01
Test objective
Transmission of IIC-Request VCI-info to all types of ITS-SCUs
Reference ISO 24102-4 [1], clause 8.2.1 and annex B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received the request to send an VCI-info request message to all ITS-SCUs
}
then {
the IUT generates an VCI-info request message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID
equal to its own ITS-SCU-ID, and forwards this with MF-COMMAND IICrequestTX to the IICA for transmission to
all ITS-SCUs
}
}

TP Id IICP/COM/BV/02
Test objective Transmission of IIC-Request VCI-info to ITS-SCUs with ITS-S router role
Reference ISO 24102-4 [1], clause 8.2.1 and annex B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT having received the request to send an VCI-info request message to all ITS-SCUs
}
then {
the IUT generates an VCI-info request message with DestinationITS-SCU-ID=2 and with SourceITS-SCU-ID
equal to its own ITS-SCU-ID, and forwards this with MF-COMMAND IICrequestTX to the IICA for transmission to
all ITS-SCUs
}
}

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 797-2 V1.2.1 (2014-06)
TP Id IICP/COM/BV/03
Test objective Transmission of VCI-info response message
Reference ISO 24102-4 [1], clause 8.3.1 and annex B.2.3
PICS Selection PICS_ROLE_RH OR PICS_ROLE_RONLY
Initial conditions
with {
the IUT having its own ITS-SCU ID, and having at least one CI to connect to another ITS-S
}
Expected behaviour
ensure that {
when {
the IUT having received an VCI-info request message
}
then {
the IUT prepares the VCI-info response message with DestinationITS-SCU-ID="private address from the
ITS-SCU which generated the request" and with SourceITS-SCU-ID equal to its own ITS-SCU-ID, and forwards
this with MF-COMMAND IICresponseTX to the IICA
}
}

TP Id IICP/COM/BV/04
Test objective Transmission of IIC-Request VCI-update to all types of ITS-SCUs
Reference
ISO 24102-4 [1], clause 8.2.1 and annex B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
ensure that {
when {
the IUT wants to provide an update of its own VCI information to all ITS-SCUs
}
then {
the IUT generates an VCI-update message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID
equal to its own ITS-SCU-ID, and forwards this with MF-COMMAND IICrequestTX to the IICA for transmission to
all ITS-SCUs
}
}

TP Id IICP/COM/BV/05
Test objective Reception of VCI-update request message
Reference ISO 24102-4 [1], clause 8.3.1 and annex B.2.4.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID
}
Expected behaviour
ensure that {
when {
the IUT having received an VCI-update request message
}
then {
the IUT does not show any visible reaction
}
}

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 102 797-2 V1.2.1 (2014-06)
TP Id IICP/COM/BV/06
Test objective Transmission of IIC-Request MF-rcmd to a specific ITS-SCU
Reference ISO 24102-4 [1], clause 8.2.1 and annex B.2.5
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID "own" allocated and knows the private ITS-SCU-ID "other" of another ITS-SCU
}
Expected behaviour
ensure that {
when {
the ITS-S management requests remote access to the MF-SAP in another ITS-SCU
}
then {
the IUT generates an MF-rcmd request message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", and forwards this with MF-COMMAND IICrequestTX to the IICA
}
}

TP Id
IICP/COM/BV/07
Test objective Transmission of IIC-Request MN-rcmd to a specific ITS-SCU
Reference ISO 24102-4 [1], clause 8.2.1 and annex B.2.5
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID "own" allocated and knows the private ITS-SCU-ID "other" of another ITS-SCU
}
Expected behaviour
ensure that {
when {
the ITS-S
...