Reuse operation for eSIM download and transfer

Abstract

Provides reuse functionality for eSIM download and transfer. [Solution] An apparatus or method for storing records of a plurality of embedded subscriber identification module (eSIM) profiles, wherein each record of the eSIM profile includes the state of the eSIM profile, and the apparatus or method includes receiving a message from a first user device (UE) indicating that the first eSIM profile has been removed from the first UE, changing the state of the first eSIM profile from installed to available, receiving a message requesting that the first eSIM profile be assigned to a second UE, changing the state of the first eSIM profile to a state that allows the eSIM profile to be downloaded to the second UE, and downloading the first eSIM profile to the second UE.

Description

Technical Field

[0001] Inventors: Raj S Chaugule, Li Li, Rohan C Malthankar, Sherman X Jin and Suraj Gupta Priority / Incorporation by Reference This application claims priority to U.S. Provisional Application No. 63 / 505,779, filed Jun. 2, 2023, entitled “Reuse Operations for eSIM Download and Transfer,” which is hereby incorporated by reference in its entirety.

Background Art

[0002] Existing implementations of user equipment (UE) embedded subscriber identity module (eSIM) operations have several areas that need improvement. Creating new eSIM profiles represents an ongoing cost for mobile network operators (MNOs). With billions of eSIM devices being used worldwide and more eSIM devices expected to be deployed in the future, MNOs desire to reduce the costs associated with creating new eSIM profiles. There is a need to develop means to reuse eSIM profiles across different devices. Summary

[0003] Some exemplary embodiments are a method for storing records of multiple embedded subscriber identification module (eSIM) profiles, each eSIM profile record including the state of the eSIM profile, receiving a message from a first user device (UE) indicating that the first eSIM profile has been removed from the first UE, changing the state of the first eSIM profile from installed to available, receiving a message requesting that the first eSIM profile be assigned to a second UE, changing the state of the first eSIM profile to a state that allows the eSIM profile to be downloaded to the second UE, and downloading the first eSIM profile to the second UE.

[0004] Other exemplary embodiments include a method for sending a delete plan request to a source user device (UE) to delete an embedded subscriber identification module (eSIM) profile, sending a request to an entitlement server for the eSIM profile, receiving a response from the entitlement server containing information for retrieving the eSIM profile, fetching the eSIM profile from a subscription manager-data preparation+ (SM-DP+), installing the eSIM profile, and sending confirmation to the SM-DP+ that the eSIM profile has been installed.

[0005] Further exemplary embodiments include a method for receiving a deletion plan request from a target UE to delete an embedded subscriber identification module (eSIM) profile, deleting the eSIM profile, and sending an indication that the eSIM profile has been deleted from the source UE.

[0006] An additional exemplary embodiment relates to a method for receiving a push notification registration from a source user device (UE) for a push notification relating to the transfer of an embedded subscriber identity module (eSIM) profile installed on the source UE; receiving a request from a target UE to install an eSIM on the target UE; sending a push notification to the source UE indicating that the source UE will delete the eSIM profile; receiving an indication from the source UE that the eSIM profile has been deleted; sending a request to a Subscription Manager-Data Preparation+ (SM-DP+) indicating that the eSIM profile will be transferred to the target UE; receiving a response from SM-DP+ indicating that the eSIM profile will be transferred to the target UE, wherein the response includes the SM-DP+'s Universal Resource Locator (URL); and sending a response to the target UE for the request to install an eSIM on the target UE, wherein the response includes the SM-DP+'s URL.

[0007] Further exemplary embodiments include a method for scanning a Quick Response (QR) code displayed by a source user device (UE), determining QR code information from the scanned QR code, which relates to the transfer of an embedded subscriber identification module (eSIM) profile from the source UE to the target UE, sending a request for the eSIM profile to a carrier server, receiving a response from the carrier server containing information for retrieving the eSIM profile, which includes a Universal Resource Locator (URL) for the Subscription Manager-Data Preparation+ (SM-DP+), fetching the eSIM profile from the SM-DP+, installing the eSIM profile, and sending confirmation to the SM-DP+ that the eSIM profile has been installed.

[0008] A further exemplary embodiment relates to a method for sending a push notification registration to a carrier server for a push notification related to the transfer of an embedded subscriber identification module (eSIM) profile installed on a source user device (UE), generating a quick response (QR) code containing QR code information displayed by the source UE, the QR code information being related to the transfer of an eSIM profile from the source UE to a target UE, receiving a push notification from the carrier server indicating that the source UE has deleted the eSIM profile, and sending an indication to the carrier server that the eSIM profile has been deleted.

[0009] Further exemplary embodiments include a method for storing records of a plurality of embedded subscriber identification module (eSIM) profiles, each eSIM profile record including the state of the eSIM profile, receiving a request for a first eSIM profile from a first user device (UE), sending the first eSIM profile to the first UE, receiving a first indication from a second UE that a second eSIM profile has been deleted from the second UE, the first UE and the second UE being associated with the same account, receiving and updating the state of the second eSIM profile to be available in response to the first indication, receiving a second indication from the first UE that the first eSIM profile has been installed in the first UE, and installing the state of the first eSIM profile in response to the second indication.

[0010] Further additional exemplary embodiments relate to a method for receiving a setup profile request from an entitlement server for an embedded subscriber identification module (eSIM) profile for a user device (UE), configuring the eSIM profile for the UE, and sending a push notification to the UE, the push notification containing information for the UE to fetch the eSIM profile.

[0011] Another exemplary embodiment relates to a method for receiving a request from a target user device (UE) for a list of devices associated with a phone number, sending a response to the target UE containing the list of devices associated with the phone number, and sending a request to the source UE to remove an embedded subscriber identification module (eSIM) profile associated with the phone number.

[0012] Another exemplary embodiment is a method for scanning a quick response (QR) code generated by a mobile network operator, determining QR code information from the scanned QR code, wherein the QR code information relates to a first embedded subscriber identification module (eSIM) profile and includes a universal resource locator (URL) for a Subscription Manager-Data Preparation+ (SM-DP+), fetching the first eSIM profile from SM-DP+, sending a phone number list request to an Original Equipment Manufacturer (OEM) cloud server, receiving a phone number list response from the OEM cloud server containing a list of devices associated with the phone numbers of the first eSIM profile, sending a delete plan request to a source user device (UE), which is one of the devices associated with the phone numbers, to delete a second eSIM profile associated with the phone number, installing the first eSIM profile, and sending a confirmation to SM-DP+ that the first eSIM profile has been installed.

[0013] Further exemplary embodiments relate to a method for receiving a deletion plan request from a target user device (UE) containing a first embedded subscriber identification module (eSIM) profile associated with a telephone number, for deleting a second eSIM profile associated with a telephone number, deleting the second eSIM profile, and sending confirmation to the Subscription Manager-Data Preparation+ (SM-DP+) that the second eSIM profile has been deleted.

[0014] An additional exemplary embodiment relates to a method for sending a deletion plan request to a source user device (UE) to delete an embedded subscriber identification module (eSIM) profile, receiving a deletion notification from the source UE indicating that the eSIM profile has been deleted from the source UE, and sending the deletion notification to a subscription manager-data preparation+ (SM-DP+).

[0015] Another exemplary embodiment relates to a device having a processor and memory coupled to the processor, wherein the processor is configured to prepare a deletion plan request to send to a source user device (UE) requesting the deletion of an embedded subscriber identification module (eSIM) profile on the source UE, prepare an entitlement server request for the eSIM profile, receive a response containing information for retrieving the eSIM profile in response to the sending of the entitlement server request, retrieve the eSIM profile from the Subscription Manager-Data Preparation+ (SM-DP+), install the eSIM profile, and prepare a confirmation to be sent to the SM-DP+ indicating that the eSIM profile has been installed.

[0016] A further exemplary embodiment relates to a device having a processor and memory coupled to the processor, wherein the processor is configured to receive a deletion plan request from a target user device (UE) to delete an embedded subscriber identification module (eSIM) profile from a source UE, delete the eSIM profile, and prepare an indication that the eSIM profile has been deleted from the source UE. [Brief explanation of the drawing]

[0017] [Figure 1] This document illustrates exemplary network configurations in various exemplary embodiments.

[0018] [Figure 2] This section illustrates exemplary UEs by various exemplary embodiments.

[0019] [Figure 3] Shows a first call flow according to various exemplary embodiments.

[0020] [Figure 4] Shows a second call flow according to various exemplary embodiments.

[0021] [Figure 5] Shows a third call flow according to various exemplary embodiments.

[0022] [Figure 6] Shows a fourth call flow according to various exemplary embodiments.

[0023] [Figure 7] Shows a fifth call flow according to various exemplary embodiments.

Mode for Carrying Out the Invention

[0024] Exemplary embodiments can be further understood by referring to the following description and the related accompanying drawings, and the same reference numerals are assigned to the same elements. Exemplary embodiments relate to improved operations for the download and transfer of eSIM.

[0025] Exemplary embodiments are described with respect to a user equipment (UE). However, the reference to the UE is provided merely for illustration. Exemplary embodiments may be used in any electronic component, and any electronic component can establish a connection to a network and is composed of hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described in this specification is used to represent any electronic component.

[0026] The exemplary embodiments are also described in relation to 5G New Radio (NR) networks. However, the exemplary embodiments may also be implemented in other types of networks, including but not limited to LTE networks, future evolutions of cellular protocols (6G networks), or any other type of network using eSIMs.

[0027] By the end of 2025, it is expected that there will be 2.4 billion eSIM-connected devices (i.e., UEs). Each of these UEs has an associated eSIM profile used to receive cellular services from an MNO. When a user purchases a new UE, the MNO typically bears the cost associated with generating a new eSIM profile.

[0028] eSIM profiles can have various states. An eSIM profile in an available state may be used by an MNO. Once an eSIM profile is installed on a UE, it enters an installed state. An installed eSIM profile cannot be reused, even with the same phone number. Therefore, a user with a new UE (e.g., upgrading a device) will receive a new eSIM profile from the MNO when transferring their phone number to the new UE.

[0029] Despite MNOs paying for these new eSIM profiles, older eSIM profiles (from older UEs) remain linked to the old UE's Embedded Universal Integrated Circuit Card (eUICC) identifier (EID). This represents a recurring cost for MNOs. Exemplary embodiments provide a way for MNOs to reduce this cost by enabling the reuse of eSIM profiles. For example, several exemplary embodiments relate to deleting eSIM profiles from older UEs and transitioning them to a usable state. This makes it possible to use the same eSIM profile with the new UE. Exemplary embodiments relate to improvements in the UE and network handling of eSIM profiles between UEs. Exemplary embodiments are described in more detail below.

[0030] Figure 1 shows an exemplary network configuration 100 in various exemplary embodiments. The exemplary network configuration 100 includes UE 110. UE 110 may be any type of electronic component configured to communicate over the network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable, or Internet of Things (IoT) device. An actual network configuration may include any number of UEs used by any number of users. Therefore, the example of one UE 110 is provided solely for illustrative purposes. The exemplary network configuration 100 also includes UE 112. UE 112 may be functionally equivalent to UE 110. In the exemplary embodiment, UE 110 may be a device that currently has an installed eSIM profile (e.g., an older device), and UE 112 may be a target device for an eSIM transfer operation (e.g., a newer device).

[0031] UEs 110 and 112 may be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UEs 110 and 112 can communicate wirelessly is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next-generation RAN (NG-RAN), legacy cellular network, etc.), and UE 110 may also communicate with networks via wired connections. With respect to exemplary embodiments, UEs 110 and 112 may establish a connection with the 5G NR RAN 120. Thus, UE 110 may have a 5G NR chipset to communicate with the NR RAN 120. Once an eSIM profile is installed on the UEs, UEs 110 and 112 may communicate with one or more networks. Exemplary embodiments describe this installation and the transfer of the eSIM profile between UEs 110 and 112 in more detail.

[0032] 5G NR RAN 120 may be part of a cellular network that can be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc.). RAN 120 may include cells or base stations configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. In this example, 5G NR RAN 120 includes gNB 120A. However, the reference to gNB is given for illustrative purposes only, and any appropriate base station or cell (e.g., node B, enode B, HeNB, eNB, gNB, gNodeB, macrocell, microcell, small cell, femtocell, etc.) may be deployed.

[0033] Any coupling procedure may be performed for UEs 110 and 112 to connect to the 5G NR RAN 120. For example, as described above, the 5G NR RAN 120 may be associated with a specific network carrier, and in that specific network carrier, UE 110 and / or the user of UE 110 have contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR RAN 120, UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120. More specifically, UEs 110 and 112 may be associated with a specific cell (e.g., gNB 120A).

[0034] The network configuration 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to UEs 110 and 112 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 in order to provide multimedia services to the UEs 110 and 112. The network services backbone 160 communicates with the Internet 140 and the cellular core network 130 either directly or indirectly. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0035] Figure 2 shows an exemplary UE 110 in various exemplary embodiments. The UE 110 is described in relation to the network configuration 100 of Figure 1. The UE 110 can represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a battery providing limited power, a data acquisition device, ports for electrically connecting the UE 110 to other electronic devices, and sensors for detecting the state of the UE 110. The eUICC 240 may be a hardware component integrated into the UE 110, configured to store several carrier profiles.

[0036] The processor 205 may be configured to run multiple engines for the UE 110. For example, the engines may include an eSIM transfer engine 235 for performing operations related to improved eSIM transfer between the UE 110 and the UE 112. The eSIM transfer engine may also perform a Local Profile Assistant (LPA) function that allows the UE 110 to download an encrypted profile to the eUICC 240 of the UE 110.

[0037] The engine described above, which is an application (e.g., a program) executed by processor 205, is merely an example. The functionality associated with the engine may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving signals and a processing circuit for processing signals and other information. The engine may also be embodied as one application or a separate application. In addition, in some UEs, the functionality described for processor 205 is divided among two or more processors, such as a baseband processor and an application processor. Exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0038] The memory device 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to the user, and the I / O device 220 may be a hardware component that allows the user to make inputs. The display device 215 and the I / O device 220 may be separate components or may be integrated together, such as a touchscreen. The transceiver 225 may be a hardware component configured to establish a connection with the 5G-NR RAN 120. Thus, the transceiver 225 may operate at various different frequencies or channels (e.g., a continuous set of frequencies). The transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded with information implementing any one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive signals from and / or transmit signals to the transceiver 225. The processor 205 may be configured to encode and / or decode signals (e.g., signaling from a base station of a network) in order to implement any one of the methods described herein.

[0039] As described above, in exemplary embodiments, UE 110 may be an older device, for example, a device on which the eSIM profile is currently installed. UE 112 is considered to be a newer device, for example, a target device on which the eSIM profile is to be installed. The above description of UE 110 is also applicable to UE 112. For example, the eSIM transfer engine 235 may be used by the older device (e.g., UE 110) to perform the operations described below during an exemplary transfer operation. Similarly, the eSIM transfer engine 235 may be used by the newer device (e.g., UE 112) to perform the operations described below during an exemplary transfer operation.

[0040] The exemplary embodiments relate to improved UE and network processing for eSIM profile transfer between UEs. Multiple exemplary use cases may exist for transferring eSIM profiles between UEs. These exemplary use cases are described in more detail below.

[0041] In a first aspect of an exemplary embodiment, eSIM transfer using UE proximity is disclosed. As described above, throughout the entirety of this disclosure, UE 110 may be a source UE (e.g., an old UE) and UE 112 may be a target UE (e.g., a new UE). UE 110 may have an associated telephone number (and eSIM). As described above, UEs 110 and 112 may include an LPA (e.g., an application residing on the UE or eUICC) that can be used to manage the eSIM profiles of UEs 110 and UE 112. Operations related to managing eSIM profiles may include downloading a new eSIM profile, activating an eSIM profile, deactivating an eSIM profile, deleting an eSIM profile, and so on.

[0042] Figure 3 shows a first call flow 300 in various exemplary embodiments. The description of the call flow 300 may describe the first embodiment. Figure 3 shows an SM-DP+ 302, which is a network element (typically a server) that prepares, stores, and protects carrier profiles (including operator credentials). The SM-DP+ 302 may also download and install profiles to a UE eUICC (e.g., eUICC 240). Other entities or networks may refer to the SM-DP+ by other names. Figure 3 also shows an entitlement server 304, which enables the radio configuration of the UE eSIM. Figure 3 also shows UE 112 (target device) and UE 110 (source device). In this example, UE 110 and UE 112 may be considered to be physically close to each other throughout the operation of the call flow 300.

[0043] In 310, SM-DP+302 has the profile state "Installed" associated with the eSIM profile installed on UE 110. This is a typical state for an eSIM profile on a UE used by a user who has a cellular contract with an MNO during the UE's lifespan.

[0044] In 312, UE 112 sends a transfer profile request to UE 110. This can be initiated by the user through interaction on UE 112. As mentioned above, in this scenario, UE 110 and UE 112 are in close proximity to each other. Therefore, UE 112 can send the transfer profile request using any short-range protocol or communication method such as Bluetooth, short-range Wi-Fi, near-field communication (NFC), or infrared.

[0045] In step 314, UE 110 sends a transfer permission request to entitlement server 304. The transfer permission request notifies the entitlement server that it is requesting that the eSIM profile on UE 110 be transferred. The transfer permission request may include any information that entitlement server 304 can use to authorize the transfer of the eSIM profile, such as the eSIM profile identification (ID), the ID of UE 110, the ID of UE 112, the subscriber ID, etc.

[0046] At 316, the entitlement server 304 sends a forwarding permission response. In call flow 300, the forwarding permission response is considered positive, and call flow 300 continues. However, if the forwarding permission response is negative, call flow 300 terminates.

[0047] In step 318, UE 110 sends a transfer profile indication to UE 112. Indication 318 informs UE 112 to proceed with the call flow 300 and to send a transfer authorization request 320 to the entitlement server 304. At this point, UE 112 does not have an eSIM profile and therefore typically cannot access the cellular network at this time. However, UE 112 may have WiFi access and can use WiFi access to contact the entitlement server 304. Therefore, in step 320, UE 112 sends a transfer authorization request to the entitlement server 304.

[0048] In 322, the entitlement server responds to UE 112 with a transfer permission response. In this case as well, the transfer permission request 320 may contain any information that the entitlement server 304 can use to authorize the transfer of the eSIM profile, as shown above. A negative transfer permission response would terminate the call flow 300, so a transfer permission response can again be considered positive. Operations 324-322 may be described as preflight operations, for example, operations used to prepare the device to perform a transfer, but may not be part of the transfer operation. In this example, these preflight operations are related to authorization. Other types of preflight operations related to authorization may exist, including obtaining an authorization token, as will be described in more detail below. Any of these preflight operations may be used in conjunction with any of the transfer call flow operations; for example, in this example, the authorization token described below may be used instead of using operations 324-322.

[0049] In step 324, UE 112 sends a delete plan request to UE 110. The delete plan request 324 notifies UE 110 that the eSIM profile should be deleted. In step 326, UE 110 deletes the eSIM profile. This delete 326 erases the eSIM profile from the device (e.g., eUICC 240), and as a result, following 326, UE 110 no longer has access to the eSIM profile. However, it should be noted that at the end of 326, SM-DP+ 302 is not yet aware that the profile has been deleted from UE 110.

[0050] In step 328, the UE 110 sends a deletion notification to the SM-DP+302 to inform the SM-DP+302 that the eSIM profile has been deleted from the UE 110. As described above, once the UE 110 deletes the eSIM profile, the UE 110 can no longer have access to cellular services, and as a result, the UE 110 may have to contact the SM-DP+302 using an alternative connection, such as Wi-Fi. In some exemplary embodiments, it is possible for the UE 110 to send the deletion notification 328 using a cellular connection before the actual deletion 326.

[0051] In operation 330, SM-DP+302 updates the eSIM profile status from installed to available. This coincides with UE 110 deleting the profile in operation 326. Since the eSIM profile is now available, it can be used by a new UE (e.g., UE 112). Thus, at the end of operation 330, the eSIM profile is available for reuse.

[0052] In step 334, UE 110 sends a delete plan response to UE 112. Response 334 notifies UE 110 that UE 112 has successfully deleted the eSIM profile and notifies SM-DP+302 of the eSIM profile deletion (in step 328).

[0053] In step 336, UE 112 sends a transfer SIM service message to the entitlement server 304. Message 336 notifies the entitlement server 304 that UE 112 should receive SIM services from an older UE (e.g., UE 110). Message 336 includes a source device (UE 110) integrated circuit card identification number (ICCID) profile, including the SRC ICCID.

[0054] In step 338, the entitlement server 304 sends an ES2+ message to the SM-DP+302 indicating that the UE 112 is ready to receive the eSIM profile. ES2+ is the interface for the UE 112 to communicate with the SM-DP+302.

[0055] In step 340, SM-DP+ updates the eSIM profile status from Available to Linked, and then to Verified. The Linked status indicates that the eSIM profile is reserved for download and linked to an Embedded Identification Document (EID), e.g., the serial number attached to the device using the eSIM. In this example, the EID is the EID of UE 112. The Verified status indicates that the eSIM profile is reserved for download, along with a Matching ID (e.g., a unique ID for each connection) and a Verification Code (e.g., a carrier-provided code), if necessary.

[0056] At step 342, the entitlement server 304 sends a transfer SIM response message 342 to the UE 112. Message 342 includes the ICCID. At step 344, the SM-DP+ 302 sends the eSIM profile to the UE 112. At step 346, the SM-DP+ 302 updates the profile status from confirmed to downloaded.

[0057] At step 348, UE 112 installs the eSIM profile containing the EID from UE 110 (maintaining the same EID). At step 350, UE 112 sends a profile fetch message response to SM-DP+302 indicating that the profile has been installed.

[0058] In step 352, SM-DP+302 updates the profile status from downloaded to installed. Step 300 of the call flow may be repeated again at a future time when the user upgrades or changes the device from UE 112.

[0059] In a second aspect of the exemplary embodiment, eSIM transfer via a Quick Response (QR) code and an Original Equipment Manufacturer (OEM) cloud service is disclosed. The QR code can be rapidly generated by the source UE to supply the target UE with the profile information necessary to initiate the eSIM transfer.

[0060] Figure 4 shows a second call flow 400 in various exemplary embodiments. Call flow 400 may illustrate a second aspect. The entitlement server 404 and SM-DP+ 402 are substantially similar to the entitlement server 304 and SM-DP+ 302 described with reference to Figure 3. Figure 4 features an OEM cloud server 405, which may be a server having associated account information linked to a specific user account. For example, the OEM cloud server may know which UE is associated with a given OEM user account or phone number (smartphone, tablet, smartwatch, etc.). In this example, UE 110 and UE 112 may be considered to be in close proximity to each other.

[0061] In 406, UE 110 sends a transfer token request to entitlement server 404. In 407, entitlement server 404 responds to UE 110 with a transfer token. In some exemplary embodiments, the transfer token request 406 may be initiated by a user of UE 110. For example, a user may have acquired a new device (e.g., UE 112) and want to initiate an eSIM profile transfer operation. As part of initiating the transfer, the user may request UE 110 to acquire a transfer token and perform the transfer. In other exemplary embodiments, the acquisition of the transfer token may be performed transparently to the user, for example, when a user acquires a new device, all devices associated with the user's account may automatically request a transfer token so that the user can select one of the devices for the transfer. The transfer token can be thought of as an authorization token that enables UE 110 to perform operations related to eSIM profile transfer, e.g., the example of the preflight operation described above. The transfer token may be valid for a predetermined time period, e.g., 1 hour, 12 hours, 24 hours, etc.

[0062] In this example, the transfer token is obtained from the entitlement server 404. However, the transfer token does not necessarily have to be obtained from the entitlement server 404. For example, the transfer token can be obtained from any carrier-related device or function.

[0063] In operation 410, the source UE (e.g., UE 110) generates a QR code. The QR code may include one or more of the following: ICCID, Mobile Country Code (MCC), Mobile Network Code (MNC), Group 1 Identifier (GID1), Group 2 Identifier (GID2), International Mobile Subscriber Identification Number (IMSI), Transfer Token (received in operation 407), Indication of whether the plan is active (i.e., whether the user has a cellular plan with an MNO), International Mobile Device Identification Number (IMEI), Embedded Identification Document (EID), Serial Number, Label, Telephone Number, UE Software Version, Product Class (e.g., iPhone®, iPad®).

[0064] In step 412, the target UE (e.g., UE 112) scans the QR code via its camera. The scanning operation 412 also includes UE 112 decoding the information contained in the QR code.

[0065] In step 414, the UE 112 sends a phone number list request to the OEM cloud server 405 (e.g., iCloud). The purpose of request 414 is to know which UEs are associated with a given phone number. For example, a user may have a smartphone, smartwatch, tablet, and laptop associated with a phone number, thereby allowing the user to answer calls on any of the devices associated with the phone number. This information ensures that only older UEs 110 (e.g., the one displaying the QR code in step 410) lose access to the phone number. For example, a user who owns both a smartwatch and a smartphone is likely to want to retain access to the phone number on their smartwatch when upgrading their smartphone.

[0066] In step 416, the OEM cloud server 405 responds to UE 112 with a list of devices that will use the phone number. UE 112 can then select the correct device (e.g., UE 110) that should lose access to the phone number and continue the call flow 400 using that device (e.g., UE 110).

[0067] In step 418, UE 112 sends a deletion plan request to UE 110. This request notifies UE 110 to delete its eSIM profile (and associated phone number). In step 420, UE 110 deletes the eSIM profile and associated phone number. UE 110 can no longer make or receive calls using the eSIM profile or phone number.

[0068] In step 422, the UE 110 sends a deletion notification to the SM-DP+402 indicating that the deletion operation 420 is complete. Using this information, the SM-DP+402 knows that the eSIM profile is no longer on the UE 110 and can update the eSIM profile status. Therefore, in step 424, the SM-DP+402 updates the profile status from installed to available.

[0069] At 426, UE 112 sends an eSIM installation request to entitlement server 404. At 428, entitlement server 404 sends an eSIM profile request 428 to SM-DP+402.

[0070] At 430, SM-DP+402 responds to Entitlement Server 404 with information related to the eSIM profile (i.e., the profile initially installed on UE 110), including the SM-DP+URL. As mentioned above, since the eSIM profile that was originally on UE 110 is now available, SM-DP+402 can select that eSIM profile for reuse.

[0071] At 432, the entitlement server 404 sends the SM-DP+ URL to the UE 112. At 434, the UE 112 sends a fetch profile request to the SM-DP+ 402 (via its newly obtained SM-DP+ URL from 432). At 436, the SM-DP+ 402 sends the eSIM profile to the UE 112.

[0072] At step 438, UE 112 installs the eSIM profile. At step 440, UE 112 sends a profile installed notification to SM-DP+402 informing it that the eSIM profile has been installed. At step 442, SM-DP+402 updates the eSIM profile status to installed in response to receiving the profile installed notification.

[0073] The eSIM profile status may be updated multiple times during call flow 400. For example, as described above, in response to UE 110 deleting the profile and indicating its deletion to SM-DP+402, the eSIM profile status is updated at 424 from installed to available. The eSIM profile status may be updated from available to linked, and then to confirmed, during the operations related to 436 and 438. Similarly, during the same operations, the eSIM profile may be updated from confirmed to released. The released status indicates that the eSIM profile is ready for download and installation after network configuration by the operator (e.g., Home Location Register (HLR) registration). Another update to the eSIM profile status may be released and then downloaded when the eSIM profile is fetched by UE 112, for example after 436. Thus, when SM-DP+402 receives the profile installed notification at 440, the eSIM profile status is updated to installed.

[0074] At the end of call flow 400, UE 112 is operating with the eSIM profile originally installed on UE 110, along with the associated phone number. No new eSIM profile was generated for UE 112.

[0075] In a third aspect of the exemplary embodiment, operations related to remote eSIM removal are disclosed herein. Figure 5 shows a third call flow 500 according to various exemplary embodiments. The call flow 500 may illustrate the third aspect.

[0076] Call flow 500 features an SM-DP+502 which is substantially the same as the SM-DP+302 shown in Figure 3. Figure 5 also features an MNO server 504. The MNO server 504 may be a server operated by the mobile network operator to which the user subscribes to cellular services.

[0077] Operations 506 and 507 are substantially the same as operations 406 and 407 described above with reference to Figure 4. The difference between operations 506 and 507 and operations 406 and 407 is that UE 110 obtains the transfer token from the MNO server 504 instead of the entitlement server. However, as explained above, the operations are merely examples, and UE 110 may also obtain the transfer token from the MNO server in 406 and 407.

[0078] In 508, UE 110 registers for push notifications from MNO server 504. As will be described in more detail below, MNO server 504 may also push eSIM profile deletion notifications to UE 110. In order for UE 110 to receive these push notifications, UE 110 registers for push notifications in 508.

[0079] Operations 510 and 512 are substantially similar to operations 410 and 412 described with reference to Figure 4. In this example, UE 110 and UE 112 are considered to be in close proximity to each other, and for example, UE 112 can scan the QR code on UE 110. Examples of the types of information that may be contained in a QR code are described above.

[0080] At 512, UE 112 scans the QR code, and at 514, UE 112 sends an Install eSIM message to MNO server 504. In the previous example, UE 112 sent a Delete Plan message to UE 110 to delete the eSIM profile. However, in this exemplary scenario, the Delete Plan message is sent remotely from UE 110. Specifically, at 516, MNO server 504 sends a Delete Plan push notification to UE 110. The Delete Plan push notification 516 notifies UE 110 that the eSIM profile should be deleted. As mentioned above, UE 110 has previously signed up to receive push notifications from MNO server 504.

[0081] At 518, UE 110 deletes the eSIM profile. At 520, UE 110 sends a deletion notification to SM-DP+502. This notification 520 informs SM-DP+502 that the eSIM profile has been deleted so that SM-DP+502 can proceed with updating the eSIM profile status. At 522, SM-DP+502 updates the eSIM profile status from installed to available, consistent with UE 110's knowledge from notification 520 that it has deleted the profile.

[0082] At step 524, UE 110 sends a deletion plan response message to MNO server 504. MNO server 504 then learns that the profile has been deleted from UE 110 (and that the profile is now available to UE 112).

[0083] At 526, the MNO server 504 sends an eSIM profile request to the SM-DP+ 502. At 528, the SM-DP+ 502 responds to the MNO server 504 with information related to the eSIM profile (i.e., the profile initially installed on the UE 110), including the SM-DP+ URL. As mentioned above, since the eSIM profile that was originally on the UE 110 is now available, the SM-DP+ 502 can select that eSIM profile for reuse.

[0084] At 530, the MNO server 504 sends the SM-DP+ URL to the UE 112. At 532, the UE 112 sends a fetch profile request to the SM-DP+ 502 (via its newly obtained SM-DP+ URL from 530). At 534, the SM-DP+ 502 sends the eSIM profile to the UE 112.

[0085] At 536, UE 112 installs the eSIM profile. At 538, UE 112 sends a profile installed notification to SM-DP+502 informing it that the eSIM profile has been installed. At 540, SM-DP+502 updates the eSIM profile status to installed in response to receiving the profile installed notification. Similar to the example above, the eSIM profile status may be updated multiple times during call flow 500, for example, from available, linked, confirmed, released, downloaded, and finally installed, as shown in 540. Again, these updates may not all occur at 540, but at various points during call flow 500.

[0086] In a fourth aspect of an exemplary embodiment, an out-of-band operation of a Signal Management Discovery Service (SMDS) is disclosed herein. The OEM cloud service may include information on all cellular plans available on any device on the same OEM cloud account. The OEM cloud service may match the phone number and send a plan deletion request to the old UE. Once the eSIM profile is deleted, the profile becomes available for subsequent use by the MNO.

[0087] A fourth aspect can be understood by referring to Figures 6 and 7, which illustrate different options of the fourth aspect. The fourth aspect may be applicable to a scenario in which a user takes the UE to an MNO office and initiates the process of transferring the eSIM and phone number to the new UE.

[0088] Figure 6 shows a fourth call flow 600 in various exemplary embodiments. The SM-DP+ 602 and entitlement server 604 are substantially the same as those described above. Figure 6 shows an MNO office 606, which may be a physical location of the MNO (e.g., a retail store, service center, etc.) that has the ability to provision cellular services from the MNO to user equipment. Figure 6 also shows an SMDS 603, which may be a discovery service that provides profile information related to eSIM provisioning. A typical use case of the call flow in Figure 6 is a user going to the MNO office to initiate eSIM / phone number transfer to a new UE.

[0089] Note that in Figures 6 and 7, the eSIM profile is recycled but not reused. In other words, at the end of call flows 600 and 700, the eSIM profile installed on UE 110 (the old UE) is not the eSIM profile installed on UE 112. Instead, the original eSIM profile is left available, and a new eSIM profile is installed on UE 112. However, the original eSIM profile is then available for the MNO to reuse later for the same or a different subscriber.

[0090] At 610, the MNO office 606 sends a call forwarding request to the entitlement server 604, for example, to forward the call number from UE 110 to UE 112. At 612, the entitlement server 604 sends a new profile retrieval request to SM-DP+ 602. Here again, the profile request pulls a new eSIM profile (profile 2) rather than the eSIM profile (profile 1) currently installed on UE 110.

[0091] At 614, SM-DP+602 sends profile 2 to the entitlement server 604. At 616, SM-DP+602 updates the profile status of profile 2 from Available to Linked, Confirmed, and Released. Each of these eSIM profile statuses is described above.

[0092] In step 618, the entitlement server 604 sends a setup profile request to the SMDS 603. In step 620, the SMDS 603 sets up an eSIM profile (profile 2) for the UE 112. As described above, the SMDS 603 contains information on all cellular plans available on any device on the same account. The SMDS 603 then associates the eSIM profile (profile 2) with the device (e.g., the UE 112) for the relevant account. Thus, the SMDS 603 is up-to-date regarding the cellular plans available for the device for the subscriber's account.

[0093] At 621, the SMDS 603 sends a push notification to the UE 112. The push notification 622 informs the UE 112 that it can proceed with the profile fetch. At 622, the UE 112 sends a profile fetch request (e.g., for profile 2) to the SM-DP+ 602.

[0094] In operation 626, SM-DP+ sends eSIM profile 2 to UE 112. Note again that at the end of operation 626, profile 1 is installed on UE 110 and profile 2 is in a released state (e.g., not installed on UE 112).

[0095] In 628, UE 112 sends a phone number request to the OEM cloud server 605. The OEM cloud server 605 recognizes the UE connected to the OEM cloud account. The OEM cloud server also recognizes the type of UE sending request 628. The exemplary embodiment primarily concerns eSIM transfer of the same type of UE (e.g., smartphone to smartphone), although this behavior can be modified by additional flags in request 628 (different types of UE). The OEM cloud server 605 knows that UE 110 and UE 112 are of the same device type. Using this knowledge, the OEM cloud server 605 knows that UE 112 is attempting to obtain the phone number of UE 110.

[0096] In step 630, the OEM cloud server 605 sends a list of devices to UE 112 using a phone number. UE 112 can then use the information in this list to select a UE 110, and in step 632, UE 112 sends a removal plan request to the UE 110.

[0097] In step 634, UE 110 deletes eSIM profile 1. UE 110 can no longer access the user's phone number. In step 635, UE 112 installs eSIM profile 2. In some examples (not shown), UE 112 may receive notification from UE 110 that eSIM profile 1 has been deleted before installing eSIM profile 2. However, this is not a requirement for eSIM profile 2 to be installed.

[0098] At step 636, UE 110 sends a deletion notification to SM-DP+602. At step 638, SM-DP+602 updates the status of profile 1 from installed to available. eSIM profile 1 becomes available to future users.

[0099] At step 644, UE 112 sends an eSIM profile 2 installation notification to SM-DP+602. At step 646, SM-DP+602 updates the eSIM profile 2 status from released to downloaded and installed.

[0100] At the end of call flow 600, the original eSIM profile (profile 1) is made available for future use, and a new profile (profile 2) is installed on the new UE 112. Note that profile 2 itself may have been "recycled" from the third UE before call flow 600 started.

[0101] Figure 7 shows a fifth call flow 700 in various exemplary embodiments. The call flow 700 represents a second option in the fourth embodiment.

[0102] SM-DP+702, SMDS 703, Entitlement Server 704, OEM Cloud Server 705, and MNO Office 706 are substantially the same as those described in the previous diagram.

[0103] At 710, the MNO office 706 generates a QR code. The QR code may include one or more of the following: ICCID, Mobile Country Code (MCC), Mobile Network Code (MNC), Group 1 Identifier (GID1), Group 2 Identifier (GID2), International Mobile Subscriber Identification Number (IMSI), Transfer Token (received at 407), Plan Active Indication (i.e., whether the user has a cellular plan with the MNO), International Mobile Device Identification Number (IMEI), Embedded Identification Document (EID), Serial Number, Label, Telephone Number, UE Software Version, and Product Class (e.g., iPhone, iPad).

[0104] At 712, UE 112 (e.g., the new UE) scans the QR code. At 714, UE 112 sends a profile fetch request to SM-DP+702. At 716, SM-DP+702 sends profile 2 to UE 112.

[0105] At 717, SM-DP+ updates the status of profile 2 from available to linked, verified, and released. At 718, UE 112 sends a phone number request to the OEM cloud server 705.

[0106] In step 720, the OEM cloud server 706 responds to UE 112 with a list of UE phone numbers associated with the user's phone number. UE 112 can then use the information in this list to select UE 110, and in step 722, UE 112 sends a deletion plan request to UE 110.

[0107] In step 724, UE 110 deletes the Profile 1 plan. UE 110 can no longer access the user's phone number. In step 725, UE 112 installs eSIM Profile 2. In some examples (not shown), UE 112 may receive notification from UE 110 that eSIM Profile 1 has been deleted before installing eSIM Profile 2. However, this is not a requirement for eSIM Profile 2 to be installed.

[0108] At 726, UE 110 sends a delete plan response to SM-DP+702. At 728, SM-DP+702 updates the status of eSIM profile 1 from installed to available. eSIM profile 1 may now be used again for future users with new phone numbers.

[0109] At step 734, UE 112 sends an eSIM profile 2 installation message to SM-DP+702. At step 736, SM-DP+ updates the status of eSIM profile 2 from released to downloaded and installed.

[0110] In the example above, it was explained that an older UE (e.g., UE 110) sent a message to SM-DP+ to indicate that the eSIM profile had been deleted, e.g., operations 422, 520, 636, and 726. However, as mentioned above, once UE 110 deletes the eSIM profile, UE 110 no longer has cellular access. Therefore, UE 110 must send such a message using a different data network. If UE 110 does not have access using a different data network, SM-DP+ will never receive a message indicating that the eSIM profile has been deleted, and the eSIM profile remains installed, which means that the eSIM profile cannot be reused.

[0111] Therefore, in some exemplary embodiments, the source UE may be required to have WiFi access to participate in the transfer process. For example, the source UE may send a message to SM-DP+ indicating that the eSIM profile state can be changed to make it available, thereby enabling the eSIM profile to be reused. For example, when calling a transfer call flow (e.g., call flow 600, call flow 700, etc.), there may be an additional check on the source device UE 110 to determine whether the source device UE 110 has WiFi access. If the source device UE 110 does not have WiFi access, the transfer call flow may be stopped or delayed. For example, the user may be given an indication to connect the source device UE 110 to WiFi in order to continue the transfer process.

[0112] In other exemplary embodiments, a new UE (e.g., UE 112) may send a message to SM-DP+ to indicate that the eSIM profile has been deleted. This message may be sent directly or indirectly to SM-DP+, as described below. For example, if UE 110 deletes the eSIM profile, UE 110 may send a short-range communication message (e.g., Bluetooth) to UE 112. In a forwarding call flow (e.g., call flows 300, 400, 500) in which UE 112 will reuse the original eSIM profile from the old UE 110, UE 112 may send a message to an entitlement server or MNO server, which may then forward the message to SM-DP+ to allow the eSIM profile to be made available and reused by UE 112.

[0113] In a forwarding call flow (e.g., call flows 600 and 700) where the original eSIM profile from an older UE 110 is made available for future use, when UE 112 has cellular services via the eSIM profile (e.g., profile 2), UE 112 may send a message to SM-DP+ indicating that the original eSIM profile (profile 1) has been removed from UE 110. SM-DP+ can then update the eSIM state of the original eSIM profile (profile 1) to make it available for future reuse. Examples

[0114] In the first example, the method includes storing records of multiple embedded subscriber identification module (eSIM) profiles, each eSIM profile record including the state of the eSIM profile; receiving a message from a first user device (UE) indicating that the first eSIM profile has been removed from the first UE; changing the state of the first eSIM profile from installed to available; receiving a message requesting that the first eSIM profile be assigned to a second UE; changing the state of the first eSIM profile to a state that allows the eSIM profile to be downloaded to the second UE; and downloading the first eSIM profile to the second UE.

[0115] In the second example, the method in the first example further includes receiving a message from the second UE indicating that the first eSIM profile has been installed on the second UE, and changing the status of the first eSIM profile to installed.

[0116] In the third example, the method of the first example is used, where a message requesting that the first eSIM profile be assigned to the second UE is received from the entitlement server.

[0117] In the fourth example, the method of the first example is used, where a message requesting that the first eSIM profile be assigned to the second UE is received from the mobile network operator (MNO) server.

[0118] In the fifth example, one or more processors are configured to run one of the first through fourth examples.

[0119] In the sixth example, the server device is configured to run one of the first four examples.

[0120] In the seventh example, the method includes sending a delete plan request to the source user equipment (UE) to delete the embedded subscriber identification module (eSIM) profile; sending a request to the entitlement server for the eSIM profile; receiving a response from the entitlement server containing information for retrieving the eSIM profile; fetching the eSIM profile from the subscription manager-data preparation+ (SM-DP+); installing the eSIM profile; and sending confirmation to the SM-DP+ that the eSIM profile has been installed.

[0121] In the eighth example, the method of the seventh example further includes sending a transfer profile request for the eSIM profile to the source UE, receiving a transfer profile response from the source UE indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed, sending a transfer permission request to the entitlement server, and receiving a transfer permission response from the entitlement server indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed.

[0122] In the ninth example, the method of the seventh example further includes receiving a delete plan response from the source UE indicating that the eSIM profile has been deleted, the request for the eSIM profile is a transfer SIM service request, and the response from the entitlement server is a transfer SIM response.

[0123] In the tenth example, the method of the seventh example further includes scanning a quick response (QR) code displayed by the source UE and determining QR code information from the scanned QR code, the QR code information relating to the transfer of an eSIM from the source UE to the target UE.

[0124] In the 11th example, the method in the 10th example includes one or more of the following QR code information: Integrated Circuit Card Identification Number (ICCID), Mobile Country Code (MCC), Mobile Network Code (MNC), Group 1 Identifier (GID1), Group 2 Identifier (GID2), International Mobile Subscriber Identification Number (IMSI), Transfer Token, Indication of Plan Active, International Mobile Device Identification Number (IMEI), Embedded Identification Document (EID), Serial Number, Label, Telephone Number, UE Software Version, and Product Class.

[0125] In the 12th example, the method of the 10th example further includes sending a phone number list request to an Original Equipment Manufacturer (OEM) cloud server and receiving a phone number list response from the OEM cloud server containing a list of devices associated with phone numbers in an eSIM profile, and the target UE sends a deletion plan request to the source UE, based at least on the information contained in the list of devices.

[0126] In the 13th example, the method of the 10th example is such that the request for the eSIM profile is an install eSIM request, and the response from the entitlement server includes the SM-DP+ Universal Resource Locator (URL).

[0127] In example 14, the processor is configured to run one of examples 7 through 13.

[0128] In the 15th example, the target user device (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the 7th to 13th examples.

[0129] In the 16th example, the method includes receiving a deletion plan request from the target UE to delete an embedded subscriber identification module (eSIM) profile, deleting the eSIM profile, and sending an indication that the eSIM profile has been deleted from the source UE.

[0130] In example 17, the method used in example 16 is used to send an indication that the eSIM profile has been removed from the source UE to the Subscription Manager - Data Preparation+ (SM-DP+).

[0131] In example 18, the method used in example 16 is used to send an indication to the target UE that the eSIM profile has been removed from the source UE.

[0132] In Example 19, the method of Example 16 further includes receiving a transfer profile request for the eSIM profile from the target UE, sending a transfer permission request to the entitlement server, receiving a transfer permission response from the entitlement server indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed, and sending a transfer profile response to the target UE indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed.

[0133] In the 20th example, the method from the 16th example further includes sending a delete plan response to the target UE indicating that the eSIM profile has been deleted.

[0134] In the 21st example, the method of the 16th example further includes generating a quick response (QR) code containing QR code information to be displayed by the source UE, where the QR code information relates to the transfer of the eSIM from the source UE to the target UE.

[0135] In the 22nd example, the method in the 21st example, the QR code information includes one or more of the following: Integrated Circuit Card Identification Number (ICCID), Mobile Country Code (MCC), Mobile Network Code (MNC), Group 1 Identifier (GID1), Group 2 Identifier (GID2), International Mobile Subscriber Identification Number (IMSI), Transfer Token, Indication of Plan Active, International Mobile Device Identification Number (IMEI), Embedded Identification Document (EID), Serial Number, Label, Telephone Number, UE Software Version, and Product Class.

[0136] In Example 23, the method of Example 16 further includes sending a transfer token request to an entitlement server and receiving a transfer token response from the entitlement server containing a transfer token indicating that an eSIM profile installed on a source UE may be transferred to another UE.

[0137] In example 24, the processor is configured to run one of examples 16 through 23.

[0138] In the 25th example, the source user equipment (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the 16th to 23rd examples.

[0139] In the 26th example, the method includes receiving a push notification registration from a source user device (UE) for a push notification relating to the transfer of an embedded subscriber identification module (eSIM) profile installed on the source UE; receiving a request from a target UE to install an eSIM on the target UE; sending a push notification to the source UE indicating that the source UE will delete the eSIM profile; receiving an indication from the source UE that the eSIM profile has been deleted; sending a request to the Subscription Manager-Data Preparation+ (SM-DP+) indicating that the eSIM profile will be transferred to the target UE; receiving a response from SM-DP+ indicating that the eSIM profile will be transferred to the target UE, wherein the response includes the Universal Resource Locator (URL) of SM-DP+; and sending a response to the target UE for the request to install an eSIM on the target UE, wherein the response includes the URL of SM-DP+.

[0140] In example 27, one or more processors are configured to run example 26.

[0141] In example 28, the server device is configured to run example 26.

[0142] In the 29th example, the method includes: scanning a quick response (QR) code displayed by a source user device (UE); determining QR code information from the scanned QR code, the QR code information relating to the transfer of an embedded subscriber identification module (eSIM) profile from the source UE to the target UE; sending a request for the eSIM profile to a carrier server; receiving a response from the carrier server containing information for retrieving the eSIM profile, the information including a universal resource locator (URL) for the subscription manager-data preparation+ (SM-DP+); fetching the eSIM profile from the SM-DP+; installing the eSIM profile; and sending a confirmation to the SM-DP+ that the eSIM profile has been installed.

[0143] In example 30, the processor is configured to run example 29.

[0144] In the 31st example, the target user device (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform the 29th example.

[0145] In the 32nd example, the method includes sending a push notification registration to a carrier server for a push notification relating to the transfer of an embedded subscriber identification module (eSIM) profile installed on a source UE; generating a quick response (QR) code containing QR code information to be displayed by the source UE, wherein the QR code information relates to the transfer of an eSIM profile from the source UE to a target UE; receiving a push notification from the carrier server indicating that the source UE has deleted the eSIM profile; and sending an indication to the carrier server that the eSIM profile has been deleted.

[0146] In example 33, the processor is configured to run example 32.

[0147] In the 34th example, the source user equipment (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform the 32nd example.

[0148] Example 35 is a method for storing records of multiple embedded subscriber identification module (eSIM) profiles, each eSIM profile record including the state of the eSIM profile; receiving a request for a first eSIM profile from a first user device (UE); sending the first eSIM profile to the first UE; receiving a first indication from a second UE that a second eSIM profile has been removed from the second UE, with the first and second UEs associated with the same account; updating the state of the second eSIM profile to make it available in response to the first indication; receiving a second indication from the first UE that the first eSIM profile has been installed on the first UE; and installing the state of the first eSIM profile in response to the second indication.

[0149] In the 36th example, the method of the 35th example further includes receiving a request from an entitlement server for a new eSIM profile for a first UE, generating a new eSIM profile for the first UE, wherein the new eSIM profile is the first eSIM profile, and sending a response to the entitlement server indicating that the new eSIM profile is available for the first UE, wherein the response includes information relating to the first eSIM profile.

[0150] In example 37, one or more processors are configured to run example 35 or 36.

[0151] In example 38, the server device is configured to run example 35 or 36.

[0152] In Example 39, the method includes receiving a setup profile request from an entitlement server for an embedded subscriber identification module (eSIM) profile for a user device (UE), configuring the eSIM profile for the UE, and sending a push notification to the UE, the push notification containing information for the UE to fetch the eSIM profile.

[0153] In example 40, one or more processors are configured to run example 39.

[0154] In example 41, the server device is configured to run example 39.

[0155] In the 42nd example, the method includes receiving a request from a target user device (UE) for a list of devices associated with a phone number, sending a response to the target UE containing the list of devices associated with a phone number, and sending a request to the source UE to remove an embedded subscriber identification module (eSIM) profile associated with a phone number.

[0156] In example 43, one or more processors are configured to run example 42.

[0157] In example 44, the server device is configured to run example 42.

[0158] Example 45 provides a method comprising: scanning a quick response (QR) code generated by a mobile network operator; determining QR code information from the scanned QR code, wherein the QR code information relates to a first embedded subscriber identification module (eSIM) profile and includes a universal resource locator (URL) for a Subscription Manager-Data Preparation+ (SM-DP+); fetching the first eSIM profile from SM-DP+; sending a telephone number list request to an Original Equipment Manufacturer (OEM) cloud server; receiving a telephone number list response from the OEM cloud server containing a list of devices associated with the telephone numbers of the first eSIM profile; sending a delete plan request to a source UE, which is one of the devices associated with the telephone numbers, to delete a second eSIM profile associated with the telephone number; installing the first eSIM profile; and sending a confirmation to SM-DP+ that the first eSIM profile has been installed.

[0159] In example 46, the processor is configured to run example 45.

[0160] In the 47th example, the target user device (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform the 45th example.

[0161] In example 48, the method includes receiving a delete plan request from a target UE containing a first embedded subscriber identification module (eSIM) profile associated with a phone number to delete a second eSIM profile associated with a phone number; deleting the second eSIM profile; and sending confirmation to the Subscription Manager-Data Preparation+ (SM-DP+) that the second eSIM profile has been deleted.

[0162] In example 49, the method used in example 48 is used, but the confirmation is sent via the Signal Management Discovery Service (SMDS).

[0163] In example 50, the processor is configured to execute example 48 or 49.

[0164] In example 51, the source user equipment (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to run examples 48 through 49.

[0165] In example 52, the method includes sending a deletion plan request to the source UE to delete an embedded subscriber identification module (eSIM) profile, receiving a deletion notification from the source UE indicating that the eSIM profile has been deleted from the source UE, and sending the deletion notification to the subscription manager-data preparation+ (SM-DP+).

[0166] In example 53, the processor is configured to run example 52.

[0167] In the 54th example, the target user device (UE) comprises a transceiver configured to communicate with a network, and a processor communicatively coupled to the transceiver and configured to perform the 52nd example.

[0168] Those skilled in the art will understand that the exemplary embodiments described above may be implemented in any preferred software configuration, hardware configuration, or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms, Windows OS, Mac platforms, and MAC OS with compatible operating systems, as well as mobile devices with operating systems such as iOS and Android. Exemplary embodiments of the above methods may be embodied as a program containing lines of code stored in a non-temporary computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0169] While this application describes various embodiments, each having different characteristics in various combinations, it will be understood by those familiar with the art that any feature of one embodiment may be combined with features of other embodiments in such a way that no particular feature is specifically disallowed, or that it does not contradict the operation of the device of the disclosed embodiment or the described function in any way.

[0170] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0171] It will be apparent to those familiar with the art that various modifications may be made in this disclosure without departing from the spirit or scope of this disclosure. Accordingly, this disclosure is intended to cover all modifications and variations of this disclosure, insofar as they fall within the scope of the appended claims and equivalents of the claims.

Claims

1. It is a method, The storage of records of multiple embedded subscriber identification module (eSIM) profiles, wherein each eSIM profile record includes the state of the eSIM profile. Receiving a message from the first user device (UE) indicating that the first eSIM profile has been deleted from the first UE, The state of the first eSIM profile described above is changed from installed to available, Receiving a message requesting that the first eSIM profile be assigned to the second UE, The state of the first eSIM profile is changed to a state that allows the eSIM profile to be downloaded to the second UE, A method comprising downloading the first eSIM profile to the second UE.

2. Receiving a message from the second UE indicating that the first eSIM profile has been installed on the second UE, The state of the first eSIM profile described above is changed to installed, The method according to claim 1, further comprising:

3. The method according to claim 1, wherein the message requesting that the first eSIM profile be assigned to the second UE is received from an entitlement server.

4. The method according to claim 1, wherein the message requesting that the first eSIM profile be assigned to the second UE is received from a mobile network operator (MNO) server.

5. A device comprising memory coupled to a processor, wherein the processor is To request the deletion of an embedded subscriber identification module (eSIM) profile on a source user device (UE), prepare a deletion plan request to be sent to the source UE, Prepare an entitlement server request for the eSIM profile, In response to the transmission of the entitlement server request, a response containing information for retrieving the eSIM profile is received. Obtain the eSIM profile from Subscription Manager - Data Preparation + (SM-DP +), Install the aforementioned eSIM profile, A device configured to prepare a confirmation to be sent to the SM-DP+ indicating that the eSIM profile has been installed.

6. The aforementioned processor, Before sending the deletion plan request, prepare a transfer profile request for the eSIM profile to be sent to the source UE. The source UE receives a transfer profile response from the source UE indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed. Prepare the transfer permission request to be sent to the aforementioned entitlement server, The apparatus according to claim 5, further configured to receive a transfer permission response from the entitlement server indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed.

7. The aforementioned processor, The apparatus according to claim 5, further configured to receive a deletion plan response from the source UE indicating that the eSIM profile has been deleted, wherein the request for the eSIM profile is a transfer SIM service request, and the response from the entitlement server is a transfer SIM response.

8. The aforementioned processor, The system processes the scanning of the quick response (QR) code displayed by the aforementioned source UE. The apparatus according to claim 5, further configured to determine QR code information from the scanned QR code, wherein the QR code information relates to the transfer of the eSIM from the source UE to the target UE.

9. The apparatus according to claim 8, wherein the QR code information comprises one or more of the following: integrated circuit card identification number (ICCID), mobile country code (MCC), mobile network code (MNC), group 1 identifier (GID1), group 2 identifier (GID2), international mobile subscriber identification number (IMSI), the transfer token, indication of plan activation, international mobile device identification number (IMEI), embedded identification document (EID), serial number, label, telephone number, UE software version, and product class.

10. The aforementioned processor, Prepare a request for a list of phone numbers to be sent to the OEM's cloud server. The apparatus according to claim 8, further configured to receive a phone number list response from the OEM cloud server, which includes a list of devices associated with the phone numbers of the eSIM profile, and to send the deletion plan request to the source UE based on at least the information contained in the list of devices.

11. The apparatus according to claim 8, wherein the request for the eSIM profile is an install eSIM request, and the response from the entitlement server includes the SM-DP+ universal resource locator (URL).

12. A device comprising memory coupled to a processor, wherein the processor is A deletion plan request is received from the target user device (UE) to remove the embedded subscriber identification module (eSIM) profile from the source UE. Delete the aforementioned eSIM profile, A device configured to prepare an indication that the eSIM profile has been removed from the source UE.

13. The apparatus according to claim 12, wherein the indication that the eSIM profile has been removed from the source UE is transmitted to the Subscription Manager - Data Preparation+ (SM-DP+).

14. The apparatus according to claim 12, wherein the indication that the eSIM profile has been removed from the source UE is transmitted to the target UE.

15. The aforementioned processor, Before receiving the deletion plan request, the target UE receives a transfer profile request for the eSIM profile, Prepare to send a transfer permission request to the entitlement server. The entitlement server receives a transfer permission response indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed. The apparatus according to claim 12, further configured to prepare to send to the target UE a transfer profile response indicating that the transfer of the eSIM profile from the source UE to the target UE can proceed.

16. The aforementioned processor, The apparatus according to claim 12, further configured to prepare to send a deletion plan response to the target UE indicating that the eSIM profile has been deleted.

17. The aforementioned processor, The apparatus according to claim 12, further configured to generate a QR code containing quick response (QR) code information to be displayed by the source UE, wherein the QR code information is related to the transfer of the eSIM from the source UE to the target UE.

18. The apparatus according to claim 17, wherein the QR code information comprises one or more of the following: integrated circuit card identification number (ICCID), mobile country code (MCC), mobile network code (MNC), group 1 identifier (GID1), group 2 identifier (GID2), international mobile subscriber identification number (IMSI), the transfer token, indication of plan active status, international mobile device identification number (IMEI), embedded identification document (EID), serial number, label, telephone number, UE software version, and product class.

19. The aforementioned processor, Prepare a transfer token request to send to the entitlement server. The apparatus according to claim 12, further configured to receive from the entitlement server a transfer token response including a transfer token indicating that the eSIM profile installed on the source UE can be transferred to another UE.

Images