本文档定义了电子收费（EFC）系统环境的体系结构，在该体系结构中，具有一个合同的客户可以在各种收费域中使用车辆，每个域具有不同的收费充电器。符合本文件要求的EFC系统可用于各种用途，包括道路（网络）收费、区域收费、收取桥梁、隧道、渡轮使用费、进出或停车费。从技术角度来看，所考虑的收费系统可以通过车辆上的电子设备或其他方式（例如自动车牌识别，ANPR）识别需要收费的车辆。从流程的角度来看，架构描述的重点是收费确定、收费和相关的强制措施。实际收取的通行费，即收取款项，不在本文件的范围内。本文件中的体系结构定义的细节不超过总体概述、通用语言、确定其他标准的需求和相互作用以及起草这些标准所需的细节。整个文件规定:-企业对体系结构的看法，它涉及到管理其所属组织内指定系统活动的目的、范围和策略；-EFC环境中常用的术语和定义；-将EFC系统环境分解为其主要企业对象；-主要行动者的作用和责任。本文件并未强制要求所有角色履行所有指定职责。还应该清楚的是，一个角色的责任可以由两个或多个行动者分担。授权履行某些职责是从该体系结构派生的标准的任务；-通过强调所需标准化交换的行动图确定所提供的服务；-EFC系统互操作性接口的识别，采用专门标准（指定或待指定）。

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).