Providing profile package on profile server for downloading to eUICC

Abstract

A method for providing a configuration file package for downloading from a configuration file server (SMD +) to an eUICC releases a linked ICCID and generates new network credentials for configuration file downloading.

Description

Technical Field

[0001] The present invention relates to providing a configuration file package on a configuration file server, for downloading the configuration file package from the configuration file server to an eUICC, and to a configuration file downloading method. Background Art

[0002] The mobile device hosts at least one eUICC including one or more profiles that allow the mobile device to authenticate itself with respect to a mobile network in order to establish and operate a communication session, such as a voice call or data transfer, in the mobile network.

[0003] Document from the prior art [1] [SGP.22 V2.2.2], GSMA SGP.22 - SGP.22 RSP Technical Specification, Version 2.2.2, 5 June 2020 (2020-06-05), relates to remote SIM provisioning, which is understood as downloading, installing, enabling, disabling and deleting profiles on an embedded Universal Integrated Circuit Card (eUICC).

[0004] To establish and operate a communication session in a mobile network under a specific profile, the profile includes a set of identifiers, such as the IMSI and Ki. In addition to identifiers, the profile also contains OTA keys (OTA = Over the Air), also known as network credentials, used in conjunction with communications between the eUICC and the OTA platform. The OTA platform is understood to be the operator platform used to remotely manage the UICC and the contents of the operator profile enabled on the eUICC. In this document, an operator is understood to be a mobile network operator (MNO) or a mobile virtual network operator (MVNO), or generally, a company that provides wireless cellular network services.

[0005] Document [2][PP], SIM Alliance, eUICC Profile Package: Interoperable Format Technical Specification, Version 2.3, October 2019, defines the content and format of the elements of a Profile Package for downloading a profile to an eUICC. A profile contains its content in the form of a ProfileElement PE. Appendix A of [2] shows a template Profile Package showing the mandatory elements of a Profile Package. According to [2] 9.2, the Profile Package contains a Profile Number, an "Integrated Circuit Card Identifier" ICCID. According to [2] 9.5, a USIM Profile Package for GSM type 4G or lower contains an Elementary File EF containing an International Mobile Subscriber Identity IMSI and an Elementary File EF containing a Key, or similar Elementary File EF in the case of an ISIM or CSIM Profile Package. A fifth generation 5G Profile contains a Subscription Permanent Identifier SUPI containing the IMSI.

[0006] From the prior art document [1] [SGP.22 V2.2.2], GSMA SGP.22-SGP.22 RSP Technical Specification, Version 2.2.2, 5 June 2020 (2020-06-05), considering mobile network generations up to the fourth generation 4G, discloses a standard set of profile identifiers comprising or consisting of an authentication key Ki and an identifier International Mobile Subscriber Identity IMSI. In mobile networks of the 5G generation, the set of profile identifiers includes SUPI as an analogue of IMSI and is used to enter and run a communication session in the mobile network in a hidden form like SUCI.

[0007] Document [1][SGP.22 V2.2.2], in particular Chapter 3.1.3 “Profile Download and Installation”, deals with the process of downloading profiles from the Profile Server (SM-DP+ in [1]) to the eUICC.

[0008] Document [1][SGP.22V 2.2.2], in particular chapter 3.1.1 “Profile Download Initiation”, also covers the process of ordering profiles at a profile server (referred to as SM-DP+ in [1]) by a connectivity service provider CSP (referred to as an operator in [1] and assumed to be a mobile network operator MNO).

[0009] BookFigure 2 Figure 9 from document [1][SGP.22 V2.2.2], chapter 3.1.1 "Profile Download Initiation" is shown. [1][SGP.22 V 2.2.2], Figure 9 and the related text of chapter 3.1.1 describe the process by which an operator orders a profile at a profile server SM-DP+. In step (1), the operator sends a profile download command to the SM-DP+ via channel ES2+ using the command ES2+.DownloadProfile(EID, profile type or ICCID). The profile download command indicates the EID of the target eUICC (EID = identifier of the eUICC hardware) and the profile type or a different profile number ICCID. According to the description of step (1) in 3.1.1.2 of [1], if an ICCID is given, the SM-DP+ shall verify that the ICCID is available. In case of an Operator Subscription Profile, a different ICCID is given in the Profile Download Command, and the SM-DP+ is aware that the ICCID is assigned to a Profile that has already been downloaded to an eUICC, then the SM-DP+ shall classify the ICCID as unavailable and shall not honour the Profile Download Command without further action. There is no further provision in the SGP.22 specification [1] [SGP.22 V2.2.2] for the action to be taken.

[0010] A known solution, at least internally, to release the ICCID of an already downloaded profile so that it becomes available is to delete the profile from its download location in the eUICC and provide a Profile Delete Notification from the eUICC to the SM-DP+. Upon receiving the Profile Delete Notification, the SM-DP+ releases the ICCID as available, the Profile Download Command referencing the ICCID is approved (assuming no other restrictions exist), and the profile can be downloaded to the target eUICC indicated in the Profile Download Command. The target eUICC can be the same or a different eUICC than the eUICC from which the profile was deleted.

[0011] Another known solution to circumvent ICCID linking (locking) is to order a new profile containing a new IMSI and assigned a new ICCID. Each IMSI and ICCID in a profile ready for use in a mobile network must be registered with the Home Location Register (HLR) of the MNO hosting the profile. The MNO charges a fee for each IMSI and ICCID registered with its HLR. Therefore, registering multiple IMSIs and ICCIDs with the MNO HLR is expensive.

[0012] Some IMSIs or ICCIDs or IMSI / ICCID pairs in the field are linked (locked) even if they are no longer in use. For example, a user may stop using their old device (e.g., put it in a drawer), including the eUICC hosted in the device, and take no further action with respect to the device / eUICC, in particular, not deleting any profiles from the eUICC. In this case, the IMSIs or ICCIDs or IMSI / ICCID pairs of the profiles on the eUICC remain linked (locked) forever in the worst case.

[0013] Another use case is that a profile user with several mobile devices may want to use copies of their profile on several of their devices without having to delete the profile on any device and without having to utilize multiple IMSIs and / or ICCIDs. However, currently, if the user wants to download the same profile a second time, the same profile credentials for network access are used, and downloading the profile a second time is only possible if the profile server receives a profile deletion notification for the already downloaded profile. Summary of the Invention

[0014] An object of the present invention is to provide a flexible, efficient and secure profile download solution that allows the use or reuse of linked (locked) profile numbers, such as ICCIDs.

[0015] In more detail, the object of the invention is achieved by a method having the following features according to claim 1. Embodiments of the invention are presented in the dependent claims.

[0016] A method for providing a profile package for downloading from a profile server to an eUICC hosted in a mobile device comprises the following steps at the profile server:

[0017] a) receiving a configuration file download command including a configuration file type or a configuration file number from a connection service provider server;

[0018] b) generating a profile package comprising profile credentials and a profile number assigned taking into account the received profile type or the received profile number; preferably, the profile credentials are used as usual for the profile;

[0019] c) Provide the generated configuration file package for downloading to the eUICC.

[0020] The method is characterized by the following steps:

[0021] a1) identifying the received or allocated Profile Number as linked to a Profile already downloaded to the eUICC;

[0022] a2) receiving a notification from the connection service provider server that release of the linked profile number is permitted due to the satisfaction of a release criterion; preferably, the connection service provider server verifies the release criterion at its terminal and notifies the profile server of the verification result, i.e., the release of the profile number is permitted;

[0023] a3) The configuration file number of the configuration file server to release the link;

[0024] a4) The Profile Server generates network access credentials to be used to download the generated Profile Package to the eUICC.

[0025] This method allows a linked profile number to be reused for a new profile download when it meets the release criteria. A linked profile number is a profile number that was previously used to download a profile to an eUICC. Due to the generation of (new) network credentials, the eUICC and backend infrastructure that previously downloaded a profile to the eUICC using the same profile number are unable to access the new profile download process. Therefore, even when using the same profile number, the confidentiality and security of the profile download are ensured due to the (new) generated network credentials. Because the profile number is released on the fly when needed, this method is particularly flexible and efficient.

[0026] Release criteria may include one or more of the following:

[0027] (1) The profile number has not been used in any authentication request received at the connectivity service provider server from any mobile device or eUICC for a predetermined period of time or longer, where the period of time may be, for example, one year, as a non-limiting example. In this case, the release of the profile number means that the profile number is no longer used for the profile to which the profile number was linked before the release. Thus, the release swaps the profile number from the old profile to the new profile, with the same number of profiles (e.g., one) being assigned to the profile number before and after the release.

[0028] (2) The Profile Number is intended to be used for two or more copies of the same Profile, which are intended to remain available in parallel on two or more different Mobile Devices or / and on two or more different eUICCs. In this case, the released Profile Number may also continue to be used for the Profile to which the Profile Number was linked before the release. Thus, the release of the Profile Number enables the addition of an additional Profile to the same Profile Number.

[0029] The Network Access Credentials may include one or more of the following: - OTA keys; - NAA parameters; - AKA parameters for MILENAGE or TUAK or a proprietary authentication algorithm. The Network Access Credentials are designed to enable secure and confidential profile downloads from the Profile Server to the eUICC via the network.

[0030] The network access credentials are preferably different from the network access credentials generated for the profile that has been downloaded to the eUICC.

[0031] The connectivity provider can be one or more of the following:

[0032] - Mobile network providers, such as MNOs;

[0033] -Mobile Virtual Network Providers, such as MVNOs.

[0034] Step a2) may include the following sub-steps:

[0035] a2-1) Sending a download command response to the connection service provider server, notifying the connection service provider server of the linked configuration file number, and requesting the connection service provider server to release the linked configuration file number;

[0036] a2-2) receiving a confirmation command from the connection service provider server for the profile number allowing release of the link;

[0037] a2-3) Release the linked profile number at the profile server.

[0038] The profile already downloaded to the eUICC may include a profile identifier, such as an IMSI, wherein the profile package of step b) may include the same profile identifier, such as an IMSI, as the profile already downloaded to the eUICC. This embodiment of the present invention allows for the reuse of a profile number (such as an ICCID) and a profile identifier (such as an IMSI) and is particularly useful when downloading the same profile to another device of the same user. In other use cases, such as when an expired profile number (such as an ICCID) is to be reused, the newly used profile identifier (such as an IMSI) will typically be different from the previously used profile identifier (such as an IMSI).

[0039] The configuration file download command of step a) may also include an eUICC hardware identifier, such as an EID, of the eUICC to which the configuration file package is to be downloaded.

[0040] A method for downloading a configuration file to an eUICC, comprising the following steps:

[0041] - providing the configuration file package on the configuration file server by the method described above;

[0042] - Here the provided profile package is downloaded from the Profile Server to the eUICC using the generated network access credentials.

[0043] Preferably, the generated network access credentials have not been previously used for configuration file download.

[0044] The profile server according to the present invention is implemented to perform the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Embodiments of the present invention will now be described with reference to the accompanying drawings, wherein like parts are designated by like reference numerals throughout, and in which:

[0046] Figure 1 A diagram depicting a profile subscription (including a release-linked ICCID) according to an embodiment of the present invention;

[0047] Figure 2 Figure 1 of SGP.22 V2.2.2 shows a diagram of a remote SIM provisioning architecture suitable for implementing the present invention. DETAILED DESCRIPTION

[0048] Figure 1 A diagram depicting profile subscription and transfer from a profile server SMDP+ to an eUICC hosted in an eSIM device is shown, where the linked profile number ICCID is released according to an embodiment of the present invention.

[0049] The connectivity service provider server CSP sends a download command for the profile to the profile server SMDP+ via the ES2+ channel. The download command contains the profile type and, optionally, the eUICC hardware identifier EID of the eUICC to which the profile package is to be downloaded.

[0050] The Profile Server SMDP+ checks the Profile Type and assigns a Profile Number ICCID that matches the Profile Type to the Profile Command. Furthermore, the Profile Server SMDP+ recognizes that the assigned Profile Number ICCID is not free but is already linked to a Profile residing in the eUICC.

[0051] The profile server SMDP+ sends a notification to the connection service provider server CSP through the channel ES2+ that the allocated profile number ICCID is linked to the profile residing in the eUICC.

[0052] The connection service provider server CSP checks the ICCID, finds that the ICCID can be released according to the release criteria, and sends a notification of allowing the release of the allocated profile number ICCID to the profile server SMDP+ through the channel ES2+.

[0053] In response to receiving a notification from the connectivity service provider (CSP) allowing the release of the assigned profile number, the profile server SMDP+ releases the profile number ICCID. Furthermore, the profile server SMDP+ generates a network credential. The generated network credential typically differs from the network credential previously generated when the ICCID was used in conjunction with the downloaded profile, for example due to the use of a random number generator during network credential generation. However, it is important that an existing network credential previously used for profile download is not reused, but rather a new network credential is generated.

[0054] The profile server SMDP+ generates profile credentials.

[0055] Authentication is performed via the ES9+ channel between the profile server SMDP+ and the esim device. Notification of the connection to the service provider is done via the ES2+ channel.

[0056] The profile server SMDP+ generates a profile package. The profile package contains the ICCID, profile structure, and generated profile credentials. The profile server generates a bound profile package (Bound ProfilePackage) from the profile package.

[0057] SMDP+ downloads the bound profile package to the eUICC hosted in the ESIM device via channel ES8+ using the newly generated network credentials.

[0058] Cited prior art documents

[0059] [1][SGP.22 V2.2.2] GSMA SGP.22 - SGP.22 RSP Technical Specification, Version 2.2.2, June 5, 2020 (2020-06-05)

[0060] [2][PP],SIM Alliance, eUICC Profile Package: Interoperable FormatTechnical Specification, Version 2.3, October 2019

Claims

1. A method for providing a profile package for downloading from a profile server (SMDP+) to an eUICC hosted in a mobile device, the method comprising the following steps at the profile server (SMDP+): a) receiving a profile download command including a profile type or profile number (ICCID) from a connection service provider server (CSP); b) generating a profile package comprising profile credentials and a profile number (ICCID) assigned taking into account the received profile type or the received profile number (ICCID); c) providing the generated configuration file package for downloading to the eUICC; It is characterized by the following steps: a1) identifying the received or assigned Profile ID (ICCID) as linked to the Profile already downloaded to the eUICC; a2) receiving a notification from the connectivity service provider server (CSP) of a profile number (ICCID) allowing release of the link, the release being allowed due to the satisfaction of release criteria; a3) Release link profile number (ICCID); a4) generating network access credentials to be used to download the generated configuration profile package to the eUICC.

2. The method according to claim 1, The release criteria include one or more of the following: the profile number (ICCID) is not used in any authentication request received at the connectivity service provider server (CSP) from any mobile device or eUICC for a predetermined period of time or longer; The profile number (ICCID) is intended to be used for two or more copies of the same profile, the two or more copies being intended to remain available in parallel on two or more different mobile devices or / and on two or more different eUICCs.

3. The method according to claim 1 or 2, wherein the network access credentials include one or more of the following: OTA Key NAA parameters AKA parameters for MILENAGE or TUAK or a proprietary authentication algorithm.

4. The method according to any one of claims 1 to 3, wherein the network access credential is different from the network access credential generated for the profile that has been downloaded to the eUICC.

5. The method according to any one of claims 1 to 4, in, A connectivity provider is one or more of the following: Mobile Network Provider (MNO) Mobile Virtual Network Provider (MVNO).

6. The method according to any one of claims 1 to 5, wherein step a2) comprises the following sub-steps: a2-1) sending a download command response to the connection service provider server (CSP), notifying the connection service provider server (CSP) of the linked configuration file number (ICCID), and requesting the connection service provider server (CSP) to release the linked configuration file number (ICCID); a2-2) receiving a confirmation command from the connection service provider server (CSP) allowing the release of the linked profile number (ICCID); a2-3) releasing the linked profile number (ICCID) at the profile server (SMDP+).

7. The method according to any one of claims 1 to 6, wherein the profile already downloaded to the eUICC includes a profile identifier (IMSI), wherein the profile package of step b) includes the same profile identifier (IMSI) as the profile already downloaded to the eUICC.

8. The method according to any one of claims 1 to 7, wherein the configuration file download command of step a) further comprises an eUICC hardware identifier (EID) of the eUICC to which the configuration file package is to be downloaded.

9. A method for downloading a configuration file to an eUICC, The following steps are involved: - providing the profile package on a profile server (SMDP+) by a method according to any one of claims 1 to 8; - Here the provided profile package is downloaded from the Profile Server (SMDP+) to the eUICC using the generated Network Access Credentials.

10. The method according to any one of claims 1 to 9, wherein the generated network access credentials have not been used for configuration file downloading, in particular have not been used for configuration file downloading before the downloading according to claim 9.

11. A profile server (SMDP+) implemented to perform the method according to any one of claims 1 to 10.

Images