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

DTS/ITS-0020003

General Information

Status
Published
Publication Date
22-Mar-2010
Current Stage
12 - Completion
Due Date
26-Mar-2010
Completion Date
23-Mar-2010
Mandate
Ref Project

Buy Standard

Standard
ETSI TS 102 708-1-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 1: Data Link Layer; Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)
English language
17 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 102 708-1-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 1: Data Link Layer;
Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)

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



Reference
DTS/ITS-0020003
Keywords
DSRC, TSS&TP, RTTT, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 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-1-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 . 6
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 . 7
5.1.4 General reference . 7
5.1.5 General conditions . 8
5.1.6 Default PICS selection . 8
5.2 Test purposes for on-board units . 8
5.2.1 Valid behaviour tests . 8
5.2.2 Invalid behaviour tests . 9
5.3 Test purposes for road side units . 10
5.3.1 Valid behaviour tests . 10
5.3.2 Invalid behaviour tests . 11
Annex A (informative): Test coverage matrix . 14
A.1 Introduction . 14
A.2 OBU . 14
A.3 RSU . . 15
History . 17

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 708-1-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 1, 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 1-1 [2].
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 708-1-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) data link layer [1].
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-1-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 1: Data
Link Layer; 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-1-2 V1.1.1 (2010-03)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] and [3] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in [1] and [3] apply.
4 Test Suite Structure
4.1 Structure
Table 1 shows the DLL Test Suite Structure (TSS) including its subgroups defined for the conformance testing.
Table 1: Test suite structure for DSRC-HDR data link layer
Group Type of system under test (SUT) Behaviour
Data link layer On Board Unit Valid behaviour
Invalid behaviour
Road Side Unit Valid behaviour
Invalid behaviour

4.2 Test groups
There is a single test group for the data link layer of DSRC-HDR.
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.
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).
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 708-1-2 V1.1.1 (2010-03)
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 sub-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).
ICS Selection Reference to the ICS 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 .
Table 3: TP naming convention
Identifier TP////
= Type of SUT OBU On Board Unit
RSU Road Side Unit
DLL Data Link Layer
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 data link layer tests. The term in the TP identifier is
used to have a consistent TP reference covering also the tests on the application layer provided in a separte
part of this multi-part deliverable.

5.1.3 Sources of TP definitions
All TPs are specified according to the base standard 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 ES 200 674-1 [1].
All references to PICS are indicating tables in TS 102 708-1-1 [2].
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 708-1-2 V1.1.1 (2010-03)
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 OBU shall be ready for communication, i.e. it shall not be in sleep mode and all boot processes shall be
finalized.
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/1, A.4/3 and A.4/9 of the PICS [2] is implicitly selected for all TPs.
For all TPs retaled to RSUs the following PICS selections shall apply in addition to those specified for a specific TP:
• Tables A.1/2, A.4/2, A.4/8 and A.5/1 of the PICS [2] is implicitly selected for all TPs.
Further PICS selections may apply as specified for a specific TP. These only give hints on the major properties to be
tested, as the base standard [1] does not contain selectable options.
5.2 Test purposes for on-board units
5.2.1 Valid behaviour tests
TP/OBU/DLL/BV/01 Verify that the IUT can reply to requests providing proper values in the LLC address field
Reference: Clauses 10.9.1, 10.4.1 and 10.4.2
PICS Selection: Table A.3/1
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends a frame to the IUT upon which a reply is expected.
2) Verify that the tester receives the expected reply with the LLC address field of the received frame containing the
same value as the LLC address field transmitted in step 1).

TP/OBU/DLL/BV/02 Verify that the IUT can receive downlink frames of maximum allowed length as defined by
N2
Reference: Clause 10.2.2.4
PICS Selection: Table A.5/4
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends downlink frame containing any sequence of PDUs in such a way that the number of octets in the frame
equals the maximum number as defined by N2.
2) Verify IUT properly confirms the requests send in step 1) by a corresponding uplink frame.

TP/OBU/DLL/BV/03 Verify that the IUT implements correctly the timing constraint T for uplink windows
umax
Reference: Clause 10.9.2
PICS Selection: Table A.5/3
TC reference:
Initial condition:
Stimulus and Expected Behaviour:
1) Tester sends a frame to the IUT containing a valid request upon which reception of a frame of maximum length from
the IUT is expected.
2) Verify that the tester receives the expected reply from the IUT. Tester records time T from the end of the last bit
umax
of the closing flag of the frame containing the request from the tester until t
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.