Management of pseudo single SIM mode and phantom CBRS eSIM

Abstract

An apparatus configured to: store an operator combination package associated with a mobile network operator (MNO) subscriber identity module (SIM), the operator combination package including an MNO authorization server address and an authorization server of a phantom SIM network; sending a getEntitlement message to an authorization server, and sending a getEntitlement message to the authorization server; processing a get Entitlement response indicating that a user equipment (UE) is allowed to offload the MNO SIM service to an embedded SIM (eSIM) of the phantom SIM network; sending a signUpForSIMService message including a primary integrated circuit card identifier (ICCID) to an authorization server, and sending the signUpForSIMService message to the authorization server, processing a signUpForSIMService response comprising an ICCID (Integrated Circuit Card Identifier) of an eSIM (Embedded Subscriber Identity Module) of the phantom SIM network; transmitting a download ICCID request message including an ICCID of the eSIM to a subscription manager-data preparation + (SD-DP +); processing an eSIM of the phantom SIM network; and installing an eSIM of the phantom SIM network on the UE.

Description

Priority / Incorporation by reference

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 508,349, filed June 15, 2023, entitled “Pseudo Single SIM Mode and Management of phantom CBRS eSIMs,” the entire contents of which are incorporated herein by reference. Background Technology

[0002] Mobile network operators (MNOs) typically own radio 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 an MNO to utilize the MNO's infrastructure as a "virtual" network. However, some MVNOs have begun deploying their own cellular infrastructure, blurring the lines between MVNOs and MNOs. One particular network configuration that will see increasing use in the future is the n71 cell for macro coverage and the n48 cell for shorter distances, utilizing Citizens Broadband Radio Service (CBRS) spectrum. In some cases, the n71 cell can be operated by an MNO, and the n48 cell can be operated by an MVNO (e.g., a mobile serving operator (MSO)). It may be advantageous for an MSO to offload certain operations (such as data transmission in the uplink or downlink) to the CBRS network instead of using the MNO network. However, there is currently no process for coordinating user equipment (UEs) to operate simultaneously on both types of networks. Summary of the Invention

[0003] Some example implementations relate 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 includes addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; determine that a triggering condition has occurred; generate a getEntitlement message for sending to the authorization server; process a getEntitlement response message based on signaling received from the authorization server, the getEntitlement response message indicating that the User Equipment (UE) is permitted to offload the MNO SIM service to an embedded SIM (eSIM) of the Phantom SIM network, wherein the eSIM and the MNO SIM are associated with the same telephone number; and generate a carrier bundle including the MNO... The system sends a signUpForSIMService message containing the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the SIM to the authorization server; processes a signUpForSIMService response message containing the ICCID of the eSIM of the Phantom SIM network based on signaling received from the authorization server; generates a download ICCID request message containing the ICCID of the eSIM to send to the Phantom SIM network subscription manager-data preparation+ (SM-DP+); processes the eSIM of the Phantom SIM network based on signaling received from SM-DP+; and installs the eSIM of the Phantom SIM network on the UE.

[0004] Other example implementations relate to an apparatus having processing circuitry configured to: store an operator bundle associated with a Mobile Network Operator (MNO) Subscriber Identity Module (SIM), wherein the operator bundle includes addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; determine that a triggering condition has occurred, wherein the triggering condition is related to a UE performing an operation related to offloading MNO SIM services to an embedded SIM (eSIM) for the Phantom SIM network; determine that the UE includes an eSIM bound to the MNO SIM; and prevent the UE from downloading an additional eSIM associated with the MNO SIM.

[0005] Another example implementation relates to a Phantom SIM network authorization server configured to: receive a getEntitlement message from a User Equipment (UE); transmit a getEntitlement response message to the UE instructing the UE to offload the 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 the same telephone number; receive a signUpForSIMService message from the UE including the primary Integrated Circuit Card Identifier (ICCID), Embedded Identity Document (EID), and Secondary International Mobile Equipment Identity of the MNO SIM; transmit a provision message to the Phantom SIM network's Business Support System (BSS) requesting the provision of an eSIM to the UE; receive a provision response from the BSS indicating that an eSIM has been provided to the UE; and transmit a signUpForSIMService response message to the UE including the ICCID of the eSIM of the Phantom SIM network.

[0006] The additional example implementation relates to an apparatus having processing circuitry configured to: perform an operation to transfer a Mobile Network Operator (MNO) Subscriber Identity Module (SIM) from another UE, wherein the other UE includes a first Phantom SIM network embedded SIM (eSIM); store an operator bundle associated with the MNO SIM, wherein the operator bundle includes addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; generate a getEntitlement message for sending to the authorization server; process a getEntitlement response message based on signaling received from the authorization server, the getEntitlement response message indicating that the UE may offload the MNO SIM service to the Phantom SIM network; and generate an MNO... The process involves sending a signUpForSIMService message containing the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the SIM to the authorization server; processing a signUpForSIMService response message containing the ICCID of a second eSIM of the Phantom SIM network, which is different from the first eSIM, based on signaling received from the authorization server; generating a download ICCID request message containing the ICCID of the second eSIM to be sent to the Phantom SIM Network Subscription Manager - Data Preparation+ (SM-DP+); processing the second eSIM of the Phantom SIM network based on signaling received from SM-DP+; and installing the second eSIM of the Phantom SIM network on the UE. Attached Figure Description

[0007] Figure 1 Example network layouts based on various example implementation schemes are shown.

[0008] Figure 2 Example UEs based on various example implementations are shown.

[0009] Figure 3 Example base stations based on various example implementation schemes are shown.

[0010] Figure 4 A simplified arrangement of the UE for the SIM in MNO and MVNO networks is shown according to various example implementation schemes.

[0011] Figure 5 The Phantom eSIM supply process is illustrated according to various example implementation schemes.

[0012] Figure 6 The call flow for pseudo-single SIM mode provisioning is illustrated according to various example implementation schemes.

[0013] Figure 7 A pseudo-single SIM trigger diagram is shown based on various example implementations.

[0014] Figure 8 Network diagrams related to the synchronization mechanism are shown according to various example implementation schemes.

[0015] Figure 9 Methods 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 implementations, are shown.

[0016] Figure 10A Methods for controlling license changes when the UE does not currently have a Phantom eSIM installed, according to various example implementations, are shown.

[0017] Figure 10B Methods for controlling license changes when a UE currently has a Phantom eSIM installed are illustrated according to various example implementations.

[0018] Figure 10C A second method for controlling license changes when a UE currently has a Phantom eSIM installed is shown, according to various example implementations.

[0019] Figure 11 Methods for managing Phantom eSIM when removing MNO SIM are illustrated according to various example implementations.

[0020] Figure 12Methods for managing Phantom eSIMs in conjunction with timers when removing an MNO SIM are illustrated according to various example implementations.

[0021] Figure 13 A network diagram related to the replacement of the main subscription is shown according to various example implementation schemes.

[0022] Figure 14 Methods for managing Phantom eSIM when the primary subscription is replaced are shown according to various example implementations.

[0023] Figure 15 Methods for switching between pseudo-single SIM mode and true dual SIM mode according to various example implementations are shown.

[0024] Figure 16 A first method for managing the maximum number of subscriptions on a UE is shown, based on various example implementation schemes.

[0025] Figure 17 A second method 1700 for managing the maximum number of subscriptions on a UE is shown according to various example implementations.

[0026] Figure 18 Methods for handling unregulated subscriptions are illustrated according to various example implementations.

[0027] Figure 19 Methods for deleting a Phantom eSIM subscription are shown according to various example implementations.

[0028] Figure 20 Methods for Phantom eSIM subscription transfer are illustrated according to various example implementations.

[0029] Figure 21A A first user interface diagram based on various example implementations is shown.

[0030] Figure 21B A second user interface diagram based on various example implementations is shown. Detailed Implementation

[0031] The example implementation can be further understood with reference to the following description and related figures, in which similar elements have the same reference numerals. The example implementation involves providing the UE with two SIMs, one for the MNO network and one for the phantom SIM network, where data operations can be offloaded to the phantom SIM network. However, unlike conventional dual-SIM modes, the example implementation uses the phantom SIM in a user-transparent manner to the UE; for example, both SIMs are associated with the same phone number.

[0032] Example embodiments are described with reference to user equipment (UE). However, references to the UE are provided for illustrative purposes only. The example embodiments can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

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

[0034] Throughout the specification, the various messages exchanged between components are described by specific names (e.g., getEntitlement message, getEntitlement response message, signupforSIMService, etc.). It should be understood that these message names are merely examples, and the messages exchanged between various components may have different names or no names at all.

[0035] As mentioned above, MNOs and MVNOs differ in several key areas. MNOs typically own radio spectrum and deploy their own radio networks over large geographic areas, while MVNOs are usually localized and contracted with an MNO to utilize the MNO's infrastructure as a "virtual" network. Some MVNOs have begun deploying their own cellular infrastructure, blurring the lines between MVNOs and MNOs. One specific network arrangement that will see increasing use in the future is the n71 cell for macro coverage and the n48 cell for shorter distances, utilizing Citizens Broadband Radio Service (CBRS) spectrum. In some cases, n71 cells can be operated by an MNO, and n48 cells can be operated by an MVNO (e.g., a Mobile Service Operator (MSO)).

[0036] CBRS refers to 150MHz of spectrum (from 3.55GHz to 3.7GHz) in the 3.5GHz band (“Band 48”) and can be used to deploy small but centrally located cellular networks. CBRS access can be based on a multi-tiered access and licensing framework configured to adapt to the band for shared federal and non-federal use.

[0037] An MSO can provide CBRS service to a UE that has subscribed to a pseudo-single SIM plan (e.g., a Phantom SIM network). If an MNO subscriber with a pseudo-single SIM subscription enters a designated geographic area, pseudo-single SIM operation can commence via, for example, a Phantom eSIM on a Phantom SIM network. As will be described in more detail below, the use of a Phantom eSIM provides the UE with two SIMs: one connected to the legacy macro network and one connected to the CBRS network. However, unlike conventional dual-SIM operation, the example implementation presents both SIMs operating in pseudo-single SIM mode, for example, as a single phone number. In pseudo-single SIM mode, the addition and use of the Phantom eSIM is transparent to the user; for example, the user does not select the phone number to use despite using multiple SIMs. This will be explained in more detail below. While the example implementation is described with reference to an MSO providing a Phantom SIM network, any entity can own / operate / manage a Phantom SIM network.

[0038] Figure 1 An example network arrangement 100 according to various example implementations is shown. The example network arrangement 100 includes a UE 110. The UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. A real network arrangement may include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with one UE 110 is provided.

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

[0040] 5G NR RAN 120 can be part of a cellular network that can be deployed by a network operator (e.g., Verizon, AT&T, T-Mobile, etc.). RAN 120 can include cells or base stations configured to transmit and receive services from UEs equipped with appropriate cellular chipsets. In this example, 5G NR RAN 120 includes gNB 120A. However, the reference to gNB is provided merely for illustrative purposes, and any appropriate base station or cell can be deployed (e.g., Node B, eNodeB, HeNB, eNB, gNB, gNodeB, macro cell, micro cell, small cell, femtocell, etc.).

[0041] Any association procedure can be performed to connect UE 110 to 5G NR RAN 120. For example, as described above, 5G NR RAN 120 can be associated with a specific network operator where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR RAN 120, UE 110 can send the corresponding credential information to associate with 5G NR RAN 120. More specifically, UE 110 can be associated with a specific cell (e.g., gNB 120A).

[0042] Network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 manages 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 the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a collection of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 in communicating with various networks.

[0043] Figure 2 Example UE 110 according to various example implementations is shown. (Refer to...) Figure 1The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory layout 210, display device 215, input / output (I / O) device 220, transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing a limited power source, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, sensors for detecting the status of UE 110, etc. eUICC 240 may be a hardware component embedded in UE 110, configured to store multiple carrier profiles.

[0044] Processor 205 can be configured to execute multiple engines of UE 110. For example, the engines may include Phantom eSIM engine 235 for performing operations related to improved UE processing of Phantom eSIM. Phantom eSIM engine 235 can also control the Local Profile Assistant (LPA) function of UE 110, which allows UE 110 to download encrypted profiles to eUICC 240 of UE 110.

[0045] The engines referenced above, as applications (e.g., programs) executed by processor 205, are merely examples. The functionality associated with these engines can also be represented as separate, combined components of UE 110, or as modular components coupled to UE 110, such as integrated circuits with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine can also be embodied as one or more separate applications. Furthermore, in some UEs, the functionality described for processor 205 is split between two or more processors, such as a baseband processor and an application processor. Example implementations can be implemented according to any of these or other configurations of the UE.

[0046] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling a user to input data. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish a connection with 5G-NR RAN 120. Therefore, transceiver 225 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information implementing any of the methods described herein. Processor 205 may be operatively coupled to transceiver 225 and configured to receive signals from and / or transmit signals to transceiver 225. The processor 205 can be configured to encode and / or decode signals (e.g., signaling from a base station in a network) for use in implementing any of the methods described herein.

[0047] Figure 3 An example base station 300 is shown according to various example implementations. Base station 300 may represent any other access node that the gNB 120A or UE 110 can use to establish connections and manage network operations.

[0048] Base station 300 may include processor 305, memory arrangement 310, input / output (I / O) devices 315, transceiver 320, and other components 325. These other components 325 may include, for example, audio input devices, audio output devices, batteries, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices and / or power sources, etc.

[0049] Memory 310 may be a hardware component configured to store data related to operations performed by base station 300. I / O device 315 may be a hardware component or port enabling a user to interact with base station 300. Transceiver 320 may be a hardware component configured to exchange data with UE 110 and any other UE in network arrangement 100. Transceiver 320 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Therefore, transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs. Transceiver 320 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information implementing any of the methods described herein. Processor 305 may be operatively coupled to transceiver 320 and configured to receive signals from and / or transmit signals to transceiver 320. The processor 305 can be configured to encode and / or decode signals (e.g., signaling from the UE) for use in implementing any of the methods described herein.

[0050] Figure 4 A simplified arrangement 400 of a UE 110 for implementing SIMs for MNO and MVNO networks according to various example implementations is shown. The UE 110 may have an MVNO SIM 410 that authorizes UE 110 to register access to CBRS n48 network 402 via MVNO protocol stack 412. Similarly, the UE 110 may also have an MNO SIM 414 that authorizes UE 110 to register access to macro network 404 (e.g., n71) via MNO protocol stack 416 418.

[0051] UE 110 has two SIMs (e.g., a dual-SIM UE), one SIM for connecting to the legacy macro network 404 (e.g., MNO SIM 414), and the other SIM for connecting to the CBRS N48 network 402 (e.g., MVNO SIM 410). Unlike conventional dual-SIM operation, the example implementation presents these two SIMs as operating in pseudo-single-SIM mode, e.g., both SIMs operate using the same phone number. The MVNO eSIM is described as a "phantom" SIM because the user is typically unaware or unable to see that it is being used at any given time. This will be explained in more detail below.

[0052] Network deployment 400 can be hierarchical. For example, CBRS n48 network 402 may take precedence over macro network 404 in a designated geographic area (e.g., a city center / dense area) or a high network traffic area. The decision to switch to using the MVNO protocol stack 412 can be based on any criteria, such as geofencing, UE 110's assessment of the signal strength of both network 402 and network 404, etc. These deployments and logic will be explained in more detail below.

[0053] In some examples, a UE 110 operating on an MNO can request a CBRS SIM, such as a phantom eSIM. The UE 110 can also download geofences to know when the phantom eSIM is activated. The phantom eSIM is typically hidden from the user. Example implementations involve seamless transitions between MNO and MVNO network deployments using both MNO and MVNO SIMs. A simplified scenario of the example implementation is a user approaching and switching to an n48 cell owned by an MVNO (which actually uses a macro network / MNO network in the background). The n48 cell and associated eSIM can also be referred to as a phantom SIM network compared to the MNO. In this scenario, the user has already seamlessly transitioned between a virtual network (hosted by the MNO) and a "real" network deployed by the MVNO.

[0054] Figure 5 The Phantom eSIM provisioning process 500 according to various example implementations is illustrated. It should be noted that... Figure 5 The circled numbers are not reference numerals, but are intended to aid those skilled in the art in visualizing the figures. Figure 5 The flow between various components is illustrated in the example. Furthermore, Figure 5 The supply chain process 500 is an advanced process and is not shown in [the provided text]. Figure 5 This illustrates all the messages exchanged between the various components. As mentioned above, some MVNOs are deploying their own network hardware; such MVNOs require logic to switch UEs between the network where the MNO operates and its CBRS network via Phantom eSIM. UEs requesting this "enhanced" coverage require Phantom eSIM to connect to the CBRS n48 network.

[0055] UE 110 may initially be operating using services on MNO 550. For clarity, UE 110 may have MVNO cellular service, but the network actually accessed by UE 110 is deployed by the MNO, as shown by the entities included in the MNO 550 box (e.g., operated by MNOs such as Verizon, AT&T, etc.). Therefore, UE 110 may have an MNO SIM that can be used to access the MNO network. The MNO SIM can be an actual SIM or an eSIM. This MNO SIM may have an MNO operator package that includes various information for accessing the MNO 550. Furthermore, as described below, the MNO operator package may also include information to allow UE 110 to request a phantom eSIM for MVNO 552. Figure 5 In the example, an MNO SIM will be considered that includes an MNO operator bundle, which includes various information as described below, such as supplying the MNO operator bundle to the MNO SIM. Figure 5 This occurs before the operation.

[0056] In 522, UE 110 connects to 5G NR RAN 120. This could occur during the initial network connection process. At any point when connecting to 5G NR RAN 120, UE 110 may request a Phantom eSIM. As described above, UE 110's MNO SIM may include an MNO operator bundle. The MNO operator bundle may include the authorizing server address (e.g., a Uniform Resource Locator (URL)) for the authorizing server (e.g., ES1 504) for MNO 550 and the authorizing server address for the authorizing server (e.g., ES2 510) for MVNO 552. For example, the MNO operator bundle includes two authorizing server URLs for both services in one bundle. Therefore, in 524, the 5G NR RAN sends a request for a Phantom eSIM to packet core 502.

[0057] Before UE 110 receives the Phantom eSIM, an authentication process can be used to verify that UE 110 is authorized to receive the Phantom eSIM. UE 110 may have already been authenticated at a previous time (e.g., UE 110 has a valid authentication token for requesting the Phantom eSIM, and therefore does not need to perform an authentication process). However, in Figure 5In the example, the authentication process will be considered. In 526, the packet core 502 sends the Phantom eSIM request to the MNO authorization server ES1 504, for example, the URL of ES1 504 in the operator bundle for UE 110. In 528, ES1 504 sends the request to the Authentication, Authorization, and Accounting (AAA) 506 function for authentication. AAA 506 may be a core network function that controls access to computer resources, enforces policies, and audits usage within the MNO 550 network. In 530, AAA 506 connects to the Home Location Register (HLR) 508, which contains information about each subscriber authorized to use the MNO network 550. In 532, ES2 510 requests authorization from AAA 506 to perform operations related to providing the Phantom eSIM to UE 110. It should be noted that the ES2 510 is authenticating to macro (MNO 550) AAA 506, for example, the Extensible Authentication Protocol Method (EAP-AKA) used for authentication and key negotiation. The UE's request for Phantom eSIM will trigger the authentication process between the ES2 510 and AAA 506.

[0058] In this example, the authentication operation is considered successful, and therefore, at the end of 532, UE 110 is authorized to make a request for the Phantom SIM (e.g., UE 110 and any other components that need authentication have received a valid authentication token to continue the operation related to the Phantom SIM request).

[0059] In step 534, packet core 502 (e.g., using the ES2 510 URL included in the MNO operator bundle) transmits a phantom SIM request to ES2 510. ES2 510 is part of the MVNO 552 network. In step 536, ES2 510 forwards the request to the Business Support System (BSS) 512. BSS 512 can be considered a network function related to operations such as product management, order management, customer service provisioning, revenue management, and customer management.

[0060] In 538, BSS 512 queries Subscription Manager Data Preparation + 518 (SM-DP+), which is a network element (e.g., a server) that prepares, stores, and protects operator profiles (including operator credentials). SM-DP+ 518 can also download and install profiles to the UE eUICC (e.g., eUICC 240).

[0061] In step 540, SM-DP+ 518 queries lookup server 520, which responds in step 542 with the credentials of UE 110. In step 544, SM-DP+ assigns an Integrated Circuit Card Identifier (ICCID) to the Phantom eSIM and sends the UE 110 credentials and ICCID to BSS 512.

[0062] In step 546, LS 520 sends an event notification to UE 110. UE 110 can use the ES11 interface (not shown) to monitor pending events. In step 548, UE 110 downloads the CBRS ICCID (e.g., Phantom eSIM) from SM-DP+ 518, as instructed by lookup server 520. UE 110 is now configured with both MNO SIM and Phantom eSIM.

[0063] exist Figure 5 In the example provisioning process 500, various components are described as participating in the process, such as AAA, HLR, BSS, SM-DP+, etc. These names are typically associated with 5G networks. The example provisioning process 500 is not limited to 5G networks. Therefore, when the provisioning process is executed on a non-5G network, the components may have different names. Furthermore, other components on the 5G network may perform some or all of the operations described for the example provisioning process 500.

[0064] Figure 6 A call flow 600 for pseudo-single SIM mode provisioning is illustrated according to various example implementations. Call flow 600 may be a registration call flow (e.g., a flow used by the UE to access the Phantom eSIM). Figure 6 The call process 600 includes the above-mentioned... Figure 5 The example supply process 500 describes some of the operations in the operation.

[0065] Figure 6 The Phantom SIM network licensing server 604, which supports over-the-air configuration of UE eSIM, is shown. Figure 6 The Phantom SIM network BSS 606 is shown, as described above, which is the network function for managing users, billing, and services. Figure 6 Also shown is the Phantom SIM network SM-DP+ 608, which, as described above, is a network element (e.g., a server) for preparing, storing, and protecting operator profiles (including operator credentials). The SM-DP+ 608 can also download and install profiles to the UEeUICC (e.g., eUICC 240). Figure 6 Also shown is the Finder Server (LS) 610. The LS 610 enables the UE 110 to discover the associated Phantom eSIM profile.

[0066] In 612, UE 110 has an inserted / activated MNO ICCID (e.g., MNO SIM). This could be the initial state during UE 110 startup. In 614, UE 110, for example, uses the URL included in the MNO operator bundle of the MNO SIM in the authorization server 604 to send a getEntitlement message with service="Offloadsimservice" to the authorization server 604. Throughout this specification, any message including the term "getEntitlement" can be considered to be related to whether UE 110 is entitled to offload data services 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 step 616, the authorization server 604 responds to UE 110 with a getEntitlement message with an authorization status of 6100, for example, indicating that the UE is entitled to download the Phantom SIM. Therefore, at step 618, UE 110 knows that the user (e.g., a subscriber) is entitled to CBRS access.

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

[0069] In step 622, the authorization server 604 sends a supply CBRS ICCID message to BSS 606. In step 624, BSS 606 sends a download / confirmation order message to SM-DP+ 608. In step 626, SM-DP+ 608 sends a registration event message to LS 610.

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

[0071] In message 634, the authorization server 604 sends a signUpForService response message to UE 110 with an authorization status of 6000, indicating that UE 110 can download the Phantom eSIM. Message 634 also includes the ICCID for the Phantom eSIM and an indication that UE 110 can contact SM-DP+ 608 to obtain the use-ds flag for the Phantom eSIM.

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

[0073] As described above, MNO SIM includes an MNO operator bundle. Similarly, Phantom eSIM may include a Phantom SIM network bundle. The Phantom SIM network bundle may include the URL of the Phantom SIM network's authorization server (e.g., ES2 510). Once Phantom eSIM is downloaded and installed, UE 110 can use the Phantom SIM network bundle to contact the Phantom SIM network's authorization server to retrieve geofences for use with the Phantom SIM network. The retrieval and use of geofences are described in more detail below.

[0074] Figure 7 A pseudo-single SIM trigger diagram 700 is shown according to various example implementation schemes. Figure 7 Three different triggers are presented, which can be used individually or in combination by the UE to determine when to execute call procedure 600, for example, when to trigger the UE to download and install Phantom eSIM.

[0075] The first trigger can occur after UE reboot 704. In 706, if a current Phantom eSIM is installed on UE 110, UE 110 can notify the authorization server (e.g., ES2 510, ES1 504, etc.) of the current Phantom eSIM. If UE 110 includes a previously installed Phantom eSIM, UE 110 may not need to download a new Phantom eSIM. In some example implementations, the network (e.g., MNO 550, Phantom SIM network 552) can also track subscriptions associated with the MNO / IMEI. This prevents UE 110 from downloading a new Phantom eSIM when UE 110 already has a Phantom eSIM available.

[0076] The second trigger could be the MNO SIM reinsertion / MNO SIM installation shown in 708. In 708, the user can remove the SIM card associated with the MNO from UE 110. In 710, UE 110 can wait a predetermined amount of time (e.g., by using a protection timer) to delete the associated phantom SIM. For example, the user can temporarily remove the MNO SIM and then reinsert the MNO SIM while the protection timer continues to run. In this case, UE 110 will not have to download a new phantom eSIM because UE 110 has not yet deleted the previously associated phantom eSIM; for example, UE 110 can continue to use the associated phantom eSIM when the MNO SIM is reinserted. On the other hand, if the protection timer expires, UE 110 will delete the associated phantom eSIM, such that if the MNO SIM is reinserted, UE 110 will have to download a new phantom eSIM (e.g., by using a protection timer). Figure 6 (Call flow). In another scenario, if the user removes the MNO SIM and replaces it with a different MNO SIM, UE 110 will again have to (e.g., using...) Figure 6 (The call process) downloads a new Phantom eSIM associated with the different MNO SIM. A protection timer can be set at any appropriate time to prevent the Phantom eSIM from being deleted based on the temporary removal of the MNO SIM.

[0077] A third trigger can be used when the authorization server is not working. For example, in 712, during the initial registration process, UE 110 may attempt to acquire the Phantom eSIM a predetermined number of times (e.g., five times). If the registration process is unsuccessful (including retries), UE 110 will not download the Phantom eSIM. As mentioned above, some example triggers are rebooting or when the user removes / reinstalls / replaces the MNO SIM. However, these actions are not typically performed frequently by the user; for example, users rarely completely reboot the UE. Instead, a more common action taken when encountering network problems is to switch to airplane mode to allow UE 110 to re-establish a cellular connection.

[0078] Therefore, in 714, the user can switch the airplane mode feature of UE 110. In response to the switch, in 716, UE 110 can check if a Phantom SIM network is bound to the MNO. If no Phantom SIM network is bound to the MNO, UE 110 can retry downloading the Phantom eSIM in response to the airplane mode switch (up to a predetermined attempt limit). In this sense, airplane mode switch 714 serves as a trigger for retrying the Phantom SIM network.

[0079] The above provides an example of when the UE can be triggered to download and install the Phantom eSIM. Below are examples of different aspects of managing the Phantom eSIM.

[0080] Figure 8 Network diagram 800 is shown, relating to the synchronization mechanism according to various example implementations. Network diagram 800 is a simplified depiction of the synchronization mechanism used for the Phantom CBRS eSIM. Network diagram 800 shows an MNO 802 that can be considered the “primary” network service provider for UE 110. MNO 802 can identify UE 110 via an MNO SIM (not shown). UE 110 may also have an associated Phantom eSIM (not shown) used to verify UE 110’s identity with the authorization server 804.

[0081] UE 110 may have logic components to prevent unnecessary Phantom eSIM installation. For example, as described above, a reboot of UE 110 can trigger registration for the Phantom eSIM service. However, if UE 110 has the same ICCID associated with the MNOSIM of MNO 802 and UE 110 has a currently installed Phantom eSIM, UE 110 may not download the additional Phantom eSIM. This will... Figure 9 A more detailed explanation follows.

[0082] Figure 9 Method 900 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 implementations, is illustrated. The generation of a new ICCID incurs charges for the Phantom SIM network, and the registration and download of the Phantom eSIM requires UE processing time. Therefore, it may be desirable to avoid generating and downloading a new Phantom SIM network ICCID.

[0083] In step 902, UE 110 has already bound the MNO ICCID and the Phantom SIM network ICCID (for Phantom eSIM). In step 904, UE 110 restarts in response to a user action or through internal UE logic. As described above, UE restart is triggered for Phantom eSIM registration. However, as described above, it may be advantageous to avoid generating and downloading new Phantom eSIMs when not needed.

[0084] Therefore, in step 906, UE 110 determines whether a Phantom eSIM already installed and bound to the MNO exists. If a Phantom eSIM already installed and bound to the MNO exists, UE 110 proceeds to step 908 and does not install a new Phantom eSIM. For example, UE 110 does not transmit a registration request for a new Phantom eSIM, and the Phantom SIM network does not need to generate a new Phantom SIM network ICCID.

[0085] If no Phantom eSIM is already installed or if there is no Phantom eSIM binding to an MNO, UE 110 proceeds to 910 and (via, for example, call procedure 600) installs a new Phantom eSIM. Those skilled in the art will understand that various scenarios may exist that could cause the UE to lose its Phantom eSIM binding, for example, UE 110 has a Phantom eSIM installed, but the Phantom eSIM is not bound to an MNO. In 912, UE 110 has a new Phantom SIM network and an MNO binding for the newly downloaded Phantom eSIM.

[0086] Some example implementation schemes for managing Phantom eSIM relate to Phantom eSIM authorization change logic. The MNO can select Phantom eSIM enablement for each account based on the user's subscription plan. For example, the MNO can select to upgrade the service level received by a user based on their geographic location, or in some cases, deny a user Phantom SIM network service based on geographic location or any other subscription-related factor. The UE and / or network can be provided with logic components for handling such scenarios. Figure 10A , Figure 10B and Figure 10C These example implementation schemes are described. Figures 10A to 10C The flowchart can be implemented on the UE alone or in combination with network components.

[0087] Figure 10A A method 1000 for controlling license changes when a UE does not currently have a Phantom eSIM installed, according to various example implementations, is shown. Method 1000 is applicable to scenarios where there is no Phantom eSIM on the UE 110.

[0088] Initially, in 1004, Phantom eSIM was not installed on UE 110. In 1006, UE 110 sent a signupforSIMService message (e.g., Figure 6 Operation 616 in the middle) is sent to the authorization server (e.g., authorization server 604).

[0089] In case 1008, the authorization server sends the authorization back. Figure 10A In the example, the authorization is negative (e.g., action state: state_not allowed_action). In 1010, UE 110 does not install Phantom eSIM. However, if the authorization state changes in the future (e.g., UE 110 moves to a different geographic area), UE 110 can try to install Phantom eSIM again; for example, UE 110 can send an additional signupforSIMService message at a later time to attempt to install Phantom eSIM.

[0090] Figure 10B A method 1001 for controlling license changes when a UE currently has a Phantom eSIM installed is illustrated according to various example implementations. Method 1001 is applicable to scenarios where a UE 110 has a Phantom eSIM installed.

[0091] In step 1012, UE 110 has already bound the MNO ICCID and the Phantom SIM network ICCID. In step 1014, the user can restart UE 110, or UE 110 can be restarted due to internal logic (e.g., for a software update process). As described above, restarting UE 110 can be triggered by UE 110 registering for the Phantom eSIM service.

[0092] In 1016, UE 110 will send the signupforSIMService message (e.g., Figure 6 Operation 616 in step 1017 is sent to the authorization server (e.g., authorization server 604). In step 1017, the authorization server sends back authorization. Figure 10B In the example, the authorization is negative (e.g., action state: state_not allowed_action).

[0093] In version 1018, the authorization server can specify the Phantom eSIM status on the UE. Authorization and the Phantom eSIM status on the UE can be sent in the same message or different messages. This status can be deleted or disabled. For example, this might happen if a user changes their cellular plan so that they no longer subscribe to Phantom SIM connectivity. Two example eSIM statuses could be Status_Not Allowed_Action, Deleted and Status_Not Allowed_Action, Disabled.

[0094] In step 1020, UE 110 determines the status received in step 1018. If the status is "deleted," UE 110 proceeds to step 1022 and deletes the Phantom eSIM. If the status received in step 1018 is "disabled," UE 110 proceeds to step 1024 and disables the Phantom eSIM.

[0095] Figure 10C A second method 1002 for controlling license changes when a UE currently has a Phantom eSIM installed, according to various example implementations, is shown. Method 1002 is applicable to situations where the license status changes.

[0096] In step 1026, UE 110 has already bound its MNO ICCID and Phantom SIM network ICCID. In step 1028, the authorization server can change the authorization status to, for example, state _disabled_authorized. For example, the authorization server can determine that there is no geofence in UE 110's geographic location, and therefore Phantom eSIM should not be used; for example, Phantom eSIM should be disabled. Therefore, in step 1030, UE 110 can disable Phantom eSIM. Phantom eSIM can remain in a disabled state until a positive authorization is received from the authorization server.

[0097] Some example implementations for managing Phantom eSIM involve 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 become inactive.

[0098] In the remainder of this disclosure, references to removing a SIM card may refer to removing a physical SIM card or to disabling eSIM. Such distinctions will be indicated appropriately when relevant to a particular implementation. Similarly, references to “reinserting” a SIM may refer to a user physically reinserting the SIM card or to enabling eSIM. Such distinctions will be indicated appropriately when relevant.

[0099] Figure 11 A method 1100 for managing a Phantom eSIM when removing an MNO SIM is illustrated according to various example implementations.

[0100] In step 1102, UE 110 has already bound the MNO ICCID (e.g., MNO SIM or eSIM) and the Phantom SIM network ICCID (e.g., Phantom eSIM). In step 1104, the user can remove the MNO SIM card. In step 1106, UE 110 can delete the Phantom eSIM. In step 1108, the MNO SIM is reinserted. In step 1110, UE 110 can perform the Phantom SIM network registration process (e.g., call procedure 600).

[0101] In some cases, it may be desirable not to immediately delete the Phantom eSIM upon MNO SIM removal. For example, there may be security issues related to malicious actors attacking SMDP+, ICCID database depletion due to overuse, physical SIM contact issues (e.g., contacts may become loose over time, which could manifest as SIM removal (false alarm)), additional signaling delays, etc. Therefore, some example implementations for managing Phantom eSIMs associated with MNO SIM removal incorporate additional checks to address various issues before deleting or disabling the Phantom eSIM.

[0102] Figure 12 A method 1200 for managing a phantom eSIM in conjunction with a timer when removing an MNO SIM is illustrated, according to various example implementations.

[0103] In step 1202, UE 110 has bound the MNO ICCID (e.g., MNO SIM or eSIM) and the Phantom SIM network ICCID (e.g., Phantom eSIM). In step 1204, the user can remove the MNO SIM card. In step 1206, UE 110 can disable the Phantom eSIM. In step 1208, UE 110 starts a timer. The timer can be a predetermined duration (e.g., 30 minutes). This duration can be left to the specific implementation of the MNO / Phantom SIM network / OEM. In step 1210, the MNO SIM is reinserted into UE 110. In step 1212, UE 110 determines if the timer has expired. If the timer has expired, in step 1214, UE 110 removes the bound Phantom eSIM. If the timer has not expired, UE 110 proceeds to step 1216 and re-enables the previously disabled Phantom eSIM.

[0104] In some example implementations, instead of deleting the phantom eSIM at 1214, UE 110 may retain the phantom eSIM on UE 110 until a configurable maximum count is reached. For example, UE 110 may have multiple phantom eSIMs stored on UE 110, but only 0 or 1 phantom eSIMs may be enabled at any given time. UE 110 may retain disabled phantom eSIMs on UE 110 until the UE reaches the configured maximum number of phantom eSIMs (e.g., three), at which point the disabled phantom eSIM may be re-enabled or deleted later. For example, UE 110 may be configured to have a first-in-first-out (FIFO) buffer, allowing a user who re-inserts an MNO SIM to reuse the associated phantom eSIM until the number of SIMs inserted into the UE reaches the maximum count. For example, a UE with three buffers may store phantom eSIMs associated with three MNO SIMs. When a fourth MNO SIM is inserted, the phantom eSIM associated with the first inserted (first in chronological order) MNO SIM may be deleted. For example, if the MNO1 SIM is inserted on Monday, the MNO2 SIM on Tuesday, and the MNO3 SIM on Wednesday, then inserting the MNO4 SIM will cause the UE to remove the phantom eSIM associated with the MNO1 SIM.

[0105] In other example implementations, the UE can delete the least recently used phantom eSIM. For example, if the phantom eSIM associated with MNO2SIM was last used on Monday, the phantom eSIM associated with MNO1SIM was last used on Tuesday, and the phantom eSIM associated with MNO3SIM was last used on Wednesday, then the insertion of MNO4SIM will cause the UE to delete the phantom eSIM associated with MNO2SIM.

[0106] Some example implementations for managing Phantom eSIMs involve replacing the primary subscription. For example, a user can install MNO SIM2, which can disable MNO SIM1. Disabling MNO SIM1 also disables the bundled Phantom eSIM1.

[0107] Figure 13 Network diagram 1300 is shown in relation to a replacement of the primary subscription according to various example implementations. Network diagram 1300 shows UE 110, MNO 1302, Authorization Server 1304, and SM-DP+ 1306. MNO network diagram 1300 shows an initial state where MNO SIM1 and Phantom eSIM1 are active. MNO network diagram 1300 then shows a subsequent state where MNO SIM2 and Phantom eSIM2 are active, and MNO SIM1 and Phantom eSIM1 are inactive. This subsequent state can be a result of the user inserting MNO SIM2 into UE 110. This allows UE 110 to disable MNO SIM1 and the associated Phantom eSIM1. Furthermore, this also allows UE 110 to perform a Phantom SIM network registration procedure with Authorization Server 1304 (e.g., call procedure 600) to obtain Phantom eSIM2 associated with MNO SIM2 from SM-DP+ 1306. In this example, the operation is considered successful and both MNO SIM2 and Phantom eSIM2 are considered active. Figure 13 In the example, it is assumed that the MNOs of MNO SIM1 and MNO SIM2 are the same MNO. However, this is not necessarily the case. The following will refer to... Figure 14 Provides further description of the replacement of the primary subscription.

[0108] Figure 14 Method 1400 for managing Phantom eSIM when the primary subscription is replaced, according to various example implementations, is shown.

[0109] In step 1402, UE 110 has already bound the MNO ICCID (e.g., MNO SIM1) and the Phantom SIM network ICCID (e.g., Phantom eSIM1). In step 1403, the user can remove MNO SIM1. In step 1404, the user can install MNO SIM2. In step 1406, UE 110 determines whether there is an associated binding between an installed MNO (e.g., MNO SIM2) and the Phantom SIM network. If an associated binding exists, UE 110 proceeds to step 1408 and does not install a new Phantom eSIM; for example, UE 110 includes a previously downloaded and installed Phantom eSIM associated with MNO SIM2. If no associated binding exists, UE 110 proceeds to step 1410, and (e.g., using...) Figure 6 (Registration process) Download and install the new Phantom eSIM2. In 1412, UE 110 binds MNO2 and Phantom eSIM2. In 1414, disable (but do not remove) Phantom eSIM1.

[0110] Some example implementations for managing Phantom eSIM involve mode switching between pseudo-single SIM mode and true dual SIM mode. For example, in some scenarios, a user can install MNO SIM2 onto a UE that operates using MNO SIM1 and Phantom eSIM. In some cases, it may be desirable to switch from pseudo-single SIM mode to true dual SIM operation.

[0111] Figure 15 A method 1500 for switching between pseudo-single SIM mode and true dual SIM mode is shown according to various example implementations.

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

[0113] If in 1508 MNO SIM2 comes from the same MNO as SIM1, then UE 110 proceeds to 1516 and (for example, using...) Figure 6(Registration process) Install Phantom eSIM2. In step 1518, UE 110 binds MNO2 to Phantom eSIM2. In step 1520, Phantom eSIM1 and Phantom eSIM2 are disabled. In step 1522, UE 110 enters Dual SIM Dual Standby mode (DSDS). If the user later disables MNO SIM1, UE 110 proceeds to step 1524, and MNO SIM2 and Phantom eSIM2 can become active. If the user disables MNO SIM2, MNO SIM1 and Phantom eSIM1 can become active.

[0114] Some example implementations for managing Phantom eSIM involve maximum subscription management. For example, these example implementations may address scenarios where subsequent (e.g., third) MNO SIM installations may exceed the maximum number of MNOs supported on the UE. In these examples, the maximum number of subscriptions may be based on UE capabilities and / or operator preferences.

[0115] Figure 16 A first method 1600 for managing the maximum number of subscriptions on a UE is shown according to various example implementations.

[0116] In step 1602, UE 110 has already bound the MNO ICCID (e.g., MNO SIM1) and the Phantom SIM network ICCID (e.g., Phantom eSIM1). In step 1604, MNO SIM1 remains enabled. In step 1606, the user installs MNO SIM2, which supports uninstallation (e.g., Phantom eSIM2 operation). In step 1608, UE 110 binds MNO2 to Phantom eSIM2. In step 1610, Phantom eSIM1 and Phantom eSIM2 are disabled.

[0117] In step 1612, the user can install an additional MNO SIM (e.g., MNO SIM3). In step 1614, UE 110 determines whether the maximum MNO count has been reached. If the maximum MNO count has not been reached, UE 110 can proceed to step 1617 and attempt the registration process with the authorizing server to download and install the Phantom eSIM3 associated with MNO SIM3. If the maximum MNO count has been reached, UE 110 proceeds to step 1616 and stops further registration with the authorizing server. If, at a later time, one of the MNOs currently stored on UE 110 is deleted, such as MNO SIM1 or MNO SIM2, then in step 1618, UE 110 can send a Phantom SIM network registration message to the authorizing server to attempt to download and install the Phantom eSIM3 associated with MNO SIM3.

[0118] Figure 17A second method 1700 for managing the maximum number of subscriptions on a UE is shown according to various example implementations.

[0119] In step 1702, UE 110 has already bound the MNO ICCID (e.g., MNO SIM1) and the Phantom SIM network ICCID (e.g., Phantom eSIM1). In step 1704, MNO SIM1 remains enabled. In step 1706, the user installs MNO SIM2, which supports uninstallation (e.g., Phantom eSIM2 operation). In step 1708, UE 110 binds MNO2 to Phantom eSIM2. In step 1710, Phantom eSIM1 and Phantom eSIM2 are disabled.

[0120] In step 1712, the user can install an additional MNO SIM (e.g., MNO SIM3). In step 1714, UE 110 determines whether the maximum MNO count has been reached. If the maximum MNO count has not been reached, UE 110 proceeds to step 1717 and attempts the registration process with the authorization server to download and install the Phantom eSIM3 associated with MNO SIM3. If the maximum MNO count has been reached, UE 110 proceeds to step 1716 and deletes Phantom eSIM1 (e.g., following FIFO logic). In step 1718, UE 110 installs Phantom eSIM3. In step 1720, Phantom eSIM2 is disabled, and Phantom eSIM3 is also disabled.

[0121] Some example implementations for managing Phantom eSIMs involve unregulated subscriptions. For example, in some scenarios, a Phantom SIM network might inadvertently provide two Phantom eSIMs for the same MNO. These example implementations not only ignore the second (e.g., the wrong) Phantom eSIM, but also notify the network that the additional ICCID is in a released state.

[0122] Figure 18 A method 1800 for handling unregulated subscriptions according to various example implementations is illustrated. In 1802, UE 110 may have an MNO ICCID associated with an MNO SIM. In 1804, UE 110 performs registration for the Phantom eSIM service with an authorization server. In 1806, SM-DP+ provides UE 110 with more than one Phantom eSIM. In 1808, UE 110 installs Phantom eSIM1 and binds it to MNO SIM1. In 1810, UE 110 determines that the received Phantom eSIM2 is for the same Mobile Directory Number (MDN) as Phantom eSIM1. In 1812, UE 110 deletes Phantom eSIM2. In 1814, UE 110 sends a message to SM-DP+ deleting Phantom eSIM2.

[0123] Some example implementations for managing Phantom eSIM involve deleting the Phantom eSIM subscription. As described above, the Phantom eSIM is not presented to the user during typical operational procedures; for example, the Phantom eSIM is transparent to the user. These example implementations involve deleting the Phantom eSIM during a typical UE Erase All Content and Settings (EACS) operation.

[0124] Figure 19 A method 1900 for deleting a Phantom eSIM subscription is illustrated according to various example implementations. In 1902, UE 110 has already bound an MNO ICCID (e.g., MNO SIM) and a Phantom SIM network ICCID (e.g., Phantom eSIM). In 1904, the user may perform an EACS procedure, for example, before recycling or selling their UE 110. In 1906, UE 110 deletes all SIM cards, including the Phantom eSIM. In 1908, UE 110 completes the EACS procedure and deletes all Phantom SIM networks and MNOSIMs. The user has successfully cleared their Phantom eSIM without requiring specific instructions that it should be deleted. In other example implementations, the user may select an option to “reset” the MNO. In this scenario, UE 110 may delete the associated Phantom eSIM only during 1906.

[0125] Some example implementations for managing Phantom eSIMs involve Phantom eSIM subscription transfers. In some cases, it may be desirable to retain the Phantom eSIM on the UE after an MNO SIM transfer. For example, a user might transfer their SIM from a personal UE to a working UE for a limited period and then transfer the MNO SIM back to the personal UE. In this scenario, it may be desirable to keep the associated Phantom eSIM on the personal UE so that, from the user's perspective, the re-association with the MNO SIM is seamless and nearly instantaneous.

[0126] Figure 20Methods 2000 for transferring a Phantom eSIM subscription are illustrated according to various example implementations. In 2002, a first UE has already bound an MNO ICCID (e.g., an MNO SIM) and a Phantom SIM network ICCID (e.g., a Phantom eSIM). In 2004, a user can initiate an MNO SIM transfer (whether physical or eSIM) from the first UE to a second UE. In 2006, the second UE has an MNO SIM but does not have a Phantom eSIM1 still on the first UE. In 2008, the second UE performs Phantom SIM network SIM registration (e.g., call flow 600). In 2010, the second UE binds a Phantom eSIM2 and an MNO SIM (e.g., the SIM initially installed on the first UE). In 2012, for scenarios where the user reinstalls the MNO SIM on the first UE, Phantom eSIM1 is retained on the first UE.

[0127] These example implementations can be modified by adding a timer function that removes the Phantom eSIM1 from the first UE after a specified time period. This prevents the Phantom eSIM1 from being abandoned because the MNO SIM never returns to the first UE.

[0128] Some example implementations involve user interface (UI) enhancements for pseudo-single SIM operation. The goal of Phantom eSIM is to minimize user management for pseudo-single SIM setup. Ideally, users should be able to seamlessly enhance coverage within the geographic areas supported by Phantom SIM. This can be achieved by, for example... Figure 21B The enhanced UI shown is as follows Figure 21A The example shown is a comparison with an existing UI used for real SIM operation.

[0129] Figure 21A Figure 2100 shows a first user interface according to various example implementation schemes. Figure 21B Figure 2106 shows a second user interface according to various example implementation schemes.

[0130] UI Figure 2100 illustrates a typical UI when true dual SIMs are active on a UE (e.g., UE 110). The first SIM may correspond to MNO 2102, and the second SIM may correspond to MNO 2104. Each of MNO 2102 and MNO 2104 has a network strength indicator (e.g., a bar) and is labeled in the UI by name (e.g., "MNO1 Mobile 5G"). Each SIM in this typical UI is its own independent entity, and the user can immediately see the difference in network strength between the two networks associated with the two SIMs.

[0131] Figure 21BUI diagram 2106 for pseudo-single SIM operation is shown. Unlike UI 2100, UI 2106 does not have separate and distinct entities for each SIM. For example, MNO 2108 could be the primary service provider for UE 110. MNO 2108 can always display its network strength because the MNO SIM is registered with IMS and has associated voice capabilities. UI 2106 also shows “MSO Mobile 5G” as a Radio Access Technology (RAT) indicator 2110. RAT indicator 2110 can be changed to the specific RAT currently being used by UE 110. For example, if UE 110 is outside the range of the Phantom SIM network eSIM area, RAT indicator 2110 could instead show the MNO RAT (similar to...). Figure 21A ).

[0132] Example In a first embodiment, a method includes: storing an operator combo packet associated with a mobile network operator (MNO) subscriber identity module (SIM), wherein the operator combo packet includes addresses of an MNO authorization server for the MNO network and an authorization server for a Phantom SIM network; determining that a triggering condition has occurred; configuring transceiver circuitry to send a getEntitlement message to the authorization server; and decoding a getEntitlement response message based on signaling received from the authorization server, the getEntitlement response message indicating whether the UE can offload MNO SIM service to an embedded SIM (eSIM) of the Phantom SIM network, wherein the eSIM and the MNO SIM are associated with the same telephone number.

[0133] In a second embodiment, according to the method of the first embodiment, wherein the getEntitlement response message instructs the UE to offload the MNO SIM service to the eSIM, the method further includes: configuring transceiver circuitry to send a signUpForSIMService message to the authorization server, wherein the signUpForSIMService message includes the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the MNO SIM; decoding the signUpForSIMService response message including the ICCID of the eSIM of the Phantom SIM network according to signaling received from the authorization server; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the eSIM to the Phantom SIM Network Subscription Manager-Data Preparation+ (SM-DP+); decoding the eSIM of the Phantom SIM network according to signaling received from the SM-DP+; and installing the eSIM of the Phantom SIM network on the UE.

[0134] In the third embodiment, according to the method of the second embodiment, the eSIM for the Phantom SIM network is for the Citizens Broadband Radio Service (CBRS) network.

[0135] In a fourth embodiment, according to the method of the second embodiment, the method further includes: decoding one or more geofences based on signaling received from the authorization server; performing data operations using the eSIM of the Phantom SIM network when within a geographic area of ​​the one or more geofences; and performing data operations using the MNO SIM when not within the geographic area of ​​the one or more geofences.

[0136] In the fifth embodiment, according to the method of the second embodiment, the triggering conditions include the restart of the UE, the insertion of the MNO SIM, or the switching of the UE's flight mode.

[0137] In a sixth embodiment, according to the method of the second embodiment, the method further includes: determining that a second triggering condition has occurred; configuring the transceiver circuit to send a second getEntitlement message to the authorization server; decoding the second getEntitlement response message according to signaling received from the authorization server, wherein the second getEntitlement response message indicates that the UE cannot offload the MNO SIM service to the eSIM of the Phantom SIM network; and decoding the status of the eSIM of the Phantom SIM network according to signaling received from the authorization server.

[0138] In the seventh embodiment, according to the method of the sixth embodiment, wherein the state of the eSIM is disabled, the method further includes disabling the eSIM.

[0139] In the eighth embodiment, according to the method of the sixth embodiment, wherein the state of the eSIM is deleted, the method further includes deleting the eSIM.

[0140] In the ninth embodiment, according to the method of the second embodiment, the method further includes: decoding a message indicating that the UE cannot offload the MNO SIM service to the Phantom SIM network based on signaling received from the authorization server; and disabling the eSIM in response to the message.

[0141] In the tenth embodiment, according to the method of the second embodiment, the method further includes determining that the MNO SIM has been removed from the UE, wherein the MNO SIM is a physical SIM or an eSIM.

[0142] In the eleventh embodiment, according to the method of the tenth embodiment, the method further includes: in response to determining that the MNO SIM has been removed from the UE, deleting the eSIM of the Phantom SIM network.

[0143] In the twelfth embodiment, according to the method of the eleventh embodiment, the method further includes: determining that the MNO SIM has been reinstalled in the UE; in response to the MNO SIM being reinstalled, configuring transceiver circuitry to send a second signUpForSIMService message to the authorization server; decoding the second signUpForSIMService response message according to signaling received from the authorization server, the second signUpForSIMService response message including the ICCID of the second eSIM of the Phantom SIM network associated with the MNO SIM; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the second eSIM to the SM-DP+; decoding the second eSIM of the Phantom SIM network according to signaling received from the SM-DP+; and installing the second eSIM of the Phantom SIM network on the UE.

[0144] In the thirteenth embodiment, according to the method of the tenth embodiment, the method further includes: disabling the eSIM in response to determining that the MNO SIM has been removed from the UE; and starting a timer.

[0145] In the fourteenth embodiment, according to the method of the thirteenth embodiment, the method further includes: determining that the MNO SIM has been reinstalled in the UE; and resetting the timer.

[0146] In the fifteenth embodiment, the method according to the fourteenth embodiment is further comprising re-enabling the eSIM when the timer has not yet expired.

[0147] In the sixteenth embodiment, according to the method of the thirteenth embodiment, the method further includes determining that the timer has expired and deleting the eSIM.

[0148] In the seventeenth embodiment, according to the method of the second embodiment, the method further includes: disabling the MNOSIM; determining that the second MNOSIM is installed on the UE; and determining whether the UE includes a second eSIM bound to the second MNOSIM.

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

[0150] In the nineteenth embodiment, according to the method of the seventeenth embodiment, wherein when the UE does not include the second eSIM bound to the second MNO SIM, the method further includes: configuring transceiver circuitry to send a second signUpForSIMService message to the authorization server; decoding a second signUpForSIMService response message according to signaling received from the authorization server, the second signUpForSIMService response message including the ICCID of the second eSIM of the Phantom SIM network associated with the second MNO SIM; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the second eSIM to the SM-DP+; decoding the second eSIM of the Phantom SIM network according to signaling received from the SM-DP+; installing the second eSIM of the Phantom SIM network on the UE; and disabling the eSIM.

[0151] In a twentieth embodiment, according to the method of the second embodiment, the method further includes: determining that a second MNOSIM is installed on the UE; and determining whether the second MNOSIM is associated with an MNO that is the same as the MNOSIM.

[0152] In the twenty-first embodiment, according to the method of the twenty-first embodiment, wherein when the second MNO SIM is not associated with an MNO that is the same as the MNO SIM, the method further includes: preventing the UE from downloading a second eSIM associated with the second MNO SIM; disabling the eSIM; and configuring the UE to operate in dual-SIM mode.

[0153] In the twenty-second embodiment, according to the method of the twenty-first embodiment, wherein when the second MNO SIM is associated with the same MNO as the MNO SIM, the method further includes: configuring transceiver circuitry to send a second signUpForSIMService message to the authorization server; decoding a second signUpForSIMService response message based on signaling received from the authorization server, the second signUpForSIMService response message including the ICCID of a second eSIM of the Phantom SIM network associated with the second MNO SIM; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the second eSIM to the SM-DP+; decoding the second eSIM of the Phantom SIM network based on signaling received from the SM-DP+; 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 dual-SIM mode.

[0154] In the twenty-third embodiment, according to the method of the twenty-second embodiment, the method further includes disabling the MNO SIM and enabling the second eSIM.

[0155] In the twenty-fourth embodiment, according to the method of the twenty-second embodiment, the method further includes disabling the second MNO SIM and enabling the eSIM.

[0156] In the twenty-fifth embodiment, according to the method of the second embodiment, the method further includes: determining that a second MNO SIM is installed on the UE; configuring transceiver circuitry to send a second signUpForSIMService message to the authorization server; decoding a second signUpForSIMService response message based on signaling received from the authorization server, the second signUpForSIMService response message including the ICCID of a second eSIM of the Phantom SIM network associated with the second MNO SIM; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the second eSIM to the SM-DP+; decoding the second eSIM of the Phantom SIM network based on signaling received from the SM-DP+; installing the second eSIM of the Phantom SIM network on the UE; disabling the eSIM and the second eSIM; determining that a third MNO SIM is installed on the UE; and determining whether the third MNO SIM exceeds the maximum number of MNO subscriptions.

[0157] In the twenty-sixth embodiment, according to the method of the twenty-fifth embodiment, wherein when the third MNO SIM exceeds the maximum number of MNO subscriptions, the method further includes preventing the UE from downloading an eSIM associated with the third MNO SIM.

[0158] In the twenty-seventh embodiment, according to the method of the twenty-fifth embodiment, wherein when the third MNO SIM exceeds the maximum number of MNO subscriptions, the method further includes: deleting the eSIM based on the fact that the eSIM is the first loaded eSIM on the UE; configuring transceiver circuitry to send a third signUpForSIMService message to the authorization server; decoding a third signUpForSIMService response message based on signaling received from the authorization server, the third signUpForSIMService response message including the ICCID of the third eSIM of the Phantom SIM network associated with the third MNO SIM; configuring transceiver circuitry to send a download ICCID request message including the ICCID of the third eSIM to the SM-DP+; decoding the third eSIM of the Phantom SIM network based on signaling received from the SM-DP+; and installing the third eSIM of the Phantom SIM network on the UE.

[0159] In the twenty-eighth embodiment, according to the method of the second embodiment, wherein the decoding of the signaling received from the SM-DP+ includes the UE receiving the eSIM and the second eSIM, the method further includes: deleting the second eSIM; and configuring the transceiver circuitry to send an indication to the SM-DP+ that the second eSIM has been deleted from the UE.

[0160] In the twenty-ninth embodiment, according to the method of the second embodiment, the method further includes receiving input from a user to perform an Erase All Content and Settings (EACS) operation for the UE, and performing the EACS operation includes deleting the eSIM.

[0161] In the thirtieth embodiment, according to the method of the first embodiment, the method further includes determining that the UE does not include an eSIM bound to the MNO SIM.

[0162] In the thirty-first embodiment, according to the method of the first embodiment, wherein the getEntitlement response message indicates that the UE cannot offload the MNO SIM service to the eSIM, the method further includes preventing the UE from downloading the eSIM associated with the MNO SIM.

[0163] In the thirty-second embodiment, a processor is configured to perform the method according to any one of the first to thirty-first embodiments.

[0164] In the thirty-third embodiment, a user equipment includes: a transceiver circuit configured to communicate with a network; and a processor communicatively coupled to the transceiver circuit and configured to perform the method according to any one of the first to thirty-first embodiments.

[0165] In a thirty-fourth embodiment, a method includes: storing an operator bundle associated with a mobile network operator (MNO) subscriber identity module (SIM), wherein the operator bundle includes addresses of an MNO authorization server for the MNO network and an authorization server for a Phantom SIM network; determining that a trigger condition has occurred, wherein the trigger condition is related to the UE performing an operation related to offloading MNO SIM services to an embedded SIM (eSIM) of the Phantom SIM network; determining that the UE includes an eSIM bound to the MNO SIM; and preventing the UE from downloading an additional eSIM associated with the MNO SIM.

[0166] In the thirty-fifth embodiment, a processor is configured to perform the method according to the thirty-fourth embodiment.

[0167] In a thirty-sixth embodiment, a user equipment includes: a transceiver circuit configured to communicate with a network; and a processor communicatively coupled to the transceiver circuit and configured to perform the method according to a thirty-fourth embodiment.

[0168] In a thirty-seventh embodiment, a method includes: receiving a getEntitlement message from a user equipment (UE); transmitting a getEntitlement response message to the UE, the getEntitlement response message instructing the UE to offload a 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 the same telephone number; receiving a signUpForSIMService message from the UE including the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the MNO SIM; transmitting a provision message to the Business Support System (BSS) of the Phantom SIM network requesting provision of the eSIM to the UE; receiving a provision response from the BSS indicating that the eSIM has been provisioned to the UE; and transmitting a signUpForSIMService response message to the UE including the ICCID of the eSIM of the Phantom SIM network.

[0169] In the thirty-eighth embodiment, a processor is configured to perform the method according to the thirty-seventh embodiment.

[0170] In the thirty-ninth embodiment, a server device includes: a network interface configured to communicate with a network; and a processor communicatively coupled to the network interface and configured to perform the method according to the thirty-fourth embodiment.

[0171] In a fortieth embodiment, a method includes: performing an operation to transfer a Mobile Network Operator (MNO) Subscriber Identity Module (SIM) from another UE to the UE, wherein the other UE includes a first Phantom SIM network embedded SIM (eSIM); storing an operator combo packet associated with the MNO SIM, wherein the operator combo packet includes addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; configuring transceiver circuitry to send a getEntitlement message to the authorization server; and decoding a getEntitlement response message based on signaling received from the authorization server, the getEntitlement response message indicating that the UE may offload the MNOSIM service to the Phantom SIM network; and configuring transceiver circuitry to send a signUpForSIMService message to the authorization server, wherein the signUpForSIMService message includes the MNO... The SIM's primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity; decoding a signUpForSIMService response message containing the ICCID of a second eSIM of the Phantom SIM network, which is different from the first eSIM, according to signaling received from the authorization server; configuring the transceiver circuit to send a download ICCID request message containing the ICCID of the second eSIM to the Phantom SIM Network Subscription Manager-Data Preparation+ (SM-DP+); decoding the second eSIM of the Phantom SIM network according to signaling received from the SM-DP+; and installing the second eSIM of the Phantom SIM network on the UE.

[0172] In the forty-first embodiment, a processor is configured to perform the method according to the forty-first embodiment.

[0173] In the forty-second embodiment, a user equipment includes: a transceiver circuit configured to communicate with a network; and a processor communicatively coupled to the transceiver circuit and configured to perform the method according to the forty-first embodiment.

[0174] Those skilled in the art will understand that the example embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Example hardware platforms for implementing the example embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Example embodiments of the methods described above may be embodied as programs containing lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0175] Although this application describes various embodiments that have different features in various combinations, those skilled in the art will understand that any feature of one embodiment can be combined with features of other embodiments in any way that is not expressly denied or that is not functionally or logically inconsistent with the operation of the device or the specified function of the disclosed embodiment.

[0176] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0177] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover modifications and variations thereof, provided they fall within the scope of the appended claims and their equivalents.

Claims

1. An apparatus comprising a processing circuit configured to: The storage includes an operator bundle associated with a Mobile Network Operator (MNO) Subscriber Identity Module (SIM), wherein the operator bundle includes the addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; It has been confirmed that the triggering condition has occurred; Generate a getEntitlement message to send to the authorization server; Based on the signaling received from the authorization server, a getEntitlement response message is processed, which indicates that the user equipment (UE) is allowed to offload the MNO SIM service to an embedded SIM (eSIM) of the Phantom SIM network, wherein the eSIM and the MNO SIM are associated with the same telephone number; Generate a signUpForSIMService message that includes the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the MNO SIM for sending to the authorization server; Based on the signaling received from the authorization server, process the signUpForSIMService response message, which includes the ICCID of the eSIM of the Phantom SIM network; Generate a Download ICCID Request Message including the ICCID of the eSIM for sending to Phantom SIM Network Subscription Manager - Data Preparation+ (SM-DP+). The eSIM of the Phantom SIM network is processed based on the signaling received from the SM-DP+. as well as The eSIM of the Phantom SIM network is installed 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 circuit is further configured to: One or more geofences are processed based on signaling received from the authorization server; When within a geographic area within one or more geofences, data operations are performed using the eSIM of the Phantom SIM network; as well as When the geographic area is not within one or more geofences, data operations are performed using the MNO SIM.

4. The apparatus according to claim 1, wherein the triggering condition includes restarting the UE, inserting the MNO SIM, or switching the flight mode of the UE.

5. The apparatus of claim 1, wherein the processing circuit is further configured to: It has been determined that the second triggering condition has occurred; Generate a second getEntitlement message to send to the authorization server; Based on the signaling received from the authorization server, process the second getEntitlement response message of the eSIM that indicates the UE cannot offload the MNO SIM service to the Phantom SIM network; The eSIM status of the Phantom SIM network is processed based on signaling received from the authorization server.

6. The apparatus of claim 5, wherein the state of the eSIM is disabled, and wherein the processing circuitry is further configured to: Disable the eSIM.

7. The apparatus of claim 5, wherein the state of the eSIM is deleted, and wherein the processing circuitry is further configured to: Delete the eSIM.

8. The apparatus of claim 1, wherein the processing circuit is further configured to: Based on the signaling received from the authorization server, process the message instructing the UE not to offload the MNO SIM service to the eSIM in the Phantom SIM network; and In response to the message, disable the eSIM.

9. The apparatus of claim 1, wherein the processing circuit is further configured to: It is determined that 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 circuit is further configured to: In response to determining that the MNO SIM has been removed from the UE, the eSIM of the Phantom SIM network is deleted.

11. The apparatus of claim 10, wherein the processing circuit is further configured to: It has been confirmed that the MNO SIM has been reinstalled in the UE; In response to the MNO SIM being reinstalled, a second signUpForSIMService message is generated for sending to the authorization server; Based on the signaling received from the authorization server, a second signUpForSIMService response message is processed, the second signUpForSIMService response message including the ICCID of the second eSIM of the Phantom SIM network associated with the MNO SIM; Generate a download ICCID request message including the ICCID of the second eSIM for sending to the SM-DP+; The second eSIM of the Phantom SIM network is processed based on the signaling received from the SM-DP+. as well as The second eSIM of the Phantom SIM network is installed on the UE.

12. The apparatus of claim 9, wherein the processing circuit is further configured to: In response to determining that the MNO SIM has been removed from the UE, the eSIM is disabled; Start the timer; as well as The timer is reset when the MNO SIM has been reinstalled in the UE; or Reactivate the eSIM before the timer expires; or When the timer expires, the eSIM is deleted.

13. The apparatus of claim 1, wherein the processing circuit is further configured to: Disable the MNO SIM; It is determined that the second MNO SIM is installed on the UE; and Determine whether the UE includes a second eSIM that is bound to the second MNO SIM.

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

15. The apparatus of claim 13, wherein when the UE does not include the second eSIM bound to the second MNO SIM, the processing circuitry is further configured to: Generate a second signUpForSIMService message to send to the authorization server; Based on the signaling received from the authorization server, a second signUpForSIMService response message is processed, the second signUpForSIMService response message including the ICCID of the second eSIM of the Phantom SIM network associated with the second MNO SIM; Generate a download ICCID request message including the ICCID of the second eSIM for sending to the SM-DP+; The second eSIM of the Phantom SIM network is processed based on the signaling received from the SM-DP+. Install the second eSIM of the Phantom SIM network on the UE; as well as Disable the eSIM.

16. The apparatus of claim 1, wherein the processing circuit is further configured to: It is determined that the second MNO SIM is installed on the UE; Determine whether the second MNO SIM is associated with the same MNO as the MNO SIM.

17. The apparatus of claim 16, wherein when the second MNO SIM is not related to an MNO that is the same as the MNO SIM, the processing circuit is further configured to: Prevent the UE from downloading the second eSIM associated with the second MNO SIM; Disable the eSIM; as well as Configure the UE to operate in dual SIM mode.

18. The apparatus of claim 17, wherein when the second MNO SIM is associated with an MNO that is the same as the MNO SIM, the processing circuit is further configured to: A second signUpForSIMService message is generated and sent to the authorization server. Based on the signaling received from the authorization server, a second signUpForSIMService response message is processed, the second signUpForSIMService response message including the ICCID of the second eSIM of the Phantom SIM network associated with the second MNO SIM; Generate a download ICCID request message including the ICCID of the second eSIM for sending to the SM-DP+; The second eSIM of the Phantom SIM network is processed based on the signaling received from the SM-DP+. Install the second eSIM of the Phantom SIM network on the UE; Disable the eSIM and the second eSIM; as well as Configure the UE to operate in dual SIM mode.

19. An apparatus comprising a processing circuit configured to: The storage includes an operator bundle associated with a Mobile Network Operator (MNO) Subscriber Identity Module (SIM), wherein the operator bundle includes the addresses of an MNO authorization server for the MNO network and an authorization server for the Phantom SIM network; It is determined that a triggering condition has occurred, wherein the triggering condition is related to the UE performing an operation related to offloading MNO SIM services to the Phantom SIM network via an embedded SIM (eSIM); It is determined that the UE includes an eSIM bound to the MNO SIM; as well as Prevent the UE from downloading an additional eSIM associated with the MNO SIM.

20. A Phantom SIM network authorization server, wherein the Phantom SIM network authorization server is configured to: Receive the getEntitlement message from the user equipment (UE); The UE is sent a getEntitlement response message, which instructs the UE to offload the Mobile Network Operator (MNO) Subscriber Identity Module (SIM) service to the embedded SIM (eSIM) of the Phantom SIM network, wherein the eSIM and the MNO SIM are associated with the same telephone number; The UE receives a signUpForSIMService message that includes the primary integrated circuit card identifier (ICCID), embedded identity document (EID), and auxiliary international mobile equipment identity of the MNO SIM. A request message is sent to the Service Support System (BSS) of the Phantom SIM network to provide the eSIM to the UE. Receive a supply response from the BSS indicating that the eSIM has been supplied to the UE; as well as The UE is sent a signUpForSIMService response message that includes the ICCID of the eSIM in the Phantom SIM network.

Images