CIPURSE V2 open standard specification released

New Products |
By eeNews Europe

Designed with a layered, modular architecture with application-specific profiles, the open and secure CIPURSE V2 standard comprises 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 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.

“Today, transit operators wanting to offer new fare collection options, like the use of mobile phones, must choose from disparate product offerings that often don’t work together, increase the complexity of their fare collection systems and are quite costly because of the limited competition among vendors,” explained Laurent Cremer, executive director for the OSPT Alliance. “With the new modular, device-agnostic design of CIPURSE V2, it is now possible for vendors to develop families of interoperable products from low- to high-end based on a single specification, enabling transit operators to easily mix and match applications as their needs change over time.”

For integrators, CIPURSE V2 means lower development costs and faster time to market because they can apply a single set of standards for all of their products, from low to high end. For transit operators, CIPURSE V2 offers the potential for greater choice among a larger ecosystem of vendors with lower costs, greater flexibility in designing and implementing fare collection systems and the benefits of open standards like Java Card and GlobalPlatform. Unlike other solutions that require a restricted area on a SIM card, CIPURSE V2 can be implemented in a variety of ways with any existing device, including Java applets. Beyond the core set of functional specifications, CIPURSE V2 includes detailed specifications for administration, personalization and life cycle management, providing a consistent and interoperable method for implementing these functions across all profiles. With its modular “onion-layered” design, the CIPURSE standard can be easily enhanced in the future with additional functionality and new profiles created to address changes in technology and business.

Also available are documents detailing the CIPURSE cryptographic API for Java Card applications and secure access module and key management specifications. A set of three application-specific profiles – subsets of the CIPURSE V2 standard tailored for different use cases – have been defined which vendors are required to comply with when creating products targeting these applications:

CIPURSE T – Takes advantage of the new transaction mechanisms included in the specification to support the use of high-level, microprocessor-based transactions using smart cards, mobile phones and similar devices for more complex transit fare applications such as monthly or annual tickets, multi-system tickets and loyalty programs.

CIPURSE S – Supports tickets that can be recharged for a specific number or rides or weekly tickets and is essentially equivalent to and supplants the current CIPURSE 1.1 specification.

CIPURSE L – Created to support applications that use very inexpensive, disposable single-ride or daily tickets.

Products based on different profiles can be added to fare collection systems at any time and may be used in parallel to provide transit operators the greatest flexibility in offering riders a range of transit fare options. Because they are derived from the same set of specifications, all the profiles are interoperable, reflect the same design criteria and have the same appearance, enabling developers to create products according to a family concept.

The CIPURSE V2 documents can be downloaded for evaluation purposes at no cost from the OSPT Alliance website – – after first agreeing to a “click-through” evaluation license.


Linked Articles
eeNews Europe