Card interface for interfacing a host application program to data storage cards

• US 6,213,392 B1
• Filed: 05/27/1998
• Issued: 04/10/2001
• Est. Priority Date: 05/09/1995
• Status: Expired due to Term

• Current Assignee: COIN Acceptors Incorporated
• Original Assignee: Smartmove Incorporated
• Inventors: Zuppicich, Alan N.
• Primary Examiner(s): Frech, Karl D.
• Application Number:
  US08/945,626
• Time in Patent Office: 1,049 Days
• Field of Search: 235/380, 235/382.5, 235/382, 235/375, 235/487, 235/492, 340/825.31, 395/500
• US Class Current: 235/380
• CPC Class Codes: G06K 7/0004 Hybrid readers
• CPC Class Codes: G06K 7/0008 General problems related to the reading of electronic memory record carriers, independent of its reading method, e.g. power transfer
• CPC Class Codes: G06K 7/0013 by galvanic contacts, e.g. card connectors for ISO-7816 compliant smart cards or memory cards, e.g. SD card readers connectors in general H01R13/00; connectors for SIM cards used in mobile phones or the like H04B1/3816
• CPC Class Codes: G06K 7/10297 arrangements for handling protocols designed for non-contact record carriers such as RFIDs NFCs, e.g. ISO/IEC 14443 and 18092 cryptographic protocols H04L9/00; network security protocols H04L63/00; real-time communication protocols in data switching networks H04L65/00; network protocols for data switching network services H04L67/00
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system

Abstract

A card reader/writer which interfaces between a host application program and a data storage card. The card reader/writer reads from and writes to the application program with high level language of the commands. The card reader/writer translates the high level language commands of the host program to corresponding sequences of low level commands for reading and writing to the data storage card. The card reader/writer stores a plurality of sets of such low level commands, and is able to establish the card type for any card interfaced with the card reader/writer, and to use the appropriate command set for the established card type. The card reader/writer also translates low level commands from the card to high level commands for the host application program. The card reader/writer can be loaded with low level command sets for additional card types as required.

Claims

1. A card reader/writer which interfaces a host application program with a data storage card having an associated card application, characterised in that:

said card reader/writer can respond to said host application program using at least one designated high level language,

a plurality of lower level protocol sets are stored which correspond to a plurality of different data storage card applications,

said card reader is able to identify from the card the particular card application for any card interfaced to it for which it has a protocol set, and select from its store of protocols the appropriate lower level protocol for the identified card application,

said card reader/writer reads and translates high level language commands from the host program to corresponding commands within said established lower level protocol and writes these lower commands to said card,

and said card reader/writer reads commands or data in said established lower level protocol from said card translates them to corresponding commands or data in said high level language and writes these commands or data to said host application program.

2. A card reader/writer according to claim 1 characterised in that it can be loaded with one or more further protocol sets appropriate to one or more card applications additional to those for which protocol sets are initially stored, or that it can be loaded with a new suite of protocol sets to replace those initially stored, including at least some of those initially stored and one or more further protocol sets additional to those initially stored.

3. A card reader/writer according to either claim 1 or claim 2 characterised in that a plurality of card application-characterising strings are stored which correspond to a plurality of data storage card applications, said card reader/writer reads from a card interfaced to it the data string which characterises the card application, and said card reader/writer matches said read data string with a said stored card application-characterising string to thereby identify the card application.

4. A card reader/writer according to claim 1 or claim 2 characterised in that a plurality of card application-characterising strings are stored which each correspond to a known data storage card application, said card reader/writer reads from a card interfaced to it the data string which characterises the application, and said card reader/writer matches said read data string with said stored card application-characterising string to thereby identify the card application, and in that each said low level protocol set comprises a set of command strings and said card reader/writer translates high level language commands from the host program to corresponding command strings.

5. A card reader/writer according to claim 2, characterised in that said card reader/writer identifies commands from said host program not supported by said card application and upon identifying an unsupported command writes an error command to said host program.

6. A method of interfacing a host application program with a data storage card having an associated card application, comprising the steps of:

identifying the particular card application from the card,

selecting from a store of a number of protocols for a number of different card applications the appropriate lower level protocol for the identified card application,

reading high level language commands from the host program,

translating said read high level language commands to corresponding commands within said identified lower level protocol,

writing said corresponding commands to said card,

reading commands or data in said established lower level protocol from said card,

translating said lower level protocol commands or data into corresponding commands or data in said high level language, and

writing said corresponding commands or data in said high level language to said host application program.

7. A method according to claim 6 wherein identifying the particular card application includes the steps of reading from the card a data string which characterises the card application and matching said read data string with a card application-characterising string from a plurality of stored card application-characterising strings, corresponding to a plurality of different data storage card applications, to thereby identify the card application.

8. A method as claimed in either claim 6 or claim 7 including the step of identifying high level language commands read from the host program not supported by said card application and upon identifying an unsupported command, returning an error command to said host program.

9. A method of enabling a controller to read and write data via a card read/write station to an electronic data storage card having an associated card application, which method uses a stored-program stored-data processor, said method comprising:

storing first data arrays containing strings of different card application-characterising data and for each string its corresponding card identifier, storing second data arrays containing card identifiers and for each identifier its corresponding command strings, and executing a program on said processor which causes said processor to;

(1) detect a card presented to said read/write station and to pass a card detect signal to said controller,

(2) read the data string which characterises the card application,

(3) search through at least one said first array for a matching data string, and upon making a successful match to retrieve the corresponding card application identifier,

(4) select the appropriate command strings in said second array using the retrieved card application identifier,

(5) accept generic transaction instructions from said controller,

(6) translate the instructions from said controller to commands appropriate to the card application using the selected command strings from the second array, and

(7) either read or write data to said card in accordance with said generic instructions.

10. A universal card interface for interfacing smartcards and other card devices having electronic data storage and having associated therewith a card application, with a controller requiring read/write access to said card comprising:

a card read/write station to which cards may be interfaced for data transfer, a processor having associated memory and input-output ports,

said read/write station connected to one input-output port and said controller connected to a second input-output port,

interface software and data arrays stored in said memory,

said data arrays including first and second data arrays with said first data arrays containing strings of different card application-characterising data and for each string its corresponding card application identifier, said second data arrays containing card application identifiers and for each identifier its corresponding command strings, said software when executed by said processor causing said processor to;

(1) detect the presence of a card presented to said read/write station and to pass a card detect signal to said controller,

(2) read from the card the data string which characterises the card application,

(3) search through at least one said first array for a matching data string, and upon making a successful match to retrieve the corresponding card application identifier,

(4) select the appropriate command strings in said second array using the retrieved card application identifier,

(5) accept generic transaction instructions from said controller,

(6) translate the instructions from said controller to commands appropriate to the card application on the card using the selected command strings from the second array, and

(7) either read or write data to said card in accordance with said generic instructions.

11. A method of enabling host application software to interface with any known type of smartcard or other data storage card devices having an associated card application, comprising:

(1) reading from the card to be interfaced the data string which characterises a particular card application,

(2) searching through a first data array containing strings of different card application-characterising data, and for each string its corresponding card application identifier, for a matching data string, and upon making a successful match retrieving the corresponding card identifier,

(3) selecting the appropriate command strings from a second data array containing card application identifiers, and for each identifier its corresponding command strings, using the retrieved card application identifier,

(4) accepting generic transaction instructions from said host application software,

(5) translating the instructions from said host application software to lower level commands appropriate to the card application being interfaced using the selected command strings from said second data array, and

(6) causing data to be either read from or written to said card in accordance with said generic instructions.

12. A software algorithm which enables host application software to interface with different types of smartcard or other data storage card devices having associated therewith a card application, comprising a hierarchy of functional modules wherein:

a first level module reads from the card to be interfaced the data string which characterises that card application and passes said data string to a second level module,

the second level module searches through a first data array containing strings of different application-characterising data, and for each string its corresponding card application identifier, for a matching data string, and upon making a successful match retrieves the corresponding card application identifier and passes said card application identifier to a third level module,

the third level module selects the appropriate command strings from a second data array containing card application identifiers, and for each identifier its corresponding command strings, using the card application identifier passed to it,

a fifth level module accepts generic transaction instructions from said host application software and passes those instructions to a fourth level module,

the fourth level module translates the instructions from said fifth level module to lower level commands appropriate to the card application being interfaced using the command strings selected by the third level module, and

the first level module either reads from or writes to said card in accordance with the translated generic instructions passed from the fourth level module.