SIST-TS CEN/TS 17154-2:2019

SLOVENSKI STANDARD
SIST-TS CEN/TS 17154-2:2019
01-julij-2019
Elektronsko pobiranje pristojbin - Ugotavljanje skladnosti za izvajanje tehnične
specifikacije CEN/TS 16986 - 2. del: Abstraktni preskuševalni niz
Electronic fee collection - Evaluation of implementation for conformity to CEN/TS 16986 -
Part 2: Abstract test suite
Elektronische Gebührenerhebung - Konformitätsevaluierung von Implementierungen
nach CEN/TS 16986 - Teil 2: Zusammengefasstes Prüfprogramm
Perception du télépéage - Évaluation de la conformité de la mise en œuvre de la
CEN/TS 16986 - Perception du télépéage - Évaluation de la conformité de la mise en
œuvre de la CEN TS 16986 - Partie 2 : Suite d'essais abstraite
Ta slovenski standard je istoveten z: CEN/TS 17154-2:2019
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TS CEN/TS 17154-2:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 17154-2:2019

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 17154-2:2019


CEN/TS 17154-2
TECHNICAL SPECIFICATION

SPÉCIFICATION TECHNIQUE

May 2019
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version

Electronic fee collection - Evaluation of implementation for
conformity to CEN/TS 16986 - Part 2: Abstract test suite
Perception du télépéage - Évaluation de la conformité Elektronische Gebührenerhebung -
de la mise en œuvre de la CEN/TS 16986 - Perception Konformitätsevaluierung von Implementierungen nach
du télépéage - Évaluation de la conformité de la mise CEN/TS 16986 - Teil 2: Zusammengefasstes
en œuvre de la CEN TS 16986 - Partie 2 : Suite d'essais Prüfprogramm
abstraite
This Technical Specification (CEN/TS) was approved by CEN on 8 March 2019 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey 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
© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17154-2:2019 E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Symbols and abbreviations . 9
5 Abstract Test Method (ATM) . 10
5.1 Introduction . 10
5.2 Test architecture . 10
5.3 Protocol Implementation Extra Information for Testing (PIXIT) . 10
6 Untestable Test Purposes (TP) . 10
7 Triggering the IUT . 11
8 Security functions . 16
9 ATS data structures . 17
9.1 ASN.1 definitions . 17
9.2 Parameterized support . 17
9.3 TTCN-3 modules . 19
10 Message filtering . 20
11 Module parameter data . 20
11.1 Introduction . 20
11.2 Tester data. 21
11.3 ICS-parameters . 21
11.4 Interoperability statement parameters . 21
11.5 Pixit data . 22
12 Test case timing . 22
13 ATS naming conventions . 22
13.1 Introduction . 22
13.2 TTCN-3 identifiers . 22
13.3 Test case identifiers . 23
Annex A (normative) Abstract Test Suite (ATS) for the central equipment of the toll chargers
and toll service providers . 24
A.1 Introduction . 24
A.2 TTCN Graphical form (TTCN.GR) . 24
A.3 TTCN Machine Processable form (TTCN.MP) . 24
Annex B (informative) PIXIT proforma for toll charger and toll service provider . 25
B.1 Introduction . 25
B.2 Identification summary . 25
B.3 ATS summary . 25
B.4 Test laboratory . 25
B.5 Client identification . 26
2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
B.6 IUT identification . 26
B.7 Protocol layer information . 26
B.7.1 Protocol identification . 26
B.7.2 IUT information . 27
B.7.3 Trust object support . 27
Bibliography . 28

3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
European foreword
This document (CEN/TS 17154-2:2019) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
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.
CEN/TS 17154, Electronic fee collection — Evaluation of implementation for conformity to
CEN/TS 16986, consists of two parts:
— Part 1: Test suite structure and purposes; and
— Part 2: Abstract test suite (this document).
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
Introduction
The Standard on information exchange between service provision and toll charging (i.e. EN ISO 12855)
is a so-called toolbox standard. It provides the foundation for interoperability but is not sufficient to
achieve full technical interoperability. The interoperable application profile specified in CEN/TS 16986
makes useful choices amongst the options which EN ISO 12855 provides and defines a coherent set of
transactions, triggers and data elements for an interoperable data exchange at the interface between
the central system equipment of toll service providers and toll chargers. The interoperable application
profile supports in both:
— dedicated short-range communication (DSRC)-based systems; and
— global navigation satellite systems /cellular network (GNSS/CN)- based – autonomous systems.
This document provides the specification for testing the conformity of technical implementations to
CEN/TS 16986. Technical implementations which can be tested using the specifications included in this
Standard are:
— central equipment of toll chargers; and
— central equipment of toll service providers.
While CEN/TS 17154-1 describes the tests on a higher abstract level which is human readable, this
Part 2 uses the test notation TTCN-3 to provide a test specification that can be used and executed in
state-of-the-art test environments.
The associated requirements specifications CEN/TS 16986 support the implementation of
interoperability in general and European electronic toll service (EETS) in particular. The technical
requirements defined in CEN/TS 16986 correspond to requirements listed in
Commission Decision 2009/750/EC. CEN/TS 16986:2016, Table D.1 provides a list that outlines how
requirements in CEN/TS 16986:2016 relate to essential requirements in European legislation.
Consequently, the CEN/TS 17154 series supports EETS in terms of providing a set of standardized test
specifications to evaluate conformance of implementation of toll chargers and toll service providers –
including implementations that provide interoperability and the EETS.
5

---------------------- Page: 7 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
1 Scope
This document provides a suite of tests in order to assess the central equipment of toll chargers and toll
service providers for compliancy towards the requirements listed in CEN/TS 16986. This document
contains the definition of such tests in the form of test cases, reflecting the required individual steps
listed in specific Test Purposes defined in CEN/TS 17154-1. The test cases are written in Testing and
Test Control Notation version 3 (TTCN v3).
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.
CEN/TS 16986:2016, Electronic Fee Collection — Interoperable application profiles for information
exchange between Service Provision and Toll Charging
ETSI ES 201 873-1 (V3.4.1:2008-09), Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 1: TTCN-3 Core Language
ETSI ES 201 873-4 (V4.6.1:2017-05), Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 4: TTCN-3 Operational Semantics
ETSI ES 201 873-7 (V4.7.1:2018-05), Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3, Part 7: Using ASN.1 with TTCN-3
ETSI ES 202 784 (V1.6.1:2017-04), Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; TTCN-3 Language Extensions: Advanced Parameterization
EN ISO 12855:2015, Electronic fee collection — Information exchange between service provision and toll
charging (ISO 12855:2015)
EN ISO 17575-1:2016, Electronic fee collection — Application interface definition for autonomous
systems — Part 1: Charging (ISO 17575-1:2016)
EN ISO 17575-2, Electronic fee collection — Application interface definition for autonomous systems —
Part 2: Communication and connection to the lower layers (ISO 17575-2)
EN ISO 17575-3, Electronic fee collection — Application interface definition for autonomous systems —
Part 3: Context data (ISO 17575-3)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
6

---------------------- Page: 8 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
3.1
base standard
approved international standard, technical specification or ITU-T Recommendation
Note 1 to entry: This includes but is not limited to approved standard deliverables from ISO, ITU, CEN, CENELEC,
ETSI and IEEE.
[SOURCE: ISO/IEC TR 10000-1:1998, 3.1.1, modified — The bit "technical specification" and Note 1 to
entry were added.]
3.2
basic trigger
trigger that stimulate a transaction as defined in CEN/TS 16986:2016, 3.37
3.3
conformance testing
assessment to determine whether an implementation complies with the requirements
3.4
data element
coded information, which might itself consist of lower level information structures
[SOURCE: EN ISO 17575-1:2016, 3.9]
3.5
electronic fee collection
fee collection by electronic means
[SOURCE: EN ISO 12855:2015, 3.6]
3.6
evaluation
systematic process of determining how individuals, procedures, systems or programs have met
formally agreed objectives and requirements
[SOURCE: ISO 10795:2011, 1.90]
3.7
implementation conformance statement
statement of capabilities and options that have been implemented defining to what extent the
implementation is compliant with a given specification
[SOURCE: CEN ISO/TS 14907-2:2016, 3.6]
3.8
implementation under test
implementation of one or more open systems interconnection (OSI) protocols in an adjacent
user/provider relationship, being part of a real system, which is to be studied by testing
7

---------------------- Page: 9 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
3.9
interoperability
ability of systems to exchange information and to make mutual use of the information that has been
exchanged
[SOURCE: ISO/IEC TR 10000-1:1998, 3.2.1, modified — The beginning of the definition was slightly
altered.]
3.10
profile
set of requirements and selected options from base standards or international standardized profiles
used to provide a specific functionality
[SOURCE: ISO/IEC TR 10000-1:1998, 3.1.4, modified — The whole wording of the definition was
modified and shortened and the original Note 1 to entry was left out.]
3.11
role
set of responsibilities
[SOURCE: ISO 17573:2010, 3.13]
3.12
support trigger
basic trigger with additional restrictions
3.13
test
procedure designed to measure characteristics of a component or system in specified conditions
[SOURCE: CEN ISO/TS 14907-1:2015, 3.20]
3.14
test case
description of test purpose, unique test case identifier, test inputs, test execution conditions, test steps,
and the results required to pass the test
[SOURCE: ISO/IEC 18013-4:2011, 4.1]
3.15
toll
charge, tax or duty levied in connection to using a vehicle in a toll domain
[SOURCE: CEN ISO/TS 19299:2015, 3.42, modified — "Any" was deleted at the start of the definition
and "in relation with" was replaced with "in connection to".]
3.16
toll charger
entity which levies toll for the use of vehicles in a toll domain
[SOURCE: ISO 17573:2010, 3.16, modified — The wording of the definition was altered and the original
Note 1 to entry was left out.]
8

---------------------- Page: 10 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
3.17
toll domain
area or a part of a road network where a certain toll regime is applied
[SOURCE: ISO 17573:2010, 3.18, modified — "Certain" was added.]
3.18
toll service provider
entity providing toll services in one or more toll domains
[SOURCE: ISO 17573:2010, 3.23, modified — The definition was shortened and the original Notes were
left out.]
3.19
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: EN ISO 17575-1:2016, 3.21]
4 Symbols and abbreviations
For the purposes of this document, the following abbreviated terms apply.
ADU Application Data Unit (EN ISO 14906)
APDU Application Protocol Data Unit (EN ISO 14906)
ASN.1 Abstract Syntax Notation One
ATM Abstract Test Method
BI Behaviour Invalid (EN 15876-1)
BV Behaviour Valid (EN 15876-1)
DSRC Dedicated Short Range Communication
EETS European Electronic Toll Service
EFC Electronic Fee Collection (ISO 17573)
GNSS Global Navigation Satellite Systems
ICS Implementation Conformance Statement (ISO/IEC 9646-7)
IUT Implementation Under Test (CEN ISO/TS 14907-1)
PIXIT Protocol Implementation Extra Information for Testing
TC Toll Charger
TP Test Purpose
TSP Toll Service Provider
TTCN-3 Testing and Test Control Notation version 3 (ETSI ES 201 873-1)
9

---------------------- Page: 11 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
5 Abstract Test Method (ATM)
5.1 Introduction
This clause describes the ATM used to test the exchange of information between the central equipment
associated with the two roles service provision and toll charging.
5.2 Test architecture
The implementation under test is either the central equipment of the toll charger or the toll service
provider.
The tester shall execute the test cases of the present test specification as specified in Annex A, running
on an emulated communication sub-layer. The test cases are written in TTCN-3 which is defined in
ETSI ES 201 873-1, TTCN-3 Core Language (CL), ETSI ES 201 873-4, TTCN-3 Semantics, and
ETSI ES 201 873-7, TTCN-3: Using ASN.1 with TTCN-3. Furthermore, to mirror the parametrization
capabilities used in the ASN.1 definitions of CEN/TS 16986, ETSI ES 202 784, TTCN-3: Extensions:
Advanced Parameterization is utilized.
Figure 1 describes the test system architecture.

Figure 1 — Test system architecture
5.3 Protocol Implementation Extra Information for Testing (PIXIT)
The supplier of the central equipment, i.e. the toll charger or toll service provider, is responsible for
providing the Protocol Implementation Extra Information for Testing (PIXIT).
The supplier of the central equipment shall complete a PIXIT; see Annex B for a proforma.
6 Untestable Test Purposes (TP)
No untestable TP has been identified.
10

---------------------- Page: 12 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
7 Triggering the IUT
When transactions need to be initiated by the IUT, the tester stimulates the IUT by sending an
indication of the transaction to be initiated. This indication is delivered through the mtcAccess service
port, which is defined in TTCN-3 as follows:
  type port MtcAccessPort message {
    out Iso16986Trigger;
    in Iso16986TriggerRsp;
  }
The mtcAccess port accepts as input the identifier of one trigger. The TTCN-3 definition of the
CEN/TS 16986:2016 defined triggers (basic triggers) is represented by an enumeration construct
named Iso16986Trigger in the TTCN module EfcInfoExchange_LibUpperTester.
The simple exchange protocol defined for port mtcAccess features a response to a trigger that notifies
the tester about the result of the operation at IUT side. The TTCN-3 definition of the response is as
follows:
type record Iso16986TriggerRsp {
 enumerated {TRIGGERED, NOT_TRIGGERED} responseCode,
 charstring reason optional
}

In some situations, the simple stimulus to initiate a transaction is not sufficient to execute a test case, as,
e.g. optional parameters are needed to be specified for the ADU(s) to be sent by the IUT. For those
situations, additional triggers (support triggers) have been defined. The complete list of all basic and
support triggers is specified in Table 1 Basic triggers are marked in boldface.
11

---------------------- Page: 13 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
Table 1 — Definition of IUT triggers
Trigger name Definition / Reference APDU for IUT to send when
triggered
USERDETAILS_TR_TC_1 See CEN/TS 16986:2016, 6.4.1 Initiating_APDU containing one or
more valid RequestADUs of type
userDetailsRequest
LISTOFUSERS_TR_TC_1 See CEN/TS 16986:2016, 6.5.1 Generic trigger not used in the test
cases
See more specific triggers
LISTOFUSERS_TR_TC_1_ONEOR See CEN TS17154– Initiating_APDU containing one or
MOREADUS 1 TP_TC_LISTOFUSERS_BV_01 more valid RequestADUs of type
userListRequest with
userIdRequestType = 0,
userId = at least one of {pan,
licensePlateNumber, obeId,
contractSerialNumber} and
userIdRequestTime present
LISTOFUSERS_TR_TC_1_ONEADU See CEN TS17154– Initiating_APDU containing exactly
1 TP_TC_LISTOFUSERS_BI_01 one(1) valid RequestADUs of type
userListRequest with
userIdRequestType = 0,
userId = at least one of {pan,
licensePlateNumber, obeId,
contractSerialNumber} and
userIdRequestTime present
LISTOFUSERS_TR_TC_1_THREEA See CEN TS17154– Initiating_APDU containing exactly
DUS 1 TP_TC_LISTOFUSERS_BI_02 three(3) valid RequestADUs of
type userListRequest with
userIdRequestType = 0,
userId = at least one of {pan,
licensePlateNumber, obeId,
contractSerialNumber} and
userIdRequestTime present
EXCEPTIONLIST_TR_TSP_1 See CEN/TS 16986:2016, 6.6.1 Generic trigger not used in the test
cases
See more specific triggers
EXCEPTIONLIST_TR_TSP_1_BLAC See CEN TS17154– Initiating_Apdu containing exactly
K 1 TP_TSP_EXCEPTIONLIST_BV one ExceptionListADU indicating
_01 listType = Black
EXCEPTIONLIST_TR_TSP_1_WHI See CEN TS17154– Initiating_Apdu containing exactly
TE 1 TP_TSP_EXCEPTIONLIST_BV one ExceptionListADU indicating
_01 listType = White
EXCEPTIONLIST_TR_TSP_1_DISC See CEN TS17154– Initiating_Apdu containing exactly
OUNT 1 TP_TSP_EXCEPTIONLIST_BV one ExceptionListADU indicating
_02 listType = Discount
12

---------------------- Page: 14 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
Trigger name Definition / Reference APDU for IUT to send when
triggered
TRUSTOBJECTS_TR_1 See CEN/TS 16986:2016, 6.7.2 Initiating_Apdu containing a valid
RequestADU as the only ADU, with
{requestedADUType = trustObject
ADU,
requestedTrustObject = trustObjec
tSpec}
TRUSTOBJECTS_TR_2 See CEN/TS 16986:2016, 6.7.2 Initiating_Apdu containing a
TrustObjectADU as the only ADU
PAYMENTCLAIM_TR_TC_1 See CEN/TS 16986:2016, 6.8.1 Generic trigger not used in the test
cases
See more specific triggers below
PAYMENTCLAIM_TR_TC_1_SEND See CEN TS17154– Initiating_Apdu containing exactly
1 TP_TC_PAYMENTCLAIM_BV_ one PaymentClaimADU with
01 actionCode=send
PAYMENTCLAIM_TR_TC_1_REVO See CEN TS17154– Initiating_Apdu containing exactly
KE 1 TP_TC_PAYMENTCLAIM_BV_ one PaymentClaimADU with
02 actionCode = revoke AND
containing
paymentClaimId = same value as a
previously sent PaymentClaimId
PAYMENTCLAIM_TR_TC_1_ADJU See CEN TS17154– Initiating_Apdu containing exactly
ST 1 TP_TC_PAYMENTCLAIM_BV_ one PaymentClaimADU with
02 actionCode=adjust AND
containing
paymentClaimId = same value as a
previously sent PaymentClaimId
DSRC_CONTRACTISSUERLIST_T See CEN/TS 16986:2016, 7.1.1 Generic trigger not used in the test
R_TSP_1 cases
See more specific triggers below
DSRC_CONTRACTISSUERLIST_TR See TP_TSP_DSRC.CONTRACTI Initiating_Apdu containing three
_TSP_1_DIFFMANUFID SSUERLIST_BV_01 ContractIssuerListADUs with
differing manufacturerID values
DSRC_EFCCONTEXTDATA_TR_T See CEN/TS 16986:2016, 7.2.1 Generic trigger not used in the test
C_1 cases
See more specific triggers below
DSRC_EFCCONTEXTDATA_TR_TC See CEN TS17154– Initiating_Apdu containing a
_1_DSRC_OPEN 1 TP_TC_DSRC.EFCCONTEXTD EFCContextDataADU as the only
ATA_BV_01 ADU, with
domainType = dsrcContext and
the values of all fields in
EFCContextDataADU being within
the range specified by the IUT
13

---------------------- Page: 15 ----------------------

SIST-TS CEN/TS 17154-2:2019
CEN/TS 17154-2:2019 (E)
Trigger name Definition / Reference APDU for IUT to send when
triggered
DSRC_EFCCONTEXTDATA_TR_TC See CEN TS17154– Initiating_Apdu containing an
_1_DSRC_CLOSED 1 TP_TC_DSRC.EFCCONTEXTD EFCContextDataADU as the only
ATA_BV_02 ADU, with
domainType = dsrcClosedContext
and the values of all fields in
EFCContextDataADU being within
the range specified by the IUT
DSRC_BILLINGDETAILS_TR_TC_ See CEN/TS 16986:2016, 7.3.1 Generic trigger not used in the test
1 cases
See more specific triggers below
DSRC_BILLINGDETAILS_TR_TC_1 See CEN TS17154– Send a valid Initiating_Apdu
_SEND 1 TP_TC_DSRC.BILLINGDETAI containing BillingDetailsADUs
LS_BV_01 with actionCode = send
DSRC_BILLINGDETAILS_TR_TC_1 See CEN TS17154– Send a valid Initiating_Apdu
_ADJUST 1 TP_TC_DSRC.BILLINGDETAI containing BillingDetailsADUs
LS_BV_02 with actionCode=adjust
DSRC_BILLINGDETAILS_TR_TC_1 See CEN TS17154– Send an Initiating_Apdu
_REVOKE 1 TP_TC_DSRC.BILLINGDETAI containing BillingDetailsADUs
LS_BV_03 with actionCode=revoke AND
relatedBillingDetails=billingDetail
sId of the previous
BillingDetailsADU
DSRC_REPORTABNORMALOBE See CEN/TS 16986:2016, 7.4.1 Initiating_APDU containing one or
_TR_TC_1 more ADUs of type
ReportAbnormal
...