CA2281576C - Multi-application ic card system - Google Patents
Multi-application ic card system Download PDFInfo
- Publication number
- CA2281576C CA2281576C CA002281576A CA2281576A CA2281576C CA 2281576 C CA2281576 C CA 2281576C CA 002281576 A CA002281576 A CA 002281576A CA 2281576 A CA2281576 A CA 2281576A CA 2281576 C CA2281576 C CA 2281576C
- Authority
- CA
- Canada
- Prior art keywords
- card
- application
- data
- cards
- personalization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1016—Devices or methods for securing the PIN and other transaction-data, e.g. by encryption
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
- G06K19/067—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
- G06K19/07—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
- G06K19/0719—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips at least one of the integrated circuit chips comprising an arrangement for application selection, e.g. an acceleration sensor or a set of radio buttons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/355—Personalisation of cards for use
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/355—Personalisation of cards for use
- G06Q20/3552—Downloading or loading of personalisation data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/357—Cards having a plurality of specified features
- G06Q20/3574—Multiple applications on card
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/357—Cards having a plurality of specified features
- G06Q20/3576—Multiple memory zones on card
- G06Q20/35765—Access rights to memory zones
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/409—Device specific authentication in transaction processing
- G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/409—Device specific authentication in transaction processing
- G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners
- G06Q20/40975—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners using encryption therefor
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
Abstract
A multi-application IC card system is disclosed having selective application loading and deleting capability. Prior to loading an application onto an IC card a test is conducted to determine if the card is qualified to receive the application using personalization data stored on the card and comparing it with permissions data associated with the application indicating one or more sets of cards upon which the application may be loaded. If the personalization data of the card falls within the allowable set of permissions for that application then the card may be loaded with the application. Preferably, the personalization data includes data representative of the card number, issuer, a product class and the date on which the card is personalized.
Description
MULTI-APPLICATION IC CARD SYSTEM
Integrated circuit ("IC") cards are becoming increasingly used for many different purposes in the world today. An IC card (also called a smart card) typically is the size of a conventional credit card which contains a computer chip including a microprocessor, read-only-memory (ROM), electrically erasable programmable read-only-memory (EEPROM), an InpuvOutput (UO) mechanism and other circuitry to support the microprocessor in its operations. An IC card may contain a single application or may contain multiple independent applications in its memory. MULTOSTM is a multiple application operating system which runs on IC cards, among other platforms, and allows multiple applications to be executed on the card itself. This allows a card user to run many programs stored in the card (for example, creditldebit, electronic money/purse andlor loyalty applications) irrespective of the type of terminal (i.e., ATM, telephone andlor POS} in which the card is inserted for use.
A conventional single application IC card, such as a telephone card or an electronic cash card, is loaded with a single application at its personalization stage. That application, however, cannot be modified or changed after the card is issued even if the modification is desired by the card user or card issuer. Moreover, if a card user wanted a variety of application functions to be performed by IC cards issued to him or her, such as SUBSTITUTE SHEET (RULE 26) both an electronic purse and a credit/debit fimction, the card user would be required to carry multiple physical cards on his or her person, which would be quite cumbersome and inconvenient. If an application developer or card user desired two different applications to interact or exchange data with each other, such as a purse application interacting with a frequent flyer loyalty application, the card user would be forced to swap multiple cards in and out of the card-receiving terminal, making the transaction difficult, lengthy and inconvenient.
The Applicant has recognised therefore, that it is beneficial to store multiple applications on the same IC card. For example, a card user may have both a purse application and a credit/debit application on the same card so that the user could select which type of payment (by electronic cash or credit card) to use to make a purchase.
Multiple applications could be provided to an IC card if sufficient memory exists and an operating system capable of supporting multiple applications is present on the card.
Altliough multiple applications could be pre-selected and placed in the memory of the card dining is production stage, it would also be beneficial to have the ability to load and delete applications for card post-production as needed.
The increased flexibility and power of storing multiple applications on a single card create new challenges to be overcome concerning the integrity and security of the information (including application code and associated data) exchanged between the individual card and the application provider as well as within the entire system when loading and deleting applications. The Applicant has fiuthez recognised that it would be beneficial to have the capability of the IC
card system to exchange data among cards, card issuers, system operators and application _2_ SUBSTITUTE SHEET (RULE 26) providers securely and to load and delete applications securely at any time from either a terminal or remotely over a telephone line, Internet or intranet connection or other data conduit. Because these data transmission lines are not typically secure lines, a number of security and entity-authentication techniques must be implemented to make sure that applications being sent over the transmission lines are only loaded on the intended cards.
As mentioned, it is important -- particularly where there is a continuing wide availability of new applications to the cardholder -- that the system has the capability of adding applications onto the IC card subsequent to issuance.
This is highly advantageous since it protects the longevity of the IC cards;
otherwise, once an application becomes outdated, the card would be useless. In this regard, to protect against the improper or undesired loading of applications onto IC cards, the Applicant lias fiirther recognised that it would be beneficial for the IC card system to have the capability of controlling the loading process and restricting, when necessary or desirable, the use of certain applications to a limited group or number of cards such that the applications are "selectively available" to the IC-cards in the system.
This "selective capability" would allow the loading and deleting of applications at, for example, a desired point in time in the card's life cycle. It would also allow the loading of an application only to those cards chosen to receive the selected application.
Accordingly, it is an advantage of a preferred embodiment of the invention that it provides these important features and specifically a secure IC-card system that allows for selective availability of smart card applications which may be loaded onto IC
cards.
SUBSTITUTE SHEET (RULE 26) These and other advantages are achieved by an embodiment of the present invention which proves an IC card system comprising at least one IC card and an application to be loaded onto the card wherein the IC card contains card personalization date and the application is assigned application permissions data designating which IC card or group of IC cards upon which the application may be loaded. The system checks to determine whether the card's personalization data falls within the permissible set indicated by the application's permissions data. If it does, the application may be loaded onto the card.
In a preferred embodiment, the card personalization data is transferred onto the card by the personalization bureau after the card is manufactured.
The data preferably includes data representing the card number, the issuer, product class (i.e., such as gold or platinum cards), and the date on which the card was personalized.
The card further preferably contains enablement data indicating whether or not the card has been enabled with personalized data.
In a further preferred embodiment, the IC card secure system checks the enablement data prior to loading an application to determine whether or not the card has been enabled. Preferably, if the card has been enabled, the system checks if the card number, the issuer, the product class andlor the date on which the card was personalized are within the acceptable set indicated by the application's permissions data.
If so, the application may be loaded onto the IC card.
SUBSTITUTE SHEET tRULE 26) WO 98/37526 PCT/GB98/00531 _ In yet another preferred embodiment, the application's permissions data may contain data representative of a blanket permission such that all cards would pass for application loading.
Further aspects, features and advantages of embodiments of the invention will become apparent from the following detailed description taken in conjunction with the accompanying figures showing illustrative embodiments of the invention, in which Fig. 1 is block diagram illustrating the three stages in the life of a multi-application IC card in a secure system;
Fig. 2 is a block diagram illustrating the steps of the card manufacture process;
Fig. 3 is a flow diagram illustrating the steps involved in enabling each of the IC cards in the secure system;
Fig. 4 is a block diagram of an IC card chip which can be used in accordance with an embodiment of the invention;
Fig. 5 is a block diagram illustrating the data stored on the IC card as indicated in block 307 of Fig. 3;
Fig. SA is a schematic of the data structures residing in an IC card and represenring personalization data;
- S -SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ Fig. 6 is a flowchart illustrating the steps of loading an application onto an IC card in the secure system;
Fig. 7 is a flow chart illustrating the checking steps as indicated in block 601 of Fig. 6;
Fig. 8 is a flowchart illustrating the steps undertaken in determining if loading of an application may proceed;
Fig. 9 is a block diagram showing the components of the system architecture for the enablement process of an IC card in a secure mufti-application IC
card system; and Fig. 10 is a system diagram of entities involved with the use of the IC card once it has been personalized.
Throughout the figures, the same reference numerals and characters, unless otherwise stated, are used to denote like features, elements, components or portions of the illustrated embodiments. Moreover, while the subject invention will now be described in detail with reference to the figures, it is done so in connection with the illustrative embodiments. It is intended that changes and modifications can be made to the described embodiments without departing from the true scope and spirit of the subject invention as defined by the appended claims.
SUBSTITUTE SHEET (RULE 26) An embodiment of the present invention provides an IC card system and process which allow the flexibility to load and delete selected applications over the lifetime of a mufti-application IC card in response to the needs or desires of the card user, card issuers and/or application developers. A card user who has such a card can selectively load and delete applications as desired if allowed by the card issuer in conjunction with the system operator or Certification Authority ("CA") which controls the loading and deleting process by certifying the transfer of information relating to the process.
By allowing applications to be selectively loaded and deleted from the card, a card issuer can extend additional functionality to an individual IC
card without having to issue new cards. Moreover, application developers can replace old applications with new enhanced versions, and applications residing on the same card using a common multiple application operating system may interact and exchange data in a safe and secure manner. For example, a frequent flyer loyalty program may automatically credit one frequent flyer mile to a card user's internal account for every dollar spent with an electronic purse such as the Mondex purse or with a credit/debit application. By allowing the ability to selectively load and delete applications, the card user, subject to the requirements of the card issuer, also has the option of changing loyalty programs as desired.
A card issuer or application developer may intend that a particular application be loaded on only one card for a particular card user in a card system. A
regional bank may desire to have a proprietary application reside only on the cards which _ 7 _ SUBSTITUTE SHEET (RULE 26) the bank issues. Embodiments in accordance with the present invention would allow for tliis selective loading and specifically allow for the prevention of loading proprietary applications onto unauthorized cards issued by others.
To achieve these desired objectives, embodiments of the present invention give each card a specific indentity by storing "card personalization data" on the card.
Morover, each application to be loaded or deleted on one or more cards in the system is assigned "application permissions data" which specify the cards upon which the applications may be loaded.
The type of personalized data can vary depending upon the needs and requirements of the card system. In the preferred embodiment, described in greater detail below, the personalization data include unique card identification designation data, the card issuer, the product class or type (which is defined by the card issuer) and the date of personalization. However, not all of these data elements are required to be used and additional elements could also be included.
The application permissions data associated with an application, also described in greater detail below, can be a single value in an identity field or could include multiple values in the identity field. For example, the application permissions data in the card issuer field could represent both product class A and product class B from a certain Bank X, indicating that the application could be loaded onto cards designated as product classes A and B issued by Bank X (as indicated in the card product ID
field of the card's personalization data).
_g_ SUBSTITUTE SHEET (RULE 26) PCT/GB98/00531 _ In addition, a "global value" could be stored in the issuer field (or other field) of the application permissions data indicating that all IC cards in the system regardless of who issued the card would match this permissions field. In this case, for example, a data value of zero stored in the application permissions card-issuer field will match all of the cards' personalization card-issuer fields.
Figure 1 shows the three steps involved in providing an operational multi-application IC card in a secure system. The first step is the card manufacturing step 101.
The second step is the personalization step 103 where card personalization data (also called entity authentication data) is loaded onto the card. The third step is the application loading step 105 which checks to see if a card is qualified to receive an application, i.e., when the personalization data is checked against the application permissions data associated with the application to be loaded. Each of these three steps is described in detail below.
Card Manufacture Figure 2 shows the steps necessary in manufacturing an IC card in a secure system. Step 20I manufactures the physical IC card by creating the integrated circuit on silicon and placing it on the card. The integrated circuit chip will include RAM, ROM
and EEPROM memories. When the card is first manufactured, a global public key of the system operator (in this case called the Certification Authority (CA)) is stored on each card in ROM in step 203. This will allow the card to authenticate that the source of any message to it is from the CA since the public key on the card will be matched to the CA's secret key.
SUBSTITUTE SHEET (RULE 26) More specifically, this public key stored on the card will allow the individual card to verify data signed with the CA's private key. The public key of the CA, which is stored on the card, is used only for determining if the data sent to the card was signed with the proper CA private key. This allows the card to verify the source of any message coming from the CA.
Step 205 inserts a card enablement key in a secure portion of EEPROM in the card to facilitate card specific confidentiality during enablement, and step 207 inserts a card identifier in EEPROM of the card. The identifier, which can be accessed by any terminal, will allow the system to determine the identity of the card in later processes.
The identifier is freely available and will not be used to authenticate messages.
Step 209 stores the operating system code in ROM on the card including any primitives which are called or supported by the operating system. The primitives are written in native language code (e.g., assembly language) and are stored in ROM. The primitives are subroutines which may be called by the operating system or by applications residing on the card such as mathematic functions (multiply or divide), data retrieval, data manipulation or cryptographic algorithms. The primitives can be executed very quickly because they are written in the native language of the processor.
After the IC cards are manufactured, they are sent to a personalization bureau ("PB") to enable and personalize the card by storing card personalization data in the memory of the card. The terms enablement and personalization are used interchangeably herein to indicate the preparatory steps taken to allow the card to be loaded securely with SUBSTITUTE SHEET (RULE 26) an application. The individual cards are preferably manufactured in batches and are sent to a personalization bureau in a group for processing.
C'~rd Enablement~ersonalization Figure 3 shows the steps of the card enablement process when the card arrives at a personalization bureau. The personalization bureau may be the card issuer (e.g., a bank or other financial institution) or may be a third party that performs the service for the card issuer. The personalization bureau configures the card to a specific user or user class.
Figure 3 specifically shows the steps taken to enable and personalize each I0 IC card which will work within the system. The cards can be placed in a terminal which communicates with IC cards and which reads the card identifier data (previously placed on the card during the manufacturing process -- see step 207). This card identification data is read from the card in step 301. The terminal will effectively send a "get identification data" command to the card and the card will return the identification data to I S the terminal.
The PB typically processes a group of cards at the same time, and will first compile a list of IC card identif cation data for the group of cards it is personalizing. The PB then sends electronically (or otherwise) this list of identification data to the Certification Authority ("CA") which creates a personalization (or enablement) data 20 block for each card identifier. The data block includes the card personalization data organized in a number of identity fields and an individual key set for the card, discussed below. These data blocks are then encrypted and sent to the PB in step 302. By using the SUBSTITUTE SHEET (RULE 26) WO 9/37526 PCT/GB98/00531 _ card identification data, the PB then matches the cards with the encrypted data blocks and separately loads each data block onto the matched card. To insure that the CA
controls the identity of the card and the integrity of the system, the PB never obtains knowledge of the content of the data blocks transferred. Some aspects of the personalization are requested by the card issuer to the CA in order to affect their preferred management of the cards they issue. The following additional steps are performed.
Step 303 first checks to see if an enablement bit stored in EEPROM of the card has been already set. If it already has been set, the card has already been configured and personalized and the enablement process will end as shown in step 304. A
card cannot be enabled and personalized twice. If the bit has not been set, then the process continues with step 305.
In step 305, the individualized card key set for the card being enabled (which key set is generated at the CA) is stored on the card. The keys can be used later in off card verification (i.e., to verify that the card is an authentic card).
This verification is necessary to further authenticate the card as the one for which the application was intended.
Step 307 generates four different MULTOS Security Manager (MSM) characteristic data elements (otherwise referred to herein as personalization data) for the card at the CA which are used for securely and correctly loading and deleting applications from a particular card. The MSM characteristics also allow for the loading of applications on specific classes of identified cards. (These MSM
characteristics are further described in connection with Figure 5.) SUBSTITUTE SHEET (RULE 26) Other data can also be stored on the card at this time as needed by the system design such as an address table or further subroutines.
Step 311 sets the enablement bit in EEPROM of the card which indicates that the enablement process has been completed for the particular card. When this bit is set, another enablement process cannot occur on the card. This ensures that only one personalization and enablement process will occur to the card thus preventing illegal tampering of the card or altering the card by mistake. in the preferred embodiment, the enablement bit is initially not set when the card is manufactured and is set at the end of the enablement process.
Figure 4 shows an example of a block diagram of an IC card chip which has been manufactured and personalized. The IC card chip is located on an IC
card for use. The IC card preferably includes a central processing unit 401, a RAM 403, a EEPROM 405, a ROM 407, a timer 409, control logic 411, an I/O ports 413 and security circuitry 415, which are connected together by a conventional data bus.
Control logic 411 in memory cards provides sufficient sequencing and switching to handle read-write access to the card's memory through the input/output ports. CPU 401 with its control logic can perform calculations, access memory locations, modify memory contents, and manage input/output ports. Some cards have a coprocessor for handling complex computations like cryptographic algorithms. Input/output ports 413 are used under the control of a CPU and control logic alone, for communications between the card and a card acceptance device. Timer 409 (which generates or provides a clock pulse) drives the control logic 411 and CPU 401 through the sequence of steps that SUBSTITUTE SHEET (RULE 26) accomplish memory access, memory reading or writing, processing, and data communication. A timer may be used to provide application features such as call duration. Security circuitry 415 includes fusible links that connect the input/output lines to internal circuitry as required for testing during manufacture, but which are destroyed ("blown") upon completion of testing to prevent later access. The personalization data to qualify the card is stored in a secured location of EEPROM 405. The comparing of the personalization data to applications permissions data is performed by the CPU
401.
Figure ~ shows the steps of generating and loading the four elements of the card personalization data into the memory of the IC cards, and Fig. SA
shows a schematic of bit maps for each identity field residing in the memory of an IC
card containing personalization data in accordance with the present invention. Each data structure for each identity field has its own descriptor code. Step 501 loads the data structure for the identity field "card ID" called "msm mcd_permissions mcd no." This nomenclature stands for MULTOS system manager _ MULTOS card device _ I S permissions_ MULTOS card device number. Although this number is typically 8 bytes long as shown in Fig. SA, the data could be any length that indicates a unique number for the card. In the preferred embodiment, 2 bytes are dedicated as a signal indicator, 2 bytes comprise a MULTOS Injection Security Module )D (MISM >D) indicating which security module injected the card with its injected keys when it was manufactured, and 4 bytes comprise an Integrated Circuit Card (ICC) serial number which identifies the individual card produced at the particular MISM.
SUBSTITUTE SHEET (RULE 26) Step 503 loads the data structure for the identity field "issuer ID" called "msm mcd_permissions_ mcd issuer id." This nomenclature stands for a_ MLJLTOS
card device issuer identification number. Each card issuer (such as a particular bank, financial institution or other company involved with an application) will be assigned a unique nurnber in the card system. Each IC card in the MULTOS system will contain information regarding the card issuer which personalized the card or is responsible for the card. A card issuer will order a certain number of cards from a manufacturer and perform or have performed the personalization process as described herein. For example, a regional bank may order 5,000 cards to be distributed to its customers. The "mcd issuer id" data structure on these cards will indicate which issuer issued the cards.
In the preferred embodiment, the data structure is 4 bytes long (as shown in Fig. SA at 503A) to allow for many different issuers in the system although the length of the data structure can vary with the needs of the card system.
Step 505 loads the data structure for the identity field "product ID" called "msm-mcd~ermissions mcd_ issuer_product id." This nomenclature stands for MULTOS card device issuer product identification number. Each card issuer may have different classes of products or cards which it may want to differentiate. For example, a bank could issue a regular credit card with one product ID, a gold credit card with another product ID and a platinum card with still another product 1D. The card issuer may wish to load certain applications onto only one class of credit cards. A gold credit card user who pays an annual fee may be entitled to a greater variety of applications than a regular credit card user who pays no annual fee. The product ID field identifies the card as a SUBSTITUTE SHEET (RULE 26) particular class and will later allow the card issuer to check the product )D
and only load applications onto cards which match the desired class.
Another way to differentiate products is by application type, such as by categorizing the application as financial, legal, medical and/or recreational, or by assigning particular applications to a group of cards. For example, one card issuer may have different loyalty programs available with different companies to different sets of card users. For example, a bank may have an American Airlines~ loyalty program and a British Airways~ loyalty program for different regions of the country dependent on where the airlines fly. The product type allows the issuer to fix the product classification of the card during the personalization process. When loading applications onto the card, the product type identification number on each card will be checked to make sure it matches the type of card onto which the issuer desires to load. The product type data structure is preferably an indexing mechanism (unlike the other personalization data structure) of 8 bits (as shown at SOSA in Fig. SAl but could be any length depending upon the needs of the card system. In the illustrated embodiment, the resulting instruction would be to locate the second bit (since the byte's indicated value is 2) in the array to be searched (see discussion of step 809 below).
Step 507 loads the data structure for the identity field data called "msm_mcd,~ermissions mcd_ controls data date." This nomenclature stands for the MIJLTOS card device controls data date or, in other words, the date on which the card was personalized so that, for example, the application loader can load cards dated only after a certain date, load cards before a certain date (e.g., for application updates) or load SUBSTITUTE SHEET (RULE 26) cards with a particular data date. The information can include the year, month and day of personalization or may include less information, if desired. The data date data structure is preferably 1 byte in length (see 507A in Fig. SA) although it could be any length depending upon the needs of the particular card system used.
Once all of the personalization data structures are loaded and stored in the card, the card has been identified by issuer, product class, date and identification number (and other data fields, if desired), and the card cannot change its identity;
these fields cannot be changed in the memory of the card. If a card user wants to change the product id stored in the card to gain access to different applications available to another product type, a new card will have to be issued to the user containing the correct personalization data. This system is consistent with a gold card member receiving a new card when the classification is changed to platinum.
After the card has been enabled and personalized by storing its individual card key set, MSM personalization characteristics and enablement bit as described in Fig.
3, the card is ready to have applications loaded into its memory.
Loading A2nlicationc The application loading process contains a number of security and card configuration checks to ensure the secure and proper loading of an application onto the intended IC card. The application loading process is preferably performed at the personalization bureau so that the card will contain one or more applications when the card is issued. The card may contain certain common applications which will be present on every card the issuer sends out, such as an electronic purse application or a creditldebit SUBSTITUTE SHEET (RULE 26) application. Alternatively, the personalization bureau could send the enabled cards to a third party for the process of loading applications. The multiple application operating system stored in the ROM of each card and the card MSM personalization data is designed to allow future loading and deleting of applications after the card has been issued depending upon the desires of the particular card user and the responsible card issuer. Thus, an older version of an application stored on the IC card could be replaced with a new version of the application. An additional loyalty application could also be added to the card after it has been initially sent to the card user because the application is newly available or the user desires to use the new application. These loading and deleting functions for applications can be performed directly by a terminal or may be performed over telephone lines, data tines, a network such as the Internet or any other way of transmitting data between two entities. In the present IC card system, the process of transmitting the application program and data ensures that only IC cards containing the proper personalization data and which fit on application permissions profile will be qualif ed and receive the corresponding application program and data.
Figure 6 shows the preferred steps performed in loading an application onto an IC card in the MLTLTOS IC card system. For this example, the personalization bureau is loading an application from a tenninal which enabled the same card.
Step 601 performs an "open command" initiated by the terminal which previews the card to make sure the card is qualified to accept the loading of a specific application.
The open command provides the card with the application's permissions data, the application's size, and instructs the card to determine ( 1 ) if the enablement bit is set indicating the card SUBSTITUTE SHEET (RULE 26) has been personalized; (2) whether the application code and associated data will fit in the existing memory space on the card; and (3) whether the personalization data assigned to the application to be loaded allows for the loading of the application onto the particular card at issue. The open command could also make additional checks as required by the S card system. These checking steps during the open command execution will be described in detail in conjunction with Figure 7.
After the open command has been executed, the application loader via the terminal will be advised if the card contains the proper identification personalization data and if enough room exists in the memory of the card for the application code and related data. If there is insufficient memory, then a negative response is returned by the card and the process is abended (abnormally ended). If the identification personalization data does not match the applications permissions data, a warning response is given in step 603, but the process continues to the load and create steps. Alternatively, if there is no match, the process may automatically be abended. If a positive response is returned by the card to the terminal in step 605, the application loader preferably proceeds to next steps. The open command allows the application to preview the card before starting any transfer of the code and data.
Step 607 then loads the application code and data onto the IC card into EEPROM. The actual loading occurs in conjunction with create step 609 which completes the loading process and enables the application to execute on the IC
card after it is loaded. The combination of the open, load and create commands are sent by the terminal. or another application provider source, to the IC card to perform the application SUBSTITUTE SHEET (RULE 26) loading process. The operating system in the IC cards is progtarnrrled to perform a specific set of instructions with respect to each of these commands so that the IC card will communicate with and properly carry out the instructions from the terminal.
Step 609 performs the create command which at least: ( 1 ) checks if an application load certificate is signed (encrypted) by the CA and therefore authenticates the application as a proper application for the system; and (2) checks the card personalization data stored on the card against the permissions profile for the application to be loaded to qualify the card for loading. It may do other checks as required. If one of the checks fails, then a failure response 610 is given and the process aborts.
The application after it has passed these checks will be loaded into the memory of the card.
Figure 7 shows the various steps of the open step 601 of Fig. 6 in more detail. Step 701 determines if the enablement (i.e., control) bit is set. This bit is set when the card has completed its personalization process and has been assigned its personalization data. An application can be loaded on an IC card in the card system only if the card contains the personalization data. If the enablement bit is not set, the card has not been personalized and therefore the card returns a negative response 703 to the terminal. If the enablement bit is set, then the card has been enabled and the test conditions continue with step 711.
Step 711 checks if there is sufficient space in the memory on the card to store the application code and its associated data. Applications will typically have associated data related to their fimctions. This data will be used and manipulated when the application is run. Storage space in the memory of an IC card is a continuing concern SUBSTITUTE SHEET (RULE 26) due to the relatively large physical space required for EEPROM and how it fits in the integrated circuit which is desired to be small enough to fit on a credit card sized card.
An example of the size of a preset EEPROM on an IC card is 16K bytes although the actual size varies. Applications can range from 1K byte or less for a very simple applicatior. up to the size of available memory for a more sophisticated application. The data associated with an application can range from no data being stored in the card memory to a size constrained by the amount of available memory. These varied sizes of application code and data continually increase as applications become more advanced and diverse.
MULTOS as an operating system is not limited by the number of applications and associated data it can store on the card. Thus, if five applications can fit in the available memory of the card, the card user will have greatly increased fiutctionality than if one or two applications were stored on the card. Once a card's memory is filled to its capacity, however, a new application cannot be loaded onto the card unless another application including its code and data of sufficient size can be deleted. Therefore, checking the amount of available space on the card is an important step. If there is not sufficient space, then an insufficient space response 713 will be returned to the terminal. The application loader can then decide if another existing application on the card should be deleted to make room for the new application. Deletion depends upon the card issuer having an application delete certificate from the CA. If there is sufficient space on the card, then the process continues with step 715.
SUBSTITUTE SHEET (RULE 26) An example of the testing of memory spaces in step 711 is now described.
The numbers used in this example in no way limit the scope of the invention but are used only to illustrate memory space requirements. An IC card may have 16K
available EEPROM when it is first manufactured. The operating system data necessary for the operating system may take up 2K of memory space. Thus, 14K would remain. An electronic purse application's code is stored in EEPROM and may take up 8K of memory space. The purse application's required data may take up an additional 4K of memory space in EEPROM. The memory space which is free for other applications would thus be 2K (16K-2K-8K-4K=2K). If a card issuer wants to load a credit/debit application whose code is 6K bytes in size onto the card in this example, the application will not fit in the memory of the IC card. Therefore, the application cannot load the new application without first removing the purse application from the card. If a new credit/debit application was loaded into EEPROM of the IC card, then it would have to overwrite other application's code or data. The application loader is prevented from doing this.
Figure 8 shows the steps performed in determining whether the card's personalization data falls within the permissible set of cards onto which the application at issue may be loaded. These steps are preferably performed during the execution of the "create" command. However, these steps may be performed at any time during the loading or deleting of an application. As described previously, the card is personalized by storing data specific to the card (MSM personalization data) including: a card ID
designation specific to an individual card, the card issuer number indicating the issuer of the card, the product type of the card, such as a gold or platinum card, and the date the SUBSTITUTE SHEET (RULE 26) card was personalized. This data uniquely identifies the card apart from all other IC cards in the system.
Accordingly, applications can be selectively stored on individual cards in the IC card system on virtually any basis, including the following. An application can be loaded selectively to cards containing one or more specific card numbers. An application can be selectively loaded on one or more cards containing a specified card issuer ID.
Moreover, an application can be loaded only upon one type of product specified by the particular card issuer, and/or the application can be loaded only on cards which have a specified date or series of dates of personalization. Each of the personalization data allows an application to be selectively loaded onto certain cards or groups of cards and also ensures that cards without the proper permissions will not receive the application.
Personalization data types in addition to the four described can also be used as needed.
The selection of IC cards upon which a particular application may be loaded is made possible by the use of "applications permissions data" which is assigned to the application and represents at least one set of cards upon which the application may be loaded. The set may be based on virtually any factor, including one or more of the following: card numbers, card issuers, product types or personalization dates.
Although the individual card's personalization data typically identify one specific number, one card issuer, one product type and one date, the application's permissions data may indicate a card numbers or a blanket permission, a card issuer or a blanket permission, and a number of product types and dates.
SUBSTITUTE SHEET (RULE 26) For example, a frequent loyalty program may be configured to allow its loading and use on cards in different product classes belonging to one card issuer. In addition, the application permissions data may indicate that the loyalty program can be used on gold and platinum product types if the card was issued after May, 1998. Thus, the MSM permissions check will determine if the card's individual personalization data is included in the allowed or permissible set of cards upon which the application may be loaded. If it is, the application will be loaded.
To expedite the comparison process, an alternative embodiment may include setting one or more permissions data at zero representing a blanket permission for that particular data. For instance, by placing a zero for the "card number"
entry in the application permissions data or some other value indicating that alt cards may be loaded regardless of their number, the system knows not to deny any cards based on their card number. Moreover, if a zero is placed in the application's permissions data "issuer m,"
then all cards similarly will pass the "issuer" test comparison. This feature allows greater flexibility in selecting groups of cards. The zero indicator could also be used for other permissions data, as required.
Referring to Figure 8, each of the permissions data is checked in the order shown, bat other orders could be followed because if any one of the permissions fails, the application will be prevented from being loaded on the IC card being checked.
The permissions are preferably checked in the order shown. Step 801 checks if the application permissions product type set encompasses the card's product type number stored in the memory of the card. Each card product type is assigned a number by the SUBSTITUTE SHEET (RULE 26) system operator. The product types are specified for each card issuer because different card issuers will have different product types. The cards are selectively checked to ensure that applications are loaded only on cards of authorized product type. The application permissions product type set can be 32 bytes long which includes multiple acceptable product types or can be a different length depending upon the needs of the system. Using data structure SOSA as an example, the operating system would check bit number 2 in the 256 bit array (32 bytes x 8 bits per byte) resulting from the 32 byte long application permissions data structure. if the permissions check fails, then the card returns a failure message to the terminal instep 803. If the product type check passes (for example, the value of bit no. 2 being 1 ), then the process continues with step 805.
Step 805 checks if the application permissions allowable card issuer number set encompasses the card's issuer number stored in the memory of the card or if the application permissions issuer data is zero (indicating all cards pass this individual permissions check). Each card issuer is assigned a number by the system operator and the cards are selectively checked to ensure that applications are loaded only on cards distributed by authorized card issuers. The application permissions card issuer number set can be 4 bytes long if one issuer is designated or can be longer depending upon the needs of the system. If the issuer check fails, then the card returns a failure message to the terminal in step 807. If the check passes, then the process continues with step 809.
Step 809 checks if the application permissions date set encompasses the card's data date stored in the memory of the card. The date that the IC card was personalized will be stored and will preferably include at least the month and year. The SUBSTITUTE SHEET (RULE 26) WO 98!37526 PCT/GB98/00531 cards are selectively checked to ensure that applications are loaded only on cards with the authorized personalization date. The application permissions date set can be 32 bytes long which includes multiple dates or can be a different length depending upon the needs of the system. If the date permissions check fails, then the card returns a failure message to the terminal in step 811. If the date check passes, then the process continues with step 813.
Step 813 checks if the application permissions allowable card number set encompasses the card's 117 number stored in the card memory or if the application permissions allowable card number data is zero (indicating all cards pass this individual permissions check). The testing of the permissions is performed on the card during the execution of the open, load and create commands. The application permissions card number data set can be 8 bytes long if one number is designated or can be longer depending upon the needs of the system. If the card number check fails, then the card returns a failure message to the terminal in step 815. If the check passes, then the process continues with step 817.
~mmaly,of IC Card ~rstem's Process Figure 9 shows the components of the system architecture for the card initialization process of an IC card in a secure multiple application IC card system. The system includes a card manufacturer 102, a personalization bureau I04, an application loader 106, the IC card 107 being initialized, the card user 109 and the certification authority 11 I for the entire multiple application secure system. The card user 131 is the SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ person or entity who will use the stored applications on the IC card. For example, a card user may prefer an IC card that contains both an electronic purse containing electronic cash (such as MONDEXTM) and a credit/debit application (such as the MasterCard~
EMV application) on the same IC card. The following is a description of one way in which the card user would obtain an IC card containing the desired applications in a secure manner.
The card user would contact a card issuer 113, such as a bank which distributes IC cards, and request an IC card with the two applications both residing in memory of a single IC card. The integrated circuit chip for the IC card would be manufactured by manufacturer 102 and sent to the card issuer 1 I3 (or an entity acting on its behalf) in the form of an IC chip on a card. As discussed above (see steps 201-209), during the manufacturing process, data is transmitted 115 via a data conduit from the manufacturer I 02 to card 107 and stored in IC card 10Ts memory. (Any of the data conduits described in this figure could be a telephone line, Internet connection or any other transmission medium.) The certification authority 111, which maintains encryptionldecryption keys for the entire system, transmits 117 security data (i.e., global public key) to the manufacturer over a data conduit which is placed on the card by the manufacturer along with other data, such as the card enablement key and card identifier.
The card's multiple application operating system is also stored in ROM and placed on the card by the manufacturer. After the cards have been initially processed, they are sent to the card issuer for personalization and application loading.
SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ The card issuer 113 performs, or has performed by another entity, two separate functions. First, the personalization bureau 104 personalizes the IC
card 107 in the ways described above, and second, the application loader 106 loads the application provided the card is qualified, as described.
Regarding personalization, an individualized card key set is generated by the CA and stored on the card (see Fig. 3). The card is further given a specific identity using MSM personalization (see Fig. 3, step 307 and Fig. 5) including a card )D number, an issuer ID number identifying the card issuer which processed the card, a card product type number which is specified by the card issuer and the date upon which the personalization took place. After the card has been personalized, applications need to be loaded onto the card so that the card can perform desired functions.
The application loader 106, which could use the same terminal or data conduit as persanalization bureau 104, first needs to have determined if the card is qualified to accept the application. This comparison process takes place on the card itself (as instructed by its operating system) using the permissions information. The card, if it is qualified, thus selectively loads the application onto itself based upon the card's identity and the card issuer's instructions. The application loader communicates 119 with the IC card via a terminal or by some other data conduit. After the applications have been loaded on the card, the card is delivered to the card user 109 for use.
The secure multiple application IC card system described herein allows for selective loading and deleting of applications at any point in the life cycle of the IC card after the card has been personalized. Thus, a card user could also receive a personalized SUBSTITUTE SHEET (RULE 26) card with no applications and then select a desired application over a common transmission line such as a telephone line or Internet connection.
Figure 10 is a system diagram of entities involved with the use of an IC
card once it has been personalized. The system includes an IC card 151, a terminal 153, S an application load/delete entity 155, the certification authority 157, a card issuer 171 and other IC cards 159 in the system. The arrows indicate communication between the respective entities. The CA 157 facilitates loading and deleting of applications. After providing the MSM permissions data and card specific keyset to the card during card enablements, the CA allows applications to be later loaded and deleted preferably by issuing an application certificate. Application specific keys are required to authenticate communication between a card and terminal. The IC card I51 also can communicate with other IC cards 159. Card issuer I71 is involved with all decisions of loading and deleting applications for a card which it issued. All communications are authenticated and transmitted securely in the system.
For instance, IC card 151 will use the following procedure to load a new application onto the card. IC card 1 O1 is connected to terminal 153 and the terminal requests that an application be loaded. Terminal 153 contacts application load/delete entity 155 which, as a result and in conjunction with card issuer I71, sends the application code, data and application permissions data (along with any other necessary data) to terminal 153. Terminal 153 then queries card I51 to ensure it is the correct card onto which the application may be loaded. If IC card passes the checks discussed above, the application is loaded onto card 151. The CA 157 provides the application load or SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ delete certificate that enables the application to be loaded or deleted from the card. This example shows one way to load the application, but other variations using the same principles could be performed, such as directly loading the application at the application load/delete entity 155.
The foregoing merely illustrates the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the invention and are thus within the spirit and scope of the invention.
For example, it will be appreciated that the MSM personalization and permissions data may not only be used for loading applications onto IC cards but also for deleting applications from said cards. The same checks involving MSM
permissions and loading applications are made for deleting applications. A delete certificate from the CA
authorizing the deletion of an application will control from which cards the application may be deleted. This is accomplished through the personalization data stored on each IC
card and the permissions check as described herein.
Moreover, the data may also be applicable to personal computers or other units onto which applications may be loaded which are not physically loaded on cards. In addition, the application's permissions data may actually include data representative of a set or sets of cards to be excluded, instead of included -- cards that cannot be loaded with the application.
SUBSTITUTE SHEET (RULE 26) The scope of the present disclosure includes any novel feature or combination of features disclosed therein either explicitly or implicitly or any generalisation thereof irrespective of whether or not it relates to the claimed invention or mitigates any or all of the problems addressed by the present invention. The applicant hereby gives notice that new claims may be formulated to such features during the prosecution of this application or of any sucli further application dernred therefrom In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims in any appropriate manner and not merely in the specific combinations enumerated in the claims.
SUBSTITUTE SHEET (RULE 26)
Integrated circuit ("IC") cards are becoming increasingly used for many different purposes in the world today. An IC card (also called a smart card) typically is the size of a conventional credit card which contains a computer chip including a microprocessor, read-only-memory (ROM), electrically erasable programmable read-only-memory (EEPROM), an InpuvOutput (UO) mechanism and other circuitry to support the microprocessor in its operations. An IC card may contain a single application or may contain multiple independent applications in its memory. MULTOSTM is a multiple application operating system which runs on IC cards, among other platforms, and allows multiple applications to be executed on the card itself. This allows a card user to run many programs stored in the card (for example, creditldebit, electronic money/purse andlor loyalty applications) irrespective of the type of terminal (i.e., ATM, telephone andlor POS} in which the card is inserted for use.
A conventional single application IC card, such as a telephone card or an electronic cash card, is loaded with a single application at its personalization stage. That application, however, cannot be modified or changed after the card is issued even if the modification is desired by the card user or card issuer. Moreover, if a card user wanted a variety of application functions to be performed by IC cards issued to him or her, such as SUBSTITUTE SHEET (RULE 26) both an electronic purse and a credit/debit fimction, the card user would be required to carry multiple physical cards on his or her person, which would be quite cumbersome and inconvenient. If an application developer or card user desired two different applications to interact or exchange data with each other, such as a purse application interacting with a frequent flyer loyalty application, the card user would be forced to swap multiple cards in and out of the card-receiving terminal, making the transaction difficult, lengthy and inconvenient.
The Applicant has recognised therefore, that it is beneficial to store multiple applications on the same IC card. For example, a card user may have both a purse application and a credit/debit application on the same card so that the user could select which type of payment (by electronic cash or credit card) to use to make a purchase.
Multiple applications could be provided to an IC card if sufficient memory exists and an operating system capable of supporting multiple applications is present on the card.
Altliough multiple applications could be pre-selected and placed in the memory of the card dining is production stage, it would also be beneficial to have the ability to load and delete applications for card post-production as needed.
The increased flexibility and power of storing multiple applications on a single card create new challenges to be overcome concerning the integrity and security of the information (including application code and associated data) exchanged between the individual card and the application provider as well as within the entire system when loading and deleting applications. The Applicant has fiuthez recognised that it would be beneficial to have the capability of the IC
card system to exchange data among cards, card issuers, system operators and application _2_ SUBSTITUTE SHEET (RULE 26) providers securely and to load and delete applications securely at any time from either a terminal or remotely over a telephone line, Internet or intranet connection or other data conduit. Because these data transmission lines are not typically secure lines, a number of security and entity-authentication techniques must be implemented to make sure that applications being sent over the transmission lines are only loaded on the intended cards.
As mentioned, it is important -- particularly where there is a continuing wide availability of new applications to the cardholder -- that the system has the capability of adding applications onto the IC card subsequent to issuance.
This is highly advantageous since it protects the longevity of the IC cards;
otherwise, once an application becomes outdated, the card would be useless. In this regard, to protect against the improper or undesired loading of applications onto IC cards, the Applicant lias fiirther recognised that it would be beneficial for the IC card system to have the capability of controlling the loading process and restricting, when necessary or desirable, the use of certain applications to a limited group or number of cards such that the applications are "selectively available" to the IC-cards in the system.
This "selective capability" would allow the loading and deleting of applications at, for example, a desired point in time in the card's life cycle. It would also allow the loading of an application only to those cards chosen to receive the selected application.
Accordingly, it is an advantage of a preferred embodiment of the invention that it provides these important features and specifically a secure IC-card system that allows for selective availability of smart card applications which may be loaded onto IC
cards.
SUBSTITUTE SHEET (RULE 26) These and other advantages are achieved by an embodiment of the present invention which proves an IC card system comprising at least one IC card and an application to be loaded onto the card wherein the IC card contains card personalization date and the application is assigned application permissions data designating which IC card or group of IC cards upon which the application may be loaded. The system checks to determine whether the card's personalization data falls within the permissible set indicated by the application's permissions data. If it does, the application may be loaded onto the card.
In a preferred embodiment, the card personalization data is transferred onto the card by the personalization bureau after the card is manufactured.
The data preferably includes data representing the card number, the issuer, product class (i.e., such as gold or platinum cards), and the date on which the card was personalized.
The card further preferably contains enablement data indicating whether or not the card has been enabled with personalized data.
In a further preferred embodiment, the IC card secure system checks the enablement data prior to loading an application to determine whether or not the card has been enabled. Preferably, if the card has been enabled, the system checks if the card number, the issuer, the product class andlor the date on which the card was personalized are within the acceptable set indicated by the application's permissions data.
If so, the application may be loaded onto the IC card.
SUBSTITUTE SHEET tRULE 26) WO 98/37526 PCT/GB98/00531 _ In yet another preferred embodiment, the application's permissions data may contain data representative of a blanket permission such that all cards would pass for application loading.
Further aspects, features and advantages of embodiments of the invention will become apparent from the following detailed description taken in conjunction with the accompanying figures showing illustrative embodiments of the invention, in which Fig. 1 is block diagram illustrating the three stages in the life of a multi-application IC card in a secure system;
Fig. 2 is a block diagram illustrating the steps of the card manufacture process;
Fig. 3 is a flow diagram illustrating the steps involved in enabling each of the IC cards in the secure system;
Fig. 4 is a block diagram of an IC card chip which can be used in accordance with an embodiment of the invention;
Fig. 5 is a block diagram illustrating the data stored on the IC card as indicated in block 307 of Fig. 3;
Fig. SA is a schematic of the data structures residing in an IC card and represenring personalization data;
- S -SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ Fig. 6 is a flowchart illustrating the steps of loading an application onto an IC card in the secure system;
Fig. 7 is a flow chart illustrating the checking steps as indicated in block 601 of Fig. 6;
Fig. 8 is a flowchart illustrating the steps undertaken in determining if loading of an application may proceed;
Fig. 9 is a block diagram showing the components of the system architecture for the enablement process of an IC card in a secure mufti-application IC
card system; and Fig. 10 is a system diagram of entities involved with the use of the IC card once it has been personalized.
Throughout the figures, the same reference numerals and characters, unless otherwise stated, are used to denote like features, elements, components or portions of the illustrated embodiments. Moreover, while the subject invention will now be described in detail with reference to the figures, it is done so in connection with the illustrative embodiments. It is intended that changes and modifications can be made to the described embodiments without departing from the true scope and spirit of the subject invention as defined by the appended claims.
SUBSTITUTE SHEET (RULE 26) An embodiment of the present invention provides an IC card system and process which allow the flexibility to load and delete selected applications over the lifetime of a mufti-application IC card in response to the needs or desires of the card user, card issuers and/or application developers. A card user who has such a card can selectively load and delete applications as desired if allowed by the card issuer in conjunction with the system operator or Certification Authority ("CA") which controls the loading and deleting process by certifying the transfer of information relating to the process.
By allowing applications to be selectively loaded and deleted from the card, a card issuer can extend additional functionality to an individual IC
card without having to issue new cards. Moreover, application developers can replace old applications with new enhanced versions, and applications residing on the same card using a common multiple application operating system may interact and exchange data in a safe and secure manner. For example, a frequent flyer loyalty program may automatically credit one frequent flyer mile to a card user's internal account for every dollar spent with an electronic purse such as the Mondex purse or with a credit/debit application. By allowing the ability to selectively load and delete applications, the card user, subject to the requirements of the card issuer, also has the option of changing loyalty programs as desired.
A card issuer or application developer may intend that a particular application be loaded on only one card for a particular card user in a card system. A
regional bank may desire to have a proprietary application reside only on the cards which _ 7 _ SUBSTITUTE SHEET (RULE 26) the bank issues. Embodiments in accordance with the present invention would allow for tliis selective loading and specifically allow for the prevention of loading proprietary applications onto unauthorized cards issued by others.
To achieve these desired objectives, embodiments of the present invention give each card a specific indentity by storing "card personalization data" on the card.
Morover, each application to be loaded or deleted on one or more cards in the system is assigned "application permissions data" which specify the cards upon which the applications may be loaded.
The type of personalized data can vary depending upon the needs and requirements of the card system. In the preferred embodiment, described in greater detail below, the personalization data include unique card identification designation data, the card issuer, the product class or type (which is defined by the card issuer) and the date of personalization. However, not all of these data elements are required to be used and additional elements could also be included.
The application permissions data associated with an application, also described in greater detail below, can be a single value in an identity field or could include multiple values in the identity field. For example, the application permissions data in the card issuer field could represent both product class A and product class B from a certain Bank X, indicating that the application could be loaded onto cards designated as product classes A and B issued by Bank X (as indicated in the card product ID
field of the card's personalization data).
_g_ SUBSTITUTE SHEET (RULE 26) PCT/GB98/00531 _ In addition, a "global value" could be stored in the issuer field (or other field) of the application permissions data indicating that all IC cards in the system regardless of who issued the card would match this permissions field. In this case, for example, a data value of zero stored in the application permissions card-issuer field will match all of the cards' personalization card-issuer fields.
Figure 1 shows the three steps involved in providing an operational multi-application IC card in a secure system. The first step is the card manufacturing step 101.
The second step is the personalization step 103 where card personalization data (also called entity authentication data) is loaded onto the card. The third step is the application loading step 105 which checks to see if a card is qualified to receive an application, i.e., when the personalization data is checked against the application permissions data associated with the application to be loaded. Each of these three steps is described in detail below.
Card Manufacture Figure 2 shows the steps necessary in manufacturing an IC card in a secure system. Step 20I manufactures the physical IC card by creating the integrated circuit on silicon and placing it on the card. The integrated circuit chip will include RAM, ROM
and EEPROM memories. When the card is first manufactured, a global public key of the system operator (in this case called the Certification Authority (CA)) is stored on each card in ROM in step 203. This will allow the card to authenticate that the source of any message to it is from the CA since the public key on the card will be matched to the CA's secret key.
SUBSTITUTE SHEET (RULE 26) More specifically, this public key stored on the card will allow the individual card to verify data signed with the CA's private key. The public key of the CA, which is stored on the card, is used only for determining if the data sent to the card was signed with the proper CA private key. This allows the card to verify the source of any message coming from the CA.
Step 205 inserts a card enablement key in a secure portion of EEPROM in the card to facilitate card specific confidentiality during enablement, and step 207 inserts a card identifier in EEPROM of the card. The identifier, which can be accessed by any terminal, will allow the system to determine the identity of the card in later processes.
The identifier is freely available and will not be used to authenticate messages.
Step 209 stores the operating system code in ROM on the card including any primitives which are called or supported by the operating system. The primitives are written in native language code (e.g., assembly language) and are stored in ROM. The primitives are subroutines which may be called by the operating system or by applications residing on the card such as mathematic functions (multiply or divide), data retrieval, data manipulation or cryptographic algorithms. The primitives can be executed very quickly because they are written in the native language of the processor.
After the IC cards are manufactured, they are sent to a personalization bureau ("PB") to enable and personalize the card by storing card personalization data in the memory of the card. The terms enablement and personalization are used interchangeably herein to indicate the preparatory steps taken to allow the card to be loaded securely with SUBSTITUTE SHEET (RULE 26) an application. The individual cards are preferably manufactured in batches and are sent to a personalization bureau in a group for processing.
C'~rd Enablement~ersonalization Figure 3 shows the steps of the card enablement process when the card arrives at a personalization bureau. The personalization bureau may be the card issuer (e.g., a bank or other financial institution) or may be a third party that performs the service for the card issuer. The personalization bureau configures the card to a specific user or user class.
Figure 3 specifically shows the steps taken to enable and personalize each I0 IC card which will work within the system. The cards can be placed in a terminal which communicates with IC cards and which reads the card identifier data (previously placed on the card during the manufacturing process -- see step 207). This card identification data is read from the card in step 301. The terminal will effectively send a "get identification data" command to the card and the card will return the identification data to I S the terminal.
The PB typically processes a group of cards at the same time, and will first compile a list of IC card identif cation data for the group of cards it is personalizing. The PB then sends electronically (or otherwise) this list of identification data to the Certification Authority ("CA") which creates a personalization (or enablement) data 20 block for each card identifier. The data block includes the card personalization data organized in a number of identity fields and an individual key set for the card, discussed below. These data blocks are then encrypted and sent to the PB in step 302. By using the SUBSTITUTE SHEET (RULE 26) WO 9/37526 PCT/GB98/00531 _ card identification data, the PB then matches the cards with the encrypted data blocks and separately loads each data block onto the matched card. To insure that the CA
controls the identity of the card and the integrity of the system, the PB never obtains knowledge of the content of the data blocks transferred. Some aspects of the personalization are requested by the card issuer to the CA in order to affect their preferred management of the cards they issue. The following additional steps are performed.
Step 303 first checks to see if an enablement bit stored in EEPROM of the card has been already set. If it already has been set, the card has already been configured and personalized and the enablement process will end as shown in step 304. A
card cannot be enabled and personalized twice. If the bit has not been set, then the process continues with step 305.
In step 305, the individualized card key set for the card being enabled (which key set is generated at the CA) is stored on the card. The keys can be used later in off card verification (i.e., to verify that the card is an authentic card).
This verification is necessary to further authenticate the card as the one for which the application was intended.
Step 307 generates four different MULTOS Security Manager (MSM) characteristic data elements (otherwise referred to herein as personalization data) for the card at the CA which are used for securely and correctly loading and deleting applications from a particular card. The MSM characteristics also allow for the loading of applications on specific classes of identified cards. (These MSM
characteristics are further described in connection with Figure 5.) SUBSTITUTE SHEET (RULE 26) Other data can also be stored on the card at this time as needed by the system design such as an address table or further subroutines.
Step 311 sets the enablement bit in EEPROM of the card which indicates that the enablement process has been completed for the particular card. When this bit is set, another enablement process cannot occur on the card. This ensures that only one personalization and enablement process will occur to the card thus preventing illegal tampering of the card or altering the card by mistake. in the preferred embodiment, the enablement bit is initially not set when the card is manufactured and is set at the end of the enablement process.
Figure 4 shows an example of a block diagram of an IC card chip which has been manufactured and personalized. The IC card chip is located on an IC
card for use. The IC card preferably includes a central processing unit 401, a RAM 403, a EEPROM 405, a ROM 407, a timer 409, control logic 411, an I/O ports 413 and security circuitry 415, which are connected together by a conventional data bus.
Control logic 411 in memory cards provides sufficient sequencing and switching to handle read-write access to the card's memory through the input/output ports. CPU 401 with its control logic can perform calculations, access memory locations, modify memory contents, and manage input/output ports. Some cards have a coprocessor for handling complex computations like cryptographic algorithms. Input/output ports 413 are used under the control of a CPU and control logic alone, for communications between the card and a card acceptance device. Timer 409 (which generates or provides a clock pulse) drives the control logic 411 and CPU 401 through the sequence of steps that SUBSTITUTE SHEET (RULE 26) accomplish memory access, memory reading or writing, processing, and data communication. A timer may be used to provide application features such as call duration. Security circuitry 415 includes fusible links that connect the input/output lines to internal circuitry as required for testing during manufacture, but which are destroyed ("blown") upon completion of testing to prevent later access. The personalization data to qualify the card is stored in a secured location of EEPROM 405. The comparing of the personalization data to applications permissions data is performed by the CPU
401.
Figure ~ shows the steps of generating and loading the four elements of the card personalization data into the memory of the IC cards, and Fig. SA
shows a schematic of bit maps for each identity field residing in the memory of an IC
card containing personalization data in accordance with the present invention. Each data structure for each identity field has its own descriptor code. Step 501 loads the data structure for the identity field "card ID" called "msm mcd_permissions mcd no." This nomenclature stands for MULTOS system manager _ MULTOS card device _ I S permissions_ MULTOS card device number. Although this number is typically 8 bytes long as shown in Fig. SA, the data could be any length that indicates a unique number for the card. In the preferred embodiment, 2 bytes are dedicated as a signal indicator, 2 bytes comprise a MULTOS Injection Security Module )D (MISM >D) indicating which security module injected the card with its injected keys when it was manufactured, and 4 bytes comprise an Integrated Circuit Card (ICC) serial number which identifies the individual card produced at the particular MISM.
SUBSTITUTE SHEET (RULE 26) Step 503 loads the data structure for the identity field "issuer ID" called "msm mcd_permissions_ mcd issuer id." This nomenclature stands for a_ MLJLTOS
card device issuer identification number. Each card issuer (such as a particular bank, financial institution or other company involved with an application) will be assigned a unique nurnber in the card system. Each IC card in the MULTOS system will contain information regarding the card issuer which personalized the card or is responsible for the card. A card issuer will order a certain number of cards from a manufacturer and perform or have performed the personalization process as described herein. For example, a regional bank may order 5,000 cards to be distributed to its customers. The "mcd issuer id" data structure on these cards will indicate which issuer issued the cards.
In the preferred embodiment, the data structure is 4 bytes long (as shown in Fig. SA at 503A) to allow for many different issuers in the system although the length of the data structure can vary with the needs of the card system.
Step 505 loads the data structure for the identity field "product ID" called "msm-mcd~ermissions mcd_ issuer_product id." This nomenclature stands for MULTOS card device issuer product identification number. Each card issuer may have different classes of products or cards which it may want to differentiate. For example, a bank could issue a regular credit card with one product ID, a gold credit card with another product ID and a platinum card with still another product 1D. The card issuer may wish to load certain applications onto only one class of credit cards. A gold credit card user who pays an annual fee may be entitled to a greater variety of applications than a regular credit card user who pays no annual fee. The product ID field identifies the card as a SUBSTITUTE SHEET (RULE 26) particular class and will later allow the card issuer to check the product )D
and only load applications onto cards which match the desired class.
Another way to differentiate products is by application type, such as by categorizing the application as financial, legal, medical and/or recreational, or by assigning particular applications to a group of cards. For example, one card issuer may have different loyalty programs available with different companies to different sets of card users. For example, a bank may have an American Airlines~ loyalty program and a British Airways~ loyalty program for different regions of the country dependent on where the airlines fly. The product type allows the issuer to fix the product classification of the card during the personalization process. When loading applications onto the card, the product type identification number on each card will be checked to make sure it matches the type of card onto which the issuer desires to load. The product type data structure is preferably an indexing mechanism (unlike the other personalization data structure) of 8 bits (as shown at SOSA in Fig. SAl but could be any length depending upon the needs of the card system. In the illustrated embodiment, the resulting instruction would be to locate the second bit (since the byte's indicated value is 2) in the array to be searched (see discussion of step 809 below).
Step 507 loads the data structure for the identity field data called "msm_mcd,~ermissions mcd_ controls data date." This nomenclature stands for the MIJLTOS card device controls data date or, in other words, the date on which the card was personalized so that, for example, the application loader can load cards dated only after a certain date, load cards before a certain date (e.g., for application updates) or load SUBSTITUTE SHEET (RULE 26) cards with a particular data date. The information can include the year, month and day of personalization or may include less information, if desired. The data date data structure is preferably 1 byte in length (see 507A in Fig. SA) although it could be any length depending upon the needs of the particular card system used.
Once all of the personalization data structures are loaded and stored in the card, the card has been identified by issuer, product class, date and identification number (and other data fields, if desired), and the card cannot change its identity;
these fields cannot be changed in the memory of the card. If a card user wants to change the product id stored in the card to gain access to different applications available to another product type, a new card will have to be issued to the user containing the correct personalization data. This system is consistent with a gold card member receiving a new card when the classification is changed to platinum.
After the card has been enabled and personalized by storing its individual card key set, MSM personalization characteristics and enablement bit as described in Fig.
3, the card is ready to have applications loaded into its memory.
Loading A2nlicationc The application loading process contains a number of security and card configuration checks to ensure the secure and proper loading of an application onto the intended IC card. The application loading process is preferably performed at the personalization bureau so that the card will contain one or more applications when the card is issued. The card may contain certain common applications which will be present on every card the issuer sends out, such as an electronic purse application or a creditldebit SUBSTITUTE SHEET (RULE 26) application. Alternatively, the personalization bureau could send the enabled cards to a third party for the process of loading applications. The multiple application operating system stored in the ROM of each card and the card MSM personalization data is designed to allow future loading and deleting of applications after the card has been issued depending upon the desires of the particular card user and the responsible card issuer. Thus, an older version of an application stored on the IC card could be replaced with a new version of the application. An additional loyalty application could also be added to the card after it has been initially sent to the card user because the application is newly available or the user desires to use the new application. These loading and deleting functions for applications can be performed directly by a terminal or may be performed over telephone lines, data tines, a network such as the Internet or any other way of transmitting data between two entities. In the present IC card system, the process of transmitting the application program and data ensures that only IC cards containing the proper personalization data and which fit on application permissions profile will be qualif ed and receive the corresponding application program and data.
Figure 6 shows the preferred steps performed in loading an application onto an IC card in the MLTLTOS IC card system. For this example, the personalization bureau is loading an application from a tenninal which enabled the same card.
Step 601 performs an "open command" initiated by the terminal which previews the card to make sure the card is qualified to accept the loading of a specific application.
The open command provides the card with the application's permissions data, the application's size, and instructs the card to determine ( 1 ) if the enablement bit is set indicating the card SUBSTITUTE SHEET (RULE 26) has been personalized; (2) whether the application code and associated data will fit in the existing memory space on the card; and (3) whether the personalization data assigned to the application to be loaded allows for the loading of the application onto the particular card at issue. The open command could also make additional checks as required by the S card system. These checking steps during the open command execution will be described in detail in conjunction with Figure 7.
After the open command has been executed, the application loader via the terminal will be advised if the card contains the proper identification personalization data and if enough room exists in the memory of the card for the application code and related data. If there is insufficient memory, then a negative response is returned by the card and the process is abended (abnormally ended). If the identification personalization data does not match the applications permissions data, a warning response is given in step 603, but the process continues to the load and create steps. Alternatively, if there is no match, the process may automatically be abended. If a positive response is returned by the card to the terminal in step 605, the application loader preferably proceeds to next steps. The open command allows the application to preview the card before starting any transfer of the code and data.
Step 607 then loads the application code and data onto the IC card into EEPROM. The actual loading occurs in conjunction with create step 609 which completes the loading process and enables the application to execute on the IC
card after it is loaded. The combination of the open, load and create commands are sent by the terminal. or another application provider source, to the IC card to perform the application SUBSTITUTE SHEET (RULE 26) loading process. The operating system in the IC cards is progtarnrrled to perform a specific set of instructions with respect to each of these commands so that the IC card will communicate with and properly carry out the instructions from the terminal.
Step 609 performs the create command which at least: ( 1 ) checks if an application load certificate is signed (encrypted) by the CA and therefore authenticates the application as a proper application for the system; and (2) checks the card personalization data stored on the card against the permissions profile for the application to be loaded to qualify the card for loading. It may do other checks as required. If one of the checks fails, then a failure response 610 is given and the process aborts.
The application after it has passed these checks will be loaded into the memory of the card.
Figure 7 shows the various steps of the open step 601 of Fig. 6 in more detail. Step 701 determines if the enablement (i.e., control) bit is set. This bit is set when the card has completed its personalization process and has been assigned its personalization data. An application can be loaded on an IC card in the card system only if the card contains the personalization data. If the enablement bit is not set, the card has not been personalized and therefore the card returns a negative response 703 to the terminal. If the enablement bit is set, then the card has been enabled and the test conditions continue with step 711.
Step 711 checks if there is sufficient space in the memory on the card to store the application code and its associated data. Applications will typically have associated data related to their fimctions. This data will be used and manipulated when the application is run. Storage space in the memory of an IC card is a continuing concern SUBSTITUTE SHEET (RULE 26) due to the relatively large physical space required for EEPROM and how it fits in the integrated circuit which is desired to be small enough to fit on a credit card sized card.
An example of the size of a preset EEPROM on an IC card is 16K bytes although the actual size varies. Applications can range from 1K byte or less for a very simple applicatior. up to the size of available memory for a more sophisticated application. The data associated with an application can range from no data being stored in the card memory to a size constrained by the amount of available memory. These varied sizes of application code and data continually increase as applications become more advanced and diverse.
MULTOS as an operating system is not limited by the number of applications and associated data it can store on the card. Thus, if five applications can fit in the available memory of the card, the card user will have greatly increased fiutctionality than if one or two applications were stored on the card. Once a card's memory is filled to its capacity, however, a new application cannot be loaded onto the card unless another application including its code and data of sufficient size can be deleted. Therefore, checking the amount of available space on the card is an important step. If there is not sufficient space, then an insufficient space response 713 will be returned to the terminal. The application loader can then decide if another existing application on the card should be deleted to make room for the new application. Deletion depends upon the card issuer having an application delete certificate from the CA. If there is sufficient space on the card, then the process continues with step 715.
SUBSTITUTE SHEET (RULE 26) An example of the testing of memory spaces in step 711 is now described.
The numbers used in this example in no way limit the scope of the invention but are used only to illustrate memory space requirements. An IC card may have 16K
available EEPROM when it is first manufactured. The operating system data necessary for the operating system may take up 2K of memory space. Thus, 14K would remain. An electronic purse application's code is stored in EEPROM and may take up 8K of memory space. The purse application's required data may take up an additional 4K of memory space in EEPROM. The memory space which is free for other applications would thus be 2K (16K-2K-8K-4K=2K). If a card issuer wants to load a credit/debit application whose code is 6K bytes in size onto the card in this example, the application will not fit in the memory of the IC card. Therefore, the application cannot load the new application without first removing the purse application from the card. If a new credit/debit application was loaded into EEPROM of the IC card, then it would have to overwrite other application's code or data. The application loader is prevented from doing this.
Figure 8 shows the steps performed in determining whether the card's personalization data falls within the permissible set of cards onto which the application at issue may be loaded. These steps are preferably performed during the execution of the "create" command. However, these steps may be performed at any time during the loading or deleting of an application. As described previously, the card is personalized by storing data specific to the card (MSM personalization data) including: a card ID
designation specific to an individual card, the card issuer number indicating the issuer of the card, the product type of the card, such as a gold or platinum card, and the date the SUBSTITUTE SHEET (RULE 26) card was personalized. This data uniquely identifies the card apart from all other IC cards in the system.
Accordingly, applications can be selectively stored on individual cards in the IC card system on virtually any basis, including the following. An application can be loaded selectively to cards containing one or more specific card numbers. An application can be selectively loaded on one or more cards containing a specified card issuer ID.
Moreover, an application can be loaded only upon one type of product specified by the particular card issuer, and/or the application can be loaded only on cards which have a specified date or series of dates of personalization. Each of the personalization data allows an application to be selectively loaded onto certain cards or groups of cards and also ensures that cards without the proper permissions will not receive the application.
Personalization data types in addition to the four described can also be used as needed.
The selection of IC cards upon which a particular application may be loaded is made possible by the use of "applications permissions data" which is assigned to the application and represents at least one set of cards upon which the application may be loaded. The set may be based on virtually any factor, including one or more of the following: card numbers, card issuers, product types or personalization dates.
Although the individual card's personalization data typically identify one specific number, one card issuer, one product type and one date, the application's permissions data may indicate a card numbers or a blanket permission, a card issuer or a blanket permission, and a number of product types and dates.
SUBSTITUTE SHEET (RULE 26) For example, a frequent loyalty program may be configured to allow its loading and use on cards in different product classes belonging to one card issuer. In addition, the application permissions data may indicate that the loyalty program can be used on gold and platinum product types if the card was issued after May, 1998. Thus, the MSM permissions check will determine if the card's individual personalization data is included in the allowed or permissible set of cards upon which the application may be loaded. If it is, the application will be loaded.
To expedite the comparison process, an alternative embodiment may include setting one or more permissions data at zero representing a blanket permission for that particular data. For instance, by placing a zero for the "card number"
entry in the application permissions data or some other value indicating that alt cards may be loaded regardless of their number, the system knows not to deny any cards based on their card number. Moreover, if a zero is placed in the application's permissions data "issuer m,"
then all cards similarly will pass the "issuer" test comparison. This feature allows greater flexibility in selecting groups of cards. The zero indicator could also be used for other permissions data, as required.
Referring to Figure 8, each of the permissions data is checked in the order shown, bat other orders could be followed because if any one of the permissions fails, the application will be prevented from being loaded on the IC card being checked.
The permissions are preferably checked in the order shown. Step 801 checks if the application permissions product type set encompasses the card's product type number stored in the memory of the card. Each card product type is assigned a number by the SUBSTITUTE SHEET (RULE 26) system operator. The product types are specified for each card issuer because different card issuers will have different product types. The cards are selectively checked to ensure that applications are loaded only on cards of authorized product type. The application permissions product type set can be 32 bytes long which includes multiple acceptable product types or can be a different length depending upon the needs of the system. Using data structure SOSA as an example, the operating system would check bit number 2 in the 256 bit array (32 bytes x 8 bits per byte) resulting from the 32 byte long application permissions data structure. if the permissions check fails, then the card returns a failure message to the terminal instep 803. If the product type check passes (for example, the value of bit no. 2 being 1 ), then the process continues with step 805.
Step 805 checks if the application permissions allowable card issuer number set encompasses the card's issuer number stored in the memory of the card or if the application permissions issuer data is zero (indicating all cards pass this individual permissions check). Each card issuer is assigned a number by the system operator and the cards are selectively checked to ensure that applications are loaded only on cards distributed by authorized card issuers. The application permissions card issuer number set can be 4 bytes long if one issuer is designated or can be longer depending upon the needs of the system. If the issuer check fails, then the card returns a failure message to the terminal in step 807. If the check passes, then the process continues with step 809.
Step 809 checks if the application permissions date set encompasses the card's data date stored in the memory of the card. The date that the IC card was personalized will be stored and will preferably include at least the month and year. The SUBSTITUTE SHEET (RULE 26) WO 98!37526 PCT/GB98/00531 cards are selectively checked to ensure that applications are loaded only on cards with the authorized personalization date. The application permissions date set can be 32 bytes long which includes multiple dates or can be a different length depending upon the needs of the system. If the date permissions check fails, then the card returns a failure message to the terminal in step 811. If the date check passes, then the process continues with step 813.
Step 813 checks if the application permissions allowable card number set encompasses the card's 117 number stored in the card memory or if the application permissions allowable card number data is zero (indicating all cards pass this individual permissions check). The testing of the permissions is performed on the card during the execution of the open, load and create commands. The application permissions card number data set can be 8 bytes long if one number is designated or can be longer depending upon the needs of the system. If the card number check fails, then the card returns a failure message to the terminal in step 815. If the check passes, then the process continues with step 817.
~mmaly,of IC Card ~rstem's Process Figure 9 shows the components of the system architecture for the card initialization process of an IC card in a secure multiple application IC card system. The system includes a card manufacturer 102, a personalization bureau I04, an application loader 106, the IC card 107 being initialized, the card user 109 and the certification authority 11 I for the entire multiple application secure system. The card user 131 is the SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ person or entity who will use the stored applications on the IC card. For example, a card user may prefer an IC card that contains both an electronic purse containing electronic cash (such as MONDEXTM) and a credit/debit application (such as the MasterCard~
EMV application) on the same IC card. The following is a description of one way in which the card user would obtain an IC card containing the desired applications in a secure manner.
The card user would contact a card issuer 113, such as a bank which distributes IC cards, and request an IC card with the two applications both residing in memory of a single IC card. The integrated circuit chip for the IC card would be manufactured by manufacturer 102 and sent to the card issuer 1 I3 (or an entity acting on its behalf) in the form of an IC chip on a card. As discussed above (see steps 201-209), during the manufacturing process, data is transmitted 115 via a data conduit from the manufacturer I 02 to card 107 and stored in IC card 10Ts memory. (Any of the data conduits described in this figure could be a telephone line, Internet connection or any other transmission medium.) The certification authority 111, which maintains encryptionldecryption keys for the entire system, transmits 117 security data (i.e., global public key) to the manufacturer over a data conduit which is placed on the card by the manufacturer along with other data, such as the card enablement key and card identifier.
The card's multiple application operating system is also stored in ROM and placed on the card by the manufacturer. After the cards have been initially processed, they are sent to the card issuer for personalization and application loading.
SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ The card issuer 113 performs, or has performed by another entity, two separate functions. First, the personalization bureau 104 personalizes the IC
card 107 in the ways described above, and second, the application loader 106 loads the application provided the card is qualified, as described.
Regarding personalization, an individualized card key set is generated by the CA and stored on the card (see Fig. 3). The card is further given a specific identity using MSM personalization (see Fig. 3, step 307 and Fig. 5) including a card )D number, an issuer ID number identifying the card issuer which processed the card, a card product type number which is specified by the card issuer and the date upon which the personalization took place. After the card has been personalized, applications need to be loaded onto the card so that the card can perform desired functions.
The application loader 106, which could use the same terminal or data conduit as persanalization bureau 104, first needs to have determined if the card is qualified to accept the application. This comparison process takes place on the card itself (as instructed by its operating system) using the permissions information. The card, if it is qualified, thus selectively loads the application onto itself based upon the card's identity and the card issuer's instructions. The application loader communicates 119 with the IC card via a terminal or by some other data conduit. After the applications have been loaded on the card, the card is delivered to the card user 109 for use.
The secure multiple application IC card system described herein allows for selective loading and deleting of applications at any point in the life cycle of the IC card after the card has been personalized. Thus, a card user could also receive a personalized SUBSTITUTE SHEET (RULE 26) card with no applications and then select a desired application over a common transmission line such as a telephone line or Internet connection.
Figure 10 is a system diagram of entities involved with the use of an IC
card once it has been personalized. The system includes an IC card 151, a terminal 153, S an application load/delete entity 155, the certification authority 157, a card issuer 171 and other IC cards 159 in the system. The arrows indicate communication between the respective entities. The CA 157 facilitates loading and deleting of applications. After providing the MSM permissions data and card specific keyset to the card during card enablements, the CA allows applications to be later loaded and deleted preferably by issuing an application certificate. Application specific keys are required to authenticate communication between a card and terminal. The IC card I51 also can communicate with other IC cards 159. Card issuer I71 is involved with all decisions of loading and deleting applications for a card which it issued. All communications are authenticated and transmitted securely in the system.
For instance, IC card 151 will use the following procedure to load a new application onto the card. IC card 1 O1 is connected to terminal 153 and the terminal requests that an application be loaded. Terminal 153 contacts application load/delete entity 155 which, as a result and in conjunction with card issuer I71, sends the application code, data and application permissions data (along with any other necessary data) to terminal 153. Terminal 153 then queries card I51 to ensure it is the correct card onto which the application may be loaded. If IC card passes the checks discussed above, the application is loaded onto card 151. The CA 157 provides the application load or SUBSTITUTE SHEET (RULE 26) WO 98/37526 PCT/GB98/00531 _ delete certificate that enables the application to be loaded or deleted from the card. This example shows one way to load the application, but other variations using the same principles could be performed, such as directly loading the application at the application load/delete entity 155.
The foregoing merely illustrates the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the invention and are thus within the spirit and scope of the invention.
For example, it will be appreciated that the MSM personalization and permissions data may not only be used for loading applications onto IC cards but also for deleting applications from said cards. The same checks involving MSM
permissions and loading applications are made for deleting applications. A delete certificate from the CA
authorizing the deletion of an application will control from which cards the application may be deleted. This is accomplished through the personalization data stored on each IC
card and the permissions check as described herein.
Moreover, the data may also be applicable to personal computers or other units onto which applications may be loaded which are not physically loaded on cards. In addition, the application's permissions data may actually include data representative of a set or sets of cards to be excluded, instead of included -- cards that cannot be loaded with the application.
SUBSTITUTE SHEET (RULE 26) The scope of the present disclosure includes any novel feature or combination of features disclosed therein either explicitly or implicitly or any generalisation thereof irrespective of whether or not it relates to the claimed invention or mitigates any or all of the problems addressed by the present invention. The applicant hereby gives notice that new claims may be formulated to such features during the prosecution of this application or of any sucli further application dernred therefrom In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims in any appropriate manner and not merely in the specific combinations enumerated in the claims.
SUBSTITUTE SHEET (RULE 26)
Claims (27)
1. An IC card system comprising at least one IC card, an application to be loaded onto said card and means for determining whether said card is qualified to accept the loading of said application onto said card, wherein said IC
card contains card personalization data, and said application is assigned application permissions data representing at least one set of IC cards upon which said application may be loaded and wherein said determining means compares said card personalization data with said application permissions data and wherein said application is loaded onto said IC card in dependence on the result of said comparison.
card contains card personalization data, and said application is assigned application permissions data representing at least one set of IC cards upon which said application may be loaded and wherein said determining means compares said card personalization data with said application permissions data and wherein said application is loaded onto said IC card in dependence on the result of said comparison.
2. The IC card system of claim 1, wherein said personalization data comprises data representative of a unique card identification designation.
3. The IC card system of any one of claims 1 or 2, wherein said personalization data comprises data representative of a card issuer.
4. The IC card system of any one of claims 1 to 3, wherein said personalization data comprises data representative of a product class.
5. The IC card system of any one of claims 1 to 4, wherein said personalization data comprises data representative of a date.
6. The IC card system of any one of claims 1 to 5, wherein said permissions data set includes one or more issuers of IC cards.
7. The IC card system of any one of claims 1 to 6, wherein said permissions data set includes one or more product classes.
8. The IC card system of any one of claims 1 to 7, wherein said permissions data set includes a plurality range of dates.
9. The IC card system of any one of claims 1 to 8, wherein said permissions data set includes all IC cards which attempt to load the application.
10. The IC card system of any one of claims 1 to 9, further comprising means for enabling said card to be loaded with said application.
11. The IC card system of claim 10, wherein said enabling means comprises means for storing personalization data onto said card.
12. The IC card system of claim 10, wherein said enabling means comprises means for setting an enablement bit.
13. The IC card system of claim 11, wherein said enabling means comprises means for setting an enablement bit.
14. The IC card system of clean 33, further comprising means for checking the enablement bit prior to enabling said IC card to determine whether or not said card has already been enabled.
15. The IC card system of claim 14, further comprising means for checking the enablement bit prior to enabling said card has already been enabled.
16. A process for loading an application onto an IC
card comprising the step of determining whether said IC card is qualified to accept the loading of said application onto the said card, wherein said determining step includes the steps of:
providing said card with personalization data;
assigning to said application permissions data representing at least one set of IC cards upon which said application may be loaded;
comparing said personalization data with said permissions data; and loading said application onto said IC card provided in dependence in the result of the comparison.
card comprising the step of determining whether said IC card is qualified to accept the loading of said application onto the said card, wherein said determining step includes the steps of:
providing said card with personalization data;
assigning to said application permissions data representing at least one set of IC cards upon which said application may be loaded;
comparing said personalization data with said permissions data; and loading said application onto said IC card provided in dependence in the result of the comparison.
17. The process of claim 16, further comprising the first step of enabling said card to be loaded with said application.
18. The process of claim 17, wherein said enabling step includes the step of storing personalization data onto said card.
19. The process of claim 18, wherein said enabling step includes the step of setting an enablement bit indicating that the card has been enabled.
20. The process of claim 19, wherein said enabling step further includes the step of setting an enablement bit indicating that the card has been enabled.
21. The process of claim 20, wherein prior to said enabling step a checking step is performed to determine whether said card has been enabled.
22. A process for deleting an application from an IC
card comprising the step of determining whether said IC card is qualified to delete said application based upon permissions data associated with said application, wherein said determining step includes the steps of:
providing said card with personalization data;
assigning to said application permissions data representing at least one set of IC cards from which said application may be deleted;
comparing said personalization data with said permissions data; and deleting said application from said IC card provided said personalization data falls within said set of cards from which said application may be deleted.
card comprising the step of determining whether said IC card is qualified to delete said application based upon permissions data associated with said application, wherein said determining step includes the steps of:
providing said card with personalization data;
assigning to said application permissions data representing at least one set of IC cards from which said application may be deleted;
comparing said personalization data with said permissions data; and deleting said application from said IC card provided said personalization data falls within said set of cards from which said application may be deleted.
23. The process of claim 16, wherein said personalization data comprises data representative of a card identification designation.
24. The process of claim 16, 22 or 23, wherein said personalization data comprises data representative of a card issuer.
25. The process of any one of claims 16 or 22 to 24, wherein said personalization data comprises data representative of a product class.
26. The process of any one of claims 16 or 22 to 25, wherein said personalization data further comprises data representative of a date.
27. An IC card system comprising at least one IC card, an application to be deleted from said card and means for determining whether said card is qualified to delete said application from said card, wherein said IC card contains card personalization data, and said application is assigned an application permissions data set representing at least one set of IC cards from which said application may be deleted, wherein said determining means compares said card personalization data with said application permissions data, and whether said application is deleted from said IC card depends on the result of said comparison, such that in the event the card personalization data matches said permissions data set the card is qualified and the application is deleted.
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GBGB9703591.9A GB9703591D0 (en) | 1997-02-21 | 1997-02-21 | Multiple application computer system |
GB9703591.9 | 1997-02-21 | ||
US4651497P | 1997-05-15 | 1997-05-15 | |
US60/046,514 | 1997-05-15 | ||
US09/023,057 US6575372B1 (en) | 1997-02-21 | 1998-02-12 | Secure multi-application IC card system having selective loading and deleting capability |
PCT/GB1998/000531 WO1998037526A1 (en) | 1997-02-21 | 1998-02-19 | Multi-application ic card system |
US09/023,057 | 1998-05-12 |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2281576A1 CA2281576A1 (en) | 1998-08-27 |
CA2281576C true CA2281576C (en) | 2004-11-30 |
Family
ID=27268738
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002281576A Expired - Lifetime CA2281576C (en) | 1997-02-21 | 1998-02-19 | Multi-application ic card system |
Country Status (8)
Country | Link |
---|---|
US (2) | US6575372B1 (en) |
EP (1) | EP0963580B1 (en) |
JP (2) | JP2001513231A (en) |
AR (1) | AR011449A1 (en) |
AU (1) | AU736325B2 (en) |
CA (1) | CA2281576C (en) |
DE (1) | DE69823649T2 (en) |
WO (1) | WO1998037526A1 (en) |
Families Citing this family (93)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DK0757336T3 (en) | 1995-08-04 | 2001-03-19 | Belle Gate Invest B V | Data Exchange System comprising portable data processing units |
US6317832B1 (en) * | 1997-02-21 | 2001-11-13 | Mondex International Limited | Secure multiple application card system and process |
FR2775375A1 (en) * | 1998-02-23 | 1999-08-27 | Solaic Sa | Loading processing programs by blocks into memory of portable devices and avoiding loss of time when contact with an emitter is lost. Particularly applicable to contactless devices |
US7636694B1 (en) * | 1998-09-18 | 2009-12-22 | Mastercard International Incorporated | Apparatus and method for generating an electronic-commerce personal identification number cryptographically related to an ATM personal identification number |
CA2345794A1 (en) | 1998-09-29 | 2000-04-06 | Sun Microsystems, Inc. | Superposition of data over voice |
US6633984B2 (en) | 1999-01-22 | 2003-10-14 | Sun Microsystems, Inc. | Techniques for permitting access across a context barrier on a small footprint device using an entry point object |
US6581206B2 (en) * | 1999-11-12 | 2003-06-17 | Sun Microsystems, Inc. | Computer program language subset validation |
US7093122B1 (en) | 1999-01-22 | 2006-08-15 | Sun Microsystems, Inc. | Techniques for permitting access across a context barrier in a small footprint device using shared object interfaces |
US6922835B1 (en) | 1999-01-22 | 2005-07-26 | Sun Microsystems, Inc. | Techniques for permitting access across a context barrier on a small footprint device using run time environment privileges |
ATE475139T1 (en) | 1999-06-10 | 2010-08-15 | Belle Gate Invest B V | DEVICE FOR STORING DIFFERENT VERSIONS OF DATA SETS IN SEPARATE DATA AREAS AND METHOD FOR UPDATE A DATA SET IN A MEMORY |
US7716080B2 (en) * | 1999-06-23 | 2010-05-11 | Signature Systems, Llc | Method and system for using multi-function cards for storing, managing and aggregating reward points |
DE19929164A1 (en) * | 1999-06-25 | 2001-01-11 | Giesecke & Devrient Gmbh | Method for operating a data carrier designed for executing reloadable function programs |
FR2797968B1 (en) * | 1999-08-24 | 2001-10-12 | Schlumberger Systems & Service | DEVICE AND METHOD FOR LOADING CONTROLS IN AN INTEGRATED CIRCUIT CARD |
DE19947986A1 (en) * | 1999-10-05 | 2001-04-12 | Ibm | Method of downloading of application parts via distributed systems on to a chip-card, requires provision of secret code or session key by the server prior to loading command-sequence of commands for downloading |
GB9925227D0 (en) | 1999-10-25 | 1999-12-22 | Internet Limited | Data storage retrieval and access system |
US6876991B1 (en) | 1999-11-08 | 2005-04-05 | Collaborative Decision Platforms, Llc. | System, method and computer program product for a collaborative decision platform |
US7158993B1 (en) | 1999-11-12 | 2007-01-02 | Sun Microsystems, Inc. | API representation enabling submerged hierarchy |
JP4398619B2 (en) * | 1999-11-30 | 2010-01-13 | 株式会社東芝 | IC card and management method of volatile memory in the IC card |
DE19958559A1 (en) * | 1999-12-04 | 2001-06-07 | Orga Kartensysteme Gmbh | Method for initializing and / or personalizing chip cards and a corresponding device |
AU1586500A (en) | 1999-12-06 | 2001-06-12 | Sun Microsystems, Inc. | Computer arrangement using non-refreshed dram |
DE69932643T2 (en) | 1999-12-07 | 2007-04-05 | Sun Microsystems, Inc., Santa Clara | IDENTIFICATION DEVICE WITH SECURED PHOTO, AND METHOD AND METHOD FOR AUTHENTICATING THIS IDENTIFICATION DEVICE |
US7493497B1 (en) * | 2000-02-03 | 2009-02-17 | Integrated Information Solutions | Digital identity device |
WO2001061659A1 (en) * | 2000-02-16 | 2001-08-23 | Mastercard International Incorporated | System and method for conducting electronic commerce with a remote wallet server |
US6651186B1 (en) | 2000-04-28 | 2003-11-18 | Sun Microsystems, Inc. | Remote incremental program verification using API definitions |
US6986132B1 (en) | 2000-04-28 | 2006-01-10 | Sun Microsytems, Inc. | Remote incremental program binary compatibility verification using API definitions |
US6883163B1 (en) | 2000-04-28 | 2005-04-19 | Sun Microsystems, Inc. | Populating resource-constrained devices with content verified using API definitions |
US20020040438A1 (en) * | 2000-05-05 | 2002-04-04 | Fisher David Landis | Method to securely load and manage multiple applications on a conventional file system smart card |
US6981245B1 (en) | 2000-09-14 | 2005-12-27 | Sun Microsystems, Inc. | Populating binary compatible resource-constrained devices with content verified using API definitions |
JP2002117376A (en) * | 2000-10-04 | 2002-04-19 | Fujitsu Ltd | Copyright information inquiry device |
US20020044655A1 (en) * | 2000-10-18 | 2002-04-18 | Applebaum David C. | Information appliance and use of same in distributed productivity environments |
US7398225B2 (en) * | 2001-03-29 | 2008-07-08 | American Express Travel Related Services Company, Inc. | System and method for networked loyalty program |
US20030135471A1 (en) * | 2000-12-22 | 2003-07-17 | Jean-Luc Jaquier | Match control method |
US20020087662A1 (en) * | 2000-12-29 | 2002-07-04 | Stephane Bouet | System and method for selective updating of media files |
JP2002305250A (en) * | 2001-02-02 | 2002-10-18 | Matsushita Electric Ind Co Ltd | Semiconductor integrated circuit and business method concerning semiconductor circuit |
WO2003015021A1 (en) * | 2001-08-03 | 2003-02-20 | Dai Nippon Printing Co., Ltd. | Multi-application ic card |
US7275260B2 (en) | 2001-10-29 | 2007-09-25 | Sun Microsystems, Inc. | Enhanced privacy protection in identification in a data communications network |
US7085840B2 (en) | 2001-10-29 | 2006-08-01 | Sun Microsystems, Inc. | Enhanced quality of identification in a data communications network |
US7496751B2 (en) | 2001-10-29 | 2009-02-24 | Sun Microsystems, Inc. | Privacy and identification in a data communications network |
US7243853B1 (en) | 2001-12-04 | 2007-07-17 | Visa U.S.A. Inc. | Method and system for facilitating memory and application management on a secured token |
JP3727907B2 (en) * | 2002-06-28 | 2005-12-21 | 株式会社東芝 | Issuing system and issuing method for portable electronic medium and portable electronic medium |
NO20023194D0 (en) * | 2002-07-01 | 2002-07-01 | Sospita As | Method and apparatus for executing software applications in a multiprocessor environment |
ATE318034T1 (en) * | 2002-09-16 | 2006-03-15 | SECURE MANUFACTURING PROCESS | |
CN1682488B (en) | 2002-09-16 | 2010-11-03 | 艾利森电话股份有限公司 | Loading data onto an electronic device |
US20040139021A1 (en) | 2002-10-07 | 2004-07-15 | Visa International Service Association | Method and system for facilitating data access and management on a secure token |
JP4557969B2 (en) * | 2003-03-31 | 2010-10-06 | エヌエックスピー ビー ヴィ | How to grant smart card change rights |
US20040249710A1 (en) * | 2003-05-16 | 2004-12-09 | David Smith | Methods and apparatus for implementing loyalty programs using portable electronic data storage devices |
EP1492061A1 (en) * | 2003-06-25 | 2004-12-29 | Nagracard S.A. | A method for allocation of secure resources in a security module |
JP4496771B2 (en) * | 2003-12-19 | 2010-07-07 | 株式会社日立製作所 | IC card system and application loading method |
US7165727B2 (en) | 2004-02-24 | 2007-01-23 | Sun Microsystems, Inc. | Method and apparatus for installing an application onto a smart card |
US7191288B2 (en) | 2004-02-24 | 2007-03-13 | Sun Microsystems, Inc. | Method and apparatus for providing an application on a smart card |
US7140549B2 (en) | 2004-02-24 | 2006-11-28 | Sun Microsystems, Inc. | Method and apparatus for selecting a desired application on a smart card |
US7374099B2 (en) | 2004-02-24 | 2008-05-20 | Sun Microsystems, Inc. | Method and apparatus for processing an application identifier from a smart card |
WO2006015617A1 (en) * | 2004-08-13 | 2006-02-16 | Telecom Italia S.P.A. | Method of and system for secure management of data stored on electronic tags |
DE102004040462A1 (en) * | 2004-08-20 | 2006-02-23 | Giesecke & Devrient Gmbh | Authenticated secure access to a volume with mass storage and a chip |
KR100471007B1 (en) * | 2004-08-27 | 2005-03-14 | 케이비 테크놀러지 (주) | Smart card for ensuring an independent nature of security domain |
FR2875949A1 (en) * | 2004-09-28 | 2006-03-31 | St Microelectronics Sa | LOCKING AN INTEGRATED CIRCUIT |
JP4794269B2 (en) * | 2004-11-08 | 2011-10-19 | パナソニック株式会社 | Secure device and relay terminal |
WO2006056669A1 (en) * | 2004-11-25 | 2006-06-01 | France Telecom | Method of securing a telecommunication terminal that is connected to terminal user identification module |
US8083133B2 (en) * | 2005-05-04 | 2011-12-27 | The Western Union Company | System and method for accounting for activation of stored value cards |
FR2888976B1 (en) * | 2005-07-25 | 2007-10-12 | Oberthur Card Syst Sa | ELECTRONIC ENTITY WITH CONTACT AND REMOTE COMMUNICATION MEANS |
US8622292B2 (en) * | 2005-09-29 | 2014-01-07 | Jeffrey Bart Katz | Reservation-based preauthorization payment system |
US9004355B2 (en) * | 2005-09-29 | 2015-04-14 | Cardfree Inc | Secure system and method to pay for a service provided at a reservation |
DE102005052888A1 (en) * | 2005-11-07 | 2007-05-16 | Giesecke & Devrient Gmbh | Portable data storage medium personalizing method, involves receiving response data of processing device from personalization system, and carrying out personalization step based on response data that are determined based on detected data |
FR2896323B1 (en) * | 2006-01-16 | 2008-10-31 | Oberthur Card Syst Sa | METHOD FOR GENERATING A PROFILE FOR CUSTOMIZING AN ELECTRONIC ENTITY AND ASSOCIATED SYSTEM |
US7689250B2 (en) * | 2006-02-01 | 2010-03-30 | General Instrument Corporation | Method, apparatus and system for partitioning and bundling access to network services and applications |
CA2642363C (en) * | 2006-02-28 | 2016-02-02 | Certicom Corp. | System and method for product registration |
EP2016535A4 (en) * | 2006-04-19 | 2010-06-23 | Stepnexus Holdings | Methods and systems for ic card application loading |
US7967194B2 (en) * | 2006-05-17 | 2011-06-28 | Mastercard International Incorporated | Centralized issuer hub for transaction card customization |
US20130139230A1 (en) * | 2006-09-24 | 2013-05-30 | Rfcyber Corporation | Trusted Service Management Process |
US8386349B2 (en) | 2007-02-28 | 2013-02-26 | Visa U.S.A. Inc. | Verification of a portable consumer device in an offline environment |
US8523069B2 (en) * | 2006-09-28 | 2013-09-03 | Visa U.S.A. Inc. | Mobile transit fare payment |
US8738485B2 (en) * | 2007-12-28 | 2014-05-27 | Visa U.S.A. Inc. | Contactless prepaid product for transit fare collection |
US8346639B2 (en) | 2007-02-28 | 2013-01-01 | Visa U.S.A. Inc. | Authentication of a data card using a transit verification value |
US20080203170A1 (en) * | 2007-02-28 | 2008-08-28 | Visa U.S.A. Inc. | Fraud prevention for transit fare collection |
US7527208B2 (en) | 2006-12-04 | 2009-05-05 | Visa U.S.A. Inc. | Bank issued contactless payment card used in transit fare collection |
US8118223B2 (en) | 2006-09-28 | 2012-02-21 | Visa U.S.A. Inc. | Smart sign mobile transit fare payment |
US20080208681A1 (en) * | 2006-09-28 | 2008-08-28 | Ayman Hammad | Payment using a mobile device |
JP4554581B2 (en) * | 2006-09-29 | 2010-09-29 | 株式会社野村総合研究所 | Job management apparatus, system and program |
US11049372B2 (en) | 2007-06-13 | 2021-06-29 | CPI Card Group—Colorado, Inc. | System and methods for generating user interfaces for custom card design session |
US7992774B2 (en) * | 2007-06-13 | 2011-08-09 | Image Asset Management Inc. | System and methods for creating a user customized bank card |
HU230695B1 (en) * | 2007-10-20 | 2017-09-28 | Andrá Vilmos | Method of preparing storing and method of storing single user access information into safe storage unit of a communication device |
US8789753B1 (en) | 2008-03-28 | 2014-07-29 | Oracle International Corporation | Method for using and maintaining user data stored on a smart card |
US8152074B1 (en) | 2008-03-28 | 2012-04-10 | Oracle America, Inc. | Method for preparing by a smart card issuer an anonymous smart card and resulting structure |
US8225386B1 (en) * | 2008-03-28 | 2012-07-17 | Oracle America, Inc. | Personalizing an anonymous multi-application smart card by an end-user |
US8220718B2 (en) * | 2008-09-15 | 2012-07-17 | Vasco Data Security, Inc. | Method for post-manufacturing data transfer to and from a sealed device |
WO2010033228A1 (en) * | 2008-09-18 | 2010-03-25 | Secure Services Corp. | System and methods for biometric identification on smart devices using multos |
US9230259B1 (en) | 2009-03-20 | 2016-01-05 | Jpmorgan Chase Bank, N.A. | Systems and methods for mobile ordering and payment |
KR100961274B1 (en) * | 2009-12-07 | 2010-06-07 | 조정식 | Integrated circuit card of unity |
EP2641208B1 (en) | 2010-11-19 | 2020-04-29 | Nagravision S.A. | Method to detect cloned software |
CN103257853B (en) * | 2012-02-17 | 2016-06-29 | 上海复旦微电子集团股份有限公司 | The synthesis application of a kind of CPU card with multi-application COS realizes method |
FR3019672B1 (en) * | 2014-04-02 | 2018-06-22 | Idemia France | METHOD OF MAKING A SECURITY DEVICE |
US11037123B2 (en) | 2019-01-07 | 2021-06-15 | Visa International Service Association | System, method, and computer program product for customizing functions of a point-of-sale terminal |
US11610188B2 (en) | 2020-04-15 | 2023-03-21 | Capital One Services, Llc | Systems and methods for ATM integrated card fabricator |
Family Cites Families (171)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4218582A (en) | 1977-10-06 | 1980-08-19 | The Board Of Trustees Of The Leland Stanford Junior University | Public key cryptographic apparatus and method |
US4405829A (en) | 1977-12-14 | 1983-09-20 | Massachusetts Institute Of Technology | Cryptographic communications system and method |
US4259720A (en) | 1978-01-09 | 1981-03-31 | Interbank Card Association | Security system for electronic funds transfer system |
US4408203A (en) | 1978-01-09 | 1983-10-04 | Mastercard International, Inc. | Security system for electronic funds transfer system |
US4214230A (en) | 1978-01-19 | 1980-07-22 | Rolf Blom | Personal identification system |
FR2455320B1 (en) | 1979-04-25 | 1986-01-24 | Cii Honeywell Bull | DEVICE FOR RECYCLING IDENTIFIABLE RECORDING MEDIA USING IDENTIFICATION DATA AND NON-VOLATILE DELETE MONOLITHIC MEMORY COMPOUNDS |
US4321672A (en) | 1979-11-26 | 1982-03-23 | Braun Edward L | Financial data processing system |
US4302810A (en) | 1979-12-28 | 1981-11-24 | International Business Machines Corporation | Method and apparatus for secure message transmission for use in electronic funds transfer systems |
US4305059A (en) | 1980-01-03 | 1981-12-08 | Benton William M | Modular funds transfer system |
FR2480539B1 (en) | 1980-04-09 | 1985-09-13 | Cii Honeywell Bull | METHOD AND SYSTEM FOR TRANSMITTING SIGNED MESSAGES |
US4341951A (en) | 1980-07-02 | 1982-07-27 | Benton William M | Electronic funds transfer and voucher issue system |
FR2497617B1 (en) | 1981-01-07 | 1989-08-18 | Transac Develop Transactions A | SECURITY METHOD AND DEVICE FOR TRIPARTITY COMMUNICATION OF CONFIDENTIAL DATA |
US4578530A (en) | 1981-06-26 | 1986-03-25 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US4423287A (en) | 1981-06-26 | 1983-12-27 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US4453074A (en) | 1981-10-19 | 1984-06-05 | American Express Company | Protection system for intelligent cards |
FR2536928B1 (en) | 1982-11-30 | 1989-10-06 | France Etat | SYSTEM FOR ENCRYPTING AND DECIPHERING INFORMATION, OF THE TYPE USING A PUBLIC KEY DECRYPTION SYSTEM |
US4906828A (en) | 1983-02-28 | 1990-03-06 | Paperless Accounting, Inc. | Electronic money purse and fund transfer system |
US4536647A (en) | 1983-07-15 | 1985-08-20 | Atalla Corporation | Pocket banking terminal, method and system |
US4759063A (en) | 1983-08-22 | 1988-07-19 | Chaum David L | Blind signature systems |
US4759064A (en) | 1985-10-07 | 1988-07-19 | Chaum David L | Blind unanticipated signature systems |
US4926480A (en) | 1983-08-22 | 1990-05-15 | David Chaum | Card-computer moderated systems |
US4605820A (en) | 1983-11-10 | 1986-08-12 | Visa U.S.A. Inc. | Key management system for on-line communication |
SE442249B (en) | 1983-11-17 | 1985-12-09 | Ericsson Telefon Ab L M | PROCEDURE AND DEVICE FOR VERIFICATION OF PERSONAL IDENTIFICATION NUMBER AND CHECKING INSERT NUMBER SERIES IN IDENTIFICATION MEDIA |
US4745267A (en) | 1983-12-28 | 1988-05-17 | Fairview Partners | Fraudulent card intercept system |
JPS60160491A (en) | 1984-01-31 | 1985-08-22 | Toshiba Corp | Ic card |
DE3579816D1 (en) | 1984-02-09 | 1990-10-25 | Toshiba Kawasaki Kk | DATA PROCESSING TERMINAL. |
US4630201A (en) | 1984-02-14 | 1986-12-16 | International Security Note & Computer Corporation | On-line and off-line transaction security system using a code generated from a transaction parameter and a random number |
JPS60144154U (en) | 1984-03-07 | 1985-09-25 | シャープ株式会社 | portable computer |
JPS60207957A (en) | 1984-03-31 | 1985-10-19 | Toshiba Corp | Data protecting system |
US4736094A (en) | 1984-04-03 | 1988-04-05 | Omron Tateisi Electronics Co. | Financial transaction processing system using an integrated circuit card device |
US4709137A (en) | 1984-04-16 | 1987-11-24 | Omron Tateisi Electronics Co. | IC card and financial transaction processing system using IC card |
US4727243A (en) | 1984-10-24 | 1988-02-23 | Telenet Communications Corporation | Financial transaction system |
GB2168514A (en) | 1984-12-12 | 1986-06-18 | Ibm | Security module |
US4650978A (en) | 1985-01-23 | 1987-03-17 | Rmh Systems, Inc. | Off line cash card system and method |
JPS61177585A (en) | 1985-02-04 | 1986-08-09 | Toshiba Corp | Sealing body of portable electronic device |
JPS61210488A (en) | 1985-03-14 | 1986-09-18 | Toppan Moore Co Ltd | Ic card |
JPS61264485A (en) | 1985-05-18 | 1986-11-22 | Hitachi Maxell Ltd | Reader and writer for integrated circuit card |
JPS61278989A (en) | 1985-06-04 | 1986-12-09 | Toppan Moore Co Ltd | Reader/writer of ic card |
JPH069067B2 (en) | 1985-07-16 | 1994-02-02 | カシオ計算機株式会社 | IC card system |
JPH0818473B2 (en) | 1985-07-31 | 1996-02-28 | トッパン・ムーア株式会社 | IC card that can set confidentiality level |
JPH0762862B2 (en) | 1985-09-17 | 1995-07-05 | カシオ計算機株式会社 | Authentication method in IC card system |
US4752677A (en) | 1985-09-25 | 1988-06-21 | Casio Computer Co., Ltd. | Customer service system for use in IC card system |
DE3682476D1 (en) | 1985-10-07 | 1991-12-19 | Toshiba Kawasaki Kk | PORTABLE ELECTRONIC DEVICE. |
US4778983A (en) | 1985-10-12 | 1988-10-18 | Sanden Corporation | Automatic vending machine |
US4669596A (en) | 1985-10-22 | 1987-06-02 | Debitek, Inc. | Vending machine accessory permitting dual mode machine operation with either money or coded cards |
JPS62105293A (en) | 1985-10-31 | 1987-05-15 | Toshiba Corp | Reading/writing device for portable recording medium |
FR2591008B1 (en) | 1985-11-30 | 1991-05-17 | Toshiba Kk | PORTABLE ELECTRONIC DEVICE |
US4849614A (en) | 1985-12-27 | 1989-07-18 | Toppan Moore Company, Ltd. | Composite IC card |
FR2592510B1 (en) | 1985-12-31 | 1988-02-12 | Bull Cp8 | METHOD AND APPARATUS FOR CERTIFYING SERVICES OBTAINED USING A PORTABLE MEDIUM SUCH AS A MEMORY CARD |
JPS62179994A (en) | 1986-02-04 | 1987-08-07 | カシオ計算機株式会社 | Electronic card |
US4874935A (en) | 1986-03-10 | 1989-10-17 | Data Card Coprporation | Smart card apparatus and method of programming same |
JPS62222363A (en) | 1986-03-25 | 1987-09-30 | Omron Tateisi Electronics Co | Automatic transaction processing device |
JPS62254265A (en) | 1986-04-28 | 1987-11-06 | Hitachi Ltd | Control system for automatic cash transaction machine |
US4742215A (en) | 1986-05-07 | 1988-05-03 | Personal Computer Card Corporation | IC card system |
US4816653A (en) | 1986-05-16 | 1989-03-28 | American Telephone And Telegraph Company | Security file system for a portable data carrier |
US4816654A (en) | 1986-05-16 | 1989-03-28 | American Telephone And Telegraph Company | Improved security system for a portable data carrier |
JP2537199B2 (en) | 1986-06-20 | 1996-09-25 | 株式会社東芝 | IC card |
US4839792A (en) | 1986-06-20 | 1989-06-13 | Kabushiki Kaisha Toshiba | Portable electronic apparatus with a device for determining data validity |
US4748668A (en) | 1986-07-09 | 1988-05-31 | Yeda Research And Development Company Limited | Method, apparatus and article for identification and signature |
FR2601535B1 (en) | 1986-07-11 | 1988-10-21 | Bull Cp8 | METHOD FOR CERTIFYING THE AUTHENTICITY OF DATA EXCHANGED BETWEEN TWO DEVICES CONNECTED LOCALLY OR REMOTELY THROUGH A TRANSMISSION LINE |
FR2601795B1 (en) | 1986-07-17 | 1988-10-07 | Bull Cp8 | METHOD FOR DIVERSIFYING A BASE KEY AND FOR AUTHENTICATING A KEY THUS DIVERSIFIED AS HAVING BEEN PREPARED FROM A PREDETERMINED BASE KEY, AND SYSTEM FOR IMPLEMENTING IT |
JPS6332658A (en) | 1986-07-28 | 1988-02-12 | Casio Comput Co Ltd | Ic card system |
JPH07104891B2 (en) | 1986-08-05 | 1995-11-13 | 沖電気工業株式会社 | Transaction processor |
US4802218A (en) | 1986-11-26 | 1989-01-31 | Wright Technologies, L.P. | Automated transaction system |
JPH087720B2 (en) | 1986-09-16 | 1996-01-29 | 富士通株式会社 | Area access method for IC cards for multiple services |
JPS6373388A (en) | 1986-09-16 | 1988-04-02 | Fujitsu Ltd | Area acquiring system for ic card for plural services |
DE3731736A1 (en) | 1986-09-27 | 1988-04-07 | Toshiba Kawasaki Kk | Processing system for a portable electronic device |
JPS63120391A (en) | 1986-11-10 | 1988-05-24 | Hitachi Ltd | Ic card |
US4900904A (en) | 1986-11-26 | 1990-02-13 | Wright Technologies, L.P. | Automated transaction system with insertable cards for downloading rate or program data |
JPS63182795A (en) | 1987-01-20 | 1988-07-28 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Portable card and manufacture thereof |
US4969188A (en) | 1987-02-17 | 1990-11-06 | Gretag Aktiengesellschaft | Process and apparatus for the protection of secret elements in a network of encrypting devices with open key management |
US5162989A (en) | 1987-02-20 | 1992-11-10 | Oki Electric Industry Co., Ltd. | Information rental system including processor equipped IC card having data erasing means |
JPH0758500B2 (en) | 1987-02-20 | 1995-06-21 | 株式会社東芝 | Portable electronic device |
JPS63229541A (en) | 1987-03-04 | 1988-09-26 | シーメンス、アクチエンゲルシヤフト | Data exchange system |
FR2611962B1 (en) | 1987-03-06 | 1989-06-09 | Trt Telecom Radio Electr | SYSTEM AND METHOD FOR APPLIED CRYPTOGRAPHY |
JPS63236186A (en) | 1987-03-24 | 1988-10-03 | Mitsubishi Electric Corp | Card issuing device |
US4949257A (en) | 1987-04-28 | 1990-08-14 | Zvi Orbach | Automated merchandising system for computer software |
US4797920A (en) | 1987-05-01 | 1989-01-10 | Mastercard International, Inc. | Electronic funds transfer system with means for verifying a personal identification number without pre-established secret keys |
JPS6421327U (en) | 1987-07-28 | 1989-02-02 | ||
GB2204973A (en) | 1987-05-19 | 1988-11-23 | Gen Electric Co Plc | Data processing system |
US4984270A (en) | 1987-06-19 | 1991-01-08 | The Exchange System | Method and system for transmission of financial data |
JP2592856B2 (en) | 1987-09-24 | 1997-03-19 | 株式会社東芝 | IC card issuing system |
JPH0161764U (en) | 1987-10-09 | 1989-04-19 | ||
US4853961A (en) | 1987-12-18 | 1989-08-01 | Pitney Bowes Inc. | Reliable document authentication system |
FR2626095B1 (en) | 1988-01-20 | 1991-08-30 | Sgs Thomson Microelectronics | SECURITY SYSTEM FOR PROTECTING PROGRAMMING AREAS OF A CHIP CARD |
JP2623332B2 (en) | 1988-02-03 | 1997-06-25 | 日立マクセル株式会社 | IC card and its operation program writing method |
US5214702A (en) | 1988-02-12 | 1993-05-25 | Fischer Addison M | Public key/signature cryptosystem with enhanced digital signature certification |
US5005200A (en) | 1988-02-12 | 1991-04-02 | Fischer Addison M | Public key/signature cryptosystem with enhanced digital signature certification |
US5012076A (en) | 1988-03-02 | 1991-04-30 | Hitachi, Ltd. | Transaction method wherein transaction amount is compared with account balance before ID is entered |
US4987593A (en) | 1988-03-16 | 1991-01-22 | David Chaum | One-show blind signature systems |
US4995081A (en) | 1988-03-21 | 1991-02-19 | Leighton Frank T | Method and system for personal identification using proofs of legitimacy |
US4879747A (en) | 1988-03-21 | 1989-11-07 | Leighton Frank T | Method and system for personal identification |
US4891503A (en) | 1988-03-29 | 1990-01-02 | Gascard, Inc. | Distributed authorization system |
JPH01259483A (en) | 1988-04-08 | 1989-10-17 | Minolta Camera Co Ltd | Ic card |
CA1321649C (en) | 1988-05-19 | 1993-08-24 | Jeffrey R. Austin | Method and system for authentication |
US4961142A (en) | 1988-06-29 | 1990-10-02 | Mastercard International, Inc. | Multi-issuer transaction device with individual identification verification plug-in application modules for each issuer |
ATE120021T1 (en) | 1988-07-20 | 1995-04-15 | Syspatronic Ag Spa | DATA CARRIER-CONTROLLED TERMINAL DEVICE IN A DATA EXCHANGE SYSTEM. |
DE68927361T4 (en) | 1988-08-12 | 1999-11-04 | Hitachi Maxell | Chip card and procedure for rewriting your program |
JP2695855B2 (en) | 1988-08-26 | 1998-01-14 | 株式会社東芝 | Portable electronic devices |
JPH0622030B2 (en) | 1988-10-03 | 1994-03-23 | 富士通株式会社 | Transaction validity confirmation method |
US5016274A (en) | 1988-11-08 | 1991-05-14 | Silvio Micali | On-line/off-line digital signing |
GB8827288D0 (en) * | 1988-11-22 | 1988-12-29 | Byron R S | Articles to be worn |
JPH02170272A (en) | 1988-12-23 | 1990-07-02 | Hitachi Maxell Ltd | Collation system for secret information |
JPH02214994A (en) | 1989-02-15 | 1990-08-27 | Hitachi Maxell Ltd | Ic card |
US5165043A (en) | 1989-03-15 | 1992-11-17 | Hitachi, Ltd. | Memory card system and access method for memory card |
US4977595A (en) | 1989-04-03 | 1990-12-11 | Nippon Telegraph And Telephone Corporation | Method and apparatus for implementing electronic cash |
US4996711A (en) | 1989-06-21 | 1991-02-26 | Chaum David L | Selected-exponent signature systems |
FR2650097B1 (en) | 1989-07-19 | 1992-12-31 | Pailles Jean Claude | CABLE MICROCIRCUIT CARD AND TRANSACTION METHOD BETWEEN A CORRESPONDING CABLE MICROCIRCUIT CARD AND A TERMINAL |
FR2651347A1 (en) | 1989-08-22 | 1991-03-01 | Trt Telecom Radio Electr | SINGLE NUMBER GENERATION METHOD FOR MICROCIRCUIT BOARD AND APPLICATION TO COOPERATION OF THE BOARD WITH A HOST SYSTEM. |
ZA907106B (en) | 1989-10-06 | 1991-09-25 | Net 1 Products Pty Ltd | Funds transfer system |
US5148481A (en) | 1989-10-06 | 1992-09-15 | International Business Machines Corporation | Transaction system security method and apparatus |
FR2653248B1 (en) | 1989-10-13 | 1991-12-20 | Gemolus Card International | PAYMENT OR INFORMATION TRANSFER SYSTEM BY ELECTRONIC MEMORY CARD. |
FR2653914A1 (en) | 1989-10-27 | 1991-05-03 | Trt Telecom Radio Electr | SYSTEM FOR AUTHENTICATING A MICROCIRCUIT CARD BY A PERSONAL MICROCOMPUTER, AND METHOD FOR ITS IMPLEMENTATION |
US5120939A (en) | 1989-11-09 | 1992-06-09 | At&T Bell Laboratories | Databaseless security system |
US4993068A (en) | 1989-11-27 | 1991-02-12 | Motorola, Inc. | Unforgeable personal identification system |
JPH03240127A (en) | 1990-02-17 | 1991-10-25 | Hitachi Maxell Ltd | Program control system |
JPH03248249A (en) | 1990-02-27 | 1991-11-06 | Mitsubishi Electric Corp | Ic memory card |
JPH0424889A (en) | 1990-05-21 | 1992-01-28 | Toshiba Corp | Ic card provided with personal identification function |
ES2047774T3 (en) | 1990-07-20 | 1994-03-01 | Siemens Nixdorf Inf Syst | PROCEDURE TO PREVENT INADMISSIBLE DEVIATIONS OF THE DEVELOPMENT PROTOCOL OF AN APPLICATION IN A DATA EXCHANGE SYSTEM. |
US5163098A (en) | 1990-09-06 | 1992-11-10 | Dahbura Abbud S | System for preventing fraudulent use of credit card |
FR2666671B1 (en) | 1990-09-12 | 1994-08-05 | Gemplus Card Int | METHOD FOR MANAGING AN APPLICATION PROGRAM LOADED IN A MICROCIRCUIT MEDIUM. |
FR2667171B1 (en) | 1990-09-25 | 1994-08-26 | Gemplus Card Int | PORTABLE MEDIUM WITH EASILY PROGRAMMABLE MICRO-CIRCUIT AND METHOD FOR PROGRAMMING THIS MICRO-CIRCUIT. |
FR2667417B1 (en) | 1990-10-02 | 1992-11-27 | Gemplus Card Int | MICROPROCESSOR CARD DESIGNED TO RECEIVE MULTIPLE PROGRAMS IN PROGRAMMABLE MEMORY. |
US5131038A (en) | 1990-11-07 | 1992-07-14 | Motorola, Inc. | Portable authentification system |
JP3114991B2 (en) | 1990-11-30 | 2000-12-04 | 株式会社東芝 | Data communication system |
FR2673476B1 (en) | 1991-01-18 | 1996-04-12 | Gemplus Card Int | SECURE METHOD FOR LOADING MULTIPLE APPLICATIONS INTO A MICROPROCESSOR MEMORY CARD. |
FR2671889A1 (en) | 1991-01-22 | 1992-07-24 | Pailles Jean Claude | METHOD OF EXCHANGING RIGHTS BETWEEN MICROPROCESSOR CARDS. |
US5224162A (en) | 1991-06-14 | 1993-06-29 | Nippon Telegraph And Telephone Corporation | Electronic cash system |
US5142578A (en) | 1991-08-22 | 1992-08-25 | International Business Machines Corporation | Hybrid public key algorithm/data encryption algorithm key distribution method based on control vectors |
US5200999A (en) | 1991-09-27 | 1993-04-06 | International Business Machines Corporation | Public key cryptosystem key management based on control vectors |
US5201000A (en) | 1991-09-27 | 1993-04-06 | International Business Machines Corporation | Method for generating public and private key pairs without using a passphrase |
JP3083187B2 (en) | 1991-09-30 | 2000-09-04 | 富士通株式会社 | Key management method of electronic wallet system |
DE69231118T2 (en) | 1991-10-18 | 2000-12-14 | Fujitsu Ltd | Message distribution system with cordless message-transmitting substations and message-receiving terminal devices |
FR2683357A1 (en) | 1991-10-30 | 1993-05-07 | Philips Composants | MICROCIRCUIT FOR PROTECTED PROGRAMMABLE MEMORY CHIP CARD. |
US5164988A (en) | 1991-10-31 | 1992-11-17 | International Business Machines Corporation | Method to establish and enforce a network cryptographic security policy in a public key cryptosystem |
WO1993010509A1 (en) | 1991-11-12 | 1993-05-27 | Security Domain Pty. Ltd. | Method and system for secure, decentralised personalisation of smart cards |
GB9126779D0 (en) | 1991-12-17 | 1992-02-12 | Int Computers Ltd | Security mechanism for a computer system |
FR2687816B1 (en) | 1992-02-24 | 1994-04-08 | Gemplus Card International | METHOD FOR PERSONALIZING A CHIP CARD. |
JPH05250523A (en) | 1992-03-06 | 1993-09-28 | Toshiba Corp | Processing system |
US5396558A (en) | 1992-09-18 | 1995-03-07 | Nippon Telegraph And Telephone Corporation | Method and apparatus for settlement of accounts by IC cards |
FR2697357B1 (en) | 1992-10-23 | 1994-12-23 | Gemplus Card Int | Software acquisition process and computer system for implementing the process. |
EP0706692B1 (en) | 1992-10-26 | 2003-04-16 | Intellect Australia Pty. Ltd. | Host and user transaction system |
US5371797A (en) | 1993-01-19 | 1994-12-06 | Bellsouth Corporation | Secure electronic funds transfer from telephone or unsecured terminal |
US5420405A (en) | 1993-02-26 | 1995-05-30 | Chasek; Norman E. | Secure, automated transaction system that supports an electronic currency operating in mixed debit & credit modes |
JPH06251206A (en) | 1993-02-26 | 1994-09-09 | Fujitsu Ltd | Processing system for card displaying plural functions |
JP3421378B2 (en) | 1993-03-23 | 2003-06-30 | 株式会社東芝 | Transmission control method |
JPH0744672A (en) | 1993-07-28 | 1995-02-14 | Oki Electric Ind Co Ltd | Ic card and ic card system |
US5544246A (en) | 1993-09-17 | 1996-08-06 | At&T Corp. | Smartcard adapted for a plurality of service providers and for remote installation of same |
US5485520A (en) | 1993-10-07 | 1996-01-16 | Amtech Corporation | Automatic real-time highway toll collection from moving vehicles |
GB9320982D0 (en) | 1993-10-12 | 1993-12-01 | Ibm | A data processing system |
GB2284689B (en) | 1993-12-07 | 1998-02-18 | Inventec Corp | Ic card back-up generating and programming device |
JP3367675B2 (en) | 1993-12-16 | 2003-01-14 | オープン マーケット インコーポレイテッド | Open network sales system and method for real-time approval of transaction transactions |
US5530232A (en) | 1993-12-22 | 1996-06-25 | Datamark Services, Inc. | Multi-application data card |
US5578808A (en) | 1993-12-22 | 1996-11-26 | Datamark Services, Inc. | Data card that can be used for transactions involving separate card issuers |
US5557516A (en) | 1994-02-04 | 1996-09-17 | Mastercard International | System and method for conducting cashless transactions |
EP0666550B1 (en) | 1994-02-08 | 1997-05-02 | Belle Gate Investment B.V. | Data exchange system comprising portable data processing units |
FR2716280B1 (en) * | 1994-02-11 | 1996-04-12 | Solaic Sa | Method for protecting memory card components against fraudulent use. |
US5511121A (en) | 1994-02-23 | 1996-04-23 | Bell Communications Research, Inc. | Efficient electronic money |
FR2720848B1 (en) | 1994-06-03 | 1996-07-26 | Gemplus Card Int | Method of conducting a transaction between a smart card and an information system. |
FR2725537B1 (en) | 1994-10-11 | 1996-11-22 | Bull Cp8 | METHOD FOR LOADING A PROTECTED MEMORY AREA OF AN INFORMATION PROCESSING DEVICE AND ASSOCIATED DEVICE |
US5715314A (en) | 1994-10-24 | 1998-02-03 | Open Market, Inc. | Network sales system |
US5517011A (en) | 1994-11-21 | 1996-05-14 | Oki Electric Industry Co. Ltd. | Slotless card reader |
US5705798A (en) | 1994-12-16 | 1998-01-06 | Mastercard International Inc. | System and method for processing a customized financial transaction card |
US5546523A (en) | 1995-04-13 | 1996-08-13 | Gatto; James G. | Electronic fund transfer system |
US5692132A (en) | 1995-06-07 | 1997-11-25 | Mastercard International, Inc. | System and method for conducting cashless transactions on a computer network |
US5708780A (en) | 1995-06-07 | 1998-01-13 | Open Market, Inc. | Internet server access control and monitoring systems |
US5799314A (en) | 1995-06-30 | 1998-08-25 | Sun Microsystems, Inc. | System and method of controlling mapping of data buffers for heterogenous programs in digital computer system |
US5699528A (en) | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
US5889941A (en) * | 1996-04-15 | 1999-03-30 | Ubiq Inc. | System and apparatus for smart card personalization |
US5704046A (en) | 1996-05-30 | 1997-12-30 | Mastercard International Inc. | System and method for conducting cashless transactions |
US5923884A (en) * | 1996-08-30 | 1999-07-13 | Gemplus S.C.A. | System and method for loading applications onto a smart card |
-
1998
- 1998-02-12 US US09/023,057 patent/US6575372B1/en not_active Expired - Lifetime
- 1998-02-19 WO PCT/GB1998/000531 patent/WO1998037526A1/en active IP Right Grant
- 1998-02-19 CA CA002281576A patent/CA2281576C/en not_active Expired - Lifetime
- 1998-02-19 DE DE69823649T patent/DE69823649T2/en not_active Expired - Lifetime
- 1998-02-19 AU AU62996/98A patent/AU736325B2/en not_active Expired
- 1998-02-19 EP EP98907003A patent/EP0963580B1/en not_active Revoked
- 1998-02-19 JP JP53639498A patent/JP2001513231A/en not_active Withdrawn
- 1998-02-20 AR ARP980100778A patent/AR011449A1/en active IP Right Grant
-
2001
- 2001-12-21 US US10/033,281 patent/US6659354B2/en not_active Expired - Lifetime
-
2008
- 2008-07-22 JP JP2008189233A patent/JP4405568B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
DE69823649T2 (en) | 2005-06-16 |
AR011449A1 (en) | 2000-08-16 |
JP2009003945A (en) | 2009-01-08 |
US20020050528A1 (en) | 2002-05-02 |
JP4405568B2 (en) | 2010-01-27 |
JP2001513231A (en) | 2001-08-28 |
AU736325B2 (en) | 2001-07-26 |
CA2281576A1 (en) | 1998-08-27 |
EP0963580B1 (en) | 2004-05-06 |
AU6299698A (en) | 1998-09-09 |
WO1998037526A1 (en) | 1998-08-27 |
EP0963580A1 (en) | 1999-12-15 |
US6659354B2 (en) | 2003-12-09 |
US6575372B1 (en) | 2003-06-10 |
DE69823649D1 (en) | 2004-06-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2281576C (en) | Multi-application ic card system | |
US7469339B2 (en) | Secure multiple application card system and process | |
EP0981807B1 (en) | Integrated circuit card with application history list | |
US5036461A (en) | Two-way authentication system between user's smart card and issuer-specific plug-in application modules in multi-issued transaction device | |
US4961142A (en) | Multi-issuer transaction device with individual identification verification plug-in application modules for each issuer | |
US5923884A (en) | System and method for loading applications onto a smart card | |
EP0985203A1 (en) | Key transformation unit for an ic card | |
CA2293297C (en) | Chip card comprising means for managing a virtual memory, associated communication method and protocol | |
US6370517B2 (en) | Electronic money card, electronic money receiving/paying machine, and electronic money card editing device | |
EP1053535A1 (en) | Configuration of ic card | |
WO1999040549A1 (en) | System and method for controlling access to computer code in an ic card | |
AU709400B2 (en) | Integrated circuit card, secure application module, system comprising a secure application module and a terminal and a method for controlling service actions to be carried out by the secure application module on the integrated circuit card |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKEX | Expiry |
Effective date: 20180219 |