ETSI TS 102 708-2-2 V1.5.1 (2018-08)

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; Sub-Part 2: Test Suite Structure and Test Purposes (TSS & TP)

RTS/ITS-00280

General Information

• Status: Published
• Publication Date: 29-Aug-2018
• Technical Committee: ITS WG2 - Architecture and Cross Layer
• Current Stage: 12 - Completion
• Due Date: 30-Aug-2018
• Completion Date: 30-Aug-2018

Standards Content (Sample)

ETSI TS 102 708-2-2 V1.5.1 (2018-08)






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;
Sub-Part 2: Test Suite Structure and Test Purposes (TSS & TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 708-2-2 V1.5.1 (2018-08)



Reference
RTS/ITS-00280
Keywords
application, DSRC, ITS, layer 7, protocol, 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/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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.

© ETSI 2018.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 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 . 7
4.4.1 Valid behaviour tests . 7
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 . 9
5.2 Test purposes for on-board units . 9
5.2.1 Kernel Unit . 9
5.2.1.1 Valid behaviour . 9
5.2.1.2 Invalid behaviour . 10
5.2.2 Read access . 12
5.2.2.1 Valid behaviour . 12
5.2.2.2 Invalid behaviour . 16
5.2.3 Write Access . 17
5.2.3.1 Valid behaviour . 17
5.2.3.2 Invalid behaviour . 27
5.2.4 Optional functionality . 27
5.2.4.1 Valid behaviour . 27
5.2.4.2 Invalid behaviour . 29
5.2.5 Security . 29
5.2.5.1 Valid behaviour . 29
5.2.5.2 Invalid behaviour . 43
5.2.6 Integrity constraints . 59
5.2.6.1 Invalid behaviour . 59
5.3 Test purposes for road side units . 71
5.3.1 Kernel Unit . 71
5.3.2 Read access . 72
5.3.3 Write access . 74
5.3.4 Optional functionality . 77
5.3.5 Security . 79
History . 86

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(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].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
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.
The objective of the present document is to provide a basis for conformance tests for DSRC-HDR equipment specified
in ETSI ES 200 674-1 [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
2.1 Normative 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
https://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.
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 200 674-1: "Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics
(RTTT); Dedicated Short Range Communications (DSRC); 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; Sub-Part 1: Protocol Implementation Conformance Statement (PICS) proforma
specification".
[3] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
2.2 Informative 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.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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.
Not applicable.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI ES 200 674-1 [1] and
ISO/IEC 9646-1 [3] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI ES 200 674-1 [1] and ISO/IEC 9646-1 [3]
apply.
4 Test Suite Structure
4.1 Structure
Table 1 shows the application layer test suite structure (TSS) including its groups defined for the conformance testing.
Table 1: Test suite structure for DSRC-HDR application layer
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
Invalid behaviour
Road Side Unit Valid behaviour
Write access On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Optional functionality On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Security On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Invalid behaviour
Integrity constraints On Board Unit Invalid behaviour

4.2 Test groups
There are six test groups defined for the application layer 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).
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
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.
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:
PICS 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 and 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.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
Table 3: TP naming convention
Identifier TP/////
= Type of SUT OBU On Board Unit
RSU Road Side Unit
AL Application Layer
KU Kernel Unit
RA Read Access
WA Write Access
OF Optional Functionality
IC Integrity Constraints
SC Security
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.

5.1.3 Sources of TP definitions
All TPs are specified according to the base standard ETSI ES 200 674-1 [1].
5.1.4 General reference
All references in the test purposes, if not stated differently, are indicating clauses of the base standard ETSI
ES 200 674-1 [1].
All references to PICS are indicating tables in ETSI TS 102 708-2-1 [2].
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.3, A.5/1, A.5/2, A5/3 and A.5/7 of the PICS [2] shall be implicitly selected for all TPs.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
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.3, B.5, B.6/1, B.6/4, B.9/1, B.9/2, B.9/3 and B.9/7 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.
5.2 Test purposes for on-board units
5.2.1 Kernel Unit
5.2.1.1 Valid behaviour
TP/OBU/AL/KU/BV/01 Verify that the IUT can handle Open-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.4/1 AND Table A.4/2 AND Table A.4/3 AND Table A.4/4
Initial conditions
with {
the IUT being in the "initial state"
}
Expected behaviour
ensure that {
when {
the IUT receives a valid Open-Rq with new private LinkID and an "AP Invocation Identifier" having a valid value
as specified by the applicant
}
then {
the IUT issues a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as received
}
}

TP/OBU/AL/KU/BV/02 Verify that the IUT can handle 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.4/1 AND Table A.4/2 AND Table A.4/3 AND Table A.4/4
Initial conditions
with {
the IUT being in the "initial state"
and the IUT having received a valid Open-Rq with new private LinkID and a valid "AP Invocation Identifier"
and the IUT having issued a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
Expected behaviour
ensure that {
when {
the IUT receives a valid Close-Rq with LinkID having the same value as in the initial conditions
}
then {
the IUT issues a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as received
}
}

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
TP/OBU/AL/KU/BV/03 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.4/1 AND Table A.4/2 AND Table A.4/3 AND Table A.4/4
Initial conditions
with {
the IUT being in the "initial state"
}
Expected behaviour
ensure that {
when {
the IUT receives a valid Open-Rq | Close-Rq with new private LinkID
}
then {
the IUT issues a response with "Result" set to '06'H and "Diagnostic" set to '00'H and with "AP Invocation
Identifier" having the same value as received
}
}

TP/OBU/AL/KU/BV/04 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.4/5 AND Table A.4/6
TC reference:
Initial condition:
Initial conditions
with {
the IUT being in the "initial state"
and the IUT having received a valid Open-Rq | Close-Rq with new private LinkID
and the IUT having issued a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
Expected behaviour
ensure that {
when {
the IUT receives a valid 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" as sent in the initial conditions
}
then {
the IUT issues a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
}

5.2.1.2 Invalid behaviour
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.4/5 AND Table A.4/6
Initial conditions
with {
the IUT being in the "initial state"
and the IUT having received a valid Open-Rq | Close-Rq with new private LinkID
and the IUT having issued a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
Expected behaviour
ensure that {
when {
the IUT receives a 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" as sent in the initial conditions, but with an invalid value of "Length"
}
then {
the IUT issues a response with "Result" set to '15'H and "Diagnostic" set to '04'H
}
}

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
TP/OBU/AL/KU/BI/02 Verify that the IUT supporting the EETS profile can manage Select-TBA-Id-Rq with an invalid
value
Reference: Clauses 11.5.4, 11.6.1, 11.6.2, 11.6.5 and D.2.2
PICS Selection: Table A.4/5 AND Table A.4/6 AND Table A.2/1
Initial conditions
with {
the IUT being in the "initial state"
and the IUT having received a valid Open-Rq | Close-Rq with new private LinkID
and the IUT having issued a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
Expected behaviour
ensure that {
when {
the IUT receives a valid 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" as sent in the initial conditions
}
then {
the IUT does not respond
}
}

TP/OBU/AL/KU/BI/03 Verify that the IUT not supporting the EETS profile 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.4/5 AND Table A.4/6 AND NOT Table A.2/1
Initial conditions
with {
the IUT being in the "initial state"
and the IUT having received a valid Open-Rq | Close-Rq with new private LinkID
and the IUT having issued a response with "Result" set to '06'H and "Diagnostic" set to '00'H
}
Expected behaviour
ensure that {
when {
the IUT receives a valid 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 previously
}
then {
the IUT does not respond OR the IUT responds with "Result" set to '15'H and "Diagnostic" set to '05'H
}
}

TP/OBU/AL/KU/BI/04 Verify that the IUT handles an invalid application identifier
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.4/1 AND Table A.4/2 AND Table A.4/3 AND Table A.4/4
Initial conditions
with {
the IUT being in the "initial state"
}
Expected behaviour
ensure that {
when {
the IUT receives a valid Open-Rq with new private LinkID and an invalid "AP Invocation Identifier" (different from
valid values specified by the applicant)
}
then {
the IUT issues a response with "Result" set to '15'H and "Diagnostic" set to '06'H
}
}

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 708-2-2 V1.5.1 (2018-08)
5.2.2 Read access
5.2.2.1 Valid behaviour
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.4/9 AND Table A.4/10
Initial conditions
with {
the IUT being in the "initial state"
}
Expected behaviour
ensure that {
repeat with different private LinkID and different combinations of "Offset" and "Length" parameters in order to cover
the whole Master Core
when {
the IUT receives a valid 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
}
then {
the IUT issues a response 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
}
}

TP/OBU/AL/RA/BV/02 Verify that the IUT can manage Read-Master-Core-Rq with broadcast LinkID
Refere
...