Electronic fee collection. Secure monitoring for autonomous toll systems - Compliance checking
Electronic fee collection. Secure monitoring for autonomous toll systems - Compliance checking
  • Load image into Gallery viewer, Electronic fee collection. Secure monitoring for autonomous toll systems - Compliance checking
  • Load image into Gallery viewer, Electronic fee collection. Secure monitoring for autonomous toll systems - Compliance checking

Electronic fee collection. Secure monitoring for autonomous toll systems - Compliance checking

Regular price
£348.00
Sale price
£348.00
Regular price
£174.00
Sold out
Unit price
per 

What is PD CEN/TS 16702-1 about?  

PD CEN/TS 16702 is a series focuses on secure monitoring of autonomous electronic fee collection systems. PD CEN/TS 16702-1 provides you compliance checking guidelines for secure monitoring of autonomous electronic fee collection systems. 

PD CEN/TS 16702-1 specifies transactions and data between roadside equipment of the Toll Charger over dedicated short-range communication as well as transactions between the Toll Charger's and the Toll Service Provider's back-end systems for Compliance Checking - Secure Monitoring.  

PD CEN/TS 16702-1 specifies: 

  • The concept and involved processes for secure monitoring 
  • The definitions of transactions and data 
  • The use of the on-board equipment compliance checking transaction for compliance checking - secure monitoring 
  • The use of back-end transactions, for compliance checking – secure monitoring. This includes definitions for the use of optional elements and reserved attributes 
  • Specification of technical and organizational security measures involved in secure monitoring, on top of measures provided for in the electronic fee collection Security Framework 
  • The interrelations between different options in the onboard equipment, Toll Service Provider and Toll Charger domain and their high-level impacts 

Who is PD CEN/TS 16702-1 for? 

PD CEN/TS 16702-1  on  secure monitoring for autonomous toll systems is useful for: 

  • Toll chargers and service providers 
  • Toll service users 
  • Electronic fee collection system 
  • Information security system 
  • European Electronic Toll Service providers 
  • Quality assurance tests organizations 
  • Compliance checking interrogator operators 

Why should you use PD CEN/TS 16702-1 

PD CEN/TS 16702-1 introduces you to the conceptual framework of secure monitoring compliance checking in terms of requirements to a system or devices implementing it. It also describes the relations between different processes and information classes.  

PD CEN/TS 16702-1 helps in Compliance Check Communication (CCC) which provides useful indications to a Toll Charger of whether the on-board equipment is operating correctly or not.  

PD CEN/TS 16702-1 provides you with further background information on the use and rationale for Secure Monitoring Compliance Checking processes. Also, secure monitoring compliance checking concept provides a solution that allows a toll charger to check the trustworthiness of the toll declarations from a toll service provider, whilst respecting the privacy of the user. 

With PD CEN/TS 16702-1, the Secure Monitoring Compliance Checking (SMCC) process enables different implementations to comply with applicable privacy. Different options for example regarding the content of itinerary data and different ways to access the data for real-time or delayed checks can be selected to apply to legal requirements.  

What’s changed since the last update? 

PD CEN/TS 167021:2020 supersedes PD CEN/TS 16702-1:2014. PD CEN/TS 167021:2020 includes some technical changes with respect to PD CEN/TS 16702-1:2014. These include: 

  • Amendment of terms, in order to reflect harmonization of terms across electronic fee collection (EFC) standards 
  • Renaming SmccClaimADU to InconsistencyReportAdu 
  • Breaking up the Checking Itinerary transaction into Checking Itinerary Trunk and Checking Itinerary Leaf transactions 
  • Renaming itinerary sequence and itinerary batch to itinerary leaf and itinerary trunk; 
  • Presenting the ASN.1 code as a separate electronic file referenced from Annex A