Providing profile packages on a profile server for download to the eUICC

Abstract

A method of providing a profile package for download from a profile server (SMDP+) to an eUICC, the method comprising releasing a link ICCID and generating a new network certificate for profile download.

Description

[Technical Field]

[0001] FIELD OF THE INVENTION The present invention relates to providing a profile server with a profile package for downloading the profile package from the profile server to an eUICC and to a profile download method. [Background technology]

[0002] Background of the Invention and Prior Art The mobile device contains at least one eUICC containing one or more profiles that enable the mobile device to authenticate itself to the mobile network to establish and carry out communication sessions (e.g., voice calls or data transmissions) on the mobile network.

[0003] Document [1] [SGP.22 V2.2.2] from the prior art, GSMA SGP.22-SGP.22 RSP Technical Specification, Version 2.2.2, 05 June 2020 (2020-06-05), relates to remote SIM provisioning, which shall download, install, enable, disable and delete profiles on an embedded Universal Integrated Circuit Card (eUICC).

[0004] To establish and execute a communication session in a mobile network under a specific profile, the profile contains a set of identifiers such as IMSI and Ki. In addition to the identifiers, the profile contains OTA keys (OTA = over the air), also called network certificates, used in conjunction with the communication between the eUICC and the OTA platform. The OTA platform is understood as an operator platform for the remote management of the eUICC and the content of available operator profiles on the eUICC. Here, an operator is understood as a mobile network operator (MNO), or a mobile virtual network operator (MVNO), or generally a company providing 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 used to download a profile to an eUICC. A profile contains content in the form of profile elements (PE). Appendix A of [2] shows a template profile package that lists the required elements of a profile package. According to [2] 9.2, a profile package contains a profile number "Integrated Circuit Card Identifier" (ICCID). According to [2] 9.5, a USIM profile package of GSM type 4G or below contains a Basic File (EF) containing the International Mobile Subscriber Identity (IMSI) and a Basic File (EF) containing a key, or in the case of an ISIM or CSIM profile package, similar Basic Files (EF) are included. A fifth-generation (5G) profile contains a Subscription Persistent Identifier (SUPI) containing the IMSI.

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

[0007] Document [1] [SGP.22 V2.2.2], in particular chapter 3.1.3 “Profile Download and Installation”, relates to the process of downloading a profile from a profile server (SM-DP+ in document [1]) to an eUICC.

[0008] Furthermore, document [1] [SGP.22 V2.2.2], in particular chapter 3.1.1 “Profile Download Initiation”, relates to the process of ordering a profile by a connectivity service provider CSP (called operator in [1], assumed to be a mobile network operator MNO) at a profile server (called SM-DP+ in [1]).

[0009] Figure 2 of this document represents Figure 9 from document [1][SGP.22 V2.2.2], chapter 3.1.1 "Profile Download Initiation". [1][SGP.22 V2.2.2], Figure 9 and the associated text in chapter 3.1.1 describe the procedure for ordering a profile by an operator at the profile server SM-DP+. In step (1), the operator sends a profile download order to the SM-DP+ over channel ES2+ with the command ES2+.DownloadProfile(EID, profile type or ICCID). The profile download command indicates the EID of the target eUICC (EID = eUICC hardware identifier) ​​and the profile type or different profile number ICCID. According to the description in [1], 3.1.1.2, step (1), given an ICCID, the SM-DP+ shall verify that this ICCID is available. If the operator commands a profile, but gives a different ICCID in the profile download command, and the SM-DP+ notices that it has assigned the ICCID to a profile already downloaded to one eUICC, then the SM-DP+ considers the ICCID unavailable and will not execute the profile download command without further action. The action to be taken is not further specified in the SGP.22 standard [1] [SGP.22 V2.2.2].

[0010] A known solution, at least nationally, to free up the ICCID of an already downloaded profile to make it available is to delete the profile from the download location on the eUICC and give a profile deletion notification from the eUICC to the SM-DP+. Upon receiving the profile deletion notification, the SM-DP+ frees up the ICCID for use, and a profile download command referencing the ICCID is authorized (provided no other restrictions exist) and can download the profile to the target eUICC indicated in the profile download command. The target eUICC can be the same or a different eUICC compared to the eUICC that deleted the profile.

[0011] Another known solution to avoid linking (locking) ICCIDs is to order a new profile containing a new identifier IMSI and assigned a new profile number ICCID. Each IMSI and ICCID of a profile ready to be used in a mobile network must be registered in the Home Location Register (HLR) of the MNO that houses the profile. The MNO charges a fee for each IMSI and ICCID registered in its HLR. Having a large number of IMSIs and ICCIDs registered in an MNO's HLR can therefore become expensive.

[0012] Even if some IMSIs or ICCIDs or IMSI / ICCID pairs are no longer in use, some IMSIs or ICCIDs or IMSI / ICCID pairs in the field are linked (locked). For example, a user may stop using an old device, including the eUICC housed in it (e.g., put the device in a drawer), and take no further action regarding the device / eUICC, in particular, not delete any profiles from the eUICC. In this situation, the IMSIs or ICCIDs or IMSI / ICCID pairs of profiles on the eUICC may, in the worst case, remain linked (locked) forever.

[0013] In another use case, a profile user who owns several mobile devices wants to use copies of their profile on several of their devices without having to delete the profile on any of the devices and without having to use several IMSIs and / or ICCIDs. However, currently, if the user wants to download the same profile a second time, the second profile download is only possible if the same profile credentials for network access are used and the profile server receives a profile deletion notification for the already downloaded profile. Summary of the Invention [Problem to be solved by the invention]

[0014] Object of the invention It is an object of the present invention to provide a flexible, efficient and secure profile download solution that can use or reuse linked (locked) profile numbers (eg, ICCIDs).

[0015] Summary of the Invention More specifically, the object of the invention is achieved by a method having the following characteristics as set forth in claim 1. Embodiments of the invention are presented in the dependent claims. [Means for solving the problem]

[0016] 1. A method of providing a profile package for download from a profile server to an eUICC housed in a mobile device, comprising: a) receiving a profile download command from a connectivity service provider server, the profile download command including a profile type or a profile number; b) generating a profile package including a profile certificate and a profile number that is assigned taking into account the received profile type or the received profile number; c) providing the generated profile package for download to the eUICC; A method comprising:

[0017] The method is: a1) identifying a received or assigned profile number as being linked to a profile already downloaded to the eUICC; a2) receiving notification from the connectivity service provider server that the link profile number is acceptable for release, where the acceptability for release is due to satisfying a release criterion, wherein preferably the connectivity service provider server verifies the release criterion at its end and notifies the profile server of the result of the verification, i.e., that the profile number is acceptable for release; a3) the profile server releasing the link profile number; a4) a profile server generating a network access certificate to be used to download the generated profile package to the eUICC; It is characterized by:

[0018] The method achieved in this way allows a link profile number to be reused for a new profile download if the link profile number satisfies the release criteria. The link profile number is a profile number that has been occupied since a profile was downloaded to an eUICC using this profile number. Due to the generation of a (new) network certificate, the eUICC and background infrastructure that previously used the same profile number to download a profile to the eUICC cannot access the new profile download process. Therefore, despite using the same profile number, confidentiality and security of the profile download are guaranteed due to the (new) generated network certificate. The method is particularly flexible and efficient, as profile numbers are released on the fly as needed.

[0019] The release criteria may include one or more of the following: (1) The profile number has not been used in any authentication request received by the connectivity service provider server from any mobile device or eUICC for a predetermined period of time or more (the period can be, for example, one year, as a non-limiting example). In this case, releasing the profile number implies ceasing to use the profile number for the profile linked before the release. Thus, the release replaces the profile number from the old profile with a new profile, and the same number of profiles (e.g., one) are assigned to the profile number before and after the release of the profile number. (2) A profile number is intended to be used for two or more copies of the same profile that are intended to be kept available in parallel on two or more different mobile devices or / and two or more different eUICCs. In this case, the released profile number may continue to be used for the profile to which it was linked before the release. Thus, releasing a profile number results in the addition of an additional profile to the same profile number.

[0020] The Network Access Certificate may contain one or more of the following: - an OTA key, - NAA parameters, - AKA parameters for MILENAGE or TUAK or a proprietary authentication algorithm. The Network Access Certificate is designed to enable secure and confidential profile download from a profile server to the eUICC over the network.

[0021] Preferably, the network access certificate is different from the network access certificate generated for the profile already downloaded to the eUICC.

[0022] Connectivity service providers - Mobile network providers (e.g. MNOs), - Mobile Virtual Network Providers (e.g., MVNOs) It may be one or more of the above.

[0023] Step a2) is a2-1) a sub-step of notifying the connectivity service provider server of a link profile number and sending a download command response to the connectivity service provider server, the download command response requesting the connectivity service provider server to release the link profile number; a2-2) receiving a confirmation command from the connectivity service provider server that the link profile number is acceptable to be released; a2-3) Substep of releasing the link profile number on the profile server; may include:

[0024] A profile already downloaded to the eUICC may include a profile identifier (e.g., IMSI), and the profile package of step b) may include the same profile identifier (e.g., IMSI) as the profile already downloaded to the eUICC. This embodiment of the invention may also reuse the profile number (e.g., ICCID) and profile identifier (e.g., IMSI), which is particularly useful when downloading the same profile to further devices of the same user. In other use cases, for example, when an expired profile number (ICCID) is to be reused, the profile identifier (e.g., IMSI) of the new use will usually be different from the profile identifier (e.g., IMSI) of the previous use.

[0025] The profile download command in step a) may further include an eUICC hardware identifier (eg, EID) of the eUICC to which the profile package should be downloaded.

[0026] To download a profile to the eUICC: - providing a profile package on a profile server according to the method described above; - downloading a provided profile package from a profile server to the eUICC using the generated network access certificate; Includes:

[0027] Preferably, the generated network access credentials have not previously been used for a profile download.

[0028] A profile server according to the present invention is implemented to perform the above-described method.

[0029] BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present invention will now be described with reference to the accompanying drawings below, in which like reference numerals refer to like parts throughout. [Brief explanation of the drawings]

[0030] [Figure 1] 10 is a diagram illustrating a profile instruction including releasing a link ICCID according to an embodiment of the present invention. [Figure 2] 1 is a diagrammatic view of a remote SIM provisioning architecture according to SGP.22 V2.2.2, FIG. 1, suitable for implementation of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0031] Detailed Description of the Invention FIG. 1 shows a diagram illustrating a profile command and sending from a profile server SMDP+ to an eUICC housed in an esim device, in this case releasing a link profile number ICCID, according to an embodiment of the present invention.

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

[0033] The profile server SMDP+ checks the profile type and assigns a profile number ICCID that conforms to the profile type to the download command. Furthermore, the profile server SMDP+ identifies that the assigned profile number ICCID is not free and is linked to a profile already resident on the eUICC.

[0034] The profile server SMDP+ sends a notification to the connectivity service provider server CSP on channel ES2+ that the assigned profile number ICCID is linked to a profile resident on the eUICC.

[0035] The connectivity service provider server CSP validates the ICCID, finds the ICCID free for release according to the release criteria and sends a notification to the profile server SMDP+ on channel ES2+ that the assigned profile number ICCID is acceptable for release.

[0036] In response to receiving notification from the connectivity service provider server CSP that the assigned profile number ICCID is acceptable for release, the profile server SMDP+ releases the profile number ICCID. Furthermore, the profile server SMDP+ generates a network certificate. The generated network certificate will typically differ from a network certificate generated when the ICCID was previously used in connection with an already downloaded profile, for example, due to the use of random number generation during the generation of the network certificate. However, it is important to generate a new network certificate if one does not already exist and it is not necessary to reuse a network certificate previously used for the profile download.

[0037] The profile server SMDP+ generates a profile certificate.

[0038] Authentication between the profile server SMDP+ and the esim device is performed over channel ES9+. Notification is made to the connectivity service provider over channel ES2+.

[0039] The profile server SMDP+ generates a profile package, which includes an ICCID, a profile structure, and a generated profile certificate. The profile server generates a combined profile package from the profile package.

[0040] The SMDP+ uses the newly generated network certificate to download the combined profile package to the eUICC housed in the esim device via the channel ES8+.

[0041] Cited prior art documents [1] [SGP.22 V2.2.2] GSMA SGP.22 - SGP.22 RSP Technical Specification, Version 2.2.2, 05 June 2020 (2020-06-05) [2] [PP], SIM Alliance, eUICC Profile Package: Interoperable Format Technical Specification, Version 2.3, October 2019

Claims

1. 1. A method of providing a profile package for download from a profile server (SMDP+) to an eUICC housed in a mobile device, comprising: a) receiving a profile download command from a connectivity service provider server (CSP) including a profile type or profile number (ICCID); b) generating a profile package including a profile certificate and a profile number (ICCID) that is assigned taking into account the received profile type or the received profile number (ICCID); c) providing the generated profile package for download to an eUICC; Including, a1) identifying the received or assigned profile number (ICCID) as being linked to a profile already downloaded to the eUICC; a2) sending a notification to the connectivity service provider server (CSP) that the profile number (ICCID) is linked to a profile resident on the eUICC, and receiving a notification from the connectivity service provider server (CSP) that the linked profile number (ICCID) is acceptable for release, where the acceptability for release is because it satisfies release criteria; a3) Releasing said linked profile number (ICCID); a4) generating a network access credential to be used to download the profile package to the eUICC; The method according to claim 1, wherein a1) to a4) can be executed as part of a) or after a) if the profile number is received in a), and can be executed after b) if the profile type is received in a).

2. The release criteria are: - the profile number (ICCID) has not been used in any authentication request received by the connectivity service provider server (CSP) from any mobile device or eUICC for more than a predetermined time; - the profile number (ICCID) is intended to be used for two or more copies of the same profile that are intended to be kept available in parallel on two or more different mobile devices or / and two or more different eUICCs; The method of claim 1 , comprising one or more of:

3. The network access credential is: - OTA key, - NAA parameters, AKA parameters for MILENAGE or TUAK or proprietary authentication algorithms The method of claim 1 , comprising one or more of:

4. The method of claim 1 , wherein the network access credential is different from a network access credential generated for the profile already downloaded to an eUICC.

5. The connectivity service provider: - Mobile Network Providers (MNOs), - Mobile Virtual Network Providers (MVNOs) The method of claim 1 , wherein the first and second electrodes are one or more of:

6. Step a2) is a2-1) sending a download command response to the connectivity service provider server (CSP), notifying the connectivity service provider server (CSP) of the linked profile number (ICCID) and requesting the connectivity service provider server (CSP) to release the linked profile number (ICCID); a2-2) receiving a confirmation command from the connectivity service provider server (CSP) that the linked profile number (ICCID) is acceptable to be released; a2-3) Releasing the linked profile number (ICCID) in the profile server (SMDP+); The method of claim 1 , comprising:

7. 2. The method of claim 1, wherein the profile already downloaded to the eUICC includes a profile identifier (IMSI), and the profile package of step b) includes the same profile identifier (IMSI) as the profile already downloaded to the eUICC.

8. The method of claim 1 , wherein the profile download instruction in step a) further includes an eUICC hardware identifier (EID) of an eUICC to which the profile package should be downloaded.

9. A method for downloading a profile to an eUICC, comprising: - providing a profile server (SMDP+) with a profile package according to the method of claim 1; - downloading the provisioned profile package from the profile server (SMDP+) to the eUICC using the network access certificate generated in a4); A method comprising:

10. A method according to any one of claims 1 to 9, wherein the network access certificate generated in a4) is not used for profile download.

11. A profile server (SMDP+) implemented to carry out the method according to any one of claims 1 to 9.

Images