ETSI TS 102 486-2-2 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 2: DSRC application layer; Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)

RTS/ITS-0040009

General Information

• Status: Published
• Publication Date: 05-Oct-2008
• Technical Committee: ITS WG4 - Media and Medium related
• Current Stage: 12 - Completion
• Due Date: 27-Aug-2008
• Completion Date: 06-Oct-2008
• Mandate: M/270
• Mandate: M/338

Standards Content (Sample)

ETSI TS 102 486-2-2 V1.2.1 (2008-10)
Technical Specification

Intelligent Transport Systems (ITS);
Road Transport and Traffic Telematics (RTTT);
Test specifications for Dedicated Short
Range Communication (DSRC) transmission equipment;
Part 2: DSRC application layer;
Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 486-2-2 V1.2.1 (2008-10)



Reference
RTS/ITS-0040009
Keywords
ITS, DSRC, 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
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

---------------------- Page: 2 ----------------------
3 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Test Suite Structure (TSS) . 6
4.1 Structure . 6
4.2 Test groups . 6
4.3 Type of SUT test groups . 7
4.4 Behaviour test groups . 7
4.4.1 Valid Behaviour (BV) tests . 7
4.4.2 Invalid Behaviour (BI) tests . 7
5 Test Purposes (TP) . 7
5.1 Introduction . 7
5.1.1 TP definition conventions . 7
5.1.2 TP naming conventions . 7
5.1.3 Sources of TP definitions . 8
5.2 Application T-kernel test purposes for On Board Unit. 8
5.2.1 BV test purposes . 8
5.2.2 BI test purposes . 13
5.3 Application T-kernel test purposes for Road Side Unit . 14
5.3.1 BV test purposes . 14
5.3.2 BI test purposes . 15
5.4 Application I-kernel test purposes for On Board Unit . 16
5.4.1 BV test purposes . 16
5.4.2 BI test purposes . 19
5.5 Application I-kernel test purposes for Road Side Unit . 20
5.5.1 BV test purposes . 20
5.5.2 BI test purposes . 21
Annex A (informative): Test coverage matrix . 23
A.1 Introduction . 23
A.2 OBU test coverage matrix . 23
A.3 RSE test coverage matrix . 30
History . 37

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 486-2-2 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 2, sub-part 2 of a multi-part deliverable covering Intelligent Transport
Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated ShortRange
Communication (DSRC) transmission equipment as identified below:
Part 1: "DSRC data link layer: medium access and logical link control";
Part 2: "DSRC application layer";
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".

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
1 Scope
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the Dedicated Short Range
Communication (DSRC); Application 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 [5] and ISO/IEC 9646-2 [6]) as well as
the ETSI rules for conformance testing (ETS 300 406 [4]) 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 12834 (2003): "Road transport and traffic telematics - Dedicated Short Range
Communication (DSRC) - DSRC application layer".
[2] CEN EN 12253 (2003): "Road transport and traffic telematics - Dedicated short-range
communication - Physical layer using microwave at 5,8 GHz".
[3] CEN EN 13372 (2003): "Road transport and traffic telematics (RTTT) - Dedicated short-range
communication - Profiles for RTTT".
[4] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[5] ISO/IEC 9646-1 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
[6] ISO/IEC 9646-2 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract Test Suite specification".
[7] ISO/IEC 9646-6 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 6: Protocol profile test specification".
[8] ISO/IEC 9646-7 (1991): "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-7 [8], EN 12253 [2],
EN 12834 [1] and EN 13372 [3] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-6 [7],
ISO/IEC 9646-7 [8] and EN 12834 [1] and the following apply:
PrWRq MAC frame Private Window Request
4 Test Suite Structure (TSS)
4.1 Structure
Figure 1 shows the Application Test Suite Structure (TSS) including its subgroups defined for the conformance testing.
Group Type of SUT behaviour
Application Layer - T-Kernel On Board Unit Valid behaviour
 Invalid behaviour
Road Side Unit Valid behaviour
 Invalid behaviour
Application Layer - I-Kernel On Board Unit Valid behaviour
 Invalid behaviour
Road Side Unit Valid behaviour
 Invalid behaviour

Figure 1: TSS for DSRC Application
4.2 Test groups
The test groups are organized in three groups. The first is designed for the application T-kernel testing. The second is
designed for Application I-kernel testing and the third is designed for Application B-kernel testing.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
4.3 Type of SUT test groups
The type of SUT test groups are organized in two groups. The first is designed for the On Board Unit testing and the
second is designed for Road Side Unit testing.
4.4 Behaviour test groups
4.4.1 Valid Behaviour (BV) tests
This test sub group shall verify that the IUT reacts in conformity with the EN, after receipt or exchange of a valid
Protocol Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged
messages are considered as valid.
4.4.2 Invalid Behaviour (BI) tests
This test sub group shall verify that the IUT reacts in conformity with the EN, after receipt of a syntactically
invalid PDU.
5 Test Purposes (TP)
5.1 Introduction
5.1.1 TP definition conventions
The TPs are defined following particular rules as shown in table 1.
Table 1: TP definition rules
TP Id according to the TP Title
naming conventions
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, paragraph).
PICS selection Reference to the PICS statement involved for selection of the TP. Contains a Boolean
expression. Only those PICS 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 TP naming conventions
The identifier of the TP is built according to table 2.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
Table 2: TP naming convention
Identifier: TP///-
AL-T Application Layer - T-Kernel
 AL-I Application Layer - I-Kernel
= type of SUT OBU On Board Unit
 RSU Road Side Unit
x = Type of testing BV Valid Behaviour Tests
 BI Invalid Behaviour Tests
= sequential number (01-99) Test Purpose Number

5.1.3 Sources of TP definitions
All TPs are specified according to EN 12834 [1].
5.2 Application T-kernel test purposes for On Board Unit
5.2.1 BV test purposes
Test subgroup objective:
- to test the behaviour of the IUT in relation to syntactically and contextual correct behaviour of the test system.
Test purposes:
TP/AL-T/OBU/BV/01 Verify that the OBU can receive GET.request and manage GET.response, with
LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.11/5
AND Table E.2/11 AND Table E.3/9
TC reference: TC_AL_T_OBU_BV_01
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends GET.request with FlowControl=7, requesting retrieval of data
available in the IUT without late response.
2. Verify IUT provides the data requested in step 1 in a GET-Response with proper
ReturnStatus.

TP/AL-T/OBU/BV/02 Verify that the OBU can receive SET.request with mode=1 and manage
SET.response, with LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/3 AND Table A.8/4 AND Table A.15/4
AND Table E.2/12 AND Table E.3/10
TC reference: TC_AL_T_OBU_BV_02
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=1 and FlowControl=7, requesting storage
of data=DATA in the IUT.
2. Verify proper ReturnStatus indicated in the SET-Response.

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
TP/AL-T/OBU/BV/03 Verify that the OBU can receive SET.request with mode=1 and GET.request, and
manage SET.response and GET.response, with LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3
AND Table A.8/4 AND Table A.11/5 AND Table A.15/4 AND Table
E.2/11 AND Table E.2/12 AND Table E.3/9 AND Table E.3/10
TC reference: TC_AL_T_OBU_BV_03
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=1 and FlowControl=7, requesting storage
of data=DATA1 in the attribute given by EID=EID1 and attributeId=attributeID1
in the IUT.
2. Verify proper ReturnStatus indicated in the SET-Response.
3. Tester sends GET.request in order to retrieve the data sent in step 1.
4. Verify proper ReturnStatus indicated in the GET-Response.
5. Verify that the data retrieved in step 3 is identical to the data sent in step 1.
6. Tester sends SET.request with mode=1 and FlowControl=7, requesting storage
of data=DATA2 in the attribute given by EID=EID1 and attributeId=attributeID1
in the IUT.
7. Verify proper ReturnStatus indicated in the SET-Response.
8. Tester sends GET.request in order to retrieve the data sent in step 6.
9. Verify proper ReturnStatus indicated in the GET-Response.
10. Verify that the data retrieved in step 8 is identical to the data sent in step 6.

TP/AL-T/OBU/BV/04 Verify that the OBU can receive SET.request with mode=0 and GET.request and
GET.response, with LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3
AND Table E.2/9 AND Table E.2/11 AND Table E.3/6 AND Table
E.3/10
TC reference: TC_AL_T_OBU_BV_04
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=0 and FlowControl=4, requesting storage
of DATA1 in the attribute given by EID=EID1 and attributeId=attributeID1 of the
IUT.
2. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1
using GET.request.
3. Tester sends SET.request with mode=0 and FlowControl=4, requesting storage
of DATA2 in the attribute given by EID=EID1 and attributeId=attributeID1 in the
IUT.
4. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1
using GET.request.

TP/AL-T/OBU/BV/05 Verify that the OBU can receive SET.request with mode=0 and GET.request and
GET.response, with LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3
AND Table E.3/6 AND Table E.2/11 AND Table E.3/9
TC reference: TC_AL_T_OBU_BV_05
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=0 and FlowControl=1, requesting storage
of DATA1 in the data element given by EID=EID1 and attributeId=attributeID1 of
the IUT.
2. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1
using GET.request.
3. Tester sends SET.request with mode=0 and FlowControl=1, requesting storage
of DATA2 in the data element given by EID=EID1 and attributeId=attributeID1 in
the IUT.
4. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1
using GET.request.

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
TP/AL-T/OBU/BV/06 Verify that the OBU can receive SET.request with mode=0 and with LID=broadcast
after initialization,and GET.request and manage GET.response, with private LID
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3
AND Table E.3/4 AND Table E.2/11 AND Table E.3/9
TC reference: TC_AL_T_OBU_BV_06
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=0, FlowControl=1 and LID=broadcast,
requesting storage of data=DATA1 in the IUT.
2. Tester sends GET.request in order to retrieve the data sent in step 1.
3. Verify that the data retrieved in step 2 is identical to the data sent in step 1.
4. Tester sends SET.request with mode=0 and FlowControl=1 and LID=broadcast,
requesting storage of data=DATA2 in the IUT.
5. Tester sends GET.request in order to retrieve the data sent in step 4.
6. Verify that the data retrieved in step 5 is identical to the data sent in step 4.

TP/AL-T/OBU/BV/07 Verify that the OBU can receive SET.request with mode=0 and with LID=broadcast
without initialization, and GET.request and manage GET.response, with private LID
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.2/5 AND Table A.3/3 AND Table A.8/1
AND Table A.8/2 AND Table A.8/3 AND Table C.4/7 AND Table
E.3/4 AND Table E.2/11 AND Table E.3/9
TC reference: TC_AL_T_OBU_BV_07
Initial condition: OBU not in sleep mode and not yet initialized.
Stimulus and Expected Behaviour:
1. Tester sends SET.request with mode=0, FlowControl=1 and LID=broadcast,
requesting storage of data=DATA1 in the IUT.
2. Perform initialization with the IUT.
3. Tester sends GET.request in order to retrieve the data sent in step 1.
4. Verify that the data retrieved in step 2 is identical to the data sent in step 1.
5. Tester sends RELEASE command.
6. Tester immediately, i.e. before beacon time-out,sends SET.request with
mode=0, FlowControl=1 and LID=broadcast, requesting storage of data=DATA2
in the IUT.
7. Repeat step 2 after beacon time-out.
8. Tester sends GET.request in order to retrieve the data sent in step 6.
9. Verify that the data retrieved in step 8 is identical to the data sent in step 6.

TP/AL-T/OBU/BV/08 Verify that the OBU can receive ACTION.request with mode=1 and manage
ACTION.response, with LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/5 AND Table A.8/6 AND Table E.2/13
AND Table E.3/11
TC reference: TC_AL_T_OBU_BV_08
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends ACTION.request with mode=1 and FlowControl=7.
2. Verify proper operation of IUT by checking the ACTION.response.

TP/AL-T/OBU/BV/09 Verify that the OBU can receive ACTION.request with mode=0 and LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/5 AND Table E.2/10
TC reference: TC_AL_T_OBU_BV_09
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends ACTION.request with mode=0 and FlowControl=4.
2. Verify proper operation of IUT by human observation of IUT behaviour.
NOTE: The applicant shall declare the SET_MMI ACTION type if possible, that allows human observation of
command execution.

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
TP/AL-T/OBU/BV/10 Verify that the OBU can receive ACTION.request with mode=0 and LID=private
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/5 AND Table E.2/7
TC reference: TC_AL_T_OBU_BV_10
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends ACTION.request with mode=0 and FlowControl=1.
2. Verify proper operation of IUT by human observation of IUT behaviour.
NOTE: The applicant shall declare the SET_MMI ACTION type if possible, that allows human observation of
command execution.

TP/AL-T/OBU/BV/11 Verify that the OBU can receive ACTION.request with mode=0 with LID=broadcast
after initialization
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.1/1 AND Table A.8/5 AND Table E.2/5
TC reference: TC_AL_T_OBU_BV_11
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends ACTION.request with mode=0, FlowControl=1 and LID=broadcast.
2. Verify proper operation of IUT by human observation of IUT behaviour.
NOTE: The applicant shall declare the SET_MMI ACTION type if possible, that allows human observation of
command execution.

TP/AL-T/OBU/BV/12 Verify that the OBU can receive and manage ACTION.request with mode=0 and
with LID=broadcast without initialization
Reference: EN 12834 [1] clauses 6.2 and Annex A
PICS Selection: Table A.8/5 ANDTable E.2/5
TC reference: TC_AL_T_OBU_BV_12
Initial condition: OBU not in sleep mode and not yet initialized.
Stimulus and Expected Behaviour:
1. Tester sends ACTION.request with mode=0, FlowControl=1 and LID=broadcast.
2. Verify proper operation of IUT by human observation of IUT behaviour.
NOTE: The applicant shall declare the SET_MMI ACTION type if possible, that allows human observation of
command execution.

TP/AL-T/OBU/BV/13 Verify that the OBU can receive and manage non-fragmented APDUs with random
PDU number
Reference: EN 12834 [1] clauses 6.3.3
PICS Selection: Table A.1/1 AND
(
(Table E.2/11 AND Table E.3/9) OR
(Table E.2/12 AND Table E.3/10) OR
(Table E.2/13 AND Table E.3/11)
)
TC reference: TC_AL_T_OBU_BV_13
Initial condition: OBU already initialized, waiting to be served by tester.
Stimulus and Expected Behaviour:
1. Tester sends SERVICE.request with mode=1 and FlowControl=7 with a random
choice of PDU number in the allowed range of 2 through 31.
2. Verify IUT correctly replies with SERVICE.response.
3. Repeat steps 1 and 2 until all allowed values of the PDU number field are
tested.
NOTE: SERVICE shall be out of GET, SET, ACTION, as declared by the applicant.

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 486-2-2 V1.2.1 (2008-10)
TP/AL-T/OBU/BV/14 Verify that the OBU can receive and manage multiplexed APDUs from two different
applications
Reference: EN 12834 [1] clauses 6.3.5 and 6.3.9
PICS Selection: Table A.1/1 AND Table A.2/6 AND Table A.6/7
(
(Table E.2/11 AND Table E.3/9) OR
(Table E.2/12 AND Table E.3/10) OR
(Table E.2/13 AND Table E.3/11)
)
TC reference: TC_AL_T_OBU_BV_14
Initial condition: OBU already initialized for two applications #A and #B, waiting to be
served by tester. It is allowed to be #A = #B, i.e. APDUs related only
...