This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger for each domain.<\/p>\n
EFC systems conforming to this document can be used for various purposes including road (network) tolling, area tolling, collecting fees for the usage of bridges, tunnels, ferries, for access or for parking. From a technical point of view the considered toll systems may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).<\/p>\n
From a process point of view the architectural description focuses on toll determination, toll charging, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.<\/p>\n
The architecture in this document is defined with no more details than required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.<\/p>\n
This document as a whole provides:<\/p>\n
the enterprise view on the architecture, which is concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part;<\/p>\n<\/li>\n
the terms and definitions for common use in an EFC environment;<\/p>\n<\/li>\n
a decomposition of the EFC systems environment into its main enterprise objects;<\/p>\n<\/li>\n
the roles and responsibilities of the main actors. This document does not impose that all roles perform all indicated responsibilities. It should also be clear that the responsibilities of a role may be shared between two or more actors. Mandating the performance of certain responsibilities is the task of standards derived from this architecture;<\/p>\n<\/li>\n
identification of the provided services by means of action diagrams that underline the needed standardised exchanges;<\/p>\n<\/li>\n
identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4 Symbols and abbreviated terms 4.1 Symbols 4.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 5 The EFC community: roles and objectives 5.1 General <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5.2 Other ITS systems and services 5.3 Sensors, vehicle system and common equipment 5.4 Infrastructure sourced data 5.5 Financial\/Commercial systems <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5.6 Telecommunication systems 5.7 Jurisdiction\/Authorities 5.8 Standardisation bodies 5.9 Common service rights provider <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 6 Roles internal to the EFC domain 6.1 General 6.2 EFC domain roles 6.3 Interoperability manager 6.3.1 Short description <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.3.2 Responsibilities 6.4 Toll service provider 6.4.1 Short description 6.4.2 Responsibilities <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.5 User of the service 6.5.1 Short description 6.5.2 Responsibilities <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.6 Toll charger role 6.6.1 Short description 6.6.2 Responsibilities <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.7 EFC functional roles and responsibilities <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 7 Services 7.1 Overview <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 7.2 Sub-services involving toll charger, toll service provider and interoperability manager roles 7.2.1 Adding or deleting a new toll charger <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.2.2 Adding or deleting a new toll service provider <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.2.3 Adding or modifying a toll regime <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.2.4 Defining rules <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 7.2.5 Monitoring operations <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.2.6 Handling disputes <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 7.3 Sub-services involving the toll service provider and user <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 7.3.1 Providing EFC contract <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 7.3.2 Providing customer care <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 7.3.3 User billing <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 7.4 Sub-services involving the toll charger and toll service provider 7.4.1 Collecting transit information in short-range communication systems <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 7.4.2 Collecting charging information (autonomous systems) <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 7.4.3 Collecting transit information (not OBE-based systems) 7.4.4 Providing payment information <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 7.4.5 Detecting Exceptions 7.4.6 Trust objects exchange <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 7.4.7 Handling exceptions <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 7.4.8 Providing local information <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | Annex\u00a0A (informative) Mapping EFC architecture to the C-ITS architecture <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Annex\u00a0B (informative) Information schemata and basic information types <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | Annex\u00a0C (informative) Enterprise objects within roles <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic fee collection. System architecture for vehicle-related tolling – Reference model<\/b><\/p>\n |