Method and control unit for transmitting esim profile data

Abstract

The invention relates to a method for transferring eSIM profile data (30) from a first eUICC device (110) to a target entity, comprising the following steps: a. Providing encrypted eSIM profile data (30) on the first eUICC device (110), the encrypted eSIM profile data (30) having been encrypted by means of a profile encryption key (20); b. Transferring the encrypted eSIM profile data (30) from the first eUICC device (110) to the target entity; c. Deleting the encrypted eSIM profile data (30) from the first eUICC device (110); d. Transmitting the profile data encryption key (20) from the first eUICC device (110) to the target entity only after completing steps b. And c.; and e. Decrypting the encrypted eSIM profile data (30) by means of the profile encryption key (20) and installing the decrypted eSIM profile data (30) on the target entity.

Description

Technical Field

[0001] The present disclosure relates to a method of transmitting eSIM profile data. Furthermore, the present disclosure relates to a control unit for performing the proposed method. Background Art

[0002] The current security protocol defined by the GSMA for downloading and installing eSIM profiles is defined on a "one-way street" principle. This means that once a profile is delivered (which is encrypted only for a single eUICC (embedded universal integrated circuit card, such as the SIM card of an electronic mobile communication device)), the eUICC is required to never expose any data from that profile, unless required and defined by the relevant telecommunication specifications (ETSI, 3GPP, etc.). The disadvantage that this brings is that the scenario of removing a plastic SIM from one device and putting it in another, keeping by any means all modifications made to the SIM so far, is not possible today in the eSIM ecosystem. With those secret credentials, cloned profiles can be created, and secret network and authentication keys can be reused, shared or exposed in an undesirable way.

[0003] Conventional eUICCs do not have the resources to fully store an encrypted Profile before decryption and processing. Therefore, Profile data is sent to the eUICC in fragments in a "streaming" mode and decrypted / processed by the eUICC. Additionally, exports will be "export streaming" where the eUICC assembles, encrypts and sends the exported Profile in fragments.

[0004] WO 2012 / 076480 A1 discloses a method for exporting secure server data included on a UICC included in a terminal. Summary of the invention

[0005] It is an object of the present invention to provide an improved method for eSIM profile data transfer.

[0006] According to a first aspect, the present disclosure proposes a method for transmitting eSIM profile data from a first eUICC device to a target entity, comprising the following steps:

[0007] a. providing encrypted eSIM profile data on the first eUICC device, the encrypted eSIM profile data having been encrypted using a profile encryption key;

[0009] b. transmitting the encrypted eSIM profile data from the first eUICC device

[0010] Sending to the target entity;

[0011] c. Deleting the encrypted eSIM profile data from the first eUICC device;

[0013] d. Only after completing steps b. and c., the profile data encryption key is transferred from

[0014] the first eUICC device being transmitted to the target entity; and

[0015] e. Decrypting the encrypted eSIM profile data by means of the profile encryption key and installing the decrypted eSIM profile data on the target entity.

[0016] In this way, cloning of eSIM profile data is largely impossible, since the eSIM profile data only exists once on a single entity at a particular time. In other words, at the moment the eSIM profile data has been deleted from the exporting entity, the normal eSIM profile data is available at the receiving party. In this way, the transfer of eSIM data from any exporting entity to any receiving entity can be achieved in a secure manner, without the possibility of having the eSIM data installed twice in two different entities. At this point, when the profile data is available for use on the receiving entity, the properties have been lost in the exporting entity and therefore exist once.

[0017] According to another aspect, the present disclosure proposes a control unit for performing the proposed method.

[0018] According to another aspect, the present disclosure proposes a system comprising at least two proposed control units.

[0019] In one or more embodiments, in step a., a profile encryption key is generated together with the eSIM profile data.

[0020] In one or more embodiments, the profile encryption key is encrypted on the first eUICC device by means of at least one key, wherein the encrypted encryption key is suitable for a single target entity. In this way, the encryption key is generated in a secure and reliable manner according to a proven method.

[0021] In one or more embodiments, in step a., the profile encryption key is encrypted by a key creation material that has been agreed upon in the handshake process between the first eUICC device and the target entity. In this way, exporting the eUICC device requires re-encoding only a small number of bytes of the eSIM profile data, which improves efficiency. The re-encoding process is typically performed on a specific hardware component (Hardware Security Module, HSM), for example, formed as a plug-in card on a server.

[0022] In one or more embodiments, the profile encryption key is decrypted with the aid of the key creation material.

[0023] In one or more embodiments, the key creation material and the configuration file encryption key are generated ephemeral. In this way, the key creation material can be used only once for the target entity, which represents a proven technique.

[0024] In one or more embodiments, the first eUICC device is arranged on a card, and the target entity is a second eUICC device.

[0025] In one or more embodiments, the first eUICC device is arranged on a card and the target entity is arranged on a server. In this way, advantageously, the eSIM profile data may be returned for the purpose of reallocation elsewhere.

[0026] In one or more embodiments, at least a single eSIM profile is transferred from the first eUICC device to the target entity. Of course, more than one eSIM profile may also be transferred with the aid of the proposed method. Also, other kinds of data may be transferred from the exporting entity to the receiving entity with the aid of the confirmed method. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above discussion / summary of the invention is not intended to describe every embodiment or every implementation of the present disclosure. The following figures and detailed description also illustrate various embodiments. The aspects as defined above and further aspects of the present disclosure are apparent from the examples of embodiments to be described below with reference to the accompanying drawings, which are explained with reference to the examples of embodiments. However, it is needless to say that the present disclosure is not limited to the examples of embodiments.

[0028] All illustrations in the drawings are schematic. It should be noted that in different figures, similar or identical elements or features have the same reference numerals or have reference numerals that differ from the corresponding reference numerals only within the first digit. In order to avoid unnecessary repetitions, elements or features that have already been explained with respect to previously described embodiments will not be explained again at a later point in the description.

[0029] Various example embodiments may be more fully understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

[0030] Figure 1 A system for generation, provisioning and transmission of eSIM profile data is shown;

[0031] Figures 2 to 4 is a diagram showing conventional transfer of eSIM profile data;

[0032] Figure 5 is a diagram showing an example of the results of the proposed method; and

[0033] Figure 6 is a flow chart illustrating the proposed method.

[0034] Although the various embodiments discussed herein allow for modifications and alternative forms, aspects of these embodiments have been illustrated by way of example in the accompanying drawings and will be described in detail. However, it should be understood that it is not intended to limit the present disclosure to the specific embodiments described. On the contrary, it is intended to cover all modifications, equivalents, and alternatives of the various aspects defined in the claims that fall within the scope of the present disclosure. In addition, the term "example" used throughout this application is only for illustration and not limitation. DETAILED DESCRIPTION

[0035] In order to avoid creating clones of eSIM profile data, modifications that change existing GSMA security protocols and data formats are proposed. The basic idea of ​​the present disclosure is that the keys used to encrypt the exported eSIM profile data can be retrieved from the target entity (e.g., the target eUICC device) only after the eSIM profile data has been completely exported and furthermore completely deleted from the exporting eUICC device. This can be provided, for example, by means of an "atomic" operation, which is an operation in which the key storage and deletion of the exported profile are written to the memory of the eUICC device in an atomic manner, so that both actions are either performed in the memory and persisted, or neither is performed in the memory and is not persisted.

[0036] This then automatically results in the fact that, in case the exported Profile is indeed deleted from the exporting eUICC device, the encrypted Profile can only be decrypted by the receiving entity and cloning is therefore not possible.

[0037] Figure 1 The structure of a system for generation, provisioning and transmission of eSIM profile data is shown, wherein components of the shown system can be used to perform the proposed method.

[0038] Conventionally, the loading of profile data is a one-way path process. Once downloaded from the server 200 to the receiving eUICC device, the eSIM profile data does not come out of the receiving eUICC device again. Of course, the eSIM profile data can be deleted, however, the eSIM profile data is then lost. A corresponding notification goes to the server 200, informing the server 200 that the eSIM profile has been successfully deleted. The server 200 can then transfer the eSIM profile data to another user. However, this is the initial profile that has been uploaded to the server 200 a long time ago. The latest eUICC devices also allow more than one profile to be activated at the same time ("dual SIM" feature).

[0039] One recognizes the GSMA RSP architecture in a simplified manner. An eUICC device 110, 210 assigned a unique ID and trust (keys, certificates, etc.) by an eUICC device manufacturer (EUM) 500 only allows loading of a security profile on site. The eUICC device manufacturer 500 may represent an electronic chip manufacturer. A device having an eUICC device 110, 210 needs to be connected to a profile provider server 200 (SM-DP+, Subscription Manager Data Preparation System) arranged in the cloud or in a data center, for example, via WiFi or a companion device (a smart watch connected to a smartphone). After the contract with the end user 400 has been concluded, the mobile network operator (MNO) 300 prepares eSIM profile data (not shown) for a specific eUICC device 110, 210. The first eUICC device 110 represents an export entity arranged on a card, and the eSIM profile data is securely transmitted to, for example, a server 200 via a first device application (LPA) 120, which is software using a temporary key (ECC-based). Alternatively, it is also possible to Figure 1 As shown in , exporting the first eUICC device can securely export the eSIM profile data to a target entity formed as a second eUICC device 210 , which is arranged on the second control unit 600 with the second device application 220 .

[0040] The first (exporting) eUICC device 110 may contain more than one eSIM profile. The data preparation system can be used by all operators that store eSIM profiles, as this system downloads the data securely into the eUICC device.

[0041] The present disclosure proposes a method and a control unit, which enable the transfer of eSIM profile data between different entities, for example, between two devices, which are coupled via Bluetooth and can transfer eSIM profile data from a first coupling device to a second coupling device by means of the proposed method.

[0042] Figure 2In principle, in a conventional process, the eSIM profile data 30 is "forward encrypted" in a manner that relies on, for example, ECC-based Diffi-Hellman key derivation. First, a temporary key pair (ECC) creation is performed on the server (not shown) and the target eUICC (not shown). Subsequently, an exchange of key creation material 10 (e.g., public keys) is performed between the server and the target eUICC. The creation of symmetric key material based on Diffie-Hellman creates a key derivation with a shared secret on the server and the eUICC. Then, the entire "Bound Profile Package" (BPP) with the eSIM profile data 30 with segments S1 ... S7 is sent to the target eUICC device, where the key creation material 10 is sent together with the profile encryption key 20, but encrypted with the key material 10 created in the previous steps described. Due to technical limitations of the underlying transport protocol on the eUICC device and the limited resources of the eUICC device, the binding profile package with the eSIM profile data 30 is sent to the eUICC device in fragments S1...S7 and is decrypted and processed / installed in fragments S1...Sn rather than as a single large data block.

[0043] Figure 3 The receiving eUICC device is shown in principle receiving packets in the abstract format and order shown (from left to right as a data flow).

[0044] In this way, so-called "forward-only encryption" is performed, which is designed for partial decryption and partial processing in streaming mode. Once the target eUICC device starts receiving the profile package (in streaming mode), the target eUICC device can directly decrypt the data and can access the secret data (e.g., keys, etc.) of the eSIM profile data 30. In this way, it is not foreseen that the profile is exported from the eUICC device to the server and / or from the peer device to other eUICC devices.

[0045] Figure 4 In principle, the decryption on the target eUICC device is shown similar to the reference Figure 2 20. As indicated, the receiving eUICC device may start decrypting the already partially retrieved data immediately after receiving the profile encryption key 20. However, at this point, it will not be ensured that the exporting eUICC device has completely exported or deleted the eSIM profile. At time T, the receiving entity may start decrypting the (partially) received data. In this way, an attacker is able to generate one or several clones of the transmitted eSIM profile.

[0046] Figure 5The proposed concept is illustrated in principle, where profile encryption keys 20 are generated by the exporting first eUICC device 110 before starting profile encryption, but the profile encryption keys 20 are sent separately only after the eSIM profile data transfer is completed and the eSIM profile data on the exporting entity is deleted, making them available to the receiving entity (e.g., target eUICC device, server, etc.). This results in Figure 5 The data export structure shown in .

[0047] One identifies a timeline with time t, where at time T1, the exporting first eUICC device 110 creates profile encryption keys 20, but stores these profile encryption keys securely internally. At time T2, the exporting first eUICC device 110 deletes the eSIM profile data 30 and makes the profile encryption keys 20 available so that the target entity can decrypt the transmitted encrypted eSIM profile data 30 and can install the decrypted eSIM profile data on the target entity.

[0048] In this way, due to the fact that the derived data structure contains only non-sensitive or encrypted data blocks, any intermediate instance on the way to the receiving eUICC device (e.g., having much more technical resources than the eUICC device), the eSIM device application "LPA" recently defined by the GSMA eSIM specification, can rearrange the structure so that for the receiving eUICC device, the same is given according to Figure 3 Standard GSMA security protocol data structure.

[0049] It should be noted that the method shown has been described exemplarily with reference to the exporting eUICC device 110 arranged on the card and with reference to the target entity arranged on the server. However, other configurations are also possible. For example, the exporting first eUICC device 110 may be arranged on the control unit 100, and the second eUICC device may also be arranged on another control unit 600 (transfer from card to card, peer-to-peer transfer). In this way, the transfer of eSIM profile data between several entities can be performed in a very comfortable and secure manner.

[0050] Anti-cloning is therefore supported in the following way: relevant key material for decryption is not sent or made available in any way until the entire profile data packet is received and the sender ensures countermeasures against cloning.

[0051] Figure 6 The flow of an embodiment of the proposed method is shown.

[0052] In step 700 , encrypted eSIM profile data 30 is provided on the first eUICC device 110 , the encrypted eSIM profile data 30 having been encrypted by means of a profile encryption key 20 .

[0053] In step 710 , the encrypted eSIM profile data 30 is transmitted from the first eUICC device 110 to a target entity.

[0054] In step 720 , the encrypted eSIM profile data 30 is deleted from the first eUICC device 110 .

[0055] In step 730 , the profile data encryption key 20 is transferred from the first eUICC device 110 to the target entity only after steps b. and c. are completed.

[0056] In step 740 , the encrypted eSIM profile data 30 is decrypted by means of the profile encryption key 20 and the decrypted eSIM profile data 30 is installed on the target entity.

[0057] The proposed control unit 100 is configured to perform the proposed method.The proposed system comprises at least two proposed control units 100, 600 configured to perform the proposed method.The proposed control unit 100 is at least partially implemented as hardware.

[0058] Aspects of the present disclosure are considered applicable to various different types of devices, systems and methods involving radar systems and related communications. In certain embodiments, aspects of the present disclosure have proven to be beneficial when used in the context of automotive radars in environments susceptible to the presence of multiple objects in relatively small areas. Aspects may be understood through the following discussion using non-limiting examples of exemplary scenarios, but are not necessarily limited thereto.

[0059] Advantageously, in addition to the transfer of different data such as applications, emails, etc., eSIM profile data may also be transferred between different entities.

[0060] In the foregoing description, various specific details have been set forth to describe the specific examples presented herein. However, it should be apparent to those skilled in the art that one or more other examples and / or variations of these examples may be practiced without all the specific details given below. In other cases, well-known features are not described in detail to avoid confusion in the description of the examples herein. For ease of illustration, the same reference numerals may be used in different diagrams to refer to the same elements or additional examples of the same elements. Moreover, although various aspects and features may be described in individual figures in some cases, it should be understood that features from one figure or embodiment may be combined with features of another figure or embodiment, even if the combination is not explicitly shown or explicitly described as a combination.

[0061] As an example, the present specification describes and / or illustrates aspects useful for implementing the claimed disclosure with the aid of various circuits or circuit systems, which may be illustrated as or using terms such as blocks, modules, devices, systems, units, controllers, and / or other circuit-type depictions. Such circuits or circuit systems are used with other elements to illustrate how certain embodiments may be implemented in form or structure, steps, functions, operations, activities, etc. For example, where such circuits or circuit systems may correspond to logic circuit systems (which may refer to or include a code-programmed / configured CPU), in one example, the logic circuit system may implement a process or method (sometimes an "algorithm") by performing such activities and / or steps associated with the above-described functions. In other examples, the logic circuit system may implement a process or method by performing these same activities / operations.

[0062] For example, in certain embodiments discussed above, one or more modules are discrete logic circuits or programmable logic circuits configured and arranged to implement these operations / activities. In certain embodiments, such programmable circuits are one or more computer circuits, including a memory circuit system for storing and accessing a program to be executed as a set of (or more) instructions (and / or used as configuration data to define how the programmable circuit executes), and the programmable circuit uses an algorithm or process as described above to perform the relevant steps, functions, operations, activities, etc. Depending on the application, the instructions (and / or configuration data) may be configured to be implemented in a logic circuit system, where the instructions (whether represented in the form of object code, firmware or software) are stored in the memory (circuitry) and can be accessed from the memory. As another example, where the specification may refer to a "first" type of structure, a "second" type of structure, the adjectives "first" and "second" are not used to imply any description of the structure or provide any substantial meaning; in fact, such adjectives are only used in English antecedents to distinguish one such similarly named structure from another similarly named structure.

[0063] Based on the above discussion and illustration, those skilled in the art will readily appreciate that various modifications and changes may be made to the various embodiments without strictly following the exemplary embodiments and applications shown and described herein. For example, the method illustrated in the figure may involve steps performed in various orders, wherein one or more aspects of the embodiments herein are retained, or may involve fewer or more steps.

[0064] It should be noted that the term "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude a plurality. Elements described in connection with different embodiments may also be combined. It should also be noted that the reference signs in the claims should not be interpreted as limiting the scope of the claims.

[0065] The disclosed devices, apparatuses, units, elements, systems, and methods described herein may be embodied, at least in part, by a computer program or multiple computer programs, which may exist in a single computer system or across multiple computer systems in multiple forms in both active and inactive states. For example, the computer program may exist as a software program consisting of program instructions in source code, object code, executable code, or other formats for performing some steps. Any of the above formats may be embodied in compressed or uncompressed form on a computer-readable medium, which may include storage devices and signals.

[0066] It should be noted that the above embodiments have been described with reference to different subject matters. In particular, some embodiments may have been described with reference to method-type claims, whereas other embodiments may have been described with reference to apparatus-type claims.

[0067] However, those skilled in the art will understand from the above that, unless otherwise stated, in addition to any combination of features belonging to one type of subject matter, any combination of features related to different subject matters, in particular, the combination of features of method type claims with features of apparatus type claims, are also deemed to be disclosed together with this document.

[0068] It has to be noted that the embodiments have been described with reference to different subject matters. In particular, some embodiments have been described with reference to method type claims, whereas other embodiments have been described with reference to apparatus type claims.

[0069] However, those skilled in the art will conclude from the above and the following description that, unless otherwise notified, in addition to any combination of features belonging to one type of subject matter, any combination of features related to different subject matters, in particular, combinations of features of method-type claims and features of device-type claims, are also deemed to be disclosed together with the present application.

[0070] Reference numerals:

[0071] 10 Key Creation Materials

[0072] 20 Configuration file encryption key

[0073] 30eSIM profile data

[0074] 100 First Control Unit

[0075] 110 first eUICC device

[0076] 120 First Device Application

[0077] 200 Server

[0078] 210 Second eUICC device

[0079] 220 Second Device Application

[0080] 300 Mobile Network Operators

[0081] 400 end users

[0082] 500 Server

[0083] 600 Second control unit

[0084] 700……740 Methods and Steps

[0085] S1...Sn segment

[0086] t time.

Claims

1. A method for transmitting eSIM profile data (30) from a first eUICC device (110) to a target entity, characterized in that The following steps are involved: a. providing encrypted eSIM profile data (30) on the first eUICC device (110), the encrypted eSIM profile data (30) having been encrypted by means of a profile encryption key (20); b. transmitting the encrypted eSIM profile data (30) from the first eUICC device (110) to the target entity; c. deleting the encrypted eSIM profile data (30) from the first eUICC device (110); d. transmitting the profile data encryption key (20) from the first eUICC device (110) to the target entity only after completing steps b. and c.; and e. Decrypting the encrypted eSIM profile data (30) by means of the profile encryption key (20) and installing the decrypted eSIM profile data (30) on the target entity.

2. The method according to claim 1, characterized in that In step a., the profile encryption key (20) is generated together with the eSIM profile data (30).

3. The method according to claim 1 or 2, characterized in that: The profile encryption key (20) is encrypted on the first eUICC device (110) by means of at least one key, wherein the encrypted encryption key (20) is suitable for a single target entity.

4. A method according to any of the preceding claims, characterised in that In step a., the profile encryption key (20) is encrypted by key creation material (10) which has been agreed upon in a handshake process between the first eUICC device (210) and the target entity.

5. The method according to claim 4, characterized in that The profile encryption key (20) is decrypted with the aid of the key creation material (10).

6. The method according to claim 4 or 5, characterized in that: The key creation material (10) and the configuration file encryption key (20) are generated transiently.

7. A method according to any of the preceding claims, characterised in that The first eUICC device (110) is arranged on a card, and the target entity is a second eUICC device (210).

8. The method according to any one of claims 1 to 6, characterized in that The first eUICC device (110) is arranged on a card, and the target entity is arranged on a server (200).

9. A control unit (100), characterized in that: The control unit (100) is configured to perform the method according to any one of claims 1 to 8.

10. A system, characterized in that: Comprising at least two control units (100, 600) according to claim 9.

Images