# Patent

## Title
Tamper resistant module certification authority

## Abstract

Methods and apparati for securely loading one or more computer software applications onto a tamper resistant module (TRM) (107) and for securely deleting one or more applications from the TRM. An embodiment of the invention comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept loading of an application. Thereafter, the method provides for loading the application onto the TRM (107) only after the first step determines that the TRM (107) is qualified to accept the loading of the application. Another embodiment comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept deleting of an application. Thereafter, the method provides for deleting the application from the TRM (107) only when the first step determines that the TRM (107) is qualified to accept the deleting of the application.

## Background
CROSS REFERENCES TO RELATED APPLICATIONS
This patent application is a continuation of and claims priority to U.S. patent application Ser. No. 11/707,824, filed on Feb. 16, 2007 now U.S. Pat. No. 7,584,358; patent application Ser. No. 11/707,824 is a continuation of and claims priority to U.S. patent application Ser. No. 11/655,497, filed on Jan. 19, 2007; patent application Ser. No. 11/655,497 is a continuation of and claims priority to U.S. patent application Ser. No. 09/932,013, filed on Aug. 17, 2001 now U.S. Pat. No. 7,469,339; patent application Ser. No. 09/932,013 is a continuation of and claims priority to U.S. patent application Ser. No. 09/076,551, filed on May 12, 1998, now U.S. Pat. No. 6,317,832, entitled “Secure Multiple Application Card System and Process”; patent application Ser. No. 09/076,551 claims the priority benefit of U.S. provisional patent application No. 60/046,514 filed on May 15, 1997, entitled “Design for a Multi Application Smart Card”, and further claims the priority benefit of U.S. provisional patent application No. 60/046,543 filed on May 15, 1997, and patent application Ser. No. 09/076,551 is a continuation of and claims priority to U.S. patent application Ser. No. 09/023,057, filed on Feb. 12, 1998, now U.S. Pat. No. 6,575,372, entitled “Secure Multi-Application IC Card System Having Selective Loading and Deleting Capability”; patent application Ser. No. 09/023,057 claims the priority benefit of U.S. provisional patent application No. 60/046,514, filed on May 15, 1997, entitled “Design for a Multi Application Smart Card”, and further claims the priority benefit of Great Britain patent application no. 9703591.9, filed on Feb. 21, 1997, entitled “Multiple Application Computer System.” All seven of these prior patent applications are hereby incorporated by reference into the present patent application in their entireties.


TECHNICAL FIELD
This invention pertains to the field of distribution of computer software applications, and, in particular, to use of a certification authority when loading software applications onto and deleting software applications from a tamper resistant module.
BACKGROUND OF THE INVENTION
The invention relates to a computer system in which a population of computers has access to multiple software applications. The computers may be personal computers (PC's) or, for example, integrated circuit cards (“IC cards”) also known as “smart cards”. The applications may be programs available from a variety of sources including computer tape or disc and, in particular, remote computers with which a serial link, typically by telephone, is established.
In the PC environment, it is customary to distribute applications on floppy discs or CD ROMS and to retain them on a local hard disc for operation. In many ways, this is inconvenient, demanding high capacity local storage media and presenting difficulties with updates. In the field of smart cards, the problem of local application storage is much more acute, because storage capacity in the integrated circuit is relatively very limited. A solution in both cases is to make available applications held remotely and download them via a remote link. Internet and intranet systems are ideal vehicles for this, and it is possible to run PC's from Internet application modules (or “applets” as they are called) for immediate running and then to discard them. The applets require no local long-term storage capacity. An example of such a system is JAVA.
Several difficulties are associated with downloaded applications. One is hardware compatibility. Different computers have different microprocessors and different operating systems. It has been customary to re-write applications to cater for different computers, but this is cost-effective only for large, widely used, and static applications. It is not practicable for applets. A second problem is control of the applets. Without control, it would be possible for applets to make direct hardware calls to take control of local storage or communication devices. This could be mischievous at best and severely damaging or criminal at worst.
JAVA meets these two difficulties by ensuring that the applets are written in a common high-level interpreted language and that a local interpreter processes the applet instructions. Thus, all applets are written in the same language, and the interpreter constitutes both a hardware and a control buffer. Similarly, and for the same reasons, proposals have been made for on-board interpreters in smart cards to run downloaded high-level language applications.
The wide availability of multiple applications to a population of computers raises another problem. For various reasons, it may be desirable to restrict the availability of certain applications to certain computers. For example, some applications may make demands which the hardware of a particular computer cannot meet. These represent technical limitations present in spite of the interpreter arrangement. Furthermore, there may be commercial or moral restraints to be placed on the accessibility of certain applications to certain computers. The present invention seeks to provide a solution to this problem.
According to the invention, a computer system comprises a population of computers; tamper-resistant modules each associated respectively with one of said computers; a plurality of computer applications; provider means for holding the computer applications; and means for coupling the provider means to the computers for downloading the computer applications to the computers.
The arrangement, according to the invention, allows the provision of computer specific applications or application specific computers. In some embodiments, both the tamper-resistant module and the application have both class identifiers and bit-maps so that mutual control may be exercised. However, in a preferred embodiment of the invention, the tamper-resistant module has the bit-map and the application has class identifiers. The integrity of the system depends upon both the bit-map and the class identifiers being secure. The tamper-resistant module secures the bit-map whereas the class identifiers are preferably secured by an encryption system in which a class identifier section of the application is digitally certified by a system manager.
In a preferred embodiment of the invention, class identifiers are provided both for the tamper-resistant module (TRM) and the application. The computers may be PC's, in which case the tamper-resistant modules may be smart cards read by readers attached to the computers or, for example, dongles, PC cards, or PCMCIA cards coupled to the computers.
In a preferred embodiment of the invention, the computers are embodied in integrated circuits which are themselves the tamper-resistant modules. Typically, the integrated circuits are mounted in IC cards, which are becoming increasingly used for many different purposes in the world today. An IC 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 Input/Output (I/O) 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, credit/debit, electronic money/purse and/or loyalty applications) irrespective of the type of terminal (i.e., ATM, telephone, and/or 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 when it is manufactured and before it is given to a card user. 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 both an electronic purse and a credit/debit function, 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.
Therefore, 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. Although multiple applications could be preselected and placed in the memory of the card during its production stage, it would also be beneficial to have the ability to load and delete applications for the 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. It would be beneficial to have the capability in the IC card system to exchange data among cards, card issuers, system operators, and application providers securely and to load and delete applications securely at any time from a local 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 not tampered with and are only loaded onto 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 necessary to protect 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, 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 object of this invention to provide these important features, and specifically a secure system that allows for selective availability of applications which may be loaded onto IC cards or other tamper resistant modules.
DISCLOSURE OF INVENTION
Methods and apparati for securely loading one or more computer software applications onto a tamper resistant module (TRM) (107) and for securely deleting one or more applications from the TRM (107). An embodiment of the invention comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept loading of an application. Thereafter, the method provides for loading the application onto the TRM (107) only if the first step determines that the TRM (107) is qualified to accept the loading of the application. Another embodiment comprises a method for determining, based at least upon an encrypted personalization data block, whether a TRM (107) is part of a qualified set of TRM's to accept deleting of an application. Thereafter, the method provides for deleting the application from the TRM (107) only when the first step determines that the TRM (107) is qualified to accept the deleting of the application.



BRIEF DESCRIPTION OF THE DRAWINGS
Further objects, features, and advantages 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 the invention;
FIG. 5A is a block diagram illustrating the data stored on the IC card as indicated in block 307 of FIG. 3;
FIG. 5B is a schematic of the data structures residing in an IC card and representing personalization data;
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 whether 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 multi-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.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
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 multi-application IC card or other tamper resistant module 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. Unlike the JAVA scenario, the application remains loaded until it is deliberately deleted. There are restrictions on who may delete applications, and deletion requests must be made to an authorized body such as the IC card issuer or perhaps the application issuer.
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 a 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 the bank issues. The present invention allows for this selective loading, and specifically allows for the prevention of loading proprietary applications onto unauthorized cards issued by others.
To achieve these desired objectives, the present invention gives each card a specific identity by storing “card personalization data” on the card. Moreover, 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).
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 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.
FIG. 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 whether 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
FIG. 2 shows the steps necessary in manufacturing 101 an IC card in a secure system. Step 201 manufactures the physical IC card by creating the integrated circuit on silicon and placing it on the card. The integrated circuit chip includes 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 allows the card to authenticate that the source of any message to it is from the CA, since the public key on the card is matched to the CA's secret key.
More specifically, this public key stored on the card allows 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 whether 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, allows the system to determine the identity of the card in later processes. The identifier is freely available and is not 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 mathematical 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 103 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 an application. The individual cards are preferably manufactured in batches and are sent to a personalization bureau in a group for processing.
Card Enablement/Personalization
FIG. 3 shows the steps of the card enablement process when the card arrives at a PB. The PB 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 PB configures the card to a specific user or user class.
FIG. 3 specifically shows the steps taken to enable and personalize 103 each IC card which 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 effectively sends a “get identification data” command to the card and the card returns the identification data to the terminal.
The PB typically processes a group of cards at the same time, and first compiles a list of IC card identification 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 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 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 the preferred management of the cards they issue. The following additional steps are performed:
Step 303 first checks to see whether 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 abnormally ends (“ABEND”), as shown in step 304. A card cannot be enabled and personalized twice. If the bit has not been set, 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 FIG. 5A.)
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.
FIG. 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 (CPU) 401, a RAM 403, an EEPROM 405, a ROM 407, a timer 409, control logic 411, I/O ports 413, and security circuitry 415, which are coupled 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 413. 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 401 and control logic 411 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 accomplish memory access, memory reading or writing, processing, and data communication. A timer 409 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.
FIG. 5A shows the steps of generating and loading the four elements of the card personalization data into the memory of the IC cards, and FIG. 5B 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_permissions_MULTOS card device number. Although this number is typically 8 bytes long as shown in FIG. 5B, 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 ID (MISM ID) 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.
Step 503 loads the data structure for the identity field “issuer ID” called “msm_mcd_permissions_mcd_issuer_id.” This nomenclature stands for a MULTOS 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 number in the card system. Each IC card in the MULTOS system contains information regarding the card issuer which personalized the card or is responsible for the card. A card issuer orders a certain number of cards from a manufacturer, and performs or has 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. 5A 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_permissions_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 ID. 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 particular class, and will later allow the card issuer to check the product ID and load only those 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 AirlinesTM loyalty program and a British AirwaysTM 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 505A in FIG. 5A), but could be any length, depending upon the needs of the card system. In the illustrated embodiment, the resulting instruction locates 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_permissions_mcd_controls_data_date.” This nomenclature stands for the MULTOS 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 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 one byte in length (see 507A in FIG. 5B), 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 Applications
The application loading process 105 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 contains 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 credit/debit 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, are 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 lines, 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 an application permissions profile will be qualified and receive the corresponding application program and data.
FIG. 6 shows the preferred steps performed in loading an application onto an IC card in the MULTOS IC card system. For this example, the PB is loading an application from a terminal 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 and the application's size, and instructs the card to determine (1) whether the enablement bit is set, indicating the card 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 card system. These checking steps during the open command execution will be described in detail in conjunction with FIG. 7.
After the open command has been executed, the application loader via the terminal is advised whether the card contains the proper identification personalization data and whether enough room exists in the memory of the card for the application code and related data. If there is insufficient memory, 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 loading process. The operating system in the IC cards is programmed 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 whether 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, a failure response 610 is given and the process aborts. After it has passed these checks, the application is loaded into the memory of the card.
FIG. 7 shows the various steps of the open step 601 of FIG. 6 in more detail. Step 701 determines whether 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, the card has been enabled, and the test conditions continue with step 711.
Step 711 checks whether there is sufficient space in the memory on the card to store the application code and its associated data. Applications typically have associated data related to their functions. This data is used and manipulated when the application is run. Storage space in the memory of an IC card is a continuing concern, 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 application 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 functionality compared with the case where one or two applications are 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, an insufficient space response 713 is returned to the terminal. The application loader can then decide whether 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, the process continues with step 715.
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 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 is thus 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 does 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 is loaded into EEPROM of the IC card, it would have to overwrite other application's code or data. The application loader is prevented from doing this.
FIG. 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 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 do 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, representing 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 number or a blanket permission, a card issuer or a blanket permission, and a number of product types and dates.
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 determines whether 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 is 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 all 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 ID,” all cards similarly 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 FIG. 8, each of the permissions data is checked in the order shown, but other orders could be followed, because if any one of the permissions fails, the application is prevented from being loaded on the IC card being checked. The permissions are preferably checked in the order shown. Step 801 checks whether 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 system operator. The product types are specified for each card issuer, because different card issuers 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 505A as an example, the operating system checks bit number 2 in the 256 bit array (32 bytes×8 bits per byte) resulting from the 32 byte long application permissions data structure. If the permissions check fails, the card returns a failure message to the terminal in step 803. If the product type check passes (for example, the value of bit no. 2 being 1), the process continues with step 805.
Step 805 checks whether the application permissions allowable card issuer number set encompasses the card's issuer number stored in the memory of the card, or whether 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, the card returns a failure message to the terminal in step 807. If the check passes, the process continues with step 809.
Step 809 checks whether 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 is stored and preferably includes at least the month and year. The 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, the card returns a failure message to the terminal in step 811. If the date check passes, the process continues with step 813.
Step 813 checks whether the application permissions allowable card number set encompasses the card's ID number stored in the card memory, or whether 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, the card returns a failure message to the terminal in step 815. If the check passes, the process continues with step 817.
Summary of IC Card System's Process
FIG. 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 104, an application loader 106, the IC card 107 being initialized, the card user 109, and the certification authority 111 for the entire multiple application secure system. The card user 109 is the person or entity who uses 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 MasterCardTM EMV application) on the same IC card. The following is a description of one way in which the card user 109 obtains an IC card 107 containing the desired applications in a secure manner.
The card user 109 contacts a card issuer 113, such as a bank which distributes IC cards, and requests an IC card with the two applications both residing in memory of a single IC card. The integrated circuit chip for the IC card 107 is manufactured by manufacturer 102 and sent to the card issuer 113 (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 102 to card 107 and stored in IC card 107's 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 encryption/decryption keys for the entire system, transmits 117 security data (i.e., a 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.
The card issuer 113 performs, or has performed by another entity, two separate functions. First, the PB 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 111 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 ID 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 personalization bureau 104, first needs to have determined whether 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 card with no applications and then select a desired application over a common transmission line such as a telephone line or Internet connection.
FIG. 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 107, a terminal 153, an application load/deleted entity 155, the CA 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 157 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 107 also can communicate with other IC cards 159. Card issuer 171 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 107 uses the following procedure to load a new application onto the card. IC card 107 is coupled 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 171, sends the application code, data, and application permissions data (along with any other necessary data) to terminal 153. Terminal 153 then queries IC card 107 to ensure it is the correct card onto which the application may be loaded. If IC card 107 passes the checks discussed above, the application is loaded onto IC card 107. The CA 157 provides the application load or 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 references to “software” include firmware and the like, and that 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 controls the cards from which the application may be deleted. This is accomplished through the personalization data stored on each IC card and the permissions check as described herein.
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.
Furthermore, although the foregoing description of the preferred embodiments revolves around a discussion of IC cards 107 (or “smart cards”), the presently claimed methods and apparati are applicable to all tamper resistant modules generally, and not just to such cards. Thus, the term “tamper resistant module” can be used in lieu of the term “IC card” or “smart card” throughout this written description. The term “tamper resistant module” includes, but is not limited to, one or more IC cards, smart cards, dongles, PC cards, and/or PCMCIA cards. The IC cards, smart cards, dongles, PC cards, and/or PCMCIA cards may be coupled to one or more computers.
Furthermore, the term “personal computer/tamper resistant module combination” can be substituted for “IC card” or “smart card” throughout this written description.

## Claims

1. Apparatus comprising:
at least one tamper resistant module (TRM), a software application to be loaded onto a TRM, and means for determining whether a TRM is qualified to accept the loading of said application onto said TRM, wherein each TRM comprises TRM personalization data, and said application is assigned application permissions data representing at least one TRM upon which said application is permitted to be loaded.

2. The apparatus of claim 1, wherein said determining means compares said TRM personalization data with said application permissions data.

3. The apparatus of claim 2, wherein whether said application is loaded onto said TRM depends on the result of said comparison, such that in the event the TRM personalization data matches said permissions data set, the TRM is qualified and the application is loaded.

4. The apparatus of claim 1, wherein said personalization data comprises data representative of a unique TRM identification designation.

5. The apparatus of claim 1, wherein said personalization data comprises data representative of at least one of a TRM issuer and a product class.

6. The apparatus of claim 1, wherein said personalization data comprises data representative of a date.

7. A method for loading a software application onto a TRM, said method comprising:
determining whether said TRM is qualified to accept the loading of said application onto said TRM, wherein said determining step comprises the substeps of:
providing said TRM with personalization data;
assigning to said application permissions data representing at least one set of TRM's upon which said application is permitted to be loaded;
comparing said personalization data with said permissions data; and
loading said application onto said TRM, provided said personalization data falls within said set of TRM's upon which said application is permitted to be loaded.

8. The method of claim 7, wherein said personalization data comprises data representative of a TRM identification designation.

9. The method of claim 7, wherein said personalization data comprises data representative of a TRM issuer.

10. The method of claim 7, wherein said personalization data comprises data representative of a product class.

11. The method of claim 7, wherein said personalization data comprises data representative of a date.

12. The method of claim 7, comprising the step of, prior to the determining step, enabling said TRM to be loaded with said application.

13. The method of claim 12, wherein said enabling step comprises setting an enablement bit indicating that the TRM has been enabled.

14. The method of claim 12, wherein said enabling step comprises storing personalization data onto said TRM.

15. The method of claim 14, wherein said enabling step comprises setting an enablement bit indicating that the TRM has been enabled.

16. The method of claim 12, wherein, prior to said enabling step, a checking step is performed to determine whether said TRM has been enabled.

17. A method for deleting a software application from a TRM, said method comprising the steps of:
determining whether said TRM is qualified to delete said application based upon permissions data associated with said application, wherein said determining step comprises the substeps of:
providing said TRM with personalization data;
assigning to said application permissions data representing at least one set of TRM's from which said application is permitted to be deleted;
comparing said personalization data with said permissions data; and
deleting said application from said TRM provided said personalization data falls within said set of TRM's from which said application is permitted to be deleted.

18. The method of claim 17, wherein said personalization data comprises data representative of a TRM identification designation.

19. The method of claim 17, wherein said personalization data comprises data representative of a TRM issuer.

20. The method of claim 17, wherein said personalization data comprises data representative of a product class.

21. The method of claim 17, wherein said personalization data comprises data representative of a date.

22. Apparatus comprising:
at least one tamper resistant module (TRM);
a software application to be deleted from said TRM; and
means for determining whether a TRM is qualified to delete said application from said TRM, wherein each TRM comprises TRM personalization data, and said application is assigned application permissions data representing at least one TRM from which said application is permitted to be deleted.

23. The apparatus of claim 22, wherein said determining means makes a comparison between said TRM personalization data and said application permissions data.

24. The apparatus of claim 23, wherein whether said application is deleted from said TRM depends on the result of said comparison, such that in the event the TRM personalization data matches said application permissions data the TRM is qualified and the application is deleted.

25. Apparatus comprising:
a personal computer (PC) having at least one tamper resistant module (TRM), a software application to be loaded onto a PC and TRM combination (PC/TRM), and means for determining whether a PC/TRM is qualified to accept the loading of said application onto said PC/TRM, wherein each PC/TRM comprises PC/TRM personalization data, and said application is assigned application permissions data representing at least one PC/TRM upon which said application is permitted to be loaded.