ETSI TS 102 486-1-3 V1.2.1 (2008-10)
Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment; Part 1: DSRC data link layer: medium access and logical link control; Sub-Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma
Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment; Part 1: DSRC data link layer: medium access and logical link control; Sub-Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma
RTS/ITS-0040007
General Information
Standards Content (Sample)
Technical Specification
Intelligent Transport Systems (ITS);
Road Transport and Traffic Telematics (RTTT);
Test specifications for Dedicated Short
Range Communication (DSRC) transmission equipment;
Part 1: DSRC data link layer:
medium access and logical link control;
Sub-Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma
�
2 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
Reference
RTS/ITS-0040007
Keywords
ITS, DSRC, MAC, LLC, protocol, testing, ATS,
TTCN, PIXIT
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 2008.
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.
ETSI
3 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
Contents
Intellectual Property Rights . 8
Foreword . 8
1 Scope . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 10
4 Abstract Test Method (ATM) . 11
4.1 DSRC MAC layer Abstract Test Method (ATM) for OBU . 11
4.1.1 Test architecture . 11
4.1 DSRC MAC layer Abstract Test Method (ATM) for RSU . 11
4.1.1 Test architecture . 12
4.2 DSRC LLC layer Abstract Test Method (ATM) . 12
4.2.1 Test architecture . 13
4.2 Test strategy . 13
5 Untestable Test Purposes (TP) . 14
6 ATS conventions . 14
6.1 Naming conventions . 14
6.1.1 Declarations part . 14
6.1.1.1 General . 14
6.1.1.2 Test suite operations . 14
6.1.1.3 Test suite parameter declarations . 15
6.1.1.4 Test case selection expression definition . 15
6.1.1.5 Test suite constant declarations . 15
6.1.1.6 Test suite variable declarations . 15
6.1.1.7 Test case variable declarations . 15
6.1.1.8 Timer declarations . 15
6.1.1.9 ASP type definitions . 15
6.1.1.10 PDU type definitions . 15
6.1.1.11 Co-ordination Message (CM) type definitions . 15
6.1.1.12 Alias definitions . 15
6.1.2 Constraints part . 16
6.1.2.1 General . 16
6.1.2.2 TTCN ASN.1 Constraints . 16
6.1.2.3 TTCN ASP Constraints . 16
6.1.2.4 TTCN PDU Constraints . 16
6.1.3 Dynamic part . 16
6.1.3.1 General . 16
6.1.3.2 Test Case (TC) identifier . 16
6.1.3.3 Test step identifier . 16
6.1.3.4 Default identifier . 17
6.2 Implementation conventions . 17
6.2.1 Declaration part . 17
6.2.2 Constraint part . 17
6.2.3 Dynamic part . 17
Annex A (normative): Abstract Test Suite (ATS) for MAC OBU . 18
A.1 The TTCN Graphical form (TTCN.GR) . 18
A.2 The TTCN Machine Processable form (TTCN.MP) . 18
ETSI
4 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
A.3 Specification of PTC1 . 18
A.3.1 General requirements . 18
A.3.2 Additional requirements . 18
Annex B (normative): Abstract Test Suite (ATS) for MAC RSU . 20
B.1 The TTCN Graphical form (TTCN.GR) . 20
B.2 The TTCN Machine Processable form (TTCN.MP) . 20
B.3 Specification of PTC1 . 20
B.3.1 General requirements . 20
B.3.2 Additional requirements . 20
Annex C (normative): Abstract Test Suite (ATS) for LLC OBU . 21
C.1 The TTCN Graphical form (TTCN.GR) . 21
C.2 The TTCN Machine Processable form (TTCN.MP) . 21
Annex D (normative): Abstract Test Suite (ATS) for LLC RSU . 22
D.1 The TTCN Graphical form (TTCN.GR) . 22
D.2 The TTCN Machine Processable form (TTCN.MP) . 22
Annex E (normative): Partial PIXIT proforma for MAC OBU . 23
E.1 Identification summary. 23
E.2 ATS summary . . 23
E.3 Test laboratory . 23
E.4 Client identification . 23
E.5 SUT . 24
E.6 Protocol layer information. 24
E.6.1 Protocol identification . 24
E.6.2 IUT information . 24
Annex F (normative): Partial PIXIT proforma for MAC RSU. 25
F.1 Identification summary. 25
F.2 ATS summary . . 25
F.3 Test laboratory . 25
F.4 Client identification . 25
F.5 SUT . 26
F.6 Protocol layer information. 26
F.6.1 Protocol identification . 26
F.6.2 IUT information . 26
Annex G (normative): Partial PIXIT proforma for LLC OBU . 27
G.1 Identification summary. 27
G.2 ATS summary . . 27
G.3 Test laboratory . 27
G.4 Client identification . 27
G.5 SUT . 28
G.6 Protocol layer information. 28
G.6.1 Protocol identification . 28
ETSI
5 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
G.6.2 IUT information . 29
Annex H (normative): Partial PIXIT proforma for LLC RSU . 30
H.1 Identification summary. 30
H.2 ATS summary . . 30
H.3 Test laboratory . 30
H.4 Client identification . 30
H.5 SUT . 31
H.6 Protocol layer information. 31
H.6.1 Protocol identification . 31
H.6.2 IUT information . 32
Annex I (normative): PCTR Proforma for MAC OBU . 33
I.1 Identification summary. 33
I.1.1 Protocol conformance test report . 33
I.1.2 IUT identification . 33
I.1.3 Testing environment . 33
I.1.4 Limits and reservation . 34
I.1.5 Comments. 34
I.2 IUT Conformance status . 34
I.3 Static conformance summary . 34
I.4 Dynamic conformance summary . 35
I.5 Static conformance review report . 35
I.6 Test campaign report . 36
I.7 Observations . 36
Annex J (normative): PCTR Proforma for MAC RSU . 37
J.1 Identification summary. 37
J.1.1 Protocol conformance test report . 37
J.1.2 IUT identification . 37
J.1.3 Testing environment . 37
J.1.4 Limits and reservation . 38
J.1.5 Comments. 38
J.2 IUT Conformance status . 38
J.3 Static conformance summary . 38
J.4 Dynamic conformance summary . 39
J.5 Static conformance review report . 39
J.6 Test campaign report . 40
J.7 Observations . 40
Annex K (normative): PCTR Proforma for LLC OBU . 41
K.1 Identification summary. 41
K.1.1 Protocol conformance test report . 41
K.1.2 IUT identification . 41
K.1.3 Testing environment . 41
K.1.4 Limits and reservation . 42
K.1.5 Comments. 42
K.2 IUT Conformance status . 42
ETSI
6 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
K.3 Static conformance summary . 42
K.4 Dynamic conformance summary . 43
K.5 Static conformance review report . 43
K.6 Test campaign report . 43
K.7 Observations . 44
Annex L (normative): PCTR Proforma for LLC RSU . 45
L.1 Identification summary. 45
L.1.1 Protocol conformance test report . 45
L.1.2 IUT identification . 45
L.1.3 Testing environment . 45
L.1.4 Limits and reservation . 46
L.1.5 Comments. 46
L.2 IUT Conformance status . 46
L.3 Static conformance summary . 46
L.4 Dynamic conformance summary . 47
L.5 Static conformance review report . 47
L.6 Test campaign report . 47
L.7 Observations . 48
Annex M (normative): Profile requirements for MAC OBU . 49
M.1 Generic test cases . 49
M.2 Specific test cases . 49
M.3 Non relevant test cases . 49
M.4 Modified test campaign report . 50
M.5 Observations . 50
Annex N (normative): Profile requirements for MAC RSU . 51
N.1 Generic test cases . 51
N.2 Specific test cases . 51
N.3 Non relevant test cases . 51
N.4 Modified test campaign report . 52
N.5 Observations . 52
Annex O (normative): Profile requirements for LLC OBU . 53
O.1 Generic test cases . 53
O.2 Specific test cases . 53
O.3 Non relevant test cases . 53
O.4 Modified test campaign report . 53
O.5 Observations . 54
Annex P (normative): Profile requirements for LLC RSU . 55
P.1 Generic test cases . 55
P.2 Specific test cases . 55
ETSI
7 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
P.3 Non relevant test cases . 55
P.4 Modified test campaign report . 55
P.5 Observations . 56
Annex Q (informative): Bibliography . 57
History . 58
ETSI
8 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
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 3 of a multi-part deliverable covering Intelligent Transport Systems (ITS);
Dedicated Short Range Communication (DSRC); Data Link Control (DLC) layer as identified below:
Part 1: "DSRC data link layer: medium access and logical link control";
Sub-part 1: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Sub-part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Sub-part 3: "Abstract Test Suite (ATS) and partial PIXIT proforma".
Part 2: "DSRC application layer".
ETSI
9 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
1 Scope
The present document contains the Abstract Test Suite (ATS) and partial PIXIT proforma to test the Dedicated Short
Range Communication (DSRC); Data Link Control (DLC) layer.
The objective of this test specification is to provide a basis for conformance tests for DSRC equipment 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 [4], ISO/IEC 9646-2 [5] and
ISO/IEC 9646-3 [6]) as well as the ETSI rules for conformance testing (ETS 300 406 [3]) are 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.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
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] CEN EN 12795 (2003): "Road transport and traffic telematics - Dedicated Short Range
Communication (DSRC) - DSRC data link layer: medium access and logical link control".
[2] CEN EN 13372 (2003): "Road transport and traffic telematics (RTTT) - Dedicated short-range
communication - Profiles for RTTT".
[3] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[5] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite Specification".
ETSI
10 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
[6] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[7] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
Conformance Assessment process".
[8] ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 6: Protocol Profile Test Specification".
[9] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance statement".
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.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [4], EN 12795 [1],
EN 13372 [2] and the following apply:
blocked signal: signal without clock and bit information, e.g. a very weak signal
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [4], ISO/IEC 9646-6 [8],
ISO/IEC 9646-7 [9], EN 12795 [1], EN 13372 [2] and the following apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BV Valid Behaviour
CM Co-ordination Message
CP Co-ordination Point
IUT Implementation Under Test
LT Lower Tester
MTC Master Test Component
PCO Point of Control and Observation
PHL Physical Layer
PrWA MAC frame Private Window Allocation
PrWRq MAC frame Private Window Request
PT Portable radio Termination
PTC Parallel Test Component
SAP Service Access Point
SUT System Under Test
TTCN Tree and Tabular Combined Notation
UT Upper Tester
ETSI
11 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
4 Abstract Test Method (ATM)
4.1 DSRC MAC layer Abstract Test Method (ATM) for OBU
This clause describes the ATM used to test the DSRC MAC layer at the OBU side.
4.1.1 Test architecture
Figure 1: Test architecture for OBU DSRC MAC layer
A parallel testing concept is used, which consists of the following abstract testing parts:
Tester: A test machine that is running a TTCN engine allowing parallel testing and having a
standard DSRC Physical layer.
SUT: System under test.
MTC: Master test component used to perform the test, and start/stop/configure the Lower MAC
Emulation Parallel Test Component.
MAC: A standard DSRC MAC layer to be tested.
Lower_MAC_SAP: Interface between the Lower MAC emulation and MTC. MAC frames, minus their FCS and
flags, are passed via this SAP. In addition, specific frame timing information is passed
upwards on this SAP.
Lower MAC emulation: An DSRC MAC emulation performing some additional functions needed for covering the
test purposes in addition of the behaviour of a standard DSRC MAC layer. In particular,
FCS and flags are added/removed as required, and timing information on received frames
is provided to the MTC.
4.1 DSRC MAC layer Abstract Test Method (ATM) for RSU
This clause describes the ATM used to test the DSRC MAC layer at the RSU side.
ETSI
12 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
4.1.1 Test architecture
Tes ter
SUT
MTC
PH Y -S A P
PTC1
CP -M AC
L ead M A C
APP L
PTC 2
emulation
A nalyse
LL C
lo g file
MA C em ulation MAC
PH Y PHY
Figure 2: Test architecture for RSU DSRC MAC layer
A parallel testing concept is used, which consists of the following abstract testing parts:
Tester: A test machine that is running a TTCN engine allowing parallel testing and having a
standard DSRC Physical layer.
SUT: System under test: Can be RSU or OBU Implementation.
MTC: Master test component used to synchronize the parallel test components and to provide the
final verdict of the test.
PTC1: Parallel test component that is in charge of managing the MAC emulation by using external
function like Start emulation, Stop emulation and some other behaviours needed for
covering all test purposes.
PTC2: Parallel test component that is in charge of analysing the log file to verify the conformity
with the corresponding test purpose at MAC frame level.
MAC: A standard DSRC MAC layer to be tested.
Log File: Log file containing a trace of the physical frame exchange.
PHY-SAP: For TTCN point of view: it is a PCO in which only receive events (without flags, FCS and
after 0 insertion suppression) are observed and no control functions are provided.
CP-MAC: Interface between the MAC emulation and PTC1. Usually a collection of Test Suite
Operation implemented to command the behaviour of the MAC emulation.
MAC emulation: A golden DSRC MAC emulation performing some additional functions needed for
covering the test purposes in addition of the behaviour of a standard DSRC MAC layer.
4.2 DSRC LLC layer Abstract Test Method (ATM)
This clause describes the ATM used to test the DSRC LLC layer at the OBU side and at the RSU side.
ETSI
13 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
4.2.1 Test architecture
Tester
SUT
MAC
SAP
Test
Case
APPL
LLC
MAC
MAC
PHY
PHY
Figure 3: Test architecture for DSRC LLC layer
A single party testing concept is used, which consists of the following abstract testing parts:
Tester: A test machine that is running a TTCN engine allowing single testing and having standard
DSRC MAC and Physical layer.
SUT: System under test: Can be RSU or OBU Implementation.
Test Case: A standard TTCN test case.
LCC: A standard DSRC LLC layer to be tested.
MAC: A standard DSRC MAC layer.
MAC-SAP: To be defined or standard SAP referring to the standard.
4.2 Test strategy
The ATM defined in clauses 4.1.1 and 4.2.1 requires the use of concurrent TTCN, which is specified in
ISO/IEC 9646-3 [6]. The parallel test components PTC1 and PTC2 are, however, seen as two independent entities. This
means that there is no communication or synchronization between the two PTCs during the test.
PTC2 is specified in TTCN (see annex A). Since PTC2 is only observing at the PCO, this ATS does not contain any
send statements. Once the Test Purposes (TP) are fulfilled, the PTC2 terminates, i.e. there are no postambles, unless
required by the TP.
The requirements for PTC1 (see annex B) are specified using EN 12795 [1].
ETSI
14 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
The Master Test Component (MTC) creates the two PTCs (using CREATE operation), PTC1 stimulates the emulation,
and then MTC waits for the two PTCs to terminate (using the DONE event). The final verdict is computed as follows:
- a PASS is assigned if PTC2 returns a PASS verdict and the expected event is received from PTC1;
- a FAIL verdict is assigned if PTC2 returns a FAIL verdict independently of what is received from PTC1;
- an INCONC verdict is assigned if: PTC2 returns an INCONC verdict and the expected event is received from
PTC1, or returns a PASS verdict and an unexpected event is received from PTC1.
5 Untestable Test Purposes (TP)
This clause gives a list of TPs which are not implemented in the Abstract Test Suites due to the chosen Abstract Test
Method or other restrictions.
Table 1: Untestable TPs
Test purpose Reason
6 ATS conventions
The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions
made for the development of the ATS. These conventions shall be considered during any later maintenance or further
development of the ATS.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming
conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the
functional structure of the ATS.
To define the ATS, the guidelines of the document ETS 300 406 [3] was considered.
6.1 Naming conventions
6.1.1 Declarations part
This clause describes the naming conventions chosen for the elements of the ATS declarations part.
6.1.1.1 General
The following general rules apply for the names given in the declarations part.
Names of ASN.1 types imported from the base standard are preserved.
Predefined types (e.g. BITSTRING [7]) are never used in structured type definitions, ASP type definitions or PDU type
definitions. Simple types are used instead.
All declarations in the test suite are listed in alphabetical order. A different order of listing should be used for only
maintenance reasons.
6.1.1.2 Test suite operations
The test suite operation identifiers are prefixed with "TSO_".
EXAMPLE: TSO_substring.
ETSI
15 ETSI TS 102 486-1-3 V1.2.1 (2008-10)
6.1.1.3 Test suite parameter declarations
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the test suite
parameter identifiers are prefixed "TSPC_".
EXAMPLE 1: TSPC_extended_rf_carriers.
If the test suite parameter references a PIXIT item, the suite parameter identifiers are prefixed "TSPX_".
EXAMPLE 2: TSPX_pmid.
If the test suite parameter represents a system parameter, the complete name defi
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...