Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Mobile-based NFC fare collection
Similar to Mobile-based NFC fare collection (20)
Recently uploaded
Recently uploaded (20)
Mobile-based NFC fare collection
- 1. MOBILE-BASED AUTOMATIC FARE COLLECTION Status and challenges for the future Ignacio Naveiras CICT-DTU student nnaveiras@gmail.com Center for Information and Communication Technologies 22/04/12 Technical University of Denmark
- 2. 0. Agenda 1. Mobile AFC in a context 2. Drivers 3. The Japanese paradigm 4. Trials in Europe: Hanau 5. Comparison and conclusions January 26, 2006 Mobile-Based Automatic Fare Collection 2
- 3. 1. Mobile AFC in a context... • Massive deployment of contactless SC technology for mass transit – Sony FeliCa in Asia/Pacific – ISO 14443 A (Philips Mifare) in Europe and USA – ISO 14443 B marginally – More than 150 million contactless transit card holders (Nokia) • Mobile transition – Replacing/complementing contactless cards – FeliCa/NFC technolgy in the devices January 26, 2006 Mobile-Based Automatic Fare Collection 3 – But still... Why on earth??
- 4. 1. Because... 1. Commuters usually carry their phones around 2. The phone can emulate a secure contactless SC Cellphone is a suitable access token!! • Besides, the mobile terminal may add value to the Mobile-Based Automatic Fare Collection January 26, 2006 transit service 4
- 5. 1. The Japanese paradigm • FeliCa transit cards with purse: JR-East Suica • Strong, controlling MNOs, high data traffic – launched Mobile FeliCa service – Mobile Suica in the chip from Jan. 2006 January 26, 2006 Mobile-Based Automatic Fare Collection 5
- 6. 1. Mobile Suica within Mobile FeliCa • Multi-application • Mobile Suica = + – Regular Suica Source: NTT DoCoMo – Visibility – Online services • By 2007: 15 mill. NTT, 5 mill. KDDI + Vodafone • Before Mobile Suica, 20-30% of owners registered for use January 26, 2006 Mobile-Based Automatic Fare Collection 6
- 7. 1. Trials in Mobile AFC: Hanau • RMV authority in Frankfurt area • get>>in SC system in Hanau – since 2002 – all buses equipped with CADs – CI/CO procedure as in Rejsekort • Nothing new under the get>>in NFC pilots – AFC, post paid, best price for sun... – Nokia 3220 with NFC shell – 6.000 users, aiming to expand P&T Source: RMV – seamlessly compatible with get>>in January 26, 2006 – Automatic Fare Collection Mobile-Based 200 commuters, 15 controllers 7
- 8. 1. Trials in Mobile AFC: Hanau • 3220 terminals with – NFC shell = NFC interface + SC controller SC emulation – MIDP 2.0 MIDlet • Delivery: – Initiation: pre-initiated 3220 shells – Personalization: contactlessly at sales points • Value-added features: Source: RMV – visibility of last CI/COs – loyalty card application Fare Collection January 26, 2006 Mobile-Based Automatic 8
- 9. 1. Any resemblances? get>>in Mobile Suica NFC pilot Platform ”open” closed multi-application mono-application Technology FeliCa NFC + secure chip Issuer/Manage NTT DoCoMo RMV r App. Provider JR East RMV Delivery OTA in the shell January 26, 2006 Mobile-Based Automatic Fare Collection 9 Added value strong Some
- 10. 5. The challenges ahead in mobile AFC • Technology is (almost) there • Delivery/issuance – initiation cumbersome in open mobile market – find a suitable role for the PTA – otherwise, impossible to start market launch • Basic functionality – replicate plastic SC • Added value – visibility + mobile services – compelling package... towards the mobile PTD January 26, 2006 Mobile-Based Automatic Fare Collection 10 – never detract from existing service value!
- 11. MOBILE-BASED AUTOMATIC FARE THANK YOU! COLLECTION the Status and challenges for future Ignacio Naveiras CICT-DTU student January 26, 2006 nnaveiras@gmail.com Mobile-Based Automatic Fare Collection 11
Editor's Notes
- NFC is a contactless communications standard which is compatible with FeliCa and ISO 14443 A (Mifare)
- Suitability as an access token is a sine-qua-non condition for migration. Maybe these arguments have not convinced you... Let me convince you through the study of two cases: Japan and Hanau.
- Start by noting relevant differences with Japan: lack of NFC platforms by
- Initiation: now, shells are delivered to the test subjects, in the future plans are to sell shells in Vodafone shops...
- Platform: Mobile Suica is a cless app in a restrictedly open multi-application platform. get>>in is a contactless application still without any hosting platform
- Technology is almost there: standard contactless HW, APIs... for interaction with existing deployed equipment. But...battery concerns. Delivery/Issuance: compare with SCs Terminal and susbcription markets are multiple, this does not suit public universal services. Comment Hanau with only one model of one vendor supported Role of the PTA should not go farther than being application provider Replicate functionality: do not flaw security or privacy or introduce new cumbersome operation or Added value: form factor not enough Visibility: balance, history of travels, but also static traffic info stored Mobile services: online traffic info, route planning, maybe combination with LBSs Compelling package: work for the creation of a package like Mobile FeliCa. For example a file exchange application for P2P. New services for the application or new applications interacting to ours. PTD: tool for other tasks than personal communication: payments, ... Never detract from existing value means do not spoil what already works, e.g. new need (for battery in a powerless environment)