Pre-personalized eSIM to support mass eSIM delivery

By pre-generating and distributing basic information of eSIM, using three-stage process to personalize the configuration when the mobile device is activated, the bottleneck problem of activation process caused by eSIM distribution in the prior art is solved, and the activation efficiency of mobile devices and users are improved Satisfaction.

CN113766485BActive Publication Date: 2024-11-08APPLE INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202111047647.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2015-11-20
Filing Date
2016-05-10
Publication Date
2024-11-08
Estimated Expiration
2036-05-10

AI Technical Summary

Technical Problem

Existing eSIM distribution technologies can lead to bottlenecks in the activation process during the massive rollout of mobile devices, reducing end-user satisfaction, especially when eSIMs need to be generated and distributed quickly.

Method used

Pre-generate basic information of eSIM and distribute it when the mobile device is activated, rather than when it is activated, through a three-stage process: the first stage generates a challenge at the manufacturer, and the second stage configures it at the distribution center Regenerating and allocation of files, the third stage directly retrieves pre-personalized eSIM when the user boots up.

Benefits of technology

Improves the efficiency of the mobile device activation process, especially in high demand, reduces processing overhead and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113766485B_ABST
    Figure CN113766485B_ABST
Patent Text Reader

Abstract

The present disclosure relates to pre-personalized eSIMs to support large-scale eSIM delivery. Representative embodiments described herein set forth techniques for optimizing large-scale delivery of electronic subscriber identity modules (eSIMs) to mobile devices. Specifically, rather than generating and allocating an eSIM when a mobile device is activated (which may require significant processing overhead), an eSIM is pre-generated with a basic set of information and then assigned to a mobile device when the device is activated. This can provide significant advantages over traditional methods of generating and allocating eSIMs during mobile device activation, particularly when new mobile devices (e.g., smartphones, tablets, etc.) are being launched and a large number of eSIM allocation requests need to be efficiently satisfied.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of invention patent application No. 201680028342.1, which has an international filing date of May 10, 2016 and enters the Chinese national phase and is entitled “Pre-personalized eSIM to support large-scale eSIM delivery”. Technical Field

[0002] The described embodiments propose a technique for optimizing the manner in which electronic subscriber identity modules (eSIMs) are provisioned to mobile devices in order to facilitate robust, large-scale delivery of eSIMs to mobile devices. Background Art

[0003] Many mobile devices are configured to utilize a universal integrated circuit card (UICC) that enables the mobile device to access services provided by a mobile network operator (MNO). Specifically, each UICC includes at least a microprocessor and a read-only memory (ROM), wherein the ROM is configured to store an MNO profile that the mobile device can utilize to register with and interact with the MNO. Typically, the UICC takes the form of a small removable card (commonly referred to as a subscriber identity module (SIM) card) that is configured to be inserted into a UICC receiving area included in the mobile device. However, in recent implementations, the UICC is embedded directly into the system board of the mobile device. These electronic / embedded UICCs (eUICCs) can provide advantages over traditional SIM cards, such as an eUICC that can store several MNO profiles—referred to herein as an electronic subscriber identity module (eSIM)—and can eliminate the need to include a UICC receiving area in the mobile device. In addition, the eSIM can be remotely provisioned to the mobile device, thereby greatly improving flexibility when users purchase mobile devices, travel to different countries, move their phone numbers to different MNOs, and the like.

[0004] Despite the various advantages provided by eSIMs, certain issues exist that have not been addressed. For example, one issue relates to the large-scale distribution of eSIMs, such as during a product launch of a mobile device that is sold in large volumes. Specifically, existing eSIM distribution techniques involve generating an eSIM in response to receiving an activation request from a mobile device (e.g., during the first power-up of the mobile device), and delivering the eSIM to the mobile device. Importantly, this process can create a bottleneck that slows down the mobile device activation process and reduces overall end-user satisfaction. Summary of the invention

[0005] Representative embodiments described herein describe techniques for optimizing the mass delivery of eSIMs to mobile devices. Specifically, rather than generating and allocating an eSIM when the mobile device is activated (which may require significant processing overhead), an eSIM is pre-generated with a basic set of information and assigned to the mobile device when the device is later activated. This can provide significant advantages over traditional methods of generating and allocating eSIMs during mobile device activation, particularly when new mobile devices (e.g., smartphones, tablets, etc.) are being launched and a large number of eSIM allocation requests need to be efficiently satisfied. According to some embodiments, these techniques can be divided into three different stages, which are described in more detail herein.

[0006] The invention summary is provided only to summarize some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described above are only examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects and advantages of the subject matter described herein will become apparent from the following detailed description, drawings and claims.

[0007] Other aspects and advantages of the embodiments described herein will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate by way of example the principles of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The included drawings are for illustrative purposes and only provide examples of possible structures and arrangements of the disclosed apparatus and methods of the present invention for providing wireless computing devices. These drawings in no way limit any changes in form and detail that may be made to the embodiments by those skilled in the art without departing from the spirit and scope of the embodiments. The embodiments will be more easily understood through the following detailed description in conjunction with the accompanying drawings, in which like reference numerals represent similar structural elements.

[0009] Figure 1 Shown is a block diagram of different components of a system configured to implement the various techniques described herein, according to some embodiments.

[0010] Figure 2 According to some embodiments, Figure 1 A block diagram of a more detailed view of specific components of the system.

[0011] Figure 3 A sequence diagram of a method performed between a mobile device and a manufacturer of the mobile device according to some embodiments is shown.

[0012] Figure 4A sequence diagram of a method performed between a distribution center for mobile devices and a manufacturer of mobile devices according to some embodiments is shown.

[0013] Figure 5 A sequence diagram of a method performed between a mobile device and a distribution center for the mobile device according to some embodiments is shown.

[0014] Figure 6 A sequence diagram of a method performed between a mobile device, a distribution center for the mobile device, and a manufacturer of the mobile device according to some embodiments is shown.

[0015] Figure 7 A detailed view of a computing device that can be used to implement the various components described herein is shown according to some embodiments. DETAILED DESCRIPTION

[0016] Representative applications of the apparatus and methods according to the embodiments described in the present invention are provided in this section. These examples are provided only to add context and to help understand the embodiments. It will therefore be apparent to those skilled in the art that the embodiments described in the present invention may be implemented without some or all of these specific details. In other cases, well-known process steps are not described in detail to avoid unnecessarily obscuring the embodiments described in the present invention. Other applications are also possible, so that the following examples should not be considered restrictive.

[0017] According to various embodiments described herein, the terms "wireless communication device", "wireless device", "mobile device", "mobile station" and "user equipment (UE)" may be used interchangeably herein to describe one or more common consumer electronic devices that may be capable of performing the processes associated with various embodiments of the present disclosure. According to various specific implementations, any of these consumer electronic devices may relate to: a cellular phone or smartphone, a tablet computer, a laptop computer, a notebook computer, a personal computer, a netbook computer, a media player device, an e-book device, Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which wireless communication capabilities may include communication via one or more wireless communication protocols, which wireless communication protocols, such as protocols used to communicate on the following networks: wireless wide area network (WWAN), wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), near field communication (NFC), cellular wireless networks, fourth generation (4G) LTE, advanced LTE (LTE-A), and / or 5G or other currently or future developed advanced cellular wireless networks.

[0018] In some embodiments, the wireless communication device may also operate as part of a wireless communication system, which may include a group of client devices, which may also be referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP), such as part of a WLAN, and / or interconnected to each other, such as part of a WPAN and / or "ad hoc" wireless network. In some embodiments, a client device may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless local area network communication protocol). In some embodiments, the WLAN technology may include a Wi-Fi (or more generally, a WLAN) wireless communication subsystem or radio component, which Wi-Fi radio equipment may implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other existing or future developed IEEE 802.11 technologies.

[0019] In addition, it should be understood that the UE described herein may be configured as a multi-mode wireless communication device that is also capable of communicating via different third generation (3G) and / or second generation (2G) RATs. In these cases, the multi-mode UE may be configured to prefer attaching to an LTE network that provides faster data rate throughput over other 3G legacy networks that provide lower data rate throughput. For example, in some specific implementations, the multi-mode UE may be configured to fall back to a 3G legacy network, such as an evolved high speed packet access (HSPA+) network, or a code division multiple access (CDMA) 2000 evolution-data only (EV-DO) network when LTE and LTE-A networks are otherwise unavailable.

[0020] Representative embodiments described herein set forth techniques for optimizing the mass delivery of eSIMs to mobile devices. According to some embodiments, an eSIM is pre-generated with a basic set of information (e.g., during or after the manufacturing phase of a mobile device) and is later assigned to a mobile device when the device is activated. This can provide significant advantages over conventional methods of generating and assigning eSIMs during mobile device activation, particularly when new mobile devices are being launched and a large number of eSIM assignment requests need to be efficiently satisfied. According to some embodiments, these techniques can be divided into three different stages, which are described in more detail below.

[0021] The first stage occurs when the mobile device is manufactured (e.g., at an Original Equipment Manufacturer (OEM)) and involves a "factory broker" requesting that an eUICC included in the mobile device generate an eSIM that will subsequently be used to pre-personalize the mobile device. In accordance with the techniques described herein, the Factory Broker, as well as other entities associated with the OEM, may be implemented by the OEM itself, or may be separate from the OEM (e.g., a third-party service). It should be noted that as the mobile device is in (or moving in and out of) manufacturing at the OEM, the type of mobile network operator (MNO) / eSIM that will ultimately be utilized by the mobile device remains unknown as several factors may come into play in the regions where the mobile device is ultimately sold and used. To address this uncertainty, special values ​​are assigned to the MNO / eSIM type fields in the Profile Request Blob to indicate that the actual assignment of these fields will occur at a later time. The following is a description of the factory broker and other entities associated with the OEM in accordance with the techniques described herein. Figure 3 Describe a more detailed breakdown of the individual steps of this first phase.

[0022] The second phase occurs after identification of the MNO (also referred to herein as the "target operator") to which the mobile device will be subscribed. The second phase may be initiated, for example, in response to a notification that the mobile device is being shipped and will soon be delivered to a retailer, end user, etc. According to some embodiments, the shipping notification includes information indicating the MNO to which the mobile device will be subscribed, and a type of eSIM that the mobile device will utilize. In response to the shipping notification, a "client profile agent" that has a layer 2 (L2) security level in the context of the technology described herein and is implemented at a distribution center that handles the delivery of the mobile device acts as an agent for the L2 component of the eUICC included in the mobile device. Specifically, the client profile agent regenerates a profile request blob (similar to the profile request blob established in the first phase) and assigns a value to the MNO / eSIM type field based on the information contained in the shipping notification. The client configuration agent may also be configured to generate a new challenge to replace the challenge generated in the first phase (otherwise, the uniqueness of the challenge between all L2 components needs to be guaranteed, but this may be problematic).

[0023] Next, the client configuration agent may be configured to cryptographically sign the profile request blob using a private key known to the client profile agent. It should be noted that the profile request blob will continue to have an L1 signature associated with the eUICC included in the mobile device because when ultimately delivered to the mobile device, the eSIM will be in an encrypted form and the eUICC will need to decrypt the encrypted eSIM in order to install the eSIM and consume services provided by the MNO. Next, the profile request blob is sent to the "server agent" using the "personalizeProfile()" command. From the perspective of the server agent, the technology described herein is no different from existing solutions, which can be beneficial because traditionally supported forms are implemented and do not require significant modifications. More specifically, the server agent is configured to return a batch descriptor to the client profile agent and personalize the eSIM for the mobile device. The client profile agent then creates a new batch descriptor in which the challenge is generated by the eUICC in the first phase and is used when the eUICC requests delivery of the eSIM at a subsequent time. The following is combined with Figure 4 A more detailed breakdown of the individual steps of this second phase is described.

[0024] Finally, the third stage occurs when the end user of the mobile device turns on the mobile device. More specifically, when the mobile device is turned on (or when the mobile device is turned on and detects that no eSIM is installed on the eUICC included in the mobile device), the mobile device issues a "getProfileOptions()" command to the eUICC to identify the available options for eSIM operation. Since the eSIM is pre-personalized for the mobile device through the first and second stages described above, the response to the "getProfileOptions()" command will include a valid batch descriptor, where the mobile device does not need to issue a "personalizeProfile()" command (as in conventional methods). Instead, the mobile device can use the information in the included descriptor to directly retrieve the pre-personalized eSIM using the "getProfile()" command. The following is combined with Figure 5 Describe a more detailed breakdown of the individual steps of this third phase.

[0025] Additional embodiments are described herein that enable pre-personalization of two or more eSIMs for a mobile device in a manner that enables a user to select from different available MNOs when acquiring a mobile device for use. As previously described, when a mobile device is manufactured, the available information about the region in which the mobile device will ultimately be utilized is limited. However, when the mobile device is distributed after manufacturing is complete, more detailed information is available, for example, if the mobile device is being shipped to the United States for sale, the mobile device is likely to consume services provided by T-Mobile, Sprint, ATT, or Verizon. At this point, the aforementioned embodiments can be modified to pre-personalize two or more eSIMs for a mobile device so that a user can select from different MNOs after purchasing the mobile device. Note that an MNO may represent a mobile network operator that implements its own infrastructure to provide services to a mobile device. Alternatively, an MNO may represent a "virtual" mobile network operator that uses the infrastructure of another MNO to provide services. Therefore, the efficiency provided by the aforementioned embodiments remains unchanged because the pre-personalized eSIMs are readily available for the mobile device. In addition, unused (i.e., unselected) pre-personalized eSIMs can be separated from the mobile device and recycled for future use by other mobile devices, thereby further improving efficiency. The following is combined with Figure 6 More detailed details of the various steps of the multi-eSIM method are described.

[0026] Therefore, the techniques described herein provide a mechanism for optimizing the large-scale delivery of eSIMs to mobile devices. A more detailed discussion of these techniques is shown below and in conjunction with Figure 1-7 A description is provided that shows detailed illustrations of systems and methods that can be used to implement these techniques.

[0027] Figure 1 1 shows a block diagram of different components of a system 100 configured to implement the various techniques described herein, according to some embodiments. More specifically, Figure 1 A high-level overview of a system 100 is shown, which includes a mobile device 102 and a set of base stations 112 managed by different MNOs 114. Figure 1 , each mobile device 102 may represent a mobile computing device (e.g., of or ), and base stations 112 may represent different radio towers configured to enable mobile device 102 and MNO 114 to communicate with each other. According to some embodiments, MNO 114 may represent different wireless service providers for providing specific services (e.g., voice and data) to which mobile device 102 may subscribe. Figure 1As shown, the system 100 may also include a mobile device manufacturer 116, which may represent, for example, an original manufacturer of the mobile device 102. In addition, the system 100 may include a mobile device distribution center 118, which may represent, for example, an inventory and shipping center that facilitates delivery of the mobile devices 102 from the mobile device manufacturer 116 to retailers, end users, etc. As described in more detail herein, the mobile device manufacturer 116 and the mobile device distribution center 118 may be configured to implement different technologies that enable efficient and large-scale delivery of eSIMs to the mobile devices 102.

[0028] like Figure 1 As shown, each mobile device 102 may include a processor 104 (sometimes referred to as an "integrated circuit"), a memory 106, a secure element 108, and a baseband component 110 (sometimes referred to as an "integrated circuit", "interface circuit" or "communication device"). These components work together to enable the mobile device 102 to provide useful features to the user, such as local computing, location-based services, and Internet connectivity. According to some embodiments, the secure element 108 may represent a removable universal integrated circuit card (UICC) or an embedded / electronic UICC (eUICC). As described in more detail below, the secure element 108 may be configured to store multiple electronic subscriber identity modules (eSIMs) for accessing different MNOs 114 through the base station 112. For example, the secure element 108 of the mobile device 102 may be configured to store an eSIM for each MNO 114 to which the mobile device 102 is subscribed. Although Figure 1 Not shown, the mobile device 102 may also be configured to include a receiving area for a removable UICC that manages one or more SIMs.

[0029] Figure 2 According to some embodiments, Figure 1 A block diagram of a more detailed view 200 of certain components of the mobile device 102 in FIG. Figure 2 As shown, the processor 104 in conjunction with the memory 106 may implement a main operating system (OS) 202 configured to execute applications (e.g., native OS applications and user applications). In addition, the processor 104 in conjunction with the memory 106 may be configured to implement a client 203 configured to facilitate communication between the secure element 108 and entities external to the mobile device 102 (e.g., the mobile device manufacturer 116 and the mobile device distribution center 118), which enables the various techniques described herein.

[0030] like Figure 2 As shown, the secure element 108 may be configured to implement hardware resources (e.g., processor and memory) configured to manage the secure element 108. Figure 2108). The secure element 108 may also be configured to implement a locker (L1) 207, an agent (L2) 208, and a client (L3) 209, which represent different entities configured to facilitate the techniques described herein. For example, the locker (L1) 207 may be configured to perform cryptographic functions (e.g., encryption, decryption, digital signature, etc.) on an eSIM received / managed by the secure element 108. The agent (L2) 208 may be configured to perform techniques for facilitating the uniqueness of an eSIM within the system 100, for example, by preventing the cloning of an eSIM in an improper or authorized manner. When the secure element 108 receives an eSIM from an external entity, the client (L3) 209 may be configured to perform identity, trust, and authorization functions to enhance overall security.

[0031] As described above, the secure element 108 can be configured to manage various eSIMs. Figure 2 108 (also referred to herein as a “profile”). Specifically, the management functions may include activating the eSIM 210 within the secure element 108 and providing access to the eSIM 210 to the baseband component 110. Figure 2 1 , but each eSIM 210 may be associated with a unique identifier (ID) and may include a number of applets that define the manner in which the eSIM 210 operates. For example, one or more of the applets, when implemented by the baseband component 110 and the secure element 108, may be configured to enable the mobile device 102 to communicate with the MNO 114 and provide useful features (e.g., phone calls and the Internet) to a user of the mobile device 102.

[0032] Likewise Figure 2 As shown, the baseband component 110 of the mobile device 102 may include a baseband OS 214 that is configured to manage the hardware resources (e.g., processor, memory, different radio components, etc.) of the baseband component 110. According to one embodiment, the baseband component 110 may implement a manager ( Figure 2 The manager can also be configured to implement various services ( Figure 2 210), such as a collection of software modules instantiated by various applets of activated eSIMs 210 managed by secure element 108. For example, the service may be configured to manage different connections between mobile device 102 and MNO 114 depending on the different eSIMs 210 that are activated.

[0033] Figure 2Further shown in FIG. 1 is a more detailed breakdown of the mobile device manufacturer 116 and the mobile device distribution center 118. According to some embodiments, the mobile device manufacturer 116 can be configured to implement a locker (L1) 230, a proxy (L2) 232, and an intermediary (L3) 234, which are configured to facilitate implementation of the techniques as described in more detail herein. According to some embodiments, the mobile device distribution center 118 can be configured to implement a proxy (L2) 240 and an intermediary (L3) 242, which are further configured to facilitate implementation of the techniques as described in more detail herein.

[0034] Figure 3 A sequence diagram of a method 300 performed between a mobile device 102 (including a secure element 108) and a mobile device manufacturer 116 according to some embodiments is shown. Specifically, the method 300 represents the first of three phases described herein. As previously described, the first phase occurs when the mobile device 102 is being manufactured by the mobile device manufacturer 116, and involves the intermediary (L3) 234 requesting the secure element 108 included in the mobile device 102 to generate a challenge that will subsequently be used to pre-personalize the eSIM / profile 210 for the mobile device 102. It should be noted that as the mobile device 102 is in (or is in and out of) the manufacturing phase at the mobile device manufacturer 116, the MNO 114 / eSIM type / profile 210 that will ultimately be utilized by the mobile device 102 remains unknown because several factors may come into play in the region where the mobile device 102 is ultimately sold and utilized. To address this uncertainty, special values ​​are assigned to the MNO 114 / eSIM type fields in the "Profile Request Blob" to indicate that the actual assignment of these fields will occur at a later time. The following in conjunction with Figure 3 The above aspects are described in more detail.

[0035] like Figure 3As shown, a first step 302 involves the client 203 issuing a "getIdentityMap(L3Current, L3Next)" command to the client (L3) 209. A next step 304 involves the client (L3) 209 (in response to the first step 302) providing the signed identity map to the client 203. A next step 306 involves the client 203 issuing a "getProfileOptions(SignedIdentityMap)" command to the broker (L3) 234. A next step 308 involves the broker (L3) 234 (in response to step 306) providing profile options to the client 203. A next step 310 involves the client 203 issuing a "createSession(ProfileOption)" command to the proxy (L2) 208. A next step 312 involves the proxy (L2) 208 (in response to step 310) providing a session request to the client 203. The next step 314 involves the client 203 issuing an "InitializeSession(sessionRequest)" command to the broker (L3) 234. The next step 316 involves the broker (L3) 234 (in response to step 314) executing a "verifySession()" command. The next step 318 involves the broker (L3) 234 issuing a "verifySession(SessionRequest)" command to the proxy (L2) 232. The next step 320 involves the proxy (L2) 232 (in response to step 318) providing the broker (L3) 234 with a signed session response. The next step 322 involves the broker (L3) 234 providing the session response to the client 203. The next step 324 involves the client 203 issuing a "prepareProfileRequest(sessionResponse)" command to the proxy (L2) 208. The next step 326 involves the agent (L2) 208 (in response to step 324) executing a "verifySession(sessionResponse)" command. The next step 328 involves the agent (L2) 208 (in response to steps 324 and 326) executing a "createChallenge(sessionResponse)" command. The next step 330 involves the agent (L2) 208 providing the profile L2 request blob to the client (L3) 209. The next step 332 involves the client (L3) 209 executing a "createL3ProfileRequestBlob()" command to generate a profile L3 request blob. The next step 334 involves the client (L3) 209 providing the profile L2 request blob and the profile L3 request blob to the client 203.The next step 336 involves the client 203 issuing a "personalizeProfile(ProfileL2RequestBlob, ProfileL3RequestBlob)" command to the intermediary (L3) 234. The next step 338 involves the intermediary (L3) 234 (in response to step 336) executing a "verifyRequest()" command. The next step 340 involves the intermediary (L3) 234 issuing a "personalizeProfile(ProfileL2RequestBlob)" command to the agent (L2) 232. The next step 342 involves the agent (L2) 232 (in response to step 340) executing the "verifyRequest()" command. The next step 344 involves the agent (L2) 232 indicating an "ErrorCodeProfilePostponed" message to the client 203. At the final step 346, the mobile device manufacturer 116 provides a challenge to the mobile device distribution center 118, which is then used to perform the following combinations separately. Figure 4 and Figure 5 The second and third stages are described.

[0036] Figure 4 A sequence diagram of a method 400 performed between a mobile device distribution center 118 and a mobile device manufacturer 116 according to some embodiments is shown. Specifically, the method 400 represents the second phase of the three phases described herein. As previously described, the second phase begins after the identification of the MNO 114 to which the mobile device 102 will be subscribed. The second phase may begin, for example, in response to a notification that the mobile device 102 is being shipped and will soon be delivered to a retailer, end user, etc. According to some embodiments, the shipping notification includes information indicating the MNO 114 to which the mobile device will be subscribed, and a type of eSIM / profile 210 that the mobile device 102 will utilize. In response to the shipping notification, the agent (L2) 240 (associated with the mobile device distribution center 118) acts as a proxy for the agent (L2) 208 associated with the secure element 108 of the mobile device 102, and performs the following in conjunction with Figure 4 A series of specific operations are described in more detail.

[0037] like Figure 4As shown, a first step 402 involves the agent (L3) 242 issuing a "prepareProfileRequest(DeviceUniqueID)" command to the agent (L2) 240. A next step 404 involves the agent (L2) 240 (in response to step 402) executing a "createChallenge(DeviceUniqueID)" command. A next step 406 involves the agent (L2) 240 providing a profile L2 request blob to the agent (L3) 242. A next step 408 involves the agent (L3) 242 executing a "createL3ProfileRequestBlob()" command. A next step 410 involves the agent (L3) 242 issuing a "personalizeProfile(ProfileL2RequestBlob, ProfileL3RequestBlob)" command to the agent (L3) 234. A next step 412 involves the agent (L3) 234 (in response to step 410) executing a "verifyRequest()" command. The next step 414 involves the broker (L3) 234 issuing a "personalizeProfile(ProfileL2RequestBlob)" command to the agent (L2) 232. The next step 416 involves the agent (L2) 232 (in response to step 414) executing a "verifyRequest()" command. The next step 418 involves the agent (L2) 232 (in response to steps 414 and 416) executing a "checkOutProfile()" command. The next step 420 involves the agent (L2) 232 providing the batch descriptor to the broker (L3) 234. The next step 422 involves the broker (L3) 234 executing a "createL3Owner()" command to establish the L3 owner. The next step 424 involves the broker (L3) 234 providing the batch descriptor and the L3 owner to the broker (L3) 242. The next step 426 involves the agent (L2) 232 issuing a "personalizeProfile(ProfileRequestBlob):Profile" command to the locker (L1) 230. The next step 428 involves the broker (L3) 242 issuing a "processBatchDescriptor(BatchDescriptor)" command to the agent (L2) 240. The next step 430 involves the agent (L2) 240 (in response to step 428) executing a "verifyChallenge()" command. In a final step 432, the agent (L2) 240 indicates to the broker (L3) 242 that the profile has been accepted.

[0038] Figure 5A sequence diagram of a method 500 performed between a mobile device 102 (including a secure element 108) and a mobile device distribution center 118 according to some embodiments is shown. Specifically, the method 500 represents the third stage of the three stages described herein. As previously described, the third stage begins when an end user of the mobile device 102 (e.g., after obtaining the mobile device 102) turns on the mobile device 102. Figure 5 Describe a more detailed breakdown of the individual steps of this third phase.

[0039] like Figure 5As shown, a first step 502 involves the client 203 issuing a "getIdentityMap(L3Current, L3Next)" command to the client (L3) 209. A next step 504 involves the client (L3) 209 (in response to step 502) providing the signed identity map to the client 203. A next step 506 involves the client 203 issuing a "getProfileOptions(SignedIdentityMap)" command to the broker (L3) 242. A next step 508 involves the broker (L3) 242 (in response to step 506) providing the profile options to the client 203. A next step 510 involves the client 203 (in response to receiving the profile options at step 508) executing a "processL3Owner()" command. A next step 512 involves the mobile device distribution center 118 receiving a batch descriptor for the mobile device 102. A next step 514 involves the client 203 issuing a "processBatchDescriptor(BatchDescriptor)" command to the proxy (L2) 208. The next step 516 involves the proxy (L2) 208 (in response to step 514) executing a "verifyChallenge()" command. The next step 518 involves the proxy (L2) 208 indicating to the client 203 that the profile has been accepted. The next step 520 involves the client 203 issuing a "getProfile(BatchDescriptorID)" command to the broker (L3) 242. The next step 522 involves the transfer of profile ownership, thereby deleting the challenge. The next step 524 involves the broker (L3) 242 providing the profile to the client 203. The next step 526 involves the client 203 issuing an "installProfile(Profile, ProfileHash)" command to the locker (L1) 207. The next step 528 involves the locker (L1) 207 indicating to the client 203 the result of installing the profile (e.g., success, failure, etc.). The next step 530 involves the client 203 issuing an "ackProfileOperation(ProfileOperationResult)" command to the broker (L3) 242 to indicate the result of installing the profile at the mobile device 102. The final step 532 involves the broker (L3) 242 issuing an "ackProfileOperation(ProfileOperationResult)" command to the proxy (L2) 240 to indicate the result of installing the profile at the mobile device 102.

[0040] Figure 61 shows a sequence diagram of a method 600 for pre-personalizing two or more eSIMs for a mobile device 102 according to some embodiments. Figure 6 As shown, the method involves the mobile device 102, the mobile device distribution center 118, and the mobile device manufacturer 116, and begins at step 602, where the mobile device manufacturer 116 queries the mobile device 102 for an L2 challenge. At step 604, the mobile device 102 generates an L2 challenge and provides it to the mobile device manufacturer 116. At step 606, the mobile device manufacturer 116 receives the L2 challenge from the mobile device 102. Note that steps 602 to 606 represent the L2 challenge described in more detail above. Figure 3 A global view of the steps.

[0041] At step 608, the mobile device manufacturer 116 identifies the region to which the mobile device 102 is being shipped. For example, this may occur when deciding to ship the manufactured mobile device 102 to a particular country or region for sale. At step 610, the mobile device manufacturer 116 provides the L2 challenge to the mobile device distribution center 118. At step 612, the mobile device distribution center 118 pre-personalizes two or more eSIMs for the mobile device 102 based on the L2 challenge (and the MNOs in the region). At step 614, the mobile device distribution center 118 provides the two or more eSIMs as a package to the mobile device 102. Note that steps 608 to 614 represent the steps described in more detail above. Figure 4 However, as described in step 612, pre-personalization may involve two or more eSIMs to enable the user to choose from available different MNOs.

[0042] At step 616, the mobile device 102 receives a selection of an eSIM included in the package. This can occur at the mobile device 102, for example, by presenting a list of eSIMs included in the package and receiving a selection of a particular eSIM. At step 618, the mobile device 102 installs the selected eSIM. At step 620, the mobile device 102 indicates the selected eSIM to the mobile device distribution center 118. According to some embodiments, the mobile device 102 may be configured to retain the L2 challenge to prevent potential replay attacks that may occur offline. In addition, retraining the L2 challenge ensures that when the mobile device 102 generates additional L2 challenges at a subsequent time, the uniqueness remains unchanged. Note that steps 616 to 620 represent the steps described in detail above. Figure 5 However, these steps involve enabling selection of two or more eSIMs included in an eSIM package and indicating the selection to the mobile device distribution center 118.

[0043] Finally, at step 622, the mobile device distribution center 118 depersonalizes and recycles the unselected eSIMs in the package. For example, the mobile device distribution center 118 can be configured to return the unselected eSIMs to a pool of eSIMs that can then be pre-personalized for other mobile devices 102.

[0044] Figure 7 Detailed view of a computing device 700 that can be used to implement various components described herein according to some embodiments is shown. Specifically, the detailed view shows various components that can be included in the mobile device 102, entities associated with the mobile device manufacturer 116 / mobile device distribution center 118, etc. Figure 1 As shown. Figure 7 As shown, the computing device 700 may include a processor 702 (sometimes referred to as an "integrated circuit") representing a microprocessor or controller for controlling the overall operation of the computing device 700. The computing device 700 may also include a user input device 708 that allows a user of the computing device 700 to interact with the computing device 700. For example, the user input device 708 may take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual / image capture input interfaces, input in the form of sensor data, etc. Further, the computing device 700 may include a display 710 (screen display) that can be controlled by the processor 702 to display information to the user. The data bus 716 may facilitate data transmission between at least the storage device 740, the processor 702, and the controller 713. The controller 713 can be used to interact with and control different devices through the device control bus 714. The computing device 700 may also include a network / bus interface 711 (sometimes referred to as an "integrated circuit", "interface circuit" or "communication device") coupled to the data link 712. In the case of a wireless connection, the network / bus interface 711 may include a wireless transceiver.

[0045] The computing device 700 also includes a storage device 740, which may include a single disk or multiple disks (e.g., a hard drive) and a storage management module that manages one or more partitions within the storage device 740. In some embodiments, the storage device 740 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 700 may also include a random access memory (RAM) 720 and a read-only memory (ROM) 722. The ROM 722 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 720 may provide volatile data storage and store instructions related to the operation of the computing device 700. The computing device 700 may also include a secure element 750, which may represent a secure element. Figure 1 to Figure 2 The security element 108 is shown in FIG. 1 and described in detail herein.

[0046] The various aspects, embodiments, implementations or features of the embodiments may be used individually or in any combination. The various aspects of the embodiments may be implemented by software, hardware, or a combination of hardware and software. The embodiments may also be embodied as computer readable code on a computer readable medium. A computer readable medium is any data storage device that can store data that can then be read by a computer system. Examples of the computer readable medium include read-only memory, random access memory, CD-ROM, DVD, magnetic tape, hard disk drive, solid state drive, and optical data storage device. The computer readable medium may also be distributed in a network coupled computer system so that the computer readable code is stored and executed in a distributed manner.

[0047] In some embodiments, the eSIM is provisioned to the mobile device. Specifically, the mobile device may receive a request to generate a challenge from an entity associated with a manufacturer of the mobile device, wherein the request is received when the mobile device is manufactured. The mobile device may then issue a command to an eUICC included in the mobile device to cause the eUICC to generate the challenge. Next, the mobile device may provide the challenge to the entity, wherein the challenge may be used to pre-personalize the eSIM to the mobile device before shipping the mobile device to an end user.

[0048] In another embodiment, the eSIM is supplied to the mobile device by an entity associated with the manufacturer of the mobile device. Specifically, the entity may issue a request to generate a challenge to the mobile device when the mobile device is manufactured. The entity may then receive the challenge from the mobile device. Next, the entity may provide the challenge to a distribution center, where the distribution center facilitates delivery of the mobile device to the end user.

[0049] In another embodiment, the eSIM is provisioned to the mobile device by an assigned distribution center to facilitate delivery of the mobile device to an end user. Specifically, the distribution center may receive a challenge associated with the mobile device. The distribution center may then receive a notification that the mobile device will be shipped to the end user. In addition, the distribution center may identify the MNO that provides the service to which the mobile device will be subscribed based on the notification. In addition, the distribution center may issue a request to personalize the eSIM to the mobile device according to the MNO to an entity associated with the manufacturer of the mobile device and using the challenge, wherein the eSIM is pre-personalized to the mobile device. Next, the distribution center may receive the eSIM, and the distribution center may cause the mobile device to install the eSIM into an eUICC included in the mobile device.

[0050] In addition, the distribution center may receive a batch descriptor that the eUICC uses to retrieve the eSIM when the mobile device is subsequently activated for use for the first time. For example, the batch descriptor may be created using a second challenge associated with the mobile device, and the second challenge may be stored on the mobile device. Note that the batch descriptor may include information specifying the MNO and the type of eSIM. This information may replace the temporary information with a virtual value of the MNO and the type of eSIM stored on the mobile device. Specifically, the temporary information may have been stored on the mobile device when the mobile device was manufactured.

[0051] In some embodiments, the eSIM is encrypted.

[0052] Additionally, the eUICC may be implemented on a secure element in a mobile device.

[0053] In some embodiments, the eSIM is provisioned to the mobile device. Specifically, the mobile device may receive a request to generate a challenge from an entity associated with a manufacturer of the mobile device, wherein the request is received when the mobile device is manufactured. The mobile device may then issue a command to an eUICC included in the mobile device to cause the eUICC to generate the challenge. Next, the mobile device may provide the challenge to the entity, wherein the challenge may be used to pre-personalize two or more eSIMs for the mobile device before shipping the mobile device to an end user.

[0054] In another embodiment, the eSIM is supplied to the mobile device by the assigned distribution center to facilitate the delivery of the mobile device to the end user. Specifically, the distribution center may receive a query associated with the mobile device. Then, the distribution center may receive a notification that the mobile device will be shipped to the end user. In addition, the distribution center may identify multiple MNOs that can provide services to the mobile device based on the notification. In addition, the distribution center may pre-personalize two or more eSIMs to the mobile device based on these MNOs. In addition, the distribution center may provide two or more eSIMs during the initialization of the mobile device. Next, the distribution center may identify a selected eSIM of the two or more eSIMs, wherein the selected eSIM enables one or more unselected eSIMs to be identified between the two or more eSIMs, and the distribution center may depersonalize the one or more unselected eSIMs.

[0055] Note that the distribution center may return one or more unselected eSIMs to multiple eSIMs that may be personalized for different mobile devices.

[0056] Another embodiment provides a mobile device that performs one or more of the foregoing operations.

[0057] Another embodiment provides a non-transitory computer-readable storage medium storing instructions that, when executed by a processor included in a mobile device, cause the mobile device to perform one or more of the foregoing operations.

[0058] Another embodiment provides an integrated circuit that performs one or more of the foregoing operations.

[0059] For the purpose of explanation, the foregoing description uses specific nomenclature to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that these specific details are not required to practice the embodiments. Therefore, the foregoing description of specific embodiments is presented for the purpose of illustration and description. These descriptions are not intended to be considered exhaustive or to limit the embodiments to the disclosed precise forms. It will be apparent to those of ordinary skill in the art that many modifications and variations are possible based on the above teachings.

Claims

1. A method for provisioning an electronic subscriber identity module (eSIM) to a mobile device, the method comprising, at an eSIM distribution entity: receiving, from a manufacturer of a mobile device, a cryptographic challenge generated by the mobile device in conjunction with the mobile device being manufactured; pre-personalizing one or more eSIMs for the mobile device based on the encrypted challenge; receiving a request for the one or more eSIMs from the mobile device in conjunction with the mobile device undergoing an initial setup process; providing the one or more eSIMs to the mobile device; receiving, from the mobile device, a selection of at least one of the one or more eSIMs; depersonalizing each of the one or more eSIMs that is different from the at least one eSIM to generate one or more depersonalized eSIMs; as well as The one or more depersonalized eSIMs are returned to the universal pool to be available for pre-personalization for other mobile devices.

2. The method of claim 1, wherein the initial setup process is performed in conjunction with: (1) the mobile device is being powered on for the first time after being delivered to the end user, or (2) It is detected that no eSIM is installed on the electronic universal integrated circuit card eUICC included in the mobile device.

3. The method according to claim 1, wherein: The mobile device presents a list of the one or more eSIMs, and The mobile device receives a selection of the at least one eSIM from the list of the one or more eSIMs.

4. The method according to claim 1, wherein: Each of the one or more eSIMs is encrypted based at least in part on the encryption challenge; and The mobile device possesses decryption information that can be used to decrypt any one of the one or more eSIMs. 5 . The method of claim 1 , wherein the eSIM distribution entity is located in the same location as where the mobile device is shipped for sale. 6 . The method of claim 1 , wherein a manufacturer of the mobile device provides the encrypted challenge to the eSIM distribution entity in conjunction with receiving the encrypted challenge from the mobile device.

7. At least one non-transitory computer-readable storage medium configured to store instructions that, when executed by at least one processor included in a computing device, cause the computing device to provision an electronic subscriber identity module (eSIM) to a mobile device by performing steps comprising: receiving, from a manufacturer of a mobile device, a cryptographic challenge generated by the mobile device in conjunction with the mobile device being manufactured; pre-personalizing one or more eSIMs for the mobile device based on the encrypted challenge; receiving a request for the one or more eSIMs from the mobile device in conjunction with the mobile device undergoing an initial setup process; providing the one or more eSIMs to the mobile device; receiving, from the mobile device, a selection of at least one of the one or more eSIMs; depersonalizing each of the one or more eSIMs that is different from the at least one eSIM to generate one or more depersonalized eSIMs; as well as The one or more depersonalized eSIMs are returned to the universal pool to be available for pre-personalization for other mobile devices.

8. The at least one non-transitory computer-readable storage medium of claim 7, wherein the initial setup process is performed in conjunction with: (1) the mobile device is being powered on for the first time after being delivered to the end user, or (2) It is detected that no eSIM is installed on the electronic universal integrated circuit card eUICC included in the mobile device.

9. The at least one non-transitory computer-readable storage medium of claim 7, wherein: The mobile device presents a list of the one or more eSIMs, and The mobile device receives a selection of the at least one eSIM from the list of the one or more eSIMs.

10. The at least one non-transitory computer-readable storage medium of claim 7, wherein: Each of the one or more eSIMs is encrypted based at least in part on the encryption challenge; and The mobile device possesses decryption information that can be used to decrypt any one of the one or more eSIMs.

11. The at least one non-transitory computer-readable storage medium of claim 7, wherein the computing device is located within a same location as a location to which the mobile device is shipped for sale.

12. The at least one non-transitory computer-readable storage medium of claim 7, wherein a manufacturer of the mobile device provides the encrypted challenge to the computing device in conjunction with receiving the encrypted challenge from the mobile device.

13. A computing device configured to provision an electronic subscriber identity module (eSIM) to a mobile device, the computing device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the computing device to: receiving, from a manufacturer of a mobile device, a cryptographic challenge generated by the mobile device in conjunction with the mobile device being manufactured; pre-personalizing one or more eSIMs for the mobile device based on the encrypted challenge; receiving a request for the one or more eSIMs from the mobile device in conjunction with the mobile device undergoing an initial setup process; providing the one or more eSIMs to the mobile device; receiving, from the mobile device, a selection of at least one of the one or more eSIMs; depersonalizing each of the one or more eSIMs that is different from the at least one eSIM to generate one or more depersonalized eSIMs; as well as The one or more depersonalized eSIMs are returned to the universal pool to be available for pre-personalization for other mobile devices.

14. The computing device of claim 13, wherein the initial setup process is performed in conjunction with: (1) the mobile device is being powered on for the first time after being delivered to the end user, or (2) It is detected that no eSIM is installed on the electronic universal integrated circuit card eUICC included in the mobile device.

15. The computing device of claim 13, wherein: The mobile device presents a list of the one or more eSIMs, and The mobile device receives a selection of the at least one eSIM from the list of the one or more eSIMs.

16. The computing device of claim 13, wherein: Each of the one or more eSIMs is encrypted based at least in part on the encryption challenge; and The mobile device possesses decryption information that can be used to decrypt any one of the one or more eSIMs.

17. The computing device of claim 13, wherein the computing device is located within a same location as a location to which the mobile device is shipped for sale.

Citation Information

Patent Citations

  • Binding a removable module to an access terminal

    CN103733591A

  • Methods and apparatus for delivering electronic identification components over a wireless network

    EP2448216A1

  • Methods and apparatus for large scale distribution of electronic access clients

    US20130227646A1