HGV

heavy goods vehicle

HTTPS

HTTP over Secure socket

HTTP

HyperText Transfer Protocol

charge area

anywhere within the width of the carriageway (all lanes in both directions) at the charge point + 1.0 meter outside the carriageway on both sides of the carriageway limited in the travelling direction by the footprint of the DSRC beacons
NOTE: The term is also in other references used for describing the whole geographical area covered by the EFC system.

anywhere within the width of the carriageway (all lanes in both directions) at the charge point + 1.0 meter outside the carriageway on both sides of the carriageway limited in the travelling direction by the footprint of the DSRC beacons
NOTE: The term is also in other references used for describing the whole geographical area covered by the EFC system.

charge object detection

event marking the usage of a charge object
NOTE 1 to entry: This event refers to the use of a certain object and not to the mechanisms by which detection is produced.

event marking the usage of a charge object
NOTE 1 to entry: This event refers to the use of a certain object and not to the mechanisms by which detection is produced.

charge object; EFC object

geographic object where a charge for the use of infrastructure is due according to the definition in the toll regime

geographic object where a charge for the use of infrastructure is due according to the definition in the toll regime

charge parameter change

event occurring within a tolling system, that is relevant for charge calculation, such as change of vehicle category, but not for the detection of a charge object itself

event occurring within a tolling system, that is relevant for charge calculation, such as change of vehicle category, but not for the detection of a charge object itself

charge report (CR)

information containing road usage and related information originated at the Front End
NOTE 1 to entry: In 2009/750/EC, Charge Report is referred to as “toll declaration”.

information containing road usage and related information originated at the Front End
NOTE 1 to entry: In 2009/750/EC, Charge Report is referred to as “toll declaration”.

CRR

charge report response

charge-relevant event

event occurring within a tolling system, which is relevant for charge calculation, but not for the detection of a Charge Object itself
NOTE: Examples of this type of event are changes in vehicle category or time zone.

event occurring within a tolling system, which is relevant for charge calculation, but not for the detection of a Charge Object itself
NOTE: Examples of this type of event are changes in vehicle category or time zone.

chargeable event

event in which a vehicle passes through a Charge Object that implies that vehicle has to be charged or a different rate (e.g. price per kilometre) applied
NOTE: This event refers to the use of a certain object and not to the mechanisms by which detection is produced.

event in which a vehicle passes through a Charge Object that implies that vehicle has to be charged or a different rate (e.g. price per kilometre) applied
NOTE: This event refers to the use of a certain object and not to the mechanisms by which detection is produced.

charging data

toll relevant data produced by the on-board equipment and sent to the Toll Service Provider's back-office systems

toll relevant data produced by the on-board equipment and sent to the Toll Service Provider's back-office systems

CELB

Charging Error Interval Lower Bound

CEUB

Charging Error Interval Upper Bound

CI

charging metric

charging performance metrics

specific calculations used to describe the charging performance of a system
NOTE 1 to entry: These calculations are technology and schema-independent.

specific calculations used to describe the charging performance of a system
NOTE 1 to entry: These calculations are technology and schema-independent.

charging period

period of time which is used to define the frequency of the Toll Declarations, when Charge Reports are aggregated to form Toll Declarations
NOTE: If the Charging Period is set to 24 hrs then in the Toll Context Data a single Toll Declaration is submitted for each 24 hr period for each Service User.

period of time which is used to define the frequency of the Toll Declarations, when Charge Reports are aggregated to form Toll Declarations
NOTE: If the Charging Period is set to 24 hrs then in the Toll Context Data a single Toll Declaration is submitted for each 24 hr period for each Service User.

charging scheme

description of an Electronic Fee Collection system and its context including (but not limited to) the motivation and strategy for the fee collection, the definition of the geographical area, road network or road section where the fee will be collected, vehicles types subject to fee collection, fee payment rules, tariffs, exception handling and enforcement rules, technology to be used,…

description of an Electronic Fee Collection system and its context including (but not limited to) the motivation and strategy for the fee collection, the definition of the geographical area, road network or road section where the fee will be collected, vehicles types subject to fee collection, fee payment rules, tariffs, exception handling and enforcement rules, technology to be used, implementation and duration and how the collected fee will be used

charging system

system for Electronic Fee Collection supporting and fulfilling the requirements of a Charging Scheme

system for Electronic Fee Collection supporting and fulfilling the requirements of a Charging Scheme

impact

an assessment of the impact that an event or operator action defined by the situation record has on the driving conditions

an assessment of the impact that an event or operator action defined by the situation record has on the driving conditions

implementation conformance statement (ICS)

statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented

statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented

implementation conformance statement proforma

document, in the form of a questionnaire, which when completed for an implementation or system becomes an implementation conformance statement

document, in the form of a questionnaire, which when completed for an implementation or system becomes an implementation conformance statement

implementation extra information for testing

statement made by the supplier or an implementor of a DUT which contains or references all of the information (in addition to that given in the implementation conformance statement) related to the DUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the DUT

statement made by the supplier or an implementor of a DUT which contains or references all of the information (in addition to that given in the implementation conformance statement) related to the DUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the DUT

implementation extra information for testing pro forma

document, in the form of a questionnaire, which when completed for an IUT becomes an implementation extra information for testing

document, in the form of a questionnaire, which when completed for an IUT becomes an implementation extra information for testing

implementation under test (IUT)

implementation of one or more OS1 protocols in an adjacent user/provider relationship, being that part of a real open system which is to be studied by testing

implementation of one or more OS1 protocols in an adjacent user/provider relationship, being that part of a real open system which is to be studied by testing

ind

indication

ICT

information and communication technologies

information asset

knowledge or data that has value to the stakeholder

knowledge or data that has value to the stakeholder

information security

preservation of confidentiality, integrity, availability, authenticity, accountability, non-repudiation and reliability of information

preservation of confidentiality, integrity, availability, authenticity, accountability, non-repudiation and reliability of information

information security event

identified occurrence of a system, service or network state indicating a possible breach of information security policy or failure of controls, or a previously unknown situation that may be security relevant

identified occurrence of a system, service or network state indicating a possible breach of information security policy or failure of controls, or a previously unknown situation that may be security relevant