BSI PD ISO/TR 20526:2017
$167.15
Account-based ticketing state of the art report
| Published By | Publication Date | Number of Pages |
| BSI | 2017 | 34 |
This document provides a state of the art of the components that make up account-based ticketing as currently understood. This state of the art can be used to identify those aspects where international standardization or coordination can lead to benefits. These will then be proposed as normal ISO work items, independent of this document.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 7 | Foreword |
| 8 | Introduction |
| 10 | 1 Scope 2 Normative references 3 Terms and definitions |
| 11 | 4 Conformance 5 Symbols and abbreviated terms |
| 12 | 6 How does account-based ticketing work 6.1 Business roles 6.1.1 Customer |
| 13 | 6.1.2 Media Provider 6.1.3 Identity Provider 6.1.4 Service Operator |
| 14 | 6.1.5 Product Owner 6.1.6 Account Provider |
| 15 | 6.1.7 Payment Provider 7 Impact of account-based ticketing 7.1 Benefits of account-based ticketing 7.1.1 General 7.1.2 Issuing media cost reduction |
| 16 | 7.1.3 Equipment validation simplification 7.1.4 Business rule seamless update 7.1.5 Instant product management 7.1.6 No media/back office reconciliation |
| 17 | 7.1.7 More flexible customer management 7.1.8 Improved customer service 7.1.9 Simpler interoperability 7.1.10 Faster time to market for new technology evolution 7.2 Disadvantages of account-based ticketing 7.2.1 General 7.2.2 Keeping the front-office equipment connected to the back office |
| 18 | 7.2.3 Treating transactions upload as business critical 7.2.4 Minimizing transaction speed 7.2.5 Supporting multiple technologies within the front office equipment 7.2.6 Making AFC back office able to support third-party technology and authentication 7.2.7 Performing control on read-only media 7.2.8 Building and maintaining customers’ confidence |
| 19 | 8 What are the significant features of account-based ticketing? 8.1 Revenue protection and journey recording 8.1.1 Purpose of recording journeys 8.1.2 Common approaches and typical data flows |
| 20 | 8.1.3 Functional operations at infrastructure to record journeys 8.1.4 Controlling fraud 8.1.5 Implications for inspection |
| 21 | 8.1.6 List management |
| 22 | 8.1.7 Use of media-based data storage other than the token ID 8.2 Data privacy |
| 23 | 8.3 Options for travel tokens and management of multiple token credentials 8.3.1 Background |
| 24 | 8.3.2 Work to be done |
| 25 | 8.4 Management of customer accounts with multiple tokens 8.4.1 General 8.4.2 Media technologies |
| 26 | 8.4.3 Impacts of using third party-issued media |
| 27 | 8.4.4 Implications for fraudulent usage 8.5 Migration to ABT or server-centric schemes 8.6 Integration of urban and long-distance ABT |
| 29 | 8.7 Interoperable ABT systems 8.7.1 Interoperability issues 8.7.2 Hub-based interoperable ABT system |
| 30 | 8.8 Considerations for payment providers |
| 32 | Bibliography |
