BSI PD ISO/TR 14806:2013
$167.15
Intelligent transport systems. Public transport requirements for the use of payment applications for fare media
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 42 |
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | Foreword |
| 7 | Introduction |
| 9 | Section sec_1 Section sec_2 1 Scope 2 Terms and definitions |
| 10 | Section sec_2.1 Section sec_2.2 Section sec_2.3 Section sec_2.4 Section sec_2.5 Section sec_2.6 Section sec_2.7 Section sec_2.8 |
| 11 | Section sec_2.9 Section sec_2.10 Section sec_2.11 Section sec_2.12 Section sec_2.13 Section sec_2.14 Section sec_2.15 Section sec_2.16 Section sec_3 3 Symbols and abbreviated terms |
| 12 | Section sec_3.1 Section sec_3.2 Section sec_3.3 Section sec_3.4 Section sec_3.5 Section sec_3.6 Section sec_3.7 Section sec_3.8 3.1 CNP 3.2 HHT 3.3 PAN 3.4 PT 3.5 PTO 3.6 TDA 3.7 TR 3.8 ZVT |
| 13 | Section sec_5 4 Objectives and general requirements for the PTO 5 Use cases |
| 14 | Section sec_5.1 Section sec_5.1.1 Section sec_5.1.2 Section sec_5.1.3 Section sec_5.2 Section sec_5.2.1 Section sec_5.2.2 5.1 Use case 1: Product purchase for loading on customer media 5.2 Use case 2: Access with PTO product data in payment application |
| 15 | Section sec_5.2.3 Section sec_5.3 Section sec_5.3.2 5.3 Use case 3: Pay single journeys on validation |
| 16 | Section sec_5.3.3 Section sec_5.3.4 Section sec_5.4 Section sec_5.4.2 Section sec_5.4.3 5.4 Use case 4: Pay after a period |
| 17 | Section sec_5.4.4 Section sec_5.5 Section sec_5.5.2 5.5 Use case 5: Entitlement with payment application |
| 18 | Section sec_5.5.3 Section sec_6 Section sec_6.1 Section sec_6.2 Section sec_6.2.1 Section sec_6.2.2 Section sec_6.3 Section sec_6.3.1 6 Requirements for payment applications used in transport ticketing 6.1 Payment application storage options 6.2 Payment application without any public transport data 6.3 Payment application with payment transaction logs |
| 19 | Section sec_6.3.2 Section sec_6.3.3 |
| 20 | Section sec_6.4 Section sec_6.4.1 6.4 Payment applications with transit data areas (TDAs) |
| 21 | Section sec_6.4.2 Section sec_6.4.3 |
| 22 | Section sec_6.5 Section sec_6.5.1 Section sec_6.5.2 6.5 Supported transaction types |
| 24 | Section sec_7 7 Matching between use cases, validation access rules and payment application types |
| 26 | Section sec_7.1 Section sec_8 7.1 Revenue protection and inspection 8 Security of payment applications |
| 27 | Section sec_9 Section sec_9.1 Section sec_9.2 Section sec_9.3 9 Condition for use in a multi-application context 9.1 Using payment application in a multi-application media 9.2 PTO Participation in the life cycle management of payment applications 9.3 Payment application selection |
| 28 | Section sec_10 Section sec_10.1 Section sec_10.2 Section sec_10.3 10 Test and certification of payment applications 10.1 Ease of integration into front end equipment 10.2 RF protocol testing 10.3 (SE) payment application certification |
| 29 | Section sec_10.4 10.4 Terminal payment application certification |
| 30 | Section sec_10.5 Section sec_11 10.5 Transaction time 11 Customer data privacy |
| 31 | Annex sec_A Annex sec_A.1 Figure fig_A.1 Annex A (informative) Business rules checklist for using payment applications |
| 32 | Annex sec_A.2 Annex sec_A.2.1 Annex sec_A.2.2 Annex sec_A.2.3 |
| 33 | Annex sec_A.3 |
| 35 | Annex sec_A.4 |
| 36 | Annex sec_B Annex sec_B.1.1 Annex B (informative) Options for providing interoperability between PTOs B.1: Background |
| 37 | Annex sec_B.1.2 Annex sec_B.1.3 Annex sec_B.1.4 Annex sec_B.2 |
| 38 | Reference ref_1 Reference ref_2 Reference ref_3 Reference ref_4 Reference ref_5 Reference ref_6 Reference ref_7 Reference ref_8 Reference ref_9 Bibliography Bibliography |
