ETSI TS 102 760-2 V1.1.1 (2009-11)

ETSI TS 102 760-2 V1.1.1 (2009-11)
Technical Specification


Intelligent Transport Systems (ITS);
Test specifications for Intelligent Transport Systems;
Communications Access for Land Mobiles (CALM);
Medium Service Access Points (ISO 21218);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 760-2 V1.1.1 (2009-11)



Reference
DTS/ITS-0020009
Keywords
ITS, calm, testing, TSS&TP
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 2009.
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 760-2 V1.1.1 (2009-11)
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 architecture . 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 . 8
5.1.4 General reference . 8
5.1.5 General conditions . 8
5.1.6 M-SAP confirm service primitives . 8
5.2 CI state transitions . 9
5.2.1 Valid behaviour tests . 9
5.2.2 Invalid behaviour tests . 14
5.3 MIB parameters . 20
5.3.1 Valid behaviour tests . 20
5.3.2 Invalid behaviour tests . 26
5.4 Handling of CIs . 28
5.4.1 Valid behaviour tests . 28
5.4.2 Invalid behaviour tests . 32
5.5 Handling of data plane . 33
5.5.1 Valid behaviour tests . 33
5.5.2 Invalid behaviour tests . 46
Annex A (normative): Extension of "Inter-CCK Communications" . 49
A.1 General description. 49
A.2 Protocol data units . 49
A.2.1 ASN.1 . 49
A.2.2 IN-Request (64) . 50
A.2.3 IN-Indication (65). 51
History . 52

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 760-2 V1.1.1 (2009-11)
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 of a multi-part deliverable covering the test specifications for access layer service access
points and related procedures as identified below:
Part 1: "Implementation Conformance Statement (ICS) proforma";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and partial PIXIT proforma".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 760-2 V1.1.1 (2009-11)
1 Scope
The present document specifies "Test Suite Structure and Test Purposes" (TSS&TP) for the access layer service access
points MI-SAP and IN-SAP and related procedures as defined in ISO 21218 [1] in accordance with the relevant
guidance given in TS 102 760-1 [4], ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6] and ETS 300 406 [7].
NOTE: ISO 21218 [1] cannot be tested without being applied to a specific CALM-compliant communication
interface (CI). Conformance with ISO 21218 thus always is restricted to the CALM-compliant CI
declared in the ICS proforma [4].
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] ISO 21218-2008: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - Medium Service Access Points".
[2] DIS 21217-2009: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - Architecture".
[3] DIS 24102-2009: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - Management".
[4] ETSI TS 102 760-1: "Intelligent Transport Systems (ITS); Test specifications for Intelligent
Transport Systems; Communications Access for Land Mobiles (CALM); Medium Service Access
Points (ISO 21218); Part 1: Implementation Conformance Statement (ICS) proforma".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concept".
[6] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite Specification".
[7] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 760-2 V1.1.1 (2009-11)
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 21218 [1], ISO 21217, [2],
ISO 24102 [3], TS 102 760-1 [4], ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6] and the following apply:
tester: entity in the test architecture controlling the tests
tester CI: CI contained in the tester
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO 21218 [1], ISO 21217, [2], ISO 24102 [3],
TS 102 760-1 [4], ISO/IEC 9646-1 [5] and ISO/IEC 9646-2 [6] apply.
4 Test suite architecture
ISO 21218 [1] cannot be tested without being applied to a specific CALM-compliant communication interface (CI).
Thus the test architecture presented in figure 1 contains also the OSI communication layers PHY and DLL which are
below the "Communication Adaptation Layer" (CAL), both in the system under test (SUT) and in the tester.

Figure 1: Test architecture
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 760-2 V1.1.1 (2009-11)
The IUT is connected via three points of control and observation (PCO) with the tester:
• "PCO IN-SAP", providing access to the IN-SAP of the IUT;
• "PCO MI-SAP", providing access to the MI-SAP of the IUT;
• "PCO Link", the communication link.
Access to the MI-SAP preferably uses "Inter-CCK Communications" as specified in [3]. Access to the IN-SAP
preferably uses an extension of "Inter-CCK Communications" as specified in annex A. Alternative approaches to access
the IN-SAP and MI-SAP also are allowed.
NOTE: Not using "Inter-CCK Communications" to access IM-SAP and MI-SAP may cause extra cost to the
applicant in order to adapt the SUT to the test environment in a test house.
A SUT may contain several CIs. However in a given test at a given time, only a single of them together with the
functionality of ISO 21218 [1] shall constitute the IUT. Testing of a SUT containing several CIs thus requires repetition
of the tests for all CIs contained in the SUT.
Tests for a configuration with several active CIs in a single SUT are not considered in the present document.
5 Test purposes
5.1 Introduction
5.1.1 Definition conventions
The test purposes (TPs) are defined following particular rules as shown in table 1.
Table 1: 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 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 and 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 2.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 760-2 V1.1.1 (2009-11)
Table 2: TP naming convention
Identifier: TP///
group = Group of tests SE State event transitions
MB MIB M-parameters
HC Handling of CIs
DP Handling of data plane
x = Type of testing BV Valid Behaviour Tests
BI Invalid Behaviour Tests
= sequential number >0 Test Purpose Number

5.1.3 Sources of TP definitions
All TPs are specified according to requirements set up in ISO 21218 [1].
5.1.4 General reference
For all TPs the general references to clause 5.2.3 and to annex E of ISO 21218 [1] shall be applicable.
5.1.5 General conditions
The following pre-conditions shall apply for all TPs, if not defined differently in a specific TP:
• The CI-ID of all CIs not being in the CI state "not_existent" and of all existent VCIs shall be known to the
Tester, see figure 1.
• The MIB of the CI / VCI shall contain default values except for the M-parameters listed below.
- Parameter 11 "MinimumUserPriority" shall be set to zero if not requested differently.
Additional pre-conditions may apply for specific TPs.
5.1.6 M-SAP confirm service primitives
According to [1], the service primitives COMMAND.confirm and REQUEST.confirm shall be present in case of an
error and may be omitted otherwise. The optional presence of confirm service primitives with ErrStatus indicating
success are not explicitly included in the TPs, but will have to be considered in the abstract test suite, i.e. in part 3 of
this multi-part deliverable.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 760-2 V1.1.1 (2009-11)
5.2 CI state transitions
5.2.1 Valid behaviour tests
TP/SE/BV/01 Verify that the IUT with CI class different from "CIC-wl5" registers correctly at the
management entity
Reference: ISO 21218 [1]: clauses 5.2.1, 5.2.4.2, 5.2.4.10 and 5.3.2, annexes B and C
ICS Selection: NOT Table C.2/5
TC reference: TC_SE_BV_01
Initial condition: The IUT shall be in the CI state "not-existent"
Stimulus and Expected Behaviour:
1) Dependent on the implementation, request the IUT to start the registration procedure.
2) Verify reception of REQUEST 0 "RegReq" at the M-SAP with "MedType" equal to the value declared by the
applicant, "MAC address" set to the unique MAC address of the IUT as declared by the applicant, "CCK-ID"
and "MedID" contained in the "CI-ID" set to zero, and the "CtrlCI" bits contained in the "CI-ID" set to zero.
Note the "SerialNumber" contained in the "CI-ID".
3) Verify that the "SerialNumber" noted in step 2) is in the range 0x0001 to 0xFEFF.
4) Before the timer "T_register" expires in the IUT, send COMMAND 0 "RegCmd" via the M-SAP to the CI-ID
with CtrlCI bits, CCK-ID and MedID set to zero and the SerialNumber set to the value reported in step 2),
providing in "M-Command" correct values of "CCK-ID" and "MedID", and confirming the unique MAC
address.
5) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "registered".

TP/SE/BV/02 Verify that the IUT with CI class "CIC-wl5" registers correctly at the management entity
Reference: ISO 21218 [1]: clauses 5.2.1, 5.2.4.2, 5.2.4.10 and 5.3.2, annexes B and C
ICS Selection: Table C.2/5
TC reference: TC_SE_BV_02
Initial condition: The IUT shall be in the CI state "not-existent"
Stimulus and Expected Behaviour:
1) Dependent on the implementation, request the IUT to start the registration procedure.
2) Verify reception of REQUEST 0 "RegReq" at the M-SAP with "MedType" equal to the value declared by the
applicant, "MAC address" set to the unique MAC address of the IUT as declared by the applicant, "CCK-ID"
contained in the "CI-ID" set to zero, "MedID" contained in the "CI-ID" set to zero and the "CtrlCI" bits
contained in the "CI-ID" set to one. Note the "SerialNumber" contained in the "CI-ID".
3) Verify that the "SerialNumber" noted in step 2) is in the range 0x0001 to 0xFEFF.
4) Before the timer "T_register" expires in the IUT, send the COMMAND 0 "RegCmd" via the M-SAP to the CI-
ID with CtrlCI bits, CCK-ID and MedID set to zero and the SerialNumber set to the value reported in step 2),
providing in the M-COMMAND correct values of "CCK-ID" and "MedID", and confirming the unique MAC
address.
5) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "registered".

TP/SE/BV/03 Verify that the IUT with CI class "CIC-wl2" automatically creates a UC-VCI and reaches the CI
state "active"
Reference: ISO 21218 [1]: clauses 5.2.1, 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/2 AND Table C.6/3 AND Table C.8/16
TC reference: TC_SE_BV_03
Initial condition: The IUT shall be in the CI state "registered".
Stimulus and Expected Behaviour:
1) Oppose the IUT to the signals of a related base station and wait at least the time needed to register at the base
station.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created UC-VCI.

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 760-2 V1.1.1 (2009-11)
TP/SE/BV/04 Verify that the IUT with CI class "CIC-wl3" automatically creates a BC-VCI and reaches the CI
state "active"
Reference: ISO 21218 [1]: clauses 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/3 AND Table C.6/1 AND NOT Table C.6/2 AND Table C.8/14
TC reference: TC_SE_BV_04
Initial condition: The IUT shall be in the CI state "registered". MAC multicast groups are not known.
Stimulus and Expected Behaviour:
1) Wait at least the time needed to create a broadcast VCI.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created BC-VCI.

TP/SE/BV/05 Verify that the IUT with CI class "CIC-wl4" automatically creates a RX-VCI and reaches the CI
state "active"
Reference: ISO 21218 [1]: clauses 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/4 AND Table C.6/4 AND Table C.8/17
TC reference: TC_SE_BV_05
Initial condition: The IUT shall be in the CI state "registered"
Stimulus and Expected Behaviour:
1) Wait at least the time needed to create a RX-VCI.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created RX-VCI.

TP/SE/BV/06 Verify that the IUT with CI class "CIC-wl1" automatically creates a UC-VCI and a BC-VCI and
reaches the CI state "active"
Reference: ISO 21218 [1]: clauses 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/1 AND Table C.6/1 AND NOT Table C.6/2 AND Table C.6/3 AND Table
C.8/14 AND Table C.8/16
TC reference: TC_SE_BV_06
Initial condition: The IUT shall be in the CI state "registered". MAC multicast groups shall not be
known.
Stimulus and Expected Behaviour:
1) Wait at least the time needed to create a BC-VCI and a UC-VCI.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created UC-VCI, and verify reception of REQUEST 9 "Event" indicating the event number 3 and the
CI-ID of the newly created BC-VCI.

TP/SE/BV/07 Verify that the IUT with CI class "CIC-wl3" automatically creates a BC-VCI and known MC-VCIs
and reaches the CI state "active"
Reference: ISO 21218 [1]: clauses 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/3 AND Table C.6/1 AND Table C.6/2 AND Table C.8/14 AND Table C.8/15
TC reference: TC_SE_BV_07
Initial condition: The IUT shall be in the CI state "registered". MAC multicast groups shall be known.
Stimulus and Expected Behaviour:
1) Wait at least the time needed to create a broadcast VCI.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created BC-VCI, and ´for all known MAC multicast groups verify reception of REQUEST 9 "Event"
indicating the event number 3 and the CI-ID of the newly created MC-VCI.

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 760-2 V1.1.1 (2009-11)
TP/SE/BV/08 Verify that the IUT with CI class "CIC-wl1" automatically creates a UC-VCI a BC-VCI and known
MC-VCIs and reaches the CI state "active"
Reference: ISO 21218 [1]: clauses 5.2.4.10, 5.3.3.1 and 5.3.2; annex C
ICS Selection: Table C.2/1 AND Table C.6/1 AND Table C.6/2 AND Table C.6/3 AND Table C.8/14
AND Table C.8/15 AND Table C.8/16
TC reference: TC_SE_BV_08
Initial condition: The IUT shall be in the CI state "registered". MAC multicast groups shall be known.
Stimulus and Expected Behaviour:
1) Wait at least the time needed to create a broadcast VCI.
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created UC-VCI, and verify reception of REQUEST 9 "Event" indicating the event number 3 and the
CI-ID of the newly created BC-VCI, and for all known MAC multicast groups verify reception of REQUEST
9 "Event" indicating the event number 3 and the CI-ID of the newly created MC-VCI.

TP/SE/BV/09 Verify that the IUT deregisters correctly from the management entity
Reference: ISO 21218 [1]: clauses 5.2.4.3 and 5.2.4.10, annexes B and D
ICS Selection:
TC reference: TC_SE_BV_09
Initial condition: The IUT shall be in the CI state "active".
Stimulus and Expected Behaviour:
1) Issue COMMAND 1 "CIstateChng" with the value "deregister".
2) Wait at least the time declared by the applicant needed to perform deregistration.
3) Issue COMMAND 1 "CIstateChng" with the value "disconnect".
4) Verify that no change of state and no error are notified via the M-SAP.
5) Repeat steps 1) through 4) for the initial condition: The IUT shall be in the CI state "connected".
6) Repeat steps 1) through 4) for the initial condition: The IUT shall be in the CI state "suspended".
7) Repeat steps 1) through 4) for the initial condition: The IUT shall be in the CI state "inactive".

TP/SE/BV/10 Verify that the IUT correctly performs inactivation
Reference: ISO 21218 [1]: clauses 5.2.4.4 and 5.2.4.10; annexes B and C
ICS Selection:
TC reference: TC_SE_BV_10
Initial condition: The IUT shall be in the CI state "active".
Stimulus and Expected Behaviour:
1) Issue COMMAND 1 "CIstateChng" with the value "inactivate".
2) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "inactive".
3) Repeat steps 1) and 2) for the initial condition: The IUT shall be in the CI state "connected".
4) Repeat steps 1) and 2) for the initial condition: The IUT shall be in the CI state "suspended".

TP/SE/BV/11 Verify that the IUT with CI class "CIC-wl2" correctly performs activation
Reference: ISO 21218 [1]: clauses 5.2.4.5, 5.2.4.10, 5.3.3.1 and 5.3.2; annexes B and C
ICS Selection: Table C.2/2
TC reference: TC_SE_BV_11
Initial condition: The IUT shall be in the CI state "inactive".
Stimulus and Expected Behaviour:
1) Issue COMMAND 1 "CIstateChng" with the value "activate".
2) Oppose the IUT to the signals of a related base station and wait at least the time typically needed to register at
the base station.
3) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created UC-VCI.

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 760-2 V1.1.1 (2009-11)
TP/SE/BV/12 Verify that the IUT with CI class "CIC-wl3" correctly performs activation
Reference: ISO 21218 [1]: clauses 5.2.4.5, 5.2.4.10, 5.3.3.1 and 5.3.2; annexes B and C
ICS Selection: Table C.2/3
TC reference: TC_SE_BV_12
Initial condition: The IUT shall be in the CI state "inactive".
Stimulus and Expected Behaviour:
1) Issue COMMAND 1 "CIstateChng" with the value "activate".
2) Wait at least the time needed to create a broadcast VCI.
3) Verify reception of REQUEST 9 "Event" indicating the event number 5 and the M-parameter 42 "CIstatus" set
to "active", and verify reception of REQUEST 9 "Event" indicating the event number 3 and the CI-ID of the
newly created BC-VCI.

TP/SE/BV/13 Verify that the IUT with CI class "CIC-wl4" correctly performs activation
Reference: ISO 21218 [1]: clauses 5.2.4.5, 5.2.4.10, 5.3.3.1 and 5.3.2; annexes B and C
ICS Selection: Table C.2/4
TC reference: TC_SE_BV_13
Initial condition: The IUT shall be in the CI state "inactive".
Stimulus and Expected Behaviour:
1) Issue COMMAND 1 "CIstateChng" with the value "activate".
2) Wa
...