Electronic fee collection — System architecture for vehicle-related tolling — Part 1: Reference model
Introduction: The widespread use of tolling also requires provisions for users of vehicles that are roaming through many different toll domains. Users should be offered a single contract for driving a vehicle through various toll domains and those vehicles require on-board equipment (OBE) that is interoperable with the toll systems in the various toll domains. In Europe, for example, this need has been recognised and legislation on interoperability has been adopted (Directive 2004/52). In addition to specialised standards there is also a need for a system architecture that: — provides an architectural “umbrella” for other EFC standards in terms of a common definition of terms and concepts, basic system functionalities, and structure; — provides a common terminology which supports its users to improve the quality of specifications to be used in an international market, — to reduce the risk for conflicting interpretations of specifications (purchaser) and descriptions (supplier), — to simplify the communication between experts from different continents, and — to enhance the potential use of other EFC standards; — defines a common framework, which enables both: — identification of potential activities subject to standardization, and — maintaining a common and consistent view of the whole area; — defines the boundaries between the EFC and external domains; — identifies all architectural objects that lay inside the EFC boundaries; — provides a basic understanding of EFC, EFC interoperability, a
Scope: 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. 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). 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. 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. This document as a whole provides: — 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; — the terms and definitions for common use in an EFC environment; — a decomposition of the EFC systems environment into its main enterprise objects; — 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; — identification of the provided services by means of action diagrams that underline the needed standardised exchanges; — identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).