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

Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for non-IP networking (ISO 29281); Part 2: Test Suite Structure and Test Purposes (TSS & TP)

RTS/ITS-00270

General Information

• Status: Published
• Publication Date: 09-Jun-2014
• Technical Committee: ITS WG2 - Architecture and Cross Layer
• Current Stage: 12 - Completion
• Due Date: 04-Jul-2014
• Completion Date: 10-Jun-2014
• Mandate: M/453

Standards Content (Sample)

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






Technical Specification
Intelligent Transport Systems (ITS);
Communications Access for Land Mobiles (CALM);
Test specifications for non-IP networking (ISO 29281);
Part 2: Test Suite Structure and Test Purposes (TSS & TP)

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



Reference
RTS/ITS-00270
Keywords
CALM, ITS, network, 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 985-2 V1.2.1 (2014-06)
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
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 FNTP . 9
6.1 Transmit packets . 9
6.1.1 Basic Procedure . 9
6.1.1.1 Valid behaviour tests . 9
6.1.1.2 Invalid behaviour tests . 10
6.1.2 Extended Procedure . 10
6.1.2.1 Valid behaviour tests . 10
6.1.2.2 Invalid behaviour tests . 11
6.1.3 Forwarding Procedure. 11
6.1.3.1 Valid behaviour tests . 11
6.1.3.2 Invalid behaviour tests . 12
6.2 Receiving packets . 13
6.2.1 Basic Procedure . 13
6.2.1.1 Valid behaviour tests . 13
6.2.1.2 Invalid behaviour tests . 14
6.2.2 Extended Procedure . 16
6.2.2.1 Valid behaviour tests . 16
6.2.2.2 Invalid behaviour tests . 18
6.2.3 Forwarding Procedure. 18
6.2.3.1 Valid behaviour tests . 18
6.2.3.2 Invalid behaviour tests . 20
6.3 CI parameter management . 20
6.3.1 Basic Procedure . 20
6.3.2 Extended Procedure . 20
6.3.2.1 Valid behaviour tests . 20
6.3.2.2 Invalid behaviour tests . 22
6.3.3 Forwarding Procedure. 22
6.3.3.1 Valid behaviour tests . 22
6.3.3.2 Invalid behaviour tests . 25
6.4 Secure communications . 25
History . 26

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 985-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 non-IP networking (ISO 29281), as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 2: "Test Suite Structure and Test Purposes (TSS & TP)";
Part 3: "Abstract Test Suite (ATS) and partial PIXIT proforma".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 985-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 29281-1 [1] 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 29281-1:2013: "Intelligent transport systems -- Communication access for land mobiles
(CALM) -- Non-IP networking -- Part 1: Fast networking & transport layer protocol (FNTP)".
[2] ETSI TS 102 985-1: "Intelligent Transport Systems (ITS); Communications Access for Land
Mobiles (CALM); Test specifications for non-IP networking (ISO 29281); Part 1: Protocol
Implementation Conformance Statement (PICS) proforma".
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] Void.
[i.3] ISO 24102-3: "Intelligent transport systems -- Communications access for land mobiles (CALM) -
- ITS station management -- Part 3: Service access points".
[i.4] ISO 24102-4: "Intelligent transport systems -- Communications access for land mobiles (CALM) -
- ITS station management -- Part 4: Station-internal management communications".
[i.5] ISO 21217: "Intelligent transport systems -- Communications access for land mobiles (CALM) --
Architecture".
[i.6] Void.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 985-2 V1.2.1 (2014-06)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO 29281-1 [1], TS 102 985-1 [2] and
EG 202 798 [i.1] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO 29281-1 [1], TS 102 985-1 [2],
EG 202 798 [i.1] and the following apply:
FNTP Fast Networking & Transport Protocol
IUT Implementation Under Test
SUT System Under Test
4 Test suite structure
In general, the conformance test system architecture presented in the ITS testing framework [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 ITS station-internal management communications [i.4] may benefit from the conformance
test system architecture illustrated in Figure 2, where the access to the IUT from top, i.e. in general via the "Upper tester
application", is performed via the MN-SAP.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 985-2 V1.2.1 (2014-06)
c
e
d
o
C
P
A
S
-
N
M

Figure 2: Conformance test system architecture for SUTs compliant with [i.4]
In general, the upper tester application [i.1] allows to access the NF-SAP of the IUT. Access to the full functionality of
the NF-SAP is also possible via the MN-SAP, applying the MN-Command "SimNFcmd". Similarly, access of the
networking and transport layer protocol to the ITS facilities layer (Upper tester application) is possible via MN-SAP,
applying the MN-Request "SimNFreq". Similarly, as specified in [i.3] and [i.4], access to the IN-SAP can be simulated
with functions of the MN-SAP; this allows avoiding the ITS lower layers.
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 Table 1 as recommended in the ITS testing framework [i.1].
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 985-2 V1.2.1 (2014-06)
Table 1: TP naming convention for FNTP [1]
TP/////
= root FNTP Fast Networking & Transport
Layer Protocol
= group TXP Transmit Packets
RXP Receive Packets
CIP CIP Management
SEC Secure Communications
= sub-group BP Basic Procedure
EP Extended Procedure
FP Forwarding Procedure
= type of testing BV Valid Behaviour Tests
BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99
NOTE 1: CIP management is only tested in the TPs of group "CIP".
NOTE 2: The groups TXP and RXP are restricted to "transmit to / receive from an ITS peer station",
i.e. the group TXP also includes TPs to test reception of an FNTP station-internal forwarding
NPDU from another local ITS-SCU, and the group RXP also includes TPs to test
transmission of an FNTP station-internal forwarding NPDU to another local ITS-SCU.
NOTE 3: A sub-group may not apply for all groups.

TPs for FNTP are specified in clause 6.
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].
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 2.
Table 2: TP proforma field description
TP Header
TP ID The TP ID is a unique identifier according to the TP naming conventions in Table 1.
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 3.
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

---------------------- Page: 8 ----------------------
9 ETSI TS 102 985-2 V1.2.1 (2014-06)
5.6 PICS mnemonics
The PICS mnemonics presented in Table 3 are used in the TP proforma.
Table 3: PICS mnemonic for ISO 29281-1 [1]
Mnemonic PICS item
PICS_ROLE_RONLY [2] A.2/1
PICS_ROLE_HONLY [2] A.2/2
PICS_ROLE_RH [2] A.2/3
PICS_EXT [2] A.3/2
PICS_ITS_S_INW [2] A.4/1
PICS_SEC [2] A.4/2
PICS_NHOPBC [2] A.4/3
PICS_LPP [2] A.4/4
PICS_CIP [2] A.4/5
PICS_15628 [2] A.5/1

6 TPs for FNTP
6.1 Transmit packets
6.1.1 Basic Procedure
6.1.1.1 Valid behaviour tests
TP Id
FNTP/TXP/BP/BV/01
Test objective Single hop broadcast transmission request with known VCI
Reference ISO 29281-1 [1], clause 7.6.1 and clause 7.6.2
PICS Selection PICS_ROLE_RH
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the local port number of the ITS-S
application
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted single hop BC transmission request
}
then {
the IUT generates a basic FNTP NPDU, and forwards it to the BC-VCI(s) for transmission
}
}

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 985-2 V1.2.1 (2014-06)
TP Id FNTP/TXP/BP/BV/02
Test objective Single hop unicast transmission request with known VCI
Reference ISO 29281-1 [1], clause 7.6.1 and clause 7.6.2
PICS Selection PICS_ROLE_RH
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the requested local port number of the ITS-S
application
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted single hop UC transmission request
}
then {
the IUT generates a basic FNTP NPDU, and forwards it to the proper UC-VCI for transmission
}
}

6.1.1.2 Invalid behaviour tests
Invalid test purposes will be defined once ISO has implemented the concept of path and flow management in the
architecture standard ISO 21217 [i.5] and subsequently in ISO 29281-1 [1].
6.1.2 Extended Procedure
6.1.2.1 Valid behaviour tests
TP Id FNTP/TXP/EP/BV/01
Test objective N- hop broadcast transmission request with known VCI
Reference ISO 29281-1 [1], clause 7.6.3
PICS Selection PICS_EXT AND PICS_ROLE_RH AND PICS_NHOPBC
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the requested local port number of the ITS-S
application
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted N-hop BC transmission request
}
then {
the IUT generates an extended FNTP NPDU, and forwards it to the BC-VCI(s) for transmission
}
}

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 985-2 V1.2.1 (2014-06)
6.1.2.2 Invalid behaviour tests
TP Id FNTP/TXP/EP/BI/01
Test objective N- hop broadcast transmission request with invalid FNTP control field, and with known VCI
Reference
ISO 29281-1 [1], clause 7.6.3
PICS Selection
PICS_EXT AND PICS_ROLE_RH AND PICS_NHOPBC
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the requested local port number of the ITS-S
application
}
Expected behaviour
ensure that {
when {
the IUT having received an N-hop BC transmission request with non-supported bits in "controlField" also set to 1
}
then {
the IUT reports failure of delivery
}
}

6.1.3 Forwarding Procedure
6.1.3.1 Valid behaviour tests
TP Id FNTP/TXP/FP/BV/01
Test objective TX from ITS-S host
Reference ISO 29281-1 [1], clause 7.6.4
PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH)
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the requested local port numbers of the
ITS-S application
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted single hop BC transmission request for delivery via a VCI contained
in a different ITS-SCU
}
then {
the IUT generates an FNTP forwarding NPDU, and forwards it to the BC-VCI for transmission to the selected
ITS-S router
}
}

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 985-2 V1.2.1 (2014-06)
TP Id FNTP/TXP/FP/BV/02
Test objective RX at ITS-S router
Reference ISO 29281-1 [1], clause 7.6.4 and clause 7.7.7
PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_RONLY OR PICS_ROLE_RH)
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of an ITS-S application in an ITS-S host
}
Expected behaviour
ensure that {
when {
the IUT having received an FNTP station-internal forwarding NPDU containing a correctly formatted FNTP basic
NPDU for single hop BC transmission
}
then {
the IUT extracts the FNTP basic NPDU, and forwards it to the BC-VCI for transmission via the IN-SAP
}
}

TP Id
FNTP/TXP/FP/BV/03
Test objective TX from ITS-S host - increment of Counter
Reference ISO 29281-1 [1], clause 7.6.4
PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH)
Initial conditions
with {
the IUT having an FNTP forwarding table with proper entry in support of the requested local port numbers of the
ITS-S application
}
Expected behaviour
ensure that {
when {
the IUT having received a sequence of correctly formatted single hop BC transmission requests for delivery via a
VCI contained in a different ITS-SCU, with the number of requests such that at least once the "Counter" value
before increment is different to 255, and at least once it is equal to 255
}
then {
the IUT generates an FNTP forwarding NPDU for every request, with the "Counter" value in an FNTP forwarding
NPDU equal to the "Counter" value from the previous FNTP forwarding NPDU incremented by one with a wrap
around from the value 255 to 0
}
}

6.1.3.2 Invalid behaviour tests
TP Id FNTP/TXP/FP/BI/01
Test objective TX from ITS-S host - unknown access to ITS station-internal network
Reference ISO 29281-1 [1], clause 7.6.4
PICS Selection
PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH)
Initial conditions
with {
the IUT having an FNTP forwarding table with no entry related to an ITS-S internal network
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted single hop BC transmission request for delivery via a VCI contained
in a different ITS-SCU
}
then {
the IUT reports failure of delivery
}
}

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 985-2 V1.2.1 (2014-06)
6.2 Receiving packets
6.2.1 Basic Procedure
6.2.1.1 Valid behaviour tests
TP Id
FNTP/RXP/BP/BV/01
Test objective Single hop unicast reception from peer station
Reference ISO 29281-1 [1], clause 7.7.1, clause 7.7.2 and clause 7.7.3
PICS Selection PICS_ROLE_RH
Initial conditions
with {
the IUT having a proper entry in the FNTP forwarding table with Service Port such that no ITS station-internal
forwarding is needed
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted unicast packet from the peer station via the IN-SAP
}
then {
the IUT delivers the message to the local ITS-SP selected by the Service Port
}
}

TP Id FNTP/RXP/BP/BV/02
Test objective
Single hop unicast reception from unknown peer station
Reference
ISO 29281-1 [1], clause 7.7.1, clause 7.7.2 and clause 7.7.3
PICS Selection PICS_ROLE_RH
Initial conditions
with {
the IUT having an entry in the FNTP forwarding table for a Service Port such that no ITS station-internal forwarding is
needed, but no entry for the peer station
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted unicast packet from the peer station via the IN-SAP
}
then {
the IUT delivers the message to the ITS-SP selected by the Service Port,
the ITU informs the management about the new peer ITS-S
}
}

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 102 985-2 V1.2.1 (2014-06)
TP Id FNTP/RXP/BP/BV/03
Test objective Single hop broadcast reception from peer station
Reference ISO 29281-1 [1], clause 7.7.1, clause 7.7.2 and clause 7.7.3
PICS Selection PICS_ROLE_RH
Initial conditions
with {
the IUT having an entry in the FNTP forwarding table for a Service Port such that no ITS station-internal forwarding is
needed
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted broadcast packet from the peer station via the IN-SAP
}
then {
the IUT forwards the message to the ITS-SP selected by the Service Port
}
}

6.2.1.2 Invalid behaviour tests
TP Id FNTP/RXP/BP/BI/01
Test objective Single hop broadcast reception to unknown Service Port
Reference ISO 29281-1 [1], clause 7.7.1 and clause 7.7.2
PICS Selection PICS_ROLE_RH OR PICS_ROLE_RONLY OR PICS_ROLE_HONLY
Initial conditions
with {
the IUT having an entry in the FNTP forwarding table for Service Port = port1, but not for Service Port = port2
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted broadcast message with a destinationPort port2, with port2 different
to port1
}
then {
the IUT discards the message
}
}

TP Id
FNTP/RXP/BP/BI/02
Test objective Single hop broadcast reception to invalid port PORT_NON
Reference ISO 29281-1 [1], clause 7.7.1
PICS Selection PICS_ROLE_RH OR PICS_ROLE_HONLY OR PICS_ROLE_RONLY
Initial conditions
none
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted broadcast message with a destinationPort PORT_NON
}
then {
the IUT discards the message
}
}

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 102 985-2 V1.2.1 (2014-06)
TP Id FNTP/RXP/BP/BI/03
Test objective Single hop broadcast reception from invalid port PORT_NON
Reference ISO 29281-1 [1], clause 7.7.1
PICS Selection PICS_ROLE_RH OR PICS_ROLE_HONLY OR PICS_ROLE_RONLY
Initial conditions
with {
the IUT having an entry in the FNTP forwarding table for Service Port = port1
}
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted broadcast message with a destinationPort port1 and a sourcePort
PORT_NON
}
then {
the IUT discards the message
}
}

TP Id
FNTP/RXP/BP/BI/04
Test objective Single hop broadcast reception from invalid port PORT_NON to invalid port PORT_NON
Reference ISO 29281-1 [1], clause 7.7.1
PICS Selection PICS_ROLE_RH OR PICS_ROLE_HONLY OR PICS_ROLE_RONLY
Initial conditions
none
Expected behaviour
ensure that {
when {
the IUT having received a correctly formatted broadcast message with a destinationPort PORT_NON and a
sourcePort PORT_NON
}
then {
the IUT discards the message
}
}

TP Id FNTP/RXP/BP/BI/05
Test objective Single hop broadcast reception with invalid pair of ports, one of which is PORT_RTR and the
other one is differen
...