Pseudo single sim mode and management of phantom cbrs esims

Abstract

An apparatus configured to store a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM), the carrier bundle comprising a MNO entitlement server address and an entitlement server of a phantom SIM network, transmit, to the entitlement server, a getEntitlement message, process a getEntitlement response indicating a user equipment (UE) is allowed to offload MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, transmit, to the entitlement server, a signUpForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID), process a signUpForSIMService response comprising an ICCID of the eSIM of the phantom SIM network, transmit, to a subscription manager-data preparation+ (SM-DP+), a download ICCID request message comprising the ICCID of the eSIM, process the eSIM of the phantom SIM network and install the eSIM of the phantom SIM network on the UE.

Description

Pseudo Single SIM Mode and Management of phantom CBRS eSIMsInventors: Raj S Chaugule, Jianwei Chen and Vikrant R SarlePRIORITY / INCORPORATION BY REFERENCE

[0001] This application claims priority to US Provisional Application Serial No. 63 / 508, 349 filed on June 15, 2023 and entitled, "Pseudo Single SIM Mode and Management of phantom CBRS eSIMs," the entirety of which is incorporated by reference herein .BACKGROUND

[0002] Mobile network operators (MNOs) typically own wireless spectrum and deploy their own radio networks (e.g., radio access networks (RANs) and network cores) . Mobile Virtual Network Operators (MVNOs) are typically localized and contract with MNOs to utilize MNO infrastructure as a "virtual" network. However, some MVNOs have begun to deploy their own cellular infrastructure, blurring the lines between MVNO and MNO. One particular network arrangement that will see increasing use in the future is n71 cells for macro coverage alongside n48 cells for shorter distances using citizens broadband radio service (CBRS) spectrum. In some cases, the n71 cells may be operated by an MNO and the n48 cells may be operated by an MVNO (e.g. , a mobile service operator (MSO) ) . There may be advantages for the MSO to offload certain operations such as data transfer in the uplink or downlink to the CBRS network rather than using the MNO network. However, there are no current procedures to coordinate a user equipment (UE) operating on both types of networks simultaneously .SUMMARY

[0003] Some example embodiments are related to an apparatus having processing circuitry configured to store a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an entitlement server of a phantom SIM network, determine a trigger condition has occurred, generate, for transmission to the entitlement server, a getEntitlement message, process, based on signaling received from the entitlement server, a getEntitlement response message indicating a user equipment (UE) is allowed to offload MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number, generate, for transmission to the entitlement server, a signUpForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, process, based on signaling received from the entitlement server, a signUpForSIMService response message comprising an ICCID of the eSIM of the phantom SIM network, generate, for transmission to a phantom SIM network subscription manager-data preparation+ (SM- DP+) , a download ICCID request message comprising the ICCID of the eSIM, process, based on signaling received from the SM-DP+, the eSIM of the phantom SIM network and install the eSIM of the phantom SIM network on the UE .

[0004] Other example embodiments are related to an apparatus having processing circuitry configured to store a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises anaddress for a MNO entitlement server of an MNO network and an entitlement server of a phantom SIM network, determine a trigger condition has occurred, wherein the trigger condition is related to the UE performing operations related to offloading MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, determine the UE includes an eSIM bound with the MNO SIM and prevent the UE from downloading a further eSIM associated with the MNO SIM.

[0005] Still further example embodiments are related to a phantom SIM network entitlement server configured to receive a getEntitlement message from a user equipment (UE) , send, to the UE, a getEntitlement response message indicating the UE may offload mobile network operator (MNO) subscriber identity module (SIM) service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number, receive, from the UE, a signUpForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, send, to a business support system (BSS) of the phantom SIM network, a provisioning message requesting the eSIM be provisioned for the UE, receive, from the BSS, a provisioning response indicating the eSIM has been provisioned for the UE and send, to the UE, a signUpForSIMService response message comprising an ICCID of the eSIM of the phantom SIM network.

[0006] Additional example embodiments are related to an apparatus having processing circuitry configured to perform an operation to transfer a mobile network operator (MNO) subscriber identity module (SIM) from a further UE to the UE, wherein the further UE comprises a first phantom SIM network embedded SIM(eSIM) , store a carrier bundle associated with the MNO SIM, wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an Entitlement server of a phantom SIM network, generate, for transmission to the entitlement server, a getEntitlement message, process, based on signaling received from the entitlement server, a getEntitlement response message indicating the UE may offload MNO SIM service to the phantom SIM network, generate, for transmission to the entitlement server, a signUpForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, process, based on signaling received from the entitlement server, a signUpForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network, wherein the second eSIM is different from the first eSIM, generate, for transmission to a phantom SIM network subscription manager-data preparation+ (SM-DP+) , a download ICCID request message comprising the ICCID of the second eSIM, process, based on signaling received from the SM-DP+, the second eSIM of the phantom SIM network and install the second eSIM of the phantom SIM network on the UE .BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Fig. 1 shows an example network arrangement according to various example embodiments.

[0008] Fig. 2 shows an example UE according to various example embodiments.

[0009] Fig. 3 shows an example base station, according to various example embodiments.

[0010] Fig. 4 shows a simplified arrangement of a UE implementing SIMs for an MNO and MVNO network according to various example embodiments.

[0011] Fig. 5 shows a phantom eSIM provisioning flow according to various example embodiments.

[0012] Fig. 6 shows a call flow for pseudo single SIM mode provisioning according to various example embodiments.

[0013] Fig. 7 shows a pseudo single SIM trigger diagram according to various example embodiments.

[0014] Fig. 8 shows a network diagram related to a synching mechanism according to various example embodiments.

[0015] Fig. 9 shows a method for preventing a UE from downloading a new phantom eSIM when a previously installed phantom eSIM is bound to an MNO according to various example embodiments .

[0016] Fig. 10A shows a method for controlling entitlement changes when a UE does not currently have a phantom eSIM installed according to various example embodiments.

[0017] Fig. 10B shows a method for controlling entitlement changes when a UE currently has a phantom eSIM installed according to various example embodiments.

[0018] Fig. 10C shows a second method for controlling entitlement changes when a UE currently has a phantom eSIM installed according to various example embodiments.

[0019] Fig. 11 shows a method for managing a phantom eSIM when an MNO SIM is removed according to various example embodiments .

[0020] Fig. 12 shows a method for managing a phantom eSIM when an MNO SIM is removed that incorporates a timer according to various example embodiments.

[0021] Fig. 13 shows a network diagram related to replacement of a primary subscription according to various example embodiments .

[0022] Fig. 14 shows a method for managing phantom eSIMs when a primary subscription is replaced according to various example embodiments .

[0023] Fig. 15 shows a method for mode switching between a pseudo-single SIM mode to a true dual SIM mode according to various example embodiments.

[0024] Fig. 16 shows a first method for managing a maximum number of subscriptions on a UE according to various example embodiments .

[0025] Fig. 17 shows a second method 1700 for managing a maximum number of subscriptions on a UE according to various example embodiments.

[0026] Fig. 18 shows a method for handling unregulated subscriptions according to various example embodiments.

[0027] Fig. 19 shows a method for deleting phantom eSIM subscriptions according to various example embodiments.

[0028] Fig. 20 shows a method for phantom eSIM subscription transfer according to various example embodiments.

[0029] Fig. 21A shows a first user interface diagram according to various example embodiments.

[0030] Fig. 21B shows a second user interface diagram according to various example embodiments.DETAILED DESCRIPTION

[0031] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to providing a UE with two SIMs, one for an MNO network and one for a phantom SIM network, where data operations may be offloaded to the phantom SIM network. However, unlike traditional dual SIM mode, the example embodiments use the phantom SIM in a manner that is transparent to the user of the UE, e.g., both SIMs are associated with the same phone number.

[0032] The example embodiments are described with regard to a user equipment (UE) . However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component.

[0033] The example embodiments are also described with reference to a 5G New Radio (NR) network. However, it should be understood that the example embodiments may also be implemented in other types of networks, including but not limited to LTE networks, future evolutions of the cellular protocol (e.g. , 6G networks) , or any other type of network.

[0034] Throughout this description various messages that are exchanged between components are described by a specific name (e.g., getEnti tlement message, getEntitlement response message, signupforSIMService, etc. ) . It should be understood that these message names are only example and the messages that are exchanged between the various components may have different names or no names at all.

[0035] As stated above, MNOs and MVNOs differ in several key areas. MNOs typically own wireless spectrum and deploy their own radio networks across large geographic areas, whereas MVNOs are typically localized and contract with MNOs to utilize MNO infrastructure as a "virtual" network. Some MVNOs have begun to deploy their own cellular infrastructure, blurring the lines between MVNO and MNO. One particular network arrangement that will see increasing use in the future is n71 cells for macro coverage alongside n48 cells for shorter distances using citizens broadband radio service (CBRS) spectrum. In some cases, the n71 cells may be operated by an MNO and the n48 cells may be operated by an MVNO (e.g. , a mobile service operator (MSO) ) .

[0036] CBRS refers to 150 MHz of spectrum (from 3.55 to 3.7 GHz) in the 3.5 GHz band ("Band 48") and may be used to deploy cellular networks with small but concentrated deployments. CBRSaccess may be based on a multi-tiered access and authorization framework configured to accommodate shared federal and non- federal use of the band.

[0037] An MSO may offer CBRS service for UEs subscribed to pseudo-single SIM plans (e.g. , a phantom SIM network) . If an MNO subscriber with a pseudo-single SIM subscription enters a specified geographic area, pseudo-single SIM operations may begin via a phantom eSIM, e.g. , on a phantom SIM network. As will be described in greater detail below the use of the phantom eSIM provides the UE with two SIMs, one to connect to the traditional macro network and one to connect to the CBRS network. However, unlike traditional dual SIM operations, the example embodiments present these two SIMs that will operate in pseudo-single SIM mode, e.g. , as one phone number. In pseudosingle SIM mode, the addition and use of the phantom eSIM is transparent to the user, e.g. , the user does not pick a phone number to use, despite the use of multiple SIMs. This will be explained in greater detail below. While the example embodiments are described with reference to an MSO providing the phantom SIM network, any entity may own / operate / administer the phantom SIM network .

[0038] Fig. 1 shows an example network arrangement 100 according to various example embodiments. The example network arrangement 100 includes a UE 110. The UE 110 may be any type of electronic component that is configured to communicate via a network, e.g. , mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (loT) devices, etc. An actual network arrangement may include any number of UEs being used by anynumber of users. Thus, the example of one UE 110 is merely provided for illustrative purposes.

[0039] The UE 110 may be configured to communicate with one or more networks. In the example of the network configuration 100, the network with which the UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, the UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN) , a legacy cellular network, etc. ) and the UE 110 may also communicate with networks over a wired connection. With regard to the example embodiments, the UE 110 may establish a connection with the 5G NR RAN 120. Therefore, the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120.

[0040] The 5G NR RAN 120 may be portions of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc. ) . The RAN 120 may include cells or base stations that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. In this example, the 5G NR RAN 120 includes the gNB 120A. However, reference to a gNB is merely provided for illustrative purposes, any appropriate base station or cell may be deployed (e.g., Node Bs, eNodeBs, HeNBs, eNBs, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc. ) .

[0041] Any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120. For example, as discussed above, the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and / or the user thereof has a contract and credential information (e.g. , stored on a SIMcard) . Upon detecting the presence of the 5G NR RAN 120, the UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120. More specifically, the UE 110 may associate with a specific cell (e.g., gNB 120A) .

[0042] The network arrangement 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 that flows between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110. The network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks.

[0043] Fig. 2 shows an example UE 110 according to various example embodiments. The UE 110 will be described with regard to the network arrangement 100 of Fig. 1. The UE 110 may 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. The other components 230 may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports toelectrically connect the UE 110 to other electronic devices, sensors to detect conditions of the UE 110, etc. An eUICC 240 may be a hardware component embedded into the UE 110 configured to store a number of carrier profiles.

[0044] The processor 205 may be configured to execute a plurality of engines for the UE 110. For example, the engines may include a phantom eSIM engine 235 for performing operations related to improved UE handling of phantom eSIMs. The phantom eSIM engine 235 may also control a local profile assistant (LPA) function of the UE 110 that allows the UE 110 to download encrypted profiles to the eUICC 240 of the UE 110.

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

[0046] The memory arrangement 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 componentconfigured to show data to a user while the I / O device 220 may be a hardware component that enables the user to enter inputs. The display device 215 and the I / O device 220 may be separate components or 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. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e.g. , set of consecutive 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 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) for implementing any one of the methods described herein.

[0047] Fig. 3 shows an example base station 300 according to various example embodiments. The base station 300 may represent the gNB 120A or any other access node through which the UE 110 may establish a connection and manage network operations.

[0048] The base station 300 may include a processor 305, a memory arrangement 310, an input / output (I / O) device 315, a transceiver 320, and other components 325. The other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 300 to other electronic devices and / or power sources, etc.

[0049] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or ports that enable a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . Therefore, the transceiver 320 may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs. The transceiver 320 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 305 may be operably coupled to the transceiver 320 and configured to receive from and / or transmit signals to the transceiver 320. The processor 305 may be configured to encode and / or decode signals (e.g., signaling from a UE) for implementing any one of the methods described herein.

[0050] Fig. 4 shows a simplified arrangement 400 of a UE 110 implementing SIMs for an MNO and MVNO network according to various example embodiments. The UE 110 may have a MVNO SIM 410, which grants the UE 110 registration access 420 to the CBRS n48 network 402 via a MVNO protocol stack 412. Similarly, the UE 110 may also have an MNO SIM 414, which grants the UE 110 registration access 418 to the macro network 404 (e.g., n71) via a MNO protocol stack 416.

[0051] The UE 110 has two SIMs (e.g., is a dual SIM UE) , one to connect to the traditional macro network 404 (e.g. , the MNO SIM 414) and one to connect to the CBRS N48 network 402 (e.g.,the MVNO SIM 410) . Unlike traditional dual SIM operations, the example embodiments present these two SIMs as operating in pseudo-single SIM mode, e.g. , the two SIMs operate using the same phone number. The MVNO eSIM is described as a "phantom" SIM because a user will typically not know or see that it is in use at any given time. This will be explained in greater detail below .

[0052] The network arrangement 400 may be hierarchical. For example, the CBRS n48 network 402 may take priority over the macro network 404 in specified geographic zones (e.g. , downtown / dense areas) or in high network traffic areas. The decision to switch to using the MVNO protocol stack 412 may be based on any criteria, e.g., geofencing, signal strength evaluation by the UE 110 of both the networks 402 and 404, etc. These arrangements and logic will be explained in greater detail below.

[0053] In some examples, the UE 110 operating on an MNO may request a CBRS SIM, e.g. , phantom eSIM. The UE 110 may also download geofences to know when to activate the phantom eSIM. The phantom eSIM is typically hidden from the user. The example embodiments are related to seamlessly transitioning between MNO and MVNO network deployments using the MNO SIM and the MVNO SIM. One simplified scenario for the example embodiments is a user with a cellular contract with an MVNO (which is actually using a macro / MNO network in the background) approaching and being handed over to an MVNO-owned n48 cell. The n48 cells and associated eSIM may also be referred to as a phantom SIM network, in contrast to the MNO. The user in such a scenario has seamlessly transitioned between the virtual network (beinghosted by an MNO) and the "real" network being deployed by the MVNO.

[0054] Fig. 5 shows a phantom eSIM provisioning flow 500 according to various example embodiments. It should be noted that the circled numbers in Fig. 5 are not reference numerals but are intended to assist one of skill in the art to visualize the flow between the various components illustrated in Fig. 5. Furthermore, the provisioning flow 500 of Fig. 5 is a high level flow and does not show all messages that are passed between the various components shown in Fig. 5. As noted above, some MVNOs are deploying their own network hardware; such MVNOs need logic to transition UEs between MNO-operated networks and their CBRS networks via phantom eSIMs. A UE requesting this "enhanced" coverage needs a phantom eSIM to connect to the CBRS n48 network .

[0055] The UE 110 may be initially operating with service on an MNO 550. For clarity, the UE 110 may have MVNO cellular service but the network that the UE 110 is actually accessing are deployed by the MNO as shown by the entities contained in the MNO 550 box, e.g., operated by an MNO such as Verizon, AT&T, etc.) . Thus, the UE 110 may have an MNO SIM that may be used to access the MNO network. The MNO SIM may be an actual SIM or an eSIM. This MNO SIM may have an MNO carrier bundle that includes various information for accessing the MNO 550. In addition, as will be described below, the MNO carrier bundle may also include information to allow the UE 110 to request a phantom eSIM for the MVNO 552. In the example of Fig. 5, it will be considered that the MNO SIM includes the MNO carrier bundle that includes various information as described below, e.g., the provisioningof the MNO SIM with the MNO carrier bundle may occur prior to the operations of Fig. 5.

[0056] In 522, the UE 110 connects to the 5G NR RAN 120. This may occur during initial network connection procedures. At any point while connected to the 5G NR-RAN 120, the UE 110 may request a phantom eSIM. As described above, the MNO SIM of the UE 110 may include an MNO carrier bundle. The MNO carrier bundle may include an entitlement server address (e.g. , uniform resource locator (URL) ) for an entitlement server of the MNO 550 (e.g., ESI 504) and an entitlement server address for an entitlement server of the MVNO 552 (e.g. , ES2 510) , e.g., the MNO carrier bundle includes two entitlement server URLs in one bundle for two services. Thus, in 524, the 5G NR RAN transmits the request for the phantom eSIM to the packet core 502.

[0057] Prior to the UE 110 receiving the phantom eSIM, an authentication procedure may be used to authenticate that the UE 110 is entitled to receive the phantom eSIM. The UE 110 may already have been authenticated at a previous time (e.g., the UE 110 has a valid authentication token for making the request for the phantom eSIM and therefore the authentication procedure does not need to be performed) . However, in the example of Fig. 5, it will be considered that the authentication procedure is performed. In 526, the packet core 502 transmits the phantom eSIM request to the MNO entitlement server ESI 504, e.g., the UE 110 has the URL of ESI 504 in the carrier bundle. In 528, the ESI 504 transmits the request to an authentication, authorization and accounting (AAA) 506 function to authenticate the request. The AAA 506 may be a core network function that controls access to computer resources, enforces policies, andaudits usage within the MNO 550 network. In 530, the AAA 506 connects to a home location register (HLR) 508, which contains information of each subscriber authorized to use the MNO network 550. In 532, the ES2 510 requests authorization from the AAA 506 to perform operations related to provisioning the UE 110 with the phantom eSIM. It should be noted that the ES2 510 is authenticating with the macro (MNO 550) AAA 506, e.g. , an Extensible Authentication Protocol method for Authentication and Key Agreement (EAP-AKA) . The request by the UE for the phantom eSIM will trigger the authentication procedure between the ES2 510 and AAA 506.

[0058] In this example, it is considered that authentication operations are successful, and thus, at the end of 532, the UE 110 is authorized to make the request for the phantom SIM (e.g. , the UE 110 and any other components requiring authentication have received a valid authentication token for continuing operations related to the phantom SIM request) .

[0059] In 534, the packet core 502 sends the phantom SIM request to the ES2 510 (e.g. , using the ES2 510 URL included in the MNO carrier bundle) . The ES2 510 is part of the MVNO 552 network. In 536, the ES2 510 transmits the request to a business support system (BSS) 512. The BSS 512 may be considered a network function that is related to operations such as product management, order management, customer services provisioning, revenue management, and customer management.

[0060] In 538, the BSS 512 queries a subscription manager data preparation! 518 (SM-DP+) which is a network element (e.g. , a server) that prepares, stores, and protects carrier profiles(including operator credentials) . The SM-DP+ 518 may also download and install profiles to a UE eUICC (e.g., the eUICC 240) .

[0061] In 540, the SM-DP+ 518 queries a lookup server 520, which responds in 542 with the credentials of the UE 110. The SM-DP+ allocates an Integrated Circuit Card Identification Number (ICCID) for the phantom eSIM and transmits the UE 110 credential information and ICCID to the BSS 512 in 544.

[0062] In 546, the LS 520 transmits an event notification to the UE 110. The UE 110 may monitor for a pending event using an ES11 interface (not shown) . In 548, the UE 110 downloads the CBRS ICCID (e.g., the phantom eSIM) from the SM-DP+ 518 as indicated by the lookup server 520. The UE 110 is now configured with both the MNO SIM and the phantom eSIM.

[0063] In the example provisioning flow 500 of Fig. 5, various components were described as participating in the flow, e.g., AAA, HLR, BSS, SM-DP+, etc. These names are typically associated with a 5G network. The example provisioning flow 500 is not limited to 5G networks. Thus, when performing the provisioning flow on non-5G networks, the components may have different names. Moreover, other components on 5G networks may perform some or all of the operations described for the example provisioning flow 500.

[0064] Fig. 6 shows a call flow 600 for pseudo single SIM mode provisioning according to various example embodiments. The call flow 600 may be a signup call flow (e.g. , the flow utilized by a UE to access a phantom eSIM) . The call flow 600 of Fig. 6includes some of the operations described above with respect to the example provisioning flow 500 of Fig. 5.

[0065] Fig. 6 shows a phantom SIM network entitlement server 604 that enables over-the-air configuration of UE eSIMs. Fig. 6 shows a phantom SIM network BSS 606, which, as described above, is a network function that manages users, billing, and services. Fig. 6 also shows a phantom SIM network SM-DP+ 608, which, as also described above, is a network element (e.g., a server) that prepares, stores, and protects carrier profiles (including operator credentials) . The SM-DP+ 608 may also download and install profiles to a UE eUICC (e.g. , the eUICC 240) . Fig. 6 also shows a lookup server (LS) 610. The LS 610 enables the UE 110 to discover an associated phantom eSIM profile.

[0066] In 612, the UE 110 has an MNO ICCID inserted / activated (e.g., the MNO SIM) . This could be the initial state during UE 110 startup. In 614, the UE 110 transmits a get getEntitlement message with service ="Of f loadsimservice" to the entitlement server 604, e.g. , using the URL of the entitlement server 604 that is included in the MNO carrier bundle of the MNO SIM. Throughout this description, any message that includes the term "getEntitlement" may be considered to be a message related to whether the UE 110 is entitled to offload data service to the phantom SIM network. These various messages are described herein by way of example but as described above different entities may refer to these messages by different names.

[0067] In 616, the entitlement server 604 responds to the UE 110 with a getEntitlement message with the entitlement status equal to 6100, e.g. , indicating the UE is entitled to downloadthe phantom SIM. Thus, at 618, the UE 110 is aware that the user(e.g., subscriber) is entitled to CBRS access.

[0068] In 620, the UE 110 transmits a signUpForSIMService message to the entitlement server 604. The message 620 may include a primary ICCID, an embedded identity document (EID) , and a secondary International Mobile Equipment Identity (IMEI) .

[0069] In 622, the entitlement server 604 transmits a provision CBRS ICCID message to the BSS 606. In 624, the BSS 606 transmits a download / conf irm order message to the SM-DP+ 608. In 626, the SM-DP+ 608 transmits a register event message to the LS 610.

[0070] The ACKs 628, 630, and 632 are transmitted from the LS 610 to the SM-DP+ 608, to the entitlement server 604, respectively .

[0071] In 634, the entitlement server 604 transmits a signUp ForService response message to the UE 110 with an entitlement status equal to 6000, e.g., the UE 110 can download the phantom eSIM. The message 634 also includes an ICCID for the phantom eSIM and a use-ds flag indicating the UE 110 may contact the SM-DP+ 608 for the phantom eSIM.

[0072] In 636, the UE 110 transmits an ICCID download request 636 to the SM-DP+ 608, which responds in 638 with the ICCID corresponding to the phantom eSIM. In 640, the UE 110 installs / has installed the CBRS ICCID (e.g., phantom eSIM) and is ready to use the phantom SIM network.

[0073] As described above, the MNO SIM includes an MNO carrier bundle. Similarly, the phantom eSIM may include aphantom SIM network bundle. The phantom SIM network bundle may include the URL for an entitlement server of the phantom SIM network (e.g. , ES2 510) . Once the phantom eSIM is downloaded and installed, the UE 110 may use the phantom SIM network bundle to contact the entitlement server of the phantom SIM network for the purposes of retrieving geofences for use of the phantom SIM network. The retrieval and use of the geofences will be described in greater detail below.

[0074] Fig. 7 shows a pseudo single SIM trigger diagram 700 according to various example embodiments. Fig. 7 presents three different triggers which may be used individually or in combination for a UE to determine when to perform the call flow 600, e.g., when the UE is triggered to download and install a phantom eSIM.

[0075] The first trigger may occur following a UE restart 704. In 706, the UE 110 may inform an entitlement server (e.g. , ES2 510, ESI 504, etc. ) of a current phantom eSIM if one is installed on the UE 110. If the UE 110 includes a previously installed phantom eSIM, the UE 110 may not download a new phantom eSIM. In some example embodiments, the network (e.g., MNO 550, phantom SIM network 552) may also track the subscription ( s ) associated with an MNO / IMEI. This may prevent the UE 110 from downloading a new phantom eSIM when the UE 110 is already provisioned with a phantom eSIM.

[0076] The second trigger may be MNO SIM reinsertion / MNO SIM installation shown in 708. In 708, a user may remove a SIM card associated with an MNO from the UE 110. In 710, the UE 110 may wait a predetermined amount of time (e.g. , through the use of a guard timer) to delete an associated phantom SIM. For example,the user may temporarily remove the MNO SIM and then reinsert the MNO SIM while the guard timer continues to run. In such a case, the UE 110 would not have to download a new phantom eSIM because the UE 110 has not yet deleted the previously associated phantom eSIM, e.g. , upon reinsertion of the MNO SIM the UE 110 may continue to use the associated phantom eSIM. On the other hand, if the guard timer expires, the UE 110 will delete the associated phantom eSIM such that if the MNO SIM is reinserted, the UE 110 would have to download a new phantom eSIM (e.g. , using the call flow of Fig. 6) . In another scenario, if the user removed the MNO SIM and replaced it with a different MNO SIM, the UE 110 would again have to download a new phantom eSIM (e.g., using the call flow of Fig. 6) that is associated with the different MNO SIM. The guard timer may be set to any appropriate time to prevent deletion of a phantom eSIM based on temporary removal of the MNO SIM.

[0077] A third trigger may be used when an entitlement server is not working. For example, in 712, during an initial signup procedure the UE 110 may attempt to get a phantom eSIM a predetermined number of times (e.g. , five times) . If this signup procedure is unsuccessful (including the retries) , the UE 110 will not have downloaded a phantom eSIM. As stated above, some example triggers are restart or when the user removes / reinstalls / replaces the MNO SIM. However, these actions are not typically performed frequently by a user, e.g., users rarely fully reboot UEs. Instead, a more common action taken when encountering network issues is to toggle airplane mode to cause the UE 110 to reestablish cellular connections.

[0078] Thus, in 714, a user may toggle an airplane mode feature of the UE 110. In response to the toggle, in 716, the UE110 may check if there is a phantom SIM network bound to the MNO. If there is no phantom SIM network bound to the MNO, the UE 110 may again attempt to download the phantom eSIM (up to the predetermined attempt limit) in response to the airplane mode toggling. In this sense, the airplane mode toggle 714 serves as a phantom SIM network reattempt trigger.

[0079] The above provided examples of when a UE may be triggered to download and install a phantom eSIM. The following provide examples of different aspects of managing phantom eSIMs.

[0080] Fig. 8 shows a network diagram 800 related to a synching mechanism according to various example embodiments. The network diagram 800 is a simplified depiction of a syncing mechanism for a phantom CBRS eSIM. The network diagram 800 shows an MNO 802 that may be considered the "primary" network service provider for the UE 110. The MNO 802 may identify the UE 110 by an MNO SIM (not shown) . The UE 110 may also have an associated phantom eSIM (not shown) which is used to verify the UE 110 identity with an Entitlement server 804.

[0081] The UE 110 may have logic to prevent unnecessary phantom eSIM installation. For example, as described above, a restart of the UE 110 may trigger a signup for phantom eSIM service. However, in scenarios where the UE 110 has the same ICCID associated with the MNO SIM for the MNO 802 and the UE 110 has a currently installed phantom eSIM, the UE 110 may not download additional phantom eSIMs. This will be explained in greater detail in Fig. 9.

[0082] Fig. 9 shows a method 900 for preventing a UE from downloading a new phantom eSIM when a previously installedphantom eSIM is bound to an MNO according to various example embodiments. The generation of new ICCIDs results in an expense for the phantom SIM network and the signup and downloading of phantom eSIMs requires UE processing time. Thus, it may be desirable to avoid generating and downloading new phantom SIM network ICCIDs.

[0083] In 902, the UE 110 has an MNO ICCID and phantom SIM network ICCID (for a phantom eSIM) bound. In 904, the UE 110 restarts whether in response to a user action or by internal UE logic. As described above, a UE restart is a trigger for a signup for a phantom eSIM. However, as described above, there may be advantages to avoiding generating and downloading new phantom eSIMs when it is not necessary.

[0084] Therefore, in 906, the UE 110 determines whether there is a phantom eSIM already installed and bound to the MNO. If there is a phantom eSIM already installed and bound to the MNO, the UE 110 proceeds to 908 and does not install a new phantom eSIM, e.g., the UE 110 does not send a signup request for a new phantom eSIM and the phantom SIM network does not need to generate a new phantom SIM network ICCID.

[0085] If there is not a phantom eSIM already installed or if there is no binding for the phantom eSIM to the MNO, the UE 110 proceeds to 910 and installs a new phantom eSIM (via, for example, the call flow 600) . One of skill in the art will understand that there may be various scenarios that may cause a UE to lose a binding for a phantom eSIM, e.g. , the UE 110 has a phantom eSIM installed but it is not bound to the MNO. In 912,the UE 110 has a new phantom SIM network and MNO binding for the newly downloaded phantom eSIM.

[0086] Some example embodiments for managing phantom eSIMs are related to phantom eSIM entitlement change logic. An MNO may choose per account phantom eSIM enablement based on a user subscription plan. For example, the MNO may choose to elevate the level of service a user receives based on the geographic location of the user or in some cases deny the user phantom SIM network service based on the geographic location or any other subscription related factor. The UE and / or the network may be provided with logic to handle such scenarios. Figs. 10A, 10B, and 10C describe these example embodiments. The flow diagrams of Figs. 10A-C may be implemented on a UE alone or in combination with network components.

[0087] Fig. 10A shows a method 1000 for controlling entitlement changes when a UE does not currently have a phantom eSIM installed according to various example embodiments. The method 1000 may be applicable to scenarios in which there is no phantom eSIM on the UE 110.

[0088] Initially, in 1004, there is no phantom eSIM installed on the UE 110. In 1006, the UE 110 transmits the signupf orSIMService message (e.g., operation 616 in Fig. 6) to an entitlement server (e.g., the Entitlement server 604) .

[0089] In 1008, the Entitlement server transmits back an entitlement. In the example of Fig. 10A, this entitlement is in the negative (e.g. , action status: Status_Disallowed_Action) . In 1010, the UE 110 does not install a phantom eSIM. However, if the entitlement status changes in the future (e.g., the UE 110moves to a different geographic area) , the UE 110 may again attempt to install the phantom eSIM, e.g. , the UE 110 may send additional signupforSIMService messages at a later time to attempt to install a phantom eSIM.

[0090] Fig. 10B shows a method 1001 for controlling entitlement changes when a UE currently has a phantom eSIM installed according to various example embodiments. The method diagram 1001 may be applicable to scenarios in which the UE 110 has a phantom eSIM installed.

[0091] In 1012, the UE 110 has an MNO ICCID and phantom SIM network ICCID bound. In 1014, the user may restart the UE 110 or the UE 110 may restart due to internal logic, e.g., such as for a software update procedure. As described above, the restart of the UE 110 may be a trigger for the UE 110 to signup for phantom eSIM service.

[0092] In 1016, the UE 110 transmits the signupforSIMService message (e.g. , operation 616 in Fig. 6) to an entitlement server(e.g., the Entitlement server 604) . In 1017, the Entitlement server transmits back an entitlement. In the example of Fig. 10B, this entitlement is in the negative (e.g. , action status: Status Disallowed Action) .

[0093] In 1018, the Entitlement server may specify an on-UE phantom eSIM state. The entitlement and the on-UE phantom eSIM state may be sent in the same message or different messages. This state may be delete or disable. This may occur, for example, if a user changes their cellular plan such that they no longer are subscribed for phantom SIM connections. Two exampleeSIM states may be STATUS_DISALLOWED_ACTION, Delete and STATUS_DISALLOWED_ACTION, Disable .

[0094] In 1020, the UE 110 determines the status received in 1018. If the status is delete, the UE 110 proceeds to 1022 and deletes the phantom eSIM. If the status received in 1018 is disable, the UE 110 proceeds to 1024 and disables the phantom eSIM.

[0095] Fig. 10C shows a second method 1002 for controlling entitlement changes when a UE currently has a phantom eSIM installed according to various example embodiments. The method 1002 may be applicable to situations in which the entitlement status changes.

[0096] In 1026, the UE 110 has an MNO ICCID and phantom SIM network ICCID bound. In 1028, an Entitlement server may change the entitlement status, for example, to STATUS_DISABLED_ENTITLEMENT. For example, the Entitlement server may determine that there are no geofences in the geographic location of the UE 110 and therefore the phantom eSIM should not be used, e.g. , should be disabled. Thus, in 1030, the UE 110 may disable the phantom eSIM. The phantom eSIM may remain in the disabled state until receiving a positive entitlement from the Entitlement server.

[0097] Some example embodiments for managing phantom eSIMs relate to MNO SIM removal. A phantom SIM network subscription is typically associated with an MNO. When a user removes an MNO SIM (or disables an MNO eSIM) , the phantom SIM network subscription should be rendered inactive.

[0098] Throughout the remainder of the disclosure, reference to removal of a SIM card may refer to removing a physical SIM card, or it may refer to disabling an eSIM. When this distinction is relevant to a particular embodiment, it will be noted appropriately. Similarly, reference to "reinserting" a SIM may refer to a user performing a physical reinsertion of a SIM card, or it may refer to enabling an eSIM. When this difference is relevant, it will be appropriately noted.

[0099] Fig. 11 shows a method 1100 for managing a phantom eSIM when an MNO SIM is removed according to various example embodiments .

[0100] In 1102, the UE 110 has an MNO ICCID (e.g. , MNO SIM or eSIM) and phantom SIM network ICCID (e.g. , phantom eSIM) bound. In 1104, the user may remove the MNO SIM. In 1106, the UE 110 may delete the phantom eSIM. In 1108, the MNO SIM is reinserted. In 1110, the UE 110 may perform a phantom SIM network signup procedure (e.g., the call flow 600) .

[0101] In some situations, it may be desirable to not immediately delete a phantom eSIM upon MNO SIM removal. For example, there may be security concerns related to malicious actors attacking the SMDP+, ICCID database depletion due to over usage, physical SIM contact issues (e.g. , contacts may become loose over time which may appear as a SIM removal (false positives) ) , additional signaling delays, etc. Thus, some example embodiments for managing phantom eSIMs related to MNO SIM removal may incorporate additional checks prior to deleting or disabling a phantom eSIM to account for the various issues.

[0102] Fig. 12 shows a method 1200 for managing a phantom eSIM when an MNO SIM is removed that incorporates a timer according to various example embodiments.

[0103] In 1202, the UE 110 has an MNO ICCID (e.g. , MNO SIM or eSIM) and phantom SIM network ICCID (e.g. , phantom eSIM) bound. In 1204, the user may remove the MNO SIM. In 1206, the UE 110 may disable the phantom eSIM. In 1208, the UE 110 starts a timer. The timer may be a predetermined length of time (e.g., 30 minutes) . This length of time may be left to MNO / phantom SIM network / OEM implementation. In 1210, the MNO SIM is reinserted in the UE 110. In 1212, the UE 110 determines whether the timer has expired. If the timer has expired, the UE 110 deletes the bound phantom eSIM in 1214. If the timer has not expired, the UE 110 proceeds to 1216 and reenables the previously disabled phantom eSIM.

[0104] In some example embodiments, instead of deleting the phantom eSIM in 1214, the UE 110 may keep the phantom eSIM on the UE 110 until a configurable maximum count is reached. For example, the UE 110 may have multiple phantom eSIMs stored on the UE 110 but only 0 or 1 phantom eSIMs may be enabled at a given time. The UE 110 may keep a disabled phantom eSIM on the UE 110 until it is later re-enabled or is deleted when the UE reaches a configured maximum number of phantom eSIMs (e.g. , three) . For example, the UE 110 may be configured to have a first in, first out (FIFO) buffer such that a user reinserting an MNO SIM may reuse the associated phantom eSIM until the number of SIMs inserted into the UE reaches the maximum count. For example, a UE with a buffer of three may store the phantom eSIMs associated with three MNO SIMs. When a fourth MNO SIM is inserted, the phantom eSIM associated with the first inserted(chronologically first) MNO SIM may be deleted. For example, if MN01 SIM is inserted Monday, MN02 SIM is inserted Tuesday, and MN03 SIM is inserted Wednesday, insertion of an MN04 SIM would cause the UE to delete the phantom eSIM associated with the MN01 SIM.

[0105] In other example embodiments, the UE may delete the phantom eSIM that was least recently used. For example, if the phantom eSIM associated with MN02 SIM was last used on Monday, the phantom eSIM associated with MN01 SIM was last used on Tuesday, and the phantom eSIM associated with MN03 SIM was last used on Wednesday, insertion of an MN04 SIM would cause the UE to delete the phantom eSIM associated with the MN02 SIM.

[0106] Some example embodiments for managing phantom eSIMs relate to replacement of a primary subscription. For example, a user may install an MNO SIM2 that may cause an MNO SIM1 to be disabled. Disabling the MNO SIM1 may also disable a bound phantom eSIMl .

[0107] Fig. 13 shows a network diagram 1300 related to replacement of a primary subscription according to various example embodiments. The network diagram 1300 shows the UE 110, an MNO 1302, an Entitlement server 1304, and an SM-DP+ 1306. The MNO network diagram 1300 shows an initial state where an MNO SIM1 and phantom eSIMl are active. The MNO network diagram 1300 then shows a subsequent state where an MNO SIM2 and phantom eSIM2 are active and the MNO SIM1 and phantom eSIMl are inactive. This subsequent state may be a result of a user inserting the MNO SIM2 into the UE 110. This may cause the UE 110 to disable the MNO SIM1 and the associated phantom eSIMl. In addition, this may also cause the UE 110 to perform the phantomSIM network signup procedure with the Entitlement server 1304 (e.g., the call flow 600) to obtain the phantom eSIM2 associated with the MNO SIM2 from the SM-DP+ 1306. In this example, it is considered that the operations were successful and the MNO SIM2 and phantom eSIM2 are active. In the example of Fig. 13, it is considered that the MNO for the MNO SIM1 and MNO SIM2 are the same MNO. However, this does not have to be the case. Further description of replacement of a primary subscription will be provided below with reference to Fig. 14.

[0108] Fig. 14 shows a method 1400 for managing phantom eSIMs when a primary subscription is replaced according to various example embodiments.

[0109] In 1402, the UE 110 has an MNO ICCID (e.g. , MNO SIM1) and phantom SIM network ICCID (e.g. , phantom eSIMl) bound. In 1403, the user may remove the MNO SIM1. In 1404, the user may install an MNO SIM2. In 1406, the UE 110 determines whether a binding between the installed MNO (e.g., MNO SIM2) and a phantom SIM network exists. If there is an associated binding, the UE 110 proceeds to 1408 and does not install a new phantom eSIM, e.g., the UE 110 includes a previously downloaded and installed phantom eSIM associated with the MNO SIM2. If there is not an associated binding, the UE 110 proceeds to 1410 and downloads and installs a new phantom eSIM2 (e.g., using the signup procedure of Fig. 6) . In 1412, the UE 110 binds MNO2 and phantom eSIM2. In 1414, the phantom eSIMl is disabled (but not deleted) .

[0110] Some example embodiments for managing phantom eSIMs relate to mode switching between the pseudo-single SIM mode to a true dual SIM mode. For example, in some scenarios, a user may install an MNO SIM2 to a UE operating with an MNO SIM1 and aphantom eSIM. It may be desirable in some situations to switch from pseudo-single SIM mode to true dual SIM operations.

[0111] Fig. 15 shows a method 1500 for mode switching between a pseudo-single SIM mode to a true dual SIM mode according to various example embodiments.

[0112] In 1502, the UE 110 has an MNO ICCID (e.g. , MNO SIM1) and phantom SIM network ICCID (e.g. , phantom eSIMl) bound. In 1504, MNO SIM1 remains enabled. In 1506, the user installs an MNO SIM2. In 1508, the UE 110 determines whether the MNO SIM2 is from the same MNO as the SIM1. If no, the UE 110 proceeds to 1510 and does not install a new phantom eSIM. In 1512, the UE 110 retains the MNO1 and phantom eSIMl binding. In 1514, the phantom eSIMl is disabled (e.g., the active SIMs are MNO SIM1 and MNO SIM2, with no phantom eSIMs active) .

[0113] If in 1508 the MNO SIM2 is from the same MNO as the SIM1, the UE 110 proceeds to 1516 and installs a phantom eSIM2 (e.g., using the signup procedure of Fig. 6) . In 1518, the UE 110 binds MNO2 with phantom eSIM2. In 1520, the phantom eSIMl is disabled and the phantom eSIM2 is disabled. In 1522, the UE 110 enters a dual SIM dual standby mode (DSDS) . If the user later disables the MNO SIM1, the UE 110 proceeds to 1524 and the MNO SIM2 and phantom eSIM2 may become active. If the user disables the MNO SIM2, the MNO SIM1 and phantom eSIMl may become active.

[0114] Some example embodiments for managing phantom eSIMs relate to maximum subscription management. For example, these example embodiments may relate to scenarios where installation of a subsequent (e.g., third) MNO SIM may exceed a maximum supported number of MNOs on a UE . In these examples, the maximumnumber of subscriptions may be based on UE capability and / or operator preference.

[0115] Fig. 16 shows a first method 1600 for managing a maximum number of subscriptions on a UE according to various example embodiments.

[0116] In 1602, the UE 110 has an MNO ICCID (e.g. , MNO SIM1) and phantom SIM network ICCID (e.g. , phantom eSIMl) bound. In 1604, MNO SIM1 remains enabled. In 1606, the user installs an MNO SIM2 that is capable of supporting offload (e.g. , phantom eSIM2 operations) . In 1608, the UE 110 binds MN02 with phantom eSIM2. In 1610, phantom eSIMl is disabled and phantom eSIM2 is disabled .

[0117] In 1612, a user may install an additional MNO SIM (e.g., MNO SIM3) . In 1614, the UE 110 determines whether the maximum MNO count has been reached. If the maximum MNO count has not been reached, the UE 110 may proceed to 1617 and attempts the signup procedure with the entitlement server to download and install a phantom eSIM3 associated with the MNO SIM3. If the maximum MNO count has been reached, the UE 110 proceeds to 1616 and halts further signups towards the entitlement server. If at a later time, one of the MNOs currently stored on the UE 110 is deleted, e.g. , MNO SIM1 or MNO SIM2, in 1618, the UE 110 may send a phantom SIM network sign up message to the Entitlement server to attempt to download and install a phantom eSIM3 associated with the MNO SIM3.

[0118] Fig. 17 shows a second method 1700 for managing a maximum number of subscriptions on a UE according to various example embodiments.

[0119] In 1702, the UE 110 has an MNO ICCID (e.g. , MNO SIM1) and phantom SIM network ICCID (e.g. , phantom eSIMl) bound. In 1704, MNO SIM1 remains enabled. In 1706, the user installs an MNO SIM2 that is capable of supporting offload (e.g. , phantom eSIM2 operations) . In 1708, the UE 110 binds MN02 with phantom eSIM2. In 1710, phantom eSIMl is disabled and phantom eSIM2 is disabled .

[0120] In 1712, a user may install an additional MNO SIM (e.g., MNO SIM3) . In 1714, the UE 110 determines whether the maximum MNO count has been reached. If the maximum MNO count has not been reached, the UE 110 may proceed to 1717 and attempts the signup procedure with the entitlement server to download and install a phantom eSIM3 associated with the MNO SIM3. If the maximum MNO count has been reached, the UE 110 proceeds to 1716 and deletes the phantom eSIMl (e.g. , following a FIFO logic) . In 1718, the UE 110 installs phantom eSIM3. In 1720, the phantom eSIM2 is disabled and the phantom eSIM3 is disabled.

[0121] Some example embodiments for managing phantom eSIMs relate to unregulated subscriptions. For example, in some scenarios, a phantom SIM network may inadvertently provide two phantom eSIMs for the same MNO. These example embodiments do not just ignore the second (e.g. , erroneous) phantom eSIM, but will inform the network that the extra ICCID is in the released state .

[0122] Fig. 18 shows a method 1800 for handling unregulated subscriptions according to various example embodiments. In 1802, the UE 110 may have an MNO ICCID associated with an MNO SIM. In 1804, the UE 110 performs a signup for a phantom eSIM service towards an Entitlement server. In 1806, an SM-DP+ provides more than one phantom eSIM to the UE 110. In 1808, the UE 110 installs the phantom eSIMl and binds it with the MNO SIM1. In 1810, the UE 110 determines that the received phantom eSIM2 was for the same mobile directory number (MDN) as the phantom eSIMl. In 1812, the UE 110 deletes the phantom eSIM2. In 1814, the UE 110 transmits a message to the SM-DP+ of the deletion of the phantom eSIM2.

[0123] Some example embodiments for managing phantom eSIMs relate to deleting phantom eSIM subscriptions. As described above, phantom eSIMs are not presented to a user during the course of typical operations, e.g. , the phantom eSIM is transparent to the user. These example embodiments are related to deleting a phantom eSIM during a typical UE erase all content and settings (EACS) operation.

[0124] Fig. 19 shows a method 1900 for deleting phantom eSIM subscriptions according to various example embodiments. In 1902, the UE 110 has an MNO ICCID (e.g., MNO SIM) and phantom SIM network ICCID (e.g. , phantom eSIM) bound. In 1904, a user may perform an EACS procedure, for example, before recycling or selling their UE 110. In 1906, the UE 110 deletes all SIM cards, including the phantom eSIM. In 1908, the UE 110 completes the EACS procedure and all phantom SIM network and MNO SIMs are deleted. The user has successfully wiped their phantom eSIM without ever needing to specifically indicate that it should bedeleted. In other example embodiments, a user may select an option to "reset" the MNO. In such a scenario, the UE 110 may only delete the associated phantom eSIM during 1906.

[0125] Some example embodiments for managing phantom eSIMs relate to phantom eSIM subscription transfer. In some situations, it may be desirable to preserve a phantom eSIM on a UE after an MNO SIM transfer. For example, a user may transfer their SIM from a personal UE to a work UE for a limited period of time, and then transfer the MNO SIM back to the personal UE . In such a scenario, it may be desirable to keep an associated phantom eSIM preserved on the personal UE such that reunification with the MNO SIM is seamless and nearly instant from the perspective of the user.

[0126] Fig. 20 shows a method 2000 for phantom eSIM subscription transfer according to various example embodiments. In 2002, a first UE has an MNO ICCID (e.g. , MNO SIM) and phantom SIM network ICCID (e.g. , phantom eSIM) bound. In 2004, a user may initiate an MNO SIM transfer (whether physical or eSIM) from a first UE to a second UE . In 2006, the second UE has the MNO SIM, but not the phantom eSIMl, which is still on the first UE . In 2008, the second UE performs a phantom SIM network SIM signup (e.g., the call flow 600) . In 2010, the second UE binds the phantom eSIM2 and the MNO SIM (e.g. , the SIM originally installed on the first UE) . In 2012, the phantom eSIMl is preserved on the first UE for the scenario when the user reinstalls the MNO SIM on the first UE .

[0127] These example embodiments may be modified by addition of a timer function that deletes the phantom eSIMl from the first UE after a specified time period. This may prevent ascenario where the phantom eSIMl is abandoned because the MNO SIM is never returned to the first UE .

[0128] Some example embodiments are related to user interface (UI) enhancements for pseudo-single SIM operations. An objective of phantom eSIMs is minimizing user management of pseudo-single SIM setup. Ideally, a user should enter a geographic area that the phantom SIM supports, and coverage should be enhanced seamlessly. This may be illustrated by contrasting an enhanced UI as shown in Fig. 21B against an existing UI for true dual SIM operations as shown in Fig. 21A.

[0129] Fig. 21A shows a first user interface diagram 2100 according to various example embodiments. Fig. 2 IB shows a second user interface diagram 2106 according to various example embodiments .

[0130] The UI diagram 2100 shows a typical UI when true dual SIMs are active on a UE (e.g. , the UE 110) . A first SIM may correspond to an MNO 2102, and a second SIM may correspond to an MNO 2104. Each of the MNOs 2102 and 2104 have network strength indicators (e.g., the bars) and are labeled by name in the UI (e.g., "MNO1 Mobile 5G") . Each SIM in this typical UI is its own independent entity, and a user may immediately see network strength differences between the two networks associated with the two S IMs .

[0131] Fig. 21B shows a UI diagram 2106 for pseudo-single SIM operations. Unlike the UI 2100, the UI 2106 does not have separate and distinct entities for each SIM. For example, an MNO 2108 may be the primary service provider of the UE 110. The MNO 2108 may have its network strength always shown because the MNOSIM is IMS registered and has voice capabilities associated with it. The UI 2106 also shows "MSO Mobile 5G" serving as a radio access technology (RAT) indicator 2110. The RAT indicator 2110 may change to the specific RAT that the UE 110 is currently using. For example, if the UE 110 is outside the range of the phantom SIM network eSIM area, the RAT indicator 2110 may instead show a MNO RAT instead (similar to Fig. 21A) .Examples

[0132] In a first example, a method comprising storing a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an entitlement server of a phantom SIM network, determining a trigger condition has occurred, configuring transceiver circuitry to transmit a getEntitlement message to the Entitlement server and decoding, from signaling received from the Entitlement server, a getEntitlement response message indicating whether the UE may offload MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number.

[0133] In a second example, the method of the first example, wherein the getEntitlement response message indicates the UE may offload MNO SIM service to the eSIM, the method further comprising configuring transceiver circuitry to transmit a signUp ForSIMService message to the Entitlement server, wherein the signUpForSIMService message comprises a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, decoding, from signaling received from theEntitlement server, a signUpForSIMService response message comprising an ICCID of the eSIM of the phantom SIM network, configuring transceiver circuitry to transmit a download ICCID request message comprising the ICCID of the eSIM to a phantom SIM network subscription manager-data preparation+ (SM-DP+) , decoding, from signaling received from the SM-DP+, the eSIM of the phantom SIM network and installing the eSIM of the phantom SIM network on the UE .

[0134] In a third example, the method of the second example, wherein the eSIM for the phantom SIM network is for a Citizens Broadband Radio Service (CBRS) network.

[0135] In a fourth example, the method of the second example, further comprising decoding, from signaling received from the Entitlement server, one or more geofences, performing data operations using the eSIM of the phantom SIM network when within a geographic area within the one or more geofences and performing data operations using the MNO SIM when not within the geographic area within the one or more geofences.

[0136] In a fifth example, the method of the second example, wherein the trigger condition comprises a restart of the UE, an insertion of the MNO SIM or a toggling of an airplane mode of the UE.

[0137] In a sixth example, the method of the second example, further comprising determining a second trigger condition has occurred, configuring transceiver circuitry to transmit a second getEntitlement message to the Entitlement server, decoding, from signaling received from the Entitlement server, a secondgetEntitlement response message indicating the UE may not offload MNO SIM service to the eSIM of the phantom SIM network, decoding, from signaling received from the Entitlement server, a status of the eSIM of the phantom SIM network.

[0138] In a seventh example, the method of the sixth example, wherein the status of the eSIM is disabled, the method further comprising disabling the eSIM.

[0139] In an eighth example, the method of the sixth example, wherein the status of the eSIM is deleted, the method further comprises deleting the eSIM.

[0140] In a ninth example, the method of the second example, further comprising decoding, from signaling received from the Entitlement server, a message indicating the UE may not offload MNO SIM service to the eSIM of the phantom SIM network and disabling the eSIM in response to the message.

[0141] In a tenth example, the method of the second example, further comprising determining the MNO SIM has been removed from the UE, wherein the MNO SIM is a physical SIM or an eSIM.

[0142] In an eleventh example, the method of the tenth example, further comprising deleting the eSIM of the phantom SIM network in response to determining the MNO SIM has been removed from the UE .

[0143] In a twelfth example, the method of the eleventh example, further comprising determining the MNO SIM has been reinstalled in the UE, in response to the MNO SIM beingreinstalled, configuring transceiver circuitry to transmit a second signUpForSIMService message to the Entitlement server, decoding, from signaling received from the Entitlement server, a second signUpForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network associated with the MNO SIM, configuring transceiver circuitry to transmit a download ICCID request message comprising the ICCID of the second eSIM to the SM-DP+, decoding, from signaling received from the SM-DP+, the second eSIM of the phantom SIM network and installing the second eSIM of the phantom SIM network on the UE .

[0144] In a thirteenth example, the method of the tenth example, further comprising disabling the eSIM in response to determining the MNO SIM has been removed from the UE and initiating a timer.

[0145] In a fourteenth example, the method of the thirteenth example, further comprising determining the MNO SIM has been reinstalled in the UE and resetting the timer.

[0146] In a fifteenth example, the method of the fourteenth example, wherein, when the timer has not expired, the method further comprising reenabling the eSIM.

[0147] In a sixteenth example, the method of the thirteenth example, further comprising determining the timer has expired and deleting the eSIM.

[0148] In a seventeenth example, the method of the second example, further comprising disabling the MNO SIM, determining asecond MNO SIM is installed on the UE, and determining whetherUE includes a second eSIM bound with the second MNO SIM.

[0149] In an eighteenth example, the method of the seventeenth example, wherein, when the UE includes the second eSIM bound with the second MNO SIM, the method further comprising preventing the UE from downloading a further eSIM associated with the second MNO SIM.

[0150] In a nineteenth example, the method of the seventeenth example, wherein, when the UE does not include the second eSIM bound with the second MNO SIM, the method further comprising configuring transceiver circuitry to transmit a second signUp ForSIMService message to the Entitlement server, decoding, from signaling received from the Entitlement server, a second signUp ForSIMService response message comprising an ICCID of the second eSIM of the phantom SIM network associated with the second MNO SIM, configuring transceiver circuitry to transmit a download ICCID request message comprising the ICCID of the second eSIM to the SM-DP+, decoding, from signaling received from the SM-DP+, the second eSIM of the phantom SIM network, installing the second eSIM of the phantom SIM network on the UE and disabling the eSIM.

[0151] In a twentieth example, the method of the second example, further comprising determining a second MNO SIM is installed on the UE, and determining whether the second MNO SIM is related to a same MNO as the MNO SIM.

[0152] In a twenty first example, the method of the twentieth example, wherein when the second MNO SIM is not related to thesame MNO as the MNO SIM, the method further comprising preventing the UE from downloading a second eSIM associated with the second MNO SIM, disabling the eSIM and configuring the UE to operate in a dual SIM mode.

[0153] In a twenty second example, the method of the twentieth example, wherein when the second MNO SIM is related to the same MNO as the MNO SIM, the method further comprising configuring transceiver circuitry to transmit a second signUp ForSIMService message to the Entitlement server, decoding, from signaling received from the Entitlement server, a second signUp ForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network associated with the second MNO SIM, configuring transceiver circuitry to transmit a download ICCID request message comprising the ICCID of the second eSIM to the SM-DP+, decoding, from signaling received from the SM-DP+, the second eSIM of the phantom SIM network, installing the second eSIM of the phantom SIM network on the UE, disabling the eSIM and the second eSIM and configuring the UE to operate in a dual SIM mode.

[0154] In a twenty third example, the method of the twenty second example, further comprising disabling the MNO SIM and enabling the second eSIM.

[0155] In a twenty fourth example, the method of the twenty second example, further comprising disabling the second MNO SIM and enabling the eSIM.

[0156] In a twenty fifth example, the method of the second example, further comprising determining a second MNO SIM isinstalled on the UE, configuring transceiver circuitry to transmit a second signUpForSIMService message to the Entitlement server, decoding, from signaling received from the Entitlement server, a second signUpForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network associated with the second MNO SIM, configuring transceiver circuitry to transmit a download ICCID reguest message comprising the ICCID of the second eSIM to the SM-DP+, decoding, from signaling received from the SM-DP+, the second eSIM of the phantom SIM network, installing the second eSIM of the phantom SIM network on the UE, disabling the eSIM and the second eSIM, determining a third MNO SIM is installed on the UE and determining whether the third MNO SIM exceeds a maximum number of MNO subscriptions.

[0157] In a twenty sixth example, the method of the twenty fifth example, wherein, when the third MNO SIM exceeds the maximum number of MNO subscriptions, the method further comprising preventing the UE from downloading an eSIM associated with the third MNO SIM.

[0158] In a twenty seventh example, the method of the twenty fifth example, wherein, when the third MNO SIM exceeds the maximum number of MNO subscriptions, the method further comprising deleting the eSIM based on the eSIM being a first loaded eSIM on the UE, configuring transceiver circuitry to transmit a third signUpForSIMService message to the Entitlement server, decoding, from signaling received from the Entitlement server, a third signUpForSIMService response message comprising an ICCID of a third eSIM of the phantom SIM network associated with the third MNO SIM, configuring transceiver circuitry to transmit a download ICCID reguest message comprising the ICCIDof the third eSIM to the SM-DP+, decoding, from signaling received from the SM-DP+, the third eSIM of the phantom SIM network and installing the third eSIM of the phantom SIM network on the UE .

[0159] In a twenty eighth example, the method of the second example, wherein the decoding of the signaling received from the SM-DP+ comprises the UE receiving the eSIM and a second eSIM, the method further comprising deleting the second eSIM and configuring transceiver circuitry to transmit an indication to the SM-DP+ that the second eSIM has been deleted from the UE .

[0160] In a twenty ninth example, the method of the second example, the method further comprising receiving an input from a user to perform an erase all content and settings (EACS) operation for the UE and performing an EACS operation comprising deleting the eSIM.

[0161] In a thirtieth example, the method of the first example, further comprising determining the UE does not include an eSIM bound with the MNO SIM.

[0162] In a thirty first example, the method of the first example, wherein the getEntitlement response message indicates the UE may not offload MNO SIM service to the eSIM, the method further comprising preventing the UE from downloading the eSIM associated with the MNO SIM.

[0163] In a thirty second example, a processor configured to perform the methods of any of the first through thirty first examples .

[0164] In a thirty third example, a user equipment comprising transceiver circuitry configured to communicate with a network and a processor communicatively coupled to the transceiver circuitry and configured to perform the methods of any of the first through thirty first examples.

[0165] In a thirty fourth example, a method comprising storing a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an entitlement server of a phantom SIM network, determining a trigger condition has occurred, wherein the trigger condition is related to the UE performing operations related to offloading MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, determining the UE includes an eSIM bound with the MNO SIM and preventing the UE from downloading a further eSIM associated with the MNO SIM.

[0166] In a thirty fifth example, a processor configured to perform the method of the thirty fourth example.

[0167] In a thirty sixth example, a user equipment comprising transceiver circuitry configured to communicate with a network and a processor communicatively coupled to the transceiver circuitry and configured to perform the method of the thirty fourth example.

[0168] In a thirty seventh example, a method comprising receiving a getEntitlement message from a user equipment (UE) , sending, to the UE, a getEntitlement response message indicating the UE may offload mobile network operator (MNO) subscriberidentity module (SIM) service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number, receiving, from the UE, a signUp ForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, sending, to a business support system (BSS) of the phantom SIM network, a provisioning message requesting the eSIM be provisioned for the UE, receiving, from the BSS, a provisioning response indicating the eSIM has been provisioned for the UE and sending, to the UE, a signUp ForS IMService response message comprising an ICCID of the eSIM of the phantom SIM network.

[0169] In a thirty eighth example, a processor configured to perform the method of the thirty seventh example.

[0170] In a thirty ninth example, a server device comprising a network interface configured to communicate with a network and a processor communicatively coupled to the network interface and configured to perform the method of the thirty fourth example.

[0171] In a fortieth example, a method comprising performing an operation to transfer a mobile network operator (MNO) subscriber identity module (SIM) from a further UE to the UE, wherein the further UE comprises a first phantom SIM network embedded SIM (eSIM) , storing a carrier bundle associated with the MNO SIM, wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an Entitlement server of a phantom SIM network, configuring transceiver circuitry to transmit a getEntitlement message to the Entitlement server and decoding, from signaling received fromthe Entitlement server, a getEntit lement response message indicating the UE may offload MNO SIM service to the phantom SIM network, configuring transceiver circuitry to transmit a signUp ForSIMService message to the Entitlement server, wherein the signUpForSIMService message comprises a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity, decoding, from signaling received from the Entitlement server, a signUpForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network, wherein the second eSIM is different from the first eSIM, configuring transceiver circuitry to transmit a download ICCID request message comprising the ICCID of the second eSIM to a phantom SIM network subscription manager-data preparation+ (SM- DP+) , decoding, from signaling received from the SM-DP+, the second eSIM of the phantom SIM network and installing the second eSIM of the phantom SIM network on the UE .

[0172] In a forty first example, a processor configured to perform the method of the fortieth example.

[0173] In a forty second example, a user equipment comprising transceiver circuitry configured to communicate with a network and a processor communicatively coupled to the transceiver circuitry and configured to perform the method of the fortieth example .

[0174] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An example hardware platform for implementing theexample embodiments may include , for example, an Intel x86 based platform with compatible operating system, a Windows OS , a Mac platform and MAC OS , a mobile device having an operating system such as iOS , Android, etc . The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that , when compiled, may be executed on a processor or microprocessor .

[0175] Although this application described various embodiments each having different features in various combinations , those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not speci fically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[0176] It is well understood that the use of personally identi fiable information should follow privacy policies and practices that are generally recogni zed as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identifiable information data should be managed and handled so as to minimi ze risks of unintentional or unauthori zed access or use , and the nature of authori zed use should be clearly indicated to users .

[0177] It will be apparent to those skilled in the art that various modi fications may be made in the present disclosure , without departing from the spirit or the scope of the disclosure . Thus , it is intended that the present disclosurecover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

What is claimed:

1. An apparatus comprising processing circuitry configured to : store a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises an address for a MNO entitlement server of an MNO network and an entitlement server of a phantom SIM network; determine a trigger condition has occurred; generate, for transmission to the entitlement server, a getEntitlement message; process, based on signaling received from the entitlement server, a getEntitlement response message indicating a user eguipment (UE) is allowed to offload MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number; generate, for transmission to the entitlement server, a signUp ForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Eguipment Identity; process, based on signaling received from the entitlement server, a signUpForSIMService response message comprising an ICCID of the eSIM of the phantom SIM network; generate, for transmission to a phantom SIM network subscription manager-data preparation+ (SM-DP+) , a download ICCID request message comprising the ICCID of the eSIM; process, based on signaling received from the SM-DP+, the eSIM of the phantom SIM network; and install the eSIM of the phantom SIM network on the UE .

2. The apparatus of claim 1, wherein the eSIM for the phantom SIM network is for a Citizens Broadband Radio Service (CBRS) network .

3. The apparatus of claim 1, wherein the processing circuitry is further configured to: process, based on signaling received from the entitlement server, one or more geofences; perform data operations using the eSIM of the phantom SIM network when within a geographic area within the one or more geofences; and perform data operations using the MNO SIM when not within the geographic area within the one or more geofences.

4. The apparatus of claim 1, wherein the trigger condition comprises a restart of the UE, an insertion of the MNO SIM or a toggling of an airplane mode of the UE .

5. The apparatus of claim 1, wherein the processing circuitry is further configured to: determine a second trigger condition has occurred; generate, for transmission to the entitlement server, a second getEntitlement message; process, based on signaling received from the entitlement server, a second getEntitlement response message indicating the UE may not offload MNO SIM service to the eSIM of the phantom SIM network; process, based on signaling received from the entitlement server, a status of the eSIM of the phantom SIM network.

6. The apparatus of claim 5, wherein the status of the eSIM is disabled, wherein the processing circuitry is further configured to : disable the eSIM.

7. The apparatus of claim 5, wherein the status of the eSIM is deleted, wherein the processing circuitry is further configured to : delete the eSIM.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to: process, based on signaling received from the entitlement server, a message indicating the UE may not offload MNO SIM service to the eSIM of the phantom SIM network; and disable the eSIM in response to the message.

9. The apparatus of claim 1, wherein the processing circuitry is further configured to: determine the MNO SIM has been removed from the UE, wherein the MNO SIM is a physical SIM or an eSIM.

10. The apparatus of claim 9, wherein the processing circuitry is further configured to: delete the eSIM of the phantom SIM network in response to determining the MNO SIM has been removed from the UE .

11. The apparatus of claim 10, wherein the processing circuitry is further configured to: determine the MNO SIM has been reinstalled in the UE;in response to the MNO SIM being reinstalled, generate, for transmission to the entitlement server, a second signUp ForSIMService message; process, based on signaling received from the entitlement server, a second signUp ForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network associated with the MNO SIM; generate, for transmission to the SM-DP+, a download ICCID request message comprising the ICCID of the second eSIM; process, based on signaling received from the SM=DP+, the second eSIM of the phantom SIM network; and install the second eSIM of the phantom SIM network on the UE .

12. The apparatus of claim 9, wherein the processing circuitry is further configured to: disable the eSIM in response to determining the MNO SIM has been removed from the UE; initiate a timer; and when the MNO SIM has been reinstalled in the UE, reset the timer, or when the timer has not expired, reenable the eSIM, or when the timer has expired, delete the eSIM.

13. The apparatus of claim 1, wherein the processing circuitry is further configured to: disable the MNO SIM; determine a second MNO SIM is installed on the UE; and determine whether UE includes a second eSIM bound with the second MNO SIM.

14. The apparatus of claim 13, wherein, when the UE includes the second eSIM bound with the second MNO SIM, the processing circuitry is further configured to: prevent the UE from downloading a further eSIM associated with the second MNO SIM.

15. The apparatus of claim 13, wherein, when the UE does not include the second eSIM bound with the second MNO SIM, the processing circuitry is further configured to: generate, for transmission to the entitlement server, a second signUpForSIMService message; process, based on signaling received from the entitlement server, a second signUpForSIMService response message comprising an ICCID of the second eSIM of the phantom SIM network associated with the second MNO SIM; generate, for transmission to the SM-DP+, a download ICCID request message comprising the ICCID of the second eSIM; process, based on signaling received from the SM-DP+, the second eSIM of the phantom SIM network; install the second eSIM of the phantom SIM network on the UE ; and disable the eSIM.

16. The apparatus of claim 1, wherein the processing circuitry is further configured to: determine a second MNO SIM is installed on the UE; determine whether the second MNO SIM is related to a sameMNO as the MNO SIM.

17. The apparatus of claim 16, wherein, when the second MNO SIM is not related to the same MNO as the MNO SIM, the processing circuitry is further configured to: prevent the UE from downloading a second eSIM associated with the second MNO SIM; disable the eSIM; and configure the UE to operate in a dual SIM mode.

18. The apparatus of claim 17, wherein, when the second MNO SIM is related to the same MNO as the MNO SIM, the processing circuitry is further configured to: generate, for transmission to the entitlement server, a second signUpForSIMService message to the Entitlement server; process, based on signaling received from the entitlement server, a second signUpForSIMService response message comprising an ICCID of a second eSIM of the phantom SIM network associated with the second MNO SIM; generate, for transmission to the SM-DP+, a download ICCID request message comprising the ICCID of the second eSIM; process, based on signaling received from the SM-DP+, the second eSIM of the phantom SIM network; install the second eSIM of the phantom SIM network on the UE; disable the eSIM and the second eSIM; and configure the UE to operate in a dual SIM mode.

19. An apparatus comprising processing circuitry configured to : store a carrier bundle associated with a mobile network operator (MNO) subscriber identity module (SIM) , wherein the carrier bundle comprises an address for a MNO entitlement serverof an MNO network and an entitlement server of a phantom SIM network; determine a trigger condition has occurred, wherein the trigger condition is related to the UE performing operations related to offloading MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network; determine the UE includes an eSIM bound with the MNO SIM; and prevent the UE from downloading a further eSIM associated with the MNO SIM.

20. A phantom SIM network entitlement server configured to: receive a getEntitlement message from a user equipment(UE) ; send, to the UE, a getEntitlement response message indicating the UE may offload mobile network operator (MNO) subscriber identity module (SIM) service to an embedded SIM (eSIM) of the phantom SIM network, wherein the eSIM and the MNO SIM are associated with a same phone number; receive, from the UE, a signUp ForSIMService message comprising a primary Integrated Circuit Card Identification (ICCID) of the MNO SIM, an Embedded Identity Document (EID) and a secondary International Mobile Equipment Identity; send, to a business support system (BSS) of the phantom SIM network, a provisioning message requesting the eSIM be provisioned for the UE; receive, from the BSS, a provisioning response indicating the eSIM has been provisioned for the UE; and send, to the UE, a signUpForSIMService response message comprising an ICCID of the eSIM of the phantom SIM network.

Images