US20050009543A1 - Adaptable chip card - Google Patents

Adaptable chip card Download PDF

Info

Publication number
US20050009543A1
US20050009543A1 US10/910,152 US91015204A US2005009543A1 US 20050009543 A1 US20050009543 A1 US 20050009543A1 US 91015204 A US91015204 A US 91015204A US 2005009543 A1 US2005009543 A1 US 2005009543A1
Authority
US
United States
Prior art keywords
apdu
chip card
card
handler
eeprom
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.)
Abandoned
Application number
US10/910,152
Inventor
Adriano Huber
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Swisscom Mobile AG
Swisscom AG
Original Assignee
Swisscom Mobile AG
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=4551739&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US20050009543(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Swisscom Mobile AG filed Critical Swisscom Mobile AG
Priority to US10/910,152 priority Critical patent/US20050009543A1/en
Publication of US20050009543A1 publication Critical patent/US20050009543A1/en
Assigned to SWISSCOM MOBILE AG reassignment SWISSCOM MOBILE AG ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HUBER, ADRIANO
Assigned to SWISSCOM (SCHWEIZ) AG reassignment SWISSCOM (SCHWEIZ) AG CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: SWISSCOM MOBILE SA (SWISSCOM MOBILE LTD)
Assigned to SWISSCOM AG reassignment SWISSCOM AG ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SWISSCOM (SCHWEIZ) AG
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • 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
    • 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/073—Special arrangements for circuits, e.g. for protecting identification code in memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/0095—Testing the sensing arrangement, e.g. testing if a magnetic card reader, bar code reader, RFID interrogator or smart card reader functions properly
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/40—Security arrangements using identity modules

Definitions

  • the present invention concerns a chip card, in particular a chip card that can be adapted after its manufacture and distribution.
  • Chip cards communicate with external devices, for example with a mobile telephone, over a logical interface often called API (Application Protocol Interface).
  • API Application Protocol Interface
  • the external device wanting to access a functionality of the chip card sends an order over this API interface.
  • the card that receives an order from the external device can decode it and trigger the corresponding action.
  • APDU Application Packet Data Unit
  • An APDU consists usually of a header and a body, the header indicating the instruction to be performed and the instruction parameters whilst the body, which is not always present, contains data. This protocol is described among others in the ISO norm ISO/IEC 7816, part 4. Further orders are specified in system specific documents (e.g. GSM 11.11, GSM 11.14).
  • the definition of the API interface and the standardization of the APDU so as to be recognized by chip cards are developed mainly in standardization forums or are proposed by individual firms. For reasons of compatibility between chip cards and devices of different manufacturers, a strong international standardization of the API interface is a desirable aim.
  • WO9819237 (Schlumberger) describes a chip card with a virtual Java machine in which different applications are stored in an EEPROM. Applications can thus be modified or replaced.
  • the instruction handler is however stored in the ROM, so that no new instructions can be added to the existing set of instructions.
  • these aims are achieved in that the functionality made available through the chip card when a data unit is received over the API interface is decoded, interpreted and performed by the application logic in the EEPROM part of the chip card.
  • the so-called APDU handler in the chip card and which determines the reaction to incoming data units can be modified, for example completed, renewed or replaced, at any moment in order to take into account newly defined, proprietary or non standardized APDU.
  • FIG. 1 shows a diagrammatic view of a system with a conventional chip card.
  • FIG. 2 shows a diagrammatic view of an APDU order according to the invention.
  • FIG. 3 shows a diagrammatic view of a system with a chip card according to a first embodiment of the invention.
  • FIG. 4 shows a diagrammatic view of a system with a chip card according to a second embodiment of the invention.
  • a chip card that is used as an identification module in a digital cellular mobile telephone, for example a SIM (Subscriber Identification Module) card or a WIM (Wireless Application protocol Identification Module) card, or WIM/SM (SIM with WIM application) that can be used for example in a GSM (Global System for Mobile Telecommunication), WAP (Wireless Application Protocol) or UMTS mobile telephone.
  • SIM Subscriber Identification Module
  • WIM Wireless Application protocol Identification Module
  • WIM/SM SIM with WIM application
  • GSM Global System for Mobile Telecommunication
  • WAP Wireless Application Protocol
  • UMTS Universal Mobile Telecommunication
  • the one skilled in the art will however understand that the present invention can also be applied to other types of chip cards, for example with JAVA (trademark of SUN Microsystems) or with OpenCard cards.
  • FIG. 1 shows diagrammatically an example of a known conventional system.
  • the system comprises a terminal 3 (Mobile Equipment ME) and a conventional SIM or WIM card 5 .
  • An application 1 for example a browser or an application program, for example a program from a service provider, is executed by data processing means (not represented) in the mobile equipment 3 .
  • the application communicates with the mobile equipment 3 over an API (Application Protocol Interface) 2 that is here not detailed.
  • API Application Protocol Interface
  • the mobile equipment 3 communicates with the SIM card 5 over another API interface 4 .
  • the mobile equipment 3 usually takes over the role of master of the communication over this interface whilst the SIM card 5 answers as slave.
  • Protocol variants are however also known (for example according to SIM-Toolkit, i.e. GSM 11.14) in which the SIM card takes over, at least temporarily, the role of master.
  • a step in the API protocol consists in an order being sent to the chip card 5 , in the card executing the order and if necessary in a reply being sent to the mobile equipment 3 .
  • orders or replies are exchanged over the interface 4 .
  • Data can be contained both in the orders and/or in the replies.
  • APDU Application Protocol Data Unit
  • Some standardized APDU for ISO chip cards are described in the norm ISO/IEC 7816-4:1995(E). Additional APDU have been defined for SIM cards and for WIM cards in order to expand the functionalities of the API interface 4 .
  • FIG. 2 shows the typical structure of an APDU 20 .
  • the data unit comprises a compulsory header 200 with four bytes and an optional body 201 of variable length.
  • the header contains a first byte (CLA) used to indicate among others which API version the data unit complies with.
  • a second byte (INS) gives the instruction that is to be executed or has just been executed by the chip card 5 .
  • two further parameters P 1 and P 2 can be indicated. If an instruction does not require a parameter P 1 and/or P 2 , this parameter must be set to zero.
  • the optional body 201 contains dada and at least one byte indicating the length of these data and/or the maximal length of the expected reply.
  • the conventional chip card 5 comprises generally a ROM 50 , an EEPROM 51 and a RAM 52 , as well as data processing means (not representted).
  • the ROM nowadays typically has 64 Kbytes and usually includes the operating system, a Java virtual machine (JVM, trademark of SUN Micro-systems) and different components F 1 , F 2 , . . . , for example JavaBeans, Applets or programs for making available the card's different functionalities.
  • Components are also stored in the EEPROM 51 , for example components that have been downloaded as applet after the personalization of the card as well as personal user data, for example a telephone directory, an electronic certificate, etc.
  • the EEPROM can for example comprise 16 or 32 Kbytes.
  • Temporary data are stored in the RAM 52 , for example temporary variables.
  • Applications (applets) can furthermore be stored in the EEPROM.
  • a data unit handler 500 receives the APDU of the mobile equipment 3 received over the API interface 4 and analyses the header 200 , in particular the bytes CLA and INS, in order to forward the order to the appropriate component F 1 , F 2 , . . . that can execute the order.
  • the APDU handler 500 can then receive the reply of this component and send this reply over the API interface 4 to the mobile equipment 3 .
  • the APDU handler 500 is usually implemented in the ROM part 50 .
  • the program is executed by the data processing means when an incoming APDU is detected. It is however also possible to devise the APDU handler as a circuit.
  • a problem with this configuration is that the mobile equipment 3 and the application cannot access new functionalities of the card made available through new components G 1 , G 2 , G 3 in the ROM, EEPROM or RAM, as long as no APDU 20 has been standardized for this functionality.
  • chip cards 5 that have already been distributed cannot offer this functionnality if they only have a conventional APDU handler 500 unable to recognize this APDU that has been defined later, even if the required component G 1 , G 2 , . . . is contained in the card. For these reasons, new functionalities that would be possible through the continuous and fast development of chip cards can be distributed only slowly.
  • FIG. 3 shows an example of a first embodiment of a chip card 5 according to the invention, for example a SIM or WIM card that can solve these problems.
  • the chip card has a test module 510 that checks all APDU 20 received over the API interface 4 . If the test module detects that the received APDU was already provided at the time the ROM part 50 was manufactured, it forward this APDU to a conventional APDU handler 500 in the ROM part 50 that makes available the corresponding functionality F 1 , F 2 , . . . as described above.
  • the test module detects that the received APDU 20 was not provided at the time the ROM part 50 was manufactured, for example because it was standarddized only in a later version of the API interface 4 , it forwards this APDU to a new, modified APDU handler 511 that calls up the component G 1 , G 2 , G 3 , . . . provided for this new APDU in the ROM or EEPROM.
  • the test as to whether the received APDU should be sent to the conventional APDU handler 500 or to a new APDU handler 511 can be performed in various ways.
  • the module 510 contains a list of APDU that are to be forwarded to the conventional APDU handler 500 and/or a list of newly defined APDU that are to be directed to the new APDU. This list is preferably located also in the EEPROM and can thus be adapted.
  • the APDU handler 500 directs the received APDU to the new APDU handler 511 only if it receives an error message from the conventional APDU handler, namely if the conventional APDU handler cannot process this APDU.
  • test module 510 can itself determine, on the basis of the CLA or INS bytes, to which APDU handler the received APDU 20 is to be forwarded.
  • newly defined APDU that are to be forwarded to the new APDU handler 511 are specially marked, for example by means of being misused, for example by containing special, impossible or very improbable parameters P 1 , P 2 or data 201 .
  • the new APDU handler 511 is preferably located in the EEPROM 51 . In this manner, it can also be altered after the manufacture of the ROM 50 , in order for example to ensure access to new components G 1 , G 2 , G 3 that have meanwhile been implemented.
  • the test module 510 is also located in the EEPROM so that the test conditions can be set after the manufacture of the ROM and/or after the distribution of the chip cards.
  • the test module 510 could however also be located in the ROM 50 or even in the RAM 52 .
  • the new components G 1 , G 2 , G 3 , . . . can be contained in the ROM 50 or in the EEPROM 51 . Further components temporarily stored in the RAM 52 can also be made available. If the chip card 5 can play the role of master of the interface 4 at least temporarily, it can with this mechanism access also components, for example applets, that are made available by the mobile equipment 3 . It is even possible for the APDU handler 501 to access components that are located in an external device connected with the mobile equipment 3 , for example over a contactless interface, for example an infrared, RFID or Bluetooth interface.
  • the APDU handler 500 is modified in the ROM part 50 so that it automatically forwards all received APDU that are not known to a new adaptable APDU handler 511 in the EEPROM 51 .
  • This embodiment makes it possible to forgo the test module 510 : that which cannot be processed by the conventional APDU handler 500 is automatically transmitted to the new APDU handler 511 .
  • FIG. 4 shows a further variant embodiment of a chip card according to the invention.
  • the normal APDU handler usually located in the ROM 50 has been replaced with a modified APDU handler 512 in the EEPROM. In this manner, it can be adapted at any time in order to take into account newly defined APDU.
  • This variant embodiment allows a great flexibility, since new components G 1 , G 2 , G 3 and new APDU can be implemented at any time in the card 5 .
  • the modified APDU handler is also located in the RAM 52 so that it can easily be modified through the chip card's operating system or through the application 1 .
  • an application 1 can access functionalities of a chip card 5 that were not provided at the time of manufacture of the card and for which no APDU has been standardized, for example functionalities G 1 , G 2 , G 3 . . . that were downloaded as applet over an air interface only after the personalization or even after the distribution of the card.
  • test module 510 and/or the new APDU handler 511 resp. 512 can be adapted with a message over a mobile radio network, for example with a SMS message, a USSD message a GPRS packet, an IP packet, etc.
  • the test module 510 and/or the APDU handler can also be modified or completed by an application 1 , for example a browser, that has been loaded for example over the air interface or with a data carrier.
  • each APDU can trigger the execution of several different functions in the chip card 5 .
  • a special APDU defines in which state the card is and which set of functions is to be used in future. This variant allows for all functionalities of the chip card to be replaced by sending a single APDU, by means of incoming APDU being processed by a new APDU handler. In this manner, for example, all parameters and components stored in the EEPROM 51 can temporarily be replaced. Another special APDU can then return the chip card to its normal state.

Abstract

Chip card (5) capable of communicating with an external device (3) over a logical interface (4), standardized data units (20) being defined for this communication. The chip card has a ROM and an EEPROM. The functionality that is made available through the chip card when a data unit (20) is received over said logical interface (4) is determined in the EEPROM, for example through an APDU handler (512) implemented in the EEPROM.

Description

    REFERENCE DATA
  • The present application is a continuation of U.S. application Ser. No. 10/150,334 filed May 16, 2002, itself a Continuation under 35 USC§111 of PCT/CH99/00553 filed on Nov. 19, 1999, the contents of which are included by reference.
    • FIELD OF THE INVENTION
  • The present invention concerns a chip card, in particular a chip card that can be adapted after its manufacture and distribution.
    • RELATED ART
  • Chip cards communicate with external devices, for example with a mobile telephone, over a logical interface often called API (Application Protocol Interface). The external device wanting to access a functionality of the chip card sends an order over this API interface. The card that receives an order from the external device can decode it and trigger the corresponding action.
  • Such orders are usually encoded as structured data units, called APDU (Application Packet Data Unit). An APDU consists usually of a header and a body, the header indicating the instruction to be performed and the instruction parameters whilst the body, which is not always present, contains data. This protocol is described among others in the ISO norm ISO/IEC 7816, part 4. Further orders are specified in system specific documents (e.g. GSM 11.11, GSM 11.14).
  • The definition of the API interface and the standardization of the APDU so as to be recognized by chip cards are developed mainly in standardization forums or are proposed by individual firms. For reasons of compatibility between chip cards and devices of different manufacturers, a strong international standardization of the API interface is a desirable aim.
  • The standardization of APDU orders is however a process that often happens more slowly than the technical development of the chip cards. For this reason, conventional chip cards cannot fulfil all the wishes of the users and in particular not all the wishes of the services providers or of the telecommunication network operators. Functionalities of a chip card that can technically already be realized and are even sometimes implemented in the card can often be offered only after the next standardization of the APDU specification.
  • WO9819237 (Schlumberger) describes a chip card with a virtual Java machine in which different applications are stored in an EEPROM. Applications can thus be modified or replaced. The instruction handler is however stored in the ROM, so that no new instructions can be added to the existing set of instructions.
  • It is therefore an aim of this invention to propose a method with which an external device can access the functionalities of a card for which the APDU has been standardized only after the manufacture of the chip card.
    • BRIEF SUMMARY OF THE INVENTION
  • According to the present invention, these aims are achieved in particular through the characteristics of the independent claims. Further advantageous embodiments are moreover described in the dependent claims and in the description.
  • In particular, these aims are achieved in that the functionality made available through the chip card when a data unit is received over the API interface is decoded, interpreted and performed by the application logic in the EEPROM part of the chip card.
  • In this way, the so-called APDU handler in the chip card and which determines the reaction to incoming data units can be modified, for example completed, renewed or replaced, at any moment in order to take into account newly defined, proprietary or non standardized APDU.
    • DESCRIPTION OF THE DRAWINGS
  • Hereafter, preferred embodiments of the invention will be described in more detail with the aid of the attached figures, in which:
  • FIG. 1 shows a diagrammatic view of a system with a conventional chip card.
  • FIG. 2 shows a diagrammatic view of an APDU order according to the invention.
  • FIG. 3 shows a diagrammatic view of a system with a chip card according to a first embodiment of the invention.
  • FIG. 4 shows a diagrammatic view of a system with a chip card according to a second embodiment of the invention.
    • DETAILED DESCRIPTION OF THE INVENTION
  • The following description refers to the special case of a chip card that is used as an identification module in a digital cellular mobile telephone, for example a SIM (Subscriber Identification Module) card or a WIM (Wireless Application protocol Identification Module) card, or WIM/SM (SIM with WIM application) that can be used for example in a GSM (Global System for Mobile Telecommunication), WAP (Wireless Application Protocol) or UMTS mobile telephone. The one skilled in the art will however understand that the present invention can also be applied to other types of chip cards, for example with JAVA (trademark of SUN Microsystems) or with OpenCard cards.
  • FIG. 1 shows diagrammatically an example of a known conventional system. The system comprises a terminal 3 (Mobile Equipment ME) and a conventional SIM or WIM card 5. An application 1, for example a browser or an application program, for example a program from a service provider, is executed by data processing means (not represented) in the mobile equipment 3. The application communicates with the mobile equipment 3 over an API (Application Protocol Interface) 2 that is here not detailed.
  • The mobile equipment 3 communicates with the SIM card 5 over another API interface 4. The mobile equipment 3 usually takes over the role of master of the communication over this interface whilst the SIM card 5 answers as slave. Protocol variants are however also known (for example according to SIM-Toolkit, i.e. GSM 11.14) in which the SIM card takes over, at least temporarily, the role of master.
  • A step in the API protocol consists in an order being sent to the chip card 5, in the card executing the order and if necessary in a reply being sent to the mobile equipment 3. Thus either orders or replies are exchanged over the interface 4. Data can be contained both in the orders and/or in the replies.
  • These questions and orders are encoded with standardized APDU (Application Protocol Data Unit). Some standardized APDU for ISO chip cards are described in the norm ISO/IEC 7816-4:1995(E). Additional APDU have been defined for SIM cards and for WIM cards in order to expand the functionalities of the API interface 4.
  • FIG. 2 shows the typical structure of an APDU 20. The data unit comprises a compulsory header 200 with four bytes and an optional body 201 of variable length.
  • The header contains a first byte (CLA) used to indicate among others which API version the data unit complies with. A second byte (INS) gives the instruction that is to be executed or has just been executed by the chip card 5. Depending on the instructions, two further parameters P1 and P2 can be indicated. If an instruction does not require a parameter P1 and/or P2, this parameter must be set to zero.
  • The optional body 201 contains dada and at least one byte indicating the length of these data and/or the maximal length of the expected reply.
  • The conventional chip card 5 comprises generally a ROM 50, an EEPROM 51 and a RAM 52, as well as data processing means (not representted). The ROM nowadays typically has 64 Kbytes and usually includes the operating system, a Java virtual machine (JVM, trademark of SUN Micro-systems) and different components F1, F2, . . . , for example JavaBeans, Applets or programs for making available the card's different functionalities. Components are also stored in the EEPROM 51, for example components that have been downloaded as applet after the personalization of the card as well as personal user data, for example a telephone directory, an electronic certificate, etc. The EEPROM can for example comprise 16 or 32 Kbytes. Temporary data are stored in the RAM 52, for example temporary variables. Applications (applets) can furthermore be stored in the EEPROM.
  • A data unit handler 500, often called APDU handler, receives the APDU of the mobile equipment 3 received over the API interface 4 and analyses the header 200, in particular the bytes CLA and INS, in order to forward the order to the appropriate component F1, F2, . . . that can execute the order. The APDU handler 500 can then receive the reply of this component and send this reply over the API interface 4 to the mobile equipment 3.
  • The APDU handler 500 is usually implemented in the ROM part 50. The program is executed by the data processing means when an incoming APDU is detected. It is however also possible to devise the APDU handler as a circuit. A problem with this configuration is that the mobile equipment 3 and the application cannot access new functionalities of the card made available through new components G1, G2, G3 in the ROM, EEPROM or RAM, as long as no APDU 20 has been standardized for this functionality. Even when such an APDU has been defined and standardized, chip cards 5 that have already been distributed cannot offer this functionnality if they only have a conventional APDU handler 500 unable to recognize this APDU that has been defined later, even if the required component G1, G2, . . . is contained in the card. For these reasons, new functionalities that would be possible through the continuous and fast development of chip cards can be distributed only slowly.
  • FIG. 3 shows an example of a first embodiment of a chip card 5 according to the invention, for example a SIM or WIM card that can solve these problems. In this embodiment, the chip card has a test module 510 that checks all APDU 20 received over the API interface 4. If the test module detects that the received APDU was already provided at the time the ROM part 50 was manufactured, it forward this APDU to a conventional APDU handler 500 in the ROM part 50 that makes available the corresponding functionality F1, F2, . . . as described above. If, on the other hand, the test module detects that the received APDU 20 was not provided at the time the ROM part 50 was manufactured, for example because it was standarddized only in a later version of the API interface 4, it forwards this APDU to a new, modified APDU handler 511 that calls up the component G1, G2, G3, . . . provided for this new APDU in the ROM or EEPROM.
  • The test as to whether the received APDU should be sent to the conventional APDU handler 500 or to a new APDU handler 511 can be performed in various ways. In a first embodiment, the module 510 contains a list of APDU that are to be forwarded to the conventional APDU handler 500 and/or a list of newly defined APDU that are to be directed to the new APDU. This list is preferably located also in the EEPROM and can thus be adapted. In another embodiment, the APDU handler 500 directs the received APDU to the new APDU handler 511 only if it receives an error message from the conventional APDU handler, namely if the conventional APDU handler cannot process this APDU. In another embodiment, the test module 510 can itself determine, on the basis of the CLA or INS bytes, to which APDU handler the received APDU 20 is to be forwarded. In yet another embodiment, newly defined APDU that are to be forwarded to the new APDU handler 511 are specially marked, for example by means of being misused, for example by containing special, impossible or very improbable parameters P1, P2 or data 201.
  • The new APDU handler 511 is preferably located in the EEPROM 51. In this manner, it can also be altered after the manufacture of the ROM 50, in order for example to ensure access to new components G1, G2, G3 that have meanwhile been implemented. Preferably, the test module 510 is also located in the EEPROM so that the test conditions can be set after the manufacture of the ROM and/or after the distribution of the chip cards. The test module 510 could however also be located in the ROM 50 or even in the RAM 52.
  • The new components G1, G2, G3, . . . can be contained in the ROM 50 or in the EEPROM 51. Further components temporarily stored in the RAM 52 can also be made available. If the chip card 5 can play the role of master of the interface 4 at least temporarily, it can with this mechanism access also components, for example applets, that are made available by the mobile equipment 3. It is even possible for the APDU handler 501 to access components that are located in an external device connected with the mobile equipment 3, for example over a contactless interface, for example an infrared, RFID or Bluetooth interface.
  • In a variant embodiment of the invention (not represented), the APDU handler 500 is modified in the ROM part 50 so that it automatically forwards all received APDU that are not known to a new adaptable APDU handler 511 in the EEPROM 51. This embodiment makes it possible to forgo the test module 510: that which cannot be processed by the conventional APDU handler 500 is automatically transmitted to the new APDU handler 511.
  • FIG. 4 shows a further variant embodiment of a chip card according to the invention. The same or similar features are referred to in all figures with the same reference numbers and will not be described again unless this is necessary. In this embodiment, the normal APDU handler usually located in the ROM 50 has been replaced with a modified APDU handler 512 in the EEPROM. In this manner, it can be adapted at any time in order to take into account newly defined APDU.
  • This variant embodiment allows a great flexibility, since new components G1, G2, G3 and new APDU can be implemented at any time in the card 5.
  • In a variant embodiment (not represented) the modified APDU handler is also located in the RAM 52 so that it can easily be modified through the chip card's operating system or through the application 1.
  • In this manner, an application 1 can access functionalities of a chip card 5 that were not provided at the time of manufacture of the card and for which no APDU has been standardized, for example functionalities G1, G2, G3 . . . that were downloaded as applet over an air interface only after the personalization or even after the distribution of the card.
  • For example, the test module 510 and/or the new APDU handler 511 resp. 512 can be adapted with a message over a mobile radio network, for example with a SMS message, a USSD message a GPRS packet, an IP packet, etc. The test module 510 and/or the APDU handler can also be modified or completed by an application 1, for example a browser, that has been loaded for example over the air interface or with a data carrier.
  • In a variant embodiment of the invention, each APDU can trigger the execution of several different functions in the chip card 5. A special APDU defines in which state the card is and which set of functions is to be used in future. This variant allows for all functionalities of the chip card to be replaced by sending a single APDU, by means of incoming APDU being processed by a new APDU handler. In this manner, for example, all parameters and components stored in the EEPROM 51 can temporarily be replaced. Another special APDU can then return the chip card to its normal state.

Claims (6)

1. A method for adapting a chip card after its manufacture to a new standardization of the API interface, comprising the steps of:
adapting a module in a memory of the chip card to determine a proper functionality when said certain data unit is received; and
receiving said certain data unit over said API interface.
2. The method of claim 1, wherein said module is adapted via a message received over a mobile radio network.
3. The method of claim 2, wherein said message is an SMS message.
4. The method of claim 2, wherein said message is a USSD message.
5. The method of claim 2, wherein said message is a GPRS packet.
6. The method of claim 2, wherein said message is an IP packet.
US10/910,152 1999-11-19 2004-08-03 Adaptable chip card Abandoned US20050009543A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/910,152 US20050009543A1 (en) 1999-11-19 2004-08-03 Adaptable chip card

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
PCT/CH1999/000553 WO2001039464A1 (en) 1999-11-19 1999-11-19 Adaptable chip card
US10/150,334 US6847831B2 (en) 1999-11-19 2002-05-16 Adaptable chip card
US10/910,152 US20050009543A1 (en) 1999-11-19 2004-08-03 Adaptable chip card

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/150,334 Continuation US6847831B2 (en) 1999-11-19 2002-05-16 Adaptable chip card

Publications (1)

Publication Number Publication Date
US20050009543A1 true US20050009543A1 (en) 2005-01-13

Family

ID=4551739

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/150,334 Expired - Lifetime US6847831B2 (en) 1999-11-19 2002-05-16 Adaptable chip card
US10/910,152 Abandoned US20050009543A1 (en) 1999-11-19 2004-08-03 Adaptable chip card

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/150,334 Expired - Lifetime US6847831B2 (en) 1999-11-19 2002-05-16 Adaptable chip card

Country Status (6)

Country Link
US (2) US6847831B2 (en)
EP (1) EP1230780B1 (en)
AT (1) ATE290744T1 (en)
AU (1) AU1145800A (en)
DE (1) DE59911743D1 (en)
WO (1) WO2001039464A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050192054A1 (en) * 2003-09-08 2005-09-01 Nec Corporation Mobile station intermittently receiving a radio signal
US20080287162A1 (en) * 1999-05-11 2008-11-20 Gemplus Radiotelephone terminal with chip card provided with browser

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8150767B2 (en) * 2000-02-16 2012-04-03 Mastercard International Incorporated System and method for conducting electronic commerce with a remote wallet server
FR2846770B1 (en) * 2002-11-04 2005-01-28 Oberthur Card Syst Sa MICROCIRCUIT CARD COMPRISING MEANS FOR PUBLICATION OF ITS COMPUTER OBJECTS
JP2004172923A (en) * 2002-11-20 2004-06-17 Nec Corp Portable telephone terminal, and pay service restriction method used therefor
DE10342112A1 (en) * 2003-09-10 2005-05-04 Vodafone Holding Gmbh Device for checking a SIM card
US7324835B2 (en) * 2004-08-07 2008-01-29 C-One Technology Corporation Motherboard and daughterboard multi-swap system with communication module for a GPRS system
WO2006045344A1 (en) * 2004-10-29 2006-05-04 Telecom Italia S.P.A. Method for establishing a secure logical connection between an integrated circuit card and a memory card through a terminal equipment
DE102005019753A1 (en) * 2005-04-28 2006-11-09 Braun Gmbh Sphygmomanometer and chip card for this
ATE489776T1 (en) * 2005-10-31 2010-12-15 Research In Motion Ltd COMBINED BATTERY AND CHIP CARD
KR100735341B1 (en) * 2006-02-27 2007-07-04 삼성전자주식회사 Apparatus and method for improving speed of data reading from subscriber identity module
ATE536058T1 (en) 2007-10-10 2011-12-15 Morpho Cards Gmbh TELECOMMUNICATIONS CARD AND METHOD THEREOF
CN101896916A (en) * 2007-12-13 2010-11-24 诺基亚公司 Interaction between secured and unsecured environments

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6131040A (en) * 1997-06-19 2000-10-10 Nokia Mobile Phones Limited Wireless communication device receiving configuration data from multiple sources
US6216014B1 (en) * 1996-05-17 2001-04-10 Gemplus Communication system for managing safely and independently a plurality of applications by each user card and corresponding user card and management method
US20020040936A1 (en) * 1998-10-27 2002-04-11 David C. Wentker Delegated management of smart card applications
US20020066792A1 (en) * 2000-12-06 2002-06-06 Mobile-Mind, Inc. Concurrent communication with multiple applications on a smart card
US6418326B1 (en) * 1995-02-15 2002-07-09 Nokia Mobile Phones Limited Method for using applications in a mobile station, a mobile station, and a system for effecting payments
US20020091933A1 (en) * 2001-01-05 2002-07-11 Quick Roy F. Local Authentication in a communication system
US20020111987A1 (en) * 1995-08-04 2002-08-15 Belle Gate Investment B.V. Data exchange system comprising portable data processing units
US6501962B1 (en) * 1996-09-13 2002-12-31 Orange Personal Communications Services Limited Mobile communications terminal smart card
US20030039263A1 (en) * 1999-01-29 2003-02-27 Avaya Technology Corp. Application module interface for a control channel in a private branch exchange (PBX) environment
US6725048B2 (en) * 2000-09-22 2004-04-20 Ericsson Inc. Traffic congestion management when providing realtime information to service providers
US6839756B1 (en) * 1999-02-19 2005-01-04 Bull Cp8 On board system comprising network interface means, and method for activating applications located in said on-board system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1183449C (en) * 1996-10-25 2005-01-05 施卢默格系统公司 using a high level programming language with a microcontroller

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6418326B1 (en) * 1995-02-15 2002-07-09 Nokia Mobile Phones Limited Method for using applications in a mobile station, a mobile station, and a system for effecting payments
US20020111987A1 (en) * 1995-08-04 2002-08-15 Belle Gate Investment B.V. Data exchange system comprising portable data processing units
US6216014B1 (en) * 1996-05-17 2001-04-10 Gemplus Communication system for managing safely and independently a plurality of applications by each user card and corresponding user card and management method
US6501962B1 (en) * 1996-09-13 2002-12-31 Orange Personal Communications Services Limited Mobile communications terminal smart card
US6131040A (en) * 1997-06-19 2000-10-10 Nokia Mobile Phones Limited Wireless communication device receiving configuration data from multiple sources
US20020040936A1 (en) * 1998-10-27 2002-04-11 David C. Wentker Delegated management of smart card applications
US20030039263A1 (en) * 1999-01-29 2003-02-27 Avaya Technology Corp. Application module interface for a control channel in a private branch exchange (PBX) environment
US6839756B1 (en) * 1999-02-19 2005-01-04 Bull Cp8 On board system comprising network interface means, and method for activating applications located in said on-board system
US6725048B2 (en) * 2000-09-22 2004-04-20 Ericsson Inc. Traffic congestion management when providing realtime information to service providers
US20020066792A1 (en) * 2000-12-06 2002-06-06 Mobile-Mind, Inc. Concurrent communication with multiple applications on a smart card
US20020091933A1 (en) * 2001-01-05 2002-07-11 Quick Roy F. Local Authentication in a communication system

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080287162A1 (en) * 1999-05-11 2008-11-20 Gemplus Radiotelephone terminal with chip card provided with browser
US7986969B2 (en) * 1999-05-11 2011-07-26 Gemalto Sa Radiotelephone terminal with chip card provided with browser
US20050192054A1 (en) * 2003-09-08 2005-09-01 Nec Corporation Mobile station intermittently receiving a radio signal
US7526318B2 (en) * 2003-09-08 2009-04-28 Nec Corporation Mobile station intermittently receiving a radio signal

Also Published As

Publication number Publication date
ATE290744T1 (en) 2005-03-15
AU1145800A (en) 2001-06-04
EP1230780B1 (en) 2005-03-09
US6847831B2 (en) 2005-01-25
US20020198022A1 (en) 2002-12-26
DE59911743D1 (en) 2005-04-14
EP1230780A1 (en) 2002-08-14
WO2001039464A1 (en) 2001-05-31

Similar Documents

Publication Publication Date Title
AU739906B2 (en) A method, a smart card and terminals for effecting transactions through a telecommunication network
US8914489B2 (en) Method of personalizing an application embedded in a secured electronic token
US8814051B2 (en) Personal token having enhanced communication abilities for a hosted application
US9037857B2 (en) System and method for downloading application
US6847831B2 (en) Adaptable chip card
FI109756B (en) A method of utilizing local resources in a communication system, a communication system and wireless communication
Reveilhac et al. Promising secure element alternatives for NFC technology
US7496193B2 (en) Method for the administration of a subscriber card for mobile telephony equipment of the type with auxiliary reader and embedded system for the implementation of the method
JP2002544610A (en) Storage media
JP3689242B2 (en) Method for adapting the functionality of a subscriber identification module to one or more interfaces of a mobile terminal for wireless communication, and corresponding subscriber identification module and mobile terminal
AU7989698A (en) Method of downloading a list of items into a mobile terminal
US20130331134A1 (en) Method for transmitting mini-messages and associated device
EP2353258B1 (en) Client - server communications in mobile radio communications device
US6775725B1 (en) Preparation and execution of a program in an additional chip card of a terminal
US7606931B2 (en) Method with which a first application can access components of a second application over a logical interface
JP4173862B2 (en) How to load applications deployed in terminals and chip cards
EP2159666A1 (en) Surface-mounted device with multi-layered SIM cards
EP1720366A2 (en) System of remote access of mobile equipment to mobile telephony services
CN102484645A (en) Method Of Managing An Application Embedded In A Secured Electronic Token
EP4195717A1 (en) Supporting multiple euicc profiles
CN1586085B (en) Method for enabling an application recorded in a radiocommunication terminal to access functions of the terminal and terminal implementing said method
GB2368702A (en) Mobile telephone provided with a microcircuit card reader
US20020196786A1 (en) Method and apparatus for data transmission
CN111742316A (en) Method for managing a tamper-resistant device comprising several software containers
CZ20001833A3 (en) Method, chip card and terminals for making transactions via a telecommunication network

Legal Events

Date Code Title Description
AS Assignment

Owner name: SWISSCOM MOBILE AG, SWITZERLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HUBER, ADRIANO;REEL/FRAME:020759/0667

Effective date: 20080326

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: SWISSCOM (SCHWEIZ) AG, SWITZERLAND

Free format text: CHANGE OF NAME;ASSIGNOR:SWISSCOM MOBILE SA (SWISSCOM MOBILE LTD);REEL/FRAME:023529/0473

Effective date: 20071212

Owner name: SWISSCOM (SCHWEIZ) AG,SWITZERLAND

Free format text: CHANGE OF NAME;ASSIGNOR:SWISSCOM MOBILE SA (SWISSCOM MOBILE LTD);REEL/FRAME:023529/0473

Effective date: 20071212

AS Assignment

Owner name: SWISSCOM AG, SWITZERLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SWISSCOM (SCHWEIZ) AG;REEL/FRAME:023534/0784

Effective date: 20090916

Owner name: SWISSCOM AG,SWITZERLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SWISSCOM (SCHWEIZ) AG;REEL/FRAME:023534/0784

Effective date: 20090916