Mobile virtual network operator identifier list in a subscriber identity module

Abstract

Methods, systems, and devices for wireless communications are described. A subscriber identity module (SIM) provisioned by an mobile virtual network operator (MVNO) may include operators with a file that contains a list of MVNO identifiers (IDs). Further, during manufacture, the device (e.g., the operating system) may be provisioned with one or more MVNO IDs. As part of SIM initialization, a device may compare the configured MVNO IDs against a list of MVNO IDs obtained from an active operator profile on the SIM. The device may communicate (e.g., establish a communication link) with the network if the comparison is successful (e.g., the device determines that the obtained MVNO ID matches one the configured MVNO IDs).

Description

MOBILE VIRTUAL NETWORK OPERATOR IDENTIFIER LIST IN A SUBSCRIBER IDENTITY MODULECROSS REFERENCE

[0001] The present Application for Patent claims priority to India Patent Application No. 202321078605 by NELUROUTH et al., entitled ‘MOBILE VIRTUAL NETWORK OPERATOR IDENTIFIER LIST IN A SUBSCRIBER IDENTITY MODULE,” filed November 20, 2023, which is assigned to the assignee hereof and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including a mobile virtual network operator identifier list in a subscriber identity module.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various ty pes of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transfomi spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support a mobile virtual netw ork operator (MVNO) identifier list in asubscriber identity module (SIM). For example, the described techniques provide for a SIM card provisioned by an MVNO, which may include operators with a file (e.g., an Elementary file) that contains a list of MVNO identifiers (IDs), where each MVNO ID may be associated with an MVNO with which the operator has made an agreement. Further, during manufacture, the device (e.g., the operating system) may be provisioned with one or more MVNO IDs. An MVNO SIM card may contain multiple operator profiles, and each operator profile may be configured with a list of MVNO IDs. As part of SIM initialization (e.g., based on bootup of the device), a device may compare its configured MVNO ID against a list of MVNO IDs obtained from one of the operator profiles on the SIM. For example, the one of the operator profiles may be an example of an active operator profile on the SIM. The device may communicate with the network if the comparison is successful (e.g., the device determines that the obtained MNVO ID matches one its configured MVNO IDs). In some cases, an MVNO device may switch between operator profiles. In such cases, the device may be re-initialized, and a comparison may be made between a configured MVNO ID and a list of MVNO IDs associated with the new operator profile.

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module, verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE, and communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may be individually or collectively operable to execute the code to cause the UE to obtain, from a subscriber identify module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identify module, verify that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in an operator data store of the UE. andcommunicating, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0007] Another UE for wireless communications is described. The UE may include means for obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module, means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. and means for communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by a processor to obtain, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity' module, verify' that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE, and communicate, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0009] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the subscriber identity module may be configured with a second operator profile that includes a second set of mobile virtual network operator identifiers.

[0010] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the second set of mobile virtual network operator identifiers includes one or more mobile virtual network operator identifiers of the set of mobile virtual network operator identifiers.

[0011] In some examples of the method. UE, and non-transitory computer-readable medium described herein, the operator profile includes an elementary file that includes the set of mobile virtual network operator identifiers.

[0012] Some examples of the method, UE, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining a second set of mobile virtual network operator identifiers that may be included in a second operator profile on the subscriber identity module, verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identity module may be included in the operator data store of the UE, and communicating, based on verifying that the one or more second identifiers may be included in the operator data store of the UE, with a second radio access network of a second carrier that may be associated with the second operator profile.

[0013] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the second set of mobile virtual network operator identifiers may be obtained based on switching between the operator profile and the second operator profile.

[0014] In some examples of the method, UE, and non-transitory computer-readable medium described herein, an operating system of the user equipment may be configured with the one or more identifiers during a device provisioning procedure.

[0015] In some examples of the method. UE, and non-transitory computer-readable medium described herein, obtaining the set of mobile virtual network operator identifiers may include operations, features, means, or instructions for performing a device personalization check, where the set of mobile virtual network operator identifiers may be obtained based on performing the device personalization check.

[0016] In some examples of the method. UE, and non-transitory computer-readable medium described herein, the communicating may be permitted based on the carrier having a roaming agreement with an operator associated with the operator profile.

[0017] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the operator profile may be configured by the carrier.

[0018] In some examples of the method, UE, and non-transitory computer-readable medium described herein, communicating with the radio access network may include operations, features, means, or instructions for transmitting, to the radio access network,an indication of the one or more identifiers and establishing a communication link with the radio access network based on transmitting the indication of the one or more identifiers.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG. 1 shows an example of a wireless communications system that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0020] FIG. 2 shows an example of a wireless communications system that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0021] FIG. 3 shows an example of a process flow that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0022] FIGs. 4 and 5 show block diagrams of devices that support a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0023] FIG. 6 shows a block diagram of a communications manager that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0024] FIG. 7 shows a diagram of a system including a device that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.

[0025] FIGs. 8 through 11 show flowcharts illustrating methods that support a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0026] In some wireless communications systems, an operator (or a wireless communications earner) may subsidize a device for users to maintain subscribers on theoperator’s network for a contract period. A SIMLOCK procedure (also referred to device personalization) may bind a device to a specific operator using information on the subscriber identity module (SIM) card and information provisioned on the device during device manufacture. Mobile Virtual Network Operators (MVNOs) are operators that work with multiple different operators to support network access. MVNOs establish agreements with multiple operator networks (e.g., carriers) across a region or regions for providing global connectivity. MVNOs also issue devices and SIM cards, but these SIM cards may host multiple operator profiles. A user equipment (UE) may add or delete operator profiles from the MVNO SIMs based on changes to their operator agreements. Further, UEs may switch between profiles on the MVNO SIMs for global network coverage. The use of multiple and changing profiles may render device subsidization by MVNOs cost prohibitive. That is, MVNO configured device may allow a user to swap a SIM to an operator SIM, thereby bypassing the MVNO. Thus, solutions to simplify SIMLOCK procedures to subsidize devices for an MVNO are desirable.

[0027] In some implementations of the present disclosure, a SIM card provisioned by an MVNO may include operators with a file (e.g., an Elementary' file) that contains a list of MVNO identifiers (IDs), where each MVNO ID may be associated with an MVNO with which the operator has made an agreement. Further, during manufacture, the device (e.g., the operating system of the device) may be provisioned with one or more MVNO IDs. An MVNO SIM card may contain multiple operator profiles, and each operator profile may be configured with a list of MVNO IDs. As part of SIM initialization (e.g., after or based on bootup of the device), a device may compare its configured MVNO ID against a list of MVNO IDs obtained from one of the operator profiles on the SIM. For example, the one of the operator profiles may be an example of an active operator profile on the SIM. The device may communicate with the network if the comparison is successful (e.g., the device determines that the obtained MNVO ID matches one its configured MVNO IDs). In some cases, an MVNO device may switch between operator profiles. In such cases, the device may be re-initialized, and a comparison may be made between a configured MVNO ID and a list of MVNO IDs associated with the new' operator profile. These and other techniques are described in further detail with respect to the figures.

[0028] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to mobile virtual network operator identifier list in a subscriber identity module.

[0029] FIG. 1 shows an example of a wireless communications system 100 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0030] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 1 15 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity' 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0031] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

[0032] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity' 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 1 15, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity' 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity' 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0033] In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g.. in accordance with an S I, N2, N3. or other interface protocol). In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g.. in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wirelessoptical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0034] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver. aNodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology ). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0035] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (I AB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC). aNon-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0036] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g.,network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170. and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170). In some cases, a functional split between a CU 160 and a DU 165. or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165. or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e g.. Fl, Fl-c, Fl-u), and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

[0037] In wireless communications systems (e.g., wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IABnetwork architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g.. referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.

[0038] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to a mobile virtual network operator identifier list in a subscriber identity module as descnbed herein. For example, some operations described as being performed by a UE 115 or a network entity7105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175. SMO 180).

[0039] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology7, where the “device’’ may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digitalassistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

[0040] The UEs 115 described herein may be able to communicate with various ty pes of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs. small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0041] The UEs 1 15 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier’ may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g.. synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity' 105 and other devices may refer to communication between the devices and any portion (e.g., entity, subentity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity' 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0042] Signal waveforms transmited via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g.. a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0043] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=seconds, for which bfmaxmay represent a supported subcarrier spacing, and N may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0044] Each frame may include multiple consecutively -numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g.. in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one ormore (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0045] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g.. in bursts of shortened TTIs (sTTIs)).

[0046] Physical charnels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given pay load size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.

[0047] In some examples, a network entity’ 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0048] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more sendees such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of sen ices, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0049] In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P). D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (EM) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

[0050] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0051] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0052] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial,scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a earner aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0053] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 1 15 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A netw ork entity' 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0054] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a netw ork entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path betw een the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0055] The wireless communications system 100 may be supported by one or more operators (e g., carriers). For example, a first network entity 105 may provide service for a first operator and a second network entity 105 may provide sendee for a second operator. Additionally, the UEs 115 may be configured with SIM cards that support access to networks supported by one or more operators. An operator (e.g., the first operator or the second operator) may subsidize a device (e.g., a UE 115) for users to maintain subscribers on the operator’s network for a contract period. A SIMLOCK procedure (also referred to device personalization) may bind a device to a specific operator using information on the SIM card and information provisioned on the device during device manufacture. A MVNO is a ty pe of operator that establish agreements with multiple operator networks (e.g., carriers) across a region or regions for providing global connectivity. That is, MVNOs may not implement the physical infrastructure (e.g., network entities 105) to support the wireless communications system, but rather, MVNOs may establish agreements with other operators to support network access via infrastructure established by the other operators. In some cases, an MVNO may also issue devices and SIM cards. The SIM cards may host multiple operator profiles and may add or delete profiles based on changes to their operator agreements. Further, the UEs 115 may switch between the operator profiles on the MVNO SIM cards for global network coverage.

[0056] Techniques described herein support subsidization of devices by MVNOs that addresses issues related to SIM swapping. In some implementations of the present disclosure, the UE 115 may include a SIM card provisioned by an MVNO. The SIM card may include operators with a file (e.g., an Elementary file) that contains a list of MVNO IDs, where each MVNO ID may be associated with an MVNO with which the operator has made an agreement. Further, during manufacture, the device (e.g., the operating system of the UE 115) may be provisioned with one or more MVNO IDs. An MVNO SIM card may contain multiple operator profiles, and each operator profile may be configured with a list of MVNO IDs. As part of SIM initialization a device maycompare its configured MVNO ID against a list of MVNO IDs obtained from one of the operator profiles on the SIM. For example, the one of the operator profiles may be an example of an active operator profile on the SIM. The device may communicate with the network (e.g., the wireless communications system 100) if the comparison is successful (e.g., the device determines that the obtained MNVO ID matches one its configured MVNO IDs). In some cases, the UE 115 with the MVNO SIM may switch between operator profiles on the SIM. In such cases, the UE 115 may be re-initialized, and a comparison may be made between a configured MVNO ID and a list of MVNO IDs associated with the new operator profile. Accordingly, UEs 115 of the wireless communications system 100 may be configured with MVNO compatible information, including MVNO IDs in the SIM card and MVNO IDs in the UEs 115, such as to support MVNO operations and device subsidization.

[0057] FIG. 2 shows an example of a wireless communications system 200 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may include a UE 115-a, a network entity 105-a, and a network entity 105-b. The UE 115-a may communicate with the network entity 105-a, the network entity 105-b, or both, via uplink and downlink signaling. In some cases, the wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more UEs 115 (e.g., the UE 115-a) and one or more network entities 105 (e.g., the network entities 105-a and 105-b), which may be examples of the corresponding devices as described herein.

[0058] The UE 115-a may include a SIM 205 (e.g., a SIM card) which may include one or more operator profiles 210. The one or more operator profiles 210 may include one or more files 215 (e.g.. elementary files). For example, the SIM 205 may include an operator profile 210-a and an operator profile 210-b. In some cases, the SIM 205 may be associated with a first MVNO. For example, the first MVNO may provision the SIM 205.

[0059] In some implementations, the operator profile 210-a may include a file 215-a, which may include a list of one or more MVNO identifiers (MVNO IDs) (e.g., an MVNO ID list). The operator profile 210-a may correspond to an operator A whichprovides sendee to the network entity 105-a. Similarly, the operator profile 210-b may include a file 215-b, which may also include an MVNO ID list. The operator profile 210-b may correspond to an operator B which provides sendee to the network entity 105-b. The files 215 may be elementary files (EFs).

[0060] The one or more MVNO IDs on the file 215-a may be associated with one or more MVNOS with which the operator A has agreements. In some cases, an MVNO ID may correspond to the first MVNO. If the operator has agreements with the first MVNO, an MVNO ID list on the file 215-a may include the MVNO ID corresponding to the first MVNO. Similarly, if the operator B has agreements with the first MVNO, an MVNO ID list on the file 215-b may include the MVNO ID corresponding to the first MVNO.

[0061] As described herein, the MVNO lists for an operator profile may be included in or formatted as the files 215, which may be a basic data file (e.g., elementary file) that is configured to store information. For example, elementary files may store a mobile subscriber phone number, services, or other information related to the network. Accordingly, SIMs may include specific elementary files for specific types of data, such as a EF_IMSI for holding the international mobile subscriber identity7. Accordingly, a similar file (e.g., EF_MVNOList) may contain the list of MVNO IDs, as described herein. Standards may define the structure and behavior of such files and the respective attributes. The SIM 205 may include the MVNO list under a universal subscriber identity7module (USIM) application. In some cases, the SIM 205, the USIM application, the operator profiles 210, the files 215, the MVNO lists, or any combination thereof may include administrative (ADM) personal identification number (PIN) protection. For example, during a manufacturing process (e.g., in a factory or during a SIMLOCK procedure), the first MVNO may securely provision the one or more MVNO IDs on the SIM 205 with ADM PIN protection or similar ty pes of protection.

[0062] In some implementations, each operator profile 210 may be configured with one or more lists of MVNO IDs (e.g., MVNO ID lists) based on an agreement between the first MVNO and one or more operators. For example, the first MVNO may establish an agreement with the operator A (e.g., through payment). The operator A may add an MVNO ID associated with the first MVNO to the MVNO ID list on the file 215-a on the operator profile 210-a. The MVNO ID list on the file 215-a may also include one ormore MVNO IDs for a terrestrial network (TN), a non-terrestrial network (NTN), or both, associated with the operator A, the first MVNO, or both. In some cases, if the SIM 205 (e.g., the SIM provisioned by the first MVNO) is to operate with a quantity of operators (e.g., 10 operators across the globe), the SIM 205 may include a quantity of operator profiles 210 equal to the quantity of operators. In such cases, each operator profile may include, in an MVNO ID list on a file 215, the MVNO ID corresponding to the first MVNO.

[0063] In some cases, a specific operator may provide service to multiple MVNOs. In such cases, the operator profile 210 which corresponds to the specific operator may include MVNO IDs corresponding to each of the multiple MVNOs. The operator profile 210 may include the MVNO IDs on the corresponding file 215. For example, if the operator A provides service to (e.g., serves or allows) MVNOs X, Y, and Z, the operator profile 210-a which corresponds to the operator A may include, in the file 215-a, an MVNO ID corresponding to each of the MVNOs X, Y, and Z.

[0064] In some cases, as part of an initialization procedure for the SIM 205 (e.g., during or in response to device bootup), the UE 115-a may compare a configured MVNO ID (e.g., an MVNO ID with which the UE 115-a or the SIM 205 is configured) with a list of MVNO IDs configured on an active operator profile 210-a (e.g., a current operator profile) of the SIM 205. For example, the initialization procedure may occur as part of a subscription initialization procedure (e.g., during manufacturing or during a SIMLOCK procedure). In some cases, if the configured MVNO ID is found on the list of MVNO IDs configured on the active operator profile 210-a (e.g., if there is a match), the SIM 205 or the UE 115-a may determine that the subscription initialization procedure is valid (e.g., that the subscription is valid). In such cases, the SIM 205 or the UE 115-a may allow the subscription (e.g., the subscription may be allowed to camp). In some cases, if the configured MVNO ID is not found on the list of MVNO IDs configured on the active operator profile 210-a (e.g., if there is not a match), the SIM 205 or the UE 115-a may determine that the subscription initialization procedure is invalid (e.g., that the subscription is invalid). In such cases, the SIM 205 or the UE 115-a may not allow7the subscription (e.g., the subscription may not be allowed to camp).

[0065] In some implementations, the UE 1 15-a may switch the active operator profile 210-a of the SIM 205. For example, the UE 115-a may switch the active operator profile 210-a from the operator profile 210-a to the operator profile 210-b based on a change in a location / region of the UE 115-a. based on a reboot of the UE 115-a, or the like. In some examples, only one profile 210 may be active on the UE 115-a at a time. If the UE 115-a performs such a switch, the UE 115-a may reinitialize (e.g., perform a reinitialization procedure on) the SIM 205 and may again compare the MVNO ID to the MVNO ID list on the file 215-b (e.g., the elementary file) on the operator profile 210-b. As described herein with respect to the comparison made during initialization, the UE 115-a may compare the configured MVNO ID with the MVNO ID list and determine whether the subscription initialization procedure is valid or invalid. This method may enable the UE 115-a to allow or validate operator subscriptions corresponding to the operator profiles 210 based on a match between an MVNO ID in the MVNO ID list on the file 215 and the configured MVNO ID.

[0066] FIG. 3 shows an example of a process flow 300 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The process flow 300 incudes a UE 115-b, a network entity 105-c, and a network entity 105-d, which may be examples of the corresponding devices as described with respect to FIGs. 1 and 2. The network entity 105-c may support wireless communications with one or more first operators, and the network entity 105-d may support wireless communications with one or more second operators. As described herein, an operator may correspond to a carrier, region, or the like. The UE 1 15-b may be configured with a SIM that includes one or more operator profiles. Each operator profile may be configured with a respective set of mobile virtual network identifiers.

[0067] At 305, the UE 115-b may perform (e.g., initiate) a device personalization check. The UE 115-b may initiate the device personalization check based on a boot of the device. Device personalization check may also be referred to as SIM initialization or SIM authorization.

[0068] At 310, the UE 115-b may obtain (e.g., retrieve, receive, read) from a SIM of the UE. a set of MVNO identifiers that are included in an operator profile on the SIM. In some cases, the operator profile includes an elementary file (or another type of file ordata object) that includes the MVNO identifiers. In some examples, the SIM is configured with a second operator profile that includes a second set of MVNO identifiers. The second set of MVNO identifiers may overlap with the first set of MVNO identifiers of the first operator profile.

[0069] At 315. the UE 115-b may verify that one or more identifiers of the set of MVNO identifiers obtained from the SIM are included in an operator data store (e.g., a SIMLOCK database) of the UE 115-b. Verification of the one or more identifiers may include comparing the set of MVNO identifiers obtained from SIM to one or more MVNO identifiers that are configured at the operating system of the UE 115-b. If the UE 1 15-b determined that one of the MVNO identifiers obtained from the SIM matches one of the operating system configured identifiers, then the verification passes.

[0070] At 320, the UE 115-b may communicate, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile. For example, the radio access network may be supported by the network entity 105-c. In some examples, the operator profile is associated with the carrier based on the carrier having a roaming agreement with the operator associated with the operator profile. Additionally, or alternatively, the operator profile is associated with carrier based on the operator profile being configured by the carrier. Communicating with the radio access network may include transmitting, to the radio access network, an indication of the one or more identifiers and establishing a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers. For example, the UE 115-b may communicate the MVNO identifiers to the network such that the network can authenticate the UE 115-b, the SIM, or both.

[0071] At 325, the UE 115-b may perform (e g., initiate) a second device personalization check. For example, the UE 115-b may initiate the second device personalization check based at least in part on the UE 115-b being booted, the UE 115-b switching between operator profiles on the SIM, and / or the UE 115-b being in a different location or region associated with a different operator.

[0072] At 330, the UE 115-b may obtain the second set of MVNO identifiers that are included in a second operator profile on the SIM. At 335, the UE 115-b may verify'that one or more second identifiers of the second set of MVNO identifiers obtained from the SIM are included in the operator data store of the UE.

[0073] At 340, the UE 115-b may communicate, based on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile. For example, the second radio access network may be supported by the network entity 105-d, and the UE 115-b may communicate with the network entity 105-d.

[0074] FIG. 4 shows a block diagram 400 of a device 405 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The device 405 may be an example of aspects of a UE 1 15 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. The device 405, or one or more components of the device 405 (e.g., the receiver 410, the transmitter 415, and the communications manager 420), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0075] The receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to mobile virtual network operator identifier list in a subscriber identity module). Information may be passed on to other components of the device 405. The receiver 410 may utilize a single antenna or a set of multiple antennas.

[0076] The transmitter 415 may provide a means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to mobile virtual network operator identifier list in a subscriber identity module). In some examples, the transmitter 415 may be co-located with a receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a set of multiple antennas.

[0077] The communications manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of mobile virtual network operator identifier list in a subscriber identity module as described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0078] In some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g.. by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0079] Additionally, or alternatively, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0080] In some examples, the communications manager 420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 410. the transmitter415, or both. For example, the communications manager 420 may receive information from the receiver 410, send information to the transmitter 415, or be integrated in combination with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0081] The communications manager 420 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 420 is capable of, configured to, or operable to support a means for obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module. The communications manager 420 is capable of, configured to, or operable to support a means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The communications manager 420 is capable of, configured to, or operable to support a means for communicating, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0082] By including or configuring the communications manager 420 in accordance with examples as described herein, the device 405 (e.g., at least one processor controlling or otherwise coupled with the receiver 410, the transmitter 415. the communications manager 420, or a combination thereof) may support techniques for mobile virtual network operator identifier list in a subscriber identity module, which may result in reduced processing, reduced power consumption, more efficient utilization of communication resources, among other advantages.

[0083] FIG. 5 shows a block diagram 500 of a device 505 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a device 405 or a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505. or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communications manager 520), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g.. via one or more buses).

[0084] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to mobile virtual network operator identifier list in a subscriber identity module). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0085] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to mobile virtual network operator identifier list in a subscriber identity7module). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0086] The device 505, or various components thereof, may be an example of means for performing various aspects of mobile virtual network operator identifier list in a subscriber identity7module as described herein. For example, the communications manager 520 may include an MVNO identifier component 525. an identifier verification component 530, a communication interface 535, or any combination thereof. The communications manager 520 may be an example of aspects of a communications manager 420 as described herein. In some examples, the communications manager 520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0087] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. The MVNO identifier component 525 is capable of, configured to, or operable to support a means for obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operatoridentifiers that are included in an operator profile on the subscriber identity module. The identifier verification component 530 is capable of, configured to, or operable to support a means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The communication interface 535 is capable of, configured to, or operable to support a means for communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0088] FIG. 6 shows a block diagram 600 of a communications manager 620 that supports a mobile virtual network operator identifier list in a subscriber identify module in accordance with one or more aspects of the present disclosure. The communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520. or both, as described herein. The communications manager 620, or various components thereof, may be an example of means for performing various aspects of mobile virtual network operator identifier list in a subscriber identify module as described herein. For example, the communications manager 620 may include an MVNO identifier component 625, an identifier verification component 630, a communication interface 635, a second MVNO identifier component 640, an identifier verification component 645, a communication interface 650, a device personalization check component 655, an identifier transmission component 660, a communication link component 665, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0089] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The MVNO identifier component 625 is capable of, configured to, or operable to support a means for obtaining, from a subscriber identify module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identify module. The identifier verification component 630 is capable of, configured to, or operable to support a means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in anoperator data store of the UE. The communication interface 635 is capable of, configured to, or operable to support a means for communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0090] In some examples, the subscriber identity module is configured with a second operator profile that includes a second set of mobile virtual network operator identifiers.

[0091] In some examples, the second set of mobile virtual network operator identifiers includes one or more mobile virtual network operator identifiers of the set of mobile virtual network operator identifiers.

[0092] In some examples, the operator profile includes an elementary file that includes the set of mobile virtual network operator identifiers.

[0093] In some examples, the second MVNO identifier component 640 is capable of, configured to, or operable to support a means for obtaining a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identity module. In some examples, the identifier verification component 645 is capable of, configured to, or operable to support a means for verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in the operator data store of the UE. In some examples, the communication interface 650 is capable of, configured to, or operable to support a means for communicating, based on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile.

[0094] In some examples, the second set of mobile virtual network operator identifiers are obtained based on switch between the operator profile and the second operator profile.

[0095] In some examples, an operating system of the user equipment is configured with the one or more identifiers during a device provisioning procedure.

[0096] In some examples, to support obtaining the set of mobile virtual network operator identifiers, the device personalization check component 655 is capable of, configured to, or operable to support a means for performing a device personalization check, where the set of mobile virtual network operator identifiers are obtained based on performing the device personalization check.

[0097] In some examples, the communicating is permitted based on the carrier having a roaming agreement with an operator associated with the operator profile.

[0098] In some examples, the operator profile is configured by the carrier.

[0099] In some examples, to support communicating with the radio access network, the identifier transmission component 660 is capable of, configured to, or operable to support a means for transmitting, to the radio access network, an indication of the one or more identifiers. In some examples, to support communicating with the radio access network, the communication link component 665 is capable of, configured to, or operable to support a means for establishing a communication link with the radio access network based on transmitting the indication of the one or more identifiers.

[0100] FIG. 7 shows a diagram of a system 700 including a device 705 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with one or more aspects of the present disclosure. The device 705 may be an example of or include the components of a device 405, a device 505, or a UE 115 as described herein. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 720. an input / output (I / O) controller 710. a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

[0101] The I / O controller 710 may manage input and output signals for the device 705. The I / O controller 710 may also manage peripherals not integrated into the device 705. In some cases, the I / O controller 710 may represent a physical connection or portto an external peripheral. In some cases, the I / O controller 710 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 710 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as the at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0102] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bi-directionally, via the one or more antennas 725, wired, or wireless links as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 715 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725. The transceiver 715, or the transceiver 715 and one or more antennas 725, may be an example of a transmitter 415, a transmitter 515, a receiver 410, a receiver 510, or any combination thereof or component thereof, as described herein.

[0103] The at least one memory 730 may include random access memory (RAM) and read-only memory (ROM). The at least one memory' 730 may store computer- readable, computer-executable code 735 including instructions that, when executed by the at least one processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory . In some cases, the code 735 may not be directly executable by the at least one processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 730 may contain, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0104] The at least one processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 740. The at least one processor 740 may be configured to execute computer-readable instructions stored in a memory (e g., the at least one memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting mobile virtual network operator identifier list in a subscriber identity module). For example, the device 705 or a component of the device 705 may include at least one processor 740 and at least one memoi ' 730 coupled with or to the at least one processor 740, the at least one processor 740 and at least one memory 730 configured to perform various functions described herein. In some examples, the at least one processor 740 may include multiple processors and the at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 740 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry' (including, for example, one or both of processor circuitry' (which may include the at least one processor 740) and memory' circuitry (which may include the at least one memory 730)). or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 740 or a processing system including the at least one processor 740 may be configured to. configurable to, or operable to cause the device 705 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, yvhen executing code stored in the at least one memory’ 730 or otherwise, to perform one or more of the functions described herein.

[0105] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a means for obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module. The communications manager 720 is capable of, configured to, or operable to support a means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The communications manager 720 is capable of. configured to, or operable to support a means for communicating, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0106] By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 may support techniques for mobile virtual network operator identifier list in a subscriber identity module, which may result in improved communication reliability', reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, among other advantages.

[0107] In some examples, the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 715, the one or more antennas 725, or any combination thereof. Although the communications manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 720 may be supported by or performed by the at least one processor 740, the at least one memory' 730. the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the at least one processor 740 to cause the device 705 to perform various aspects of mobile virtual network operator identifier list in a subscriber identify module as described herein, or the at least one processor 740 and the at least one memory' 730 may be otherwise configured to, individually or collectively, perform or support such operations.

[0108] FIG. 8 shows a flowchart illustrating a method 800 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a UE or its components as described herein. For example, the operations of the method 800 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0109] At 805, the method may include obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module. The operations of block 805 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 obtaining the MVNO identifiers from one or more of the files 215 of the operator profiles 210. That is, the operator profile and the information included therein may be similar to that as described with respect to, and illustrated in, Figure 2. In some examples, aspects of the operations of 805 may be performed by an MVNO identifier component 625 as described with reference to FIG. 6.

[0110] At 810. the method may include verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The operations of block 810 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 verifying the MVNO identifiers from one or more of the files 215 of the operator profiles 210. The UE 115 may verify the MVNO identifiers similar to as described in Figures 2 and 3. In some examples, aspects of the operations of 810 may be performed by an identifier verification component 630 as described with reference to FIG. 6.[OHl] At 815, the method may include communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile. The operations of block 815 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 communicating with a radio access network supported by thenetwork entity 105-a and / or the network entity! 05-b and corresponding carriers. In some examples, aspects of the operations of 815 may be performed by a communication interface 635 as described with reference to FIG. 6.

[0112] FIG. 9 shows a flowchart illustrating a method 900 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0113] At 905, the method may include obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module. The operations of block 905 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 obtaining the MVNO identifiers from one or more of the files 215 of the operator profiles 210. That is, the operator profile and the information included therein may be similar to that as described with respect to, and illustrated in, Figure 2. In some examples, aspects of the operations of 905 may be performed by an MVNO identifier component 625 as described with reference to FIG. 6.

[0114] At 910, the method may include verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The operations of block 910 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 verifying the MVNO identifiers from one or more of the files 215 of the operator profiles 210. The UE 115 may verify the MVNO identifiers similar to as described in Figures 2 and 3. In some examples, aspects of the operations of 910 may be performed by an identifier verification component 630 as described with reference to FIG. 6.

[0115] At 915, the method may include communicating, based on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile, such as the UE 115-a of Figure 2 communicating with a radio access network supported by the network entity 105-a and / or the network entity 105-b and corresponding carriers. The operations of block 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 91 may be performed by a communication interface 635 as described with reference to FIG. 6.

[0116] At 920, the method may include obtaining a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identity module. The operations of block 920 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 obtaining the MVNO identifiers from one or more of the files 215 of the operator profiles 210. That is. the operator profile and the information included therein may be similar to that as described with respect to, and illustrated in, Figure 2. In some examples, aspects of the operations of 920 may be performed by a second MVNO identifier component 640 as described with reference to FIG. 6.

[0117] At 925, the method may include verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in the operator data store of the UE. The operations of block 925 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 verifying the MVNO identifiers from one or more of the files 215 of the operator profiles 210. The UE 115 may verify’ the MVNO identifiers similar to as described in Figures 2 and 3. In some examples, aspects of the operations of 925 may be performed by an identifier verification component 645 as described with reference to FIG. 6.

[0118] At 930, the method may include communicating, based on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile. The operations of block 930 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 communicating with a radio access network supported by the network entity 105-a and / or the networkentity 105-b and corresponding carriers. In some examples, aspects of the operations of 930 may be performed by a communication interface 650 as described with reference to FIG. 6.

[0119] FIG. 10 shows a flowchart illustrating a method 1000 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0120] At 1005, the method may include performing a device personalization check, where the set of mobile virtual network operator identifiers are obtained based on performing the device personalization check. The operations of block 1005 may be performed in accordance with examples as disclosed herein, such as the UE 115-b performing a device personalization check as described in figure 3. In some examples, aspects of the operations of 1005 may be performed by a device personalization check component 655 as described with reference to FIG. 6.

[0121] At 1010, the method may include obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module, such as the UE 115-a of Figure 2 obtaining the MVNO identifiers from one or more of the files 215 of the operator profiles 210. That is. the operator profile and the information included therein may be similar to that as described with respect to, and illustrated in, Figure 2. The operations of block 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by an MVNO identifier component 625 as described with reference to FIG. 6.

[0122] At 1015, the method may include verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The operations ofblock 1015 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 verifying the MVNO identifiers from one or more of the files 215 of the operator profiles 210. The UE 115 may verify the MVNO identifiers similar to as described in Figures 2 and 3. In some examples, aspects of the operations of 1015 may be performed by an identifier verification component 630 as described with reference to FIG. 6.

[0123] At 1020, the method may include communicating, based on verify ing that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile. The operations of block 1020 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 communicating with a radio access network supported by the network entity 105-a and / or the network entity!05-b and corresponding carriers. In some examples, aspects of the operations of 1020 may be performed by a communication interface 635 as described with reference to FIG. 6.

[0124] FIG. 11 shows a flowchart illustrating a method 1 100 that supports a mobile virtual network operator identifier list in a subscriber identity module in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1 100 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0125] At 1105, the method may include obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identify module. The operations of block 1105 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 obtaining the MVNO identifiers from one or more of the files 215 of the operator profiles 210. That is, the operator profile and the information included therein may be similar to that as described with respect to, and illustrated in, Figure 2. In some examples, aspects of the operations of 1105 may be performed by an MVNO identifier component 625 as described with reference to FIG. 6.

[0126] At 1 1 10, the method may include verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE. The operations of block 1110 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 verifying the MVNO identifiers from one or more of the files 215 of the operator profiles 210. The UE 115 may verify the MVNO identifiers similar to as described in Figures 2 and 3. In some examples, aspects of the operations of 1110 may be performed by an identifier verification component 630 as described with reference to FIG. 6.

[0127] At 1115, the method may include communicating, based on verify ing that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile. The operations of block 1115 may be performed in accordance with examples as disclosed herein, such as the UE 115-a of Figure 2 communicating with a radio access network supported by the network entity 105-a and / or the network entity 105-b and corresponding carriers. In some examples, aspects of the operations of 1115 may be performed by a communication interface 635 as described with reference to FIG. 6.

[0128] At 1120, the method may include transmitting, to the radio access network, an indication of the one or more identifiers. The operations of block 1120 may be performed in accordance with examples as disclosed herein, such as the UE 115-b of Figure 3 transmitting an indication of an identifier in response to verifying an MVNO identifier obtained from the SIM. In some examples, aspects of the operations of 1120 may be performed by an identifier transmission component 660 as described with reference to FIG. 6.

[0129] At 1125, the method may include establishing a communication link with the radio access network based on transmitting the indication of the one or more identifiers. The operations of block 1125 may be performed in accordance with examples as disclosed herein. For example, the operations of block 1125 may be performed in accordance with techniques described with respect to Figures 2 and 3, where the corresponding UEs 115 establishing a link with the corresponding network entity 105. In some examples, aspects of the operations of 1125 may be performed by a communication link component 665 as described with reference to FIG. 6.

[0130] The following provides an overview of aspects of the present disclosure:

[0131] Aspect 1 : A method for wireless communications at a UE, comprising: obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module; verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE; and communicating, based at least in part on verify ing that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

[0132] Aspect 2: The method of aspect 1, wherein the subscriber identity module is configured with a second operator profile that includes a second set of mobile virtual network operator identifiers.

[0133] Aspect 3: The method of aspect 2, wherein the second set of mobile virtual network operator identifiers includes one or more mobile virtual network operator identifiers of the set of mobile virtual network operator identifiers.

[0134] Aspect 4: The method of any of aspects 1 through 3. wherein the operator profile includes an elementary file that comprises the set of mobile virtual network operator identifiers.

[0135] Aspect 5: The method of any of aspects 1 through 4, further comprising: obtaining a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identity module; verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identity' module are included in the operator data store of the UE; and communicating, based at least in part on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile.

[0136] Aspect 6: The method of aspect 5, wherein the second set of mobile virtual network operator identifiers are obtained based at least in part on switch between the operator profile and the second operator profile.

[0137] Aspect 7: The method of any of aspects 1 through 6, wherein an operating system of the user equipment is configured with the one or more identifiers during a device provisioning procedure.

[0138] Aspect 8: The method of any of aspects 1 through 7. wherein obtaining the set of mobile virtual network operator identifiers comprises: performing a device personalization check, wherein the set of mobile virtual network operator identifiers are obtained based at least in part on performing the device personalization check.

[0139] Aspect 9: The method of any of aspects 1 through 8 wherein the communicating is permitted based at least in part on the carrier having a roaming agreement with an operator associated with the operator profile.

[0140] Aspect 10: The method of any of aspects 1 through 9. wherein the operator profile is configured by the carrier.

[0141] Aspect 11 : The method of any of aspects 1 through 10, wherein communicating with the radio access network comprises: transmitting, to the radio access network, an indication of the one or more identifiers: and establishing a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers.

[0142] Aspect 12: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 11.

[0143] Aspect 13: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 11.

[0144] Aspect 14: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 11.

[0145] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0146] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology7may be used in much of the description, the techniques described herein are applicable beyond LTE. LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0147] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0148] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0149] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. Forexample, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0150] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory. compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0151] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e.. A and B and C). Also, as used herein, the phrase“based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0152] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components.” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0153] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0154] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished byfollowing the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

[0155] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term ‘‘example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0156] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary' skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:1 . A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: obtain, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module; verify that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE; and communicate, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

2. The UE of claim 1, wherein the subscriber identify module is configured with a second operator profile that includes a second set of mobile virtual network operator identifiers.

3. The UE of claim 2, wherein the second set of mobile virtual network operator identifiers includes one or more mobile virtual network operator identifiers of the set of mobile virtual network operator identifiers.

4. The UE of claim 1, wherein the operator profile includes an elementary file that comprises the set of mobile virtual network operator identifiers.

5. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: obtain a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identify module; verify that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in the operator data store of the UE; andcommunicate, based at least in part on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile.

6. The UE of claim 5, wherein the second set of mobile virtual network operator identifiers are obtained based at least in part on switch between the operator profile and the second operator profile.

7. The UE of claim 1, wherein an operating system of the user equipment is configured with the one or more identifiers during a device provisioning procedure.

8. The UE of claim 1, wherein, to obtain the set of mobile virtual network operator identifiers, the one or more processors are individually or collectively operable to execute the code to cause the UE to: perform a device personalization check, wherein the set of mobile virtual network operator identifiers are obtained based at least in part on performing the device personalization check.

9. The UE of claim 1, wherein the communicating is permitted based at least in part on the carrier having a roaming agreement with an operator associated with the operator profile.

10. The UE of claim 1 , wherein the operator profile is configured by the carrier.

11. The UE of claim 1, wherein, to communicate w ith the radio access netw ork, the one or more processors are individually or collectively operable to execute the code to cause the UE to: transmit, to the radio access netw ork, an indication of the one or more identifiers; and establish a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers.

12. A method for wireless communications at a user equipment (UE), comprising:obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module; verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE; and communicating, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

13. The method of claim 12, wherein the subscriber identify module is configured w ith a second operator profile that includes a second set of mobile virtual network operator identifiers.

14. The method of claim 13, wherein the second set of mobile virtual network operator identifiers includes one or more mobile virtual netw ork operator identifiers of the set of mobile virtual network operator identifiers.

15. The method of claim 12, wherein the operator profile includes an elementary file that comprises the set of mobile virtual netw ork operator identifiers.

16. The method of claim 12, further comprising: obtaining a second set of mobile virtual netw ork operator identifiers that are included in a second operator profile on the subscriber identify module; verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in the operator data store of the UE; and communicating, based at least in part on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated w i th the second operator profile.

17. The method of claim 16, wherein the second set of mobile virtual network operator identifiers are obtained based at least in part on switch between the operator profile and the second operator profile.

18. The method of claim 12, wherein an operating system of the user equipment is configured with the one or more identifiers during a device provisioning procedure.

19. The method of claim 12, wherein obtaining the set of mobile virtual network operator identifiers comprises: performing a device personalization check, wherein the set of mobile virtual network operator identifiers are obtained based at least in part on performing the device personalization check.

20. The method of claim 12 wherein the communicating is permitted based at least in part on the carrier having a roaming agreement with an operator associated with the operator profile.

21. The method of claim 12, wherein the operator profile is configured by the carrier.

22. The method of claim 12, wherein communicating with the radio access network comprises: transmitting, to the radio access network, an indication of the one or more identifiers; and establishing a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers.

23. A user equipment (UE) for wireless communications, comprising: means for obtaining, from a subscriber identity module of the UE, a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity module; means for verifying that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE; and means for communicating, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

24. The UE of claim 23, further comprising: means for obtaining a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identity module; means for verifying that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identity7module are included in the operator data store of the UE; and means for communicating, based at least in part on verifying that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile.

25. The UE of claim 23, wherein the means for obtaining the set of mobile virtual network operator identifiers comprise: means for performing a device personalization check, wherein the set of mobile virtual network operator identifiers are obtained based at least in part on performing the device personalization check.

26. The UE of claim 23, wherein the means for communicating with the radio access network comprise: means for transmitting, to the radio access network, an indication of the one or more identifiers; and means for establishing a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers.

27. A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to: obtain, from a subscriber identity module of a UE. a set of mobile virtual network operator identifiers that are included in an operator profile on the subscriber identity' module;verify that one or more identifiers of the set of mobile virtual network operator identifiers obtained from the subscriber identity module are included in an operator data store of the UE; and communicate, based at least in part on verifying that the one or more identifiers are included in the operator data store of the UE, with a radio access network of a carrier that is associated with the operator profile.

28. The non-transitory computer-readable medium of claim 27, wherein the instructions are further executable by the one or more processors to: obtain a second set of mobile virtual network operator identifiers that are included in a second operator profile on the subscriber identify module; verify that one or more second identifiers of the second set of mobile virtual network operator identifiers obtained from the subscriber identify module are included in the operator data store of the UE; and communicate, based at least in part on verify ing that the one or more second identifiers are included in the operator data store of the UE, with a second radio access network of a second carrier that is associated with the second operator profile.

29. The non-transitory computer-readable medium of claim 27, wherein the instructions to obtain the set of mobile virtual network operator identifiers are executable by the one or more processors to: perform a device personalization check, wherein the set of mobile virtual network operator identifiers are obtained based at least in part on performing the device personalization check.

30. The non-transitory computer-readable medium of claim 27, wherein the instructions to communicate with the radio access network are executable by the one or more processors to: transmit, to the radio access network, an indication of the one or more identifiers; and establish a communication link with the radio access network based at least in part on transmitting the indication of the one or more identifiers.

Images