ETSI TS 102 708-2-2 V1.1.1 (2010-03)

Intelligent Transport Systems (ITS); RTTT; Test specifications for High Data Rate (HDR) data transmission equipment operating in the 5,8 GHz ISM band; Part 2: Application Layer Common Application Service Elements; Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)

DTS/ITS-0020006

General Information

• Status: Published
• Publication Date: 29-Mar-2010
• Technical Committee: ITS WG2 - Architecture and Cross Layer
• Current Stage: 12 - Completion
• Due Date: 06-Apr-2010
• Completion Date: 30-Mar-2010
• Mandate: M/338

Standards Content (Sample)

ETSI TS 102 708-2-2 V1.1.1 (2010-03)
Technical Specification

Intelligent Transport Systems (ITS);
RTTT;
Test specifications for High Data Rate (HDR) data
transmission equipment operating in the 5,8 GHz ISM band;
Part 2: Application Layer Common Application
Service Elements;
Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 708-2-2 V1.1.1 (2010-03)



Reference
DTS/ITS-0020006
Keywords
DSRC, application, layer 7, ITS, testing
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
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 2010.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being 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 708-2-2 V1.1.1 (2010-03)
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 Structure . 6
4.2 Test groups . 6
4.3 Type of SUT . 6
4.4 Behaviour test groups . 6
4.4.1 Valid behaviour tests . 6
4.4.2 Invalid behaviour tests . 7
5 Test purposes . 7
5.1 Introduction . 7
5.1.1 Definition conventions . 7
5.1.2 Naming conventions . 7
5.1.3 Sources of TP definitions . 8
5.1.4 General reference . 8
5.1.5 General conditions . 8
5.1.6 Default PICS selection . 8
5.1.7 Presentation conventions . 8
5.2 Test purposes for on-board units . 9
5.2.1 Kernel Unit . 9
5.2.1.1 Valid behaviour tests . 9
5.2.1.2 Invalid behaviour tests . 9
5.2.2 Read access . 10
5.2.3 Write Access . 12
5.2.4 Optional functionality . 16
5.2.4.1 Valid behaviour tests . 16
5.2.4.2 Invalid behaviour tests . 17
5.2.5 Integrity constraints . 17
5.3 Test purposes for road side units . 22
5.3.1 Kernel Unit . 22
5.3.2 Read access . 22
5.3.3 Write access . 23
5.3.4 Optional functionality . 24
Annex A (informative): Test coverage matrix . 26
A.1 Introduction . 26
A.2 OBU . 26
A.3 RSU . . 28
History . 30

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
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://webapp.etsi.org/IPR/home.asp).
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, sub-part 2 of a multi-part deliverable covering the test specifications for High Data Rate
(HDR) Dedicated Short Range Communication (DSRC).
Full details of the entire series can be found in part 2-1 [2].
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
1 Scope
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the Dedicated Short Range
Communication (DSRC) High Data Rate (HDR) Application Layer Common Application Service Elements.
The objective of this test specification is to provide a basis for conformance tests for DSRC-HDR equipment specified
in [1] giving a high probability of inter-operability between different manufacturer's equipment.
The ISO standard for the methodology of conformance testing ISO/IEC 9646-1 [3] is used as a basis for the test
methodology.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
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 indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 200 674-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Road
Transport and Traffic Telematics (RTTT); Part 1: Technical characteristics and test methods for
High Data Rate (HDR) data transmission equipment operating in the 5,8 GHz Industrial, Scientific
and Medical (ISM) band".
[2] ETSI TS 102 708-2-1: "Intelligent Transport Systems (ITS); RTTT; Test specifications for High
Data Rate (HDR) data transmission equipment operating in the 5,8 GHz ISM band;
Part 2: Application Layer Common Application Service Elements; Sub-Part 1: Protocol
Implementation Conformance Statement (PICS) proforma specification".
[3] ISO/IEC 9646-1 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
3 Definitions and abbreviations
3.1 Definitions
For the purpose of the present document, the terms and definitions given in [1] and [3] apply.
3.2 Abbreviations
For the purpose of the present document, the abbreviations given in [1] and [3] apply.
4 Test Suite Structure
4.1 Structure
Table 1 shows the application layer common application service elements test suite structure (TSS) including its groups
defined for the conformance testing.
Table 1: Test suite structure for DSRC-HDR application layer common application service elements
Group Type of system under test (SUT) Behaviour
Kernel unit On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Read access On Board Unit Valid behaviour
Road Side Unit Valid behaviour
Write access On Board Unit Valid behaviour
Road Side Unit Valid behaviour
Optional functionality On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Integrity constraints On Board Unit Invalid behaviour

4.2 Test groups
There are five test groups defined for the application layer common application service elements of DSRC-HDR as
presented in table 1.
4.3 Type of SUT
Two types of systems under test (SUT) are distinguished, i.e. on board units (OBUs) and road side units (RSUs).
4.4 Behaviour test groups
4.4.1 Valid behaviour tests
Valid behaviour tests shall verify that the IUT reacts in conformity with the base standard [1], after receipt or exchange
of valid protocol data units (PDUs). "Valid PDU" means that the exchange of messages and the content of the
exchanged messages are considered as valid, i.e. compliant with the base standard.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
4.4.2 Invalid behaviour tests
Invalid behaviour tests shall verify that the IUT reacts in conformity with the base standard [1], after receipt of a
syntactically invalid protocol data unit (PDU).
5 Test purposes
5.1 Introduction
5.1.1 Definition conventions
Test purposes (TPs) are defined following particular rules as presented in table 2.
Table 2: TP definition rules
TP ID Title:
Reference:
ICS Selection:
TC Reference:
Initial condition:
Stimulus and Expected behaviour:

TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming
conventions defined in the clause below.
Title Short description of test purpose objective.
Reference The reference should contain the references of the subject to be validated by the actual
TP (specification reference, clause, paragraph).
PICS Selection Reference to the PICS statement involved for selection of the TP. Contains a Boolean
expression. Only those ICS statements are shown that are explicitly related to the test.
TC reference
Shows the reference number of the related test case in the ATS.
Initial condition The condition defines in which initial state the IUT has to be to apply the actual TP.
Stimulus and Expected Definition of the events the tester performs, and the events that are expected from the
behaviour
IUT to conform to the base specification.

5.1.2 Naming conventions
The identifier of the TP is built according to table 3.
Table 3: TP naming convention
Identifier TP/////
= Type of SUT OBU On Board Unit
RSU Road Side Unit
AL Data Link Layer
KU Kernel Unit
RA Read Access
WA Write Access
OF Optional Functionality
IC Integrity Constraints
x = Type of testing BV Valid Behaviour Test
BI Invalid Behaviour Test
= sequential number >0 = sequential number
NOTE: All tests specified in the present document are application layer tests. The term in the TP identifier is
used to have a consistent TP reference covering also the tests on the data link layer provided in a separate
part of this multi-part deliverable.

ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
5.1.3 Sources of TP definitions
All TPs are specified according to the base standard ES 200 674 [1].
5.1.4 General reference
All references in the test purposes, if not stated differently, are indicating clauses of the base standard ES 200 674 [1].
All references to PICS are indicating tables in part 2 sub-part 1 [2] of this multi-part deliverable.
5.1.5 General conditions
For all TPs related to OBUs the following pre-conditions shall apply, if not defined differently for a specific TP:
• The SUT (OBU) shall be ready for communication, i.e. it shall not be in sleep mode and all boot processes
shall be finalized.
• The "AP Invocation Identifier" used in the SUT shall be as defined by the applicant.
• "Responding Mode" used in the SUT (RSU) shall be set to "response-slow-speed", if not required differently
for a specific TP.
• The SUT (OBU) shall have no active association with the tester (RSU).
For all TPs related to RSUs, the following general conditions shall apply, if not defined differently for a specific TP:
• The SUT (RSU) shall provide means which allow issuing requests for APDUs to be transmitted.
• Repetition of a request message shall be possible only in case a reply was not received within due time.
NOTE: From this it follows that repetitive or periodic request messages are disabled in the SUT.
Additional pre-conditions may apply for specific TPs.
5.1.6 Default PICS selection
For all TPs related to OBUs the following PICS selections shall apply in addition to those specified for a specific TP:
• Tables A.1, A.2, A.4/1, A.4/2 and A.4/3 of the PICS [2] shall be implicitly selected for all TPs.
For all TPs related to RSUs the following PICS selections shall apply in addition to those specified for a specific TP:
• Tables B.1, B.2, B.4/1, B.4/2 and B.4/3 of the PICS [2] shall be implicitly selected for all TPs.
Further PICS selections may apply as specified for a specific TP. These either select options of the base standard [1] or
give hints on the major properties to be tested.
5.1.7 Presentation conventions
Concatenation of directives in a single frame shall be indicated with the symbol |.
EXAMPLE: Concatenation of Open-Rq with Close-Rq is presented as
Open-Rq | Close-Rq,
with Open-Rq sent first.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
5.2 Test purposes for on-board units
5.2.1 Kernel Unit
5.2.1.1 Valid behaviour tests
TP/OBU/AL/KU/BV/01
Verify that the IUT can handle Open-Rq and Close-Rq
Reference: Clauses 11.5.2, 11.5.3, 11.6.1, 11.6.2, 11.6.3 and 11.6.4
PICS Selection: Table A.3/1 AND Table A.3/2 AND Table A.3/3 AND Table A.3/4
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq with new private LinkID.
2) Verify reception of a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as used in step 1).
3) Tester sends Close-Rq with LinkID as used in step 1).
4) Verify reception of a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as used in step 3).
5) Tester sends Open-Rq | Close-Rq with new private LinkID.
6) Verify reception of a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as used in step 5).

TP/OBU/AL/KU/BV/02 Verify that the IUT can handle Select-TBA-Id-Rq
Reference: Clauses 11.5.4, 11.6.1, 11.6.2 and 11.6.5
PICS Selection: Table A.3/5 AND Table A.3/6
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Close-Rq with new private LinkID.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H. Note the value of
"Called AP Title".
3) Tester sends Open | Select-TBA-Id-Rq | Close-Rq with new private LinkID and with "Responding AP Title" set equal
to the value of "Called AP Title" noted in step 2).
4) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H.

5.2.1.2 Invalid behaviour tests
TP/OBU/AL/KU/BI/01 Verify that the IUT can manage Select-TBA-Id-Rq with an invalid length
Reference: Clauses 11.5.4, 11.6.1, 11.6.2 and 11.6.5
PICS Selection: Table A.3/5 AND Table A.3/6
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Close-Rq with new private LinkID.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostics" set to '00'H. Note the value of
"Called AP Title".
3) Tester sends Open | Select-TBA-Id-Rq | Close-Rq with new private LinkID and with "Responding AP Title" set equal
to the value of "Called AP Title" noted in step 2), but giving a wrong value of "Length".
4) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '05'H.

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
TP/OBU/AL/KU/BI/02 Verify that the IUT can manage Select-TBA-Id-Rq with an invalid value
Reference: Clauses 11.5.4, 11.6.1, 11.6.2 and 11.6.5
PICS Selection: Table A.3/5 AND Table A.3/6
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Close-Rq new private LinkID.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H. Note the value of
"Called AP Title".
3) Tester sends Open | Select-TBA-Id-Rq | Close-Rq with new private LinkID and with "Responding AP Title" set equal
to a value different to "Called AP Title" noted in step 2), but with correct value of "Length".
4) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '05'H.

5.2.2 Read access
TP/OBU/AL/RA/BV/01
Verify that the IUT can manage Open-Rq | Read-Master-Core-Rq | Close-Rq
Reference: Clauses 11.5.6, 11.6.2 and 11.6.7
PICS Selection: Table A.3/9 AND Table A.3/10
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Read-Master-Core-Rq | Close-Rq with new private LinkID and with valid combinations of
"Offset" and "Length" in Read-Master-Core-Rq in order to retrieve a part of or the whole master core.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Master-Core-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole master
core, each with new private LinkID.

TP/OBU/AL/RA/BV/02 Verify that the IUT can manage Read-Master-Core-Rq with broadcast LinkID
Reference: Clauses 11.5.6, 11.6.2 and 11.6.7
PICS Selection: Table A.3/9 AND Table A.3/10
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Read-Master-Core-Rq with broadcast LinkID and with valid combinations of "Offset" and "Length" in
Read-Master-Core-Rq in order to retrieve a part of or the whole master core.
2) Verify reception of a response message with "Result " set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Master-Core-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole master
core.

TP/OBU/AL/RA/BV/03 Verify that the IUT can manage Open-Rq | Read-Appl-Core-Rq | Close-Rq
Reference: Clauses 11.5.7, 11.6.2 and 11.6.8
PICS Selection: Table A.3/11 AND Table A.3/12
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Read-Appl-Core-Rq | Close-Rq with new private LinkID and with valid combinations of
"Offset" and "Length" in Read-Appl-Core-Rq in order to retrieve a part of or the whole application core.
2) Verify reception of a response message with "Result " set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Appl-Core-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole
application core, each with new private LinkID.

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
TP/OBU/AL/RA/BV/04 Verify that the IUT can manage Read-Appl-Core-Rq with broadcast LinkId
Reference: Clauses 11.5.7, 11.6.2 and 11.6.8
PICS Selection: Table A.3/11 AND Table A.3/12
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Read-Appl-Core-Rq with broadcast LinkID with valid combinations of "Offset" and "Length" in Read-
Appl-Core-Rq in order to retrieve a part of or the whole application core.
2) Verify reception of a response message with “"Result”" set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Appl-Core-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole
application core.

TP/OBU/AL/RA/BV/05 Verify that the IUT can manage Open-Rq | Read-Appl-Record-Rq | Close-Rq
Reference: Clauses 11.5.10, 11.6.2 and 11.6.11
PICS Selection: Table A.3/17 AND Table A.3/18
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Read-Appl-Record-Rq | Close-Rq with new private LinkID and with valid combinations of
"Offset" and "Length" in Read-Appl-Record -Rq in order to retrieve a part of or the whole application record.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Appl-Record-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole
application record, each with new private LinkID.

TP/OBU/AL/RA/BV/06
Verify that the IUT can manage Read-Appl-Record-Rq with broadcast LinkId
Reference: Clauses 11.5.10, 11.6.2 and 11.6.11
PICS Selection: Table A.3/17 AND Table A.3/18
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Read-Appl-Record-Rq with broadcast Link ID with valid combinations of "Offset" and "Length" in Read-
Appl-Record-Rq in order to retrieve a part of or the whole application record.
2) Verify reception of a response message with "Result”" set to '06'H and "Diagnostic" set to '00'H, and with the data of
"Read-Appl-Record-Rs" as specified by the applicant for the selected range.
3) Repeat steps 1) and 2) for different valid combinations of "Offset" and "Length" in order to cover the whole
application record.

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 708-2-2 V1.1.1 (2010-03)
5.2.3 Write Access
TP/OBU/AL/WA/BV/01 Verify that the IUT can manage Open-Rq | Select-TBA-Id-Rq | Write-Appl-Core-Rq | Close-Rq
Reference: Clauses 11.5.8, 11.6.2 and 11.6.9
PICS Selection: Table A.3/13 AND Table A.3/14
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends Open-Rq | Read-Appl-Core-Rq | Close-Rq with new private LinkID and with valid combinations of
"Offset" and "Length" in Read-Appl-Core-Rq in order to retrieve a part of or the whole application core.
2) Verify reception of a response message with "Result" set to '06'H and "Diagnostic" set to '00'H. Note the data
retrieved. Note the value of "Called AP Title".
3) Tester sends Open-Rq | Select-TBA-Id-Rq | Write-Appl-Core-Rq | Close-Rq with new private LinkID with the same
value of "Offset" and "Length" as used in step 1) and with
...