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

Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for non-IP networking (ISO 29281); Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma

RTS/ITS-00271

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-3 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 3: Abstract Test Suite (ATS) and partial PIXIT proforma

�

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



Reference
RTS/ITS-00271
Keywords
ATS, CALM, ITS, network, testing, TTCN
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-3 V1.2.1 (2014-06)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Abstract test method . 7
4.1 Abstract protocol tester . 7
4.2 Test configurations . 9
4.2.1 Roles of an ITS-SCU . 9
4.2.2 Test configuration CF01: No ITS station-internal network . 9
4.2.3 Test configuration CF02: ITS station-internal network . 10
4.3 Test architecture . 11
4.4 Ports and abstract service primitives . 12
4.4.1 Overview . 12
4.4.2 ASPs of the fntpPort . 12
4.4.3 ASPs of the utPort . 12
4.4.4 ASPs of the cfPort . 12
5 ATS conventions . 12
5.1 Testing conventions . 12
5.1.1 Testing states . 12
5.1.1.1 Initial state . 12
5.1.1.2 Final state . 13
5.1.2 Message types - ASN.1 definitions . 13
5.2 Naming conventions . 13
5.2.1 General guidelines . 13
5.2.2 Usage of Log statements . 13
5.2.3 Test Case (TC) identifier . 14
Annex A (normative): Partial PIXIT proforma for FNTP . 15
A.1 Identification summary. 15
A.2 ATS summary . 15
A.3 Test laboratory . 15
A.4 Client identification . 16
A.5 SUT . 16
A.6 Protocol layer information. 16
A.6.1 Protocol identification . 16
A.6.2 IUT information . 17
Annex B (normative): TTCN-3 library modules . 21
B.1 Electronic annex, zip file with TTCN-3 code . 21
B.2 Extensions of Architecture of conformance validation framework. 21
B.2.1 Test Adapter . 21
B.2.2 Lower Tester . 22
B.2.3 Dispatcher. 23
B.2.4 Codecs source code . 23
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 985-3 V1.2.1 (2014-06)
B.2.5 Test Adapter source code . 23
B.2.6 Dispatcher source code . 23
B.3 Upper Tester message format . 24
B.3.1 FNTP Upper Tester Primitives . 24
B.3.1.1 FntpInitialize . 24
B.3.1.2 FntpPortCreationRequest . 24
B.3.1.3 FntpPortCreationConfirm . 24
B.3.1.4 FntpForwardTableNotification . 25
B.3.2 FSAP Upper Tester Primitives - FsapInitialize . 25
B.3.3 IICP Upper Tester Primitives - IicpInitialize. 25
History . 26

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 985-3 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 3 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: 5 ----------------------
6 ETSI TS 102 985-3 V1.2.1 (2014-06)
1 Scope
The present document provides the Abstract Test Suite (ATS) and partial PIXIT proforma for the protocols specified in
ISO 29281-1 [1] based on the related TSS & TP specification [3] and the PICS proforma [2], and in accordance with the
relevant guidance given in ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETS 300 406 [6] and 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
referenced 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".
[3] ETSI TS 102 985-2: "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)".
[4] ISO/IEC 9646-1:1994: "Information technology -- Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 1: General concepts".
[5] ISO/IEC 9646-2:1994: "Information technology -- Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 2: Abstract Test Suite specification".
[6] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[7] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[8] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[9] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)".
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".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 985-3 V1.2.1 (2014-06)
[i.2] ISO 21217: "Intelligent transport systems -- Communications access for land mobiles (CALM) --
Architecture".
[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 21218: "Intelligent transport systems -- Communications access for land mobiles (CALM) --
Access technology support".
[i.6] ETSI TR 103 099 (V1.1.1): "Intelligent Transport Systems (ITS);Architecture of conformance
validation framework".
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],
TS 102 985-2 [3], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETS 300 406 [6], ES 201 873-1 [7], ES 201 873-7 [8],
EG 202 798 [i.1], ISO 21217 [i.2], ISO 24102-3 [i.3], ISO 24102-4 [i.4] and ISO 21218 [i.5] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO 29281-1 [1], TS 102 985-1 [2],
TS 102 985-2 [3], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETS 300 406 [6], ES 201 873-1 [7], ES 201 873-7 [8],
EG 202 798 [i.1], ISO 21217 [i.2], ISO 24102-3 [i.3], ISO 24102-4 [i.4] and ISO 21218 [i.5] apply.
4 Abstract test method
4.1 Abstract protocol tester
In general, the conformance test system architecture as illustrated in the ITS testing framework [i.1], see figure 1,
applies. For the present document, the IUT is the FNTP. The upper tester application allows accessing the NF-SAP of
the IUT. Lower layer protocols indicated by the block "ITS lower layers" allow access to the IUT from the lower side.
NOTE 1: There is also the need and possibility to configure the IUT by the ITS test system. This feature is not
illustrated in figure 1, but is presented in figure 5.
The test system simulates valid and invalid protocol behaviour, and analyses the reaction of the IUT.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 985-3 V1.2.1 (2014-06)
c
e
d
o
C

Figure 1: Abstract protocol tester - General approach
SUTs which support the "ITS station-internal management communications protocol" (IICP) [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 applying the MN-Command "UpTest_NF_Cmd" [i.3]. Similarly,
access of the networking & transport layer protocol to the ITS facilities layer (Upper tester application) is possible via
MN-SAP applying the MN-Request "UpTest_NF_Req" [i.3].
P
A
S
-
c
e
N
d
M
o
C

Figure 2: Abstract protocol tester - IICP approach
NOTE 2: In CALM-compliant implementations, in addition to the upper tester access, configuration of the IUT by
the ITS test system is also done via the ITS station-internal network. This feature is illustrated in figure 5.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 985-3 V1.2.1 (2014-06)
4.2 Test configurations
4.2.1 Roles of an ITS-SCU
This test suite uses two test configurations in order to cover the different test scenarios. Distinction between the two
configurations is given by the two possible implementation scenarios for an ITS station, i.e. a single-unit
implementation, or an implementation with several "ITS station communication units" (ITS-SCU) which are
interconnected via an ITS station-internal network [1] and [i.2]. These ITS-SCUs can take over the roles of an ITS-S
host, or an ITS-S router, or the combined role of ITS-S host and ITS-S router. These two identified testing
configurations are referred to as CF01 for the single unit implementation illustrated in figure 3, and CF02 for the
multi-unit implementation illustrated in figure 4, and are described in clause 4.2.2 and clause 4.2.3.
4.2.2 Test configuration CF01: No ITS station-internal network
In test configuration CF01, the roles of ITS-S host and ITS-S router are implemented in a single ITS-SCU as illustrated
in figure 3. Consequently the whole supported functionality of FNTP is given in a single ITS-SCU, and no station-
internal forwarding between ITS-S host and ITS-S router is needed.

Figure 3: Test configuration CF01 architecture
In this test configuration, the FNTP is connected only to communication interfaces (CI) which establish a link to
another instance of an ITS station. Such CIs provide "virtual communication interfaces" (VCIs) for MAC broadcast
communications, multicast communications and unicast communications. Details on VCIs, and how the ITS-S access
layer is connected to the ITS-S networking & transport layer via the IN-SAP are specified in [i.5]. The following
address elements contained in the element LinkID specified in [i.5] are used:
• LocalCIID, identifying uniquely a CI, specified in the following PIXIT variable:
PX_WL_LOCAL_CIID.
• RemoteCIID, identifying VCI for broadcast communications in destination_address.RemoteCIID of the
IN-UNITDATA.request service primitive, specified in the following PIXIT variable:
PX_WL_REMOTE_CIID_BC
• RemoteCIID, identifying VCI for multicast communications in destination_address.RemoteCIID of the
IN-UNITDATA.request service primitive, specified in the following PIXIT variable:
PX_WL_REMOTE_CIID_MC
• RemoteCIID, identifying a VCI for unicast communications in destination_address.RemoteCIID of the
IN-UNITDATA.request service primitive / source_address.RemoteCIID of the IN-UNITDATA.indication
service primitive, specified in the following PIXIT variable:
PX_WL_REMOTE_CIID_UC.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 985-3 V1.2.1 (2014-06)
Note that for every know peer ITS station, a distinct VCI identified by destination_address.RemoteCIID of the
IN-UNITDATA.request service primitive / source_address.RemoteCIID of the IN-UNITDATA.indication service
primitive is given.
This configuration is used in the cases listed below [3]:
• ITS-S station internal-network PICS (PICS_S_INW) is set to false.
• The roles PICS (PICS_ROLE_RH) is set to true.
4.2.3 Test configuration CF02: ITS station-internal network
In test configuration CF02, the roles of ITS-S host and ITS-S router may be implemented in different ITS-SCUs as
illustrated in figure 4. It is considered for testing that the functionality of FNTP is separated into two parts, one part
available in an ITS-SCU with the role of an ITS-S host, and one part available in an ITS-SCU with the role of an ITS-S
host. Further on, presence of an ITS station-internal network is required.
t t
n n
e e
y y
t t
i i
m m
r r
e e
u u
g g
c c
a a
e e
n n
S S
a a
M M

Figure 4: Test configuration CF02 architecture
In this test configuration, the FNTP part located in the ITS-SCU with role of an ITS-S router is connected to
communication interfaces (CI) which establish a link to another instance of an ITS station, and to a communication
interface which establishes the connection to the ITS station internal network. The following address elements
contained in the element LinkID specified in [i.5] are used:
• To connect to the ITS station-internal network with IN-UNITDATA.request service primitive:
- LocalCIID, identifying uniquely a CI to connect to another ITS station, specified in the following PIXIT
variable:
PX_LAN_LOCAL_CIID
- RemoteCIID, identifying VCI for broadcast communications in destination_address.RemoteCIID of the
IN-UNITDATA.request service primitive, specified in the following PIXIT variable:
PX_LAN_REMOTE_CIID_BC
- RemoteCIID, identifying VCI for unicast communications in source_address.RemoteCIID of the
IN-UNITDATA.indication service primitive, specified in the following PIXIT variable:
PX_LAN_REMOTE_CIID_UC
Note that communications on the ITS station-internal network could also be unicast communications.
• To connect to another ITS station, see test configuration CF01.
Note that for every known peer ITS station, a distinct VCI is given.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 985-3 V1.2.1 (2014-06)
This configuration is used in the cases listed below [2]:
• ITS-S station internal-network PICS (PICS_S_INW) is set to true.
• Either one of the roles PICS (PICS_ROLE_RH, PICS_ROLE_RONLY, PICS_ROLE_HONLY) is set to true.
4.3 Test architecture
The present document implements the general TTCN-3 test architecture described in EG 202 798 [i.1], clause 6.3.2 and
clause 8.3.1.
Figure 5 shows the TTCN-3 test architecture used for the FNTP ATS.
• The MTC is of type ItsFNTP and communicates with the SUT over fntpPort in order to exchange FNTP
NPDUs between the FNTP test component and the FNTP IUT. The "ITS lower layers transport" system
adapter is used to enable usage of ITS lower layers in the SUT in case the IN-SAP is not directly accessible.
• The MTC communicates with the SUT over the utPort in order to trigger FNTP functionalities by simulating
primitives from e.g. application or LDM entities. It is required to trigger the FNTP layer in the SUT to send
FNTP messages, which are resulting from upper layer primitives. Furthermore, receiving FNTP messages may
result for the FNTP layer in sending primitives to the upper layer. The "Upper tester transport" system adapter
is used to adapt to the upper tester application implementation of the SUT.
• The MTC communicates with the SUT over the cfPort in order to perform settings in the SUT. The
"Configuration transport" system adapter is used to adapt to the configuration access implementation of the
SUT.

Figure 5: Test system architecture
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 985-3 V1.2.1 (2014-06)
NOTE: In CALM-compliant implementations, "Upper tester transport" and "Configuration Transport" may map
on the same ITS station-internal network.
4.4 Ports and abstract service primitives
4.4.1 Overview
The following TTCN-3 ports are used by the FNTP ATS:
• The fntpPort of type FntpPort is used to receive messages from and transmit messages to the IUT (via
IN-SAP).
• The utPort of type UpperTesterPort is used to receive service data units from and transmit service data units to
the IUT (via NF-SAP).
• The cfPort of type CfPort is used to configure the FNTP (via MN-SAP).
• The acPort of type AdapterControlPort is not used.
Every port provides "Abstract Service Primitives" (ASPs) as specified in the following clauses.
4.4.2 ASPs of the fntpPort
Two ASPs are used in the fntpPort:
• The INsapPrimitivesUp primitive used to send messages of type FNTPNPDU to the IUT.
• The INsapPrimitivesDown primitive used to receive messages of type FNTPNPDU from the IUT.
4.4.3 ASPs of the utPort
The following ASPs are used in the utPort:
• The UtInitialize primitive is used to initialize IUT.
• The UtFntpEvent primitive is used to send NF-SAP service primitives to the IUT.
• The UtFntpEventInd primitive is used to receive NF-SAP service primitives from the IUT.
4.4.4 ASPs of the cfPort
This port is used to monitor notifications from the IUT.
• The CfFntpEventInd primitive is used to receive messages at the MN-SAP.
5 ATS conventions
5.1 Testing conventions
5.1.1 Testing states
5.1.1.1 Initial state
All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking
the upper tester primitive UtInitialize.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 985-3 V1.2.1 (2014-06)
5.1.1.2 Final state
All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific
actions are required for the idle state in the base standard ISO 29281-1 [1], the function f_ poDefault does not invoke
any action.
As necessary, further actions may be included in the f_poDefault function.
5.1.2 Message types - ASN.1 definitions
Message types are defined in ASN.1. ASN.1 definitions from the base standard ISO 29281-1 [1] are directly imported
in TTCN-3 using the ASN.1 import method specified in ES 201 873-7 [8].
The following example shows the TTCN-3 import statement used to import ASN.1 definitions from ISO 29281-1 [1] in
the TTCN-3 modules:
import from CALMfntp language "ASN.1:1997" all;

5.2 Naming conventions
5.2.1 General guidelines
This test suite follows the naming convention guidelines provided in EG 202 798 [i.1].
5.2.2 Usage of Log statements
All TTCN-3 log statements use the following format:
• Three asterisks followed by a blank character.
• The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a
blank character.
• One of the possible log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed
by a colon and a blank character.
• Free text.
• A blank character followed by three asterisks.
EXAMPLE 1:
log("*** TC_FNTP_TXP_BP_BV_01: INFO: Preamble: FNTP Forwarding Table was setup properly ***");
Furthermore, the following rules are applied for the Fntp ATS:
• Log statements are used in the body of
...