Contactless Fare Media System Standard Part 2: Contactless Fare Media Data Format and Interface...

Contactless Fare Media Contactless Fare Media System StandardSystem Standard

Part 2: Contactless Fare Part 2: Contactless Fare Media Data Format and Media Data Format and

Interface StandardInterface Standard

Tomas Oliva

Using Standards to Make Using Standards to Make ““Smart” ChoicesSmart” Choices

Talking Technology and Transportation (T3)Talking Technology and Transportation (T3)May 17, 2006May 17, 2006

T3 Webinar May 17, 2006 Using Standards to Make` “Smart” Choices

American PublicAmerican PublicTransportation Transportation AssociationAssociation

UTFS Elements of UTFS Elements of StandardizationStandardization

REGIONAL CENTRAL SYSTEM

AGENCY CENTRAL SYSTEM

DEVICE(CID)

PICC(Smart Card)

DEPOT/STATION COMPUTER

PART 3 – Regional Central System

Interface SpecificationPART 4 – System Security

Planning and Implementatio

n Guideline

PART 2 – Contactless Fare Media Data

Format and Interface Standard



General Scope of the General Scope of the Part 2 StandardPart 2 Standard

Applies to contactless card-based fare Applies to contactless card-based fare collection systemscollection systems

Requires a Proximity Integrated Circuit Requires a Proximity Integrated Circuit Card (PICC) with a Card Operating System, Card (PICC) with a Card Operating System, compliant with ISO/IEC14443:2-4, with a compliant with ISO/IEC14443:2-4, with a minimum of 2KB of useable memoryminimum of 2KB of useable memory

Provides a specification for components of Provides a specification for components of the data architecture to be used on the the data architecture to be used on the cardcard

Uses existing standards and common Uses existing standards and common practices where possiblepractices where possible



General Purpose of the General Purpose of the Part 2 StandardPart 2 Standard

Define a common set of data objects that Define a common set of data objects that enable compliant PICCs and Card Interface enable compliant PICCs and Card Interface Devices (CID) to be used interchangeably Devices (CID) to be used interchangeably with each other within a systemwith each other within a system

Enable multiple transit agencies within a Enable multiple transit agencies within a region to accept each others fare mediaregion to accept each others fare media

Provide a set of data objects and associated Provide a set of data objects and associated software logic that, once developed, can be software logic that, once developed, can be applied to other projects/systemsapplied to other projects/systems



Objectives of the Objectives of the Part 2 StandardPart 2 Standard

Accommodate most known fare Accommodate most known fare products and related services products and related services currently used in the UScurrently used in the US

Base card data components on Base card data components on open standards to enable open open standards to enable open sourcing from multiple vendorssourcing from multiple vendors

Ensure that new interface device Ensure that new interface device technologies can be adopted within technologies can be adopted within the core application infrastructurethe core application infrastructure



Advantages of AdoptionAdvantages of Adoption

InteroperabilityInteroperability Transit agencies can accept other agencies Transit agencies can accept other agencies

smart cards.smart cards. Agency systems can be procured at Agency systems can be procured at

different times.different times. Reduced CostReduced Cost

Reduced need for customization and Reduced need for customization and re-engineering.re-engineering.

Transit agencies can purchase equipment Transit agencies can purchase equipment from multiple vendors (competitive from multiple vendors (competitive procurement).procurement).

Potential to share costs through common Potential to share costs through common operations.operations.



Use of the Part 2 Use of the Part 2 StandardStandard

The Standard is not sufficient to build a The Standard is not sufficient to build a functioning system or to achieve functioning system or to achieve interoperability; interoperability; for example, agencies for example, agencies must also define:must also define:

PICC file structurePICC file structure (Standard provides an example (Standard provides an example only)only)

PICC data definition mappingPICC data definition mapping (need to make (need to make choices)choices)

List of fare products that will be accepted and List of fare products that will be accepted and processed by the systemprocessed by the system

Security is outside the scope of the Security is outside the scope of the Standard, although the data architecture Standard, although the data architecture does provide for the implementation of does provide for the implementation of security schemes. security schemes.



Mechanism for Adoption & Mechanism for Adoption & UseUse

Achieve consensus for UTFS adoption Achieve consensus for UTFS adoption among participating agencies.among participating agencies.

Define business rules for regional Define business rules for regional program participation (including program participation (including ownership, governance, regional fare ownership, governance, regional fare products, fee and revenue sharing).products, fee and revenue sharing).

Identify distinct messages and Identify distinct messages and implementation approach to be used implementation approach to be used within the region.within the region.



Key Terms in the Key Terms in the StandardsStandards

Following from ISO standards:Following from ISO standards: PICC: PICC: Proximity Integrated Circuit Proximity Integrated Circuit

CardCard

PCD: Proximity Coupling Device PCD: Proximity Coupling Device

CID: Card Interface DeviceCID: Card Interface Device



Card-Reader Transaction Card-Reader Transaction OverviewOverview

Initiatecommunication

with PICC

Determine ifPICC is valid

Identify PICCholder type

Identify what’son the PICC

Recordtransaction on

PICC

Carry outtransaction



General DescriptionGeneral Description

The basic data architecture is built The basic data architecture is built on a set ofon a set of objects made up ofobjects made up of a a defined set of elements.defined set of elements.

Each core object is 16 bytes in Each core object is 16 bytes in length.length.

Standard makes provisions for Standard makes provisions for additional data through extensions additional data through extensions to the core objects, which are also to the core objects, which are also no longer that 16 bytes.no longer that 16 bytes.



Object Definition FormatObject Definition Format

Objects are defined in a consistent Objects are defined in a consistent format to assist in interpretation.format to assist in interpretation.

Each object is specified in its own section Each object is specified in its own section of the standard.of the standard.

Object specification: Object specification: Includes a summary explanation of the object’s Includes a summary explanation of the object’s

function, and a table listing the elements that are function, and a table listing the elements that are part of the object, along with heir size, potential part of the object, along with heir size, potential values, position, and a description. values, position, and a description.

Concludes with a user’s information subsection Concludes with a user’s information subsection that provides additional details about the elements that provides additional details about the elements that are part of the object.that are part of the object.



Core ObjectsCore Objects

DirectoryIndex Object

ProductIndex Objects

Add/DeductValue History

Objects(Optional)

PICC HolderProfile Object

TransactionHistoryObjects

TransitApplication

Profile Object

FareProducts



Directory Index Object Directory Index Object (DIO)(DIO)

• Contains pointers that identify the location Contains pointers that identify the location (file) in which most other data objects are (file) in which most other data objects are storedstored

• For each file, provides:For each file, provides:• ID of the fileID of the file• Size of the fileSize of the file• Type of fileType of file• Ownership (if applicable) of the fileOwnership (if applicable) of the file

• A card normally contains only one DIOA card normally contains only one DIO• Enables AFC system to quickly locate other Enables AFC system to quickly locate other

data objects, while enabling the contents of data objects, while enabling the contents of data files to be flexible and dynamicdata files to be flexible and dynamic



Transit Application Profile Transit Application Profile Object (TAPO)Object (TAPO)

The TAPO is a required core object that The TAPO is a required core object that identifies the PICC’s origin, issuer,identifies the PICC’s origin, issuer, and and general capabilities/limitations required general capabilities/limitations required by the transit application.by the transit application.

The TAPO is encoded or configured at the The TAPO is encoded or configured at the PICC pre-issuance stage or the PICC PICC pre-issuance stage or the PICC initialization stage.initialization stage.

The PICC contains only one TAPO.The PICC contains only one TAPO.

Sample elements:Sample elements: Country ID, Region ID, Country ID, Region ID, Issuer ID, Transit application expiry date, Issuer ID, Transit application expiry date, PICC Manufacturer ID, Issuing CID IDPICC Manufacturer ID, Issuing CID ID



PICC Holder Profile PICC Holder Profile Objects (PHPO)Objects (PHPO)

The PHPO identifies the transit patron’s The PHPO identifies the transit patron’s profile relative to their personal preferences profile relative to their personal preferences for transit fare products and servicesfor transit fare products and services

The PICC contains only one PHPO. The PICC contains only one PHPO. An optional PHPO extension must be utilized An optional PHPO extension must be utilized

for secret or private profile protection.for secret or private profile protection.

Sample elements:Sample elements: Fare class code, birth date of Fare class code, birth date of patron, language preference, start and end of patron, language preference, start and end of profile, and associated discountprofile, and associated discount



Add/Deduct Value History Add/Deduct Value History Objects (A&DVO)Objects (A&DVO)

The A&DVO will record up to eight of the The A&DVO will record up to eight of the most recent add or Autoload (Unload) value most recent add or Autoload (Unload) value transactions from the T-purse and/or stored transactions from the T-purse and/or stored value products.value products.

The A&DVO is an optional object, although The A&DVO is an optional object, although if used, at least 2 are required.if used, at least 2 are required.

Sample elements:Sample elements: Payment type (cash, credit, Payment type (cash, credit, recurring load, etc.), transaction date and recurring load, etc.), transaction date and time, value added or deducted, location time, value added or deducted, location where transaction took place.where transaction took place.



Transaction History Transaction History Objects (THO)Objects (THO)

The THO contains up to 16 of the most The THO contains up to 16 of the most recent transactions, after which the recent transactions, after which the oldest transaction is overwritten.oldest transaction is overwritten.

Allows for up to 16 transaction types to Allows for up to 16 transaction types to be defined.be defined.

The THO is a required core object.The THO is a required core object.

Sample elements:Sample elements: Fare product used, agency Fare product used, agency where PICC was used, is the transaction where PICC was used, is the transaction linked to the previous transaction (i.e. linked to the previous transaction (i.e. transfer rules), transaction value. transfer rules), transaction value.



Transaction TypesTransaction Types

0 = Reserved 0 = Reserved

1 = Load1 = Load

2 = Product Blocked 2 = Product Blocked

3 = Product Un-Blocked 3 = Product Un-Blocked

4 = Validation or 4 = Validation or DeductionDeduction

5 = Validation or 5 = Validation or Deduction Date and Deduction Date and Time Override Time Override

6 = Reserved6 = Reserved

7 = Configuration 7 = Configuration ChangeChange

8 = Previous 8 = Previous Transaction UndoneTransaction Undone



11 = Negative List 11 = Negative List Status ChangeStatus Change

12 = Unload12 = Unload



15 = Out of Region T-15 = Out of Region T-Purse UsePurse Use



Product Index Object Product Index Object (PIO)(PIO)

A mandatory index of the transit fare products A mandatory index of the transit fare products (defined by Product Objects) on a specific PICC (defined by Product Objects) on a specific PICC application.application.

Provides summary details of the transit fare Provides summary details of the transit fare products currently stored on the PICC.products currently stored on the PICC.

Enables AFC system to quickly identify Enables AFC system to quickly identify products that might be applied to the current products that might be applied to the current fare payment.fare payment.

PICC contains only one PIO and one PIO PICC contains only one PIO and one PIO extension but can have two additional extension but can have two additional extensions, if required.extensions, if required.

Sample elements:Sample elements: PICC transaction sequence number PICC transaction sequence number (maximum of 127 transactions are tracked), fare (maximum of 127 transactions are tracked), fare product used in last transaction, product type product used in last transaction, product type codes.codes.



Available Product ObjectsAvailable Product Objects

The Standard accommodates any fare The Standard accommodates any fare products that are time-, prepaid ride/trip-, products that are time-, prepaid ride/trip-, value-, or reward-based, and those with linked value-, or reward-based, and those with linked (e.g. bankcard) accounts.(e.g. bankcard) accounts.

A given fare product is represented by a single A given fare product is represented by a single Product Object with or without object Product Object with or without object extensions. extensions.

There are 256 distinct Product Types available There are 256 distinct Product Types available to each Agency (253 pass types, one stored to each Agency (253 pass types, one stored value, one account linked and one AutoValue-value, one account linked and one AutoValue-based product).based product).

Each Agency defines the Fare Product Type Each Agency defines the Fare Product Type Codes, and the rules for use of those products.Codes, and the rules for use of those products.



Pass and Transfer Product Pass and Transfer Product Objects (P&TPO)Objects (P&TPO)

Contains the required information or Contains the required information or functionality and data representing functionality and data representing either a pass or transfer product.either a pass or transfer product.

P&TPO is a core object required by the P&TPO is a core object required by the standard.standard.

Sample elements:Sample elements: Whether the user has Whether the user has subscribed to Autoload, pass or transfer subscribed to Autoload, pass or transfer expiry date and time, number of remaining expiry date and time, number of remaining trips or rides, where the product is valid trips or rides, where the product is valid (i.e., specific zone)(i.e., specific zone)



Stored Value and T-Purse Stored Value and T-Purse Product Objects Product Objects

(SV&TPPO)(SV&TPPO) Stored value objects are agency-specific.Stored value objects are agency-specific. The T-Purse is the regional stored value fare The T-Purse is the regional stored value fare

product, usually stored in local currency product, usually stored in local currency ($US).($US).

When the PICC is initialized, SV&TPPO are When the PICC is initialized, SV&TPPO are usually set at 0.usually set at 0.

Autoload feature can be enabled.Autoload feature can be enabled. There can only be one instance of a T-Purse There can only be one instance of a T-Purse

on a PICC.on a PICC.

Sample elements:Sample elements: Frequency of autoload, Frequency of autoload, autoload threshold (trigger), autoload amountautoload threshold (trigger), autoload amount



Account Linked Product Account Linked Product Object (ALPO)Object (ALPO)

Used to define a fare product that is tied Used to define a fare product that is tied (“linked”) to a host-based account, such as a (“linked”) to a host-based account, such as a credit or debit cardcredit or debit card

Acts like a T-Purse product, except does not Acts like a T-Purse product, except does not require pre-fundingrequire pre-funding

There can be only one instance of an Account There can be only one instance of an Account Linked product on a PICCLinked product on a PICC

Sample elements:Sample elements: Accumulated value used in a Accumulated value used in a particular day, definition of time period for which particular day, definition of time period for which a transaction limit applies, time period start, a transaction limit applies, time period start, number of transactions performed during time number of transactions performed during time limit.limit.



Account Linked Reference Account Linked Reference Object (ALRO)Object (ALRO)

The ALRO is an object containing the The ALRO is an object containing the Account Linked Product reference Account Linked Product reference information (e.g., bankcard number) that information (e.g., bankcard number) that requires secure access. requires secure access.

The ALRO object must occupy a dedicated The ALRO object must occupy a dedicated file on the PICC with a separate security file on the PICC with a separate security write key.write key.

Sample elements:Sample elements: Daily limit of payments that Daily limit of payments that can be performed “on account”, bankcard can be performed “on account”, bankcard information from which payment is made, information from which payment is made, bankcard expiry date. bankcard expiry date.



Autovalue Product Object Autovalue Product Object (APO)(APO)

Implemented when an agency or Implemented when an agency or regional operator wants to provide regional operator wants to provide incentives (rewards) for frequent use incentives (rewards) for frequent use or bulk fare purchases.or bulk fare purchases.

Sample elements: Type of autovalue Sample elements: Type of autovalue product, accumulation of value units product, accumulation of value units today, accumulation of value units this today, accumulation of value units this week, last week, 2 weeks ago, and 3 week, last week, 2 weeks ago, and 3 weeks ago. weeks ago.



Evolution of the StandardEvolution of the Standard

Add provision for use of PICC Add provision for use of PICC products that don’t meet all of the products that don’t meet all of the requirements (Limited Use PICCs)requirements (Limited Use PICCs)

Develop an Implementation GuideDevelop an Implementation Guide

Develop Certification and Testing Develop Certification and Testing requirementsrequirements



Review PointsReview Points

Comprehensive description of objects and Comprehensive description of objects and their elements accommodating a broad range their elements accommodating a broad range of fare collection related transactions.of fare collection related transactions.

Users have significant flexibility in selecting Users have significant flexibility in selecting how to use the objects.how to use the objects.

While the Standard does provide PICC While the Standard does provide PICC specifications, the focus is on data formats specifications, the focus is on data formats and a standardized communication protocol and a standardized communication protocol with the CID. This opens up future with the CID. This opens up future possibilities for the implementation of other possibilities for the implementation of other electronic form factors such as key fobs, electronic form factors such as key fobs, mobile telephones fitted with contactless mobile telephones fitted with contactless chips, etc.chips, etc.



More InformationMore Information

Martin Schroeder, Martin Schroeder, P.E., APTAP.E., APTA

mschroedermschroeder@@aptaapta.com.com

202-496-4885202-496-4885

Contactless Fare Media System Standard Part 2: Contactless Fare Media Data Format and Interface...

Documents

Transcript of Contactless Fare Media System Standard Part 2: Contactless Fare Media Data Format and Interface...