Cipurse V2 Mobile guidelines address new form factors
The new guidelines enable transit operators to enhance their systems to support mobile ticketing with new form factors. “Transit tickets are already one of the most frequently used contactless card applications in the world, and now as people are looking to their NFC phones to replace their physical payment cards, it is only natural that transit fare systems should go mobile, too,” said Laurent Cremer, executive director for the OSPT Alliance. “With the release of these new mobile guidelines, the OSPT Alliance continues to fulfil the promise of the CIPURSE standard to provide a single, consistent set of specifications for all the security, personalization, administration and life-cycle management functions needed to create a broad range of interoperable transit applications, from low to high end and across all form factors.”
Just as with other mobile applications, the CIPURSE application is personalized and installed over the air (OTA) by a trusted service manager (TSM) into a mobile device’s secure element (SE). Transit operators are free to deploy their own branded mobile app – essentially the user interface component – for Android, iOS, Windows, BlackBerry or any other platform, which interacts with the CIPURSE application to conduct transit transactions.
The guidelines define what the transport organization needs to do, define the role of the TSM, provide details on handling lost or stolen phones, detail how to purchase tickets online for the mobile phone and how to purchase tickets directly using the phone, present battery-off and battery-low considerations and much more.
The guidelines lay out the requirements for certification, and are completely form factor and operating system independent, providing implementation guidelines for hosting the CIPURSE application in embedded secure elements (eSE), as well as in SIM-UICC and microSD card-based secure elements. Especially developed for the NFC mobile industry, the guidelines provide numerous use cases that detail the interactions between end users, transport organizations, secure element owners, TSMs and other ecosystem partners in the day-to-day environment to provide a clear understanding of how the CIPURSE standard should be implemented for mobile applications. The guidelines also detail what kinds of application programming interfaces (APIs) need to be developed and which other specifications are required, such as GlobalPlatform 2.2.1.
The open and secure CIPURSE V2 standard is designed as a layered, modular architecture with application-specific profiles to support a broad range of interoperable transit applications – from inexpensive single ride or daily paper tickets, to rechargeable fixed-count or weekly plastic tickets, to longer-term smart card or smart phone-based commuter tickets that may also support loyalty or other applications.
Download the CIPURSE Mobile Guidelines from the OSPT web site at www.osptalliance.org
If you enjoyed this article, you will like the following ones: don't miss them by subscribing to :
