2009 Fare Collection Workshop

Transcription

1 IFMS: Integrating in Fare Systems & Mobile s Chung-Chung Tam Chicago Transit Authority Revenue Systems Engineer ISO TC204 WG8 Committee U.S. Expert APTA UTFS Task Force International Lead Houston, Texas March 15-18, 2009 GROWTH AND RENEWAL

2 OVERVIEW Public Transport and Emergency Services [ISO TC204 WG8 Committee] Develops standards used in Intelligent Transportation Systems (ITS) applications For use in public transportation and emergency services applications Interoperable Fare Management Systems (IFMS) Joint effort with European Committee for Standardization (CEN) CEN TC278 WG3 SG5 Committee Page 2

3 ISO/CEN Membership Countries [ISO TC204 WG8] & [CEN TC278 WG3 SG5] 14 countries: China Finland France Germany Great Britain Ireland Italy Japan Korea Netherlands Norway South Africa Switzerland United States Page 3

4 CEN Internal Enquiry 1st contact, Vienna PWI, Vancouver WI, Paris Discussion of Japanese requirements and negotiation of comments, Oslo and Frankfurt Internal comment resolution, London Official comment resolution, Busan Target final voting Published [ISO :2007] Presentation in Beijing TIMELINE OF STANDARDIZATION WORK IFMS Part 1: Architecture ISO TC204 WG8 CEN TC278 WG3 SG t Page 4

5 ISO STANDARDS Interoperable Fare Management System (IFMS) ISO :2007 (Published) Public Transport IFMS Part 1: Architecture number=41985 ISO/PDTR (In Progress) Public Transport IFMS Part 2: Recommended Business Practice for Set of Rules PDTR Proposed Draft Technical Report Page 5

6 INTEROPERABILITY A Customer s Perspective Interoperability provides the customer with a seamless journey using one Customer Media independent of the transport means and service providers Operator 2 Operator 3 Operator 4... Operator X Operator 1 Customer Media Operator Y Page 6

7 REQUIREMENTS IFMS Part 1: Architecture Interoperability Hardware & supplier independent interface description Functionally neutral to specific transport organization structures Recognize and prevent internal & external fraud attacks (Security) Integrity of data Easy & fair settlement, independent of commercial agreements Flexibility to cover existing & new tariff systems (Products) Compliance with data protection & financial services laws Multi-application customer media Page 7

8 SCOPE IFMS Part 1: Architecture Provide the basis for multi-operator/multiservice Interoperable Public Transport Fare Management Systems (IFMS) on a national and international level To define a reference functional architecture To identify the requirements that are relevant to ensure interoperability between several actors in the context of the use of electronic tickets To extend existing international standards to describe ticketing requirements Page 8

9 FUNCTIONS IFMS Part 1: Architecture The IFM system includes the following functions involved in the fare management process: Management of s Management of Products Security management Certification, Registration & Identification Page 9

10 THE IFM STANDARD IFMS Part 1: Architecture Identification of different functional entities in relation to the overall fare management system Definition of a generic model describing the logical & functional architecture Use cases describing interactions & data flows between different functional entities Description of security requirements Page 10

11 IFM MODEL CONTENTS IFMS Part 1: Architecture Crucial terms in the IFM standard Product Roles IFM Manager Registrar Security Manager Owner & Retailer Product Owner & Retailer Service Operator Customer Customer Service (Optional) Collection & Forwarding Page 11

12 IFM APPLICATION? IFMS Part 1: Architecture A container placed on a Customer media for 1 or more products Description of Functions File structure on the Customer media Data elements Security Architecture Product no. 1 Product no. 2 Product no. n No. 1 Customer media No. 2 No. n Page 12

13 IFM PRODUCT & PRODUCT TERMS IFMS Part 1: Architecture Product Rules Usage rules Pricing rules Commercial rules Product Specification Functions Data elements Security scheme Product Instance of a Product template on the Customer media Unique ID Product Template Technical master for the Product to be installed on the Customer media Page 13

14 PRODUCT RULES IFMS Part 1: Architecture Usage rules Describes when the service may be used Describes the area/route where the service may be used Describes Customer profile Type of service Etc. Pricing rules Describes the price for a service given certain conditions Describes the payment conditions Etc. Commercial rules Describes clearing & apportionment rules Describes commissions Etc. Page 14

15 IFM MANAGER IFMS Part 1: Architecture IFM System IFM Manager appoints establishes & manages is built on A Set of IFM Rules Technical requirements Commercial requirements Security requirements Legal requirements Any other IFM requirements IFM Registrar Issuing unique identities IFM Security Manager Certification Auditing and monitoring Security key management Page 15

16 APPLICATION OWNER & RETAILER IFMS Part 1: Architecture holds the application contract with Customer Retailer(s) installs holds appoints & authorizes Customer media Owner owns & specifies No. 1 No. 2 No. n Page 16

17 PRODUCT OWNER & RETAILER IFMS Part 1: Architecture sells the product to collects the payment from Customer Product Retailer(s) installs holds appoints & authorizes Customer media Product no. 1 Product Owner owns & specify (make Product Rules) Product no. 2 Product no. n No. 1 No. 2 No. n Page 17

18 SERVICE OPERATOR IFMS Part 1: Architecture Customer holds Provides transport service Customer media Product no. 1 Service Operator accepts product as proof of travel rights Product no. 2 Product no. n No. 1 No. 2 No. n Page 18

19 COLLECTION & FORWARDING IFMS Part 1: Architecture To facilitate data interchanges Owner Security Manager Product Owner Collection & Forwarding Registrar Product Retailer Service Operator Retailer Page 19

20 THE IFM MODEL IFMS Part 1: Architecture Owner Product Owner Retailer Product Retailer Customer Service Collection & Forwarding Security Manager Registrar IFM Manager Customer Service Operator Page 20

21 USE CASES DESCRIPTION IFMS Part 1: Architecture Use Cases describe a toolbox for the implementation of IFM systems 32 separate Use Cases cover the following areas Certification Registration Management of Management of Product Security Management Customer Service Management (Optional) Page 21

22 IDENTIFICATION IFMS Part 1: Architecture ID s are needed for Security (enabling of authentication, message integrity, security lists) Communication (addressing of entities in the network) Auditing (enable auditing e.g. tracking transactions) Who has to be identified? Actors (Organizations) Templates & s Product Templates & s Components (e.g. SAMs) There is only one Registrar function Page 22

23 GENERAL SECURITY REQUIREMENTS IFMS Part 1: Architecture Information Not available or disclosed without authorization Not be altered or destroyed without authorization ID of subject or resource shall be authenticated Protection against an entity s false denial Each message shall be unique Accordance with IFM security policy Security key management Security list management Page 23

24 IFMS PART 2 Recommended Business Practice for Set of Rules Why IFMS Part 2? Aims to provide a tool which gives a clear & unambiguous picture of Part 1 and its relationship with related systems. Such as other IFMS, mobile & financial systems What is IFMS Part 2? It is a Technical Report (White Paper) To illustrate how the tool effectively works, the process is explained where the core part of Set of Rules is expanded into a whole Set of Rules Recommended business practices in a real environment for system compliant with ISO are listed, which provide some of the best practices in the world Page 24

25 MULTI-APPLICATION ENVIRONMENT New Stakeholders & Procedure for App. Download Media Management IFM Management Media Owner Owner Media Security Manager Media Retailer Retailer Product Owner IFM Security Manager Media Registrar Product Retailer C&F IFM Registrar Specific process description is needed Customer (Media) Operator Page 25

26 MULTI-APPLICATION ENVIRONMENT New Stakeholders Media Owner: Defines customer media rules Management of applications on Media Media Rules: Rules on how applications can be downloaded Security requirements Authentication procedures Media Specification: Functions, Data elements & Security scheme Media: Houses application Provides authentication Identified by Unique Identifier Page 26

27 MULTI-APPLICATION ENVIRONMENT Sequence Diagram for Download of s Media Owner Media SM Media IFM SM App Retailer App Owner Mutual Contract Media Certifiction Certification App Download request Mutual Authentication Template Install ID Acknowledge Security feature request Security features Security features Personalisation Page 27

28 MULTI-APPLICATION ENVIRONMENT Sequence Diagram for Download of s Prerequisites Mutual certification guarantees that Media fulfills specific set of rules and IFM fulfills the specific set of rules of the media owner Procedures for mutual authentication between Media and App. Retailer are essential for a secure application download Implementation/download of security features requires that security features can be created on demand and distributed via an online communication Page 28

29 ROLE MODEL IN A MULTI-APP. ENVIRONMENT IFM Model As Is Page 29

30 ROLE MODEL IN A MULTI-APP. ENVIRONMENT IFM Model as Seen By End Users IFM IFM Collection & Forwarding functions Security Manager Registrar Owner Owner Ticketing Product Product Owner Owners Fare responsibility Retailers Retailer Product Product Retailers Retailer Transport Operator Service Operators Customer care Subscribes Buys Products Consumes Products Transport Customer care End user Page 30

31 Media management and loading processes ROLE MODEL IN A MULTI-APP. ENVIRONMENT Adding a Multi-application Media Security Manager? Registrar? IFM IFM IFM IFM Collection & Forwarding functions Security Manager Registrar Medium owner Owner Owner Ticketing Product Product Owner Owners Fare responsibility Medium Retailer Retailers Retailer Product Product Retailers Retailer Transport Operator Service Operators media Customer care Subscribes or buys ONE media Customer care Subscribes s From IFMs Buys Products Consumes products Transport Customer care End user Page 31

32 USE CASE FOR NFC MOBILE PHONES Framework for GSMA Mobile Ticketing in France Mobile Phone manufacturers SIM manufacturers SIM & Mobile Phones Validation Manager SIM Owners Mobile Network Mobile Operators Network Operators IFM IFM IFM IFM Collection & Forwarding functions Owner Owner Ticketing Product Product Owners Owner Security Manager Registrar Fare responsibility Mobile Phone Retailers SIM Retailers Secure element 4 SIM Manager Retailers Retailer Product Product Retailers Retailer Transport Operator Service Operators OTA App. Product remote mgmt NFC Mobile Set Customer care Buys Mobile set Mobile network Customer care Customer care Holds media Subscribes Mobile network Subscribes s Buys Products consumes products Transport Customer care Page 32

33 USE CASE FOR NFC MOBILE PHONES Framework for GSMA Mobile Ticketing in France Telecom World 1. Gets an NFC mobile set from Mobile Phone Retailer 2. Subscribes mobile ticketing service from Mobile Network Operators (MNO) through SIM Retailer SIM Retailer provides the SIM card Telecom and Transport 3. Subscribes from Retailer. is downloaded OTA, allowing MNO to manage the media Transport World 4. Buys Product from Product Retailer (OTA or NFC) 5. Consumes Products from Service Operators (NFC) Customer can use any method to subscribe an or buy a Product from Retailers (paper, POS, call centers, Internet ) Page 33

34 APTA NFC TRANSIT APPLICATION Conceptual Diagram Media Management IFM Management Media Owner Owner Media Security Manager Media Retailer Retailer Product Owner IFM Security Manager Media Registrar Product Retailer C&F IFM Registrar Specific process description is needed Customer (Media) Operator Page 34

35 NEXT STEPS U.S. Contribution to (ISO ) Public Transport IFMS Part 1: Architecture (ISO :2007) - Published Annex C: Reference to APTA UTFS/CFMS Standard Public Transport IFMS Part 2: Recommended Business Practice for Set of Rules (ISO/PDTR ) - In Progress Section 7 - Business Practices as examples; Subsection Mobile Telecom APTA System Architecture for Mobile NFC in Transit Page 35

36 REFERENCES Used in this Presentation Public Transport IFMS Part 1: Architecture (ISO :2007) ISO Publication Draft Public Transport IFMS Part 2: Recommended Business Practice for Set of Rules (ISO/PDTR ) ISO Document Ideas for the multi-application environment New stakeholders and procedure for the application download Berthold Radermacher, Association of German Transport Undertakings, VDV, Germany Role model in a multi-application environment Gilles de Chanterac, AFNOR, France Page 36

37 THANK YOU!!! Chung-Chung Tam U.S. Expert, ISO TC204 WG8 Chicago Transit Authority 901 W. Division Street Chicago, IL Office: (312) Martin P. Schroeder Chair, ISO TC204 WAG8 American Public Transportation Association 1666 K St. NW Washington, DC Office: (202) mschroeder@apta.com Page 37