BS/EN 15876-2-2016 pdf download.Electronic fee collection Evaluation of on-board and roadside equipment for conformity to EN 15509 Part 2: Abstract test suite.
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 (ICS)
[ISO/IEC 9646-1:1994, 3.3.40]
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 19105:2000, 3.201
3.8
implementation extra information for testing proforma
document, in the form of a questionnaire, which when completed for an implementation under test (IUT) becomes an implementation extra information for testing (IXIT)
(SOURCE: lSO/IEC 9646-1:1994, 3.3.42, modifiedl
3.9
on-board equipment
all required equipment on-board a vehicle for performing required EFC functions and communication services
3.10
roadside equipment
equipment located along the road, either fixed or mobile
[SOURCE: EN ISO 14906:2011,3.171
3.11
tester
combination of equipment, humans and processes able to perform specified conformance tests
[EN 15876-1:2016, 3.12]
DLC Data Link Control
DSRC Dedicated Short-Range communication (ISO 14906)
DUT Device LinderTest (CEN ISO/TS 14907-2)
EID Element Identifier (ISO 14906)
EFC Electronic Fee Collection (ISO 17573)
EVENT-RT EVENT-REPORT (EN 12834)
ICS Implementation Conformance Statement (EN 15509)
IUT Implementation Under Test (ISO/TS 14907-1)
IXIT Implementation eXtra Information for Testing (CEN ISO/TS 14907-2)
LLC Logical Link Control (EN 12795)
MAC Medium Access Control (EN 12795)
OBE On-board equipment
OBU On-board unit
PDU Protocol Data Unit (ISO 14906)
RSE Road-side equipment
TC Test Case
TP Test Purpose
TSS Test Suite Structure (EN 15876-1)
VST Vehicle Service Table (ISO 14906)
5 Abstract Test Method (ATM)
5.1 General
This clause describes the abstract test method (ATM) used to test the layers at the OBE side and at the RSE side.
5.2 Test architecture
ETSI/TS 102 486-1-3:2009, Clause 4 and ETSI/TS 102 486-2-3:2009, Clause 4 describe the test architecture for their respective layers for testing. As test purposes (TPs) from ETSI/TS 102 486-1-3
7 Abstract test suite (ATS) conventions
7.1 General
The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS.
7.2 Naming conventions
7.2.1 Declarations part
7.2.1.1 General
This clause describes the naming conventions chosen for the elements of the ATS declarations part.
The following general rules apply for the names given in the declarations part.
Names of ASN.1 types imported from the base standard are preserved.
Predefined types (e.g. I3ITSTRING as defined in lSO/1EC9646-5) are never used in structured type definitions, application service point (ASP) type definitions or protocol type unit (PDtJ) type definitions. Simple types are used instead.
All declarations in the test suite are listed in alphabetical order. A different order of listing should be used for only maintenance reasons.
7.2.1.2 Test suite operations
The test suite operation identifiers are prefixed with TSO_”.
EXAMPLE TSQsubstring.
7.2.1.3 Test suite parameter declarations
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the test suite parameter identifiers are prefixed ‘TSPC_”.
EXAMPLE I TSPC_extended_rlcarriers.
If the test suite parameter references a PIXIT item, the suite parameter identifiers are prefixed “TSPX_’.
EXAMPLE 2 TSPXpmid.
If the test suite parameter represents a system parameter, the complete name defined in the protocol is used.
7.2.1.4 Test case selection expression definition
The test case selection expression identifiers begin with the prefix SEL_.
7.2.1.5 Test suite constant declarations
The test suite constant identifiers are prefixed MTSC_”.
If the test suite constant represents a system parameter, the complete name defined in the protocol is used.
7.2.1.6 Test suite variable declarations
The test Suite variable identifiers are prefixed HTSV_.
Complete names as defined in the protocol are used.
7.2.1.7 Test case variable declarations
The test case variable identifiers are prefixed °TCV_”.
Complete names as defined in the protocol are used.
7.2.1.8 Timer declarations
Timers begin with the prefix “T_.
7.2.1.9 ApplicatIon service point (ASP) type definition
The general conventions in 7.2.1.1 apply for application service point (ASP) type definitions. All capital
letters shall be used.
The identifier of an ASP type uses the same name as the name defined in the protocol.BS/EN 15876-2-2016 pdf download.