Method and system for personalizing secure elements

By loading an operating system image onto the secure element and using configuration commands to control the personalization process, the flexibility issue of the secure element personalization process is solved, enabling segmented personalization and firmware updates at different times and locations, thereby improving production efficiency and security.

CN119053980APending Publication Date: 2024-11-29GIESECKE & DEVRIENT EPAYMENTS GMBH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034920.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-20
Filing Date
2023-04-21
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The personalization process for security elements in existing technologies lacks flexibility, cannot effectively allocate production time and location, and is limited by firmware updates, making it impossible to expand data sets.

Method used

By loading an operating system image onto a secure element and controlling the personalization process using configuration commands, it allows for segmented personalization of data groups at different times and locations, supporting distributed personalization and firmware updates.

Benefits of technology

It enables flexibility and scalability in the personalization process of security elements, allowing production time to be allocated at different locations and times, supporting firmware updates and bug corrections, and meeting different security requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119053980A_ABST
    Figure CN119053980A_ABST
Patent Text Reader

Abstract

The invention relates to a method for personalizing a secure element in a computer-aided manner, on which an image is loaded, in which an operating system of the secure element is integrated. In the method according to the invention, one or more data sets (DS) individually provided for the secure element are written into a special storage area of the secure element. In personalization of a secure element, a configuration command (CSP) is used to determine an order in which a data set (DS) to be written is personalized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to a method and a system for computer-assisted personalization of a security element, onto which an image is loaded, in which an operating system of the security element is integrated. Background Art

[0002] The secure element is, for example, a participant identity module in the form of a universal integrated chip card (Universal Integrated Chip Card=UICC) for managing authentication data for the use of services of a communication network. In other embodiments, the secure element is an embedded UICC (embedded UICC=eUICC), a "chip card", an integrated eUICC (Integrated eUICC ("iUICC")), an integrated secure element, an embedded secure element, a Secure Element, a SIM or a chip card.

[0003] During the production of a security element, for example an eUICC, the security element is personalized with individual data. Here, first an image (English: "image") is loaded onto the security element. This processing is performed, for example, at the manufacturer of the security element. Subsequently, the data provided individually for the security element are written into a special data area on the security element. This step can also be performed, for example, at the manufacturer of the security element. Afterwards, the personalization is performed, which will be explained further below.

[0004] The data provided separately for the security element may include confidential data, such as keys, trusted root certificates, PINs, etc. These data are therefore non-public and can only be accessed by a limited range of people. In addition, the separate data may also include non-confidential (i.e. public) data, such as the identification of the security element, public certificates, etc. The confidential data may be personalized separately from the non-confidential data, such as at the initial startup of the security element after the confidential data is loaded onto the security element. This personalization may be performed, for example, at the manufacturer of the security element or at the manufacturer of the terminal device into which the security element is to be integrated. Individual confidential data is usually personalized during the use of a secure handshake method. This processing is usually performed at the manufacturer of the terminal device.

[0005] When personalizing confidential and non-confidential data, objects are allocated or created in the secure element, and then the individual data is written to the objects later. After the data is written, personalization is complete.

[0006] EP 1 622 098 A1 describes a design for distributed personalization of a security element. Here, a first command sets the security element to a state in which it only accepts a second command, which enables secure personalization. The personalization itself is performed by means of a third command.

[0007] EP 2 289 225 B1 discloses a method for personalizing a secure element of a mobile terminal device, in which distributed personalization is also applied. Here, a method is described in which the production of the secure element and the installation of the operating system are carried out at one location, and the personalization of the secure element is carried out at another secure location. For this purpose, it is proposed to finally personalize the secure element when the user uses the terminal device for the first time.

[0008] A method for initializing and personalizing a chip card is known from DE 199 39 280 A1. Data structures are created in the data memory of the chip card, which data structures make it possible to uniquely associate personalization data with the respective chip card application. In a preliminary initialization step, an application description and an associated personalization description are created in the memory blocks of the memory area to be personalized. During subsequent personalization, the personalization data are transferred to the chip card for the application and associated with the application by means of the personalization description. Apart from the personalization data, no further additional data need to be transferred. Summary of the invention

[0009] The object of the present invention is to further improve the flexibility when personalizing a security element.

[0010] This object is achieved by a method for computer-aided personalization of a security element according to the features of patent claim 1 and by a system for computer-aided personalization of a security element according to the features of patent claim 11. Advantageous embodiments are disclosed in the dependent claims.

[0011] In the method for personalizing a security element in a computer-aided manner according to the present invention, an image is loaded on the security element, and the operating system of the security element is integrated in the image. In the method, one or more data groups provided separately for the security element are written into a special storage area of ​​the security element. The separate data group contains data separate for the card, and the security element is personalized under the control of the operating system using the data separate for the card. Therefore, the method according to the present invention is based on a security element that is pre-personalized in a manner known per se, and an image with an operating system is loaded on the security element, and the operating system is used to run the security element. The loading or writing of one or more data groups provided separately for the security element can also be carried out in a manner known per se. The term "data group provided separately for the security element" should be understood as information that is only uniquely provided for a single security element, such as a key, a certificate, etc. It is suitable to provide data separate for the card in the form of a data block or a data group chain. In addition to the data separate for the card, the data group chain can also contain the following data, which are, for example, unique to a specific series of security elements, i.e., for example, so-called batch global data (Batch-globale Daten).

[0012] In the course of the method according to the invention, during the personalization of the secure element, the order in which the data records to be written are personalized is determined using configuration commands.

[0013] The use of such configuration commands makes it possible to interrupt the step of introducing the personalization data in a controlled manner and to continue it at a later point in time. This can be used, for example, to divide the production time between different locations. For example, general production can be carried out at one location, while further personalization is carried out at the end customer. This reduces the production time at a factory, for example at a manufacturer of security elements.

[0014] For example, the personalization can also be divided into logical sequences corresponding to the required logic, for example according to the required logic. Thus, for example, the introduction of the necessary information can be separated from the personalization of the boot profile.

[0015] Another possibility opened up by the use of configuration commands is to divide the personalized segments into different locations according to the confidentiality and security requirements of the personalized.

[0016] Another advantage of the process according to the invention is that it is possible to perform only partial personalization so that an update can be performed before further personalization. Depending on the personalization step, different components outside the security element, such as a server, can also participate. These components are also referred to as non-card components. These components can be provided in different environments, which can have authenticated access, non-authenticated access or HSM access, if necessary. Depending on the involved components outside the security element, different security mechanisms can be implemented.

[0017] According to a suitable embodiment of the method, the configuration command determines which data of one or more of the data sets are to be personalized in the first step. After the personalization of these data in the first step, further personalization is then interrupted. Thus, for example, it can be determined which data are to be personalized in the factory of the user of the security element. Subsequently, further personalization can be performed at a later point in time.

[0018] According to another suitable design, it is provided that one or more interruption points for personalizing the data set are set by the configuration command. Thus, the time point of the interruption in the personalization process can be defined. In other words, it is determined until which data set is to be personalized and when the interruption is to be performed.

[0019] Another suitable design is to configure the continuation of personalization at a later point in time by means of a configuration command. According to one design, this can be done in the following way, that is, a pre-given event is configured by means of a configuration command, and personalization is continued when this event occurs. Such an event can be, for example, a restart (Reset) of a security element or the reaching of a pre-given number of restarts of a security element. Then, when such an event occurs, further personalization is continued. In this case, multiple implicit personalization steps can be configured. For example, for each event, only a part of the data set is personalized, and then interrupted. Then, when the next event occurs, further personalization is performed.

[0020] In another embodiment, it is provided that the configuration command is sent to the security element at least once more, so that the personalization is continued at a later point in time. This process of personalization also enables the personalization of other parts of the data set in distributed steps. Further distributed steps can be performed by receiving further implicit configuration commands in dependence on the occurrence of predefined events.

[0021] In this way, the data set can be personalized at different times and different locations depending on the urgency. For the production of the terminal device using the security element, the important personalization can be carried out immediately. For example, further personalization can be carried out later at the customer of the terminal device. This distributes the overall time for personalization and thus the production time for the manufacturer of the security element.

[0022] According to another suitable embodiment, the configuration command is sent to the secure element at least once more, whereby the personalization is continued (after the interruption at a later point in time). Thus, the configuration command can be sent to the secure element once or several times. Depending on the application and the security requirements, the configuration command can be transmitted to the secure element in an encrypted or unencrypted manner. The encryption and / or transmission can be performed according to methods known from the prior art.

[0023] Thus, the event for continuing the personalization can be configured with the configuration command. For example, a configuration is possible in which, after a restart of the secure element, further personalization is performed with a predetermined data set, for example, data sets #2 to #3. The remaining data is then subsequently personalized with the next restart.

[0024] In the event that personalization is to be continued by explicitly receiving further configuration commands, the configuration commands are sent to the secure element at least once more. Nevertheless, a trigger command for initialization and for starting personalization in the prior art has only been required once so far. As a result, backward compatibility with existing systems continues to be supported without further adaptation being required.

[0025] Another suitable design provides that in a first step, the firmware update key is personalized in one of the data sets. Then, in a second step, the firmware update is performed. This provides the possibility of being able to perform a firmware update before the security element is completely personalized. The card-specific data or confidential data can contain the firmware update key that is mandatory for a later firmware update.

[0026] Since a firmware update is not possible without a firmware update key, the update can only be performed in the traditional way after the personalization is completed. This means that the code executed during the personalization process cannot be changed and that the code must know the future structure of the data set that will be loaded later without errors at the time of creation. This limits the use of secure elements in the prior art, because the data set may not be expanded later. It is also impossible to eliminate errors during the personalization process.

[0027] These disadvantages can be eliminated by the proposed process. By personalizing only the firmware update key in a first step, this allows the operating system, including the code for further personalization, to be updated immediately afterwards. This makes it possible to add new features that were not known at the initial development time or to personalize these new features. In addition, errors that may occur during the personalization process can be eliminated.

[0028] In addition to the personalization method described above, the present invention also relates to a system for personalizing a security element in a computer-aided manner, an image being loaded on the security element, in which an operating system of the security element is integrated, wherein the system is configured to perform the personalization method according to the present invention according to one or more preferred design aspects of the personalization method.

[0029] The present invention enables different trust levels (English: "Level of Trust") through controlled personalization. The trust levels of units outside the security element that participate in the personalization process (non-card components) can also be adjusted accordingly. This means that, depending on the application, different components, such as production machines, participating servers may be involved. Thus, for example, the firmware update key can be partially personalized at the manufacturer of the security element, and the subsequent sensitive data can be partially personalized at the production site of the terminal device manufacturer who is to introduce the security element into its terminal device. The data group to be personalized can also be protected in different ways. Each production site can then only decrypt the area predetermined by itself.

[0030] This results in a considerable flexibility and scalability of the personalization process. The personalization process can be divided into a plurality of parts in order to distribute production times and production locations and / or to change and / or expand the personalization process. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The present invention will be described in detail below based on the embodiments shown in the accompanying drawings.

[0032] In the attached picture:

[0033] Figure 1 A flow chart is shown in which the configuration of a distributed personalization of a security element is explained;

[0034] Figure 2 A flow chart is shown in which a personalization which has already been started is continued with the aid of an explicitly received configuration command;

[0035] Figure 3 A flow chart is shown in which a personalization that has already begun is continued upon the occurrence of a preconfigured event;

[0036] Figure 4 A flow chart is shown which illustrates distributed personalization of a secure element;

[0037] Figure 5 A data set chain with a plurality of data sets to be personalized is shown, which are protected with a uniform key; and

[0038] Figure 6 A data record chain is shown with a plurality of data records to be personalized, which are protected in different ways according to the different personalization steps to be carried out. DETAILED DESCRIPTION

[0039] The invention is described below with reference to a security element to be integrated into a terminal device, such as a mobile phone. Preferably, the security element is a participant identity module in the form of an embedded Universal Integrated Chip Card (embedded Universal Integrated Chip Card=eUICC) fixedly installed in the terminal device for managing authentication data for use of a mobile radio network. In other embodiments, the security element can also be a UICC (=Universal Integrated Chip Card), an integrated eUICC ("iUICC (Integrated eUICC)"), a SIM (=Subscriber Identity Module) or a chip card.

[0040] The starting point of the method is a secure element (not shown in the figure) with an operating system installed. This is usually done by the chip manufacturer of the secure element. The operating system is integrated into an image ("image"), which also contains a so-called root profile.

[0041] After the image is mounted on the secure element, the card-specific data are written into a special storage area of ​​the secure element. These card-specific data can consist of confidential data (e.g. keys, trusted root certificates, PINs, etc.) and non-confidential data (e.g. card ID, public certificates). The card-specific data are stored as data set DS (see Figure 5 and Figure 6 ) exists. It is suitable to provide card-specific data in the form of data blocks or data group chains, such as Figure 5 and Figure 6 In addition to the card-specific data, the data chain can also contain, for example, data that are jointly specific to a particular series of security elements. The data blocks or the card-specific data can also be introduced, for example, at the chip manufacturer.

[0042] Subsequently, under the control of the operating system, the card-specific data are personalized accordingly, i.e. made accessible to the operating system, by means of configuration commands, i.e., the keys required for operating system functions, such as for performing firmware updates, are written to the location in the storage area where the operating system expects and needs the keys.

[0043] The individual data for the card can have different confidentiality levels. In principle, the non-confidential data can be personalized separately from the confidential data, for example after the secure element is powered on for the first time and once the data has been loaded. This is usually done at the manufacturer of the secure element or partly at the device manufacturer of the terminal device in which the secure element is installed.

[0044] Personalization of confidential data is usually performed during a secure handshake method using authentication and key exchange. Personalization can be performed at a later point in time, for example, at the device manufacturer.

[0045] At the time of personalization, an object is created in the security element corresponding to the card-specific data. Depending on the size of the object, the creation of the object may take up production time, wherein after the creation the object is personalized with the corresponding card-specific data.

[0046] Personalization can therefore be done in three different locations:

[0047] a) at the manufacturer of the operating system of the secure element, where the image is introduced into the secure element,

[0048] b) at the chip card manufacturer, where the card-specific data are loaded, wherein non-confidential data can optionally be personalized, and

[0049] c) At the device manufacturer, where the non-confidential data is personalized if not already done, and finally the confidential data is personalized.

[0050] With the method according to the invention described below, the order in which the data sets DS are personalized can be determined by using configuration commands in the personalization of the security element. The configuration commands do not contain personalization data, but only configure the execution of the personalization, i.e. the individual data contained in the data sets DS are provided to the operating system under the control of the operating system. In particular, it is determined how many data sets DS are personalized or at which data set DS the personalization should be interrupted. The configuration commands enable the interruption and later continuation of the personalization in a controlled manner.

[0051] For this purpose, the card-specific data used in the personalization process are divided into different data sets DS, such as Figure 5 and Figure 6All card-specific data for the security element are expediently provided together in a data set chain together with any series-specific data that may be present.

[0052] exist Figure 5 , which comprises, by way of example, seven data sets DS. These data sets are all protected with a common or identical key K1. The security element obtains the key K1 from the personalization device via a handshake method. The first data set comprises, for example, the FWU key, the second data set DS comprises the certificate A, the third data set DS comprises the key A associated therewith, the fourth data set comprises the certificate B, the fifth data set DS comprises the key B associated therewith, the sixth data set DS comprises the certificate C, and the seventh data set DS comprises the key C associated therewith. Here, A, B and C represent the production location or the second manufacturer A, B or C.

[0053] exist Figure 6 , the same seven data groups DS of a data group chain are shown, but these data groups are protected with different keys K1 to K4. For example, key K1 is used to protect the firmware update key. Key K2 is used to protect the second and third data groups. The fourth and fifth data groups are protected with key K3, and the sixth and seventh data groups are protected with key K4. Keys K2-K4 are respectively assigned to one of the production sites A, B, C. Each of these production sites can personalize a special data part, but not more. Through this division, personalization can be divided into different units, so that different security requirements are met.

[0054] The data sets DS are usually personalized in a defined order. In this case, the configuration commands used according to the invention make it possible to determine which data sets DS are to be personalized in the respective steps. For example, it can be determined that in the first personalization step, Figure 5 In the data set chain shown, only the first data set containing the key for the firmware update is personalized, and further personalization is then interrupted. Thus, for example, it can be determined which data are to be personalized at the production site of the device manufacturer. Further personalization can then be performed at a later point in time.

[0055] By personalizing only the key for the firmware update in a first personalization step, it is possible, for example, to first load an error correction element into the operating system, with which the other data sets DS can then be personalized in a subsequent personalization step. In principle, in this way, it is also possible to write a completely new data set chain with new data sets DS to the secure element and then personalize these data sets DS.

[0056] Figure 1A flow chart is shown in which the configuration of a distributed personalization of a not shown secure element is described with the aid of the configuration commands according to the invention. The flow chart shows how a first configuration is carried out and then a corresponding personalization is carried out.

[0057] In a first step S101, a command CSP is sent to the secure element. The command CSP is a configuration command. In step S102, a command TSP is sent to the secure element. The command TSP is a trigger signal for starting personalization as known from the prior art. In step S103, it is checked whether the configuration is set. If this is not the case (path "No"), a complete personalization as known from the prior art is carried out in step S104, whereupon the personalization ends.

[0058] If a configuration is set in step S103 (path "yes"), then in step S105 a check is made to see if there are other configurations. If this is not the case (path "no"), then personalization is finished. If in step S105 there are other configurations (path "yes"), then in step S106 a check is made to see if an implicit configuration is to be performed. Figure 3 This is explained further. If implicit configuration is to be performed (path "yes"), then in step S107, the further configuration event for personalization is continued. Subsequently, the method ends. If implicit configuration is not to be performed (path "no" of step S106), then in step S108, the first data set DS of the data set chain to be executed is personalized, and the method returns to step S105.

[0059] After the personalization is interrupted, further personalization can be continued by the configuration command CSP sent to the secure element. This kind of personalization is called explicit completion.

[0060] Figure 2 A flow chart is shown in which the continuation of the configuration by means of explicit completion is shown. In order to cause further personalization, in step S201 a command CSP, i.e. a configuration command, is sent to the secure element. While the configuration is continuing, the trigger command TSP is not resent. In step S202 it is checked whether the configuration is set or whether there is a configuration. If this is not the case (path "No"), further personalization is carried out in step S203. If the configuration is set in step S202 (path "Yes"), the further process corresponds to that in step S203. Figure 1 The process described in .

[0061] The implementation or completion of personalization can also be performed implicitly. For this purpose, special events can be configured for continuing personalization. For this purpose, for example, a restart of the security element can be defined or a predetermined number of restarts can be determined. When such an event occurs, personalization continues. In this variant, multiple implicit personalization steps can also be configured. For example, for each event, only a part of the data set DS can be personalized, and then interrupted. Then, when the next (preconfigured) event occurs, further personalization is performed.

[0062] Figure 3 A flow chart is shown in which personalization continues due to an implicitly occurring event. In step S301, it is determined whether an implicit configuration exists. If this is not the case (path "No"), the method continues with step S307, in which personalization is performed according to a process known from the prior art. Subsequently, personalization and the method end.

[0063] If in step S301 an implicit configuration is configured (path "yes"), in step S302, it is checked whether a predefined event is met. If this is not the case (path "no"), the method jumps to step S307 again. If in step S302 a preconfigured event is met (path "yes"), in step S303 it is checked whether a data set DS exists. If this is not the case (path "no"), the method continues with step S307 again. If a data set DS exists (path "yes"), the data set DS is personalized in step S304. In step S305, it is checked whether an implicit configuration exists. If this is not the case (path "no"), the method returns to step S303 and rechecks whether a data set exists. If the check in step S305 shows that an implicit configuration exists (path "yes"), the event is configured for further continuation. Subsequently, the method proceeds to step S307.

[0064] The method described enables, while the secure element is running, for example after a restart of the secure element, to check without further configuration commands whether implicit personalization is configured and is waiting for implicit personalization. If the configured event is met, personalization continues. Here, the configured data group is personalized. If other implicit configurations for other data groups were configured by previous configuration commands CSP, further implicit configurations for other data groups can be performed.

[0065] Both implicit and explicit completion of personalization enables data sets to be personalized at different points in time and at different locations, depending on urgency. Personalization that is important for production can be done immediately. Further personalization can be done at the customer's location later. This distributes the total time for personalization and enables production time to be saved.

[0066] The process described above can be repeated by sending multiple times (one or more times) of the configuration command CSP. Depending on the application and security information, the transmission of the command CSP can be performed in an unprotected or protected manner.

[0067] Thus, the interruption time can be defined with the aid of the configuration command CSP. It is defined until which data set DS is to be personalized and when the interruption is to be performed. There is the possibility of configuring additional implicit events for continuing the personalization. For example, it can be configured that after a restart, further personalization is performed with data sets #2 to #3. Then, the remaining data can be personalized by restarting again. In this way, the order in which the data sets DS of the data set chain are personalized is determined with the aid of the configuration command CSP.

[0068] like Figure 4 As shown, there is the possibility of performing a firmware update before personalization is completed. Figure 4 In step S401, a configuration command CSP is transmitted to the security element, wherein the configuration is defined as personalizing only the firmware update (Firmware-Update, FWU) key. In step S402, a trigger command TSP known from the prior art is transmitted to the security element. The firmware update key is then personalized and the personalization process is subsequently interrupted. Subsequently, the firmware update can be performed immediately (step S403). The firmware update can, for example, include error correction and / or extensions. The following loaded data groups can be personalized using feature extensions, which are not yet known at the initial development time of the security element. After the firmware update, the configuration command CSP is sent again to the security element to start the remaining personalization (step S404).

[0069] The present invention enables targeted and timely firmware updates, that is, error correction or feature expansion can be performed directly after the firmware update key is personalized. The remaining personalization can then be performed.

[0070] It is possible to distribute the personalization in different production locations. It can save production time.

[0071] Individual applications or configurations can be divided based on different security requirements. When using multiple production locations and corresponding security levels, corresponding keys can be provided for corresponding data groups (see Figure 6 The sensitive data can be personalized according to the security level or application situation.

[0072] The continuation of the started personalization can be controlled, for example, after a certain number of restarts, explicitly by further configuration commands or implicitly by previous configuration of certain events.

Claims

1. A method for computer-aided personalization of a security element, on which an image is loaded, in which an operating system of the security element is integrated, in which method: One or more data sets (DS) provided individually for the security element are written into a special storage area of ​​the security element, the data sets containing card-specific data, with which the security element is personalized under the control of the operating system, wherein: During the personalization of the secure element, a configuration command (CSP) is used to define the sequence in which the data sets (DS) are personalized.

2. The method according to claim 1, characterized in that: The configuration command (CSP) specifies which data of one or more of the data sets (DS) are to be personalized in a first step.

3. The method according to claim 1 or 2, characterized in that: One or more interruption points are set by the configuration command (CSP) which personalize the data set (DS).

4. The method according to any one of the preceding claims, characterized in that The continuation of the personalization at a later point in time is configured using the configuration command (CSP).

5. The method according to claim 4, characterized in that Predefined events are configured via the configuration commands (CSP), upon the occurrence of which the personalization is continued.

6. The method according to claim 5, characterized in that The event is a restart of the secure element or the reaching of a predefined number of restarts of the secure element.

7. The method according to any one of the preceding claims, characterized in that The configuration command (CSP) is sent to the secure element at least once more, whereby personalization is continued at a later point in time.

8. The method according to any one of the preceding claims, characterized in that The configuration command (CSP) is transmitted to the secure element in an encrypted or unencrypted manner.

9. The method according to any one of the preceding claims, characterized in that In the first step, a firmware update key is personalized in one of the data sets (DS).

10. The method according to claim 9, characterized in that In a second step a firmware update is performed.

11. A system for computer-aided personalization of a security element, on which an image is loaded, in which an operating system of the security element is integrated, wherein: The system is designed so that, when the system is in operation, writing one or more data sets (DS) provided individually for the secure element into a special storage area of ​​the secure element, the data sets containing card-specific data, with which the secure element is personalized under the control of the operating system, and During the personalization of the secure element, a configuration command (CSP) is used to define the order in which the data sets (DS) to be written are personalized.

12. The system according to claim 11, characterized in that The system is configured to perform the method according to any one of claims 1 to 10.