• There are no items in your cart

09/30167386 DC : DRAFT JAN 2009

Superseded

Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by

BS EN ISO 17573 - ELECTRONIC FEE COLLECTION - SYSTEMS ARCHITECTURE FOR VEHICLE RELATED TOLLING

Superseded date

31-01-2011

Superseded by

BS ISO 17573:2010

Published date

23-11-2012

Sorry this product is not available in your region.

1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations and symbols
    4.1 Abbreviations
    4.2 Symbols
5 The EFC community: roles and objectives
    5.1 Introduction
    5.2 Toll charging environment
    5.3 External objects
         5.3.1 Financial systems, e.g. banks, credit cards
                 companies and clearing houses
         5.3.2 Telecom systems
         5.3.3 Positioning systems
         5.3.4 Vehicle sensors and data stores
         5.3.5 Environmental sensors and other ITS systems
         5.3.6 EFC equipment suppliers
         5.3.7 Certification bodies
         5.3.8 Standardisation bodies
         5.3.9 Authorities
6 Roles and responsibilities in the toll charging environment
    6.1 Introduction
    6.2 Role related to the provision of the toll service
    6.3 Role related to the use of the toll service
    6.4 Role related to the charging of the toll
    6.5 Role related to the management of the toll charging
         environment
    6.6 Decomposition of the toll charging environment
         6.6.1 Introduction
         6.6.2 The toll service provider domain
         6.6.3 The user domain
         6.6.4 The toll charger domain
         6.6.5 The toll charging environment management domain
7 EFC system behaviour
    7.1 Introduction
    7.2 Roles, responsibilities and actors
    7.3 Interaction matrix and action diagrams
         7.3.1 Adding (or excluding) a new toll charger
         7.3.2 Adding (or excluding) a new service provider
         7.3.3 Adding, modifying or closing an EFC regime
         7.3.4 Defining rules and monitoring operations
         7.3.5 Providing EFC contract - subscribing (or
                unsubscribing) of a new user
         7.3.6 Collecting fee information - user billing
         7.3.7 Collecting transit information
         7.3.8 Collecting charging information (GNSS/CN)
         7.3.9 Claiming fees
         7.3.10 Providing customer care
         7.3.11 Exceptions detection - user and OBE compliance
                checking
    7.4 Resulting interaction between actors
8 Information schemata and basic information types
    8.1 Static schema
    8.2 Basic information objects
         8.2.1 The EFC rules
         8.2.2 Transit information
         8.2.3 Operational information
         8.2.4 Payment information
    8.3 Dynamic schema
9 Interfaces and computational objects
    9.1 Generalities
    9.2 Management object interfaces
         9.2.1 Security requirements
    9.3 Charging object interfaces
         9.3.1 General
         9.3.2 Charging-Management interface
         9.3.3 Charging-Basic Provision interface
         9.3.4 Charging-Providing EFC Context Data interface
         9.3.5 Charging-Operating Pre-billing interface
         9.3.6 Charging-Use interface
         9.3.7 Security requirements
    9.4 Basic Provision object interfaces
         9.4.1 General
         9.4.2 Basic Provision-Management interface
         9.4.3 Basic Provision-Charging interface
         9.4.4 Basic Provision-Personalizing the OBE interface
         9.4.5 Basic Provision-Acting as a Contract Agent
                interface
         9.4.6 Basic Provision-Operating Pre-billing interface
         9.4.7 Basic Provision-Use interface
         9.4.8 Security requirements
    9.5 Maintaining the OBE object interfaces
         9.5.1 General
         9.5.2 Maintaining the OBE-Personalizing the OBE
                interface
         9.5.3 Maintaining the OBE-Use interface
         9.5.4 Security requirements
    9.6 Personalizing the OBE object interfaces
         9.6.1 General
         9.6.2 Personalizing the OBE-Basic provision interface
         9.6.3 Personalizing the OBE-Maintaining the OBE
                interface
         9.6.4 Personalizing the OBE-Acting as a Contract Agent
                interface
         9.6.5 Personalizing the OBE-Use interface
         9.6.6 Security requirements
    9.7 Acting as a Contract Agent object interfaces
         9.7.1 General
         9.7.2 Acting as a Contract Agent-Basic Provision
                interface
         9.7.3 Acting as a Contract Agent-Maintaining the OBE
                interface
         9.7.4 Acting as a Contract Agent-Personalizing the OBE
                interface
         9.7.5 Acting as a Contract Agent-Charging interface
         9.7.6 Acting as a Contract Agent-Use interface
         9.7.7 Security requirements
   9.8 Providing Context Data object interfaces
         9.8.1 General
         9.8.2 Providing Context Data-Charging interface
         9.8.3 Providing Context Data-Use interface
         9.8.4 Security requirements
   9.9 Operating Pre-billing object interfaces
         9.9.1 General
         9.9.2 Operating Pre-billing-Basic Provision interface
         9.9.3 Operating Pre-billing-Charging interface
         9.9.4 Operating Pre-billing-Use interface
         9.9.5 Security requirements
   9.10 Use object interfaces
         9.10.1 General
         9.10.2 Use-Basic Provision interface
         9.10.3 Use-Maintaining the OBE interface
         9.10.4 Use-Personalizing the OBE interface
         9.10.5 Use-Acting as a Contract Agent interface
         9.10.6 Use-Providing Context Data interface
         9.10.7 Use-Operating Pre-billing interface
         9.10.8 Use-Charging interface
         9.10.9 Security requirements
10 Points of observation and viewpoint correspondences
    10.1 Points of observation
    10.2 Correspondence between enterprise and information
         viewpoints
    10.3 Correspondence between enterprise and computational
         viewpoints
Annex A (informative) - Short ODP description
Annex B (informative) - Comparison with previous versions
    B.1 Previous model for EFC used for vehicle related transport
        services
    B.2 The relationships between the new and the previous
        conceptual model
Annex C (informative) - Relations between this Standard and IFMSA
    C.1 Introduction: the IFM environment
    C.2 The relationships between the EFC model in this Standard
        and the IFMSA model
Annex D (informative) - Relation with the European Electronic
        Toll System
    D.1 Terms
    D.2 EETS roles model
Annex E (informative) - Example of the Japanese electronic toll
        system
    E.1 Updated previous class diagram for EFC system
    E.2 The relation with the new model

BS EN ISO 17573

Committee
EPL/278
DocumentType
Draft
PublisherName
British Standards Institution
Status
Superseded
SupersededBy

EN ISO 24014-1:2015 Public transport - Interoperable fare management system - Part 1: Architecture (ISO 24014-1:2015)
ISO/IEC 7498-1:1994 Information technology Open Systems Interconnection Basic Reference Model: The Basic Model
ISO/IEC 10746-3:2009 Information technology Open distributed processing Reference model: Architecture Part 3:
ISO/IEC 15414:2015 Information technology Open distributed processing Reference model Enterprise language
ISO/IEC 10746-2:2009 Information technology Open distributed processing Reference model: Foundations Part 2:
ISO/IEC 10746-4:1998 Information technology — Open Distributed Processing — Reference Model: Architectural semantics — Part 4:
ISO/IEC 10746-1:1998 Information technology — Open Distributed Processing — Reference model: Overview — Part 1:

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.