Techniques for recovery of network service based on location change

Abstract

Methods, systems, and devices for wireless communications are described that provide for a user equipment (UE) operation subsequent to receipt of a rejection message in response to a registration request. The UE, upon receipt of the rejection message that indicates the rejection is based on a location of the UE, may start a timer for a subsequent registration request, and may monitor one or more conditions associated with the UE location. Upon detection of a changed UE location, the UE may resend the registration request irrespective of the timer status. The one or more conditions associated with the UE location may include, for example, a change in a set of physical cell identities in idle mode mobility, a transition to an out-of-service state, a satellite-based detection of a location change, a Wi-Fi / Bluetooth coverage change, or any combinations thereof.

Description

TECHNIQUES FOR RECOVERY OF NETWORK SERVICE BASED ON LOCATION CHANGECROSS REFERENCE

[0001] The present Application for Patent claims the benefit of India Patent Application No. 202341062451 by TARIMALA et al., entitled “TECHNIQUES FOR RECOVERY OF NETWORK SERVICE BASED ON LOCATION CHANGE,” filed September 16,2023, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including techniques for recovery of network service based on location change.BACKGROUND

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

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for recovery of network service based on location change. For example, the described techniques provide for a user equipment (UE), that receives a rejection message in response to a registration request, to resend the registration request upon detection of a location change of the UE subsequent to transmission of the initial registration request. In some aspects, a UE may request access (e.g., via a non-terrestrial network (NTN)) to a first network, such as a first public land mobile network (PLMN), and receive a rejection message that indicates the registration of the UE at the first network is rejected due to the UE location. The UE, based on the rejection message, may start a timer for a subsequent registration request, and may transmit the subsequent registration request upon detection of a mobile country code (MCC) change at the UE irrespective of the timer status. Such techniques may allow the UE to transmit the request immediately upon MCC change detection, which may improve access latency. Additionally, or alternatively, the UE may refrain from transmitting a subsequent registration request when the MCC has not changed, which may reduce power consumption. In some aspects, a MCC change may be determined based on a PLMN scan at the UE and MCCs from the detected PLMNs. The PLMN scan may be triggered by one or more detected conditions at the UE, such as change in a physical cell identity (PCI) set during idle mode mobility, the UE moving to an out-of- service state, a global navigation satellite system (GNSS)-based location change, a WiFi or Bluetooth coverage change, or any combinations thereof. In some aspects, if the MCC has changed at the UE, the PLMN is removed from a blocked PLMN list at the UE, and a subsequent registration request may be transmitted (e.g., via the NTN).

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include transmitting a first registration request to register with a first mobile network, receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE, initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network, and transmitting a second registration request to register with the first mobile network, thesecond registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to transmit a first registration request to register with a first mobile network, receive a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE, initiate a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network, and transmit a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0007] Another UE for wireless communications is described. The UE may include means for transmitting a first registration request to register with a first mobile network, means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE, means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network, and means for transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by a processor to transmit a first registration request to register with a first mobile network, receive a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE, initiate a timer associated with therejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network, and transmit a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0009] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the timer has expired and refraining from transmitting a subsequent registration request to register with the first mobile network based on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

[0010] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for triggering a scan to detect a current mobile country code associated with the UE based on one or more trigger conditions and performing the scan to detect the current mobile country code associated with the UE. In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof. In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the wireless local area network coverage change detection includes one or more of a Wi-Fi coverage change detection or a Bluetooth coverage change detection. In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the scan to detect the current mobile country code may include operations, features, means, or instructions for scanning one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes.

[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first registration request and the second registration request may be transmitted via a non-terrestrial network, and the first mobile network may be a home public land mobile network (HPLMN), an equivalent HPLMN (EHPLMN), or a registered public land mobile network (RPLMN).

[0012] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the rejection message may be an enhanced packet core (EPC) mobile management (EMM) reject message that includes a reject cause that indicates a public land mobile network (PLMN) identification associated with the first mobile network may be not allowed to operate at a present location of the UE.

[0013] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for adding, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE and removing the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE may have changed.

[0014] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the second registration request is transmitted via a nonterrestrial network responsive to a loss of terrestrial network coverage at the UE.

[0015] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first registration request and the second registration request may be transmitted via a non-terrestrial network and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for establishing a connection with the first mobile network via the non-terrestrial network responsive to the second registration request and transmitting or receiving one or more messages to or from the first mobile network via the nonterrestrial network.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 shows an example of a wireless communications system that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0017] FIG. 2 shows an example of a portion of a wireless communications system that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0018] FIGs. 3 and 4 show examples of flow charts illustrating methods that support techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0019] FIGs. 5 and 6 show block diagrams of devices that support techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0020] FIG. 7 shows a block diagram of a communications manager that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0021] FIG. 8 shows a diagram of a system including a device that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.

[0022] FIGs. 9 through 12 show flowcharts illustrating methods that support techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0023] In some wireless communications systems, one or more aerial-based platforms may be part of a non-terrestrial network (NTN, and may be used for some communications with a user equipment (UE). Such aerial platforms may include, for example, a space satellite, a balloon, a dirigible, an airplane, a drone, an unmanned aerial vehicle, other vehicle, or any combination thereof, which may support communications from a generally non-terrestrial, overhead, or elevated position. Asused herein, the term satellite may be used to generally refer to any such aerial platforms. In some cases, a satellite may provide a relatively large coverage area, particularly in comparison to a terrestrial component such as a terrestrial base station or terrestrial transmission-reception point (TRP). Such relatively large coverage areas in some instances may span across areas of two or more countries.

[0024] In some NTNs, a UE may connect with a public land mobile network (PLMN) via a satellite that may provide for enhanced network coverage for UEs that may not have terrestrial network coverage, and may provide important communications and can be crucial in emergency cases where emergency messaging or SOS communications may be needed. However, some countries do not allow connection to certain mobile networks (e.g., access to some PLMNs are not allowed). For terrestrial networks, forbidding access to some networks is relatively straightforward, as such networks may simply avoid installing base stations or TRPs within the restricted area or that have coverage in the restricted area (e.g., by configuring antenna coverage only for permitted communications areas). As discussed, NTNs may have a relatively larger coverage areas, which may extend to restricted areas. Traditional techniques to prevent access to restricted PLMNs from locations (e.g., countries) in which a PLMN is restricted include enhanced packet core (EPC) mobility management (EMM) procedures that provide that a PLMN can reject a registration request from a UE in a restricted location. For example, a UE may transmit a registration request to a PLMN and the PLMN may reject the request, with a reject cause that indicates the UE is in a restricted area (e.g., EMM reject cause #78) (e.g., EMM reject cause #78). A subsequent registration request may be transmitted upon expiration of an associated timer (e.g., a one hour timer), or if the UE’s location has changed by a certain amount (e.g., if the UE’s location has changed by at least 50 km). However, timer-based subsequent registration requests may cause increased power consumption and, if the UE’s location has not changed, are unlikely to be successful. Further, location-based subsequent requests may not be transmitted until the timer has expired, which may result in unnecessary delay in transmitting a subsequent registration request.

[0025] In accordance with various aspects as discussed herein, a subsequent registration request may be transmitted based on a UE determining that the registration request has an increased likelihood of success irrespective of a status of a timer that isstarted upon receipt of a reject message. In some aspects, a UE, subsequent to receiving a registration rejection message for accessing a PLMN (e.g., via a NTN), may start a timer for a subsequent registration request, but may transmit the subsequent registration request upon detection of a mobile country code (MCC) change at the UE irrespective of the timer status. Such techniques may allow the UE to transmit the request immediately upon MCC change detection, which improves access latency. Additionally, or alternatively, the UE may refrain from transmitting registration requests when the MCC has not changed, which can reduce power consumption through reduced transmissions. In some aspects, a MCC change may be determined based on a PLMN scan at the UE and the MCCs of detected PLMNs. Such a PLMN scan may be triggered by one or more detected conditions at the UE, such as change in a physical cell identity (PCI) set during idle mobility, the UE moving to an out-of-service state, a GNSS-based location change, a Wi-Fi or Bluetooth coverage change, or any combinations thereof. In some aspects, if the MCC has changed at the UE, the PLMN may be removed from a blocked PLMN list and a subsequent registration request may be transmitted (e.g., via the NTN).

[0026] Such techniques may provide for faster recovery of service in case of coverage loss of a non-restricted network due to event-based transmission of registration requests subsequent to a notification that a PLMN is restricted or blocked, irrespective of a timer associated with a blocked PLMN. Such decreased recovery times, for example, may provide for increased availability of an NTN which may be critical in emergency cases such as emergency messaging or SOS communications. Further, such techniques may provide efficient throttling of registration attempts in cases where a UE location has not changed.

[0027] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for recovery of network service based on location change.

[0028] FIG. 1 shows an example of a wireless communications system 100 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or moreUEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0037] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support techniques for recovery of network service based on location change as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

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

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

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

[0041] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non- standalone mode, in which case a connection isanchored using a different carrier (e.g., of the same or a different radio access technology).

[0042] The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0043] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

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

[0045] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

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

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

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

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

[0050] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cellmay be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0051] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140), as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.

[0052] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

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

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

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

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

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

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

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

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

[0061] Wireless communications system 100 may also include one or more satellites 190. A satellite 190 may communicate with network entity 105, which may be referred to as gateways in an NTN, and UEs 115, which may include other high altitude or terrestrial communications devices. In some examples, a satellite 190 itself may be an example of a network entity 105. A satellite 190 may be any suitable type ofcommunication satellite configured to relay or otherwise support communications between different devices in the wireless communications system 100. A satellite 190 may be an example of a space satellite, a balloon, a dirigible, an airplane, a drone, an unmanned aerial vehicle, or other vehicle which may support communications from a generally non-terrestrial, overhead, or elevated position. In some examples, a satellite 190 may be in a geosynchronous or geostationary earth orbit, a low earth orbit, or a medium earth orbit. A satellite 190 may be a multi -beam satellite configured to provide service for multiple service beam coverage areas in a configured geographical service area. The satellite 190 may be any distance away from the surface of the earth or other reference surface.

[0062] In some examples, a cell may be provided or established by a satellite 190 as part of an NTN. A satellite 190 may, in some cases, perform the functions of a network entity 105, act as a bent-pipe satellite, or act as a regenerative satellite, or a combination thereof. In some examples, a satellite 190 may be an example of a smart satellite, or a satellite with intelligence or other communications processing capability. For example, a smart satellite may be configured to perform more functions than a regenerative satellite (e.g., may be configured to perform particular algorithms beyond those used in regenerative satellites, to be reprogrammed). In a bent-pipe transponder configuration, a satellite 190 may be configured to receive signals from ground stations (e.g., gateways, network entity 105, a core network 130) and transmit those signals to different ground stations or terminals (e.g., UEs 115, network entity 105). In some cases, a satellite 190 supporting a bent-pipe transponder configuration may amplify signals or shift from uplink frequencies to downlink frequencies. In some examples, a satellite 190 supporting a regenerative transponder configuration may relay signals like a bent-pipe transponder configuration, but may also use on-board processing to perform other functions. Examples of these other functions may include demodulating a received signal, decoding a received signal, re-encoding a signal to be transmitted, modulating the signal to be transmitted, or a combination thereof. In some examples, a satellite 190 supporting a bent pipe transponder configuration or regenerative transponder configuration may receive a signal from a network entity 105 and may relay the signal to a UE 115 or network entity 105, or vice-versa.

[0063] In accordance with various aspects, a UE 115 may transmit a registration request for communications with a network (e.g., a PLMN) via a network entity 105, and may receive a rejection message in response thereto. The UE 115 may start a timer associated with the network, and resend the registration request upon detection of a location change of the UE 115 irrespective of a status of the timer. In some aspects, the UE 115 may transmit the subsequent registration request upon detection of a MCC change at the UE 115. Such techniques may allow the UE to transmit the request immediately upon MCC change detection, which may improve access latency. Additionally, or alternatively, the UE may refrain from transmitting a subsequent registration request when the MCC has not changed, which may reduce power consumption.

[0064] FIG. 2 shows an example of a wireless communications system 200 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. In the example of FIG. 2 a UE 115-a may communicate with a network entity 105-a, a satellite or NTN TRP 205, or any combination thereof. In some examples, the network entity 105-a may be an example or a terrestrial network entity or a non-terrestrial network entity with coverage area or cell 110-a. Additionally or alternatively, the NTN TRP 205 may be an example of an NTN network entity, and may be associated with coverage area or cell 110-b.

[0065] In this example, the UE 115-a may communicate with one or both of the network entity 105-a using a first communications link 210 or the NTN TRP 205 using a second communications link 215. It is noted that although various examples discussed herein discuss a PLMN accessed through a NTN such as via NTN TRP 205, such techniques may also be used for some terrestrial networks that may have one or more TRPs (such as network entity 105-a) that have coverage areas 110 that extend into restricted areas. Continuing with the example of FIG. 2, the UE 115-a may initially be located at a first location in country A 220 at a first time 240 (ti). In this example, country A 220 may forbid access to a PLMN that is accessed through one or both of the NTN TRP 205 or network entity 105-a. At a second time 245 (t2) the UE 115-a may chance location to country B 225, as indicated by arrow 250. In this example, country B 225 may allow access to the PLMN through one or both of the NTN TRP 205 or network entity 105-a.

[0066] In some cases, at the first time 240 the UE 115-a may transmit a registration request 230 (e.g., via NTN TRP 205 or network entity 105-a) to begin communications with the PLMN. Because the UE 115-a is located in country A 220 at the time of the transmission of the registration request 230, the network may transmit a rejection message 235 to the UE 115-a that indicates the registration request is rejected due to the location of the UE 115-a (e.g., EMM reject cause #78 as defined in 3GPP specifications). For example, the UE 115-a may attempt to register with its home PLMN (HPLMN), and the registration may fail when it is located in country A 220 at the first time 240, but after the UE 115-a moves to country B 225 at the second time 245, the same PLMN could accept the UE 115-a HPLMN registration. Based on the rejection message 235, the UE 115-a may start a timer that is associated with the inclusion of the PLMN on a blocked network list.

[0067] In accordance with various aspects as discussed herein, a subsequent registration request may be transmitted based on the UE 115-a determining that a subsequent registration request 230 has an increased likelihood of success irrespective of a status of the timer. In some aspects, a UE, subsequent to receiving a registration rejection message 235, may transmit the subsequent registration request upon detection of a MCC change at the UE 115-a irrespective of the timer status. Such techniques may allow the UE 115-a to transmit the request immediately upon MCC change detection, which improves access latency. Further, in some cases the UE may refrain from transmitting a subsequent registration request when the MCC has not changed, which can reduce power consumption through reduced transmissions that have a low likelihood of resulting in a network connection. In some aspects, a MCC change may be determined based on a PLMN scan at the UE 115-a and the MCCs of detected PLMNs. Such a PLMN scan may be triggered by one or more detected conditions at the UE 115- a, such as change in a PCI set during idle mobility, the UE 115-a moving to an out-of- service state, a GNSS-based location change, a Wi-Fi or Bluetooth coverage change, or any combinations thereof. In some aspects, if the MCC has changed at the UE 115-a, the PLMN may be removed from a blocked PLMN list and a subsequent registration request may be transmitted (e.g., via the NTN).

[0068] FIG. 3 shows an example of a flow chart illustrating a method 300 that supports techniques for recovery of network service based on location change inaccordance with one or more aspects of the present disclosure. In some examples, the method 300 may implement, or be implemented by, aspects of wireless communications systems 100 or 200, as described with reference to FIGs. 1 and 2. In some examples, the operations illustrated FIG. 3 may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code (e.g., software or firmware) executed by a processor, or any combination thereof. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

[0069] At 305, the UE may transmit a registration request to a network. For example, the UE, while at a first location may transmit a registration request via a NTN to a HPLMN.

[0070] At 310, the UE may receive a rejection message from the network. For example, the UE may receive an attach or tracking area update (TAU) reject message with a cause that indicates the rejection is based on UE location (e.g., Attach / TAU reject message with cause #78 as defined in the 3GPP specifications).

[0071] At 315, the UE may add the network to a list of blocked networks, and start a timer that is associated with the network. For example, the UE may add an identification of the HPLMN to a blocked list. In some cases, the timer (e.g., a one hour timer) may start when the network is added to the list, and an expiration of the timer may indicate that the UE may attempt another registration with the network.

[0072] At 320, the UE may monitor a set of events to determine whether the MCC of the UE has changed. In some cases, the set of events may include one or more of a change in a PCI set because of cell selection or reselection (e.g., as part of a mobility procedure at the UE), the UE 115-a moving to an out-of-service state, a GNSS-based location change, a Wi-Fi or Bluetooth coverage change, or any combinations thereof. If one of the events has occurred, it may indicate a change of location of the UE and trigger the UE to perform a PLMN scan to determine a MCC of the UE based on MCCs of detected PLMNs.

[0073] At 325, the UE may determine whether its MCC has changed. For example, the UE may determine the current MCC based on the PLMN scan, and compare it to aprior MCC that was identified as part of the initial registration request. In this example, if the MCC has not changed, the UE continues with operations at 320.

[0074] At 330, if the MCC has changed, the UE may unblock the network and attempt to register with the network again. For example, the PLMN may be removed from the UE’s blocked PLMN list and a subsequent registration request may be transmitted (e.g., via the NTN).

[0075] FIG. 4 shows another example of a flow chart illustrating a method 400 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. In some examples, the method 400 may implement, or be implemented by, aspects of wireless communications systems 100 or 200, as described with reference to FIGs. 1 and 2. In some examples, the operations illustrated FIG. 4 may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code (e.g., software or firmware) executed by a processor, or any combination thereof. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

[0076] At 405, the UE may transmit a registration request to a network. For example, the UE, while at a first location, may transmit a registration request via a NTN to a HPLMN.

[0077] At 410, the UE may receive a rejection message from the network. For example, the UE may receive an attach or tracking area update (TAU) reject message with a cause that indicates the rejection is based on UE location (e.g., Attach / TAU reject message with cause #78 as defined in the 4GPP specifications).

[0078] At 415, the UE may add the network to a list of blocked networks, and start a timer that is associated with the network. For example, the UE may add an identification of the PLMN to a blocked list. In some cases, the timer (e.g., a one hour timer) may start when the network is added to the list, and an expiration of the timer may indicate that the UE may attempt another registration with the network.

[0079] At 420, the UE may monitor a set of events to determine whether the MCC of the UE has changed. In some cases, the set of events may include one or more of a change in a PCI set because of cell selection or reselection (e.g., as part of a mobility procedure at the UE), the UE 115-a moving to an out-of-service state, a GNSS-based location change, a Wi-Fi or Bluetooth coverage change, or any combinations thereof. If one of the events has occurred, it may indicate a change of location of the UE and trigger the UE to perform a PLMN scan to determine a MCC of the UE based on MCCs of detected PLMNs.

[0080] At 425, the UE may determine whether the timer has expired. At 430, if the timer has not expired, or if the timer has expired, the UE may detect that a MCC scan trigger condition has been satisfied. For example, the UE may determine that a PLMN scan is triggered based on the monitoring of the set of events as discussed with reference to 420.

[0081] At 435, the UE may determine whether its MCC has changed. For example, the UE may determine the current MCC based on the PLMN scan, and compare it to a prior MCC that was identified as part of the initial registration request. In this example, if the MCC has not changed, the UE continues with operations at 420.

[0082] At 440, if the MCC has changed, the UE may unblock the network and attempt to register with the network again. For example, the PLMN may be removed from the UE’s blocked PLMN list and a subsequent registration request may be transmitted (e.g., via the NTN). In some aspects, upon expiration of the timer at 425, the UE may unblock the PLMN (e.g., based on an elapsed time from a prior registration request exceeding a threshold, such as one day or some user or manufacturer selected threshold, based on an explicit user request, based on a type of communication requested, such as an emergency communication, or any combinations thereof).

[0083] FIG. 5 shows a block diagram 500 of a device 505 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communicationsmanager 520), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0084] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for recovery of network service based on location change). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

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

[0086] The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for recovery of network service based on location change as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0090] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for transmitting a first registration request to register with a first mobile network. The communications manager 520 is capable of, configured to, or operable to support a means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The communications manager 520 is capable of, configured to, or operable to support a means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequentregistration requests to register with the first mobile network. The communications manager 520 is capable of, configured to, or operable to support a means for transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0091] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for efficient recovery of services at a restricted network that provide for faster return to service due to event-based transmission of registration requests to a blocked network, increased availability of an NTN for emergency messaging or SOS communications, and / or power reduction from efficient throttling of registration attempts in cases where a UE location has not changed.

[0092] FIG. 6 shows a block diagram 600 of a device 605 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0093] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for recovery of network service based on location change). Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0094] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for recovery of network service based on location change). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0095] The device 605, or various components thereof, may be an example of means for performing various aspects of techniques for recovery of network service based on location change as described herein. For example, the communications manager 620 may include an PLMN registration manager 625, a rejection message manager 630, a timer manager 635, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0096] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The PLMN registration manager 625 is capable of, configured to, or operable to support a means for transmitting a first registration request to register with a first mobile network. The rejection message manager 630 is capable of, configured to, or operable to support a means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The timer manager 635 is capable of, configured to, or operable to support a means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests toregister with the first mobile network. The PLMN registration manager 625 is capable of, configured to, or operable to support a means for transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0097] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of techniques for recovery of network service based on location change as described herein. For example, the communications manager 720 may include an PLMN registration manager 725, a rejection message manager 730, a timer manager 735, an MCC scan manager 740, an NTN communication manager 745, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0098] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The PLMN registration manager 725 is capable of, configured to, or operable to support a means for transmitting a first registration request to register with a first mobile network. The rejection message manager 730 is capable of, configured to, or operable to support a means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The timer manager 735 is capable of, configured to, or operable to support a means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. In some examples, the PLMN registration manager 725 is capable of, configured to, or operable to support a means for transmitting a second registration request to register with the first mobile network, thesecond registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0099] In some examples, the timer manager 735 is capable of, configured to, or operable to support a means for determining that the timer has expired. In some examples, the rejection message manager 730 is capable of, configured to, or operable to support a means for refraining from transmitting a subsequent registration request to register with the first mobile network based on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

[0100] In some examples, the MCC scan manager 740 is capable of, configured to, or operable to support a means for triggering a scan to detect a current mobile country code associated with the UE based on one or more trigger conditions. In some examples, the MCC scan manager 740 is capable of, configured to, or operable to support a means for performing the scan to detect the current mobile country code associated with the UE. In some examples, the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof. In some examples, the wireless local area network coverage change detection includes one or more of a Wi-Fi coverage change detection or a Bluetooth coverage change detection.

[0101] In some examples, to support performing the scan to detect the current mobile country code, the MCC scan manager 740 is capable of, configured to, or operable to support a means for scanning one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes. In some examples, the first registration request and the second registration request are transmitted via a non-terrestrial network, and the first mobile network is a home public land mobile network (HPLMN), an equivalent HPLMN (EHPLMN), or a registered public land mobile network (RPLMN). In some examples, the rejection message is an EMM reject message that includes a reject cause that indicates a PLMN identification associated with the first mobile network is not allowed to operate at a present location of the UE (e.g., EMM reject cause #78).

[0102] In some examples, the rejection message manager 730 is capable of, configured to, or operable to support a means for adding, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE. In some examples, the rejection message manager 730 is capable of, configured to, or operable to support a means for removing the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE has changed. In some examples, the second registration request is transmitted via a non-terrestrial network responsive to a loss of terrestrial network coverage at the UE.

[0103] In some examples, the first registration request and the second registration request are transmitted via a non-terrestrial network, and the PLMN registration manager 725 is capable of, configured to, or operable to support a means for establishing a connection with the first mobile network via the non-terrestrial network responsive to the second registration request. In some examples, the first registration request and the second registration request are transmitted via a non-terrestrial network, and the NTN communication manager 745 is capable of, configured to, or operable to support a means for transmitting or receiving one or more messages to or from the first mobile network via the non-terrestrial network.

[0104] FIG. 8 shows a diagram of a system 800 including a device 805 that supports techniques for recovery of network service based on location change in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

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

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

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

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

[0109] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for transmitting a first registration request to register with a first mobile network. The communications manager 820 is capable of, configured to, or operable to support a means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The communications manager 820 is capable of, configured to, or operable to support a means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0110] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for efficient recovery of services at a restricted network that provide for faster return to service due to event-based transmission of registration requests to a blocked network, increased availability of an NTN for emergency messaging or SOS communications, and / or power reduction from efficient throttling of registration attempts in cases where a UE location has not changed.[OHl] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combinationthereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of techniques for recovery of network service based on location change as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

[0112] FIG. 9 shows a flowchart illustrating a method 900 that supports techniques for recovery of network service based on location change in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0113] At 905, the method may include transmitting a first registration request to register with a first mobile network. The operations of block 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0114] At 910, the method may include receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The operations of block 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0115] At 915, the method may include initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The operations of block 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by a timer manager 735 as described with reference to FIG. 7.

[0116] At 920, the method may include transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer. The operations of block 920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0117] FIG. 10 shows a flowchart illustrating a method 1000 that supports techniques for recovery of network service based on location change in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0118] At 1005, the method may include transmitting a first registration request to register with a first mobile network. The operations of block 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0119] At 1010, the method may include receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The operations of block 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0120] At 1015, the method may include initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The operations of block 1015 may be performedin accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a timer manager 735 as described with reference to FIG. 7.

[0121] At 1020, the method may include determining that the timer has expired. The operations of block 1020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed by a timer manager 735 as described with reference to FIG. 7.

[0122] At 1025, the method may include refraining from transmitting a subsequent registration request to register with the first mobile network based on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request. The operations of block 1025 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1025 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0123] At 1030, the method may include transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer. The operations of block 1030 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1030 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0124] FIG. 11 shows a flowchart illustrating a method 1100 that supports techniques for recovery of network service based on location change in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0125] At 1105, the method may include transmitting a first registration request to register with a first mobile network. The operations of block 1105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0126] At 1110, the method may include receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The operations of block 1110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0127] At 1115, the method may include initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The operations of block 1115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed by a timer manager 735 as described with reference to FIG. 7.

[0128] At 1120, the method may include triggering a scan to detect a current mobile country code associated with the UE based on one or more trigger conditions. The operations of block 1120 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1120 may be performed by an MCC scan manager 740 as described with reference to FIG. 7.

[0129] At 1125, the method may include performing the scan to detect the current mobile country code associated with the UE. The operations of block 1125 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1125 may be performed by an MCC scan manager 740 as described with reference to FIG. 7.

[0130] At 1130, the method may include transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmittedirrespective of a status of the timer. The operations of block 1130 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1130 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0131] FIG. 12 shows a flowchart illustrating a method 1200 that supports techniques for recovery of network service based on location change in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0132] At 1205, the method may include transmitting a first registration request to register with a first mobile network. The operations of block 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

[0133] At 1210, the method may include receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE. The operations of block 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0134] At 1215, the method may include adding, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE. The operations of block 1215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0135] At 1220, the method may include initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during whichthe UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The operations of block 1220 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed by a timer manager 735 as described with reference to FIG. 7.

[0136] At 1225, the method may include removing the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE has changed. The operations of block 1225 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1225 may be performed by a rejection message manager 730 as described with reference to FIG. 7.

[0137] At 1230, the method may include transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer. The operations of block 1230 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1230 may be performed by an PLMN registration manager 725 as described with reference to FIG. 7.

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

[0139] Aspect 1 : A method for wireless communications by a UE, comprising: transmitting a first registration request to register with a first mobile network; receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE; initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network; and transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

[0140] Aspect 2: The method of aspect 1, further comprising: determining that the timer has expired; and refraining from transmitting a subsequent registration request to register with the first mobile network based at least in part on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

[0141] Aspect 3: The method of any of aspects 1 through 2, further comprising: triggering a scan to detect a current mobile country code associated with the UE based at least in part on one or more trigger conditions; and performing the scan to detect the current mobile country code associated with the UE.

[0142] Aspect 4: The method of aspect 3, wherein the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof.

[0143] Aspect 5: The method of aspect 4, wherein the wireless local area network coverage change detection includes one or more of a Wi-Fi coverage change detection or a Bluetooth coverage change detection.

[0144] Aspect 6: The method of any of aspects 3 through 5, wherein performing the scan to detect the current mobile country code comprises: scanning one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes.

[0145] Aspect 7: The method of any of aspects 1 through 6, wherein the first registration request and the second registration request are transmitted via a nonterrestrial network, and the first mobile network is a home public land mobile network (HPLMN), an equivalent HPLMN (EHPLMN), or a registered public land mobile network (RPLMN).

[0146] Aspect 8: The method of any of aspects 1 through 7, wherein the rejection message is an enhanced packet core (EPC) mobile management (EMM) reject message that includes a reject cause that indicates a public land mobile network (PLMN)identification associated with the first mobile network is not allowed to operate at a present location of the UE.

[0147] Aspect 9: The method of any of aspects 1 through 8, further comprising: adding, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE; and removing the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE has changed.

[0148] Aspect 10: The method of any of aspects 1 through 9, wherein the second registration request is transmitted via a non-terrestrial network responsive to a loss of terrestrial network coverage at the UE.

[0149] Aspect 11 : The method of any of aspects 1 through 10, wherein the first registration request and the second registration request are transmitted via a nonterrestrial network, and wherein the method further comprises: establishing a connection with the first mobile network via the non-terrestrial network responsive to the second registration request; and transmitting or receiving one or more messages to or from the first mobile network via the non-terrestrial network.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: transmit a first registration request to register with a first mobile network; receive a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE; initiate a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network; and transmit a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

2. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine that the timer has expired; and refrain from transmitting a subsequent registration request to register with the first mobile network based at least in part on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

3. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: trigger a scan to detect a current mobile country code associated with the UE based at least in part on one or more trigger conditions; andperform the scan to detect the current mobile country code associated with the UE.

4. The UE of claim 3, wherein the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof.

5. The UE of claim 4, wherein the wireless local area network coverage change detection includes one or more of a Wi-Fi coverage change detection or a Bluetooth coverage change detection.

6. The UE of claim 3, wherein, to perform the scan to detect the current mobile country code, the one or more processors are individually or collectively operable to execute the code to cause the UE to: scan one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes.

7. The UE of claim 1, wherein the first registration request and the second registration request are transmitted via a non-terrestrial network, and the first mobile network is a home public land mobile network (HPLMN), an equivalent HPLMN (EHPLMN), or a registered public land mobile network (RPLMN).

8. The UE of claim 1, wherein the rejection message is an enhanced packet core (EPC) mobile management (EMM) reject message that includes a reject cause that indicates a public land mobile network (PLMN) identification associated with the first mobile network is not allowed to operate at a present location of the UE.

9. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: add, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE; andremove the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE has changed.

10. The UE of claim 1, wherein the second registration request is transmitted via a non-terrestrial network responsive to a loss of terrestrial network coverage at the UE.

11. The UE of claim 1, wherein the first registration request and the second registration request are transmitted via a non-terrestrial network, and the one or more processors are individually or collectively further operable to execute the code to cause the UE to: establish a connection with the first mobile network via the nonterrestrial network responsive to the second registration request; and transmit or receive one or more messages to or from the first mobile network via the non-terrestrial network.

12. A method for wireless communications by a user equipment (UE), comprising: transmitting a first registration request to register with a first mobile network; receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE; initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network; and transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

13. The method of claim 12, further comprising:determining that the timer has expired; and refraining from transmitting a subsequent registration request to register with the first mobile network based at least in part on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

14. The method of claim 12, further comprising: triggering a scan to detect a current mobile country code associated with the UE based at least in part on one or more trigger conditions; and performing the scan to detect the current mobile country code associated with the UE.

15. The method of claim 14, wherein the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof.

16. The method of claim 15, wherein the wireless local area network coverage change detection includes one or more of a Wi-Fi coverage change detection or a Bluetooth coverage change detection.

17. The method of claim 14, wherein performing the scan to detect the current mobile country code comprises: scanning one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes.

18. The method of claim 12, wherein the first registration request and the second registration request are transmitted via a non-terrestrial network, and the first mobile network is a home public land mobile network (HPLMN), an equivalent HPLMN (EHPLMN), or a registered public land mobile network (RPLMN).

19. The method of claim 12, wherein the rejection message is an enhanced packet core (EPC) mobile management (EMM) reject message that includes a reject cause that indicates a public land mobile network (PLMN) identificationassociated with the first mobile network is not allowed to operate at a present location of the UE.

20. The method of claim 12, further comprising: adding, subsequent to receipt of the rejection message, an identification of the first mobile network to a blocked mobile network list at the UE; and removing the identification of the first mobile network from the blocked mobile network list at the UE responsive to detecting that the mobile country code associated with the UE has changed.

21. The method of claim 12, wherein the second registration request is transmitted via a non-terrestrial network responsive to a loss of terrestrial network coverage at the UE.

22. The method of claim 12, wherein the first registration request and the second registration request are transmitted via a non-terrestrial network, and wherein the method further comprises: establishing a connection with the first mobile network via the nonterrestrial network responsive to the second registration request; and transmitting or receiving one or more messages to or from the first mobile network via the non-terrestrial network.

23. A user equipment (UE) for wireless communications, comprising: means for transmitting a first registration request to register with a first mobile network; means for receiving a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE; means for initiating a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network; and means for transmitting a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission ofthe first registration request, the second registration request transmitted irrespective of a status of the timer.

24. The UE of claim 23, further comprising: means for determining that the timer has expired; and means for refraining from transmitting a subsequent registration request to register with the first mobile network based at least in part on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

25. The UE of claim 23, further comprising: means for triggering a scan to detect a current mobile country code associated with the UE based at least in part on one or more trigger conditions; and means for performing the scan to detect the current mobile country code associated with the UE.

26. The UE of claim 25, wherein the one or more trigger conditions include one or more of a physical cell identification set change during idle mode mobility at the UE, an out-of-service condition at the UE, a global navigation satellite system (GNSS) based location change of the UE, a wireless local area network coverage change detection, or any combinations thereof.

27. The UE of claim 25, wherein the means for performing the scan to detect the current mobile country code comprise: means for scanning one or more radio frequency channels to identify available public land mobile networks (PLMNs) and associated mobile country codes.

28. A non-transitory computer-readable medium storing code for wireless communications at a user equipment (UE), the code comprising instructions executable by one or more processors to: transmit a first registration request to register with a first mobile network; receive a rejection message that indicates a rejection of the first registration request and that the rejection is based on a location of the UE;initiate a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE is to refrain from transmitting one or more subsequent registration requests to register with the first mobile network; and transmit a second registration request to register with the first mobile network, the second registration request responsive to detecting that a mobile country code associated with the UE has changed subsequent to transmission of the first registration request, the second registration request transmitted irrespective of a status of the timer.

29. The non-transitory computer-readable medium of claim 28, wherein the instructions are further executable by the one or more processors to: determine that the timer has expired; and refrain from transmitting a subsequent registration request to register with the first mobile network based at least in part on the mobile country code associated with the UE being unchanged subsequent to transmission of the first registration request.

30. The non-transitory computer-readable medium of claim 28, wherein the instructions are further executable by the one or more processors to: trigger a scan to detect a current mobile country code associated with the UE based at least in part on one or more trigger conditions; and perform the scan to detect the current mobile country code associated with the UE.

Images