Network Interface Management for Citizens Broadband Radio Service

Apparatuses, systems, and methods for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond, including methods for coarse selection of CBRS networks and fine selection of CBRS networks as well as support for multiple CBRS networks. Coarse selection of CBRS networks may include various triggers for automatic CBRS profile enabling and/or disabling, user management and overriding of system selections, tiered hierarchy for CBRS network enabling and/or disabling, as well as mechanisms to avoid ping-ponging between network selection. Fine selection of CBRS networks may include data slot switching between mobile network operators (MNOs, e.g., LTE/NR macro cells) and CBRS eSIM as well as prioritization of CBRS networks over Wi-Fi networks. Multiple CBRS networks support may include CBRS network identifier (NID) matching for unique identification as well as user-ranked CBRS priority.

FIELD

The invention relates to wireless communications, and more particularly to apparatuses, systems, and methods for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities.

Long Term Evolution (LTE) is currently the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. Thus, in2015study of a new radio access technology began and, in2017, a first release of Fifth Generation New Radio (5G NR) was standardized.

5G-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption. Further, NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.

Additionally, rapid spread and use of wireless communications has led to an ever-increasing deployment of distributed antenna systems (DAS). Driven in part by rising bandwidth requirements and quality of service expectations, the deployment and maintenance of today's advanced DAS has experienced a steady cost increase. For many years, auctioned licensed spectrum allocations statewide and nationwide were exclusively acquired by Tier-1 cellular carriers as it proved too expensive for Tier-2/Tier-3 carriers and other potential local operators. Tier-1 carriers were thereby able to use the allocated spectrum as a strategic asset for 3GPP technologies (e.g., LTE and/or NR), which has proven to be a barrier to innovation in wireless services as well as slowing down service improvements. For example, deployment has been focused on Tier-1 venues, leaving Tier-2/Tier-3 venues and indoor venues with poor coverage. Tier-2/Tier-3 network operators, enterprises, small communities and venue owners cannot acquire spectrum that would allow them to improve the wireless coverage in Tier-2/Tier-3 venues and indoor private buildings, which slows the densification and installation of small cells.

For at least the above reasons, the wireless industry as a whole has been pursuing a variety of service delivery models designed to offset these high costs while ensuring reliable and profitable in-building coverage and capacity. One particular DAS that has received much attention is the neutral host DAS, or neutral host for short. A neutral host shifts the ownership of the system from a carrier to either a building owner, DAS integrator or a third-party system provider. Present day DAS system deployments, e.g., in enterprise buildings, have proven to be extremely expensive due to the required installation of Tier-1 carrier equipment for operating in the carrier's licensed spectrum. Under the neutral host model, the independent third-party host assumes all financial, regulatory, legal and technical responsibility for deploying, installing and maintaining the system. The host may lease space or access to the system to one or more operators. The neutral host model provides a number of attractive benefits, chief among them the increased number of providers who are able and willing to help satisfy the growing demand in the market. To facilitate the installation, reduce the cost, and simplify the process and spread of effective neutral hosts, a new Citizens Broadband Radio Service (CBRS) for shared wireless broadband use of the 3550-3700 MHz band (3.5 GHz Band) was established. CBRS provides potential benefits of indoor and outdoor cellular services, e.g., LTE/NR services within a shared 3.5 GHz spectrum by opening up those bands for commercial use such as carrier-based cellular service extensions and private LTE/NR networks within enterprises, sports stadiums and conference centers, among others. Such services promise to complement, and in some cases possibly replace Wi-Fi, in addition to paving the way for 5G/NR wireless services. In other words, CBRS band(s) can be used by cellular networks to provide private LTE/NR and neutral host networks (e.g., Wi-Fi Type deployments in buildings and enterprises) using LTE or NR small cells and networks.

The welcome addition of these new wireless services also raises new issues. Devices are expected to recognize and efficiently connect with and operate on these new wireless networks. In addition, improved device mobility is required to allow devices to seamlessly move from operating on one wireless service to operating on another wireless service.

SUMMARY

Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond.

For example, embodiments include methods for coarse selection of CBRS networks and fine selection of CBRS networks as well as support for multiple CBRS networks. Coarse selection of CBRS networks may include various triggers for automatic CBRS profile enabling and/or disabling, user management and overriding of system selections, tiered hierarchy for CBRS network enabling and/or disabling, as well as mechanisms to avoid ping-ponging between network selection. Fine selection of CBRS networks may include data slot switching between mobile network operators (MNOs, e.g., LTE/NR macro cells) and CBRS eSIM as well as prioritization of CBRS networks over Wi-Fi networks. Multiple CBRS networks support may include CBRS network identifier (NID) matching for unique identification as well as user-ranked CBRS priority.

The techniques described herein may be implemented in and/or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), a UTM server, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

DETAILED DESCRIPTION

Acronyms

Various acronyms are used throughout the present disclosure. Definitions of the most prominently used acronyms that may appear throughout the present disclosure are provided below:3GPP: Third Generation Partnership ProjectUE: User EquipmentRF: Radio FrequencyBS: Base StationDL: DownlinkUL: UplinkLTE: Long Term EvolutionNR: New RadioCBRS: Citizens Broadband Radio ServiceDAS: Distributed Antenna System5GS: 5G System5GMM: 5GS Mobility Management5GC/5GCN: 5G Core NetworkSIM: Subscriber Identity ModuleeSIM: Embedded Subscriber Identity ModuleIE: Information ElementCE: Control ElementMAC: Medium Access ControlSSB: Synchronization Signal BlockCSI-RS: Channel State Information Reference SignalPDCCH: Physical Downlink Control ChannelPDSCH: Physical Downlink Shared ChannelRRC: Radio Resource ControlRRM: Radio Resource ManagementCORESET: Control Resource SetTCI: Transmission Configuration IndicatorDCI: Downlink Control Indicator

Terms

User Equipment (UE) (or “UE Device”)— any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™ Play Station Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

3GPP Access—refers to accesses (e.g., radio access technologies) that are specified by 3GPP standards. These accesses include, but are not limited to, GSM/GPRS, LTE, LTE-A, and/or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.

Non-3GPP Access—refers any accesses (e.g., radio access technologies) that are not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and/or fixed networks. Non-3GPP accesses may be split into two categories, “trusted” and “untrusted”: Trusted non-3GPP accesses can interact directly with an evolved packet core (EPC) and/or a 5G core (5GC) whereas untrusted non-3GPP accesses interwork with the EPC/5GC via a network entity, such as an Evolved Packet Data Gateway and/or a 5G NR gateway. In general, non-3GPP access refers to various types on non-cellular access technologies.

FIG.1Aillustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system ofFIG.1Ais merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

The base station (BS)102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs106A through106N.

As shown, the base station102A may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102A may facilitate communication between the user devices and/or between the user devices and the network100. In particular, the cellular base station102A may provide UEs106with various telecommunication capabilities, such as voice, SMS and/or data services.

In some embodiments, base station102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

FIG.1Billustrates user equipment106(e.g., one of the devices106A through106N) in communication with a base station102and an access point112, according to some embodiments. The UE106may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

FIG.2: Block Diagram of a Base Station

FIG.2illustrates an example block diagram of a base station102, according to some embodiments. It is noted that the base station ofFIG.3is merely one example of a possible base station. As shown, the base station102may include processor(s)204which may execute program instructions for the base station102. The processor(s)204may also be coupled to memory management unit (MMU)240, which may be configured to receive addresses from the processor(s)204and translate those addresses to locations in memory (e.g., memory260and read only memory (ROM)250) or to other circuits or devices.

The base station102may include at least one network port270. The network port270may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices106, access to the telephone network as described above inFIGS.1and2.

The base station102may include at least one antenna234, and possibly multiple antennas. The at least one antenna234may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices106via radio230. The antenna234communicates with the radio230via communication chain232. Communication chain232may be a receive chain, a transmit chain or both. The radio230may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

As described further subsequently herein, the BS102may include hardware and software components for implementing or supporting implementation of features described herein. The processor204of the base station102may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor204may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor204of the BS102, in conjunction with one or more of the other components230,232,234,240,250,260,270may be configured to implement or support implementation of part or all of the features described herein.

In addition, as described herein, processor(s)204may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s)204. Thus, processor(s)204may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)204.

Further, as described herein, radio230may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio230. Thus, radio230may include one or more integrated circuits (ICs) that are configured to perform the functions of radio230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio230.

FIG.3: Block Diagram of a Server

FIG.3illustrates an example block diagram of a server104, according to some embodiments. It is noted that the server ofFIG.3is merely one example of a possible server. As shown, the server104may include processor(s)344which may execute program instructions for the server104. The processor(s)344may also be coupled to memory management unit (MMU)374, which may be configured to receive addresses from the processor(s)344and translate those addresses to locations in memory (e.g., memory364and read only memory (ROM)354) or to other circuits or devices.

The server104may be configured to provide a plurality of devices, such as base station102, UE devices106, and/or UTM108, access to network functions, e.g., as further described herein.

In some embodiments, the server104may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server104may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.

As described further subsequently herein, the server104may include hardware and software components for implementing or supporting implementation of features described herein. The processor344of the server104may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor344may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor344of the server104, in conjunction with one or more of the other components354,364, and/or374may be configured to implement or support implementation of part or all of the features described herein.

In addition, as described herein, processor(s)344may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s)344. Thus, processor(s)344may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)344.

FIG.4: Block Diagram of a UE

FIG.4illustrates an example simplified block diagram of a communication device106, according to some embodiments. It is noted that the block diagram of the communication device ofFIG.4is only one example of a possible communication device. According to embodiments, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and/or a combination of devices, among other devices. As shown, the communication device106may include a set of components400configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components400may be implemented as separate components or groups of components for the various purposes. The set of components400may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device106.

For example, the communication device106may include various types of memory (e.g., including NAND flash410), an input/output interface such as connector I/F420(e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display460, which may be integrated with or external to the communication device106, and cellular communication circuitry430such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry429(e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device106may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

The cellular communication circuitry430may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas435and436as shown. The short to medium range wireless communication circuitry429may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas437and438as shown. Alternatively, the short to medium range wireless communication circuitry429may couple (e.g., communicatively; directly or indirectly) to the antennas435and436in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas437and438. The short to medium range wireless communication circuitry429and/or cellular communication circuitry430may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

The communication device106may further include one or more smart cards445that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards445, one or more eUICCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE106may include at least two SIMs. Each SIM may execute one or more SIM applications and/or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE106, or each SIM410may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and/or the SIMs410may be one or more embedded cards (such as embedded UICCs (eUICCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUICC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMS may include components such as a processor and/or a memory; instructions for performing SIM/eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE106may include a combination of removable smart cards and fixed/non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality), as desired. For example, the UE106may comprise two embedded SIMs, two removable SIMS, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

As noted above, in some embodiments, the UE106may include two or more SIMs. The inclusion of two or more SIMs in the UE106may allow the UE106to support two different telephone numbers and may allow the UE106to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM410support a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the UE106comprises two SIMs, the UE106may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE106to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE106to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and/or voice over NR (VoNR) technology. In some embodiments, the UE106may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE106to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and/or RATs.

As shown, the SOC400may include processor(s)402, which may execute program instructions for the communication device106and display circuitry404, which may perform graphics processing and provide display signals to the display460. The processor(s)402may also be coupled to memory management unit (MMU)440, which may be configured to receive addresses from the processor(s)402and translate those addresses to locations in memory (e.g., memory406, read only memory (ROM)450, NAND flash memory410) and/or to other circuits or devices, such as the display circuitry404, short to medium range wireless communication circuitry429, cellular communication circuitry430, connector I/F420, and/or display460. The MMU440may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU440may be included as a portion of the processor(s)402.

As noted above, the communication device106may be configured to communicate using wireless and/or wired communication circuitry. The communication device106may be configured to perform methods for revocation and/or modification of user consent in MEC, e.g., in LTE and/or 5G NR systems and beyond, as further described herein.

As described herein, the communication device106may include hardware and software components for implementing the above features for a communication device106to communicate a scheduling profile for power savings to a network. The processor402of the communication device106may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor402may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor402of the communication device106, in conjunction with one or more of the other components400,404,406,410,420,429,430,440,445,450,460may be configured to implement part or all of the features described herein.

In addition, as described herein, processor402may include one or more processing elements. Thus, processor402may include one or more integrated circuits (ICs) that are configured to perform the functions of processor402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)402.

Further, as described herein, cellular communication circuitry430and short to medium range wireless communication circuitry429may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry430and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry429. Thus, cellular communication circuitry430may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry430. Similarly, the short to medium range wireless communication circuitry429may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry429.

FIG.5: Block Diagram of Cellular Communication Circuitry

The cellular communication circuitry530may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas435a-band436as shown (inFIG.4). In some embodiments, cellular communication circuitry530may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown inFIG.5, cellular communication circuitry530may include a modem510and a modem520. Modem510may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem520may be configured for communications according to a second RAT, e.g., such as 5G NR.

In some embodiments, a switch570may couple transmit circuitry534to uplink (UL) front end572. In addition, switch570may couple transmit circuitry544to UL front end572. UL front end572may include circuitry for transmitting radio signals via antenna336. Thus, when cellular communication circuitry530receives instructions to transmit according to the first RAT (e.g., as supported via modem510), switch570may be switched to a first state that allows modem510to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry534and UL front end572). Similarly, when cellular communication circuitry530receives instructions to transmit according to the second RAT (e.g., as supported via modem520), switch570may be switched to a second state that allows modem520to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry544and UL front end572).

In some embodiments, the cellular communication circuitry530may be configured to perform methods for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond, as further described herein.

As described herein, the modem510may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors512may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor512may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor512, in conjunction with one or more of the other components530,532,534,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors512may include one or more processing elements. Thus, processors512may include one or more integrated circuits (ICs) that are configured to perform the functions of processors512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors512.

As described herein, the modem520may include hardware and software components for implementing the above features for communicating a scheduling profile for power savings to a network, as well as the various other techniques described herein. The processors522may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor522may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor522, in conjunction with one or more of the other components540,542,544,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors522may include one or more processing elements. Thus, processors522may include one or more integrated circuits (ICs) that are configured to perform the functions of processors522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors522.

In some embodiments, the 5G core network (CN) may be accessed via (or through) a cellular connection/interface (e.g., via a 3GPP communication architecture/protocol) and a non-cellular connection/interface (e.g., a non-3GPP access architecture/protocol such as Wi-Fi connection).FIG.6Aillustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB604, which may be a base station102) and an access point, such as AP612. The AP612may include a connection to the Internet600as well as a connection to a non-3GPP interworking function (N3IWF)603network entity. The N3IWF may include a connection to a core access and mobility management function (AMF)605of the 5G CN. The AMF605may include an instance of a 5G mobility management (5G MM) function associated with the UE106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE106access via both gNB604and AP612. As shown, the AMF605may include one or more functional entities associated with the 5G CN (e.g., network slice selection function (NSSF)620, short message service function (SMSF)622, application function (AF)624, unified data management (UDM)626, policy control function (PCF)628, and/or authentication server function (AUSF)630). Note that these functional entities may also be supported by a session management function (SMF)606aand an SMF606bof the 5G CN. The AMF605may be connected to (or in communication with) the SMF606a. Further, the gNB604may in communication with (or connected to) a user plane function (UPF)608athat may also be communication with the SMF606a. Similarly, the N3IWF603may be communicating with a UPF608bthat may also be communicating with the SMF606b. Both UPFs may be communicating with the data network (e.g., DN610aand610b) and/or the Internet600and Internet Protocol (IP) Multimedia Subsystem/IP Multimedia Core Network Subsystem (IMS) core network610.

FIG.6Billustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB604or eNB602, which may be a base station102) and an access point, such as AP612. The AP612may include a connection to the Internet600as well as a connection to the N3IWF603network entity. The N3IWF may include a connection to the AMF605of the 5G CN. The AMF605may include an instance of the 5G MM function associated with the UE106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE106access via both gNB604and AP612. In addition, the 5G CN may support dual-registration of the UE on both a legacy network (e.g., LTE via eNB602) and a 5G network (e.g., via gNB604). As shown, the eNB602may have connections to a mobility management entity (MME)642and a serving gateway (SGW)644. The MME642may have connections to both the SGW644and the AMF605. In addition, the SGW644may have connections to both the SMF606aand the UPF608a. As shown, the AMF605may include one or more functional entities associated with the 5G CN (e.g., NSSF620, SMSF622, AF624, UDM626, PCF628, and/or AUSF630). Note that UDM626may also include a home subscriber server (HSS) function and the PCF may also include a policy and charging rules function (PCRF). Note further that these functional entities may also be supported by the SMF606aand the SMF606bof the 5G CN. The AMF606may be connected to (or in communication with) the SMF606a. Further, the gNB604may in communication with (or connected to) the UPF608athat may also be communication with the SMF606a. Similarly, the N3IWF603may be communicating with a UPF608bthat may also be communicating with the SMF606b. Both UPFs may be communicating with the data network (e.g., DN610aand610b) and/or the Internet600and IMS core network610.

Note that in various embodiments, one or more of the above-described network entities may be configured to perform methods to improve security checks in a 5G NR network, including mechanisms for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond, e.g., as further described herein.

FIG.7illustrates an example of a baseband processor architecture for a UE (e.g., such as UE106), according to some embodiments. The baseband processor architecture700described inFIG.7may be implemented on one or more radios (e.g., radios429and/or430described above) or modems (e.g., modems510and/or520) as described above. As shown, the non-access stratum (NAS)710may include a 5G NAS720and a legacy NAS750. The legacy NAS750may include a communication connection with a legacy access stratum (AS)770. The 5G NAS720may include communication connections with both a 5G AS740and a non-3GPP AS730and Wi-Fi AS732. The 5G NAS720may include functional entities associated with both access stratums. Thus, the 5G NAS720may include multiple 5G MM entities726and728and 5G session management (SM) entities722and724. The legacy NAS750may include functional entities such as short message service (SMS) entity752, evolved packet system (EPS) session management (ESM) entity754, session management (SM) entity756, EPS mobility management (EMM) entity758, and mobility management (MM)/GPRS mobility management (GMM) entity760. In addition, the legacy AS770may include functional entities such as LTE AS772, UMTS AS774, and/or GSM/GPRS AS776.

Thus, the baseband processor architecture700allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that as shown, the 5G MM may maintain individual connection management and registration management state machines for each connection. Additionally, a device (e.g., UE106) may register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. Further, it may be possible for the device to be in a connected state in one access and an idle state in another access and vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, de-registration, identification, authentication, as so forth) for both accesses.

Note that in various embodiments, one or more of the above-described functional entities of the 5G NAS and/or 5G AS may be configured to perform methods for network interface management for Citizens Broadband Radio Service (CBRS) deployments, e.g., in LTE and/or 5G NR systems and beyond, e.g., as further described herein.

Network Interface Management for CBRS

In current implementations, Citizens Broadband Radio Service (CBRS) is defined as a shared spectrum radio access technology (RAT) at 3550-3700 megahertz (MHz) with 3 tiers. A first tier, which receives highest priority in the CBRS shared spectrum, is reserved for military and/or government radio, however, the first tier is rarely in use and/or used. The second tier includes 10 MHz bands licensed to enterprises. The third tier is open access for anyone, however, priority is given to higher tiers as needed/required. Given the free access to the third tier, private CBRS networks have become economically feasible on a commercial level with theoretical performance of CBRS (e.g., such as CBRS LTE) significantly better than Wi-Fi and/or Macro-cell. Additionally, CBRS cells have a limited range which leads to reduced interference as well as allowance for targeted deployments. For example, a warehouse may install a private CBRS for workers to camp on, providing higher bandwidth than previous Wi-Fi networks. As another example, an enterprise may offer employees confidential material only on its CBRS private network to decrease the probability of information leak over the internet. As a further example, a stadium may turn on a CBRS station whenever the stadium is in use (concert, sporting event, and so forth), e.g., to alleviate high demand of data locally during the period of time of an event. However, the availability of these various CBRS private networks requires improved device mobility, e.g., to allow devices to seamlessly move from operating on one wireless service to operating on another wireless service (e.g., from NR/LTE to Wi-Fi to CBRS and the like).

Embodiments described herein provide systems, methods, and mechanisms to support network interface management for Citizens Broadband Radio Service (CBRS) deployments, including systems, methods, and mechanisms for coarse selection of CBRS networks and fine selection of CBRS networks as well as support for multiple CBRS networks. For example, systems, methods, and mechanisms for coarse selection of CBRS networks may include various triggers for automatic CBRS profile enabling and/or disabling, user management and overriding of system selections, tiered hierarchy for CBRS network enabling and/or disabling, as well as mechanisms to avoid ping-ponging between network selection. As another example, systems, methods, and mechanisms for fine selection of CBRS networks may include data slot switching between mobile network operators (MNOs, e.g., LTE/NR macro cells) and CBRS eSIM as well as prioritization of CBRS networks over Wi-Fi networks. As a further example, systems, methods, and mechanisms for multiple CBRS networks support may include CBRS network identifier (NID) matching for unique identification as well as user-ranked CBRS priority.

As indicated above, in some embodiments, coarse selection may include multiple triggers for automatic CBRS profile enabling and/or CBRS profile disabling. For example, badging into/out of an office space (e.g., such as an office building) may automatically enable and/or disable a corresponding CBRS profile. As another example, camping on/off a Wi-Fi network that is deployed near a CBRS network may automatically enable/disable a CBRS profile corresponding to the CBRS network. Further, entering/exiting a geofence may cause automatic enabling/disabling of a CBRS profile corresponding to a CBRS network associated with the geofence. Additionally, signal loss may cause automatic disabling of a CBRS profile associated with a CBRS network for which the signal has been lost.

Additionally, as indicated above, in some embodiments, coarse selection may also and/or alternatively include user management and overriding of system selections. For example, a user may manually select a CBRS profile to activate, e.g., via a user interface (UI). Note that such a selection may be higher priority than most system triggers. Similarly, a user may manually disable a CBRS profile(s). Note that once disabled, the CBRS profile(s) may be placed on a deny list which may lead to system triggers associated with the disabled CBRS profile(s) being ignored for at least a period of time.

Further, as indicated above, in some embodiments, coarse selection may also and/or alternatively include a tiered hierarchy for CBRS network/profile enabling and/or disabling. For example, a user selection of a CBRS network and/or profile may be given a highest (or first) priority, e.g., geofence, WiFi, and/or badging triggers cannot cause a user-enabled CBRS network/profile to be turned off. Further, geofence may be given a second highest (or second) priority, e.g., geofence enabling/disabling of a CBRS network/profile may override WiFi and/or badging triggers for automatic enabling/disabling of a CBRS network/profile. Additionally, WiFi and/or badging may have a lowest (or third) priority, e.g., WiFi and/or badging may be considered indicators of geofence locations, thus, WiFi triggers may be ignored if and/or when a CBRS network/profile is active due to user selection or geofence trigger. Note that in an absence of location services, machine learning may be used to enable more accurate predictions.

In addition, as indicated above, in some embodiments, coarse selection may also and/or alternatively include mechanisms to avoid ping-ponging between network selection. For example, a trigger of sufficient priority (e.g., higher priority than a trigger used to select a current CBRS network/profile) may cause a stable state timer to be reset. Then, a decision to enable and/or disable a CBRS network/profile may only be evaluated after a stable state is reached and/or when the stable state timer finishes a countdown without reset. Note that such a mechanism may prevent energy drain and service disruptions from frequent enabling and/or disabling of CBRS networks/profiles.

As indicated above, in some embodiments, fine selection may include data slot switching between mobile network operators (MNOs) (e.g., LTE/NR macro cells) and CBRS eSIM. For example, a radio access arbitrator may monitor a variety (e.g., a plurality) of signal quality indicators of MNO and CBRS connections. Additionally, the radio access arbitrator may send data SIM recommendation to a CBRS xontroller, e.g., based on the monitoring of the signal quality indicators of the MNO connection and the CBRS connection. Further, the CBRS controller may consider radio access arbitrator recommendations along with carrier policies and user preferences to select an appropriate eSIM for data. In other words, eSIM selection for data traffic may be based, at least in part, on one or more of signal quality indicators of the MNO connection and the CBRS connection, carrier policies, and/or user preferences.

In addition, as indicated above, in some embodiments, fine selection may also or alternatively include prioritization of CBRS networks over Wi-Fi networks. For example, a radio access arbitrator may monitor signal quality indicators for a WiFi connection as well as signal quality indicators of an MNO connection and a CBRS connection. The radio access arbitrator may compare the signal quality indicators for the WiFi connection to the signal quality indicators of the MNO connection and the CBRS connection. Then, if and/or when the WiFi connection, based on the comparison, is the best connection for data (e.g., as compared to the MNO connection and/or the CBRS connection), the radio access arbitrator may signal a WiFi preference over cellular to a network layer, thus the MNO connection and the CBRS connection may be ignored since both are cellular connections. Further, if and/or when the MNO connection, based on the comparison, is the best connection for data (e.g., as compared to the WiFi connection and/or the CBRS connection), the radio access arbitrator may signal cellular preference over WiFi to the network layer and an MNO preference over CBRS to a CBRS controller. Additionally, if and/or when the CBRS connection, based on the comparison, is the best connection for data (e.g., as compared to the MNO connection and/or the WiFi connection), the radio access arbitrator may signal cellular preference over WiFi to the network layer and an CBRS preference over MNO to a CBRS controller.

Additionally, as indicated above, in some embodiments, multiple CBRS networks support may include CBRS NID matching for unique identification. For example, each CBRS deployment may have a unique NID which is included in geofencing data and/or a CBRS profile associated with the CBRS deployment. Coarse selection may consider the CBRS NID when enabling a CBRS profile (e.g., a CBRS profile with a NID associated with one location or entity will not be enabled when entering a geofence for a NID associated with another location or entity).

Further, as indicated above, in some embodiments, multiple CBRS network support may include user-ranked CBRS priority. For example, upon installing a new CBRS profile, a user may be asked to rank the new CBRS profile against other existing CBRS profiles. Then, automatic activation may prefer a highest-ranked CBRS profile first, e.g., if and/or when automatic activation conditions for multiple CBRS profiles are simultaneously triggered.

FIG.8illustrates an example of signaling for provisioning of one or more CBRS profiles, according to some embodiments. The signaling shown inFIG.8may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

At830, a CBRS network802, e.g., a base station and/or access point of the CBRS network802, may send and/or provide CBRS geofence data830to an operator portal808, e.g., a server of an operator of the CBRS network. The geofence data830may include various information associated with the location of the CBRS network802, e.g., such as coordinates of boundary locations, a network name, a base station identifier (ID) and/or name, a band and/or Absolute Radio Frequency Channel (ARFCN), Shared Home. Network Identifier (SHNI) and/or Public Land Mobile Network (PLMN) ID, tracking area code (TAC), cell ID, CBRS network ID (NID), latitude, longitude, altitude, radius, and/or a list of co-located WiFi Service Set Identifiers (SSIDs), among other information. Note that the operator portal808may be a third party server, e.g., such as a server104.

Then, the operator portal808may send and/or provide the geofence data to a geofencing data server804, e.g., via a load geofencing data operation832. Thus, the operator portal808may provide the geofencing data server804with the CBRS geofence data830received from CBRS network802.

Further, a CBRS controller812of a UE, such as UE106, may retrieve CBRS geofence data from the geofencing data server804. Note that the particular CBRS geofence data retrieved from the geofencing data server804may be based, at least in part, on an installed CBRS profile and/or installed CBRS profiles on an eSIM of the UE. In such a manner, one or more CBRS profiles may be provisioned for use by the UE.

FIGS.9A and9Billustrate an example of signaling for selection of a CBRS network based on one or more provisioned CBRS profiles, according to some embodiments. The signaling shown inFIGS.9A and9Bmay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

A CBRS controller812, once provisioned with one or more CBRS profiles, e.g., as described above with reference toFIG.8, may configure a geofence location, e.g., based on the geofence data received from the geofence server804. Thus, the CBRS controller812may configure a geofence with location module820of a UE, such as UE106, based on provisioned CBRS profiles, via geofence configure operation902. Thus, the location module820may be configured to detect entry and exit from a geofence associated with provisioned CBRS profiles.

Then, upon detection of an entry into a geofence associated with a provisioned CBRS profile, the location module820may notify the CBRS controller812of geofence entry (e.g., geofence entry detection904).

At906, CBRS controller812may perform coarse selection, e.g., as further described below in reference toFIGS.14,15A, and15B. For example, CBRS controller812may monitor for various triggers for automatic CBRS profile enabling and/or disabling, perform user management and overriding of system selections, and implement tiered hierarchy for CBRS network enabling and/or disabling, as well as implement mechanisms to avoid ping-ponging between network selections.

After performing coarse selection906, CBRS controller812may enable a selected CBRS profile by notifying eSIM816(e.g., a baseband eSIM of UE106) via enable CBRS eSIM message908.

Further, CBRS controller812may configure a band scan, e.g., based on the provisioned CBRS profile (e.g., based on the geofence data included in the provisioned CBRS profile) and notify a baseband network access stratum (NAS) layer of the UE (e.g., NAS818) of the configuration via configure scan message910.

At912, NAS818may perform a band scan, e.g., based on the configuration received from CBRS controller812. Then, based on the band scan, NAS818may perform network attachment914.

Further, a radio access arbitrator (e.g., RAA814) of UE106may receive WiFi signal quality metrics916from WiFi layer822of UE106as well as CBRS signal quality metrics and MNO signal quality metrics918from NAS818.

At920, RAA814may perform fine selection, e.g., as further described in reference toFIG.16. For example, RAA814may perform data slot switching between MNOs (e.g., LTE/NR macro cells) and CBRS eSIM as well as prioritization of CBRS networks over Wi-Fi networks. Then, based on the fine selection, RAA814may send recommendation922to CBRS controller812. The recommendation922may indicate whether to use an MNO or the CBRS profile.

Continuing toFIG.9B, based on the recommendation (e.g., when the recommendation indicates to use the CBRS profile), CBRS controller812may send a command924to NAS818to switch data to CBRS. Additionally, CBRS controller812may send a command926to networking layer824of UE106to prefer cellular over WiFi.

Location module820may monitor the location of UE106in comparison to the geofence associated with the CBRS profile in use. Upon detection of an exit from the geofence area, location module820may send a notification928to CBRS controller812indicating exit from the geofence. Based on the notification, CBRS controller812may send a command930to eSIM816disabling the CBRS profile in use. Further, based on the notification, CBRS controller812may send a command932to NAS818to switch data to MNO. Finally, based on the notification, CBRS controller812may send a command932to WiFi layer822to prefer WiFi over cellular for data transmission.

FIG.10illustrates an example of a block diagram of a method for a CBRS controller to perform various operations, according to some embodiments. The method shown inFIG.10may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

CBRS controller812may receive inputs from various components/layers of a UE, such as UE106, and may perform and/or command various actions based on the inputs e.g., as described above in reference toFIGS.9A-9B. For example, at1010, CBRS controller812may receive WiFi connection information (e.g., such as signal quality metrics of received WiFi signals). At1012, CBRS controller812may receive internet status (e.g., active sessions, connection status, and so forth). At1014, CBRS controller812may receive carrier features (e.g., CBRS features supported by a MNO, e.g., from a carrier server). At1016, CBRS controller812may receive eSIM information (e.g., such as available/disabled CBRS profiles, active CBRS profile). At1018, CBRS controller812may receive network connectivity information (e.g., bands and network types available for connection). At1020, CBRS controller812may receive geofence information (e.g., such as entry and/or exit from a geofence area/location). At1022, CBRS controller812may receive radio access arbitrator (RAA) recommendations (e.g., data slot recommendations). At1024, CBRS controller812may receive user preferences (e.g., user selections associated with CBRS). Further, based on the received inputs, CBRS controller812may perform and/or command various actions. For example, at1030, CBRS controller812may fetch server data (e.g., to update one or more CBRS profiles). At1032, CBRS controller812may perform geofence configuration (e.g., based on available CBRS profiles). At1034, CBRS controller812may enable a CBRS profile (e.g., based on WiFi, geofence detection, and/or user preference). At1036, CBRS controller812may disable a CBRS profile (e.g., based on WiFi, geofence detection, registration status, and/or user preference). At1038, CBRS controller812may enable optimizations. At1040, CBRS controller812may disable optimizations.

Note that in addition to retrieving and/or fetching geofence data from various servers such as a geofencing server (e.g., a central server or a server identifiable via a network ID), a private server (e.g., a central server hosted by a UE manufacturer) or an entitlement server (e.g., a server hosted by an MNO), a UE, e.g., a CBRS controller of a UE, may receive geofence data via a mobile device management (MDM) command, an installation of a configuration profile, embedded carrier configuration files, and/or a public application.FIGS.11,12A,12B,13A, and13Billustrate various methods for CBRS profile retrieval from a server as well as methods for updating a server of CBRS profile changes.

FIG.11illustrates an example of a block diagram of a method for a CBRS profile change or update, according to some embodiments. The method shown inFIG.11may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1102, a UE, such as UE106, may detect a CBRS profile and/or at1104, the UE may determine that a CBRS profile has expired and/or that the UE has received a command to update the CBRS profile (e.g., a forced update).

At1106, in response to detecting the CBRS profile, the UE may determine whether the CBRS profile has changed.

At1108, in response to determining that the CBRS profile has not changed, the UE may determine whether the CBRS profile has expired.

At1110, in response to determining that the CBRS profile has not changed, the UE may take no action regarding the CBRS profile.

At1112, in response to determining that the CBRS profile has changed and/or in response to determining that a CBRS profile has expired and/or that the UE has received a command to update the CBRS profile, the UE may determine whether a carrier (e.g., via query to an entitlements server of the carrier) supports geofence data.

At1114, in response to determining that the carrier supports geofence data, the UE may fetch and/or retrieve the geofence data from the carrier.

At1116, in response to determining that the carrier does not support geofence data, the UE may fetch and/or retrieved the geofence data from a server hosted by a manufacturer of the UE.

FIG.12Aillustrates an example of a block diagram of a method for on device learning of geofence data, according to some embodiments. The method shown inFIG.12Amay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1202, a UE, such as UE106may enter a known CBRS region. For example, the UE may detect entry into a geofence location of a known CBRS region.

At1204, the UE may be requested (e.g., by an MNO or some other entity) to verify the CBRS region.

At1206, the UE may attempt to verify the CBRS region.

At1208, in response to verifying the CBRS region, the UE may send a confirmation to a server.

Alternatively, at1210, the UE may be requested to scan for a CBRS region, e.g., based on a current location of the UE.

At1212, in response to the request to scan for the CBRS region, the UE may determine whether a new CBRS region has been located.

At1214, in response to not locating a new CBRS, the UE may take no further action.

Alternatively, at1216, in response to locating a new CBRS and/or in response to not verifying the CBRS region (e.g., at1206), the UE may send updated CBRS information to the sever.

FIG.12Billustrates an example of a block diagram of a method for updating a geofence server based on device learning of geofence data, according to some embodiments. The method shown inFIG.12Bmay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1220, a server, such as server104, may receive, from a UE, such as UE106, updated CBRS information.

At1222, the server may determine whether the updated CBRS information matches any CBRS information stored on the server.

At1224, in response to determining a match, the sever may take no further action.

Alternatively, at1226, in response to determining that there is not a match, the server may record (e.g., store) the updated CBRS information.

FIG.13Aillustrates an example of a block diagram of a method for crowd sourced updates of geofence data, according to some embodiments. The method shown inFIG.13Amay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1302, a UE, such as UE106may enter a possible CBRS region. For example, the UE may detect entry into a geofence location of a possible CBRS region. Further, based on location of the UE, the UE may be requested (e.g., randomly) to scan for a CBRS network.

Alternatively, at1304, a user of the UE may detect a CBRS network (either in band or out of band).

At1306, the UE may determine whether the UE supports CBRS.

At1308, in response to determining that the UE supports CBRS and/or in response to a request to scan for the CBRS network, the UE may scan for the CBRS network.

At1310, the UE may determine whether the scan found a CBRS network and/or whether the found CBRS network matches the identified CBRS network and/or possible CBRS network.

At1312, in response to determining that the scan found the CBRS network and/or that the found CBRS network matches the identified CBRS network and/or possible CBRS network, the UE may send a confirmation to a server.

Alternatively, at1314, in response to determining that the scan did not find the CBRS network and/or did not find that the CBRS network matches the identified CBRS network and/or possible CBRS network, the UE may take no further action.

Additionally, at1316, in response to determining that the UE does not support CBRS, the UE may send the possible CBRS network to the server.

FIG.13Billustrates an example of a block diagram of a method for updating a geofence server based on crowd sourced geofence data, according to some embodiments. The method shown inFIG.13Bmay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1320, a server, such as server104, may receive, from a UE, such as UE106, a confirmation of CBRS network location.

Alternatively, at1322, the server may receive, from the UE, an indication of a possible CBRS network location.

At1324, the server may compare the possible CBRS network location to CBRS network locations stored on the server.

At1326, in response to receiving the confirmation of CBRS network location and/or in response to determining that the possible CBRS network location matches a CBRS network location stored on the server, the server may store the CBRS information in a confirmed network pool (e.g., a data structure containing confirmed CBRS information).

Alternatively, at1328, in response to determining that the possible CBRS network location does not match a CBRS network location stored on the server, the server may store the CBRS information in a possible network pool (e.g., a data structure containing possible (e.g., unconfirmed) CBRS information). Note that data in the possible network pool may be removed periodically if not confirmed by another UE within a specified period of time.

FIG.14illustrates an example of a block diagram of a method for avoiding rapid switching (e.g., ping-ponging) between enabling and/or disabling a CBRS profile, according to some embodiments. The method shown inFIG.14may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1402, a trigger condition associated with CBRS profile enablement/disablement may be detected, e.g., by a UE and/or by a CBRS controller of a UE. The trigger condition may be based on UE mobility state and/or a type of trigger. In some embodiments, trigger conditions to disable a CBRS profile may include the UE stopping camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging out of a location (e.g., office), the UE exiting a geofence location, a user of the UE turning of CBRS, and/or a loss of a CBRS signal. In some embodiments, trigger conditions to enable a CBRS profile may include the UE camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging into a location (e.g., office), the UE entering a geofence location, and/or a user turning on CBRS. Note that any trigger of sufficient priority may cause entry into the method (e.g., algorithm). Note further that trigger conditions may be prioritized base on trigger type. For example, a user generated trigger condition may be given a highest priority whereas a WiFi/badge associated trigger condition may be given a lowest priority. Further, a geofence associated trigger condition may be given a priority between the highest priority and the lowest priority.

At1404, the UE may determine whether the trigger was user generated.

At1406, in response to determining that the trigger was user generated, the UE may apply a user action associated with the trigger condition.

At1408, in response to determining that the trigger was not user generated, the UE may wait for a specified time period, e.g., a hysteresis timer.

At1410, the UE may determine whether the trigger condition persists (e.g., remains).

At1412, in response to determining that the trigger condition persists, the UE may perform a CBRS update (e.g., CBRS profile enablement/disablement) based on the trigger condition.

At1414, in response to determining that the trigger condition does not persist, the UE may take no further action. In this manner, the UE may avoid energy drain and/or service disruptions associated with frequent CBRS profile enablement/disablement.

In some embodiments, an action that the UE takes resulting from the trigger condition may depend on a previous CBRS state. For example, when a trigger condition attempts to disable a CBRS profile, the triggering condition will be ignored when the previous CBRS state is inactive. As another example, when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was WiFi enabled/badge enabled, the UE may enter the hysteresis cycle described above in reference toFIG.14when the triggering condition is any of the UE stopping camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging out of a location (e.g., office), the UE exiting a geofence location, and/or a loss of a CBRS signal. Note that when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was WiFi enabled/badge enabled, the UE may turn off the CBRS immediately when the trigger condition is the user turning off CBRS. As a further example, when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was geofence enabled, the UE may enter the hysteresis cycle described above in reference toFIG.14when the triggering condition is the UE exiting a geofence location and/or a loss of a CBRS signal. Note that when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was geofence enabled, the UE may ignore the trigger condition when the trigger condition is the UE stopping camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging out of a location (e.g., office). Note further that when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was geofence enabled, the UE may turn off the CBRS immediately when the trigger condition is the user turning off CBRS. As another further example, when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was user enabled, the UE may ignore the trigger condition when the trigger condition is the UE stopping camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging out of a location (e.g., office) or the UE exiting a geofence location. Further, when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was user enabled, the UE may enter the hysteresis cycle described above in reference toFIG.14when the triggering condition is a loss of a CBRS signal. Additionally, when a trigger condition attempts to disable a CBRS profile and the previous CBRS state was user enabled, the UE may turn off the CBRS immediately when the trigger condition is the user turning off CBRS.

As a yet further example, when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was inactive, the UE may enter the hysteresis cycle described above in reference toFIG.14when the trigger condition is the UE camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging into a location (e.g., office) or the UE entering a geofence location. Note that when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was inactive, the UE may immediately turn on CBRS when the trigger condition is a user turning on CBRS. As another example, when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was WiFi enabled/badge enabled, the UE may enter the hysteresis cycle described above in reference to Figure when the trigger condition is the UE entering a geofence location. Note that when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was WiFi enabled/badge enabled, the UE may immediately turn on CBRS when the trigger condition is a user turning on CBRS. Note further, that when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was WiFi enabled/badge enabled, the UE may ignore the trigger condition when the trigger condition is the UE camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging into a location (e.g., office). As a further example, when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was geofence enabled or user enabled, the UE may ignore the trigger condition when the trigger condition is the UE camping on a WiFi network co-located with a CBRS network associated with the CBRS profile and/or the UE badging into a location (e.g., office) or the UE entering a geofence location. Note that when a trigger condition attempts to enable a CBRS profile and the previous CBRS state was geofence enabled or user enabled, the UE may immediately turn on CBRS when the trigger condition is a user turning on CBRS.

FIGS.15A and15Billustrate an example of a block diagram of a method for triggered coarse selection of a CBRS profile, according to some embodiments. The method shown inFIGS.15A and15Bmay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1502, a UE (e.g., a CBRS controller of a UE, such as UE106) may detect a CBRS trigger condition, e.g., as described above.

At1504, the UE may determine if any user selection (e.g., manual override) requires the UE to ignore the trigger, e.g., as described above.

At1506, in response to determining that there is a user selection (e.g., manual override) that requires the UE to ignore the trigger, the UE ignores the trigger.

At1508, in response to determining that there is not a user selection (e.g., manual override) that requires the UE to ignore the trigger, the UE may determine whether CBRS is disabled and whether the trigger condition is entry into a geofence location.

At1510, in response to determining at least one of that CBRS is not disabled or that the trigger condition is not entry into a geofence location, the UE may determine whether CBRS is enabled and whether the trigger condition is exiting a geofence location.

At1512, in response to determining at least one of that CBRS is not enabled or that the trigger condition is not exiting a geofence location, the UE may determine whether CBRS is disabled and whether the trigger condition is association with a WiFi network co-located with the CBRS network.

At1514, in response to determining at least one of that CBRS is not disabled or that the trigger condition is not association with a WiFi network co-located with the CBRS network, the UE may determine whether CBRS is enabled and whether the trigger condition is disassociation with a WiFi network co-located with the CBRS network.

At1516, in response to determining at least one of CBRS is disabled and the trigger condition is entry into a geofence location, CBRS is enabled and the trigger condition is exiting a geofence location, CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, or CBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network, the UE may wait for expiration of a time out period (e.g., wait for expiration of a hysteresis timer as described above).

Alternatively, in response to determining at least one of that CBRS is not enabled or the trigger condition is not disassociation with a WiFi network co-located with the CBRS network, the UE may ignore the trigger condition at1506.

Continuing withFIG.15B, after waiting for the timeout period to expire the UE, at1518, the UE may determine whether CBRS is disabled and whether the UE is within a geofence location.

At1520, in response to determining at least one of that CBRS is not disabled or the UE is not within a geofence location, the UE may determine whether CBRS is disabled and whether the UE is associated with a WiFi network co-located with the CBRS network.

At1522, in response to determining at least one of that CBRS is disabled and that the UE is within a geofence location or that CBRS is disabled and that the UE is associated with a WiFi network co-located with the CBRS network, the UE may enable CBRS.

At1524, in response to determining at least one of that CBRS is not disabled or that the UE is not associated with a WiFi network co-located with the CBRS network, the UE may determine whether the UE detects a CBRS signal.

In response to determining that the UE detects a CBRS signal, the UE may perform no further operations at1506.

At1526, in response to determining that the UE does not detect a CBRS signal, the UE may determine whether CBRS is enabled and whether the UE is outside a geofence location and/or outside of a WiFi network co-located with the CBRS network.

At1528, in response to determining at least one of that CBRS is not enabled or whether the UE is not outside a geofence location, the UE may determine whether CBRS is enabled by geofence detection and whether the UE outside a geofence location.

At1530, in response to determining at least one of that CBRS is enabled and the UE is outside a geofence location and/or outside of a WiFi network co-located with the CBRS network or that CBRS is enabled by geofence detection and the UE is outside a geofence location, the UE may disable CBRS.

In response to determining at least one of that CBRS is not enabled by geofence detection or the UE is not outside a geofence location, the UE may ignore the trigger at1506.

FIG.16illustrates an example of a block diagram of a method for a radio resource arbitrator to perform various operations, according to some embodiments. The method shown inFIG.16may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1610, a radio access arbitrator814of a UE, such as UE106, may receive WiFi signal quality metrics, e.g., from a WiFi layer/interface of the UE.

At1612, the radio access arbitrator814may receive MNO (e.g., cellular, such as LTE and/or NR) signal quality metrics, e.g., from a NAS layer/interface of the UE.

At1614, the radio access arbitrator814may receive CBRS signal quality metrics, e.g., from the NAS layer/interface of the UE.

At1616, the radio access arbitrator814may receive application metrics, e.g., such as quality of service requirements, current internet session connections, and so forth from an application executing on the UE.

At1618, the radio access arbitrator814may receive network policies, e.g., such as preferences of the CBRS network and/or carrier.

At1620, based on the received metrics and/or policies, the radio access arbitrator814may determine whether to recommend CBRS slots or MNO slots and send the recommendation to a CBRS controller812of the UE.

At1622, radio access arbitrator814may determine whether to prefer cellular or WiFi for data and may send the preference to a network layer824of the UE.

FIG.17illustrates an example of a block diagram of a method for ranking CBRS profiles, according to some embodiments. The method shown inFIG.17may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1702, a new CBRS profile may be installed on a UE, such as UE106.

At1704, the UE may determine whether any other CBRS profiles have been installed.

At1706, in response to determining that other CBRS profiles have been installed, the UE may request the user to rank the new CBRS profile along with the other CBRS profiles.

At1708, the UE may determine whether the user ranking is complete. In an instance, the determination as to whether the ranking is complete may be based on one or more factors, such as but not limited to, expiration of a timer, a user input canceling the ranking process, a loss of power to the UE, and so forth.

At1710, in response to determining that the user ranking is complete, the UE may apply the user ranking to the new CBRS profile along with the other CBRS profiles.

At1712, in response to determining that the user ranking is not complete, the UE may apply a default ranking to the new CBRS profile along with the other CBRS profiles. For example, default strategies for ranking CBRS profiles when user declines ranking and/or does not complete ranking may include ranking based on time of use with most recently used receiving highest ranking, ranking based on frequency of use with most frequently used receiving highest ranking, ranking based on signal strength with strongest signal receiving highest ranking, and/or using a pop-up notification to user when multiple CBRS have their activation conditions met.

At1714, in response to determining that no other CBRS profiles have been installed, rank the new CBRS profile with a highest ranking.

FIGS.18A and18Billustrate an example of a block diagram of a method for selection of a CBRS profile from among multiple CBRS profiles, according to some embodiments. The method shown inFIGS.18A and18Bmay be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1802, a UE (e.g., a CBRS controller of a UE, such as UE106) may detect a CBRS trigger condition, e.g., as described above.

At1804, the UE may determine if any user selection (e.g., manual override) requires the UE to ignore the trigger, e.g., as described above.

At1806, in response to determining that there is a user selection (e.g., manual override) that requires the UE to ignore the trigger, the UE ignores the trigger.

At1808, in response to determining that there is not a user selection (e.g., manual override) that requires the UE to ignore the trigger, the UE may determine whether CBRS is disabled and whether the trigger condition is entry into a geofence location.

At1810, in response to determining at least one of that CBRS is not disabled or that the trigger condition is not entry into a geofence location, the UE may determine whether CBRS is enabled and whether the trigger condition is exiting a geofence location.

At1812, in response to determining at least one of that CBRS is not enabled or that the trigger condition is not exiting a geofence location, the UE may determine whether CBRS is disabled and whether the trigger condition is association with a WiFi network co-located with the CBRS network.

At1814, in response to determining at least one of that CBRS is not disabled or that the trigger condition is not association with a WiFi network co-located with the CBRS network, the UE may determine whether CBRS is enabled and whether the trigger condition is disassociation with a WiFi network co-located with the CBRS network.

At1816, in response to determining at least one of CBRS is disabled and the trigger condition is entry into a geofence location, CBRS is enabled and the trigger condition is exiting a geofence location, CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, or CBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network, the UE may wait for expiration of a time out period (e.g., wait for expiration of a hysteresis timer as described above).

Alternatively, in response to determining at least one of that CBRS is not enabled or the trigger condition is not disassociation with a WiFi network co-located with the CBRS network, the UE may ignore the trigger condition at1806.

Continuing withFIG.18B, after waiting for the timeout period to expire the UE, at1818, the UE may determine whether CBRS is enabled.

At1820, in response to determining that CBRS is enabled, the UE may determine whether an enabled CBRS profile meets a disabling condition.

At1822, in response to determining that the enabled CBRS profile meets a disabling condition, the UE may disable the CBRS profile.

At1824, in response to disabling the CBRS profile at1822or in response to determining that CBRS is not enabled, the UE may determine whether another CBRS profile meets an enabling condition.

At1826, in response to determining that another CBRS profile meets an enabling condition, the UE may enable the CBRS profile that meets the enabling condition.

At1828, in response to enabling the CBRS profile that meets the enabling condition or in response to determining that an enabled CBRS profile does not meet a disabling condition, the UE may determine whether any other CBRS profile meets the enabling condition.

At1830, in response to determining that at least one additional CBRS profile meets the enabling condition, the UE may use a ranking of the CBRS profiles (e.g., as described above) to select a highest ranked CBRS profile that meets the enabling condition.

At1832, the UE may determine whether a different CBRS profile is selected as compared to the enabled CBRS profile.

At1834, in response to determining that a different CBRS profile is selected as compared to the enabled CBRS profile, the UE may activate the selected CBRS profile.

Alternatively, in response to determining that a different CBRS profile is not selected as compared to the enabled CBRS profile, that another CBRS profile does not meet an enabling condition at1824or1828, the UE may take no action at1806.

In some embodiments, a user may manage CBRS profiles. For example, a user may change a CBRS profile. Then, the UE may determine whether the changed CBRS profile is a disabled CBRS profile. In response to determining that the changed CBRS profile is a disabled CBRS profile, the UE may place the disabled CBRS profile on a deny/ignore list, at least for a period of time. Alternatively, if the changed CBRS profile was not a disabled CBRS profile, the UE may determine whether the CBRS profiles is enabled. In response to determining that the CBRS profile was not enabled, the UE may take no further action. However, in response to determining that the CBRS profile was enabled, the UE may check whether the changed CBRS profile is on the deny/ignore list. Further, in response to determining that the changed CBRS profile is on the deny/ignore list, the UE may remove the changed CBRS profile from the deny/ignore list and note user selection in CBRS controller. Alternatively, in response to determining that the changed CBRS profile is not on the deny/ignore list, the UE may note user selection in CBRS controller.

In some embodiments, machine learning may be implemented to augment detection of CBRS networks. For example, in some embodiments, reinforcement machine learning may be implemented to augment detection of CBRS networks. For example, an environment may be a model of a city with CBRS deployments and co-located WiFi locations collected from real deployments and an agent may be a device that does not have the ability to detect geofence around CBRS deployments, but does detect WiFi, movement speed, and so forth. The agent may be moved around the city like a real user, camping on/off WiFi networks where available. Then, when the agent correctly performs action (for example, turning on CBRS when inside coverage due to detection of a strong co-located WiFi), the agent may receive a reward and is thus more likely to perform the same action next time. Since the agent does not know the CBRS coverage exactly, the agent may learn to turn on CBRS when co-located WiFi network strength reaches a certain threshold. Further, when the agent incorrectly performs action (for example, turning on CBRS when detecting a weak WiFi network signal), the agent may receive a punishment. Since the agent does not know the CBRS coverage exactly, the agent may learn to not turn on CBRS immediately if the WiFi network signal is weak (which may indicate that the device has not yet entered CBRS geofence). Then, over time, the agent may learn optimal conditions to turn on/off CBRS so that it can be deployed on real devices to do the same in real-world scenarios. As another example, in some embodiments, federated machine learning may be implemented to augment detection of CBRS networks. For example, distributed machine learning on-device may be implemented to protect privacy of users. Thus, each device can obtain WiFi and geofence data independently and train the same machine learning model. Then, a weighted gradient is pooled and returned to centralized server. This is equivalent of training using all the data on the centralized server, but the server does not know each individual training data. The server may then use gradients to update machine learning model and periodically distribute it to each device.

FIG.19illustrates a block diagram of an example of a method for selection of a Citizens Broadband Radio Service (CBRS) profile, according to some embodiments. The method shown inFIG.19may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

At1902, a UE, such as UE106, may detect a trigger condition associated with a CBRS profile. The CBRS profile may be one of one or more CBRS profiles provisioned to the UE. In some instances, the trigger condition may be one of a plurality of trigger conditions. In addition, the plurality of trigger conditions may be prioritized based, at least in part, on trigger type. For example, a first trigger type associated with a user generated trigger condition may be a higher priority trigger condition as compared to a second trigger type associated with a geofence trigger condition. Additionally, the second trigger type may be a higher priority trigger condition as compared to a third trigger type associated with camping on a WiFi or badging into a location.

In some instances, detecting the trigger condition may include the UE determining whether the trigger condition was user generated. In addition, when the UE determines the trigger condition was user generated, the UE may apply the action associated with the trigger condition. Further, when the UE determines the trigger condition was not user generated, the UE may wait a predefined and/or specified period of time (e.g., a hysteresis cycle) prior to performing the action associated with the trigger condition. In such instances, in response to determining, after the predefined and/or specified period of time, that the trigger condition persists, the UE may apply the action associated with the trigger condition. Additionally, in response to determining, after the predefined and/or specified period of time, that the trigger condition does not persist, the UE may not apply the action associated with the trigger condition.

At1904, the UE may perform, in response to detection of the trigger condition, an action associated with the trigger condition. The action may include at least enablement of the CBRS profile. The CBRS profile may be selected from one or more CBRS profiles. In some instances, the action associated with the trigger condition may include ignoring the trigger condition, CBRS profile disablement, and/or a CBRS profile update.

At1906, the UE may enable the CBRS profile.

In some instances, the UE may retrieve, from a geofencing data server, CBRS geofence data based, at least in part, on one or more CBRS profiles installed on an eSIM of the UE. In addition, the UE may generate, based on the retrieved CBRS geofence data, the one or more CBRS profiles, thereby provisioning the one or more CBRS profiles to the UE. The CBRS geofence data may be provided to the geofencing data server by an operator portal. The operator portal may receive the CBRS geofence data from a CBRS network transmit/receive point (TRP). The CBRS network TRP may be a base station or an access point. The CBRS geofence data may include information associated with locations of one or more CBRS networks. Additionally, for each CBRS network of the one or more CBRS networks, the information associated with location may include any, any combination of, and/or all of (e.g., one or more of and/or at least one of) coordinates of boundary locations of a CBRS network, a network name, a base station identifier (ID), a base station name, a band, an Absolute Radio Frequency Channel (ARFCN), a Shared Home. Network Identifier (SHNI), a Public Land Mobile Network (PLMN) ID, a tracking area code (TAC), a cell ID, a CBRS network ID (NID), a latitude of a TRP, a longitude of a TRP, an altitude of a TRP, a radius of the geofence area, and/or a list of co-located WiFi Service Set Identifiers (SSIDs).

In some instances, the UE may perform a band scan based on the CBRS profile and perform network attachment to a CBRS network associated with the CBRS profile.

In some instances, the UE may determine to prefer cellular communications via the CBRS network over WiFi communications for data transmissions.

In some instances, the UE may monitor, relative to a geofence area associated with the CBRS profile, UE location and upon determining an exit from the geofence area, disable the CBRS profile. In some instances, the UE may switch a data preference from a CBRS network to a co-located mobile network operator network (MNO) network. In some instances, the UE may determine to prefer WiFi communications over cellular communications via the co-located MNO network for data transmissions.

In some instances, detecting the trigger condition may include the UE detecting include any, any combination of, and/or all of (e.g., one or more of and/or at least one of) entry into a geofence area, wherein the geofence area is associated with the CBRS profile, camping on a WiFi network co-located with a CBRS network associated with the CBRS profile, badging into a location associated with a CBRS network associated with the CBRS profile, and/or enablement of a CBRS mode of the UE.

In some instances, the action associated with the trigger condition may depend, at least in part, on a CBRS state. For example, when the action associated with the trigger condition is CBRS profile disablement, the UE may ignore the action when the CBRS state is inactive, when the CBRS state is geofence enabled and the trigger condition is at least one of disconnecting from a WiFi network co-located with a CBRS network associated with the CBRS profile or badging out of a location associated with a CBRS network associated with the CBRS profile, or when the CBRS state is user enabled and the trigger condition is at least one of disconnecting from on a WiFi network co-located with a CBRS network associated with the CBRS profile, badging out of a location associated with a CBRS network associated with the CBRS profile, and/or exit from a geofence area associated with the CBRS profile. As another example, when the action associated with the trigger condition is CBRS profile disablement, the UE may enter a hysteresis cycle when the CBRS state is WiFi enabled or badge enabled and the trigger condition is at least one of exiting from a geofence area associated with the CBRS profile, disconnecting from a WiFi network co-located with a CBRS network associated with the CBRS profile, badging out of a location associated with a CBRS network associated with the CBRS profile, or loss of a CBRS signal, when the CBRS state is geofence enabled and the trigger condition is at least one of exiting from a geofence area associated with the CBRS profile or loss of a CBRS signal, entering a hysteresis cycle, and/or when the CBRS state is user enabled and the trigger condition is loss of a CBRS signal. As a further example, when the action associated with the trigger condition is CBRS profile enablement, the UE may ignore the action when the CBRS state is WiFi enabled or badge enabled and the trigger condition is at least one of camping on a WiFi network co-located with a CBRS network associated with the CBRS profile or badging into a location associated with a CBRS network associated with the CBRS profile, when the CBRS state is geofence enabled or user enabled and the trigger condition is at least one of camping on a WiFi network co-located with a CBRS network associated with the CBRS profile, and/or badging into a location associated with a CBRS network associated with the CBRS profile. In yet another example, when the action associated with the trigger condition is CBRS profile enablement, the UE may enter a hysteresis cycle when the CBRS state is inactive and the trigger condition is at least one of camping on a WiFi network co-located with a CBRS network associated with the CBRS profile, badging into a location associated with a CBRS network associated with the CBRS profile, or the entering geofence area associated with the CBRS profile, and/or when the CBRS state is WiFi enabled or badge enabled and the trigger condition is entering a geofence location associated with the CBRS profile. Note that the hysteresis cycle may include the UE waiting a predefined and/or specified period of time prior to performing the action associated with the trigger condition.

In some instances, performing, in response to detection of the trigger condition, an action associated with the trigger condition may include the UE ignoring the trigger condition in response to determining that a user selection requires the UE to ignore the trigger condition. Further, the UE may wait for expiration of a time out period (e.g., performing a hysteresis cycle) in response to determining at least one of CBRS is disabled and the trigger condition is entry into a geofence location, CBRS is enabled and the trigger condition is exiting a geofence location, CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, and/or CBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network. In some instances, the UE may ignore the trigger condition when none of the following conditions are satisfied:CBRS is disabled and the trigger condition is entry into a geofence location;CBRS is enabled and the trigger condition is exiting a geofence location;CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network; andCBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network.

In some instances, the UE may, after expiration of the timeout period, enabling CBRS when CBRS is disabled and the trigger condition is entry into a geofence location or when CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, disable CBRS when CBRS is enabled and the trigger condition is exiting a geofence location or when CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, and ignore the trigger condition when a CBRS signal is detected or when none of the following conditions are satisfied:CBRS is disabled and the trigger condition is entry into a geofence location;CBRS is enabled and the trigger condition is exiting a geofence location;CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network; andCBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network.

In some instances, the UE may determine signal quality metrics for one or more networks co-located with a CBRS network associated with the CBRS profile, wherein the one or more networks include one or more mobile network operator (MNO) networks and one or more WiFi networks. Further, the UE may determine, based, at least in part, on the determined signal quality metrics, a preference order for MNO networks and the CBRS network and a preference order for the CBRS network, MNO networks, and WiFi networks. In some instances, determining, based, at least in part, on the determined signal quality metrics, a preference order for MNO networks and the CBRS network and a preference order for the CBRS network, MNO networks, and WiFi networks may include the UE determining the preference order for MNO networks and the CBRS network and the preference order for the CBRS network, MNO networks, and WiFi networks based further on one or more application metrics or network policies. Note that application metrics may include one or more quality of service requirements or current internet session connections. Note further that the network policies may include one or more of CBRS network preferences or carrier preferences.

In some instances, the UE may install a new CBRS profile and determine whether any other CBRS profiles have been previously installed. Further, in response to determining that other CBRS profiles have been installed, the UE may request, via a user interface, a user to rank the new CBRS profile along with the other CBRS profiles. Additionally, the UE may determine whether the user ranking is complete and in response to determining that the user ranking is not complete, apply a default ranking to the new CBRS profile along with the other CBRS profiles. The default ranking may include any, any combination of, and/or all of (e.g., at least one of and/or one or more of) ranking based on time of use with a most recently used CBRS profile receiving a highest ranking, ranking based on frequency of use with a most frequently used CBRS profile receiving a highest ranking, ranking based on signal strength with a strongest signal CBRS profile receiving highest ranking, and/or using a pop-up notification to query a user to select a CBRS profile when multiple CBRS profiles have activation conditions met.

In some instances, performing, in response to detection of the trigger condition, an action associated with the trigger condition may include the UE ignoring the trigger condition in response to determining that a user selection requires the UE to ignore the trigger condition. In addition, the UE may wait for expiration of a time out period (e.g., a hysteresis cycle) in response to determining that the CBRS is disabled and the trigger condition is entry into a geofence location, determining that the CBRS is enabled and the trigger condition is exiting a geofence location, determining that the CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network, and/or determining that the CBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network. The UE may, after expiration of timeout period and in response to determining that the CBRS is not enabled and a CBRS profile meets an enabling condition or that an enabled CBRS does not meet a disabling condition, determine whether another CBRS profile meets an enabling condition. Further, in response to determining the another CBRS profile meets the enabling condition, the UE may select a CBRS profile based on user input or a ranking of CBRS profiles. In some instances, the UE may ignore the trigger condition when none of the following conditions are satisfied:CBRS is disabled and the trigger condition is entry into a geofence location;CBRS is enabled and the trigger condition is exiting a geofence location;CBRS is disabled and the trigger condition is association with a WiFi network co-located with the CBRS network; andCBRS is enabled and the trigger condition is disassociation with a WiFi network co-located with the CBRS network.

In some instances, the UE may determine that a CBRS profile has changed or expired and determine whether a carrier supports geofence data. In addition, the UE may retrieve or fetch, in response to determining that the carrier supports geofence data, the geofence data from the carrier. In some instances, determining whether the carrier supports geofence data may include the UE querying an entitlements server of the carrier. In some instances, the UE may retrieve or fetch, in response to determining that the carrier does not support geofence data, the geofence data from a server hosted by a manufacturer of the UE.

In some instances, the UE may receive a command to update a CBRS profile and determine whether a carrier supports geofence data. Further, the UE may retrieve or fetch, in response to determining that the carrier supports geofence data, the geofence data from the carrier. In some instances, determining whether the carrier supports geofence data may include the UE querying an entitlements server of the carrier. In some instances, the UE may retrieve or fetch, in response to determining that the carrier does not support geofence data, the geofence data from a server hosted by a manufacturer of the UE.

In some instances, the UE may detect entry into a geofence location of a known CBRS region and attempt to verify the CBRS region. The UE may transmit, to a server, a confirmation of verification in response to verifying the CBRS region. In some instances, attempting to verify the CBRS region may be in response to the UE receiving a request to verify the CBRS region. In some instances, the UE may transmit, to the server, updated CBRS information in response to not verifying the CBRS region.

In some instances, the UE may receive, based on a current location of the UE, a request to scan for a CBRS region and determine, in response to the request, whether a new CBRS region has been located. Further, in response to determining the new CBRS region has been located, the UE may send updated CBRS information to a server. The request may be received from a mobile network operator (MNO) or carrier.

Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message/signal X received by the UE in the downlink as message/signal X transmitted by the base station, and each message/signal Y transmitted in the uplink by the UE as a message/signal Y received by the base station.