Smartcard Interoperability Issues for the Transit Industry (2006) / Chapter Skim
Currently Skimming:
Pages 79-86
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 79... ...
Given that both of these readers use proprietary APIs from their respective manufacturers, the development of conversion layer software was required in order for the readers to work with the AFC simulator. The conversion layer was designed to convert the proprietary reader API functions to the standard API functions, allowing the AFC simulator to function with smartcards that are compatible with the ASK LDB 215 reader and the OTI Saturn 5000 reader.
|
From page 80... ...
The module that is loaded is the conversion layer with the standard API functions embedded so that the simulator application can make the same function calls, regardless of which reader has been selected. Exhibit 2 is a code segment that loads the standard smartcard reader API functions from the conversion layer software.
|
From page 81... ...
Exhibit 3. Standard API compared to proprietary API.
|
From page 82... ...
Table 18 shows the transaction times of fare tickets with AFC simulator using 7816-4 commands within projected execution time. 82 Smart Card Interoperability Issues for the Transit Industry Activity DESFire with ASK LDB 215 DESFire with OTI Saturn 5k UltraLight with ASK LDB 215 UltraLight with OTI Saturn 5k Select App 47 ms*
|
From page 83... ...
The Philips Mifare UltraLight COS supports a memory block architecture to store the data. The fare ticket's data structure is implemented as a block, and can be configured to be irreversible when the card is issued from the AFC simulator.
|
From page 84... ...
In the AFC simulator, the irreversible data setting was disabled to limit the consumption of UltraLight cards during demonstration. Figure 17 shows the simulator program flow.
|
From page 85... ...
Findings of Proof of Concept Using Standard API 85 Authenticate the Security Key (Triple DES) Check Agency Read data Update data Write transaction history Fail Success Agency's ticket declined Agency's ticket accepted Exit Figure 18.
|
From page 86... ...
Analysis of more contactless smartcard readers is needed to develop a broader and more scalable standard API. 86 Smart Card Interoperability Issues for the Transit Industry GUI Application (EXE)
|
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.