The present invention relates to smart cards in general and in particular to methods and devices for installing and hiding applications onto smart cards. Particularly, the smart card can be based on the Java Card technology and can be a payment transaction card or a SIM (Subscriber Identity Module) card device for mobile communication of any form factor, implying plug-in SIM cards and embedded eUICCs for fixed mounting into a mobile device.
Java Card technology enables secure elements, such as smart cards and other tamper-resistant security chips, to host applications (applets) which employ Java technology. Java Card offers a secure and interoperable execution platform that can store, update and run multiple applications on a single resource-constrained device, while retaining the highest certification levels and compatibility with standards.
The GlobalPlatform Card Technology Specification sets up a global standard for cards and/or secure elements issuers that shall be implemented on smart cards. In particular, the GlobalPlatform Card and API specification define a card management framework which complements the Java Card specification by defining a set of commands that can be used to manage applications on a Java Card product.
Based on the GlobalPlatform technologies, multi-application product lines have been put forward, as for example Giesecke+Devrient's Convego® Join, which allows to implement and combine value-added applications onto smart cards, such as, loyalty schemes, transport apps, and authentication solutions.
Manufacturing a smart card usually involves an initialization and a personalization process. During the initialization process, an integrated circuit chip is embedded into the plastic card body. The chip is loaded with at least one application program, such as a credit or a stored value application. After a card is initialized, it is then typically personalized. During personalization, the smart card is generally loaded with data that uniquely identifies the card, and with data that allows the card to be used for example in a payment system. Personalization data may include file information, application information, a personal identification number (PIN) or other cardholder information. Further information may be included, such as the currency in which the card or application is valid, the expiration date of the card or application, and a variety of cryptographic keys and algorithm information for the card or applications on the card.
Card personalization amounts to one of the major cost components in the production of smart cards. In particular, the personalization process duration is a critical factor, as it requires loading a significant amount of data into the Java Card memory during personalization.
In particular, it is currently observed that installation of Java Card payment applets on top of the Convego® Join Operating System (OS) consumes a substantial amount of the secure element's CPU execution time, notably between 1 to 2 seconds. This execution time is beyond acceptable limits and has to be reduced significantly.
It is therefore desirable to provide a solution for a time-efficient personalization of a Java Card that overcomes the above-mentioned drawbacks.
Document [1]
Document [2]
The present invention addresses the above object by the subject-matter covered by the independent claims. Preferred embodiments of the invention are defined in the dependent claims.
According to a first aspect of the present invention, there is provided a method for installing applet instances in a card device, the card device comprising an operating system, OS. The method comprises in a step receiving from an off-card entity a request for installing an instance of a first applet, the request for installing comprising a first applet identifier, AID. In a subsequent step, an applet instance with the first applet identifier is installed in a registry of the OS. In a further step, a request, sent from the off-card entity, for hiding the instance of the first applet identified by the first applet identifier is received at the card device. Subsequently, the applet instance identified by the first applet identifier is hidden on the card device.
The proposed method provides an efficient solution to time-saving personalization of a Java card, since it allows to install several applet instances for frequently used applications in the Java card before the personalization is actually performed. Since at this time it is not known which applet instances will be needed/used later during personalization of the card, these applet instances are, after having been installed, "hidden" in the card. A hidden applet instance is physically present on the card device, however not visible from outside. That is, the card device or secure element will not reveal the presence of a hidden applet instance, when requested. Later on, when personalization of the card is effected, and decided which applet instances to be used, the corresponding already installed hidden applet instances can be unhidden and made visible, and directly used during personalization, without having to upload and install a complete applet instance unto the Java card.
In some embodiments of the present invention, the method further comprises receiving from the off-card entity a further request for installing an instance of a second applet, the further request comprising a second applet identifier, wherein the second applet is different from the first applet; checking whether the second applet identifier matches the applet identifier of one of the hidden applet instances; if the second applet identifier matches the applet identifier of one of the hidden applet instances, changing the applet identifier of the hidden applet instance to a new applet identifier; and installing the instance of the second applet with the second applet identifier in the registry of the OS.
This allow to install in the card device, before personalization, several new instances of different applets, while avoiding an applet identifier conflict, that may arise due to already hidden applet instances with the same AID. As no two applet instances can have the same AID, the OS will usually not allow installation of two applet instances with the same AID.
According to the present invention, the method further comprises receiving from the off-card entity a request for installing an instance of a third applet, the request comprising a third applet identifier identifying the instance of the third applet; checking whether there is a hidden applet instance of the third applet installed in the card device; checking whether the applet identifier of the hidden applet instance matches the third applet identifier; and if the applet identifier of the hidden applet instance matches the third applet identifier, unhiding the hidden applet instance.
This allows during personalization, when a request is received to install a new applet instance, to find, disclose and reuse a suitable hidden applet instance, instead of creating a new one from scratch. This intelligent re-use save crucial production time, thereby increasing production throughput. In particular, disclosing and reusing applet instances consumes between 0.1-0.2 seconds which is an on average 80% improvement over applet installation from scratch.
Preferably, if the applet identifier of the hidden applet instance differs from the third applet identifier, the applet identifier of the hidden applet instance is changed to the third applet identifier before unhiding the hidden applet instance.
Preferably, if there is no hidden applet instance of the third applet in the card device, the instance of the third applet is installed with the third applet identifier in the card device.
The number of applets, first, second, third applet, are given as examples. The invention is not restricted to 3 different applets. It is generic and applies to any number of different applets within a card device.
Preferably, the request for installing an instance of an applet comprises further installation parameters.
In some embodiments of the present invention, installing an applet instance with an applet identifier in the card device comprises creating a new applet instance, and storing in the OS registry the new applet instance with the applet identifier and preferably installation parameters received from an off-card entity.
By default, upon installing an applet instance the status of the newly installed applet instance should be "visible", meaning that the applet instance is visible from outside and the applet instance can be accessed and selected upon request. Alternatively, the step of installing an applet instance with an applet identifier in the card device may comprise explicitly setting a status of the applet instance to visible.
In some embodiments of the present invention, the request for hiding an instance of an applet comprises further installation parameters, and checking whether there is a corresponding visible applet instance installed in the card device for the applet comprises further checking whether the received installation parameters match installation parameters which were received with a request for installing the corresponding applet instance.
This ensures that when an instance of an applet is to be hidden, the selected installed applet instance is a correct match and no unrelated installed applet instance is wrongly hidden.
Preferably, hiding an installed applet instance comprises setting a status of the applet instance to hidden. A hidden applet instance is physically present on the card device, however not visible nor selectable (i.e, accessible) from outside.
Preferably, the request for installing an instance of a third applet comprises further installation parameter for the third applet, and wherein checking whether there is a hidden applet instance of the third applet installed in the card device comprises further checking whether the received installation parameters match installation parameters which were received with a request for installing the hidden applet instance.
This ensures that, during personalization, a request for installing a new applet instance is sent by the off-card entity and received at the card device with exactly the same installation parameters like the ones used to install the hidden applet instance. This check can be implemented in the card device or in the off-card entity. Only a hidden applet instance exactly matching a new applet instance to be installed can thus be unhidden and used, avoiding therefore the use of a wrong applet instance during personalization.
Preferably, unhiding a hidden applet instance comprises changing the status of the applet instance from hidden to visible.
According to a second aspect of the present invention, a card device is provided. The card device comprises a card operating system, OS, and is configured to receive from an off-card entity a request for installing an instance of an applet, the request comprising an applet identifier, and to install an applet instance with the received applet identifier in a registry of the OS. Further, the card device is configured to receive from the off-card entity a request for hiding the instance of the applet identified by the applet identifier, and to hide the applet instance identified by the applet identifier.
Preferably, the card device is further configured, upon receiving from the off-card entity the request for hiding an instance of an applet installed in the OS registry, to apply to the applet instance a HIDE command to change a status of the applet instance from visible to hidden.
In some embodiments of the present invention according to the second aspect, the card device is further configured, upon receiving from the off-card entity the request for installing an instance of an applet, to check whether the received applet identifier matches an applet identifier of one of the hidden applet instances. If the received applet identifier matches the applet identifier of one of the hidden applet instances, the applet identifier of the hidden applet instance is changed to a new applet identifier, and the instance of the requested applet to be installed is installed with the applet identifier in the OS registry. Preferably, the card device is further configured to set a status of the installed applet instance to visible.
Preferably, the card device according to the second aspect is further configured to perform the method according to the first aspect and/or the embodiments of the first aspect.
According to a third aspect of the present invention, an Application Protocol Data Unit, APDU, Hide command is provided. The APDU Hide command comprises a data field for transferring an applet identifier, AID, of an applet instance to be hidden on a card device, and is configured to cause the card device upon applying the command to change the status of an installed applet instance from visible to hidden.
This provide a proprietary interface, which allows to install hidden applet instances in a card device.
Preferably, both the method according to the first aspect of the present invention and the card device according to the second aspect of the present invention implement the request for hiding an instance of an applet by the APDU Hide command according to the third aspect.
It has to be noted that all the devices, elements, units and means described in the present application could be implemented in software or hardware elements or combination thereof. All steps which are performed by the various entities described in the present application as well as the described functionalities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities.
Further aspects, features and advantages of the present invention will become apparent to those of ordinary skill in the art upon reviewing the following detailed description of preferred embodiments and variants of the present invention in conjunction with the accompanying figures.
Reference will now be made to the accompanying figures, in which
Detailed explanations of the present invention are given below with reference to attached drawings that illustrate specific embodiment examples of the present invention. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It is to be understood that the various embodiments of the present invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described herein in connection with one embodiment may be implemented within other embodiments without departing from the scope of the present invention. In addition, it is to be understood that the position or arrangement of individual elements within each disclosed embodiment may be modified without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims, appropriately interpreted, along with the full range of equivalents to which the claims are entitled. In the drawings, like numerals refer to the same or similar functionality throughout the several views. Through this specification, the expressions "Java Card", "card device" and "secure element" are used interchangeable.
Associated with each applet 130 on smart card 100 is an Application Identifier (AID) 131 (131-1, 131-2, 131-3). The AID is a byte string up to 16 bytes long, whose format is defined by International Standard ISO/IEC 7816-5, and is used to uniquely identify an applet instance.
The off-card entity 200 comprises and APDU Tool 210 for sending APDUs (Application Protocol Data Units) commands to the Java Card OS 110 of the card device 100. Applets are loaded into a card device by means of APDU commands, as specified in the Global Card Platform Specification. In particular, an applet is installed in a card device by loading a load packet for the applet into the card device with the LOAD command, while an instance of the applet is installed in the card device with an INSTALL (Install [for Install] APDU) command. The Install [for Install] APDU is described in the GlobalPlatform Card Specification, according to which the AID of an applet instance to be installed is transferred in the data field of the INSTALL command, notably in the sub-field "Application AID". A further sub-field, the "Install Parameters field" carry installation parameters. In particular, installation parameters comprise application specific parameters, system specific parameters, and control parameters.
During real-life production, card personalization usually requires loading and installing a significant amount of data into the Java Card memory, increasing thus the overall personalization time.
The present invention proposes a solution to time-saving personalization of a Java card. To have to transfer less data at personalization time, several applet instances for frequently used applications are installed in the Java card before the personalization is actually performed. As at this time it is not known which applet instances will be needed/used later on during personalization of the card, these applet instances are, after having been installed, "hidden" in the card. A hidden applet instance is physically present on the card device, however not visible and not directly accessible from outside. That is, the card device or secure element will not reveal the presence of a hidden applet instance, when requested. Later on, when personalization of the card is effected, and decided which applet instances to be used, the corresponding already installed hidden applet instances are made visible. In this case, there is no need to upload or create a complete applet instance unto the Java card, but only to unhide an already installed hidden applet instance. This process of installing, hiding, and unhiding applet instances leads to a reduction of personalization or applet installation time for up to 80% over the conventional approach.
With reference to
Upon receiving the request, the card device 100 creates and registers in the operating system, OS, 110 a new applet instance with AID_1 (step S11). By default, the status of this instance is "visible". Alternatively, the status can be explicitly set to "visible". For specifying the visibility status of an applet instance, a Boolean flag associated with each applet instance, e.g., "0" indicating "hidden" and "1" indicating "visible", can be used. Other implementations are also possible, for example managing a list of visible applet instances. Applet instances can be stored in a registry of the OS.
In a further step, S2, the card device 100 receives from the off-card entity 200 a request for hiding the instance of the first applet identified by the first applet identifier. As with the installing request, this request for hiding an applet instance is generated by the APDU Tool 210 in the off-card entity 200 (step S22), and send through the APDU command "Hide" to the card device 100. For instance, the request is for hiding the "instance of Applet_A with AID_1".
Upon receiving the request, the card device 100 finds the instance of Applet_A with AID_1 in the OS registry and change the visibility option/status of the found applet instance from "visible" to "hidden".
Steps S1 and S2 described above allow to install and hide several applet instances before card personalization, as will be described in detail below, with reference to
During the personalization process, to make a hidden applet instance visible, an Install [for Install] APDU is generated, S23, by the off-card device 200, and sent to the Java card 100 in step S3. Upon receiving the request, it is checked, S13, whether there exists any matching hidden instance in the OS registry. If a matching applet instance is found, the applet instance in unhidden, that is, its visibility option/status is changed from "hidden" to "visible". Further details of this unhiding process are given below with reference to
When an instance of a new applet (Applet_A) is to be installed with an applet identifier (AID_i) S110, under the assumption that instances of at least a different applet have already been installed and hidden in the card device, it is first checked S120 whether the received AID_i match with an applet identifier of a hidden applet instance. If this is the case, the applet identifier of the matching hidden instance will be changed S121 internally, that is, in the OS registry, to a new applet identifier, e.g., AID_k. After the change is effected, a new instance for Applet_A is created S130, and stored S140 together with AID_i in the OS registry.
In this way, an AID conflict is avoided, and both applets instances can be installed in the OS registry. Otherwise, the card device OS will not allow installation of two applet instances with the same AID.
After the new instance for Applet_A with AID_i has been stored in the OS registry, the status of this instance is set to "visible" (S150). Alternatively, the status can be specified to be by default "visible" upon storing the instance. For specifying the visibility status of an applet instance, a Boolean flag associated with each applet instance, e.g., "0" indicating "hidden" and "1" indicating "visible", can be used. Other implementations are also possible, for example managing a list of visible applet instances and a list of hidden applet instances.
With respect to the overall method described in
After a new instance for an applet has been installed in the card, a request to hide the applet instance is received in step S160. The card's OS finds the corresponding matching instance of Applet_A with AID_i and changes the status to "hidden", S170.
Steps S160 and S170 are a preferred implementation of step S12 in
The method illustrated in
During personalization, to make a hidden applet instance visible, the Install [for Install] APDU is sent by the off-card entity 200 to the card device 100. The request contains the applet identifier, AID among other fields, such as applet name and installation parameters.
At the card device, upon receiving the request for installing Applet_A with AID_i in step S210, a suitable hidden applet instance is searched in the OS registry, S220. If a matching hidden applet instance is found, in a further step S230 the card device checks whether the AID, AID_k, of the hidden applet instance corresponds to the received AID, that is, whether AID_k = AID_i. This step is performed, since during installation of the hidden applet instance its original AID might have internally changed to avoid a potential AID conflict with other hidden applet instances.
If the AID of the matching hidden applet instance differs from the AID applet instance to be installed, the applet identifier of the matching hidden applet instance is changed back to the received AID, AID_i, in step S240, after which the hidden applet instance is made visible in step S250.
If the applet identifier of the hidden applet instance corresponds to the received AID_i, step S240 is skipped and step S250 is directly performed, by changing the status of the matching hidden applet instance to "visible".
If there is no hidden applet instance matching the new applet to be installed, an instance of this new applet will be installed from scratch. This include, creating S260 and storing S270 a new instance for Applet_A with AID_i in the OS registry. Preferably, the status of this applet instance is by default "visible". Alternatively, the status can be set to "visible" in a further step S280.
According to the implementation details described above for the step for hiding an applet instance before card personalization (S12), as well as for the step for unhiding an applet instance during card personalization (S13), it is checked whether there is a corresponding visible/hidden applet instance installed in the card device for the applet instance (S120, S170, S220).
In addition to checking the AID (and possibly the applet name) of the applet instance against already installed applet instances, a further check can be performed to detect whether installation parameters match. Preferably, the request for installing an instance of an applet and/or the request for hiding an instance of an applet comprises further installation parameters, and wherein checking whether there is a corresponding hidden and/or visible applet instance installed in the card device for the applet comprises further checking whether the received installation parameters match installation parameters which were received with a request for installing the corresponding applet instance.
Such an additional check can be implemented in the steps S120, S170, S220 described above. To support a comparison of installation parameter used to install applet instances, installation parameters can be stored in the OS registry together with the applet identifier for each applet instance installed in the card device.
By the above-described method, during personalization when a request is received to install a new applet instance, a suitable hidden instance is found, disclosed, that is, made visible, and reused instead of creating a new one from scratch. This intelligent re-use save crucial production time, thereby increasing production throughput.
Installing visible applet instances in a secure element or card device can be done via a standard interface, such as GlobalPlatform's Install [for Install] APDU command. However, there is no standard interface that supports installation of hidden applet instances within the card device.
Therefore, in a second aspect of the present invention, a proprietary APDU command is proposed. After receiving such an APDU, secure element's OS will find the applet instance with the given AID and hide it. Preferably, the APDU command "Hide AID_i" comprises a data field for transferring an applet identifier, AID_i, of an applet instance to be hidden on a card device 100. The Hide APDU is configured to cause the card device 100 upon applying the command to change the status of an installed applet instance, identified by AID_i, from visible to hidden.
The request for hiding an instance of an applet sent in step S2 by the off-card entity to the card device (as depicted in
In a further aspect of the present invention, the card device 100 in
The above embodiments for installing, hiding and unhiding Java Card applet instances of the present invention provide several advantages due to the reduced data transfer at personalization time. In particular:
To avoid an increase in memory consumption caused by installing several applet instances compared to the conventional approach of uploading applet instances only when needed, applet instances to be uploaded before personalization are selected based on criteria such as frequency of use or use case relevance.
In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader scope of the invention. For example, the above-described process flows are described with reference to a particular ordering of process actions. However, the ordering of many of the described process actions may be changed without affecting the scope or operation of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense.
This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.