ETSI TS 103 191-2 V1.2.1 (2017-03)

Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Facilities layer protocols and communication requirements for infrastructure services; Part 2: Test Suite Structure and Test Purposes (TSS & TP)

RTS/ITS-00176

General Information

• Status: Published
• Publication Date: 27-Mar-2017
• Technical Committee: ITS WG1 - Application Requirements and Services
• Current Stage: 12 - Completion
• Due Date: 31-Mar-2017
• Completion Date: 28-Mar-2017

Standards Content (Sample)

TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
Testing;
Conformance test specifications for
Facilities layer protocols and communication requirements
for infrastructure services;
Part 2: Test Suite Structure and Test Purposes (TSS & TP)

2 ETSI TS 103 191-2 V1.2.1 (2017-03)

Reference
RTS/ITS-00176
Keywords
ITS, 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.

© European Telecommunications Standards Institute 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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
3 ETSI TS 103 191-2 V1.2.1 (2017-03)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Test Suite Structure (TSS) . 8
4.1 Structure for MAPEM-SPATEM tests . 8
4.1.1 Test groups. 8
4.1.1.1 Introduction . 8
4.1.1.2 Root . 8
4.1.1.3 Groups . 8
4.1.1.4 Categories. 8
4.2 Structure for IVIM tests . 8
4.2.1 Test groups. 9
4.2.1.1 Introduction . 9
4.2.1.2 Root . 9
4.2.1.3 Groups . 9
4.2.1.4 Categories. 9
4.3 Structure for SREM-SSEM tests . 9
4.3.1 Test groups. 9
4.3.1.1 Introduction . 9
4.3.1.2 Root . 9
4.3.1.3 Groups . 10
4.3.1.4 Categories. 10
5 Test Purposes (TPs) . 10
5.1 Introduction . 10
5.1.1 TP definition conventions . 10
5.1.2 TP Identifier naming conventions . 10
5.1.3 Rules for the behaviour description . 10
5.1.4 Sources of TP definitions . 11
5.1.5 Mnemonics for PICS reference . 11
5.2 Requirements . 11
5.2.1 Traffic Light Manoeuvre (TLM) service . 11
5.2.1.1 Check the message protocol version . 11
5.2.1.2 TLM service trigger, update, repetition and termination. 12
5.2.1.3 Check presence of destination area . 13
5.2.1.4 Check BTP type and port number . 13
5.2.1.5 Check destination type . 14
5.2.1.6 TLM security parameters . 14
5.2.1.6.1 Check TLM ITS AID value . 14
5.2.1.6.2 Check TLM SSP version . 15
5.2.1.6.3 Check TLM Service specific parameters . 16
5.2.2 Road and Lane Topology (RLT) service . 21
5.2.2.1 Check that RLT protocol version is set to 1 . 21
5.2.2.2 Check the RLT message fragmenting . 22
5.2.2.3 Check continuous transmission with the SPAT messages . 23
5.2.2.4 Check BTP type and port number . 23
5.2.2.5 Check destination type . 24
5.2.3 Infrastructure to Vehicle Information (IVI) service . 24
ETSI
4 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.2.3.1 Check that IVIM protocol version is set to 1 . 24
5.2.3.2 Check that new iviIdentificationNumber value is generated for each new request . 25
5.2.3.3 Check that the value of iviIdentificationNumber is not used recently . 25
5.2.3.4 Check that a new generated IVIM contains an iviStatus set to 'new' . 26
5.2.3.5 Check that an updated IVIM contains an iviStatus set to 'update' . 26
5.2.3.6 Check that an update can change or add the end time to the IVIM . 27
5.2.3.7 Check that the timeStamp is set to the current time when generating a new IVM or last change of
information content (if iviStatus set to update) . 28
5.2.3.8 Check that the iviIdentificationNumber remains unchanged IVIM is updated . 29
5.2.3.9 Check that IVIM are generated in respect of a pre-defined repetition interval . 29
5.2.3.10 Check that the IVI Service activates repetition under the request from the ITS-S application . 30
5.2.3.11 Check that the IVI Service terminates IVM generation on validity duration expiry or on
termination request . 31
5.2.3.12 Check that the IVI Service terminates IVM generation on cancellation request . 32
5.2.3.13 Check that the IVI Service terminates IVM generation on negation request . 32
5.2.3.14 Check BTP type and port number . 33
5.2.3.15 Check destination type . 33
5.2.4 Traffic Light Control (TLC) service . 34
5.2.4.1 Check that SREM protocol version is set to 1 . 34
5.2.4.2 Check that SSEM protocol version is set to 1 . 34
5.2.4.3 Check that the IUT identifies SREM with a unique request identifier . 35
5.2.4.4 Check that the IUT increments the sequenceNumber when a SREM update is generated . 36
5.2.4.5 Check BTP type and port number . 36
5.2.4.6 Check destination type . 37
History . 38

ETSI
5 ETSI TS 103 191-2 V1.2.1 (2017-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 (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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS).
The present document is part 2 of a multi-part deliverable covering Conformance test specifications for Facilities layer
protocols and communication requirements for infrastructure services, as identified below:
Part 1: "Test requirements and Protocol Implementation Conformance Statement (PICS) pro forma";
Part 2: "Test Suite Structure and Test Purposes (TSS & TP)";
Part 3: "Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)".
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
6 ETSI TS 103 191-2 V1.2.1 (2017-03)
1 Scope
The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for MAPEM-SPATEM, IVIM
and SREM-SSEM as defined in SAE J2735 [1] and ETSI TS 103 301 [2] in compliance with the relevant requirements
and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.4]. The ISO standards for the methodology of
conformance testing (ISO/IEC 9646-1 [i.2] and ISO/IEC 9646-2 [i.3]) as well as the ETSI rules for conformance testing
(ETSI ETS 300 406 [i.5]) are 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
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.
The following referenced documents are necessary for the application of the present document.
[1] SAE J2735 (2016-03): "Dedicated Short Range Communications (DSRC) Message Set
Dictionary™".
[2] ETSI TS 103 301 (V1.1.1) (2016-11): "Intelligent Transport Systems (ITS); Vehicular
Communications; Basic Set of Applications; Facilities layer protocols and communication
requirements for infrastructure services".
[3] ETSI TS 103 191-1 (V1.2.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for Facilities layer protocols and communication requirements for infrastructure
services; Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS)
pro forma".
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.
[i.1] ETSI EG 202 798 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for
conformance and interoperability testing".
[i.2] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 1: General concepts".
[i.3] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification".
ETSI
7 ETSI TS 103 191-2 V1.2.1 (2017-03)
[i.4] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[i.5] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in SAE J2735 [1], ISO/IEC 9646-1 [i.2] and
in ISO/IEC 9646-7 [i.4] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
BTP Basic Transport Protocol
BV Valid test events for Behaviour tests
GN GeoNetworking
ISO International Organization for Standardization
ITS Intelligent Transport Systems
IUT Implementation Under Test
IVI Infrastructure to Vehicle Information
IVIM IVI-message
MAPEM MapData Messages
MSD Message Dissemination
MSP Message Processing
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
RLT Road and Lane Topology
SAE Society of Automotive Engineers
SHB Single Hop Broadcast
SPATEM Signal Phase And Timing Messages
SREM Signal Request Message
SSEM Signal Response Message
TLC Traffic Light Control
TLM Traffic Light Manoeuvre
TP Test Purposes
TSS Test Suite Structure
ETSI
8 ETSI TS 103 191-2 V1.2.1 (2017-03)
4 Test Suite Structure (TSS)
4.1 Structure for MAPEM-SPATEM tests
Table 1 shows the MAPEM-SPATEM Test Suite Structure (TSS) including its subgroups defined for conformance
testing.
Table 1: TSS for MAPEM-SPATEM
Root Group Category
MAPEM-SPATEM Message Dissemination Valid
Message processing Valid
The test suite is structured as a tree with the root defined as MAPEM-SPATEM. The tree is of rank 2 with the first rank
a Group and the second a category. The second rank is the standard ISO conformance test categories.
4.1.1 Test groups
4.1.1.1 Introduction
The test suite has a total of three levels. The first level is the root. The second level separates the root into various
functional areas. The third level is the standard ISO conformance test categories.
4.1.1.2 Root
The root identifies the MapData and SPAT Messages given in SAE J2735 [1] and ETSI TS 103 301 [2].
4.1.1.3 Groups
This level contains two functional areas identified as:
• Message Dissemination
• Message Processing
4.1.1.4 Categories
This level contains the standard ISO conformance test categories limited to valid behaviour.
4.2 Structure for IVIM tests
Table 2 shows the IVIM Test Suite Structure (TSS) including its subgroups defined for conformance testing.
Table 2: TSS for IVIM
Root Group Category
IVIM Message Dissemination Valid
Message processing Valid
The test suite is structured as a tree with the root defined as IVI. The tree is of rank 2 with the first rank a Group and the
second a category. The second rank is the standard ISO conformance test categories.
ETSI
9 ETSI TS 103 191-2 V1.2.1 (2017-03)
4.2.1 Test groups
4.2.1.1 Introduction
The test suite has a total of three levels. The first level is the root. The second level separates the root into various
functional areas. The third level is the standard ISO conformance test categories.
4.2.1.2 Root
The root identifies the IVI Messages given in ETSI TS 103 301 [2].
4.2.1.3 Groups
This level contains two functional areas identified as:
• Message Dissemination
• Message Processing
4.2.1.4 Categories
This level contains the standard ISO conformance test categories limited to valid behaviour.
4.3 Structure for SREM-SSEM tests
Table 3 shows the SREM-SSEM Test Suite Structure (TSS) including its subgroups defined for conformance testing.
Table 3: TSS for SREM-SSEM
Root Group Category
SREM-SSEM Message Dissemination Valid
Message processing Valid
The test suite is structured as a tree with the root defined as SREM-SSEM. The tree is of rank 2 with the first rank a
Group and the second a category. The second rank is the standard ISO conformance test categories.
4.3.1 Test groups
4.3.1.1 Introduction
The test suite has a total of three levels. The first level is the root. The second level separates the root into various
functional areas. The third level is the standard ISO conformance test categories.
4.3.1.2 Root
The root identifies the SREM and SSEM given in ETSI TS 103 301 [2].
ETSI
10 ETSI TS 103 191-2 V1.2.1 (2017-03)
4.3.1.3 Groups
This level contains two functional areas identified as:
• Message Dissemination
• Message Processing
4.3.1.4 Categories
This level contains the standard ISO conformance test categories limited to valid behaviour.
5 Test Purposes (TPs)
5.1 Introduction
5.1.1 TP definition conventions
The TP definition is built according to ETSI EG 202 798 [i.1].
5.1.2 TP Identifier naming conventions
The identifier of the TP is built according to table 4.
Table 4: TP naming convention
Identifier TP//// Example
= root IS_TLM
IS_RLT
IS_IVI
IS_TLC
= group MSGF Message Dissemination
EVUP Event Update
EVGN Event Generation
EVTR Event Termination
COMM Communication
GFQ Timers
SEC_SND Send behaviour of Security
Send behaviour of Specific
SSP_SND
service Permission
Receive behaviour of Specific
SSP_RCV
service Permission
= type of testing BV Valid event tests
= sequential number 01 to 99

5.1.3 Rules for the behaviour description
The description of the TP is built according to ETSI EG 202 798 [i.1].
SAE J2735 [1] does not use finite state machine concept. As consequence, the test purposes use a generic "Initial State"
that corresponds to a state where the IUT is ready for starting the test execution. Furthermore, the IUT shall be left in
this "Initial State", when the test is completed.
Being in the "Initial State" refers to the starting point of the initial device configuration. There are no pending actions,
no instantiated buffers or variables, which could disturb the execution of a test.
ETSI
11 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.1.4 Sources of TP definitions
All TPs have been specified according to SAE J2735 [1] and ETSI TS 103 301 [2].
5.1.5 Mnemonics for PICS reference
To avoid an update of all TPs when the PICS document is changed, table 5 introduces mnemonics name and the
correspondence with the real PICS item number.
The PICS item column refers to tables and items of ETSI TS 103 191-1 [3]. The 'PICS item' as defined in ETSI
TS 103 191-1 [3] shall be used to determine the test applicability.
Table 5: Mnemonics for PICS reference
Mnemonic PICS item
PICS_SPATEM_GENERATION A.2/3
PICS_SPATEM_RECEPTION A.2/4
PICS_MAPEM_GENERATION A.2/1
PICS_MAPEM_RECEPTION A.2/2
PICS_IVIM_GENERATION A.3/1
PICS_IVIM_RECEPTION A.3/5
PICS_IVIM_UPDATE A.3/2
PICS_IVIM_CANCELLATION A.3/3
PICS_IVIM_NEGATION A.3/4
PICS_SREM_GENERATION A.5/1
PICS_SREM_RECEPTION A.5/2
PICS_SSEM_GENERATION A.5/3
PICS_SSEM_RECEPTION A.5/4
PICS_IS_IUT_SECURED A.1/1
PICS_T_GENIVIMMIN A.4/1
PICS_T_GENIVIMMAX A.4/2
5.2 Requirements
5.2.1 Traffic Light Manoeuvre (TLM) service
5.2.1.1 Check the message protocol version
TP Id TP_IS_TLM_MSGF_BV_01
Summary
Check that protocolVersion is set to 1 and messageID is set to 4
Reference
ETSI TS 103 301 [2], clause 5.3
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
containing ITS PDU header
containing protocolVersion
indicating value '1'
and containing messageID
indicating value '4'
ETSI
12 ETSI TS 103 191-2 V1.2.1 (2017-03)
TP Id
TP_IS_TLM_MSGF_BV_02
Summary
Check that the IUT can successfully process all mandatory fields of SPATEM received
Reference ETSI TS 103 301 [2], clause 5.3
PICS Selection PICS_SPATEM_RECEPTION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT having receive a valid SPATEM
ensure that
when
the IUT receives a valid SPATEM
then
the IUT forwards the SPATEM content to upper layers
and the IUT forwards the SPATEM content to other facilities

5.2.1.2 TLM service trigger, update, repetition and termination
TP Id TP_IS_TLM_EVGN_BV_01
Check that TLM Service generates a new SPATEM on reception of a valid AppSPATEM
Summary
_Start request
Reference
ETSI TS 103 301 [2], clause 5.4.2
PICS Selection
PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT has not sent any SPATEM yet
ensure that
when
the IUT receives an AppSPATEM_Start request from the application layer
then
the IUT sends a valid SPATEM
TP Id
TP_IS_TLM_EVGN_BV_02
Summary
Check that TLM Service generates SPATEM are time ordered
Reference ETSI TS 103 301 [2], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT has sent a SPATEM
ensure that
when
several SPATEM are generated
then
the IUT sends SPATEM in time order

TP Id TP_IS_TLM_EVGN_BV_03
Summary Check that TLM Service terminates on reception of a valid AppSPATEM _Stop request
Reference ETSI TS 103 301 [2], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT sending SPATEM
ensure that
when
the IUT receives an AppSPATEM _Stop request from the application layer
then
the IUT stops sending SPATEM
ETSI
13 ETSI TS 103 191-2 V1.2.1 (2017-03)
TP Id
TP_IS_TLM_EVGN_BV_04
Check that TLM Service generates a new SPATEM on reception of a valid
Summary
AppSPATEM_Trigger request
Reference ETSI TS 103 301 [2], clause 5.4.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
ensure that
when
the IUT receives an AppSPATEM_Trigger request from the application layer
then
the IUT sends a valid SPATEM
5.2.1.3 Check presence of destination area
TP Id
TP_IS_TLM_COM_BV_01
Summary
Check that TLM Service provides the destination area in SPATEM
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
containing spat
containing regional
containing at least on region
indicating a regionId
and indication a regExtValue
5.2.1.4 Check BTP type and port number
TP Id TP_IS_TLM_COM_BV_02
Check that SPATEM uses BTP_B packet
Summary
Check that the destination port for SPATEM is set to 2004
Reference ETSI TS 103 301 [2], clauses 10.2 and 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
encapsulated in a BTP-B packet
containing a destination port value set to 2004
and containing a destination port info value set to 0

ETSI
14 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.2.1.5 Check destination type
TP Id TP_IS_TLM_COM_BV_03
Check that TLM service encapsulates SPATEM in a GBC with the HeaderType field set to
Summary
the value of 4
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION
Expected behaviour
with
the IUT being in the "initial state"
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
encapsulated in a GBC packet
containing a correctly formatted Common Header
containing HeaderType field
indicating the value '4'
5.2.1.6 TLM security parameters
5.2.1.6.1 Check TLM ITS AID value
TP Id TP_IS_TLM_SEC_SND_BV_01
Summary Check that TLM service uses certificate containing valid ITS AID to sign SPATEM messages
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
containing a correctly formatted Security Header
containing SignerInfo header
containing certificate
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
ETSI
15 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.2.1.6.2 Check TLM SSP version
TP Id TP_IS_TLM_SSP_SND_BV_01
Check that TLM service uses certificate containing valid Service Specific Permissions to
Summary
sign SPATEM messages and the SSP version is set to 1
Reference
ETSI TS 103 301 [2], clause 4.5.1
PICS Selection PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
ensure that
when
a SPATEM is generated
then
the IUT sends a valid SPATEM
containing a correctly formatted Security Header
containing SignerInfo header
containing certificate
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
indicating first octet = 01h
ETSI
16 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.2.1.6.3 Check TLM Service specific parameters
5.2.1.6.3.1 SSP IntersectionState
TP Id
TP_IS_TLM_SSP_SND_BV_02
Check that TLM service sends a SPAT message containing IntersectionState without
Summary advisory speed and manoeuvre assist information when it is permitted by the signing
certificate
Reference
ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection
PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
and the IUT uses the certificate to sign SPATEM messages
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 80h
ensure that
when
the IUT is triggered to send a SPATEM
not containing advisory speed
and not containing manoeuvre assisting information
and not containing public transport prioritization
then
the IUT sends a valid SPATEM
containing spat.intersections
containing any items of type IntersectionState
not containing manoeuvreAssistList
and not containing regional
and containing states
containing any item of type MovementEvent
not containing speeds
and not containing manoeuvreAssistList
and not containing regional
ETSI
17 ETSI TS 103 191-2 V1.2.1 (2017-03)
TP Id
TP_IS_TLM_SSP_SND_BV_03
Check that TLM service does not send a SPAT message containing IntersectionState if it is
Summary
not permitted by the certificate
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
and the IUT uses the certificate to sign SPATEM messages
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 78h
ensure that
when
the IUT is triggered to send a SPATEM
not containing advisory speed
and not containing manoeuvre assisting information
and not containing public transport prioritization
then
the IUT does not send a SPATEM
TP Id TP_IS_TLM_SSP_RCV_04
Check that the IUT discards the SPATEM message containing IntersectionState without
Summary
additional information not permitted by the signing certificate
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_RECEPTION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT is able to process received SPATEM
ensure that
when
the IUT receives SPATEM
containing spat.intersections
containing any items of type IntersectionState
not containing manoeuvreAssistList
and not containing regional
and containing states
containing any item of type MovementEvent
not containing speeds
and not containing manoeuvreAssistList
and not containing regional
embedded in GeoNetworking packet
containing SecurityHeader
containing SignerInfo header
containing certificate
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 78h
then
the IUT discards the SPATEM
ETSI
18 ETSI TS 103 191-2 V1.2.1 (2017-03)
TP Id
TP_IS_TLM_SSP_RCV_05
Check that the IUT accepts the SPATEM message containing IntersectionState without
Summary
additional information permitted by the signing certificate
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_RECEPTION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT is able to process received SPATEM
ensure that
when
the IUT receives SPATEM
containing spat.intersections
containing any items of type IntersectionState
not containing manoeuvreAssistList
and not containing regional
and containing states
containing any item of type MovementEvent
not containing speeds
and not containing manoeuvreAssistList
and not containing regional
embedded in GeoNetworking packet
containing SecurityHeader
containing SignerInfo header
containing certificate
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 80h
then
the IUT accepts the SPATEM
ETSI
19 ETSI TS 103 191-2 V1.2.1 (2017-03)
5.2.1.6.3.2 SSP IntersectionState.status
TP Id TP_IS_TLM_SSP_SND_BV_06
Check that TLM service sends a SPAT message containing IntersectionState without
Summary advisory speed and manoeuvre assist information when it is permitted by the signing
certificate
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
and the IUT uses the certificate to sign SPATEM messages
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 80h
ensure that
when
the IUT is triggered to send a SPATEM
not containing advisory speed
and not containing manoeuvre assisting information
and not containing public transport prioritization
then
the IUT sends a valid SPATEM
containing spat.intersections
containing any items of type IntersectionState
not containing manoeuvreAssistList
and not containing regional
and containing states
containing any item of type MovementEvent
not containing speeds
and not containing manoeuvreAssistList
and not containing regional
ETSI
20 ETSI TS 103 191-2 V1.2.1 (2017-03)
TP Id
TP_IS_TLM_SSP_SND_BV_07
Check that TLM service does not send a SPAT message containing IntersectionState if it is
Summary
not permitted by the certificate
Reference ETSI TS 103 301 [2], clause 5.4.3.2
PICS Selection PICS_SPATEM_GENERATION AND PICS_IS_IUT_SECURED
Expected behaviour
with
the IUT being in the "initial state"
and the IUT is operating in secured mode
and the IUT sending SPATEM
and the IUT uses the certificate to sign SPATEM messages
containing SecurityAttribute of type its_aid_ssp_list
containing ItsAidSsp item
containing its_aid
indicating 137
and containing service_specific_permissions
containing first octet
indicating 01h
and containing second octet
indicating 78h
ensure that
when
the IUT is triggered to send a SPATEM
not containing advisory speed
and not containing manoeuvre assisting information
and not containing public transport prioritization
then
the IUT does not send a SPATEM
TP Id TP_IS_TLM_SSP_RCV_BO_08
Check that the IUT discards the SPATEM message containing IntersectionState without
Summary
additional information not permitted by the signing
...