BSI PD CEN/TS 16702-1:2020
$215.11
Electronic fee collection. Secure monitoring for autonomous toll systems – Compliance checking
Published By | Publication Date | Number of Pages |
BSI | 2020 | 90 |
This document specifies transactions and data for Compliance Checking – Secure Monitoring. The Scope of this document consists of:
-
the concept and involved processes for Secure Monitoring;
-
the definition of transactions and data;
-
the use of the OBE compliance checking transaction as specified in EN ISO 12813 , for the purpose of Compliance Checking – Secure Monitoring;
-
the use of back end transactions as specified in EN ISO 12855 , for the purpose of Compliance Checking – Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes;
-
a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework;
-
the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.
Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
9 | 1 Scope 2 Normative references |
11 | 3 Terms and definitions |
14 | 4 Abbreviations |
15 | 5 Processes 5.1 Overview |
17 | 5.2 Profiles |
22 | 5.3 Itinerary Freezing 5.3.1 Introduction |
23 | 5.3.2 Generate Itinerary |
24 | 5.3.3 Real-time freezing |
25 | 5.3.4 Freezing per declaration 5.4 Checking of Itinerary Freezing 5.4.1 Introduction |
26 | 5.4.2 Observing a vehicle 5.4.3 Retrieving Proof of Itinerary Freezing (PIF) |
27 | 5.4.4 Checking PIF against Observation |
28 | 5.5 Checking of Toll Declaration 5.5.1 Introduction 5.5.2 Retrieve Itinerary Data 5.5.3 Check Itinerary Consistency |
29 | 5.5.4 Checking Toll Declaration against Itinerary 5.6 Inconsistency report 5.7 Providing EFC Context Data |
30 | 5.8 Key Management 5.8.1 Introduction 5.8.2 Requirements |
31 | 6 Transactions 6.1 Introduction |
33 | 6.2 Description of Itinerary Data 6.2.1 Introduction |
34 | 6.2.2 Itinerary Leaf |
35 | 6.2.3 Itinerary Record Data Elements 6.2.3.1 Introduction 6.2.3.2 Common Data Elements for all Itinerary Records 6.2.3.3 Common data elements for Itinerary Records frozen in real-time |
36 | 6.2.3.4 Common data elements for Context Independent Itinerary Records |
37 | 6.2.3.5 Common data elements for Context Dependent Itinerary Records – Detected Charge Object 6.2.3.6 Common data elements for Context Dependent Itinerary Records – Number of detected Events 6.3 Retrieving PIF in real-time (DSRC Transaction) 6.3.1 Transactional Model |
38 | 6.3.2 Syntax and Semantics |
40 | 6.3.3 Security 6.4 Toll Declaration 6.4.1 Transactional Model |
41 | 6.4.2 Syntax and semantics 6.4.3 Itinerary Trunk |
43 | 6.4.4 Security 6.5 Back end data checking 6.5.1 Introduction 6.5.2 Transactional model |
45 | 6.5.3 Checks of the Itinerary |
46 | 6.5.4 Syntax and semantics 6.5.5 Security 6.6 Inconsistency Report 6.6.1 Transactional model |
47 | 6.6.2 Syntax and semantics |
48 | 6.6.3 Security 6.7 Providing EFC Context Data 6.7.1 Transactional model |
49 | 6.7.2 Syntax and semantics 6.7.3 Security 7 Security 7.1 Security functions and elements 7.1.1 Hash functions 7.1.2 MAC |
50 | 7.1.3 Digital signatures 7.1.4 Public Keys, Certificates and CRL 7.2 Key Management 7.2.1 Key Exchange between Stakeholders |
51 | 7.2.2 Key generation and certification 7.3 Trusted Recorder and SM_CC Verification SAM characteristics 7.3.1 Introduction |
52 | 7.3.2 Trusted Recorder |
53 | 7.3.3 SM_CC Verification SAM |
54 | Annex A (normative)Data type specification |
55 | Annex B (normative)Protocol Implementation Conformance Statement Proforma B.1 Guidance for completing the PICS proforma B.1.1 Purposes and structure B.1.2 Abbreviations and conventions |
58 | B.1.3 Instructions for completing the PICS proforma B.2 Identification of the implementation B.2.1 General B.2.2 Date of the statement B.2.3 Implementation Under Test (IUT) identification |
59 | B.2.4 System Under Test (SUT) identification B.2.5 Product supplier |
60 | B.2.6 Applicant (if different from product supplier) B.2.7 PICS contact person B.3 Identification of the protocol B.4 Global statement of conformance |
61 | B.5 Roles B.6 Types of Secure Monitoring |
62 | B.7 Capabilities and conditions B.8 Processes |
64 | Annex C (informative)Example transactions |
71 | Annex D (informative)Relationships to other standards D.1 Relation to CEN ISO/TS 19299, Electronic fee collection – Security framework |
72 | D.2 Relations to EN ISO 12855 and EN ISO 12813 |
73 | Annex E (informative)Essentials of the SM_CC concept E.1 Introduction E.2 The SM_CC concept – FAQs E.2.1 What is the purpose of SM_CC? E.2.2 How does it work? |
74 | E.2.3 Why is a separate stream of data necessary for SM_CC? E.2.4 We already have a standard for CCC. What does SM_CC add? |
75 | E.2.5 Will SM_CC replace CCC? E.3 SM_CC options E.3.1 SM_CC_1 E.3.1.1 The process of itinerary freezing in real-time |
76 | E.3.1.2 Observing the vehicle and checking of itinerary freezing |
78 | E.3.1.3 Choice of a type of Itinerary Record E.3.1.4 Checking of Toll Declaration |
79 | E.3.2 SM_CC_2 E.3.2.1 The process of itinerary freezing in real-time with a TR with a trusted time source |
80 | E.3.2.2 Implementation E.3.2.3 Observing the vehicle and checking of itinerary freezing |
81 | E.3.2.4 Checking of Toll Declaration E.3.3 SM_CC_3a E.3.3.1 The process of itinerary freezing per declaration |
82 | E.3.3.2 Observing the vehicle and checking of itinerary freezing |
83 | E.3.3.3 Checking of Toll Declaration E.3.4 SM_CC_3b E.3.4.1 General E.3.4.2 The process of itinerary freezing |
84 | E.3.4.3 Observing the vehicle and checking of itinerary freezing E.4 Managing multiple toll domains E.4.1 Overlapping toll domains E.4.1.1 Introduction E.4.1.2 Using toll domain counters simultaneously |
85 | E.4.1.3 A maximum of 4 simultaneous toll domain counters E.4.1.4 Harmonization of real-time freezing parameters between adjacent domains |
86 | E.4.2 The ‘catch-all’ toll domain counter |
87 | Annex F (informative)Use of this document for the EETS F.1 General F.2 Overall relationship between European standardization and the EETS F.3 European standardization work supporting the EETS |
88 | F.4 Correspondence between this document and the EETS |