Providing profile data of at least one profile to an eUICC

Abstract

A method for establishing profile data of at least one profile in a target eUICC, the profile data comprising at least an authentication key K, the method comprising the steps of: a) receiving at the eUICC MNO information comprising at least an indication of which profile data shall be generated; the method is characterized by the steps performed after step a) of: b) generating in the target eUICC at least some of the profile data, here at least the network authentication key K; c) outputting from the target eUICC to an external entity the profile data generated in the target eUICC or at least a part thereof after step b); d) receiving at the external entity at least some or all of the profile data output, here at least the authentication key K; and e) initiating at the external entity or at an entity invoked by the external entity the generation of a profile comprising the received authentication key.

Description

Technical Field

[0001] This invention relates to configuration file data for providing at least one configuration file to an eUICC, which is designed to be hosted in a wireless network communication device (or simply a mobile device). Background Technology

[0002] The world is connected via wireless communication networks (also known as mobile communication networks), where devices hosting eUICCs communicate securely with each other and with wireless network backend servers. The eUICC hosted on a device includes at least one or more subscription profiles, or simply profiles, containing profile data such as the International Mobile Subscriber Identity (IMSI, or SUPI or NAI in 5G), an authentication key K, a profile number ICCID, an OTA key, and other profile data, enabling communication within the wireless communication network.

[0003] Several form factors are known for eUICC, including insertable SIM cards or pSIMs, embedded and soldered eUICCs or eSIMs in the strict sense, and integrated iUICCs or iSIMs integrated into the chipset of the device hosting the eUICC. In the context of this invention, unless explicitly stated otherwise, eUICC is understood to include any form factor, including any of the listed form factors.

[0004] Devices are referred to, for example, as consumer wireless network communication devices (such as smartphones and network-connected tablet PCs), and as M2M wireless network communication devices (including automotive wireless network communication devices and industrial wireless network communication devices). In the following text, a device refers to a wireless network communication device that hosts an eUICC including one or more profiles and is configured to communicate with other devices or network servers via a mobile communication network, including eUICCs used for security-related tasks such as authentication.

[0005] Reference [1][SGP.22] GSMA SGP.22 RSP Technical Specification Version 3.0, October 19, 2022, describes the process and architecture for supplying configuration files to eUICCs already hosted in consumer devices in the field. In the SGP.22 scenario, the configuration file server that downloads the configuration files to the eUICC is also called SM-DP+.

[0006] According to [1][SGP.22], Section 2.5 “Profile Protection and Delivery”, the operator’s profile is protected within the profile package before being downloaded to eUICC. As further described in Section 2.5.1 “Overview of Profile Package Types”, the profile package will be in the following different formats from generation to download:

[0007] • Unprotected Profile Package (UPP): The original eUICC profile package TLV sequence.

[0008] • Protected Profile Package (PPP): Segmented and protected within the BSP payload TLV.

[0009] • Binding Profile Package (BPP): Contains session key protocol information, key replacement package, and ISD-P creation and configuration information.

[0010] • Segmented Binding Profile Package (SBPP): The BPP is segmented into storage data APDU scripts for loading into the eUICC. This step is performed by the LPD when the LPD is in the device.

[0011] Reference [1][SGP.22] allows the use of keys that are not specific to any eUICC or keys that are specific to the eUICC to encrypt protected configuration file packages. The process of converting a protected configuration file package PPP into a bound configuration file package BBP is also called binding. The purpose of the operation of converting a protected configuration file package PPP into a bound configuration file package BPP is to link the protected configuration file package to a specific eUICC.

[0012] According to [1][SGP.22], Section 2.5.4 “Binding Profile Package”, the Binding Profile Package (BPP) is generated by SM-DP+ within the Profile Package Binding function. This is done during the key negotiation process between eUICC and SM-DP+, which is described in the Download and Installation process (Section 3.1.3). According to [1][SGP.22], Section 2.6.4.1 “Key Negotiation”, the Elliptic Curve Key Negotiation (ECKA) algorithm is used to establish the shared secret value. It should follow the definition of anonymous Diffie-Hellman key negotiation in BSI TR-03111. The algorithm performs as follows:

[0013] • The SM-DP+ uses the eUICC one-time public key otPK.EUICC.KA and the SM-DP+ one-time private key (sometimes referred to as the "secret" of the "private key") otSK.DP.KA, and

[0014] • eUICC uses SM-DP + one-time public key otPK.DP.KA and eUICC one-time private key otSK.EUICC.KA;

[0015] To calculate the shared secret value.

[0016] Based on the shared secret value, session keys S-ENC and S-MAC are derived. These session keys S-ENC and S-MAC are then used to encrypt and authenticate the configuration file protection keys PPK-ENC and PPK-MAC. Using the configuration file protection key PPK-ENC, the payload of the protected configuration file package is encrypted (unless, according to a specific option, it is directly encrypted with S-ENC).

[0017] After SM-DP+ has established the binding profile package BBP and downloaded BBP to eUICC, eUICC performs the above key negotiation to export the shared secret value and finally export the profile protection key PPK-ENC (or S-ENC in a specific option), and decrypts the encrypted protected profile package payload.

[0018] Clearly, only the eUICC that contributed the one-time public key otPK.EUICC.KA can decrypt the encrypted protected configuration file payload.

[0019] For the binding process, in order to bind the protected configuration file package PPP to eUICC and generate the binding configuration file package BBP, the above two public keys and two private keys are required.

[0020] Reference [3][SGP.32] GSMA eSIM IoT Technical Specification, version 1.0.1, July 4, 2023, discloses the process and architecture for providing profiles to eUICC hosted in IoT devices, similar to [2][SGP.22] for consumer devices, but with some differences in architecture (i.e. IPA instead of LPA) and process.

[0021] Similarly, according to [2][SGP.32], the configuration file protection key negotiated using a process similar to that described in [1][SGP.22] above is used to prepare the binding configuration file package (BPP).

[0022] The risk remains that the key used to prepare the binding profile package may be shared with an unauthorized party, enabling the profile to be loaded and installed into an unauthorized eUICC. This risk exists for both consumer and IoT eUICCs.

[0023] Reference [4] EP2283666B1 discloses a method for initiating a first operation of a SIM (UICC) in a mobile network. The SIM stores a non-personal parameter dataset, which includes at least a non-personal subscriber identifier (IMSI) and a non-personal network authentication key (K), which may be the same for several SIMs. During the first operation of the SIM in the mobile network, the SIM is personalized, wherein a personal parameter dataset is established, in which the personal subscriber identifier (IMSI) and the personal network authentication key (K) are transmitted to the SIM and stored in the SIM.

[0024] Reference [5] EP3669562B1 describes a method for initiating a first operation of a SIM (UICC) in a mobile network. The SIM already stores an Individual Subscriber Identity (IMSI), but only stores a Non-Individual Network Authentication Key (K), which can be the same for several SIMs. In the personalization step, the Individual Network Authentication Key K is transmitted to the SIM with the Individual Subscriber Identity (IMSI), and the Non-Individual Network Authentication Key K is replaced with the Individual Network Authentication Key K. Since the Individual Network Authentication Key K is only sent in a controlled manner to the SIM with the specified Individual Subscriber Identity (IMSI), unauthorized cloning of the parameter dataset and the distribution of cloned parameter datasets to more SIMs than allowed can be prevented. Summary of the Invention

[0025] The purpose of this invention is to provide a secure method for providing a configuration file to an eUICC, which is preferably applicable to both consumer and IoT eUICC.

[0026] The object of the present invention is achieved by a method having the following features according to claim 1. Embodiments of the invention are presented in the dependent claims.

[0027] More specifically, the object of the present invention is achieved by a method for establishing configuration file data for at least one configuration file in a target eUICC, the configuration file data including at least an authentication key K.

[0028] The method includes the following steps: a) receiving MNO information at eUICC, the MNO information including at least an indication of which configuration file data should be established.

[0029] The method is characterized by the steps performed after step a):

[0030] b) Generate at least some of the configuration data in the target eUICC configuration data, where at least the network authentication key K is generated;

[0031] c) After step b), output the configuration file data generated in the target eUICC, or at least a portion thereof, from the target eUICC to an external entity;

[0032] d) Receive at least some or all of the output configuration file data at the external entity, including at least the authentication key K; and

[0033] e) Initiate the generation of a configuration file including the received authentication key at the external entity or at the entity invoked by the external entity.

[0034] While existing binding solutions rely on leveraging the target eUICC's footprint to protect the binding profile package (BPP), or on transferring the eUICC's unique profile data from a profile server to the eUICC, this invention proposes generating at least some profile data onboard within the eUICC, including at least the network authentication key K.

[0035] The solution of the present invention has the following advantages:

[0036] a) Delayed configuration file generation is implemented, eliminating the need to pre-assign configuration files to the target eUICC at an early stage.

[0037] b) The immediate personalization achieved through the network authentication key K generated in the target eUICC prevents clones from being distributed to the field;

[0038] c) Since the network authentication key K is generated within eUICC, it prevents the network authentication key K from being leaked to entities seeking to produce clones, which helps the proposed solution to be a secure approach.

[0039] Therefore, the present invention provides a secure method for providing a configuration file to an eUICC (here referred to as the target eUICC).

[0040] Some other configuration file data or other data can be pre-stored on the eUICC, and onboard generated data or configuration file data can be combined with pre-stored data or configuration file data.

[0041] MNO information may include information included in the configuration file download order, such as EID, ICCID, configuration file type, and similar MNO information according to the configuration file download order [1][SGP.22].

[0042] According to some embodiments, the external entity is or includes one or more of the following:

[0043] -Local Profile Assistant LPA or IoT Profile Assistant IPA;

[0044] -SM-DP+ server;

[0045] -OEM server or carrier server or EUM;

[0046] - The transport chain of entities, including the transport chains of several entities listed above.

[0047] According to some embodiments, the network authentication key K generated in step b) is specific and / or unique to the target eUICC.

[0048] According to some embodiments, before performing step b) to generate the configuration file data, the target eUICC lacks a network authentication key K specific to or unique to the target eUICC. The eUICC may be empty, or it may only lack the authentication key K.

[0049] According to some embodiments, before performing step b) to generate the configuration file data, the target eUICC contains pre-installed configuration file data, but lacks configuration file data in the form of a network authentication key K specific to or unique to the target eUICC. In such embodiments, the pre-installed configuration file data can be combined with onboard generated configuration file data.

[0050] According to some embodiments, step b) of generating configuration file data is triggered by step a) of receiving MNO information. In other words, the onboard generation of authentication key K and possibly other configuration file data can be triggered by receiving MNO information, particularly by receiving a configuration file order that includes such MNO information, through which a configuration file is ordered for the eUICC.

[0051] According to some embodiments, the configuration file data generated in the target eUICC in step b) further includes one or more of the following:

[0052] -OTA key;

[0053] -Security channel key;

[0054] - Symmetric keys, especially symmetric keys for any purpose;

[0055] - Asymmetric key pairs, especially asymmetric key pairs for any purpose.

[0056] According to some embodiments, in step a), MNO information is received from any of the following entities:

[0057] -Local Profile Assistant LPA or IoT Profile Assistant IPA;

[0058] -SM-DP+ server;

[0059] -OEM server or carrier server or EUM;

[0060] - A transport chain that includes multiple entities among those listed above.

[0061] According to some embodiments, the configuration file data generated in step b) in the target eUICC is embodied in or includes one or more of the following:

[0062] - One or more random numbers;

[0063] - Export configuration file data derived from one or more random numbers, representing the master key.

[0064] Other random numbers and / or other data may have been pre-stored in the eUICC. Pre-stored and onboard generated data can be combined with each other.

[0065] According to some embodiments, the network authentication key K generated in step b) in the target eUICC is generated through a key generation process including one or more of the following steps:

[0066] - Establish the network authentication key K as a random number generated in the target eUICC;

[0067] - Establish the network authentication key K based on the random number generated in the target eUICC and other key-derived data;

[0068] - Provide the generated network authentication key K as the master key to derive additional keys that are specific to and / or unique to the target eUICC, wherein the additional keys include one or more of the following: OTA key; secure channel key; any other symmetric or asymmetric key;

[0069] - Provide the generated network authentication key K as a key derived from the master key, which is also used to derive additional keys specific to and / or unique to the target eUICC, wherein the additional keys include one or more of the following: OTA key; secure channel key; any other symmetric or asymmetric key.

[0070] According to some embodiments, in step c), the configuration file data or a portion thereof output from the target eUICC is output in encrypted form using an output key.

[0071] According to some embodiments, the output key is manifested as one or more keys that satisfy one or more of the following characteristics:

[0072] - The output key generated in the target eUICC;

[0073] - In the case of receiving a bulk binding configuration file package at the target eUICC, a key that is the same as the key used to encrypt the bulk binding configuration file package, or a key derived from the key used to encrypt the bulk binding configuration file package;

[0074] -Based on the random keys PPK-ENC and PPK-MAC of SGP.22;

[0075] - Based on the session keys S-ENC and S-MAC of SGP.22;

[0076] - Output keys exported from a one-time key newly generated on eUICC each time output is performed, and / or other keys included in the bulk binding configuration file package.

[0077] According to some embodiments, the method further includes: setting or maintaining at least a portion of the generated and / or received configuration file data in a blocked or disabled state, in which the configuration file data is inoperable, and releasing or enabling the blocked or disabled configuration file data upon the occurrence of a specified event, wherein the specified event is one of the following:

[0078] - Use the generated authentication key K to authenticate or perform initial authentication of the eUICC in the mobile network;

[0079] - Successfully authenticate or first-time authenticate eUICC in the mobile network using the generated authentication key K;

[0080] - The generated configuration file data is verified by an external entity, which may be or include any one or more of the following: SM-DP+; EUM.

[0081] According to some implementation schemes, the method further includes, after step e):

[0082] f) Generate a configuration file containing the received authentication key K at the external entity or at the entity invoked by the external entity.

[0083] According to some embodiments, the generated configuration file may also include one or more or all of the following additional configuration file data:

[0084] -Subscriber ID (IMSI; SUPI; NAI);

[0085] - Configuration file number ICCID.

[0086] According to some embodiments, the method further includes one or more or all of the following steps:

[0087] g) Download the generated configuration file from eUICC; or exclude the configuration file data generated in eUICC from the generated configuration file data.

[0088] h) Install the downloaded configuration file in eUICC;

[0089] i) Enable the configuration file installed in eUICC. Attached Figure Description

[0090] Embodiments of the invention will now be described with reference to the accompanying drawings, in which the same parts are indicated by the same reference numerals throughout the drawings, and wherein:

[0091] Figure 1 The configuration file supply settings applicable to this invention are based on [1] SGP.22;

[0092] Figure 2 The configuration file provided in accordance with [2]SGP.32 applies to the present invention. Detailed Implementation

[0093] Figure 1 A configuration file provisioning setup according to [1] SGP.22 suitable for the present invention is shown. The setup includes a device as a consumer device, including a local configuration file assistant LPA embodied in the device as an LPA device (LPAd). Furthermore, the setup includes an eUICC hosted on the device. Additionally, the setup includes a configuration file server SM-DP+. The setup also includes an end user (consumer). On the device, a configuration file management application MNP APP is implemented, thereby allowing the end user (consumer) operating the device to manage configuration files in the eUICC, including selecting MNOs, and downloading, installing, enabling, disabling, and deleting configuration files for the selected MNOs.

[0094] This setup may also include, and preferably includes, the carrier, SM-DS, EUM, and CI.

[0095] exist Figure 1 The prerequisite for implementing the invention in the configuration provisioning settings according to [1]SGP.22 is that the eUICC has the ability to generate keys (e.g., authentication key K and OTA key), while according to [1]SGP.22, the eUICC is neither required to have such an ability nor prohibited from having such an ability.

[0096] In the following text, see references Figure 1 This section will describe a method for creating configuration file data in eUICC according to an embodiment of the present invention.

[0097] End users (consumers) select MNO in the MNP App.

[0098] The MNO App uses the MNO information of the selected MNO to launch the local profile assistant LPAd to begin profile management. The MNO data includes at least an indication of which profile data should be generated.

[0099] The specification for configuration file data can be explicit, by specifying the configuration file data, or implicit, by generating a standard configuration file dataset when no configuration file data is explicitly specified.

[0100] exist Figure 1In one embodiment, the MNO information includes an indication of the authentication key K, a limited number of OTA keys, and the URL of the selected MNO or the SM-DP+ profile server associated with the selected MNO.

[0101] In response to the launch of the MNP APP, the LPA starts eUICC to generate configuration file data for the configuration file.

[0102] Therefore, LPA sends the MNO information to eUICC, and in step a), eUICC receives the MNO information.

[0103] According to the first option, only MNO information is sent and received, and is interpreted in eUICC as a request to generate configuration file data.

[0104] According to the second option, along with the MNO information, an explicit request to generate configuration file data is sent and received at eUICC.

[0105] Subsequently, in step b), in eUICC, the indicated configuration file data is generated, which in this case is the authentication key K and a limited number of OTA keys.

[0106] In the subsequent step c), eUICC encrypts the generated configuration file data authentication key K and OTA key.

[0107] In step c) following step b), the eUICC sends or outputs the generated and then encrypted configuration file data (authentication key K, OTA key) and the URL of SM-DP+ to an external entity outside the eUICC. Figure 1 In this embodiment, eUICC first sends the encrypted configuration file data (including the authentication key K and the key data of the OTA key) to the local configuration file assistant LPA, and LPA further sends the encrypted configuration file data to SM-DP+ (transport chain eUICC-LPA-SM-DP+) associated with URLS.

[0108] In step d), the SM-DP+, as the final target external entity, receives the output configuration file data, including the authentication key K and the OTA key.

[0109] In step e), SM-DP+ initiates the generation of a configuration file including the received authentication key K. In step f), SM-DP+ generates a configuration file including the received authentication key K and other configuration file data provided at SM-DP+. The additional configuration file data may include: subscriber identifier IMSI, SUPI, or NAI; configuration file number ICCID.

[0110] In step g), SM-DP+ downloads the generated configuration file (including or excluding configuration file data generated in eUICC) to eUICC via the local configuration file assistant LPA.

[0111] In step h), eUICC installs the downloaded configuration file within itself, potentially utilizing previously generated key material to fill in the gaps. Additionally, eUICC sends a notification to SM-DP+ regarding the installation result.

[0112] In step i), the end user (consumer) enables the configuration file installed in eUICC.

[0113] Figure 2 A profile provisioning setup according to [2] SGP.32 suitable for the present invention is shown. This setup includes an eUICC hosted in an IoT device, an SM-DP+ profile server, and an eSIM IoT remote manager (eIM). The setup may also include, and preferably includes, an operator and an SM-DS.

[0114] exist Figure 2 The prerequisite for implementing the invention in the configuration provisioning settings according to [2]SGP.32 is that the eUICC has the ability to generate keys (e.g., authentication key K and OTA key), while according to [2]SGP.32, the eUICC is neither required to have such an ability nor prohibited from having such an ability.

[0115] In the following text, see references Figure 2 This section will describe a method for creating configuration file data in eUICC according to an embodiment of the present invention.

[0116] eIM sends MNO information (e.g., IMSI, DP+ URL, etc.) to eUICC via IPAd or directly via IPAe, and requests key generation.

[0117] In step a), eUICC receives MNO information and requests.

[0118] In step b), eUICC generates keys as configuration file data, and in step c), these keys (via IPAd or via IPAe) are sent along with encrypted MNO information to the selected SM-DP+.

[0119] Steps d), e), and f): SM-DP+ uses the received key generated in the eUICC and additional configuration file data to generate a configuration file. This additional configuration file data may include IMSI / ICCID.

[0120] According to one option, the binding of the IMSI / ICCID to the generated key has already been completed in the eUICC's internal MNO configuration file, and the configuration file data output in step c) includes the IMSI / ICCID and the generated key. This use case is generally applicable to the scenarios in [1] and [2], and may be particularly advantageous in IoT scenarios (e.g., [2][SGP.32]).

[0121] In step g), SM-DP+ sends the required profile data to the operator (=MNO's server), including the key generated by eUICC and the subscriber identifier IMSI, SUPI, or NAI, for network activation of the profile.

[0122] In addition, in step g), SM-DP+ sends a configuration file to eUICC with or without key material generated by eUICC.

[0123] In step h), eUICC installs the configuration file and potentially uses previously generated key material to fill in the blanks.

[0124] Furthermore, eUICC sends a notification of the installation results to SM-DP+.

[0125] In addition, eUICC sends a notification to eIM regarding the installation results.

[0126] In addition, eIM sends a request to eUICC to enable the MNO profile.

[0127] References

[0128] [1][SGP.22] GSMA SGP.22 RSP Technical Specification, Version 3.0, October 19, 2022

[0129] [2][SGP.32]GSMA eSIM IoT Technical Specification, Version 1.0.1, July 4, 2023

[0130] [3]EP2283666B1

[0131] [4]EP3669562B1

Claims

1. A method for establishing configuration file data for at least one configuration file in a target eUICC, the configuration file data including at least an authentication key K, the method comprising the following steps: a) Receive MNO information at eUICC, the MNO information including at least an indication of which configuration file data should be created; The method is characterized by the following step performed after step a): b) Generate at least some of the configuration file data in the target eUICC configuration file data, where at least the network authentication key K is generated; c) After step b), output the configuration file data generated in the target eUICC or at least a portion thereof from the target eUICC to an external entity; d) Receive at least some or all of the output configuration file data at the external entity, where at least the authentication key K is received; and e) At the external entity or at the entity invoked by the external entity, initiate the generation of a configuration file including the received authentication key.

2. The method according to claim 1, wherein, The external entity is or includes one or more of the following: -Local Profile Assistant LPA or IoT Profile Assistant IPA; -SM-DP+ server; -OEM server or carrier server or EUM; - A transport chain that includes multiple entities among those listed above.

3. The method according to claim 1 or 2, wherein, The network authentication key K generated in step b) is specific and / or unique to the target eUICC.

4. The method according to any one of claims 1 to 3, wherein, Before step b) of generating configuration file data is executed: - The target eUICC lacks a network authentication key K that is specific or unique to the target eUICC; or / and - The target eUICC contains pre-installed configuration file data, but lacks configuration file data in the form of a network authentication key K specific or unique to the target eUICC.

5. The method according to any one of claims 1 to 4, wherein, Step b) of generating the configuration file data is triggered by step a) of receiving the MNO information.

6. The method according to any one of claims 1 to 5, wherein, The configuration file data generated in step b) in the target eUICC further includes one or more of the following: -OTA key; -Security channel key; - Symmetric keys, especially symmetric keys for any purpose; - Asymmetric key pairs, especially asymmetric key pairs for any purpose.

7. The method according to any one of claims 1 to 6, wherein, In step a), the MNO information is received from any of the following entities: -Local Profile Assistant LPA or IoT Profile Assistant IPA; -SM-DP+ server; -OEM server or carrier server or EUM; - A transport chain that includes multiple entities among those listed above.

8. The method according to any one of claims 1 to 7, wherein, The configuration file data generated in step b) in the target eUICC is embodied in or includes one or more of the following: - One or more random numbers; - Export configuration file data derived from one or more random numbers, representing the master key.

9. The method according to any one of claims 1 to 8, wherein the network authentication key K generated in step b) in the target eUICC is generated by a key generation process comprising one or more of the following steps: - Establish the network authentication key K as a random number generated in the target eUICC; - The network authentication key K is established based on the random number generated in the target eUICC and additional key derivation data; - Provide the generated network authentication key K as the master key to derive an additional key specific and / or unique to the target eUICC, wherein the additional key includes one or more of the following: OTA key; secure channel key; any other symmetric or asymmetric key; - The generated network authentication key K is provided as a key derived from the master key, which is also used to derive an additional key specific to and / or unique to the target eUICC, wherein the additional key includes one or more of the following: OTA key; secure channel key; any other symmetric or asymmetric key.

10. The method according to any one of claims 1 to 9, wherein, In step c), the configuration file data or a portion thereof output from the target eUICC is output in an encrypted form using the output key.

11. The method according to claim 10, wherein, The output key is manifested as one or more keys that satisfy one or more of the following characteristics: - The output key generated in the target eUICC; - In the event that a bulk binding configuration file package is received at the target eUICC, the same key as the key used to encrypt the bulk binding configuration file package, or a key derived from the key used to encrypt the bulk binding configuration file package; -Based on the random keys PPK-ENC and PPK-MAC of SGP.22; - Based on the session keys S-ENC and S-MAC of SGP.22; - Output keys exported from the one-time keys newly generated on eUICC for each output, and / or other keys included in the bulk binding configuration file package.

12. The method according to any one of claims 1 to 11, further comprising: For at least some of the generated and / or received configuration file data, the at least portion of the configuration file data is set or held in a blocked or disabled state, in which the configuration file data is inoperable, and the blocked or disabled configuration file data is released or enabled upon the occurrence of a specified event, wherein the specified event is one of the following: - Use the generated authentication key K to authenticate or perform initial authentication of the eUICC in the mobile network; - Successfully authenticate or first-time authenticate eUICC in the mobile network using the generated authentication key K; - The generated configuration file data is verified by an external entity, which may be or include any one or more of the following: SM-DP+; EUM.

13. The method according to any one of claims 1 to 12, further comprising, after step e): f) Generate a configuration file including the received authentication key K at the external entity or at an entity invoked by the external entity.

14. The method according to claim 13, wherein, The generated configuration file also includes one or more of the following additional configuration file data: -Subscriber ID (IMSI; SUPI; NAI); - Configuration file number ICCID.

15. The method of claim 13 or 14, further comprising one or more of the following steps: g) Download to the eUICC: the generated configuration file; or the generated configuration file excluding configuration file data generated in the eUICC; h) Install the downloaded configuration file into the eUICC; i) Enable the configuration file installed in the eUICC.

Images