Subscription service file management for esim transfer

Abstract

The described implementations set forth techniques for managing subscription service files (e.g., Customized Applications for Mobile Enhanced Logic (CAMEL) Application Part (CAP) files) for export and / or transfer of an electronic SIM (eSIM) from a source wireless device. As part of an eSIM process for transferring an eSIM, a processor of the source wireless device obtains one or more subscription service files from one or more applet asset servers that can be used to generate a version of an applet associated with the eSIM. The wireless device generates an eSIM export package that includes the eSIM and at least one of the one or more subscription service files. The processor of the source wireless device provides the eSIM export package to a target wireless device for installation of the transferred eSIM and one or more applets based on the subscription service files on an eUICC of the target wireless device.

Description

Technical Field

[0001] The described implementation scheme illustrates the technology for managing subscription service files, such as Custom Application Part (CAP) files for Mobile Network Enhancement Logic (CAMEL), for electronic SIM (eSIM) transfer between wireless devices. Background Technology

[0002] Many mobile wireless devices are configured to use a removable universal integrated circuit card (UICC), which enables the mobile wireless device to access services provided by a mobile network operator (MNO). Specifically, each UICC includes at least a microprocessor and read-only memory (ROM), which is configured to store an MNO profile that the wireless device can use to register and interact with the MNO to obtain wireless services via a cellular wireless network. The profile may also be referred to as a subscriber identity module (SIM). Typically, the UICC takes the form of a small, removable card (often called a SIM card) inserted into the UICC receiver area of ​​the mobile wireless device. In more recent implementations, the UICC is directly embedded into the system board of the wireless device as an embedded UICC (eUICC), which offers advantages over traditional removable UICCs. The eUICC may include rewritable memory that facilitates the installation, modification, and / or removal of one or more electronic SIMs (eSIMs) on the eUICC, where the eSIMs can provide new and / or different services and / or updates for accessing extended features provided by the MNO. The eUICC can store several MNO profiles (also referred to as eSIM in this document) and eliminates the need to include the UICC receiver area in the wireless device. Applets associated with the eSIM can also be installed on the eUICC based on subscription service files (such as CAP files), which are provided in the Binding Profile Package (BPP) received from the provisioning server.

[0003] Mechanisms for transferring cellular wireless service plans between wireless devices include: i) a physical transfer of the UICC (SIM card) from a source device to a target device; and ii) an electronic transfer of the eSIM from the eUICC of the source wireless device to the eSIM on the eUICC of the target wireless device. After the applet associated with the eSIM is installed on the eUICC, the process of this invention discards certain subscription service files (such as CAP files) associated with the eSIM. The absence of subscription service files (such as CAP files) associated with the eSIM's applet hinders the generation of an interoperable eSIM package for transferring the eSIM from the eUICC of the source wireless device to the eUICC of the target wireless device. A mechanism is needed for managing the eSIM's subscription service files (including CAP files) for the eSIM management process. Summary of the Invention

[0004] This application describes techniques for managing subscription service files for exporting and / or transferring electronic SIMs (eSIMs) from wireless devices. These subscription service files may include Custom Application Part (CAP) files of Mobile Network Enhancement Logic (CAMEL). Subscription service files (such as CAP files) can be used to generate applets that are installed on an embedded universal integrated circuit card (eUICC) of the wireless device along with an eSIM profile. When one or more applets associated with the wireless device's eSIM are installed on the eUICC, one or more subscription service files (such as CAP files) used to generate the one or more applets may be encrypted by the eUICC and stored locally at the wireless device and / or remotely on a network-accessible server for later retrieval when used to generate an eSIM export package for transferring the eSIM from the eUICC of one wireless device to the eUICC of another wireless device. In some embodiments, as part of an eSIM export process for transferring an eSIM from the eUICC of a source wireless device to the eUICC of a target wireless device, the processor of the source wireless device obtains one or more subscription service files that may include one or more CAP files and provides these one or more subscription service files to the eUICC of the source wireless device. The source wireless device's eUICC can combine one or more subscription service files with eSIM configuration file information to generate an eSIM export package, which is then provided to the target wireless device's eUICC for installing the transferred eSIM and one or more applets based on the subscription service files on the target wireless device's eUICC. In some implementations, the source wireless device's processor obtains one or more subscription service files (e.g., one or more CAP files) from one or more applet asset servers, and can obtain a network address (e.g., a Universal Record Locator (URL) value) for that applet asset server from the source wireless device's eUICC or from a network-accessible applet asset discovery server. In some implementations, the source wireless device's processor obtains an encrypted version of one or more subscription service files, which may include one or more CAP files, from local storage at the source wireless device or from a network-accessible remote storage device, and provides the encrypted version of the one or more subscription service files to the source wireless device's eUICC to generate a decrypted version of the one or more subscription service files included in the eSIM export package. For example, when communicating with an applet asset discovery server and / or one or more applet asset servers, the source wireless device's processor can reference the subscription service file based on the applet's Application Identifier (AID) value associated with the subscription service file. In some implementations, the processor of the source wireless device obtains one or more AID values ​​of a applet associated with the eSIM to be transferred to the eUICC of the target wireless device from the source wireless device's eUICC.In some implementations, the source wireless device's eUICC stores personalized applet data for the eSIM, such as each AID value corresponding to each applet. In some implementations, the source wireless device's eUICC provides this personalized applet data to the target wireless device's eUICC for personalizing the eSIM on the target wireless device's eUICC. In some implementations, the personalized applet data is included in (or included together with) the eSIM export package provided to the target wireless device, while in other implementations, the personalized applet data is provided to the target wireless device separately from the eSIM export package.

[0005] Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings illustrating the principles of the described embodiments by way of example.

[0006] The content of this invention is provided merely to outline 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 above features are merely illustrative and should not be construed as narrowing the scope or substance 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. Attached Figure Description

[0007] This disclosure will be more readily understood by taking into account the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals denote similar structural elements.

[0008] Figure 1 Block diagrams illustrating different components of exemplary systems configured to implement the various technologies described herein, according to some implementation schemes.

[0009] Figure 2 Examples are given based on some implementation schemes. Figure 1 A block diagram showing a more detailed view of exemplary components of the system.

[0010] Figure 3A and Figure 3B A block diagram illustrating an exemplary cellular service transfer mechanism for a wireless device according to some implementation schemes is shown.

[0011] Figure 4A , Figure 4B and Figure 4C An exemplary sequence of actions is illustrated according to some implementations for exporting and transferring an eSIM with a CAP file associated with an eSIM applet from a source wireless device to a target wireless device.

[0012] Figure 5AA flowchart illustrating an exemplary method, according to some implementations, for transferring an eSIM with a applet to a target wireless device, is provided.

[0013] Figure 5B A flowchart illustrating another exemplary method, according to some implementations, for transferring an eSIM with a applet to a target wireless device, is shown.

[0014] Figure 5C A flowchart illustrating an exemplary method, according to some implementation schemes, executed by a mini-program asset server to help transfer an eSIM with a mini-program from a source wireless device to a target wireless device.

[0015] Figure 6A and Figure 6B This illustrates another exemplary sequence of actions performed, according to some implementations, to export and transfer an eSIM with a CAP file associated with an eSIM applet from a source wireless device to a target wireless device.

[0016] Figure 7 A block diagram illustrating exemplary components of a mobile wireless device according to some implementation schemes is shown. Detailed Implementation

[0017] This section describes representative applications of the methods and apparatus according to this application. These examples are provided only to add context and aid in understanding the described embodiments. Therefore, it will be apparent to those skilled in the art that the described embodiments can be practiced without some or all of these specific details. In other instances, well-known processing steps have not been described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are possible, such that the following examples should not be considered limiting.

[0018] In the following detailed description, reference is made to the accompanying drawings, which form part of this specification, and specific embodiments according to the described embodiments are illustrated by way of example in the drawings. While these embodiments are described in sufficient detail to enable those skilled in the art to practice the described embodiments, it should be understood that these examples are not limiting; other embodiments are permitted for use, and modifications may be made without departing from the spirit and scope of the described embodiments.

[0019] This application describes techniques for managing subscription service files for exporting and / or transferring electronic SIMs (eSIMs) from wireless devices. These subscription service files may include Custom Application Part (CAP) files for Mobile Network Enhancement Logic (CAMEL). Subscription service files (such as CAP files) can be used to generate applets that are installed on an embedded universal integrated circuit card (eUICC) of the wireless device along with an eSIM profile. After the installation of the applets associated with the eSIM on the eUICC is complete, the process of this invention discards one or more subscription service files (such as one or more CAP files). The absence of subscription service files (e.g., CAP files) associated with the applets of the eSIM hinders the generation of an interoperable eSIM package for transferring the eSIM from the eUICC of a source wireless device to the eUICC of a target wireless device. In some embodiments described in this application, one or more subscription service files (such as one or more CAP files) may later be reused as part of an eSIM process (e.g., an eSIM export process) to transfer the eSIM (and thus the associated applets) from the source wireless device to the target wireless device. When one or more applets associated with the eSIM of the source wireless device are installed on the eUICC, one or more subscription service files (such as one or more CAP files) used to generate one or more applets may be encrypted by the eUICC and stored locally at the source wireless device and / or remotely on a network-accessible server for later retrieval, for use in generating an eSIM export package for transferring the eSIM from the eUICC of the source wireless device to the eUICC of the target wireless device.

[0020] In some implementations, as part of an eSIM process (e.g., an eSIM export process) for transferring an eSIM from the eUICC of a source wireless device to the eUICC of a target wireless device, the processor of the source wireless device, outside the eUICC of the source wireless device, obtains one or more subscription service files (e.g., one or more CAP files) and provides these one or more subscription service files (e.g., one or more CAP files) to the eUICC of the source wireless device. The eUICC of the source wireless device may combine one or more subscription service files, which may include one or more CAP files, with eSIM profile information to generate an eSIM export package, which is provided to the eUICC of the target wireless device for installing the transferred eSIM on the eUICC of the target wireless device. In some implementations, the processor of the source wireless device obtains one or more subscription service files (e.g., one or more CAP files) from one or more applet asset servers, and may obtain a network address (e.g., a Universal Record Locator (URL) value) from the eUICC of the source wireless device or from a network-accessible applet asset discovery server for the purposes of these one or more applet asset servers. In some cases, subscription service files (such as CAP files) obtained from a mini-program asset server may correspond to an updated (e.g., current, newer) version of the mini-program installed with the eSIM on the eUICC of the source wireless device. In other cases, subscription service files (e.g., CAP files) obtained from a mini-program server may correspond to a version of the mini-program installed with the eSIM on the eUICC of the source wireless device (e.g., as initially installed or currently installed when generating an eSIM export package for transferring the eSIM associated with the mini-program). In some implementations, the processor of the source wireless device obtains an encrypted version of one or more subscription service files, which may include one or more CAP files, from local storage at the source wireless device or from network-accessible remote storage, and provides the encrypted version of the one or more subscription service files, which may include one or more CAP files, to the eUICC of the source wireless device to generate a decrypted version of the one or more subscription service files (e.g., one or more CAP files) to be included in the eSIM export package. In some cases, the processor provides one or more subscription service files (e.g., one or more CAP files) from local storage devices and / or remote storage devices, as well as one or more subscription service files (e.g., one or more CAP files) from one or more applet asset servers to the source wireless device's eUICC.The source wireless device's eUICC can generate an eSIM export package that does not include any one of the subscription service files obtained by the processor from various sources, or includes some or all of the subscription service files in the one or more subscription service files, which may include one or more CAP files.

[0021] For example, when communicating with a mini-program asset discovery server and / or with one or more mini-program asset servers, the processor of the source wireless device may reference a subscription service file based on the application identifier (AID) value of the mini-program associated with one or more subscription service files (e.g., one or more CAP files), which may include one or more CAP files. In some implementations, the processor of the source wireless device obtains one or more AID values ​​of the mini-program associated with the eSIM to be transferred to the eUICC of the target wireless device from the eUICC of the source wireless device. The one or more AID values ​​may be provided as an array by the eUICC in response to a request for mini-program assertion server information, which may include the network address (e.g., a URL value) of each mini-program asset server associated with the mini-program identified by the AID values ​​in the array. In some implementations, the processor of the source wireless device establishes a separate authenticated session with the mini-program asset server to obtain one or more subscription service files (e.g., one or more CAP files) of the mini-program identified by the AID values ​​and associated with the mini-program asset server. In some implementations, the processor of the source wireless device establishes separate authenticated sessions with multiple mini-program asset servers, for example, establishing a separate authenticated session with each mini-program asset server identified in an array obtained from eUICC. In some implementations, in response to a request for mini-program asset server information, eUICC provides the processor of the source wireless device with an array of AID values ​​of the mini-programs associated with the eSIM and the network address (e.g., a URL value) of the mini-program asset discovery server, obtaining the network address of the mini-program asset server associated with each AID value from that mini-program asset discovery server. The processor of the source wireless device can obtain the network address response from the mini-program asset discovery server for a request including one or more AID values.

[0022] The processor of the source wireless device provides one or more subscription service files (e.g., one or more CAP files) to the eUICC of the source wireless device. These subscription service files may be unencrypted versions of one or more subscription service files (e.g., one or more CAP files) obtained from one or more applet asset servers and / or encrypted versions of one or more subscription service files (e.g., one or more CAP files) obtained from local storage and / or remote storage. The eUICC of the source wireless device may combine one or more subscription service files, including one or more CAP files, with eSIM profile information to form an eSIM export package, which is then transmitted to the eUICC of the target wireless device for installing the eSIM profile and associated applets (which can be generated using one or more subscription service files, such as one or more CAP files). In some embodiments, the eUICC of the source wireless device stores personalized applet data for the eSIM, such as each AID value corresponding to each applet. In some embodiments, the eUICC of the source wireless device provides the personalized applet data to the eUICC of the target wireless device for personalizing the eSIM on the eUICC of the target wireless device. In some implementations, personalized app data is included in (or included together with) the eSIM export package provided to the target wireless device, while in other implementations, personalized app data is provided to the target wireless device separately from the eSIM export package.

[0023] These and other implementation schemes are referenced below. Figure 1 The discussion extends to Figure 6; however, those skilled in the art will readily understand that the detailed descriptions given herein with respect to these figures are for illustrative purposes only and should not be construed as limiting.

[0024] Figure 1 Block diagrams illustrating different components of a system 100 configured to implement the various technologies described herein, according to some implementation schemes. More specifically, Figure 1A brief overview of system 100 is illustrated in the figure. The system includes a wireless device 102 (which may also be referred to as a device, wireless equipment, mobile device, user equipment (UE), etc.), a set of base stations 112-1 to 112-N managed by different mobile network operators (MNOs) 114, and a set of MNO dispatch servers 116 communicating with MNO 114. Additional MNO infrastructure servers, such as those used for account management and billing, are not shown. Wireless device 102 may represent a mobile computing device (e.g., a telephone, tablet computer, peripheral device, etc.), and base stations 112-1 to 112-n may represent cellular radio access network (RAN) entities, including evolved Node Bs (eNodeBs or eNBs) and / or next-generation Node Bs (gNodeBs or gNBs), configured to communicate with wireless device 102. Each of base stations 112-1 to 112-n may be a single entity, a quasi-co-located entity, or separated among multiple units (e.g., central unit (CU), distributed unit (DU), remote unit (RU), etc.). MNO 114 may represent different wireless service providers that offer specific cellular wireless services (e.g., voice and data) that wireless device 102 can subscribe to, such as through a user's subscription account of wireless device 102.

[0025] like Figure 1As shown, wireless device 102 may include processing circuitry (which may include one or more processors 104 and memory 106), an embedded universal integrated circuit card (eUICC) 108 and / or an integrated UICC (iUICC) (not shown), and baseband wireless circuitry 110 for transmitting and receiving cellular radio frequency signals. Baseband wireless circuitry 110 may include analog hardware components such as antennas and amplifiers, and digital processing components such as signal processors (and / or general-purpose / limited-purpose processors) and associated memory. In some embodiments, in addition to eUICC 108, wireless device 102 may also include one or more physical UICCs 118 (also referred to as Subscriber Identity Module (SIM) cards). The components of wireless device 102 work together to enable wireless device 102 to provide users of wireless device 102 with useful features such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and internet connectivity. Although depicted as distinct blocks, various components (e.g., memory 106, processor 104, eUICC 108, baseband wireless circuitry 110, and UICC 118) can be arranged and combined in any number of configurations. eUICC 108 can be configured to store multiple electronic SIMs (eSIMs) for accessing cellular wireless services provided by different MNOs 114 via connections to their respective cellular wireless networks through base stations 112-1 to 112-N. For example, eUICC 108 can be configured to store and manage one or more eSIMs for one or more MNOs 114 with different subscriptions associated with wireless device 102. To access services provided by the MNOs, eSIMs can be downloaded to and installed on eUICC 108. In some implementations, eUICC 108 obtains one or more eSIMs from one or more associated MNO dispatch servers 116. MNO dispatch servers 116 can be maintained by MNOs 114, OEM manufacturers, third-party entities, etc. eSIM data communication between MNO dispatch server 116 and eUICC 108 (or between MNO dispatch server 116 and a processing circuit (e.g., processor 104) of wireless device 102 outside eUICC 108) may use a secure communication channel.

[0026] Figure 2 Examples are given based on some implementation schemes. Figure 1 A more detailed view 200 of specific components of the wireless device 102. (See block diagram 200.) Figure 2 As shown, the processor 104, combined with memory 106, can implement a main operating system (OS) 202 configured to execute applications 204 (e.g., local OS applications and user applications). Similarly, as... Figure 2As shown, the eUICC 108 can be configured to implement an eUICC OS 206, which is configured to manage the hardware resources of the eUICC 108 (e.g., the processor and memory embedded in the eUICC 108). The eUICC OS 206 can also be configured to manage the eSIM 208 stored by the eUICC 108, for example, by downloading, installing, deleting, enabling, disabling, modifying, or otherwise performing management of the eSIM 208 within the eUICC 108 and providing access to the eSIM 208 to the baseband wireless circuit 110 to provide access to wireless services to the wireless device 102. The eUICC 108 OS may include an eSIM manager 210, which can perform management functions on various eSIMs 208. Figure 2 As illustrated, each eSIM 208 may include several applets 212 that define how the eSIM 208 operates. For example, one or more applets 212, when implemented in conjunction with baseband wireless circuit 110 and eUICC 108, may be configured to enable wireless device 102 to communicate with MNO 114 and provide useful features (e.g., telephone calling and internet access) to users of wireless device 102. Applets 212 of eSIM 208 may be installed on eUICC 108 according to one or more subscription service files, such as one or more Custom Application Application Part (CAP) files for Mobile Network Enhancement Logic (CAMEL), which may be included in the Binding Profile Package (BPP) of eSIM 208 obtained from MNO dispatch server 116. As further discussed herein, subscription service files (such as CAP files) may be retained after applet 212 is installed, or obtained from applet asset server for new installations, reinstallations, and / or updates of applet 212.

[0027] Similarly, Figure 2As shown, the baseband wireless circuit 110 of the wireless device 102 may include a baseband OS 214 configured to manage the hardware resources of the baseband wireless circuit 110 (e.g., processor, memory, various radio components, etc.). According to some embodiments, the baseband wireless circuit 110 may implement a baseband manager 216 configured to interface with the eUICC 108 to establish a secure channel with the MNO dispatch server 116 and obtain information (such as eSIM data) from the MNO dispatch server 116 for managing the eSIM 208. The baseband manager 216 may be configured to implement a service 218, representing a collection of software modules instantiated through various applets 212 included in the enabled eSIM 208 within the eUICC 108. For example, service 218 may be configured to manage different connections between the wireless device 102 and the MNO 114 based on the different eSIMs 208 enabled within the eUICC 108.

[0028] Figure 3A Figures 300 and 320 illustrate two exemplary mechanisms for transferring a cellular radio service plan from a source wireless device 102A to a target wireless device 102B. In Figure 300, the cellular radio service plan is associated with a UICC (SIM card) 118, which includes credentials for accessing the wireless network of MNO 114. When the target wireless device 102B supports the hardware and software capabilities required to access the wireless network of MNO 114 using the SIM in UICC 118, the user can remove UICC 118 from the source wireless device 102A and insert UICC 118 into the receiving area of ​​the target wireless device 102B. The target wireless device 102B can use the credentials included in the SIM in UICC 118 to authenticate to and reside on the cellular radio access network associated with the MNO 114, which is associated with the SIM in UICC 118. The source wireless device 102A and the target wireless device 102B may belong to different users and may be supplied by different original equipment manufacturers (OEMs). The applet 212 associated with the SIM of the UICC 118 may also be stored on the UICC 118 and transferred from the source wireless device 102A to the target wireless device 102B along with the SIM.

[0029] Figure 320 illustrates an exemplary mechanism for transferring a cellular wireless service plan associated with eSIM 208 on eUICC 108 from source wireless device 102A to target wireless device 102B using cloud network service 302. Unlike the mechanism illustrated in Figure 300, no physical transfer of UICC 118 is performed, and in some cases, a new eSIM 208 may be provided to the eUICC 108 of target wireless device 102B as part of the transfer. If the new eSIM 208 is downloaded from MNO dispatch server 116, the CAP file for installing applet 212 may also be provided by MNO dispatch server 116 in a BPP including the new eSIM 208. In some cases, each of the source wireless device 102A and target wireless device 102B may register with services such as cloud-based services (e.g., iCloud). ® A public user account managed by the service account. Source wireless device 102A can provide information about available cellular service plans on source wireless device 102A to cloud network service 302, and target wireless device 102B can discover available cellular service plans based on information stored at cloud network service 302. Source wireless device 102A can obtain a transfer token from MNO authorization server 304 required to transfer the cellular service plan associated with eSIM 208. Target wireless device 102B can obtain eSIM 208 from MNO allocation server 116, which is authorized to release eSIM 208 to target wireless device 102B based on communication from MNO authorization server 304. Target wireless device 102B can download, install, and activate eSIM 208 on its eUICC 108. However, the transfer mechanism illustrated in Figure 320 requires the source wireless device 102A and the target wireless device 102B to link through a public user account at the cloud network service 302, and requires the download of a new eSIM 208 from the MNO dispatch server 116.

[0030] Figure 3BFigures 340 and 360 illustrate an additional exemplary mechanism for transferring a cellular wireless service plan associated with eSIM 208 from a source wireless device 102A to a target wireless device 102B, wherein the source wireless device 102A and the target wireless device 102B do not need to link to a public user account for a cloud-based network service or need not be manufactured by a public OEM. As illustrated in Figure 340, the source wireless device 102A and the target wireless device 102B can establish a secure local connection 342 between them, through which they exchange the information required to select the cellular wireless service plan associated with the SIM on the UICC 118 of the source wireless device 102A or the eSIM 208 on the eUICC 108 and transfer it to a new eSIM 208 downloaded to the eUICC 108 of the target wireless device 102B. In some implementations, as illustrated in Figure 360, source wireless device 102A may use a Quick Response (QR) code to provide information for transferring a cellular wireless service plan to target wireless device 102B, which can be scanned by target wireless device 102B. In some implementations, source wireless device 102A and target wireless device 102B are within close proximity to each other to allow a QR code to be displayed on source wireless device 102A and scanned by the camera of target wireless device 102B. In some implementations, source wireless device 102A and target wireless device 102B are not within close proximity to each other, and source wireless device 102A provides the QR code to target wireless device 102B via an alternative out-of-band communication channel (not shown) (such as via email or via a messaging service). In either mechanism (secure Bluetooth or QR code), each of the source wireless device 102A and the target wireless device 102B can communicate with the MNO authorization server 304 to authorize the transfer of a cellular wireless service plan from the source wireless device 102A to the target wireless device 102B. The MNO authorization server 304 can communicate information to the MNO allocation server 116 to reserve a new eSIM 208 for the transferred cellular wireless service plan. The target wireless device 102B can download the new eSIM 208 from the MNO allocation server 116 and subsequently install and activate the new eSIM 208 on its eUICC 108. In some implementations, the source wireless device 102A and the target wireless device 102B need to be within a threshold proximity distance to establish a secure Bluetooth communication channel. In some implementations, the source wireless device 102A and the target wireless device 102B can use different operating systems and can be manufactured by different OEMs, such as iOS devices manufactured by Apple and Android devices manufactured by Motorola. ™ equipment.

[0031] Figure 3A and Figure 3B The illustrated transfer mechanism relies on downloading a new eSIM 208 from an MNO allocation server 116, which may include one or more subscription service files (such as CAP files) for installing an applet 212 for the new eSIM 208. However, in some cases, it is preferable to have the source wireless device 102A generate an eSIM export package including an eSIM profile and one or more subscription service files (such as CAP files) for installing the applet 212 associated with the transferred eSIM profile, and to provide the eSIM export package to the target wireless device 102B for installing the transferred eSIM profile and associated applet 212 on the target wireless device 102B's eUICC 108. Currently, the subscription service files (such as CAP files) used to install (or update) the eSIM 208 on the eUICC 108 are discarded after the applet 212 is installed. Regenerating subscription service files (e.g., one or more CAP files) from the already installed applet 212 of the eSIM 208 is not feasible. Conversely, as described herein, the subscription service file (e.g., the CAP file) can be retained after applet 212 is installed, or retrieved again by the source wireless device 102A from the applet asset server to generate a complete eSIM export package for transferring eSIM 208 to the target wireless device 102B. The transfer of the eSIM export package can be performed via various mechanisms, such as via a secure local connection 342, via cloud network service 302, via QR code encoding, or via another secure transfer between the source wireless device 102A and the target wireless device 102B. In some implementations, eSIM 208 can be installed on the target wireless device 102B's eUICC 108B without needing to download a new eSIM 208 from the MNO provisioning server 116.

[0032] Figure 4AFigure 400 illustrates an exemplary sequence of actions performed to export and transfer eSIM 208, along with a subscription service file (e.g., a CAP file) associated with applet 212 of eSIM 208, from source wireless device 102A to target wireless device 102B. At 404, the eUICC 108A of source wireless device 102A may transmit a message to the processor 104A of source wireless device 102A initiating the process of transferring eSIM 208 from the eUICC 108A of source wireless device 102A to the eUICC 108B of target wireless device 102B. The processor 104A of source wireless device 102A may respond at 406 by transmitting a message to the eUICC 108A of source wireless device 102A requesting applet assertion server information for applet 212 associated with the eSIM 208 to be transferred. The eUICC 108A of the source wireless device 102A can determine the applet 212 associated with the eSIM 208 to be transferred (where each applet can be identified by an Application Identifier (AID) value), and respond to the processor 104A of the source wireless device 102A by transmitting a message at 408 including an array of one or more AID values ​​and one or more network addresses (e.g., URL values) of the applet asset server 402, obtaining a subscription service file (e.g., a CAP file) from the applet asset server for generating a version of the applet 212 associated with the eSIM 208 to be transferred. In some embodiments, the processor 104A of the source wireless device 102A can retrieve the subscription service file (e.g., a CAP file) of the eSIM 208 to be transferred from a single applet asset server 402. In some embodiments, the processor 104A of the source wireless device 102A can retrieve the subscription service files (e.g., CAP files) of the eSIM 208 to be transferred from multiple different applet asset servers 402.

[0033] For each mini-program asset server 402, at 410, the eUICC 108A of the source wireless device 102A can establish a secure, authenticated session between the source wireless device 102A and the mini-program asset server 402. When the subscription service file (e.g., CAP file) for the mini-program 212 used for the eSIM 208 to be transferred is distributed among multiple mini-program asset servers 402, the source wireless device 102A can establish a separate secure, authenticated session with each applicable mini-program asset server 402. At 412, the mini-program asset server 402 can provide a random number to the processor 104A of the source wireless device 102A, and at 414, the processor 104A of the source wireless device 102A can provide this random number to the eUICC 108A of the source wireless device 102A in a message requesting the AID value of the mini-program 212 associated with the eSIM 208 to be transferred. At 416, the eUICC 108A of the source wireless device 102A responds by sending a message signed by the eUICC 108A to the processor 104A of the source wireless device 102A. This message includes a random number received from the applet asset server 402, a unique identifier for the eSIM 208 to be transferred (e.g., an International Circuit Card Identifier (ICCID) value), and an array of one or more AID values. At 418, the processor 104A of the source wireless device 102A sends a message to the applet asset server 402 requesting a subscription service file (e.g., a CAP file) for applet 212 identified by an array of one or more AID values. This message includes the signed message received from the eUICC 108A at 416. At 420, the applet asset server 402 responds to this request using a message comprising an array of one or more subscription service files (e.g., one or more CAP files) for applet 212 identified by an array of one or more AID values. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to respond to a newer version of the applet associated with the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to respond to a completely new applet used with the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to copy a version of the applet used for the eSIM 208 to be transferred, such as the version originally installed with the eSIM 208 on the source wireless device 102A's eUICC 108A or the version currently installed for the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may respond to an AID value indicated in an array of one or more AID values ​​without providing a subscription service file (e.g., a CAP file).

[0034] At 422, the processor 104A of the source wireless device 102A provides a message to the eUICC 108A of the source wireless device 102A requesting the transfer of the eSIM 208 along with subscription service files (e.g., CAP files) associated with the applet 212 of the eSIM 208. This message may include the ICCID value of the eSIM 208 and an array for generating, for example, one or more subscription service files (e.g., one or more CAP files) associated with the applet 212 of the eSIM 208 at the eUICC 108B of the target wireless device 102B. At 424, the eUICC 108A of the source wireless device 102A merges the subscription service files (e.g., one or more CAP files) obtained from the processor 104A of the source wireless device 102A with eSIM profile data to form the eSIM export package. The eSIM export package may include one or more subscription service files (e.g., one or more CAP files) for generating applet 212 at the eUICC 108B of the target wireless device 102B when the eSIM 208 is installed on the eUICC 108 of the target wireless device 102B. In some embodiments, at 426, the eUICC 108A of the source wireless device 102A stores personalized applet data for one or more applets 212, for example, via AID values ​​for each applet identifier. In some embodiments, the personalized applet data may be transferred to the target wireless device 102B for personalizing the applet 212 generated by the one or more subscription service files (e.g., one or more CAP files) in association with the installation of the eSIM at the eUICC 108B of the target wireless device 102B. At 428, the eUICC 108A of the source wireless device 102A provides the eSIM export package to the processor 104A of the source wireless device 102A. At 430, the processor forwards the eSIM export package to the processor 104B of the target wireless device 102B, for provision to the eUICC 108B of the target wireless device 102B at 432. At 434, the eUICC 108B of the target wireless device 102B can, for example, use a provided subscription service file (e.g., one or more CAP files included in the eSIM export package) to install the eSIM 208 and the associated applet 212. In some embodiments, the applet 212 is personalized by the eUICC 108B of the target wireless device 102B based on personalized applet data obtained from the eUICC 108A of the source wireless device 102A.

[0035] Figure 4BFigure 440 illustrates another exemplary sequence of actions performed to export and transfer eSIM 208, along with subscription service files (e.g., CAP files) associated with applet 212 of eSIM 208, from source wireless device 102A to target wireless device 102B. Figure 4A In this process, the processor 104A of the source wireless device 102A obtains one or more network addresses (e.g., URL values) of the applet asset server 402 from the eUICC 108A of the source wireless device 102A. Figure 4B In this process, the processor 104A of the source wireless device 102A obtains the network address (e.g., URL value) of the mini-program asset discovery server 442. This network address is simpler to maintain for the eUICC 108A of the source wireless device 102A. The processor 104A of the source wireless device 102A obtains the network addresses (e.g., URL values) of one or more mini-program asset servers 402 from the mini-program asset discovery server 442. This network address can be used as a public resource from which information about multiple mini-program asset servers 402 of the source wireless device 102A is obtained.

[0036] At 404, the eUICC 108A of the source wireless device 102A may send a message to the processor 104A of the source wireless device 102A initiating a process to transfer the eSIM 208 from the eUICC 108A of the source wireless device 102A to the eUICC 108B of the target wireless device 102B. The processor 104A of the source wireless device 102A may respond at 406 by sending a message to the eUICC 108A of the source wireless device 102A to obtain applet assertion server information associated with applet 212 of the eSIM 208 to be transferred. The eUICC 108A of the source wireless device 102A can determine the applet 212 associated with the eSIM 208 to be transferred (where each applet can be identified by an Application Identifier (AID) value), and responds to the processor 104A of the source wireless device 102A by transmitting a message at 448 including an array of one or more AID values ​​and a network address (e.g., a URL value) of the applet asset server 402, from which a subscription service file (e.g., a CAP file) is obtained to generate a version of the applet 212 associated with the eSIM 208 to be transferred. At 450, the processor 104A of the source wireless device 102A transmits a request to the applet asset server 442 for the network addresses (e.g., URL values) of one or more applet asset servers 402, from which a subscription service file (e.g., a CAP file) is obtained, and these subscription service files are used to generate the applet 212 identified by one or more AID values. The request may include an array of one or more AID values. The mini-program asset discovery server 442 may respond at 452 with a message including one or more AID values, each AID value paired with a corresponding network address (e.g., a URL value) of the mini-program asset server 402, obtain a CAP file from the mini-program asset server, and use these CAP files to generate a mini-program 212 identified by the AID values. In some embodiments, the processor 104A of the source wireless device 102A may retrieve a subscription service file (e.g., a CAP file) of the eSIM 208 to be transferred from a single mini-program asset server 402. In some embodiments, the processor 104A of the source wireless device 102A may retrieve subscription service files (e.g., CAP files) of the eSIM 208 to be transferred from multiple different mini-program asset servers 402.

[0037] For each mini-program asset server 402, at 410, the eUICC 108A of the source wireless device 102A can establish a secure, authenticated session between the source wireless device 102A and the mini-program asset server 402. When the subscription service file (e.g., CAP file) for the mini-program 212 used for the eSIM 208 to be transferred is distributed among multiple mini-program asset servers 402, the source wireless device 102A can establish a separate secure, authenticated session with each applicable mini-program asset server 402. At 412, the mini-program asset server 402 can provide a random number to the processor 104A of the source wireless device 102A, and at 414, the processor 104A of the source wireless device 102A can provide this random number to the eUICC 108A of the source wireless device 102A in a message requesting the AID value of the mini-program 212 associated with the eSIM 208 to be transferred. At 416, the eUICC 108A of the source wireless device 102A responds by sending a message signed by the eUICC 108A to the processor 104A of the source wireless device 102A. This message includes a random number received from the applet asset server 402, a unique identifier for the eSIM 208 to be transferred (e.g., an International Circuit Card Identifier (ICCID) value), and an array of one or more AID values. At 418, the processor 104A of the source wireless device 102A sends a message to the applet asset server 402 requesting a subscription service file (e.g., a CAP file) for applet 212 identified by an array of one or more AID values. This message includes the signed message received from the eUICC 108A at 416. At 420, the applet asset server 402 responds to this request using a message comprising an array of one or more subscription service files (e.g., one or more CAP files) for applet 212 identified by an array of one or more AID values. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to respond to a newer version of the applet associated with the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to respond to a completely new applet used with the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may utilize a subscription service file (e.g., a CAP file) to copy a version of the applet used for the eSIM 208 to be transferred, such as the version originally installed with the eSIM 208 on the source wireless device 102A's eUICC 108A or the version currently installed for the eSIM 208 to be transferred. In some implementations, the applet asset server 402 may respond to an AID value indicated in an array of one or more AID values ​​without providing a subscription service file (e.g., a CAP file).

[0038] At 422, the processor 104A of the source wireless device 102A provides a message to the eUICC 108A of the source wireless device 102A requesting the transfer of the eSIM 208 along with a subscription service file (e.g., a CAP file) associated with the applet 212 of the eSIM 208. This message may include the ICCID value of the eSIM 208 and an array for generating, for example, one or more subscription service files (e.g., one or more CAP files) associated with the applet 212 at the eUICC 108B of the target wireless device 102B. At 424, the eUICC 108A of the source wireless device 102A merges the subscription service file (e.g., the CAP file) obtained from the processor 104A of the source wireless device 102A with eSIM profile data to form the eSIM export package. The eSIM export package may include one or more subscription service files (e.g., one or more CAP files) for generating applet 212 at the eUICC 108B of the target wireless device 102B when the eSIM 208 is installed on the eUICC 108 of the target wireless device 102B. In some embodiments, at 426, the eUICC 108A of the source wireless device 102A stores personalized applet data for one or more applets 212, for example, via AID values ​​for each applet identifier. In some embodiments, the personalized applet data may be transferred to the target wireless device 102B for personalizing the applet 212 generated from the subscription service files (e.g., CAP files) in association with the installation of the eSIM at the eUICC 108B of the target wireless device 102B. At 428, the eUICC 108A of the source wireless device 102A provides an eSIM export package to the processor 104A of the source wireless device 102A. At 430, the processor forwards the eSIM export package to the processor 104B of the target wireless device 102B, for provision to the eUICC 108B of the target wireless device 102B at 432. At 434, the eUICC 108B of the target wireless device 102B can, for example, use a provided subscription service file (e.g., a CAP file included in the eSIM export package) to install the eSIM 208 and the associated applet 212. In some embodiments, the applet 212 is personalized by the eUICC 108B of the target wireless device 102B based on personalized applet data obtained from the eUICC 108A of the source wireless device 102A.

[0039] Figure 4CFigure 460 illustrates another exemplary sequence of actions performed to export and transfer eSIM 208, along with subscription service files (e.g., CAP files) associated with applet 212 of eSIM 208, from source wireless device 102A to target wireless device 102B. Figure 4A and Figure 4B In this process, the source wireless device 102A obtains one or more subscription service files (e.g., one or more CAP files) from one or more mini-program asset servers 402. Figure 4C In this process, the source wireless device 102A obtains one or more subscription service files (e.g., one or more CAP files) previously received from the MNO dispatch server 116 during the installation of eSIM 208, either from a local storage device or a remote storage device. This eSIM is to be transferred and / or used to update applets (or customize eSIM 208) after eSIM 208 is installed on the source wireless device 102A's eUICC 108A.

[0040] At 462, the eUICC 108A of the source wireless device 102A performs the process of downloading eSIM 208 from MNO dispatch server 116. eSIM 208 may be received as a Binding Profile Package (BPP), which may include one or more subscription service files (e.g., one or more CAP files) for installing applet 212 associated with eSIM 208 on the eUICC 108A of the source wireless device 102A. At 464, the eUICC 108A installs eSIM 208 and one or more applets 212 generated by executing one or more subscription service files (e.g., one or more CAP files), which are included together with the eSIM 208 obtained from MNO dispatch server 116. Unlike the current conventional process, the eUICC 108A of the source wireless device 102A encrypts one or more subscription service files (e.g., one or more CAP files) at 466, and provides the encrypted one or more subscription service files (e.g., one or more CAP files) to the processor 104A of the source wireless device 102A at 468. The encrypted one or more subscription service files (e.g., one or more CAP files) can be referenced based on the AID value of applet 212, which can be generated from the corresponding subscription service file (e.g., CAP file). At 470, the processor 104A of the source wireless device 102A stores the encrypted one or more subscription service files (e.g., one or more CAP files) locally at the source wireless device 102A and / or remotely at a network-accessible storage device, such as securely stored in cloud network service 302 or other secure remote storage device. The encrypted subscription service files (e.g., encrypted CAP files) can later be used when exporting eSIM 208 to the target wireless device 102B.

[0041] At 404, the eUICC 108A of the source wireless device 102A may transmit a message to the processor 104A of the source wireless device 102A initiating a process to transfer the eSIM 208 from the eUICC 108A of the source wireless device 102A to the eUICC 108B of the target wireless device 102B. At 472, the processor 104A of the source wireless device 102A responds with a request for applet AID data (e.g., the AID value of applet 212 associated with the eSIM 208 to be transferred). At 474, the eUICC 108A of the source wireless device 102A responds with an array of one or more AID values ​​of applet 212 associated with the eSIM 208. At 476, the processor 104A of the source wireless device 102A retrieves one or more encrypted subscription service files (e.g., one or more encrypted CAP files) from local storage and / or from network-accessible remote storage, wherein one or more AID values ​​can be used to identify the applicable encrypted subscription service file (e.g., the applicable encrypted CAP file) of applet 212 of eSIM 208. At 478, the processor 104A of the source wireless device 102A provides a message to the eUICC 108A of the source wireless device 102A requesting an eSIM export package for the eSIM 208 to be transferred. This message may include a unique identifier value (e.g., an ICCID value) for eSIM 208 and an array for one or more encrypted subscription service files (e.g., one or more encrypted CAP files) of applet 212 associated with eSIM 208.

[0042] At 480, the eUICC 108A of the source wireless device 102A decrypts one or more encrypted subscription service files (e.g., one or more encrypted CAP files). At 424, the eUICC 108A of the source wireless device 102A merges the decrypted version of the subscription service file (e.g., the CAP file) with eSIM profile data to form an eSIM export package. The eSIM export package may include one or more subscription service files (e.g., CAP files) for use in generating applet 212 at the eUICC 108B of the target wireless device 102B when the eSIM 208 is installed on the eUICC 108 of the target wireless device 102B. In some implementations, at 426, the eUICC 108A of the source wireless device 102A stores personalized applet data for one or more applets 212, for example, via an AID value for each applet identifier. In some implementations, personalized applet data can be transferred to target wireless device 102B for personalizing applet 212 generated from a subscription service file (e.g., a CAP file) in association with the installation of an eSIM at the eUICC 108B of target wireless device 102B. The eUICC 108A of source wireless device 102A provides an eSIM export package to its processor 104A at 428, which forwards the eSIM export package to the processor 104B of target wireless device 102B at 430, for provision to the eUICC 108B of target wireless device 102B at 432. At 434, the eUICC 108B of target wireless device 102B can, for example, use the provided subscription service file (e.g., a CAP file included in the eSIM export package) to install eSIM 208 and the associated applet 212. In some implementations, the eUICC 108B of the target wireless device 102B personalizes the mini-program 212 based on the personalized mini-program data of the mini-program 212 obtained from the eUICC 108A of the source wireless device 102A.

[0043] Figure 5AA flowchart 500 illustrates an exemplary method executed by a source wireless device 102A to transfer an eSIM 208 with applet 212 to a target wireless device 102B. At 502, the processor 104A of the source wireless device 102A obtains one or more network addresses (e.g., URL values) of one or more applet asset servers 402 corresponding to one or more applets 212, which are associated with the eSIM 208 to be transferred from the eUICC 108A of the source wireless device 102A to the eUICC 108B of the target wireless device 102B. At 504, the processor 104A of the source wireless device 102A obtains one or more subscription service files corresponding to the one or more applets 212 of the eSIM 208 from the one or more applet asset servers 402. At 506, the processor 104A of the source wireless device 102A generates an eSIM export package including the eSIM 208 and the one or more subscription service files. At 508, the processor 104A of the source wireless device 102A transmits the eSIM export packet to the target wireless device 102B.

[0044] In some implementations, the processor of the source wireless device 102A is external to the eUICC 108A of the source wireless device 102A. In some implementations, the processor of the source wireless device 102A is integrated with the eUICC 108A of the source wireless device 102A. In some implementations, the functionality of the eUICC 108A of the source wireless device is integrated into the processor of the source wireless device 102A. In some implementations, the processor 104A of the source wireless device 102A, in conjunction with the eUICC 108A of the source wireless device 102A (e.g., with the assistance of the eUICC), generates the eSIM export package.

[0045] In some implementations, at least one of the subscription service files includes a Custom Application Part (CAP) file for Mobile Network Enhancement Logic (CAMEL). In some implementations, the processor of the source wireless device 102A obtains one or more network addresses (e.g., URL values) of one or more mini-program asset servers 402 from the eUICC 108A of the source wireless device 102A. In some implementations, the one or more network addresses include one or more Application Identifier (AID) values, where each AID value is paired with a corresponding mini-program asset server network address. In some implementations, the processor 104A of the source wireless device 102A obtains one or more network addresses (e.g., URL values) of one or more mini-program asset servers 402 from the mini-program asset discovery server 442. In some implementations, the processor 104A of the source wireless device 102A: i) transmits a first message to the mini-program asset discovery server 442 requesting one or more network addresses (e.g., URL values) of one or more mini-program asset servers 402; and ii) receives a second message from the mini-program asset discovery server 442 including one or more application identifier (AID) values, each AID value paired with a corresponding network address (e.g., URL value) of the mini-program asset server 402. In some implementations, the first message includes one or more AID values. In some implementations, the processor 104A of the source wireless device 102A obtains one or more application identifier (AID) values ​​and the network address (e.g., URL value) of the mini-program asset discovery server 442 from the eUICC 108A of the source wireless device 102A. In some implementations, the processor 104A of the source wireless device 102A targets each of one or more mini-program asset servers 402: i) obtains the AID value of the mini-program 212 associated with the eSIM 208 and the mini-program asset server 402 from the eUICC 108A of the source wireless device 102A; ii) transmits a message to the mini-program asset server 402 requesting a subscription service file corresponding to the AID value; and ii) receives a subscription service file from the mini-program asset server 402, wherein the subscription service file is included in one or more subscription service files provided to the eUICC 108A of the source wireless device 102A. In some implementations, the subscription service file includes a newer version of the mini-program 212 associated with the eSIM 208 installed on the eUICC 108A of the source wireless device 102A. In some implementations, the eUICC 108A of the source wireless device 102A and / or the processor of the source wireless device 102A store personalized mini-program data associated with each mini-program 212 identified by the corresponding AID value of the eSIM 208.In some implementations, the eUICC 108A of the source wireless device 102A and / or the processor of the source wireless device 102A transfers personalized applet data to the eUICC 108B of the target wireless device 102B to personalize one or more applets transferred to the eSIM 208 of the target wireless device 102B.

[0046] Figure 5B A flowchart 520 illustrates another exemplary method executed by a source wireless device 102A to transfer an eSIM 208 with applet 212 to a target wireless device 102B. At 522, the processor 104A of the source wireless device 102A retrieves one or more encrypted subscription services corresponding to one or more applets 212 of the eSIM 208 to be transferred from the eUICC 108A of the source wireless device 102A to the eUICC 108B of the target wireless device 102B, either from local storage at the source wireless device 102A or from remote storage at a network-accessible server. At 524, the processor 104A of the source wireless device 102A generates an eSIM export package comprising at least one decrypted version of the eSIM 208 and one or more encrypted subscription service files. At 526, the processor 104A of the source wireless device 102A transmits the eSIM export package to the target wireless device 102B.

[0047] In some implementations, the processor of the source wireless device 102A is external to the eUICC 108A of the source wireless device 102A. In some implementations, the processor of the source wireless device 102A is integrated with the eUICC 108A of the source wireless device 102A. In some implementations, the functionality of the eUICC 108A of the source wireless device is integrated into the processor of the source wireless device 102A. In some implementations, the processor 104A of the source wireless device 102A, in conjunction with the eUICC 108A of the source wireless device 102A (e.g., with the assistance of the eUICC), generates the eSIM export package.

[0048] In some implementations, the generation of the eSIM export package includes the processor of the source wireless device 102A: i) transmitting one or more encrypted subscription service files to the eUICC 108A of the source wireless device 102A; and ii) receiving the eSIM export package from the eUICC 108A of the source wireless device 102A. In some implementations, at least one of the encrypted subscription service files includes an encrypted Custom Application for Mobile Network Enhancement Logic (CAMEL) Application Part (CAP) file. In some implementations, the processor 104A of the source wireless device 102A: i) receiving one or more encrypted subscription service files from the eUICC 108A of the source wireless device 102A in connection with the process of installing the eSIM 208 on the eUICC 108A of the source wireless device 102A; and ii) storing one or more encrypted subscription service files on local storage of the source wireless device 102A or on remote storage of a network-accessible server. In some implementations, the processor 104A of the source wireless device 102A: i) transmits a first message to the eUICC 108A of the source wireless device 102A requesting application identifier (AID) data for one or more applets 212 of the eSIM 208; and ii) receives from the eUICC 108A of the source wireless device 102A an array of AID values ​​corresponding to one or more applets 212 associated with the eSIM 208. In some implementations, the processor 104A of the source wireless device 102A retrieves one or more encrypted subscription service files based at least in part on the array of AID values. In some implementations, the eUICC 108A of the source wireless device 102A stores personalized applet data associated with each applet 212 identified by the corresponding AID value of the eSIM 208, and transfers the personalized applet data to the eUICC 108B of the target wireless device 102B to personalize one or more applets 212 of the eSIM 208 transferred to the target wireless device 102B.

[0049] Figure 5C A flowchart 540 illustrates an exemplary method executed by a mini-program asset server 402 to facilitate the transfer of an eSIM 208 with mini-programs 212 from a source wireless device 102A to a target wireless device 102B. At 542, the mini-program asset server 402 receives from the processor 104A of the source wireless device 102A a first message requesting one or more subscription service files corresponding to one or more mini-programs 212 of the eSIM 208, the first message including one or more AID values ​​corresponding to the mini-programs 212 of the eSIM 208. At 544, the mini-program asset server 402 transmits a second message to the processor 104A of the source wireless device 102A, including one or more subscription service files.

[0050] In some implementations, one or more subscription service files include a Custom Application for Mobile Network Enhancement Logic (CAMEL) application portion (CAP) file. In some implementations, one or more subscription service files include a subscription service file corresponding to a version of applet 212 of eSIM 208 installed with eSIM 208 on the eUICC 108A of the source wireless device 102A. In some implementations, one or more subscription service files include a subscription service file corresponding to a newer version of applet 212 of eSIM 208 installed on the eUICC 108A of the source wireless device 102A.

[0051] Figure 6A and Figure 6B Figures 600 and 630 illustrate another exemplary sequence of actions performed to export and transfer eSIM 208, along with a subscription service file (e.g., a CAP file) associated with the applet 212 of eSIM 208, from source wireless device 102A to target wireless device 102B. Figure 6A and Figure 6B In the process of the variation shown, with Figure 4C Compared to other processes, this reduces the actions performed by the eUICC 108A of the source wireless device 102A because the processor 104A of the source wireless device 102A, for example, uses a Local Profile Assistant (LPA) executing on the processor 104A to assemble the multipart eSIM profile export package without decrypting the encrypted subscription service files (e.g., encrypted CAP files) or reassembling them by the eUICC 108A of the source wireless device 102A. The multipart eSIM profile export package may include the eSIM profile core assembled by the eUICC 108A and one or more encrypted subscription service files (e.g., one or more encrypted CAP files) retrieved by the processor 104A from local storage or remote storage for the export process, wherein the one or more encrypted subscription service files were previously encrypted and stored as part of the eSIM installation process.

[0052] At 602, the eUICC 108A of the source wireless device 102A performs the process of downloading eSIM 208 from MNO dispatch server 116. eSIM 208 may be received as a Binding Profile Package (BPP), which may include one or more subscription service files (e.g., one or more CAP files) for installing applet 212 associated with eSIM 208 on the eUICC 108A of the source wireless device 102A. At 604, the eUICC 108A installs eSIM 208 and one or more applets 212 generated by executing one or more subscription service files (e.g., one or more CAP files), which are included together with eSIM 208 in the BPP obtained from MNO dispatch server 116. Unlike the current conventional process, at 606, the eUICC 108A of the source wireless device 102A encrypts the one or more subscription service files (e.g., one or more CAP files), for example, using a symmetric key. The eUICC 108A of the source wireless device 102A may include random data and one or more subscription service files (e.g., one or more CAP files) as part of the encryption process at 606 to ensure that the encrypted one or more subscription service files (e.g., one or more CAP files) are unique (i.e., not identical) among different eUICCs 108 of different wireless devices 102. At 608, the eUICC 108A of the source wireless device 102A generates a new asymmetric encryption key pair {SK, PK}, which includes a secret (private) key (SK) and a corresponding public key (PK). At 610, the eUICC 108A of the source wireless device 102A uses the generated public key PK to encrypt the symmetric key (used to encrypt one or more subscription service files (e.g., one or more CAP files)). At 612, the eUICC 108A of the source wireless device 102A provides one or more encrypted subscription service files (e.g., one or more encrypted CAP files) to the processor 104A of the source wireless device 102A. One or more encrypted subscription service files (e.g., one or more encrypted CAP files) can be referenced based on the AID value of the mini-program 212, which can be generated from the corresponding one or more subscription service files (e.g., one or more CAP files). At 614, the processor 104A of the source wireless device 102A stores one or more encrypted subscription service files (e.g., one or more encrypted CAP files) locally at the source wireless device 102A and / or remotely at a network-accessible storage device, such as securely stored in cloud network service 302 or other secure remote storage device.One or more encrypted subscription service files (e.g., one or more encrypted CAP files) can later be used when exporting the eSIM 208 to the target wireless device 102B.

[0053] At 616, the processor 104A of the source wireless device 102A can initiate a process to transfer the eSIM 208 from the eUICC 108A of the source wireless device 102A to the eUICC 108B of the target wireless device 102B. At 618, the eUICC 108A of the source wireless device 102A performs a mutual authentication process with the eUICC 108B of the target wireless device 102B. At 620, the eUICC 108B of the target wireless device 102B generates a new elliptic curve cryptography (ECC) asymmetric encryption key pair {eccSK, eccPK}, which includes an ECC secret (private) key (eccSK) and an ECC public key (eccPK). The ECC asymmetric encryption key pair can be used for the secure transmission of the eSIM profile package from the source wireless device 102A to the target wireless device 102B. At position 622, the eUICC 108B of the target wireless device 102B provides the ECC public key eccPK to the eUICC 108A of the source wireless device 102A.

[0054] At 632, the source wireless device 102A's eUICC 108A uses the ECC public key eccPK received from the target wireless device 102B's eUICC 108B to repackage the symmetric key (encrypt the symmetric key). At 634, the source wireless device 102A's eUICC 108A assembles the transferred eSIM 208 into an exportable eSIM profile package, which may include: i) the eSIM's file system; ii) encrypted data, such as Ki and other encryption key materials; iii) personalized (user-specific) applet data (optional); and iv) the encrypted (repackaged) symmetric key. At 636, the source wireless device 102A's eUICC 108A uses the ECC public key eccPK received from the target wireless device 102B's eUICC 108B to encrypt the assembled eSIM profile package. At 638, the source wireless device's eUICC 108A provides the eccPK-encrypted eSIM profile packet to the source wireless device 102A's processor 104A.

[0055] At 640, the processor 104A of the source wireless device 102A retrieves one or more encrypted subscription service files (e.g., one or more encrypted CAP files) associated with the transferred eSIM 208 from local storage and / or from network-accessible remote storage. At 642, the processor 104A of the source wireless device 102A assembles a multi-part eSIM profile export package comprising: i) an eccPK-encrypted eSIM profile package received from the eUICC 108A of the source wireless device 102A; and ii) at least one of the retrieved encrypted subscription service files (e.g., at least one encrypted CAP file). At 644, the processor 104A of the source wireless device 102A transmits the multi-part eSIM profile export package to the processor 104B of the target wireless device 102B for provision to the eUICC 108B of the target wireless device 102B at 646. At 648, the eUICC 108B of the target wireless device 102B may, for example, use one or more subscription service files provided (e.g., one or more CAP files included in the eSIM export package (after decryption)) to install the eSIM 208 and the associated applet 212. In some implementations, the applet 212 is personalized by the eUICC 108B of the target wireless device 102B based on personalized applet data of the applet 212 obtained from the eUICC 108A of the source wireless device 102A.

[0056] Representative equipment Figure 7 Detailed views of a representative computing device 700, according to some embodiments, that can be used to implement the various methods described herein are illustrated. Specifically, these detailed views illustrate various components that may be included in wireless device 102 (such as source wireless device 102A and / or target wireless device 102B). Figure 7As shown, computing device 700 may include a processor 702 representing a microprocessor or controller for controlling the overall operation of computing device 700. Computing device 700 may also include a user input device 708 that allows a user of computing device 700 to interact with computing device 700. For example, user input device 708 may take various forms, such as buttons, keypads, dial pads, touchscreens, audio input interfaces, visual / image capture input interfaces, sensor data input, etc. Furthermore, computing device 700 may include a display 710 that can be controlled by processor 702 to display information to a user. Data bus 716 facilitates data transfer between at least storage device 740, processor 702, and controller 713. Controller 713 can be used to interact with and control different devices via equipment control bus 714. Computing device 700 may also include a network / bus interface 711 communicatively coupled to data link 712. In the case of wireless connectivity, network / bus interface 711 may include a wireless transceiver.

[0057] The computing device 700 also includes a storage device 740, which may include a single disk or multiple disks (e.g., a hard disk drive), and includes a storage management module for managing 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 random access memory (RAM) 720 and read-only memory (ROM) 722. ROM 722 may store programs, utilities, or procedures that will be executed in a non-volatile manner. 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 (SE) 724, such as eUICC 108, UICC 118, or another secure storage device for cellular wireless system access by wireless device 102, source wireless device 102A, and / or target wireless device 102B.

[0058] Wireless terminology According to the various embodiments described herein, the terms "wireless communication device," "wireless device," "mobile wireless device," "mobile station," and "user equipment (UE)" are used interchangeably herein to describe one or more general consumer electronic devices capable of performing processes associated with the various embodiments of this disclosure. According to various specific embodiments, any of these consumer electronic devices may relate to: cellular phones or smartphones, tablet computers, laptop computers, notebook computers, personal computers, netbook computers, media player devices, e-book devices, MiFi devices, etc. ®Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which may include communication via one or more wireless communication protocols, such as protocols for communicating on networks including: 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 Network, Fourth Generation (4G) Long Term Evolution (LTE), LTE-Advanced (LTE-A), and / or 5G or other currently or future advanced cellular wireless networks.

[0059] In some implementations, the wireless communication devices may also operate as part of a wireless communication system that may include a group of client devices, also referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP) (e.g., as part of a WLAN), and / or interconnected with each other (e.g., as part of a WPAN and / or a “self-organizing” wireless network). In some implementations, the client devices may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless LAN communication protocol). In some implementations, WLAN technology may include a Wi-Fi (or more generally, WLAN) wireless communication subsystem or radio component that implements 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 currently or future IEEE 802.11 technologies.

[0060] Furthermore, it should be understood that the UE described herein can be configured as a multi-mode wireless communication device capable of communicating via different third-generation (3G) and / or second-generation (2G) RATs. In these scenarios, the multi-mode UE can be configured to prefer attaching to LTE networks that offer faster data rate throughput compared to other 3G legacy networks that offer lower data rate throughput. For example, in some specific implementations, the multi-mode UE can 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.

[0061] Various aspects, implementations, specific embodiments, or features of the described embodiments may be used individually or in any combination. Various aspects of the described embodiments may be implemented by software, hardware, or a combination of hardware and software. The described embodiments may also be implemented as computer-readable code on a non-transitory computer-readable medium. A non-transitory computer-readable medium is any data storage device capable of storing data that can subsequently be read by a computer system. Examples of non-transitory computer-readable media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices. Non-transitory computer-readable media may also be distributed across network-coupled computer systems, such that the computer-readable code is stored and executed in a distributed manner.

[0062] Regarding this disclosure, it is widely known that the use of personally identifiable information should comply with privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0063] For illustrative purposes, the foregoing description uses specific names to provide a thorough understanding of the described embodiments. However, it will be apparent to those skilled in the art that specific details are not required to practice the described embodiments. Therefore, the foregoing description of specific embodiments is presented for illustrative and descriptive purposes. The foregoing description is not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. It will be apparent to those skilled in the art that many modifications and variations are possible in light of the teachings above.

Claims

1. A method for transferring an electronic subscriber identity module (eSIM) from a source wireless device to a target wireless device, the method comprising: The processor of the source wireless device: Obtain one or more network addresses of one or more mini-program asset servers corresponding to one or more mini-programs, the one or more mini-programs being associated with the eSIM of the eSIM to be transferred from the embedded universal integrated circuit (eUICC) of the source wireless device to the eUICC of the target wireless device; Obtain one or more subscription service files corresponding to the one or more mini-programs of the eSIM from the one or more mini-program asset servers; Generate an eSIM export package that includes the eSIM and at least one of the one or more subscription service files; as well as The eSIM export package is transmitted to the target wireless device.

2. The method of claim 1, wherein at least one of the one or more subscription service files includes a Custom Application (CAMEL) application portion (CAP) file for mobile network enhancement logic.

3. The method according to claim 1, further comprising: Obtain the one or more network addresses of the one or more mini-program asset servers from the eUICC of the source wireless device.

4. The method according to claim 3, wherein: The one or more network addresses include one or more Application Identifier (AID) values; and Each AID value is paired with the network address of the corresponding mini-program asset server in the one or more mini-program asset servers.

5. The method according to claim 1, further comprising: Obtain the one or more network addresses of the one or more mini-program asset servers from the mini-program asset discovery server.

6. The method according to claim 5, further comprising: A first message is sent to the mini-program asset discovery server requesting the one or more network addresses of the one or more mini-program asset servers; as well as The system receives a second message from the mini-program asset discovery server, which includes one or more application identifier (AID) values, each AID value being paired with the network address of a corresponding mini-program asset server among the one or more mini-program asset servers.

7. The method of claim 6, wherein the first message includes the one or more AID values.

8. The method according to claim 5, further comprising: Obtain one or more Application Identifier (AID) values ​​and the network address of the mini-program asset discovery server from the eUICC of the source wireless device.

9. The method according to claim 1, further comprising: For each of the one or more mini-program asset servers: Obtain the AID value of the mini-program associated with the eSIM and the mini-program asset server from the eUICC of the source wireless device; Send a message to the mini-program asset server requesting the subscription service file corresponding to the AID value; as well as Receive the subscription service file from the mini-program asset server. The subscription service file is included in one or more subscription service files included in the eSIM export package.

10. The method of claim 9, wherein the subscription service file includes a newer version of the applet associated with the eSIM installed on the eUICC of the source wireless device.

11. The method according to claim 1, further comprising: Personalized mini-program data associated with each mini-program identified by the corresponding AID value of the eSIM is stored on the eUICC of the source wireless device.

12. The method according to claim 11, further comprising: The personalized mini-program data is transferred to the eUICC of the target wireless device to personalize one or more mini-programs of the eSIM transferred to the target wireless device.

13. A processor for a source wireless device, the processor being configured to: Obtain one or more network addresses of one or more mini-program asset servers corresponding to one or more mini-programs, the one or more mini-programs being associated with an electronic subscriber identity module (eSIM) to be transferred from the embedded universal integrated circuit (eUICC) of the source wireless device to the eUICC of the target wireless device; Obtain one or more subscription service files corresponding to the one or more mini-programs of the eSIM from the one or more mini-program asset servers; Generate an eSIM export package that includes the eSIM and at least one of the one or more subscription service files; as well as The eSIM export package is transmitted to the target wireless device.

14. The processor of claim 13, wherein at least one of the one or more subscription service files includes a Custom Application (CAMEL) application portion (CAP) file for mobile network enhancement logic.

15. The processor according to claim 13, wherein: The processor is also configured to obtain the one or more network addresses of the one or more mini-program asset servers from the eUICC of the source wireless device; The one or more network addresses include one or more application identifier (AID) values; as well as Each AID value is paired with the network address of the corresponding mini-program asset server in the one or more mini-program asset servers.

16. The processor of claim 13, further configured to: Obtain the one or more network addresses of the one or more mini-program asset servers from the mini-program asset discovery server; A first message is sent to the mini-program asset discovery server requesting the one or more network addresses of the one or more mini-program asset servers, the first message including one or more application identifier (AID) values; and The system receives a second message from the mini-program asset discovery server, which includes one or more AID values, each AID value being paired with the network address of a corresponding mini-program asset server among the one or more mini-program asset servers.

17. The processor of claim 13, further configured to: Obtain one or more Application Identifier (AID) values ​​and the network address of the Mini Program Asset Discovery Server from the eUICC of the source wireless device; and Obtain the one or more network addresses of the one or more mini-program asset servers from the mini-program asset discovery server.

18. The processor of claim 13, further configured to: For each of the one or more mini-program asset servers: Obtain the AID value of the mini-program associated with the eSIM and the mini-program asset server from the eUICC of the source wireless device; Send a message to the mini-program asset server requesting the subscription service file corresponding to the AID value; as well as Receive the subscription service file from the mini-program asset server. in: The subscription service file is included in one or more subscription service files included in the eSIM export package; as well as The subscription service file includes a newer version of the applet associated with the eSIM installed on the eUICC of the source wireless device.

19. The processor of claim 13, further configured to: Personalized mini-program data associated with each mini-program identified by the corresponding AID value of the eSIM is stored on the eUICC of the source wireless device; and The personalized mini-program data is transferred to the eUICC of the target wireless device to personalize one or more mini-programs of the eSIM transferred to the target wireless device.

20. A non-transitory computer-readable medium storing instructions for configuring a processor of a source wireless device, the instructions comprising: Instructions for obtaining one or more network addresses of one or more mini-program asset servers corresponding to one or more mini-programs, the one or more mini-programs being associated with an electronic subscriber identity module (eSIM) to be transferred from the embedded universal integrated circuit (eUICC) of the source wireless device to the eUICC of the target wireless device; Instructions for obtaining one or more subscription service files corresponding to the one or more mini-programs of the eSIM from the one or more mini-program asset servers; Instructions for generating an eSIM export package that includes the eSIM and at least one of the one or more subscription service files; as well as Instructions for transmitting the eSIM export package to the target wireless device.

21. A method for transferring an electronic subscriber identity module (eSIM) from a source wireless device to a target wireless device, the method comprising: The processor of the source wireless device: Retrieve one or more encrypted subscription service files corresponding to one or more applets of the eSIM to be transferred from the embedded universal integrated circuit card (eUICC) of the source wireless device to the eUICC of the target wireless device from the local storage device at the source wireless device or from the remote storage device at the network-accessible server; Generate an eSIM export package that includes at least one decrypted version of the eSIM and the one or more encrypted subscription service files; as well as The eSIM export package is transmitted to the target wireless device.

22. The method of claim 21, wherein generating the eSIM export package comprises: Transmit the one or more encrypted subscription service files to the eUICC of the source wireless device; as well as The eSIM export packet is received from the eUICC of the source wireless device.

23. The method of claim 21, wherein at least one of the encrypted subscription service files comprises an encrypted Custom Application (CAMEL) application portion (CAP) file of Mobile Network Enhancement Logic.

24. The method of claim 21, further comprising: The one or more encrypted subscription service files are received from the eUICC of the source wireless device in connection with the process of installing the eSIM on the eUICC of the source wireless device; as well as The one or more encrypted subscription service files are stored on the local storage device at the source wireless device or on the remote storage device at the network-accessible server.

25. The method of claim 24, wherein the one or more encrypted subscription service files received from the eUICC of the source wireless device are organized by an associated application identifier (AID) value.

26. The method according to claim 21, further comprising: Obtain an array of AID values ​​corresponding to the one or more applets associated with the eSIM from the eUICC of the source wireless device.

27. The method of claim 26, wherein retrieving the one or more encrypted subscription service files from the local storage device or the remote storage device is based at least in part on the array of AID values.

28. The method of claim 21, further comprising: Save personalized mini-program data associated with each mini-program identified by the corresponding AID value of the eSIM; as well as The personalized mini-program data is transferred to the eUICC of the target wireless device to personalize one or more mini-programs of the eSIM transferred to the target wireless device.

29. A processor for a source wireless device, the processor being configured to: Retrieve one or more encrypted subscription service files corresponding to one or more applets of the electronic subscriber identity module (eSIM) of the embedded universal integrated circuit card (eUICC) to be transferred from the source wireless device to the eUICC of the target wireless device from the local storage device or from the remote storage device of the network-accessible server; Generate an eSIM export package that includes at least one decrypted version of the eSIM and the one or more encrypted subscription service files; as well as The eSIM export package is transmitted to the target wireless device.

30. The processor of claim 29, further configured to generate the eSIM export package by at least the following manner: Transmit the one or more encrypted subscription service files to the eUICC of the source wireless device; and The eSIM export packet is received from the eUICC of the source wireless device.

31. The processor of claim 29, wherein at least one of the encrypted subscription service files comprises an encrypted Custom Application (CAMEL) application portion (CAP) file of Mobile Network Enhancement Logic.

32. The processor of claim 29, further configured to: In connection with the process of installing the eSIM on the eUICC of the source wireless device, the one or more encrypted subscription service files are received from the eUICC of the source wireless device; and The one or more encrypted subscription service files are stored on the local storage device at the source wireless device or on the remote storage device at the network-accessible server.

33. The processor of claim 32, wherein the one or more encrypted subscription service files received from the eUICC of the source wireless device are organized by an associated application identifier (AID) value.

34. The processor of claim 29, further configured to: Obtain an array of AID values ​​corresponding to the one or more applets associated with the eSIM from the eUICC of the source wireless device.

35. The processor of claim 34, wherein retrieving the one or more encrypted subscription service files from the local storage device or the remote storage device is based at least in part on the array of AID values.

36. The processor of claim 29, further configured to: Storing personalized mini-program data associated with each mini-program identified by the corresponding AID value of the eSIM; and The personalized mini-program data is transferred to the eUICC of the target wireless device to personalize one or more mini-programs of the eSIM transferred to the target wireless device.

37. A method for managing one or more subscription service files corresponding to one or more applets of an Electronic Subscriber Identity Module (eSIM) to be transferred from a source wireless device to a target wireless device: By Mini Program Asset Server: A first message is received from the source wireless device requesting one or more subscription service files corresponding to the one or more applets of the eSIM, the first message including one or more application identifier (AID) values ​​corresponding to the one or more applets of the eSIM; and A second message, including the one or more subscription service files, is transmitted to the source wireless device.

38. The method of claim 37, wherein the one or more subscription service files include a Custom Application (CAMEL) application portion (CAP) file for mobile network enhancement logic.

39. The method of claim 37, wherein the one or more subscription service files include a subscription service file corresponding to a version of the applet of the eSIM installed together with the eSIM on the embedded universal integrated circuit card (eUICC) of the source wireless device.

40. The method of claim 37, wherein the one or more subscription service files include a subscription service file corresponding to a newer version of the applet of the eSIM installed together with the eSIM on the embedded universal integrated circuit card (eUICC) of the source wireless device.

Images