ETSI TS 102 797-2 V1.1.1 (2012-08)

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)

2 ETSI TS 102 797-2 V1.1.1 (2012-08)

Reference
DTS/ITS-0020011
Keywords
CALM, ITS, testing, TSS&TP
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 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 797-2 V1.1.1 (2012-08)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Test suite structure . 6
4.1 Test architecture . 6
5 TP basics . 7
5.1 TP definition conventions . 7
5.2 TP identifier naming conventions . 7
5.3 Rules for behaviour description . 8
5.4 Sources of TP definitions . 8
5.5 TP proforma . 8
5.6 PICS mnemonics . 9
6 TPs for local station management protocols . 9
7 TPs for remote station management protocols . 9
8 TPs for IICP . 10
8.1 Management . 10
8.1.1 Valid behaviour tests . 10
8.1.2 Invalid behaviour tests . 12
8.2 Communications . 13
8.2.1 Valid behaviour tests . 13
8.2.2 Invalid behaviour tests . 21
9 TPs for FSAP . 23
9.1 Service provider . 23
9.1.1 Combined ITS-S host and ITS-S router . 23
9.1.1.1 Valid behaviour tests . 23
9.1.1.2 Invalid behaviour tests . 25
9.1.2 ITS-S host only . 26
9.1.2.1 Valid behaviour tests . 26
9.1.2.2 Invalid behaviour tests . 28
9.1.3 ITS-S router only . 29
9.1.3.1 Valid behaviour tests . 29
9.1.3.2 Invalid behaviour tests . 32
9.2 Service user . 33
9.2.1 Combined ITS-S host and ITS-S router . 33
9.2.1.1 Valid behaviour tests . 33
9.2.1.2 Invalid behaviour tests . 35
9.2.2 ITS-S host only . 35
9.2.2.1 Valid behaviour tests . 35
9.2.2.2 Invalid behaviour tests . 35
9.2.3 ITS-S router only . 36
9.2.3.1 Valid behaviour tests . 36
9.2.3.2 Invalid behaviour tests . 37
History . 38

ETSI
4 ETSI TS 102 797-2 V1.1.1 (2012-08)
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 2 of a multi-part deliverable covering "Test Suite Structure and Test Purposes" (TSS&TP)
specifications for ITS station management protocols 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".
ETSI
5 ETSI TS 102 797-2 V1.1.1 (2012-08)
1 Scope
The present document provides the test suite structure and test purpose specification for the ISO protocols specified in
ISO/DIS 24102 [1], [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/DIS 24102-4: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 4: Station-internal management communications".
NOTE: Available at http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=61565.
[2] ISO/DIS 24102-5: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 5: Fast service advertisement protocol (FSAP)".
NOTE: Available at http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=61566.
[3] ETSI TS 102 797-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".
[i.2] ISO/DIS 24102-1: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 1: Local management".
[i.3] ISO/DIS 24102-3: "Intelligent transport systems -- Communications access for land mobiles
(CALM) -- ITS station management -- Part 3: Service access points".
ETSI
6 ETSI TS 102 797-2 V1.1.1 (2012-08)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1], [2], [i.1] and [i.3] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in [1], [2], [i.1] and [i.3] apply.
4 Test suite structure
4.1 Test architecture
In general, the conformance test system architecture as illustrated in the ITS testing framework [i.1] applies. Such SUTs
which support the "Inter-ITS-SCU-Communications Protocol" (IICP) [1] may benefit from the conformance test system
architecture illustrated in figure 1, where the access to the IUT from top, i.e. in general via the "Upper tester
application", is performed via remote access to the management SAPs applying IICP.
P P
A A
S S
- -
F F
M M
P P
c
A A
e
S S
d
- -
o
N N
C
M M
P P
A A
S S
- -
I I
M M
Figure 1: Conformance test system architecture for SUTs compliant with [1]
Testing a protocol which resides inside the ITS management entity does not follow strictly the illustrations given in the
ITS testing framework [i.1]. Nevertheless the principles outlined there apply also. The essential difference is, that the
access from the "upper tester application" and form the "ITS lower layers" to the IUT is via the management SAPs.
In general, the upper tester application [i.1] allows to access anyone of the three management SAPs of the IUT,
i.e. MI-SAP, MN-SAP and MF-SAP. The ITS test system uses the remote management commands specified in [1].
Note that for testing of FSAP and IICP, the ITS lower layers connect to the IUT via MF-SAP only.
ETSI
7 ETSI TS 102 797-2 V1.1.1 (2012-08)
5 TP basics
5.1 TP definition conventions
The TP definition is built according to the guidelines provided in the ITS testing framework [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, 2, 3 and 4 as recommended in the ITS testing framework [i.1].
Table 1: TP naming convention for station-internal management protocols
TP/////
= root INTM Other management protocols
= group
= sub- group
= type of testing BV Valid Behaviour tests
BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99

NOTE 1: The present document does not contain TPs related to table 1, which will be provided in a future version.
Table 2: TP naming convention for remote station management protocols
TP/////
= root EXTM Other management protocols
= group
= sub- group
= type of testing BV Valid Behaviour tests
BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99

NOTE 2: The present document does not contain TPs related to table 2, which will be provided in a future version.
Table 3: TP naming convention for Inter-ITS-SCU communication protocol (IICP)
TP////
= root IICP Inter-ITS-SCU 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 8.
ETSI
8 ETSI TS 102 797-2 V1.1.1 (2012-08)
Table 4: TP naming convention for FSAP
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 9.
5.3 Rules for behaviour description
The description of the TP is built according to the guidelines provided in the ITS testing framework [i.1].
5.4 Sources of TP definitions
All TPs are specified according to [1],[2].
5.5 TP proforma
[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 5.
Table 5: TP proforma field description
TP Header
TP ID The TP ID is a unique identifier according to the TP naming conventions in tables 1, 2, 3
and 4.
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 table.
This section is only used in case an optional or conditional behaviour needs to be
selected. Mandatory behaviour is not identified here.
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.

ETSI
9 ETSI TS 102 797-2 V1.1.1 (2012-08)
5.6 PICS mnemonics
The PICS mnemonics presented in table 6 are used in the TP proforma.
Table 6: PICS mnemonics for FSAP
Mnemonic PICS item
PICS_FSAP_ROLE_SP [3] D.1/1
PICS_FSAP_ROLE_SU [3] D.1/2
PICS_SIP_W_CTX [3] D.3/1
PICS_SIP_N_CTX [3] D.3/2
PICS_ROLE_RONLY [3] D.5/1
PICS_ROLE_HONLY [3] D.5/2
PICS_ROLE_RH [3] D.5/3
PICS_ITS_S_INW [3] D.6/1
Table 7: PICS mnemonics for IICP
Mnemonic PICS item
PICS_ROLE_HONLY [3] C.1/1
PICS_ROLE_RONLY [3] C.1/2
PICS_ROLE_RH [3] C.1/3
PICS_IICP_MGM [3] C.8/1
6 TPs for local station management protocols
NOTE: The present document does not contain TPs related to local management of an ITS station specified
in [i.2], as such TPs are not covered by the scope of ETSI STF 422, which developed the present
document. These TPs will be defined in a future version.
7 TPs for remote station management protocols
NOTE: The present document does not contain TPs related to remote management of an ITS station. These TPs
will be defined in the future.
ETSI
10 ETSI TS 102 797-2 V1.1.1 (2012-08)
8 TPs for IICP
8.1 Management
8.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
9.1, 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having no knowledge about other ITS-SCUs in the SUT
}
Expected behaviour
evaluate whether {
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 9.1, 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
11 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/MGM/BV/03
Test objective Reception of ITS-SCUalive (new) message with address conflict
Reference 9.1, 9.2
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
9.1, 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
9.1, 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
12 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/MGM/BV/06
Test objective Transmission of ITS-SCUalive (delete) message
Reference 9.1, 9.4
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
}
}
8.1.2 Invalid behaviour tests
TP Id
IICP/MGM/BI/01
Test objective
Reception of ITS-SCUalive (alive) message with address conflict
Reference 9.1, 9.3
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
PICS Selection
PICS_IICP_MGM
Initial conditions
with {
the IUT having own ITS-SCU-ID
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ITS-SCUalive message with unknown AliveMessage
}
then {
the IUT acknowledges the message with ErrorStatus 3
}
}
ETSI
13 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/MGM/BI/03
Test objective Reception of ITS-SCUalive message with unknown ITS-SCU type
Reference 9
PICS Selection PICS_IICP_MGM
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ITS-SCUalive message with unknown ITS-SCU type
}
then {
the IUT acknowledges the message with ErrorStatus 4
}
}
8.2 Communications
8.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 8.2.1, B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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 8.2.1, B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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
14 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/03
Test objective Transmission of VCI-info response message
Reference B.2.3, 8.3.1
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
evaluate whether {
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
8.2.1, B.2.3
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
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 B.2.3, 8.3.1
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID
}
Expected behaviour
evaluate whether {
when {
the IUT having received an VCI-update request message
}
then {
the IUT does not show any visible reaction
}
}
ETSI
15 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/06
Test objective Transmission of IIC-Request MF-rcmd to a specific ITS-SCU
Reference 8.2.1, 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
evaluate whether {
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 8.2.1, 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
evaluate whether {
when {
the ITS-S management requests remote access to the MN-SAP in another ITS-SCU
}
then {
the IUT generates an MN-rcmd 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/08
Test objective
Transmission of IIC-Request MI-rcmd to a specific ITS-SCU
Reference
8.2.1, 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
evaluate whether {
when {
the ITS-S management requests remote access to the MI-SAP in another ITS-SCU
}
then {
the IUT generates an MI-rcmd message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-ID "own",
and forwards this with MF-COMMAND IICrequestTX to the IICA
}
}
ETSI
16 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/09
Test objective Transmission of IIC-Request MI-rget to a specific ITS-SCU
Reference 8.2.1, 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
evaluate whether {
when {
the ITS-S management requests remote access to the MI-SAP in another ITS-SCU in order to get the value of an
I-Parameter
}
then {
the IUT generates an MI-rget 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/10
Test objective Transmission of IIC-Request MI-rset to a specific ITS-SCU
Reference
8.2.1, 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
evaluate whether {
when {
the ITS-S management requests remote access to the MI-SAP in another ITS-SCU in order to set the value of an
I-Parameter
}
then {
the IUT generates an MI-rset 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/11
Test objective Transmission of MF-rcmd response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own" allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MF-rcmd request message from an ITS-SCU with ITS-SCU-ID="other" which requires
a response
}
then {
the IUT generates an MF-rcmd response message with DestinationITS-SCU-ID="other" and with SourceITS-
SCU-ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
ETSI
17 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/12
Test objective Transmission of MN-rcmd response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MN-rcmd request message from an ITS-SCU with ITS-SCU-ID="other" which requires
a response
}
then {
the IUT generates an MN-rcmd response message with DestinationITS-SCU-ID="other" and with SourceITS-
SCU-ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
TP Id IICP/COM/BV/13
Test objective Transmission of MI-rcmd response message
Reference
B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MI-rcmd request message from an ITS-SCU with ITS-SCU-ID="other" which requires
a response
}
then {
the IUT generates an MI-rcmd response message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
TP Id IICP/COM/BV/14
Test objective Transmission of MI-rget response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MI-rget request message from an ITS-SCU with ITS-SCU-ID="other" which
constitutes an authorized get request
}
then {
the IUT generates an MI-rget response message providing the requested value with DestinationITS-SCU-
ID="other" and with SourceITS-SCU-ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
ETSI
18 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/15
Test objective Transmission of MI-rset response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MI-rset request message from an ITS-SCU with ITS-SCU-ID="other" which constitutes
an unauthorized set request
}
then {
the IUT generates an MI-rset response message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", indicating the proper error code, and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
TP Id IICP/COM/BV/16
Test objective Transmission of IIC-Request MF-rreq to a specific ITS-SCU
Reference
8.2.1, 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
evaluate whether {
when {
ITS-S management entity is used by ITS-S facilities layer to request access to a remote management
}
then {
the IUT generates an MF-rreq 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/17
Test objective Transmission of IIC-Request MN-rreq to a specific ITS-SCU
Reference 8.2.1, 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
evaluate whether {
when {
ITS-S management entity is used by ITS-S networking&transport layer to request access to a remote
management
}
then {
the IUT generates an MN-rreq message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-ID "own",
and forwards this with MF-COMMAND IICrequestTX to the IICA
}
}
ETSI
19 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/18
Test objective Transmission of IIC-Request MI-rreq to a specific ITS-SCU
Reference 8.2.1, 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
evaluate whether {
when {
ITS-S management entity is used by ITS-S access layer to request access to a remote management
}
then {
the IUT generates an MI-rreq 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/19
Test objective Transmission of MF-rreq response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MF-rreq request message from an ITS-SCU with ITS-SCU-ID="other" which requires
a response
}
then {
the IUT generates an MF-rreq response message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
TP Id IICP/COM/BV/20
Test objective Transmission of MN-rreq response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MN-rreq request message from an ITS-SCU with ITS-SCU-ID="other" which requires
a response
}
then {
the IUT generates an MN-rreq response message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
ETSI
20 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BV/21
Test objective Transmission of MI-rreq response message
Reference B.2.3, 8.3.1, 8.2.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU ID "own"
}
Expected behaviour
evaluate whether {
when {
the IUT having received an MI-rreq request message from an ITS-SCU with ITS-SCU-ID="other" which requires a
response
}
then {
the IUT generates an MI-rreq response message with DestinationITS-SCU-ID="other" and with SourceITS-SCU-
ID "own", and forwards this with MF-COMMAND IICresponseTX to the IICA
}
}
TP Id IICP/COM/BV/22
Test objective Reception of an ICC-Request message with invalid DestinationITS-SCU-ID=1
Reference
8.3.1
PICS Selection PICS_ROLE_RONLY
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Request message with invalid DestinationITS-SCU-ID=1 (ITS-S host)
}
then {
the IUT deletes the received message
}
}
TP Id IICP/COM/BV/23
Test objective
Reception of an ICC-Request message with invalid DestinationITS-SCU-ID=2
Reference
8.3.1
PICS Selection PICS_ROLE_HONLY
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Request message with invalid DestinationITS-SCU-ID=2 (ITS-S router)
}
then {
the IUT deletes the received message
}
}
ETSI
21 ETSI TS 102 797-2 V1.1.1 (2012-08)
8.2.2 Invalid behaviour tests
TP Id IICP/COM/BI/01
Test objective Reception of an ICC-Request message with invalid DestinationITS-SCU-ID (reserved)
Reference 8.3.1
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Request message with invalid DestinationITS-SCU-ID (reserved)
}
then {
the IUT deletes the received message
}
}
TP Id IICP/COM/BI/02
Test objective Reception of an ICC-Response message with invalid DestinationITS-SCU-ID=1
Reference 8.3.2
PICS Selection PICS_ROLE_RONLY
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Response message with invalid DestinationITS-SCU-ID=1 (ITS-S host)
}
then {
the IUT deletes the received message
}
}
TP Id IICP/COM/BI/03
Test objective Reception of an ICC-Response message with invalid DestinationITS-SCU-ID=2
Reference 8.3.2
PICS Selection PICS_ROLE_HONLY
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Response message with invalid DestinationITS-SCU-ID=2 (ITS-S router)
}
then {
the IUT deletes the received message
}
}
ETSI
22 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BI/04
Test objective Reception of an ICC-Response message with invalid DestinationITS-SCU-ID (reserved)
Reference 8.3.2
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an ICC-Response message with invalid DestinationITS-SCU-ID (reserved)
}
then {
the IUT deletes the received message
}
}
TP Id IICP/COM/BI/05
Test objective Reception of an ICC-Request message with odd "PDU-Counter" value
Reference 8.3.1
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an IIC-Request message with odd "PDU-Counter" value
}
then {
the IUT deletes the received message
}
}
TP Id IICP/COM/BI/06
Test objective Reception of an ICC-Response message with even "PDU-Counter" value
Reference 8.3.1
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated
}
Expected behaviour
evaluate whether {
when {
the IUT having received an IIC-Response message with even "PDU-Counter" value
}
then {
the IUT deletes the received message
}
}
ETSI
23 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id IICP/COM/BI/07
Test objective Reception of an ICC-Response message with "PDU-Counter" not indicating a previous ICC-
Request message
Reference 8.3.1
PICS Selection
Initial conditions
with {
the IUT having its own ITS-SCU-ID allocated, the ITU not awaiting an IIC-Response message
}
Expected behaviour
evaluate whether {
when {
the IUT having received a privately addressed IIC-Response message with odd "PDU-Counter" value
}
then {
the IUT deletes the received message
}
}
9 TPs for FSAP
9.1 Service provider
9.1.1 Combined ITS-S host and ITS-S router
9.1.1.1 Valid behaviour tests
TP Id FSAP/SP/HR/BV/01
Test objective Registration of ITS-S application for message distribution only (no session phase) with request
of specific access technology
Reference 8.2.1, 8.2.4, 8.2.5
PICS Selection PICS_FSAP_ROLE_SP AND PICS_ROLE_RH
Initial conditions
with {
the IUT having not registered any ITS-S application for service announcement,
the IUT knowing the requested access technology
}
Expected behaviour
evaluate whether {
when {
the IUT having received a GCregServer registration request for an ITS-S application including a required access
technology and non-IP communications
}
then {
the IUT periodically sends out SAM via the requested access technology with the requested repetition rate, not
inviting for a reply
}
}
ETSI
24 ETSI TS 102 797-2 V1.1.1 (2012-08)
TP Id FSAP/SP/HR/BV/02
Test objective Registration of ITS-S application for message distribution only (no session phase) with no
request of specific access technology
Reference 8.2.1, 8.2.4, 8.2.5
PICS Selection PICS_FSAP_ROLE_SP AND PICS_ROLE_RH
Initial conditions
with {
the IUT having not registered any ITS-S application for service announcement,
the IUT knowing a suitable access technology
}
Expected behaviour
evaluate whether {
when {
the IUT having received a GCregServer registration request for
...