BS EN ISO 24014-1:2021
$215.11
Public transport. Interoperable fare management system – Architecture
Published By | Publication Date | Number of Pages |
BSI | 2021 | 92 |
This document gives guidelines for the development of multi-operator/multi-service interoperable public surface (including subways) transport fare management systems (IFMSs) on a national and international level.
This document is applicable to bodies in public transport and related services which agree that their systems need to interoperate.
This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative.
This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring interoperability between several actors in the context of the use of electronic tickets.
The IFMS includes all the functions involved in the fare management process, such as:
-
management of media,
-
management of applications,
-
management of products,
-
security management, and
-
certification, registration, and identification.
This document defines the following main elements:
-
identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems;
-
a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems;
-
use cases describing the interactions and data flows between the different sets of functions;
-
security requirements.
In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E).
This document does not define:
-
the technical aspects of the interface between the medium and the medium access device;
-
the data exchanges between the medium and the medium access device;
The data exchanges between the medium and the medium access device are proposed by other standardization committees.
-
the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
4 | European foreword |
8 | Foreword |
9 | Introduction |
11 | 1 Scope |
12 | 2 Normative references 3 Terms and definitions |
15 | 4 Abbreviated terms |
16 | 5 Requirements |
17 | 6 System environment for IFMS 6.1 General 6.2 Mobility platforms 7 Conceptual framework for IFMS 7.1 General |
18 | 7.2 Description of IFM roles and external roles |
22 | 7.3 Basic framework of the generic IFM functional model |
23 | 8 Use case description for the IFM functional model 8.1 Description of IFM-roles and external roles |
24 | 8.2 Define set of rules 8.2.1 General 8.2.2 Define set of rules for Customer accounts 8.2.3 Define set of rules for media |
25 | 8.2.4 Define set of rules for ID services 8.2.5 Define set of rules for payment services 8.3 Certification 8.3.1 General |
26 | 8.3.2 Certification of organizations 8.3.3 Certification of components 8.3.4 Certification of media 8.3.5 Certification of ID services |
27 | 8.3.6 Certification of payment services 8.3.7 Certification of application specifications and templates 8.3.8 Certification of product specifications and templates |
28 | 8.4 Interaction with external objects 8.4.1 General 8.4.2 Interaction with external media |
29 | 8.4.3 Interaction with external applications |
30 | 8.4.4 Interaction with external ID services |
31 | 8.4.5 Interaction with external payment services |
32 | 8.5 Registration 8.5.1 General 8.5.2 Registration of organizations 8.5.3 Registration of components |
33 | 8.5.4 Registration of ID services 8.5.5 Registration of customer accounts |
34 | 8.5.6 Registration of payment services 8.5.7 Registration of media |
35 | 8.5.8 Registration of customer media 8.5.9 Registration of application templates 8.5.10 Registration of applications 8.5.11 Registration of product templates |
36 | 8.5.12 Registration of products 8.6 Managing ID services 8.6.1 General 8.6.2 Enrolment and update of Customer ID data via an application form |
37 | 8.6.3 Enrolment and update of Customer ID data via an external ID service 8.6.4 Update of Customer ID data via an online account |
38 | 8.6.5 Re-use of incumbent Customer ID data 8.6.6 Management and maintenance of Customer ID data |
39 | 8.6.7 Providing the ID service to IFMS internal and external organizations |
40 | 8.7 Management of customer accounts 8.7.1 General 8.7.2 Secure login to customer online accounts 8.7.3 Connect/disconnect customer media to/from the customer online account |
41 | 8.7.4 Transfer of products between connected customer media |
42 | 8.7.5 Connect system generated account with a customer account |
43 | 8.7.6 Termination of customer accounts |
44 | 8.8 Management of customer media 8.8.1 General 8.8.2 Provisioning of media |
45 | 8.8.3 Termination of customer media |
46 | 8.9 Management of applications 8.9.1 General 8.9.2 Dissemination of application templates 8.9.3 Acquisition of applications |
47 | 8.9.4 Termination of application templates |
48 | 8.9.5 Termination of applications 8.10 Management of products |
49 | 8.10.1 Dissemination of product templates 8.10.2 Termination of product templates |
50 | 8.10.3 Management of action lists 8.10.4 Acquisition of products |
51 | 8.10.5 Modification of product parameters 8.10.6 Termination of products |
52 | 8.10.7 Use and inspection of products |
53 | 8.10.8 Collection of data 8.10.9 Forwarding data |
54 | 8.10.10 Generation and distribution of clearing reports 8.11 Security management 8.11.1 General |
55 | 8.11.2 Monitoring of IFM processes and IFM data life cycle 8.11.3 Management of IFM security keys 8.11.4 Management of security lists |
58 | 8.12 Customer Service management (optional) 9 System interface identification 10 Identification 10.1 General |
59 | 10.2 Numbering scheme 10.3 Prerequisites 10.3.1 There is one Registrar within the IFMS. 10.3.2 All objects, e.g. templates and components, have an owner who is one of the actors in the IFMS. 10.3.3 The identification of the application and product shall be as short and compact as possible due to the minimization of the transaction time between the customer medium and the MAD. 11 Security in IFMSs 11.1 General |
60 | 11.2 Protection of the interests of the public 11.3 Assets to be protected |
61 | 11.4 General IFM security requirements |
62 | Annex A (informative) Mobility Platform ā German example |
67 | Annex B (informative) Pay-As-You-Go (PAYG) roles and relationships in an IFMS |
73 | Annex C (informative) Mobility ID service example |
82 | Annex D (informative) Examples of IFMS implementations |
88 | Annex E (informative) Media centric management and back-office centric management |
90 | Bibliography |