Profile generation for provisioning profiles to eUICC

Abstract

To provide a method of profile generation for provisioning a profile to an eUICC.SOLUTION: A method for generating at least one profile for provisioning the profile to an eUICC designed to be hosted in a device includes the steps of: S1) providing profile generation data for generating a profile container; S2) generating a profile and a dynamic-data description file indicating the content and storage location of dynamic profile data in the profile; S3-1) creating the profile container in the eUICC; and S3-2) transferring the extracted dynamic profile data to the eUICC, and installing the transferred extracted dynamic profile data in the profile container created in the step S3-1).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] FIELD OF THE INVENTION The present invention relates to the generation of profiles intended to be provisioned to a wireless network communication device, or briefly an eUICC designed to be hosted on the device. [Background technology]

[0002] Background of the Invention and Prior Art The world is connected via wireless communication networks, also called mobile communication networks, and devices hosting eUICC communications communicate with each other and with wireless network background servers in a secure manner. The eUICCs hosted on the devices contain at least one or more subscription profiles, or profiles for short, comprising profile data such as an International Mobile Subscriber Identity IMSI and an authentication key Ki as well as a profile number ICCID, an OTA key and further profile data that enable communication within the wireless communication network.

[0003] In the case of the eUICC, several form factors are known, including a plug-in SIM card that is strictly embedded and soldered within the eUICC, and an integrated iUICC that is integrated within a chip in the chipset of the device that hosts the eUICC.

[0004] The devices are known as M2M wireless network communication devices, including for example consumer wireless network communication devices such as smartphones and network-enabled tablet PCs, as well as automotive wireless network communication devices and industrial wireless network communication devices. In the following, a device is meant to be a wireless network communication device that hosts an eUICC containing one or more profiles and is configured to communicate with other devices or network servers over a mobile communication network, including the eUICC, for security-related tasks such as authentication.

[0005] Documents [1][SGP.22] GSMA SGP.22 RSP Technical Specification Version 2.2.2, 05 June 2020 and [2][SGP.02] SGP.02 - Remote Provisioning Architecture for Embedded UICC Technical Specification, Version 4.2, 07 July 2020 describe procedures and architecture for provisioning profiles to device-hosted eUICCs. Document [3][SGP.31] GSMA SGP.31 eSIM IoT Architecture and Requirements Version 1.0, 19 April 2022 describes procedures and architecture for provisioning profiles to device-hosted eUICCs in IoT environments.

[0006] Provisioning a profile to an eUICC involves authentication between a profile server and the eUICC, profile download, and profile installation. Chapter 3.1.2 of [1] [SGP.22] describes common mutual authentication, and chapter 3.1.3 describes profile download and installation on the eUICC of a consumer device. [2] [3] describe similar procedures for M2M and IoT environments. The profile download architecture includes a profile provisioning server (SM-DP+) in [1] [SGP.22] or [3] or an SM-DP in [2] [SGP.02], a profile assistant (which can be in the device or the eUICC, or both, and can be a local profile assistant LPA in [1] [2] or an IoT profile assistant IPA in [3]), and the eUICC. Profiles are downloaded from the profile provisioning server on the profile assistant (LPA or IPA) to the eUICC.

[0007] According to [1][SGP.22] and [2][SGP.02], profiles are downloaded from a profile provisioning server within a bound profile package (BPP), which typically contains a considerable amount of data.

[0008] The profile installation sub-procedure includes several sub-steps. [1] [SGP.22], chapter 3.1.3.3 "Sub-procedure Profile Installation", step [3] (Fig. 14 and subsequent description) first establishes and configures the profile container ISD-P, then steps [4], [5] and [6] (further Fig. 14 and subsequent description) install the metadata, the replaced session key and the profile data elements into the profile container ISD-P. The profile container ISD-P is created from static profile data. The profile data elements installed in the profile container ISD-P are part of or contain dynamic profile data.

[0009] The mutual authentication, profile download from the provisioning server to the eUICC and profile installation within the eUICC require a significant amount of time, typically more than 10 seconds.

[0010] Profile generation is outside the scope of documents [1][SGP.22] and [2][SGP.02]. For profile generation, profile data, including static and dynamic profile data, are provided to the profile provider's data generation platform as a proprietary profile, which is the configuration of the profile data in the profile provider's proprietary data format. For profile download from the profile provisioning server to the eUICC, the profile must be provided in a non-proprietary, standardized, interoperable format as described in document [5][PP IF] SIM Alliance eUICC Profile Package: Interoperable Format Technical Specification, Version 2.3, October 2019, which, following the name change from SIM Alliance to Trusted Connectivity Alliance, is also referred to as the Trusted Connectivity Alliance compliant format, or TCA compliant format. Therefore, in the data generation platform, the proprietary profile is converted into a TCA compliant profile, which is then provided from the data generation platform to a profile provisioning platform, such as SM-DP+ or SM-DP, for download to the eUICC.

[0011] In-factory personalization or provisioning is a setup where profiles are provisioned locally to the eUICC in a factory environment, as opposed to the standard remote provisioning procedures envisaged in [1][SGP.22], [2][SGP.02] and [3][SGP.31], where profiles are downloaded to the eUICC from a remote profile provisioning server.

[0012] In in-factory provisioning, profiles are downloaded to the eUICC not from a remote profile provisioning server such as SM-DP+, but instead from a local personalization device that resides in a protected production environment. The protected production environment may be that of the eUICC manufacturer that manufactures the eUICC, or the semiconductor chip manufacturer that manufactured the semiconductor chip hosted on the eUICC, or the device manufacturer that manufactured the device. Furthermore, in in-factory provisioning, the eUICC is not necessarily already attached to the device, but may be attached to an eUICC reader that is coupled to or integrated into the personalization device. In this case, the eUICC is provisioned from the personalization device via the eUICC reader. Thus, the personalization device may be part of, for example, the production machine for manufacturing the eUICC.

[0013] Profile generation in a factory provisioning setup can be performed by the eUICC manufacturer instead of the profile provider or alternatively by the profile provider as in a standard provisioning setup.

[0014] Document [4] from the prior art, German Patent No. 102019001840B3, discloses a method for profile provisioning for an eUICC, wherein a profile downloaded to the eUICC contains empty locations into which profile data from another profile already present in the eUICC is inserted after download and upon profile installation on the eUICC.

[0015] Document [5] from the prior art, EP 2802162 A1, discloses a method for provisioning a profile to an eUICC, where an empty profile template is created by running an executable file and profile data is loaded into the profile template.

[0016] Device manufacturers, including M2M device manufacturers and smartphone manufacturers who provision or have provisioned their devices, particularly when provisioning in the factory, require a shorter processing time for profile provisioning to the eUICC of less than 10 seconds per profile provisioning.

[0017] [1][SGP.22] full cycle of authentication, profile download and profile installation does not allow such a small processing time for profile provisioning.

[0018] Profiles that are provided outside the eUICC on a platform or server are often referred to as virtual profiles, while profiles that are installed on the eUICC are simply referred to as profiles. Summary of the Invention [Problem to be solved by the invention]

[0019] Object of the invention It is an object of the present invention to provide a method for provisioning a profile to an eUICC that has reduced processing time for profile provisioning.

[0020] In particular, a provisioning solution is provided that is suitable for making in-factory provisioning more efficient and less error prone. [Means for solving the problem]

[0021] Summary of the Invention The object of the invention is achieved by a method according to claim 1 having the following characteristics: Embodiments of the invention are presented in the dependent claims.

[0022] The basic idea underlying the present invention is to split the preparatory steps of profile provisioning and execute the split steps separately so as to reduce the processing time required during the actual profile provisioning.

[0023] In particular, the creation of a profile container, for example an ISD-P, within the eUICC can be performed in a time-available manner.

[0024] Then, during profile provisioning, all that is required is to provision the profile data into the existing profile container.

[0025] Correspondingly, the processing time for profile provisioning is reduced.

[0026] The method is particularly useful and applicable in the case of in-factory personalization.

[0027] More particularly, the present invention provides a method for generating at least one profile for provisioning the profile to an eUICC designed to be device-hosted.

[0028] The method is: S1) providing profile generation data, including static profile data and dynamic profile data, from a wireless network operator (MNO) or a virtual wireless network operator (MVNO) to a data generation platform for generating a profile container; S2) generating a profile and a dynamic data description file indicating the content and storage location of at least the dynamic profile data in the profile from profile generation data including static profile data and dynamic profile data for generating a profile container; S3-1) creating at least one profile container on the eUICC; S3-2) providing the profile and the dynamic data description file to an IFPP dynamic converter and extracting the dynamic profile data from the profile with the aid of the dynamic data description file in the IFPP dynamic converter, then transferring the extracted dynamic profile data to the eUICC and installing the transferred extracted dynamic profile data in the profile container created in step S3-1). Includes.

[0029] Dynamic profile data for later storage in the prepared profile container is obtained from the already generated profile, rather than from a data storage that stores dynamic profile data for multiple profiles, thereby utilizing a dynamic data description file, which facilitates obtaining dynamic profile data for only one profile and keeping the dynamic profile data of a profile aligned with a profile container created from static profile data of the same profile.

[0030] More specifically, the profile data provided for profile generation on a data generation platform hosted by a hosting party, which may be, for example, an eUICC manufacturer or a profile manufacturer, is typically provided on said data generation platform in a proprietary format established by the hosting party. The proprietary format established by the hosting party on the data generation platform may refer to the individual formatting characteristics of the hosting party itself and / or other parties, such as, for example, the MNO or MVNO that is the owner of the profile to be generated. Therefore, the dynamic profile data may be structured in very different ways on different data generation platforms. Therefore, retrieval of the dynamic profile data from the data generation platform requires detailed knowledge of the format and structure, including, for example, the storage location of the dynamic profile data within the data generation platform.

[0031] Conversely, retrieving dynamic profile data from an already generated profile reduces the effort of retrieving dynamic profile data to a search for one single profile, regardless of whether the dynamic profile data is retrieved from an already generated profile in a proprietary format or a TCA-compliant format.

[0032] Additionally, when dynamic profile data is retrieved from a profile in a TCA-compliant format, the dynamic profile data is provided within the already-generated profile in a well-defined, standardized location within the profile. Thus, retrieving dynamic profile data from an already-generated profile in a TCA-compliant format has the additional advantage that the complexity of the search and retrieval process for standalone dynamic profile data is further reduced.

[0033] The step S3-1) of creating a profile container and the step S3-2) of providing the profile and dynamic data description file to the IFPP dynamic converter can be performed in a time-separated or similar time and in any order of the two steps relative to each other, i.e. as a first step S3-1) or as a first step S3-2), depending on the requirements of the particular use case.

[0034] In some embodiments, two or more profiles, corresponding dynamic data description files and corresponding extracted dynamic profile data are created.

[0035] According to the embodiments described herein, batches of dynamic profile data for several profiles may be provided in an ordered manner.

[0036] According to some embodiments, the method comprises: S4) Transferring the extracted dynamic profile data extracted in step S3-2) to the eUICC, and installing the transferred extracted dynamic profile data in the profile container created in step S3-1). and provisioning the generated profile to the eUICC by performing

[0037] The steps described here complete the profile provisioning enabled by the above method for generating a profile, with the aim of subsequently provisioning the profile to an eUICC.

[0038] According to some embodiments, step S4) comprises: S4-1) providing the extracted dynamic profile data extracted in step S3-2) to an IFPP controller installed in the eUICC production environment; S4-2) eUICC read / write equipment connected to or integrated into the eUICC production machine installed in the eUICC production environment To, The created profile container have eUICC of Sub-steps of providing, S4-3) a sub-step of providing the extracted dynamic profile data to an eUICC production machine by an IFPP controller; S4-4) A sub-step of downloading the extracted dynamic profile data to the eUICC by the eUICC production machine and installing the transferred extracted dynamic profile data in the profile container created in step S3-1) to create a profile and thereby provisioning the profile to the eUICC. This is performed as a sequence of:

[0039] In the embodiment described herein, while the eUICC occupies the eUICC production machine, only the extracted dynamic profile data needs to be provisioned into the existing profile container. This significantly reduces the time span during which the eUICC occupies the eUICC production machine for profile provisioning compared to the conventional provisioning of the entire profile in one single step. Therefore, this solution is preferable, especially in the eUICC production environment of an IFPP, where machine occupancy time is highly valued. In addition, the smaller amount of data transferred from the eUICC production machine to the eUICC can help reduce the risk of data transfer errors. Therefore, this provisioning solution is suitable for making in-factory provisioning more efficient and less prone to errors.

[0040] According to some embodiments, in step S3-1), two or more profile containers are created from static profile data of different profiles, and step S4-3) further includes selecting the correct profile container that corresponds to the dynamic profile data provided in step S4-1).

[0041] According to the embodiments described herein, batches of dynamic profile data for several profiles may be provided in an ordered manner.

[0042] According to some embodiments, in steps S4-1 and S4-3), a profile identifier is provided along with the provided dynamic profile data, and the profile identifier is also provided along with the correct existing created profile container, and the correct profile container is selected based on the provided profile identifier.

[0043] According to some embodiments, the profile identifier is: - profile container identifier ISD-P AID, - Profile number ICCID, or - Profile name, or - a combination of one, some or all of the following: profile container identifier ISD-P AID, profile number ICCID and profile name is or contains

[0044] According to some embodiments, the dynamic profile data is: - International Mobile Subscriber Identity IMSI, - authentication key Ki, - further authentication parameters, - profile number ICCID, - access control state ACC, - one or several personal identification numbers PIN, - one or several Personal Unblocking Keys (PUK) - Default Issuer Security Domain Profile Default-ISD-P, - other dynamic parameters for MNO or MVNO, including roaming partners Contains one, some, or all of the following:

[0045] According to some embodiments, the generation according to step S2) is carried out on a data generation platform, which may be hosted by the eUICC manufacturer or the profile provider, S2-1) From profile generation data including static profile data and dynamic profile data for generating a profile container, - A profile provider can provide its own profile in its own data format, and - Dynamic Data Description File generating S2-2) Converting a proprietary profile into a TCA-compliant profile Includes.

[0046] For provisioning to an eUICC, the profiles are preferably provided in an interoperable TCA, Trusted Connectivity Alliance compliant format, however profile providers often use proprietary profile formats on their data generation platforms, so that conversion to a TCA compliant format is preferred or required.

[0047] According to some embodiments, the extraction of dynamic data according to step S3-2) is performed from a unique profile.

[0048] According to some embodiments, the extraction of dynamic data according to step S3-2) is performed from a TCA-compliant profile with the further advantages described above.

[0049] According to some embodiments, an IFPP dynamic converter for extracting dynamic data is provided in the data generation platform.

[0050] According to some embodiments, the IFPP dynamic converter that extracts the dynamic data may, for example, After generation TCA compliant profile and dynamic data description file proposed offered RuS It is provided in a profile provisioning platform such as M-DP+ or SM-DP.

[0051] According to some embodiments, the IFPP dynamic converter extracts dynamic data from a profile with the aid of a dynamic data description file in response to a profile provisioning platform (e.g., SM-DP+ or SM-DP) receiving a request to download a profile to said eUICC on which a profile container corresponding to the profile is already installed, where the profile container can be installed on the eUICC first and then, possibly much later, the dynamic profile data is extracted from the profile.

[0052] According to some embodiments, the request to download the profile is received from an eUICC production machine, in particular an eUICC production machine in a factory provisioning environment.

[0053] BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present invention will now be described with reference to the accompanying drawings, which represent the following figures, in which like parts are referred to by like numerals throughout: [Brief explanation of the drawings]

[0054] [Figure 1] 1 is a profile provisioning setup including an IFPP dynamic converter according to an embodiment of the present invention. [Figure 2] 2 is a profile provisioning setup including an IFPP controller suitable for use in combination with the embodiment of FIG. 1; [Figure 3] 11 details two options for providing an IFPP converter in combination with a TCA-compliant profile according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0055] Detailed Description of the Invention FIG. 1 illustrates a profile provisioning setup including an IFPP dynamic converter according to an embodiment of the present invention. In a first step S1), a wireless network operator (often referred to as a mobile network operator (MNO)) provides a data generation platform with profile generation data MNO1, including static profile data for generating a profile container T_ISD-P[] and dynamic profile data EDP-P1. The data generation platform is a server or computer capable of processing the profile data to generate a profile. The data generation platform is provided by the eUICC manufacturer, but may alternatively be provided by a profile provider. In step S2), a first profile P1 is generated from the first profile generation data MNO1, including static profile data and dynamic profile data for generating the profile container ISD-P. The first profile P1 may also be referred to as a virtual profile P1 in its current state because it is currently provided on the data generation platform server and has not yet been installed on the eUICC. Furthermore, a dynamic data description file D-XML is generated, which indicates the content and storage location of at least the dynamic profile data in the first profile P1. The wireless network operator NMO also provides a further set of profile data similar to the first profile data NMO1, for example second profile data MNO2, from which a second profile P2 (not further described here) can be generated.

[0056] In an embodiment with an IFPP converter provided in the profile provisioning server SM-DP+, step S2-1) is performed and the generated profile P1 and the generated dynamic data description file D-XML are provided to the profile provisioning server SM-DP+, where the profile P1 may also be named virtual profile P1, without yet being installed on the eUICC.

[0057] In a further step S3-1) within the eUICC, at least one profile container T_ISD-P[ ] is created from the static profile data of the first profile data MNO1.

[0058] In a further step S3-2), the generated first profile P1 and the dynamic data description file D-XML of the first profile P1 are provided to an IFPP dynamic converter, where dynamic profile data EDP-P1 are extracted from the first profile P1 with the aid of the dynamic data description file D-XML. Profile data MNOi for further profiles Pi may be present (not shown).

[0059] According to first option 1, the IFPP dynamic converter is provided in or connected to a data generation platform, in particular at the eUICC manufacturer.

[0060] According to the second option 2, in step S2-1), the IFPP dynamic converter is provided in or connected to a profile provisioning server SM-DP+, to which the generated profile P1 and the generated dynamic data description file D-XML are provided.

[0061] In a subsequent step S4, the extracted dynamic profile data EDP-P1 can be transferred to the eUICC and installed in the profile container T_ISD-P[] created in step S3-1.

[0062] In the embodiment of Figure 1, the dynamic profile EDP-P1 data of the first profile P1 includes the profile container identifier ISD-P AID of the profile container T_ISD-P[] created in step S3-1, the profile name, the ICCID (profile number), the IMSI (subscriber identity), the ACC, the Opc, the authentication key Ki, the PIN, the PUK, the Key and possibly further parameters.

[0063] FIG. 2 illustrates a profile provisioning setup including an IFPP controller in a production environment, suitable for combination with the embodiment of FIG.

[0064] According to the embodiment of FIG. 2, in a subsequent step S4, the extracted dynamic profile data EDP-P1 is transferred from the IFPP controller to the eUICC and installed in the profile container T_ISD-P[] created in step S3-1.

[0065] In detail, step S4 includes: S4-1) Providing the extracted dynamic profile data EDP-P1 extracted in step S3-2) to an IFPP controller installed in the eUICC production environment, where the dynamic profile data EDP-P1 can be encrypted with a transport key and sent to an HSM, re-encrypted in the HSM with an eUICC-specific key and sent back to the IFPP controller; S4-2) eUICC read / write equipment connected to or integrated into the eUICC production machine installed in the eUICC production environment To, The created profile container T_ISD-P[] is have eUICC of To provide, S4-3) Providing the extracted dynamic profile data EDP-P1 to the eUICC production machine by the IFPP controller; S4-4) The eUICC production machine downloads the extracted dynamic profile data EDP-P1 to the eUICC and writes the transferred extracted dynamic profile data EDP-P1 into the profile container T_ISD-P[] created in step S3-1) to create a profile and thereby provision the profile to the eUICC. Includes.

[0066] Figure 3 details two options for providing an IFPP converter in combination with a TCA-compliant profile according to an embodiment of the present invention. The profile data is provided on a data generation platform. The data generation platform is provided in a protected production environment. On the data generation platform, a proprietary profile in a proprietary data format of the owner or host of the data generation platform (e.g., eUICC manufacturer or profile provider) is created from the profile data. The proprietary profile is converted into a TCA-compliant profile to be provided to a profile provisioning platform, which can be provided to an IFPP production machine or SM-DP+. In addition, a dynamic data description file D-XML is also generated.

[0067] According to the embodiment of Fig. 3, an external IFPP requester requests provisioning of profile P1 to an eUICC whose profile container T_ISD-P[] is already created by the static profile data of profile P1 as an empty profile mask T_ISD-P[] for later receiving dynamic profile data EDP-P1 of the same profile P1. By means of the dynamic data description file D-XML, the dynamic profile data EDP-P1 is extracted from the TCA compliant profile, packed into a credentials file and sent to the IFPP container.

[0068] According to the first option, option 1, the dynamic profile data EDP-P1 is extracted from the TCA compliant platform already on the data generation platform. Correspondingly, an IFPP dynamic converter is provided on the data generation platform.

[0069] According to a second option, option 2, the dynamic profile data EDP-P1 is extracted from the TCA-compliant profile on the data provisioning platform SM-DP+. Correspondingly, an IFPP dynamic converter is provided on the data provisioning platform SM-DP+. In this case, both the TCA-compliant profile and the dynamic data description file D-XML are sent from the data generation platform to the data provisioning platform SM-DP+.

[0070] References [1][SGP.22] GSMA SGP.22 RSP Technical Specification Version 2.2.2, 05 June 2020 [2][SGP.02] SGP.02 - Remote Provisioning Architecture for Embedded UICC Technical Specification, Version 4.2, 07 July 2020 [3][SGP.31] GSMA SGP.31 eSIM IoT Architecture and Requirements Version 1.0, 19 April 2022 [4] German Patent No. 102019001840B3 [5][PP IF] SIM Allianc eUICC Profile Package: Interoperable Format Technical Specification, Version 2.3, October 2019 [Explanation of symbols]

[0071] D-XML Dynamic Data Description File EDP-P1 Dynamic Profile Data ISD-P Profile Container MNO Mobile Network Operator MNO1 profile generation data MNO2 Second Profile Data P1 First Profile P2 Second Profile SM-DP, SM-DP+ Profile Provisioning Server T_ISD-P[] Profile container

Claims

1. 1. A method for generating at least one profile for provisioning said profile to an eUICC designed to be device-hosted, comprising: S1) providing profile generation data including static profile data and dynamic profile data (EDP-P1) from a wireless network operator (MNO) or a virtual wireless network operator (MVNO) to a data generation platform for generating a profile container (T_ISD-P[]); S2) generating a profile (P1) and a dynamic data description file (D-XML) indicating the content and storage location of at least the dynamic profile data (EDP-P1) in the profile (P1) from the profile generation data including the static profile data and the dynamic profile data (EDP-P1) for generating a profile container (T_ISD-P[ ]); S3-1) Creating at least one profile container (T_ISD-P[]) from the static profile data in the eUICC; S3-2) Providing the profile (P1) and the dynamic data description file (D-XML) to an IFPP dynamic converter, and extracting the dynamic profile data (EDP-P1) from the profile (P1) with the help of the dynamic data description file (D-XML) in the IFPP dynamic converter, thereafter transferring the extracted dynamic profile data (EDP-P1) to the eUICC, and installing the transferred extracted dynamic profile data (EDP-P1) in the profile container (T_ISD-P[]) created in step S3-1). A method comprising:

2. The method of claim 1, wherein two or more profiles, corresponding dynamic data description files (D-XML) and corresponding extracted dynamic profile data (EDP-P1) are created.

3. S4) A step of transferring the extracted dynamic profile data (EDP-P1) extracted in step S3-2) to the eUICC, and installing the transferred extracted dynamic profile data (EDP-P1) in the profile container (T_ISD-P[ ]) created in step S3-1). The method of claim 1 or 2, further comprising provisioning the generated profile to the eUICC by performing:

4. Step S4) is S4-1) a sub-step of providing the extracted dynamic profile data (EDP-P1) extracted in step S3-2) to an IFPP controller installed in an eUICC production environment; S4-2) providing the eUICC having the created profile container (ISD-P) to an eUICC read / write device connected to or integrated into an eUICC production machine installed in the eUICC production environment; S4-3) a sub-step of providing the extracted dynamic profile data (EDP-P1) to the eUICC production machine by the IFPP controller; S4-4) A substep of downloading the extracted dynamic profile data (EDP-P1) to the eUICC by the eUICC production machine and installing the transferred extracted dynamic profile data (EDP-P1) into the profile container (T_ISD-P[]) created in step S3-1) to create the profile and thereby provisioning the profile to the eUICC. The method of claim 3 , wherein the method is performed as a sequence of:

5. The method of claim 4, wherein in step S3-1), two or more profile containers (T_ISD-P[]) are created from static profile data of different profiles, and step S4-3) further comprises selecting the correct profile container (T_ISD-P[]) corresponding to the dynamic profile data (EDP-P1) provided in step S4-1).

6. 6. The method of claim 5, wherein in steps S4-1 and S4-3, a profile identifier is provided together with the provided dynamic profile data (EDP-P1), and the profile identifier is also provided together with the correct existing created profile container (T_ISD-P[]), and the correct profile container (T_ISD-P[]) is selected based on the provided profile identifier.

7. The profile identifier is - profile container identifier ISD-P AID, - Profile number ICCID, or - Profile name, or a combination of one, some or all of the following: a profile container identifier ISD-P AID, a profile number ICCID and a profile name 7. The method of claim 6, which is or comprises:

8. The dynamic profile data (EDP-P1) is - International Mobile Subscriber Identity IMSI, an authentication key Ki, - Further authentication parameters (OP(c)), - profile number ICCID, - access control status ACC, one or several personal identification numbers PINs, one or several personal unblocking keys PUK, - Default Issuer Security Domain Profile Default-ISD-P, - one, some or all of the other dynamic parameters for the MNO or MVNO, including roaming partners.

9. The generation according to step S2) is performed on the data generation platform, S2-1) From the profile creation data including the static profile data and the dynamic profile data (EDP-P1) for creating a profile container ISD-P, - A unique profile in a unique data format for the profile provider, and - the dynamic data description file (D-XML) generating S2-2) Converting the unique profile into a TCA-compliant profile The method of claim 1 , comprising:

10. The method according to claim 9, wherein the extraction of said dynamic profile data (EDP-P1) according to step S3-2) is performed from said unique profile.

11. The method according to claim 9, wherein the extraction of said dynamic profile data (EDP-P1) according to step S3-2) is performed from said TCA-compliant profile.

12. The method of claim 1 , wherein the IFPP dynamic converter that extracts the dynamic profile data (EDP-P1) is provided in the data generation platform.

13. 2. The method of claim 1, wherein the IFPP dynamic converter for extracting the dynamic profile data (EDP-P1) is provided in a profile provisioning platform (SM-DP+, SM-DP) to which the profile, in particular the TCA compliant profile, and the dynamic data description file (D-XML) are provided (S2-1) after generation.

14. The method of claim 13, wherein the IFPP dynamic converter extracts the dynamic profile data (EDP-P1) from the profile (P1) with the aid of the dynamic data description file (D-XML) in response to the profile provisioning platform (SM-DP+, SM-DP) receiving a request to download the profile (P1) to the eUICC in which the profile container (T_ISD-P[ ]) corresponding to the profile (P1) is already installed.

15. The method of claim 14 , wherein the request to download the profile is received from an eUICC production machine, in particular an eUICC production machine in a factory provisioning environment.

Images