Skip to main content

Smartcard Interoperability Issues for the Transit Industry (2006) / Chapter Skim
Currently Skimming:


Pages 51-68

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 51...
... , or by an individual organization such as the American Public Transportation Association (APTA) or Europay, Mastercard, or Visa (EMV)
Read the entire page →
From page 52...
... The interoperability of fare media requires the exchange of information in the following areas: • Fare media communication protocol and • Application communication protocol 52 Smartcard Interoperability Issues for the Transit Industry
Read the entire page →
From page 53...
... • CEN Workshop Agreement (CWA) 13987 addresses user-related information for interoperable citizen services within smart card systems EMV 2000 Integrated Circuit Specification for Payment Systems, Version 4.0 EMV 2000 is an integrated circuit specification that ensures single terminal and card approval processes are developed at a level that will allow cross payment system interoperability through compliance with the "EMV" specifications (Europay Mastercard Visa Integrated Chip Card Standard)
Read the entire page →
From page 54...
... The RKF Travel Card Technical Requirement Specification identifies requirements for selected IC-card technologies for the RKF travel card. WMATA Washington, DC SmarTrip Regional Customer Service Center Contract Book and Draft SmarTrip Interoperability Regional Specification The Washington Metropolitan Area Transit Authority (WMATA)
Read the entire page →
From page 55...
... is an initiative developed by the European Commission to further the development of smart cards across Europe and promote the following objectives: • Interoperability • Multi-application cards • Secure transactions • User acceptance • Accessibility National Institute of Science and Technology (NIST) Government SmartCard Interoperability Specification, Version 2.1 Smart Card Alliance Transit and Retail Payment: Opportunities for Collaboration and Convergence Report 10–Fare Policies, Structures, and Technologies Transit Cooperative Research Program (TCRP)
Read the entire page →
From page 56...
... • Part 4: Transmission Protocol-Defines the communication protocol and framing for data exchange. Because of its transparency, it can encapsulate any application command, which permits a variety of functionality and flexibility.
Read the entire page →
From page 57...
... • UPDATE RECORD -- Modifies existing data within a record-based (non-transparent-based) file on the smartcard.
Read the entire page →
From page 58...
... 1.0 NA NA NA NA NA NA NA NA NA NA RKF v. 2.0 CardValidityEndDate Country ID ApplicationIssuerID CardProvider Base data type of MACKeyID MACKeyIdentifier ManufacturerData CardSerialNumber Base data type of BirthDate Base data type of StartDate Base data type of EndDate Base data type of LanguageID DialoguePreferences NA NA NA NA NA EntitlementType PassengerType Deposit UserData Table 13.
Read the entire page →
From page 59...
... 1.0 ITSO v. 1.2 Stored Value Information AutoSubscribe ValueExpires RemValueSign RemValue ExpRecurDate RecurringAutoloadType AutoThreshold SVThreshloadLoadAmount SVRecurringLoadAmount CurrencyCode CIDTransactionNumber Number CIDID DeviceID Base data type of SerialNumbers Device Pass/Transfer Information AutoloadSubscribed PaymentType LocationEncodingType RemTripRidesTransfers ExpDate EndDate Base data type of EndTime Base data type of Base data type of DateTime ExpTime DateTime RenewedInAdvance AutoThreshold ProdID LocationEncoding CIDTransactionNumber Number CIDID DeviceID Base data type of SerialNumbers Device ValueATPAFlags EndDate NA NA NA NA NA NA Threshold TopUpAmount NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA PlaceNA DeviceTransactionNA NA ThresholdAmount NA AuthorizedProduct ContractSerial Number NA NA Balance Base data type of Base data type of NA Date Value AutoloadLoad Status NA AutoloadValue NA AutoloadValue NA CurencyUnit NA Device Transaction EndDate CEN v.
Read the entire page →
From page 60...
... 1.0 RKF v. 2.0 Add Value History Information LoadType NA NA ValueExpires NA NA AgencyID ProductOwner NA Date Date Time Base datatype of DateTime Time DataTimeStamp NA Base datatype of DateTime RecurringAutoloadType NA NA SVTransaction NA NA SVTransactionNegative NA NA RegionID NA NA LocationID LocationData Place CIDTransactionNumber ReceiptFlag TransactionNumber CIDID SAMID SAMID Base datatype of DeviceID Base datatype of SerialNumbers Device Transaction History Information TransactionType TransactionType TransactionType NA NA In_Out NA NA ProdID_or_RegionID ProductID ContractSerialNumber AgencyID ServiceOperator Basetype of CardProvider LocationID LocationData Place DateStamp DateTimeStamp Date Base datatype of DateTime TimeStamp DateTimeStamp Time Base datatype of DateTime TransactionLinked NA NA TransferStartTime NA NA NA NA NA Time Base datatype of DateTime TransValue FareDeducted MoneyAmount TransValueSign NA NA TransferCode NA NA Special NA NA ValueAPTAFlags Value EndDate IssuerID DateTimeStamp NA NA NA NA NA NA TransactionSequenceNumber ActualAmount
Read the entire page →
From page 61...
... ProfileStartDate Provides the date this profile becomes valid for use (Format ddmmyy) ProfileExpireDated Provides the expiration date of this customer profile and associated discount if applicable (Format ddmmyy)
Read the entire page →
From page 62...
... ProfileStartDate Provides the date this profile becomes valid for use (Format ddmmyy) ProfileExpireDate Provides the expiration date of this customer profile and associated discount if applicable (Format ddmmyy)
Read the entire page →
From page 63...
... The currency code is considered fixed and permanent where indicated and consistent for all regions that recognize and adhere to this transit smart PICC Regional Interoperability Standard. The fare collection system conforming to these specifications will recognize the defined currency and deduct the equivalent of that currency from the T-purse CIDTransactionNumber Represents the LSB of the Event Identifier assigned by the issuing machine's CID CIDID Represents the issuing machine CIDID, used to identify the encoding equipment AutoSubscribe Represents the autoload subscription indicator for this load ValueExpires Indicates that this is a Single Load SV product that expires on the date indicated by ExpRecurDate RemValueSign Value designates a positive or negative balance RemValue Provides remaining currency value ExpRecurDate Provides the date that this product expires or last recurring load date (Format ddmmyy)
Read the entire page →
From page 64...
... These codes are not fixed and permanent and can be changed by the owning transit agency within the region via tables/fare rules. The code is captured by the faregate reader and used for accounting, demographic reporting, and other downstream fare collection system processing LocationEncoding Represents the valid locations indicator CIDTransactionNumber Represents the LSB of Event Identifier assigned by the issuing machine's CID CIDID Indicates the issuing machine CIDID used to identify the Encoding equipment LoadType Represents the payment type code.
Read the entire page →
From page 65...
... . Add Value History Info Field Description CIDTransactionNumber Represents the LSB of the event identifier assigned by the issuing machine's CID CIDID Represents the issuing machine CIDID used to identify the encoding equipment TransactionType Denotes the type of transaction In/Out Indicates in or out of "paid area" for closed systems ProdID Or RegionID Provides the product ID for in-region product use or region ID for out-of- region T-Purse use AgencyID Represents the service providing agency/agencies for the associated product LocationID Represents the unique location of the device within the regional system DateStamp Indicates the date of transaction (Format: ddmmyy)
Read the entire page →
From page 66...
... 66 Smartcard Interoperability Issues for the Transit Industry Fraud Theft Virus Attack Accidental Damage Sabotage Communications Failure Wiretapping Insertion of Data Emanations Interception Operating System Alteration Software Failure Hardware Failure Strikes Privacy Violation Availability Confidentiality Integrity Dismissal Prison Competition Loss of Customer Insolvency Loss of Credibility Embarrassment Loss of Profit Data Figure 10. Data security breaches and impacts.
Read the entire page →
From page 67...
... • Authentication -- This is the process of ensuring the message received is the message sent and preventing message modification. • Non-repudiation -- This guarantees that the message sender cannot deny having sent the message.
Read the entire page →
From page 68...
... Interoperability is accomplished through proprietary solutions at the application and security layers. Proprietary elements are embedded even into data elements governed by standards.
Read the entire page →

Key Terms

  • travel card
  • communication protocol
  • transit cooperative
  • base data
  • rkf travel

  • data type
  • format ddmmyy
  • smart cards
  • global platform
  • issuing machine

  • expiration date
  • event identifier
  • field description
  • minutes past
  • machine cidid

  • picc holder
  • cid cidid
  • past midnight
  • identifier assigned
  • cidtransactionnumber represents

  • transit authority
  • transportation association
  • application data
  • government data
  • interoperability regional

  • data standards
  • smartrip regional
  • cen workshop
  • ensure interoperability
  • circuit specification


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.