This International Standard specifies<\/p>\n
the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. also systems automatically reading licence plate numbers of vehicles passing a toll point;<\/p>\n<\/li>\n
an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.<\/p>\n<\/li>\n
charging related data (toll declarations, billing details),<\/p>\n<\/li>\n
administrative data, and<\/p>\n<\/li>\n
confirmation data;<\/p>\n<\/li>\n
transfer mechanisms and supporting functions;<\/p>\n<\/li>\n
information objects, data syntax and semantics;<\/p>\n<\/li>\n
examples of data interchanges.<\/p>\n<\/li>\n<\/ul>\n
This International Standard supports any toll service and any technology used for charging.<\/p>\n
It is defined as a toolbox standard of transactions and messages which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.<\/p>\n
The scope of this International Standard is illustrated in Figure 2. The data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO\/IEC 8824-1.<\/p>\n
Any communication between Toll Charger and\/or Toll Service Provider with any other involved party is outside the scope of this International Standard. Any communication between elements of the Toll Charger and the Toll Service Provider which is not part of the back office communication is outside the scope of this International Standard.<\/p>\n
The processes regarding the payments and exchanges of fiscal, commercial or legal accounting documents are outside the scope of this International Standard.<\/p>\n
The definitions of service communication channels, protocols and service primitive to actually transfer the messages are outside the scope of this International Standard.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 9<\/td>\n | Scope <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | Normative references <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Architectural concept Main roles in the Toll Charging environment Information exchange between Toll Charging and Provision General <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Basic interaction protocol Basic protocol mechanisms General approach Identification schema Request message <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Acknowledge message Status message Exchange Trust Objects Originating and providing EFC context data <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | Manage Exception list General Exception list entry requested by a Toll Charger Exception list entry decided by the Toll Service Provider <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | Report Toll declarations <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Report Billing details Claim payment for service usage <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | Exchange Enforcement data General Retrieve User Details <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Provide User Details Retrieve and Report CCC Event Exchange Quality assurance parameters <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Computational specification Overview <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Application Protocol Data Units General Application Protocol Control Information <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Application Data Unit <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | RequestADU data structure <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | AcknowledgeADU data structure StatusADU data structure <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | TrustObjectsADU data structure <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | EFCContextDataADU data structure ExceptionListADU data structure <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | ReportAbnormalOBEADU data structure <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | RetrieveTollDeclarationADU data structure Toll DeclarationADU data structure <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | BillingDetailsADU data structure <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | PaymentClaimADU data structure <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | RetrieveUserDetailsADU data structure ProvideUserDetailsADU data structure <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | RetrieveCCCEventADU data structure <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | ReportCCCEventADU data structure Report QA data structure <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | Transfer mechanisms and supporting functions Transfer mechanisms Supporting functions Communication Services Message Authenticators <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | Untitled <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic fee collection. Information exchange between service provision and toll charging<\/b><\/p>\n |