EN 15876:2023

SLOVENSKI STANDARD
01-julij-2023
Nadomešča:
SIST EN 15876-1:2017
Elektronsko pobiranje pristojbin - Vrednotenje skladnosti opreme v vozilu in v
obcestni napravi s standardom EN 15509
Electronic fee collection - Conformity evaluation of on-board and roadside equipment to
EN 15509
Elektronische Gebührenerhebung - Konformitätsprüfung von Fahrzeuggeräten und
straßenseitigen Einrichtungen nach EN 15509
Perception de télépéage - Evaluation de conformité de l'équipement embarqué et de
l'équipement au sol à la EN 15509
Ta slovenski standard je istoveten z: EN 15876:2023
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
43.040.15 Avtomobilska informatika. Car informatics. On board
Vgrajeni računalniški sistemi computer systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 15876
EUROPEAN STANDARD
NORME EUROPÉENNE
May 2023
EUROPÄISCHE NORM
ICS 35.240.60 Supersedes EN 15876-1:2016
English Version
Electronic fee collection - Conformity evaluation of on-
board and roadside equipment to EN 15509
Perception de télépéage - Evaluation de conformité de Elektronische Gebührenerhebung -
l'équipement embarqué et de l'équipement au sol à la Konformitätsprüfung von Fahrzeuggeräten und
EN 15509 straßenseitigen Einrichtungen nach EN 15509
This European Standard was approved by CEN on 17 April 2023.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 15876:2023 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Abbreviations . 8
5 Conformance . 9
6 Test suite structure . 9
6.1 Structure . 9
6.2 Reference to conformance specifications . 10
6.3 Test purposes . 10
Annex A (normative) Test purposes for on-board equipment . 13
Annex B (normative) Test purposes for roadside equipment . 71
Annex C (normative) PCTR proforma for on-board equipment . 103
Annex D (normative) PCTR proforma for roadside equipment . 114
Bibliography . 122

European foreword
This document (EN 15876:2023) has been prepared by Technical Committee CEN/TC 278, Intelligent
transport systems, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by November 2023 and conflicting national standards shall
be withdrawn at the latest by November 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 15876-1:2016.
This document has been prepared under a Standardization Request given to CEN by the European
Commission and the European Free Trade Association.
This third edition of EN 15876 incorporates the following main modifications compared with the
previous version:
 amendments to reflect changes to the underlying requirements standards, in particular the updated
data definitions in EN 15509;
 amendments to reflect changes in EN ISO 14907-2, specifically updated references following its
amended structure;
 updated terms to reflect the harmonized terms between electronic fee collection standards in
ISO/TS 17573-2;
 amendment of the document reference and title of EN 15876-1 to EN 15876, Electronic fee collection
– Conformity evaluation of on-board and roadside equipment to EN 15509, following the withdrawal of
EN 15876-2.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia,
Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland,
Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North
Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the United
Kingdom.
Introduction
CEN/TC 278 has produced a set of standards that support interoperable DSRC-EFC-systems e.g.
EN ISO 14906 (a "toolbox" for defining EFC-application transaction) and EN ISO 14907-2 (EFC
application interface conformance tests for on-board units). However, these standards are only of an
enabling nature and do not ensure technical interoperability. Therefore, EN 15509, Electronic fee
collection ― Interoperability application profile for DSRC was developed to support technical
interoperability between EFC-systems.
This document specifies the test suite structure and the test purposes for conformity evaluation of on-
board and roadside equipment designed for compliance with the requirements of EN 15509. A test
standard for evaluation of conformity of on-board and roadside equipment is a necessary element for
coherent, practical and effective appraisal of products' compliance to EN 15509.
EN 15876 provides the necessary foundation for verification of the implementation of the
interoperability requirements as stated in EN 15509:
— industry is provided with an easy-to-use toolbox for product assessment;
— operators can easily assess conformity to EN 15509 and reference to the standard in tendering
processes;
— authorities and joint undertakings may reference to the test standard when stating interoperability
requirements;
— certification organizations are given an effective tool for certification of products.

1 Scope
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluation of on-board
equipment (OBE) and roadside equipment (RSE) to EN 15509.
Normative Annex A presents the test purposes for the OBE.
Normative Annex B presents the test purposes for the RSE.
Normative Annex C provides the protocol conformance test report (PCTR) proforma for OBE.
Normative Annex D provides the PCTR proforma for RSE.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 15509:2023, Electronic fee collection — Interoperability application profile for DSRC
EN ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code (ISO 3166-1)
EN ISO 14816, Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure (ISO 14816)
EN ISO 14906:2023, Electronic fee collection — Application interface definition for dedicated short-range
communication (ISO 14906:2022)
EN ISO 14907-2:2021, Electronic fee collection — Test procedures for user and fixed equipment — Part 2:
Conformance test for the on-board unit application interface (ISO 14907-2:2021)
ETSI EN 300 674-1:2004, Electromagnetic compatibility and Radio spectrum Matters (ERM); Road
Transport and Traffic Telematics; Dedicated Short Range Communication (DSRC) transmission equipment
(500 kbit/s / 250 kbit/s) operating in the 5,8 GHz Industrial, Scientific and Medical (ISM) band; Part 1:
General characteristics and test methods for Road Side Units (RSU) and On-Board Units (OBU)
ETSI/TS 102 486-1-2:2008, 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 2: Test Suite Structure and
Test Purposes (TSS&TP)
ETSI/TS 102 486-2-2:2008, 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)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1
attribute
addressable package of data consisting of a single data element or structured sequences of data elements
[SOURCE: ISO/TS 17573-2:2020, 3.13]
3.2
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: ISO/TS 17573-2:2020, 3.16]
3.3
data group
class of closely related attributes
[SOURCE: ISO/TS 17573-2:2020, 3.55]
3.4
Element
EFC Element
coherent set of data and functionality
Note 1 to entry: The functionality includes, where applicable, the security-related functions and the associated
security keys.
Note 2 to entry: EFC Elements are created by the applications and addressed using Element identifiers.
Note 3 to entry: In a given on-board equipment (OBE) (3.9), the EID is used to address a toll context, identified by
the EFC-ContextMark, in which attributes (3.1) can be addressed unambiguously by AttributeIDs inside an EFC
Element of the OBE.
[SOURCE: ISO/TS 17573-2:2020, 3.71]
3.5
implementation conformance statement
statement of capabilities and options that have been implemented that defines to what extent the
implementation is compliant with a given specification
[SOURCE: ISO/TS 17573-2:2020, 3.90]
3.6
implementation conformance statement proforma
document, in the form of a questionnaire, which when completed for an implementation or system
becomes an implementation conformance statement (3.5)
[SOURCE: ISO/TS 17573-2:2020, 3.91]
3.7
implementation extra information for testing
statement containing all of the information related to the implementation under test (IUT) and its
corresponding system under test (SUT) which will enable the testing laboratory to run an appropriate
test suite against that IUT
[SOURCE: ISO/TS 17573-2:2020, 3.92]
3.8
implementation extra information for testing proforma
document, in the form of a questionnaire, which when completed for an IUT becomes an implementation
extra information for testing (3.7)
[SOURCE: ISO/TS 17573-2:2020, 3.93]
3.9
on-board equipment
all required equipment on-board a vehicle for performing required electronic fee collection functions and
communication services
[SOURCE: ISO/TS 17573-2:2020, 3.126]
3.10
on-board unit
electronic unit on-board a vehicle for performing specific electronic fee collection functions and for
communication with external systems
Note 1 to entry: OBE and OBU have been used as terms with the same or similar meaning in the standardization
of DSRC and DSRC-based EFC within CEN and ETSI. Previously developed relevant standards used the term OBU
with the meaning OBE as defined in this document. When referring to relevant tests in other documents, this
document uses the terms of the referenced source, which explains why the term OBU is often used in the Annexes.
[SOURCE: ISO/TS 17573-2:2020, 3.127]
3.11
roadside equipment
fixed or movable electronic fee collection equipment located along the road
Note 1 to entry: RSE and RSU have been used as terms with the same or similar meaning in the standardization
of DSRC and DSRC-based EFC within CEN and ETSI. Previously developed relevant standards used the term RSU
with the meaning RSE as defined in this document. When referring to relevant tests in other documents, this
document uses the terms of the referenced source, which explains why the term RSU is often used in the Annexes.
[SOURCE: ISO/TS 17573-2:2020, 3.161]
3.12
tester
combination of equipment, humans and processes able to perform specified conformance tests
[SOURCE: ISO/TS 17573-2:2020, 3.188]
3.13
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO/TS 17573-2:2020, 3.211]
4 Abbreviations
For the purposes of this document, the following abbreviations apply throughout the document unless
otherwise specified.
APDU application protocol data unit
AP application process
ASN.1 abstract syntax notation one (ISO/IEC 8824-1)
ATS abstract test suite
BI behaviour invalid (i.e. invalid behaviour tests)
BST beacon service table
BV behaviour valid (i.e. valid behaviour tests)
DSRC dedicated short-range communication
EFC electronic fee collection
ICS implementation conformance statement
IUT implementation under test
LLC logical link control
LPDU LLC protocol data unit
MAC medium access control
OBE on-board equipment
OBU on-board unit
PCTR protocol conformance test report
PDU protocol data unit
PICS protocol implementation conformance statement
PIXIT protocol implementation extra information for testing
RSE roadside equipment
RSU roadside unit
SCTR system conformance test report
TP test purposes
TSS test suite structure
VST vehicle service table
5 Conformance
The supplier of the OBE and RSE, respectively, is responsible for providing a conformance test report.
The supplier of the OBE shall complete the protocol conformance test report (PCTR) for the OBE as
specified in Annex C.
The supplier of the RSE shall complete the PCTR for the RSE as specified in Annex D.
6 Test suite structure
6.1 Structure
Table 1 below shows the test suite structure (TSS) including its subgroups specified for the conformance
testing.
Table 1 — Test Suite Structure
Group Type of IUT Behaviour
Physical layer OBE Valid behaviour
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
DLC MAC sublayer OBE Valid behaviour
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
DLC LLC sublayer OBE Valid behaviour
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Application layer – Functions OBE Valid behaviour
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Application Layer – Data OBE Valid behaviour
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Application Layer – Security OBE Valid behaviour
Level 0
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Application Layer – Security OBE Valid behaviour
Level 1
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Application Layer – OBE Valid behaviour
Transactions
Invalid behaviour
RSE Valid behaviour
Invalid behaviour
Physical layer tests are to be performed in a radio wave laboratory. They will not form part of the abstract
test suite (ATS).
6.2 Reference to conformance specifications
Conformance to a profile standard implies conformance to the related base standards. Hence, a number
of test cases for the profile standard are exactly the same as the conformance test cases for the related
base standards. Other test cases are derived from the base standards conformance test cases, by applying
some restrictions or choices in e.g. the parameters values, according to what is stated in the profile
standard. Finally, specific conformance test cases for the profile standard are identified for statements
contained in the profile standard, which have no equivalence in the base standards. These latter cases
cover for example the security algorithms and functions that are described in the profile standard. This
document takes into account already specified test purposes for conformance to the base standards by
referencing them, so that:
a) For test purposes that are identical to those specified in the base standards conformance test cases
(see e.g. ETSI/TS 102 486-1-2 or ETSI/TS 102 486-2-2) a direct reference is reported. For reader's
convenience, the title or a verbal description of the referenced test purpose is given, together with
the reference.
b) For test purposes that are derived from those specified in the base standards conformance test cases,
a direct reference is reported, plus an indication on how the referred test purpose has to be modified
for the profile conformance testing.
c) For test purposes that are specific to the standard profile, a complete description is given.
An indication on whether a test purpose is identical, derived, or specific is given in each test purpose.
6.3 Test purposes
6.3.1 TP Definition conventions
The TPs are specified following the rules shown in Table 2 below.
Table 2 — TP definition rules
TP ID according to the TP Title
naming conventions
Reference
TP origin
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 specified 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).
TP origin Indicates if the TP is identical to a TP specified in another test standard,
derived from a TP specified in another test standard, or specific for this profile
standard.
Initial condition The condition specifies in which initial state the IUT has to be to apply the
actual TP.
Stimulus and Definition of the events the tester performs, and the events that are expected
expected behaviour from the IUT to conform to the base specification.
Note that the reference field normally points to the clause of the base standard EN 15509. As the same
standard contains the Protocol Implementation Conformance Statement proforma, where appropriate a
reference to the relevant table of the PICS is given either in this field or in the text introducing the group
of Test Purposes.
6.3.2 TP Naming conventions
Each TP is given a unique identification. This unique identification is built up to contain the following
string of information:
TP///-
TP : to indicate that it is a Test Purpose;
: which group among those specified in Table 1 — Test Suite Structure does the TP
apply to;
: type of IUT (i.e. OBE or RSE);
X : type of testing (i.e. Valid Behaviour tests – BV, or Invalid Behaviour tests – BI);
: sequential TP number (01-99).
The naming conventions are as described in Table 3 — TP Naming Conventions below.
Table 3 — TP Naming conventions
Identifier: TP/// >-
PHY Physical layer
MAC MAC sublayer
LLC LLC sublayer
AP-0BAS Application layer – I Kernel support Security level 0
AP-0FUN Application layer – T Kernel support Security level 0
AP-0DAT Application layer – Data attributes support Security Level 0
AP-0SEC Application layer – Security Level 0 support
AP-0TRA Application layer – Transaction support Security level 0
AP-1BAS Application layer – I Kernel support Security level 1
AP-1FUN Application layer – T Kernel support Security level 1
AP-1DAT Application layer – Data attributes support Security Level 1
AP-1SEC Application layer – Security Level 1 support
AP-1TRA Application layer – Transaction support Security level 1
AP-0BAS Application layer – Initialisation phase support Security level 0
AP-0GET Application layer - GET-rq PDU test purposes, security level 0
AP-0SET Application layer - SET-rq PDU test purposes, security level 0
AP-0STA Application layer - GET-STAMPED-rq PDU test purposes, security
level 0
AP-0MMI Application layer - SET-MMI-rq PDU test purposes security level 0
AP-0ECH Application layer - ECHO-rq PDU test purposes, security level 0
AP-0REL Application layer - EVENT-REPORT-rq PDU test purposes,
security level 0
AP-1BAS Application layer - initialization phase test purposes, security
level 1
AP-1GET Application layer - GET-rq PDU test purposes, security level 1
AP-1SET Application layer - SET-rq PDU test purposes, security level 1
AP-1STA Application layer - GET-STAMPED-rq PDU test purposes, security
level 1
AP-1MMI Application layer - SET-MMI-rq PDU test purposes security level 1
AP-1ECH Application layer - ECHO-rq PDU test purposes, security level 1
= type of IUT OBE On-board equipment
RSE Roadside equipment
x  = Type of testing BV Valid Behaviour Tests
BI Invalid Behaviour Tests
= sequential (01-99) Test Purpose Number
number
Annex A
(normative)
Test purposes for on-board equipment
A.1 Introduction
This annex contains the test purposes (TP) for the conformity evaluation of on-board equipment (OBE)
to EN 15509:2023.
OBE and OBU have been used as terms with the same or similar meaning in the standardization of DSRC
and DSRC-based EFC within CEN and ETSI. Previously developed relevant standards used the term OBU
with the meaning OBE as defined in this document. When referring to relevant tests in other documents,
this document uses the terms of the referenced source, which explains why the term OBU is often used in
this Annex
A.2 Physical layer
A.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.
TP/PHY/OBU/BV/01 Dynamic range – sensitivity
TP Origin Identical to ETSI EN 300 674-1:2004, 10.1.1
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.1.1

TP/PHY/OBU/BV/02 Dynamic range – upper power limit for communication
TP Origin Identical to ETSI EN 300 674-1:2004, 10.1.2
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.1.2

TP/PHY/OBU/BV/03 Cut-off power level
TP Origin Identical to ETSI EN 300 674-1:2004, 10.2
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.2

TP/PHY/OBU/BV/04 Conversion gain
TP Origin Identical to ETSI EN 300 674-1:2004, 10.3
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.3

TP/PHY/OBU/BV/05 Maximum equivalent isotropically radiated power
TP Origin Identical to ETSI EN 300 674-1:2004, 10.4
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.4

TP/PHY/OBU/BV/06 Frequency error
TP Origin Identical to ETSI EN 300 674-1:2004, 10.5
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.5

TP/PHY/OBU/BV/07 Transmitter spectrum mask
TP Origin Identical to ETSI EN 300 674-1:2004, 10.6
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.6

TP/PHY/OBU/BV/08 Transmitter unwanted emissions
TP Origin Identical to ETSI EN 300 674-1:2004, 10.7
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.7

TP/PHY/OBU/BV/09 Receiver spurious emissions
TP Origin Identical to ETSI EN 300 674-1:2004, 10.8
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI EN 300 674-1:2004, Clause 8.
Stimulus and Expected Behaviour
See ETSI EN 300 674-1:2004, 10.8
A.2.2 BI test purposes
BI test purposes group do not apply for Layer 1.
A.3 MAC
A.3.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.
TP/MAC/OBU/BV/01 Receive downlink frames – maximum length
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/01
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/01
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/01

TP/MAC/OBU/BV/02 Receive downlink frames within T1
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/02
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/02
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/02

TP/MAC/OBU/BV/03 Timing constraints for public uplink windows
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/03
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/03
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/03

TP/MAC/OBU/BV/04 Receive downlink frames within T2
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/04
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/04
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/04

TP/MAC/OBU/BV/05 Timing constraints for private uplink windows
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/05
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/05
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/05

TP/MAC/OBU/BV/06 S-bit and L-bit in MAC control field
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/06
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/06
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/06

TP/MAC/OBU/BV/07 Manage S-bit state variable
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/07
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/07
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/07

TP/MAC/OBU/BV/08 Random selection of N5 public uplink windows
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/08
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/08
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BV/08
A.3.2 BI test purposes
Test subgroup objective:
— to check the behaviour of the IUT in response to invalid stimuli and behaviour from the test tool.
TP/MAC/OBU/BI/01 Manage double-bit errors in the LID, MAC control and LPDU fields
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/01
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/01
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/01

TP/MAC/OBU/BI/02 Detect and manage double-bit errors in the FCS field
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/02
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/02
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/02

TP/MAC/OBU/BI/03 Detect and manage a block of 15 bits errors
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/03
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/03
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/03

TP/MAC/OBU/BI/04 Detect and manage the abort sequence in the LPDU field
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/04
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/04
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/04

TP/MAC/OBU/BI/05 Detect and manage the abort sequence at the end of a downlink frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/05
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/05
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/05

TP/MAC/OBU/BI/06 Detect and manage a too long downlink frame according to N2
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/06
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/06
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/06

TP/MAC/OBU/BI/07 Detect and manage wrong format of LID
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/07
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/07
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/07

TP/MAC/OBU/BI/08 Detect and manage missing MAC control field
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/08
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/08
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/08

TP/MAC/OBU/BI/09 Detect and manage wrong A-bit in MAC control field in broadcast frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/09
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/09
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/09

TP/MAC/OBU/BI/10 Detect and manage wrong D-bit in MAC control field in broadcast frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/10
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/10
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/10

TP/MAC/OBU/BI/11 Detect and manage wrong D-bit in MAC control field in private frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/11
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/11
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/11

TP/MAC/OBU/BI/12 Detect and manage wrong L-bit in MAC control field in broadcast frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/12
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/12
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/12

TP/MAC/OBU/BI/13 Detect and manage wrong L-bit in MAC control field in private frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/13
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/13
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/13

TP/MAC/OBU/BI/14 Detect and manage wrong C/R–bit in MAC control field of a PrWa frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/14
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/14
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/14

TP/MAC/OBU/BI/15 Detect and manage a wrong MAC control field
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/15
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/15
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/15

TP/MAC/OBU/BI/16 Detect and manage blocked signals
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/16
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/16
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/16

TP/MAC/OBU/BI/17 Detect and manage blocked end flag
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/17
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/17
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/17

TP/MAC/OBU/BI/18 Detect and manage blocked start flag
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/18
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/18
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/18

TP/MAC/OBU/BI/19 Detect and manage broadcast LID where expecting private LID
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/19
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/19
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/19

TP/MAC/OBU/BI/20 Detect and manage multicast LID where expecting private LID
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/20
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/20
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/20

TP/MAC/OBU/BI/21 Detect and manage wrong A-bit in MAC control field in private frame
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/21
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/21
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/21

Manage wrong A-bit in MAC control field in private downlink frame with
TP/MAC/OBU/BI/22
ACn
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/22
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/22
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/22

TP/MAC/OBU/BI/23 Detect and manage wrong private LID
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/23
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/23
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/23

TP/MAC/OBU/BI/24 Verify that the OBU can manage retransmission of PrWRq
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/24
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/24
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/MAC/OBU/BI/24
A.4 LLC
A.4.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.
TP/LLC/OBU/BV/01 Exchange UI commands
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/01
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/01
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/01

TP/LLC/OBU/BV/02 Manage ACn data transmission
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/02
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/02
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/02

TP/LLC/OBU/BV/03 Manage ACn data exchange
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/03
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/03
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/03

Empty Test Purpose, left to keep numbering aligned with ETSI/TS 102 486-
TP/LLC/OBU/BV/04
1-2:2008
TP Origin
Reference
Initial condition
Stimulus and Expected Behaviour

TP/LLC/OBU/BV/05 Manage data response Procedure I
TP Origin Identical to ETSI/TS 102 486-1-2 TP/LLC/OBU/BV/05
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/05
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BV/05
A.4.2 BI test purposes
Test subgroup objective:
— to check the behaviour of the IUT in response to invalid stimuli and behaviour from the test tool.
Detect and manage corrupted LLC control field when expecting UI
TP/LLC/OBU/BI/01
command
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/01
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/01
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/01

TP/LLC/OBU/BI/02 Detect and manage invalid LPDU with fractional number of octets in length
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/02
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/02
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/02

Detect and manage corrupted LLC control field when expecting ACn
TP/LLC/OBU/BI/03
command
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/03
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/03
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/03

Detect and manage LPDU containing acknowledged connectionless LLC
TP/LLC/OBU/BI/04
command control field when LID is multicast or broadcast
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/04
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/04
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/04
TP/LLC/OBU/BI/05 Detect and manage invalid LPDU with fractional number of octets in length
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/05
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/05
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/05

TP/LLC/OBU/BI/06 Detect and manage an invalid ACn command with P=1 and no LSDU.
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/06
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/06
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/06

TP/LLC/OBU/BI/07 Detect and manage duplicate ACn commands
TP Origin Identical to ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/07
Reference EN 15509:2023, 6.1.2
Initial condition See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/07
Stimulus and Expected Behaviour
See ETSI/TS 102 486-1-2:2008 TP/LLC/OBU/BI/07
A.5 Application layer
A.5.1 Introduction and general conventions
For the application layer test purposes, a special notation and symbol convention is used, as specified
below.
Symbols are used in the description of the TPs, with meanings according to Table A.1.
Table A.1 — Description of TP Symbols
SYMBOL DESCRIPTION
XXX.rq ⇒ The Tester sends the XXX.rq PDU to the IUT
⇐ YYY.rs The IUT sends the YYY.rs PDU to the Tester
A ≡ B Test Purpose A "is congruent to" Test Purpose B. The notation Test Purpose
A ≡ Test Purpose B means that the Test Purpose A is the same as Test
Purpose B. If differences in parameters or parameter values have to be
applied, these differences are indicated in the text immediately below.
A → B Object A "is transformed" into Object B. So a notation like "Table X → Table
Y" means that, for the scope of the Test Purpose, any ref
...