Techniques for restoring network services based on location changes

Abstract

Methods, systems, and devices are described for wireless communication that provide operation of a user equipment (UE) after receiving a rejection message in response to a registration request. Upon receiving a rejection message indicating a rejection of the location based on the UE, the UE may start a timer for a subsequent registration request and may monitor one or more conditions associated with the UE location. Upon detecting a change in UE location, the UE may retransmit the registration request regardless of the timer status. The one or more conditions associated with UE location may include, for example, a physical cell identity set change in idle mode mobility, a transition to a no-service state, satellite-based detection of a location change, a Wi-Fi / Bluetooth coverage change, or any combination thereof.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This Patent Application claims the benefit of Indian Patent Application No. 202341062451 by TARIMALA et al., entitled “TECHNIQUES FOR RECOVERY OF NETWORK SERVICE BASED ON LOCATION CHANGE” and filed September 16, 2023, assigned to the assignee of this Patent Application and fully incorporated herein by reference in its entirety for all purposes. TECHNICAL FIELD

[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 can 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 can be referred to as New Radio (NR) systems. These systems can 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 can include one or more base stations each simultaneously supporting communication with multiple communication devices, which can be otherwise known as user equipment (UE). SUMMARY

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

[0005] A method for wireless communication by a user equipment (UE) is described. The method can include transmitting a first registration request to register with a first mobile network, receiving a rejection message indicating a rejection of the first registration request, and the rejection being based on a location of the UE, starting a timer associated with the rejection message, a duration of the timer being associated with a time period during which the UE will 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 being transmitted in response to detecting that a mobile country code associated with the UE has changed after transmission of the first registration request, the second registration request being transmitted regardless of a status of the timer.

[0006] A UE for wireless communication is described. The UE can 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 are individually or collectively capable of operating 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 indicating rejection of the first registration request, and the rejection is based on a location of the UE, start a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE will 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 is transmitted in response to detecting that a mobile country code associated with the UE has changed after the transmission of the first registration request, the second registration request is transmitted regardless of a status of the timer.

[0007] Another UE for wireless communication is described. The UE can include means for transmitting a first registration request to register with a first mobile network, means for receiving a rejection message indicating rejection of the first registration request, and the rejection is based on a location of the UE, means for starting a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE will 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 is transmitted in response to detecting that a mobile country code associated with the UE has changed after the transmission of the first registration request, the second registration request is transmitted regardless of a status of the timer.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by a processor to transmit a first registration request to register with a first mobile network, receive a rejection message indicating rejection of the first registration request, and the rejection is based on a location of the UE, start a timer associated with the rejection message, a duration of the timer is associated with a time period during which the UE will 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 is transmitted in response to detecting that a mobile country code associated with the UE has changed after the transmission of the first registration request, the second registration request is transmitted regardless of a status of the timer.

[0009] Some examples of the method, UE, and non-transitory computer-readable medium described herein can 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 not changing after transmission of the first registration request.

[0010] Some examples of the method, UE, and non-transitory computer-readable medium described herein can 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, UE, and non-transitory computer-readable medium described herein, the one or more trigger conditions include one or more of a physical cell identity set change during idle mode mobility at the UE, an out-of-service condition at the UE, a location change of the UE based on a global navigation satellite system (GNSS), a wireless local area network coverage change detection, or any combination thereof. In some examples of the method, UE, 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, UE, and non-transitory computer-readable medium described herein, performing the scan to detect the current mobile country code can 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, UE, and non-transitory computer-readable medium described herein, the first registration request and the second registration request can be transmitted via a non-terrestrial network, and the first mobile network can 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, UE, and non-transitory computer-readable medium described herein, the rejection message can be an enhanced packet core (EPC) mobility management (EMM) reject message including a rejection cause indicating that a public land mobile network (PLMN) identity associated with the first mobile network can not be allowed to operate at a current location of the UE.

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

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

[0015] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the first registration request and the second registration request can be transmitted via a non-terrestrial network, and the methods, apparatuses, and non-transitory computer- readable medium can include further operations, features, means for, or instructions for establishing, via the non-terrestrial network, a connection with the first mobile network in response 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. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 An example of a wireless communications system that supports techniques for resuming network services based on location changes is shown.

[0017] Figure 2 An example of a portion of a wireless communications system that supports techniques for resuming network services based on location changes is shown.

[0018] Figure 3 And Figure 4 An example of a flow diagram illustrating a method that supports techniques for resuming network services based on location changes is shown.

[0019] Figure 5 And Figure 6 A block diagram of a device that supports techniques for resuming network services based on location changes is shown.

[0020] Figure 7 A block diagram of a communications manager that supports techniques for resuming network services based on location changes is shown.

[0021] Figure 8A diagram illustrating a system that includes a device that supports techniques for resuming network service based on a change in location in accordance with one or more aspects of the present disclosure is shown.

[0022] Figures 9 to 12 A flow diagram illustrating a method that supports techniques for resuming network service based on a change in location in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0023] In some wireless communications systems, one or more aerial-based platforms can be part of a non-terrestrial network (NTN) and can be used for some communications with user equipment (UEs). Such aerial platforms can include, for example, space satellites, balloons, airships, airplanes, drones, unmanned aerial vehicles, other aircraft, or any combination thereof, which can support communications from generally non-terrestrial, overhead, or high-altitude positions. As used herein, the term satellite can be used to generally refer to any such aerial platform. In some cases, a satellite can provide a relatively large coverage area, particularly as compared to terrestrial components such as ground base stations or ground transmission-reception points (TRPs). In some instances, such a relatively large coverage area can span the area of two or more countries.

[0024] In some NTN, a UE can connect with a public land mobile network (PLMN) via a satellite, which can provide enhanced network coverage for UEs that can not have terrestrial network coverage and can provide important communications and can be critical in emergency situations that can require emergency messaging or SOS communications. However, some countries do not allow connection to certain mobile networks (e.g., do not allow access to some PLMNs). For terrestrial networks, it is relatively straightforward to prohibit access to some networks, as such networks can simply avoid installing base stations or TRPs within or having coverage in restricted areas (e.g., by configuring antennas for coverage only for allowed communication areas). As discussed, NTN can have a relatively large coverage area, which can extend to restricted areas. Traditional techniques for preventing access to restricted PLMNs from a location (e.g., a country) where the PLMN is restricted include enhanced packet core (EPC) mobility management (EMM) procedures, which enable a PLMN to reject registration requests from UEs in restricted locations. For example, a UE can send a registration request to a PLMN, and the PLMN can reject the request with a rejection cause indicating that the UE is in a restricted area (e.g., EMM rejection cause #78) (e.g., EMM rejection cause #78). Subsequent registration requests can be sent upon expiration of an associated timer (e.g., a one hour timer), or if the location of the UE has changed by a certain amount (e.g., if the location of the UE has changed by at least 50 km). However, timer-based subsequent registration requests can result in increased power consumption, and are likely to be unsuccessful if the location of the UE has not changed. Moreover, location-based subsequent requests can not be sent until the timer expires, which can result in unnecessary delay in sending the subsequent registration request.

[0025] According to various aspects as discussed herein, a subsequent registration request can be transmitted based on the UE determining that the registration request has an increased likelihood of success, regardless of the status of a timer initiated upon receiving a rejection message. In some aspects, after receiving a registration rejection message for accessing a PLMN (e.g., via an NTN), a UE can initiate a timer for a subsequent registration request, but can transmit the subsequent registration request upon detecting a mobile country code (MCC) change at the UE regardless of the timer status. Such techniques can allow the UE to transmit a request immediately upon MCC change detection, which improves access latency. Additionally or alternatively, the UE can refrain from transmitting a registration request when the MCC has not changed, which can reduce power consumption by reducing transmissions. In some aspects, the MCC change can be determined based on PLMN scanning at the UE and a detected MCC of a PLMN. Such PLMN scanning can be triggered by one or more detected conditions at the UE, such as a physical cell identity (PCI) set change 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 combination thereof. In some aspects, if the MCC has changed at the UE, the PLMN can be removed from a blocked PLMN list and a subsequent registration request can be transmitted (e.g., via the NTN).

[0026] In the case of coverage loss of an unrestricted network, such techniques can provide faster service restoration due to event-based transmission of registration requests after notification that a PLMN is restricted or blocked, regardless of a timer associated with the blocked PLMN. Such reduced restoration time can, for example, result in increased availability of an NTN, which can be critical in emergency situations such as emergency messaging or SOS communication. Moreover, such techniques can provide efficient throttling of registration attempts without a change in UE location.

[0027] Aspects of the disclosure are first described in the context of a wireless communications system. Aspects of the disclosure are further illustrated by and described in connection with apparatus diagrams, system diagrams, and flowcharts relating to techniques for restoring network service based on location change.

[0028] Figure 1An example of a wireless communications system 100 that supports techniques for resuming network services based on location changes is shown, in accordance with one or more aspects of the present disclosure. The wireless communications system 100 can include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 can be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, a New Radio (NR) network, or a network operating according to some other wireless communications technology including future iterations of the aforementioned systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0029] The network entities 105 can be dispersed throughout the geographic area of a wireless communication system 100, and can each include devices that are in different forms or have different capabilities. In various examples, the network entities 105 can be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other examples. In some examples, the network entities 105 and the UEs 115 can wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, a network entity 105 can support a coverage area 110 (e.g., a geographic coverage area) within which the network entity 105 and the UEs 115 can establish one or more communication links 125. The coverage area 110 can be an example of a geographic area within which a network entity 105 and a UE 115 can support communication in accordance with one or more radio access technologies (RATs).

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

[0031] ​As described herein, a node of the wireless communications system 100, which can be referred to as a network node or a wireless node, can be a network entity 105 (e.g., any of the network entities described herein), a UE 115 (e.g., any of the UEs described herein), a network controller, a device, an apparatus, 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 can be a UE 115. As another example, a node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different with respect to these examples. Similarly, references to a UE 115, a network entity 105, a device, an apparatus, a computing system, and the like can include the disclosure of the UE 115, the network entity 105, the device, the apparatus, the computing system, and the like as a node. For example, a disclosure of a UE 115 configured to receive information from a network entity 105 also discloses a first node configured to receive information from a second node.

[0032] In some examples, the network entities 105 can communicate with the core network 130, or with each other, or both. For example, the network entities 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an SI, N2, N3, or other interface protocol). In some examples, the network entities 105 can communicate with each other via the backhaul communication links 120 (e.g., directly between the network entities 105, or indirectly via the core network 130, or both). In some examples, the network entities 105 can communicate with each other via the midhaul communication links 162 (e.g., according to a midhaul interface protocol) or the front-haul communication links 168 (e.g., according to a front-haul interface protocol), or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the front-haul communication links 168 can be or include one or more wired links (e.g., electrical, fiber optic), one or more wireless links (e.g., radio, wireless optical), etc., or various combinations thereof. The UEs 115 can communicate with the core network 130 via communication links 155.

[0033] One or more of the network entities 105 described herein can include or can be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, a 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 can 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, the network entity 105 (e.g., base station 140) can be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that can be configured to utilize a protocol stack integrated physically or logically within a single network entity 105 (e.g., a single RAN node such as a base station 140).

[0034] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack distributed physically or logically between two or more network entities 105 such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can 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. The RU 170 can also be referred to as a radio head, an intelligent 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 entity 105 in the disaggregated RAN architecture can be co-located, or one or more components of the network entity 105 can be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0035] The functional split between the CU 160, the DU 165, and the RU 170 is flexible and can support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at the CU 160, the DU 165, or the RU 170. For example, a functional split of a protocol stack can be employed between the CU 160 and the DU 165, such that the CU 160 can support one or more layers of the protocol stack, and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can connect to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 can 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 can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of a protocol stack can be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 can be further split in functionality into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU 160 can connect to one or more DUs 165 via a backhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and the DU 165 can connect to one or more RUs 170 via a front-haul communication link 168 (e.g., open front-haul (FH) interface). In some examples, the backhaul communication link 162 or the front-haul communication link 168 can be implemented in accordance with an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 105 that communicate via such communication links.

[0036] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections to provide an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by one another. One or more IAB nodes 104 can be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate 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). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled DU 165 of an IAB donor. The IAB-MT can include a separate set of antennas for relaying communications with UEs 115 or can share the same antennas (e.g., of a RU 170) of the IAB node 104 for accessing via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 can include a DU 165 that supports a communication link with an additional entity (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of an access network. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) can be configured to operate according to the techniques described herein.

[0037] In cases where the techniques described herein apply in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture can be configured to support techniques for resuming network services based on location changes as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0038] A UE 115 can include or can 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” can also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 can also include or can 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 can include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which can be implemented in various objects such as appliances or vehicles, among other examples.

[0039] The UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115 that can sometimes act as relays or Figure 1 as shown.

[0040] The UEs 115 and the network entities 105 can wirelessly communicate with each other using resources associated with one or more carriers via one or more communication links 125 (e.g., access links). The term “carrier” can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier used for a communication link 125 can include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating 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 can carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. The wireless communications system 100 can support communication with UEs 115 using carrier aggregation or multi-carrier operation. According to carrier aggregation, a UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communications between a network entity 105 and other devices can refer to communications between those devices and any part of the network entity 105 (e.g., an entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” can refer to any part 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 carrier aggregation configurations, a carrier can also have acquisition signaling or control signaling that coordinates operations of other carriers. A carrier can be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be identified according to a channel raster for discovery by UEs 115. A carrier can be operated in a standalone mode where initial acquisition and connection can be performed by a UE 115 via the carrier, or the carrier can be operated in a non-standalone mode where a different carrier (e.g., of a same or different radio access technology) is used for anchoring connection.

[0042] The communication links 125 shown in wireless communication system 100 can include downlink transmissions from a network entity 105 to a UE 115, uplink transmissions from a UE 115 to a network entity 105, or both, as well as other transmissions. A carrier can carry downlink or uplink communications (e.g., in an FDD mode) or can be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0043] A carrier can be associated with a particular bandwidth of the RF spectrum, and in some examples the carrier bandwidth can be referred to as a “system bandwidth” of the carrier or wireless communication system 100. For example, the carrier bandwidth can 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 wireless communication system 100 (e.g., network entities 105, UEs 115, or both) can have hardware configurations that support communications using a particular carrier bandwidth or can be configurable to support communications using one of a set of carrier bandwidths. In some examples, wireless communication system 100 can 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 can be configured for operating

[0044] Signal waveforms transmitted over a carrier can include 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 can refer to a resource comprising a symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing can be inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) so that the relative amounts of data carried by different resource elements (e.g., in a transmission duration) can be adjusted by adjusting the modulation scheme or coding rate associated with those resource elements. The wireless communications resource can refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data capacity for communications with a UE 115.

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

[0046] Time intervals for the network entity 105 or the UE 115 can be expressed in multiples of a basic time unit, which may, for example, refer to a sampling period of seconds, where may represent supported subcarrier spacings, and may represent supported discrete Fourier transform (DFT) sizes. Time intervals of a communications resource can be organized as radio frames, each

[0047] Each frame can include a plurality of consecutive numbered subframes or slots, and each subframe or slot can have the same duration. In some examples, a frame can be divided (e.g., in the time domain) into subframes, and each subframe can be further divided into a number of slots. Alternatively, each frame can include a variable number of slots, and the number of slots can depend on the subcarrier spacing. Each slot can include a number 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 can be further divided into multiple mini-slots. Each symbol period can be associated with a number of subcarriers (e.g., in the frequency domain).​ A symbol period can be associated with one or more sampling periods. The duration of a symbol period can depend on a subcarrier spacing or a band of operation.

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

[0049] According to various techniques, physical channels can be multiplexed for communication using a carrier. A physical control channel and a physical data channel can 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)) of a physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information according to one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner in one or more aggregation levels. An aggregation level of a control channel candidate can refer to a quantity of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. A search space set can include common search space sets configured for transmitting control information to multiple UEs 115, and UE-specific search space sets for transmitting control information to a specific UE 115.

[0050] The network entity 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" can refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and can be associated with a identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifiers) used by a UE 115 to identify a cell. In some examples, a cell can also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which a logical communication entity operates. The range of such a cell can vary depending on various factors such as the capabilities of the network entity 105. For example, a cell can be a building, a subset of a building, or an outdoor space between or overlapping with coverage areas 110, or can include a building, a subset of a building, or an outdoor space between or overlapping with coverage areas 110, etc.

[0051] A macro cell generally covers a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell can be associated with a lower power network entity 105 (e.g., a low power base station 140) and can operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell can provide restricted access by UEs 115 with service subscriptions with the network provider supporting the small cell, or restricted access by UEs 115 in an open (e.g., non subscription-based) model. A network entity 105 can support one or multiple cells, and can also use one or multiple component carriers to support communications via one or more cells.

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

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

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

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

[0056] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or 5G core (5GC), which can include at least one control plane entity that can manage 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 can route packets or interconnect 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 can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets can be transferred through the user plane entity, which can provide IP address allocation as well as other functions. The user plane entity can be connected to the IP services 150 of the one or more network operators. The IP services 150 can include access to the Internet, Intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0057] The wireless communications system 100 can operate using one or more frequency bands, 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, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors. The use of UHF frequencies, however, can support relatively large cells, and can enable use of smaller antennas than those used for smaller frequencies, which can support larger

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

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

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

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

[0062] In some examples, a cell can be provided or established by satellite 190 as part of an NTN. In some cases, satellite 190 can perform the functions of network entity 105, act as a bent pipe satellite, or act as a regenerative satellite, or a combination thereof. In some examples, satellite 190 can be an example of a smart satellite or a satellite with intelligence or other communication processing capabilities. For example, a smart satellite can be configured to perform more functions than a regenerative satellite (e.g., can be configured to perform specific algorithms in addition to the algorithms used in a regenerative satellite in order to be reprogrammed). In a bent pipe transponder configuration, satellite 190 can be configured to receive signals from a ground station (e.g., a gateway, network entity 105, core network 130) and transmit those signals to a different ground station or terminal (e.g., UE 115, network entity 105). In some cases, satellite 190 supporting a bent pipe transponder configuration can amplify signals, or convert from an uplink frequency to a downlink frequency. In some examples, satellite 190 supporting a regenerative transponder configuration can relay signals like a bent pipe transponder configuration, but can also perform other functions using onboard processing. Examples of these other functions can include demodulating received signals, decoding received signals, re-encoding signals to be transmitted, modulating signals to be transmitted, or a combination thereof. In some examples, satellite 190 supporting a bent pipe transponder configuration or a regenerative transponder configuration can receive signals from network entity 105 and can relay the signals to UE 115 or network entity 105, or vice versa.

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

[0064] Figure 2 An example of a wireless communications system 200 that supports techniques for resuming network services based on location changes is shown in accordance with one or more aspects of the present disclosure. In Figure 2 In examples, the UE 115-a can 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 can be an example of a terrestrial network entity or a non-terrestrial network entity with a coverage area or cell 110-a. Additionally, or alternatively, the NTN TRP 205 can be an example of an NTN network entity and can be associated with a coverage area or cell 110-b.

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

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

[0067] According to various aspects as discussed herein, a subsequent registration request can be transmitted based on the UE 115-a determining that the subsequent registration request 230 has an increased likelihood of success, regardless of the status of the timer. In some aspects, after receiving the registration rejection message 235, the UE can transmit a subsequent registration request when a MCC change is detected at the UE 115-a, regardless of the timer status. Such techniques can allow the UE 115-a to transmit a request immediately upon MCC change detection, which improves access latency. Moreover, in some cases, the UE can refrain from transmitting a subsequent registration request when the MCC has not changed, which can reduce power consumption by reducing transmissions that have a lower likelihood of resulting in a network connection. In some aspects, the MCC change can be determined based on PLMN scanning at the UE 115-a and a detected MCC of a PLMN. Such PLMN scanning can be triggered by one or more detected conditions at the UE 115-a, such as a PCI set change 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 combination thereof. In some aspects, if the MCC has changed at the UE 115-a, the PLMN can be removed from the blocked PLMN list, and a subsequent registration request can be transmitted (e.g., via the NTN).

[0068] Figure 3 An example illustrates a flow diagram of a method 300 that supports techniques for resuming network service based on location changes in accordance with one or more aspects of the present disclosure. In some examples, the method 300 can implement aspects as referenced with Figure 1 and Figure 2Aspects of the wireless communications system 100 or 200 are described or enabled by these aspects. In some examples, Figure 3 The operations illustrated in FIG. 3 can 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 can be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps can include additional features not mentioned below, or other steps can be added.

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

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

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

[0072] At 320, the UE can monitor a set of events to determine whether the MCC of the UE has changed. In some cases, the set of events can include one or more of a change in a set of PCIs due to 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 change in GNSS-based location, a change in Wi-Fi or Bluetooth coverage, or any combination thereof. If one of these events has occurred, the event can indicate a change in location of the UE and trigger the UE to perform a PLMN scan to determine the MCC of the UE based on the MCC of a detected PLMN.

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

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

[0075] Figure 4 Another example illustrating a flow chart of a method 400 that supports techniques for resuming network service based on location change in accordance with one or more aspects of the present disclosure is shown. In some examples, the method 400 can implement aspects of, or be implemented by, a wireless communication system 100 or 200, as described with reference to FIGs. 1 and 2. In some examples, the method 400 can implement aspects of, or be implemented by, a UE 115 or 215, as described with reference to FIGs. 1 and 2. Figure 1 and Figure 2 In some examples, the operations illustrated in Figure 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 can be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps can include additional features not mentioned below, or other steps can be added.

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

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

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

[0079] At 420, the UE can monitor a set of events to determine whether the MCC of the UE has changed. In some cases, the set of events can include one or more of a change in a set of PCIs due to 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 combination thereof. If one of these events has occurred, the event can indicate a change in location of the UE and trigger the UE to perform a PLMN scan to determine the MCC of the UE based on the MCC of a detected PLMN.

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

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

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

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

[0084] The receiver 510 can provide 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 resuming network service based on location change). Information can be passed on to other components of the device 505. The receiver 510 can utilize a single antenna or a set of multiple antennas.

[0085] The transmitter 515 can provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 can 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 resuming network service based on location change). In some examples, the transmitter 515 can be collocated with the receiver 510 in a transceiver module. The transmitter 515 can 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 can be examples of means for performing various aspects of techniques for resuming 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 can 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 can be implemented in hardware (e.g., in communications management circuitry). The hardware can include at least one of the following: 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 microcode circuit, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof. In some examples, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., the at least one processor executing instructions stored in the at least one memory).

[0088] Additionally or alternatively, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof, can 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 communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof, can be executed 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 the components described in this disclosure to perform the functions described in this disclosure).

[0089] In some examples, the communication manager 520 can 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 communication manager 520 can receive information from the receiver 510, transmit 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 communication manager 520 can support wireless communication in accordance with examples as disclosed herein. For example, the communication manager 520 can be capable of, configured to, or operable to support means for transmitting a first registration request to register with a first mobile network. The communication manager 520 can be capable of, configured to, or operable to support means for receiving a rejection message indicating a rejection of the first registration request, and the rejection is based on a location of the UE. The communication manager 520 can be capable of, configured to, or operable to support means for starting a timer associated with the rejection message, a duration of the timer being associated with a time period during which the UE will refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The communication manager 520 can be capable of, configured to, or operable to support means for transmitting a second registration request to register with the first mobile network, the second registration request being transmitted in response to detecting that a mobile country code associated with the UE has changed after transmission of the first registration request, the second registration request being transmitted regardless 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 of the device 505 coupled with or otherwise controlling or otherwise in communication with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) can support techniques for efficient recovery of services at a restricted network that provide faster return of services due to event-based transmission of registration requests to a blocked network, increased availability of NTNs for emergency messaging or SOS communications, and / or reduced power through efficient throttling of registration attempts where the UE location has not changed.

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

[0093] The receiver 610 can 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 services based on location changes). Information can be passed on to other components of the device 605. The receiver 610 can utilize a single antenna or a set of multiple antennas.

[0094] The transmitter 615 can provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can 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 services based on location changes). In some examples, the transmitter 615 can be collocated with the receiver 610 in a transceiver module. The transmitter 615 can utilize a single antenna or a set of multiple antennas.

[0095] The device 605, or various components thereof, can be an example of means for performing various aspects of techniques for resuming network service based on location changes as described herein. For example, the communications manager 620 can include a PLMN registration manager 625, a rejection message manager 630, a timer manager 635, or any combination thereof. The communications manager 620 can be an example of aspects of the communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 can receive information from the receiver 610, transmit 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 can support wireless communication in accordance with examples as disclosed herein. The PLMN registration manager 625 can enable, be configured as, or be operable to support means for transmitting a first registration request to register with a first mobile network. The rejection message manager 630 can enable, be configured as, or be operable to support means for receiving a rejection message indicating a rejection of the first registration request, and the rejection is based on a location of the UE. The timer manager 635 can enable, be configured as, or be operable to support means for starting a timer associated with the rejection message, a duration of the timer being associated with a time period during which the UE will refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The PLMN registration manager 625 can enable, be configured as, or be operable to support means for transmitting a second registration request to register with the first mobile network, the second registration request being transmitted in response to detecting that a mobile country code associated with the UE has changed since the transmission of the first registration request, the second registration request being transmitted regardless of a status of the timer.

[0097] Figure 7A block diagram 700 of a communications manager 720 that supports techniques for resuming network services based on location changes is shown, in accordance with one or more aspects of the present disclosure. The communications manager 720 can 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, can be an example of means for performing various aspects of techniques for resuming network services based on location changes, as described herein. For example, the communications manager 720 can include a PLMN registration manager 725, a rejection message manager 730, a timer manager 735, a MCC scan manager 740, an NTN communication manager 745, or any combination thereof. Each of these components, or the components or sub-components thereof (e.g., one or more processors, one or more memories), can communicate, directly or indirectly, with one another (e.g., via one or more buses).

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

[0099] In some examples, the timer manager 735 can enable, be configured as, or be operable to support means for determining that the timer has expired. In some examples, the rejection message manager 730 can enable, be configured as, or be operable to support 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 not changing after transmission of the first registration request.

[0100] In some examples, the MCC scan manager 740 can be, be configured as, or be operable with 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 can be, be configured as, or be operable with 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 identity set change during idle mode mobility at the UE, an out-of-service condition at the UE, a location change of the UE based on a global navigation satellite system (GNSS), a wireless local area network coverage change detection, or any combination 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 can be, be configured as, or be operable with 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 rejection message including a rejection cause indicating that a PLMN identity associated with the first mobile network is not allowed to operate at a current location of the UE (e.g., EMM rejection cause #78).

[0102] In some examples, the rejection message manager 730 can be, be configured as, or be operable with a means for adding, after receiving the rejection message, an identity of the first mobile network to a blocked mobile network list at the UE. In some examples, the rejection message manager 730 can be, be configured as, or be operable with a means for removing, at the UE, the identity of the first mobile network from the blocked mobile network list in response 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 in response 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 means for establishing a connection with the first mobile network via the non-terrestrial network in response 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 means for transmitting or receiving one or more messages to or from the first mobile network via the non-terrestrial network.

[0104] Figure 8 A diagram illustrating a system 800 including a device 805 that supports techniques for resuming network services based on location changes in accordance with one or more aspects of the present disclosure is shown. The device 805 can be an example of or include the components of device 505, device 605, or a UE 115 as described herein. The device 805 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 805 can 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 can 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 can manage input and output signals for the device 805. The I / O controller 810 can also manage peripherals ® , ANDROID ® , MS-DOS ® , MS-WINDOWS ® , OS / 2 ® , UNIX ® , LINUX ®or another known operating system. Additionally, or alternatively, I / O controller 810 can represent a modem, a keyboard, a mouse, a touchscreen, or a similar device, or interaction with such a device. In some cases, I / O controller 810 can be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user can interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

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

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

[0108] The at least one processor 840 can 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 can be configured to operate a memory array using a memory controller. In some other cases, a memory controller can be integrated into the at least one processor 840. The at least one processor 840 can 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 resuming network service based on location changes). For example, the device 805 or a component of the device 805 can include the at least one processor 840 and the at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein. In some examples, the at least one processor 840 can include a plurality of processors, and the at least one memory 830 can include a plurality of memories. One or more processors in the plurality of processors can be coupled with one or more memories in the plurality of memories, which can be individually or collectively configured to perform various functions herein. In some examples, the at least one processor 840 can be a component of a processing system that can refer to a machine (such as a series of machines), a circuit (including, for example, one or both of a processor circuit (which can include the at least one processor 840) and a memory circuit (which can include the at least one memory 830)), or a system of components that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system can be configured to perform one or more of the functions described herein. As such, the at least one processor 840, or a processing system that includes the at least one processor 840, can be configured to, capable of being configured to, or operable to cause the device 805 to perform one or more of the functions described herein. Moreover, as described herein, “configured to,” “capable of being configured to,” and “operable to” can be used interchangeably and can be associated with the ability of the at least one processor 840, or a processing system that includes the at least one processor 840, to perform one or more of the functions described herein when executing code stored in the at least one memory 830 or otherwise.

[0109] The communications manager 820 can support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 820 can enable, be configured as, or be operable to support a means for transmitting a first registration request to register with a first mobile network. The communications manager 820 can enable, be configured as, or be operable to support a means for receiving a rejection message indicating a rejection of the first registration request, and the rejection is based on a location of the UE. The communications manager 820 can enable, be configured as, or be operable to support a means for starting a timer associated with the rejection message, a duration of the timer being associated with a time period during which the UE will refrain from transmitting one or more subsequent registration requests to register with the first mobile network. The communications manager 820 can enable, be configured as, or be operable to support a means for transmitting a second registration request to register with the first mobile network, the second registration request being transmitted in response to detecting that a mobile country code associated with the UE has changed after the transmission of the first registration request, the second registration request being transmitted regardless 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 can support techniques for efficient recovery of service at a restricted network that provide faster return of service due to event-based transmission of registration requests to a blocked network, increased availability of NTNs for emergency messaging or SOS communications, and / or efficient throttling of registration attempts to reduce power in cases where the UE location has not changed.

[0111] In some examples, the communications manager 820 can be configured to perform or otherwise support the 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 can be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 can 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 changes as described herein, or the at least one processor 840 and the at least one memory 830 can be otherwise configured to, individually or collectively, perform or support performance of such operations.

[0112] Figure 9 A flow diagram illustrating a method 900 that supports techniques for recovery of network service based on location changes in accordance with aspects of the present disclosure is shown. The operations of method 900 can be implemented by a UE or its components as described herein. For example, the operations of method 900 can be performed by a UE as described with reference to FIGs. 1-8. Figures 1 to 8The UEs 115 described are configured to perform the operations described. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the operations described. Additionally or alternatively, the UE can perform various aspects of the operations described using special-purpose hardware.

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

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

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

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

[0117] Figure 10 A flow diagram illustrating a method 1000 that supports techniques for resuming network service based on location changes in accordance with aspects of the present disclosure is shown. The operations of method 1000 can be implemented by a UE or its components as described herein. For example, the operations of method 1000 can be performed by a UE 115 as described with reference to Figures 1 to 8 FIG. 1. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the operations described. Additionally or alternatively, the UE can perform various aspects of the operations described using special-purpose hardware. FIG. 1. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the operations described. Additionally or alternatively, the UE can perform various aspects of the operations described using special-purpose hardware.

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

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

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

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

[0122] At 1025, the method can 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 not changing after transmission of the first registration request. The operations of block 1025 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1025 can be performed by a rejection message manager 730 as described with reference to FIG. 6. Figure 7

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

[0124] ​​​​​​Figure 11 A flow diagram illustrating a method 1100 that supports techniques for resuming network services based on location changes in accordance with aspects of the present disclosure is shown. The operations of method 1100 can be implemented by a UE or its components as described herein. For example, the operations of method 1100 can be performed by a UE 115 as described with reference to FIGs. 1-2. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware. Figures 1 to 8

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

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

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

[0128] At 1120, the method can 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 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1120 can be performed by a MCC scan manager 740 as described with reference to FIG. 5. Figure 7

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

[0130] At 1130, the method can include transmitting a second registration request to register with the first mobile network, the second registration request being transmitted in response to detecting that a mobile country code associated with the UE has changed after transmission of the first registration request, the second registration request being transmitted regardless of the state of the timer. The operations of block 1130 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1130 can be performed by a PLMN registration manager 725 as described with reference to Figure 7 FIG. 7.

[0131] Figure 12 A flow diagram illustrating a method 1200 that supports techniques for resuming network services based on location changes in accordance with aspects of the present disclosure is shown. The operations of method 1200 can be implemented by a UE or its components as described herein. For example, the operations of method 1200 can be performed by a UE 115 as described with reference to Figures 1 to 8 FIG. 1. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

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

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

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

[0135] At 1220, the method may include initiating a timer associated with the rejection message, the duration of which is associated with a time period during which the UE will avoid sending one or more subsequent registration requests to the first mobile network. Operation of block 1220 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1220 may be provided by reference to [reference needed]. Figure 7 The timer manager 735 described is used for execution.

[0136] At 1225, the method may include removing the identifier of the first mobile network from the blocked mobile network list at the UE in response to detecting that the mobile country code associated with the UE has changed. Operation of block 1225 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1225 may be provided by reference to [reference needed]. Figure 7 The described rejection message manager 730 is used to execute.

[0137] At 1230, the method may include sending a second registration request to the first mobile network, the second registration request being sent in response to detection that the mobile country code associated with the UE has changed after the sending of the first registration request, regardless of the state of the timer. The operation of block 1230 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1230 may be provided by reference to [reference needed]. Figure 7 The PLMN Registration Manager 725 described is used for execution.

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

[0139] Aspect 1: A method for wireless communication by a UE, the method comprising: sending a first registration request to register with a first mobile network; receiving a rejection message indicating a rejection of the first registration request, the rejection being based on the location of the UE; starting a timer associated with the rejection message, the duration of the timer being associated with a time period during which the UE will avoid sending one or more subsequent registration requests to register with the first mobile network; and sending a second registration request to register with the first mobile network in response to detection that a mobile country code associated with the UE has changed after the sending of the first registration request, the second registration request being sent regardless of the state of the timer.

[0140] Aspect 2: According to the method of aspect 1, the method further includes: determining that the timer has expired; and avoiding sending a subsequent registration request to register with the first mobile network, based at least in part on the fact that the mobile country code associated with the UE has not changed after the first registration request was sent.

[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 comprise one or more of: a physical cell identity set change during idle mode mobility at the UE, an out-of-service condition at the UE, a location change of the UE based on a global navigation satellite system (GNSS), a wireless local area network coverage change detection, or any combination thereof.

[0143] Aspect 5: The method of aspect 4, wherein the wireless local area network coverage change detection comprises 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 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).

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

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

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

[0149] Aspect 11: The method of any of aspects 1-10, 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 non-terrestrial network in response 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 communication, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of individually or collectively executing the code to cause the UE to perform the method of any of aspects 1-11.

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

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

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

[0154] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system can be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology can 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 can be applicable to various other wireless communication 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, and others.

[0155] Information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can 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 can be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a 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. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. The processor can 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). The various functions and operations described herein as being able to be performed by the processor can alternatively be performed by the processor in cooperation with one or more other processors.

[0157] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions can 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 place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can 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 can be used to carry or store desired program code means in the form of instructions or data structures and that can 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 where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Any functions or operations described herein that are capable of being performed by a memory can be performed by a plurality of memories capable of performing the described functions or operations individually or collectively.

[0159] As used herein, including in the claims “or” as used in a list of items (for example, 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” can 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" preceding a noun is an open, indefinite article, and is to be construed to mean "at least one" or "one or more" of the noun. Therefore, the terms "a," "at least one," "one or more," and "at least one of each" are interchangeable. For example, where a claim recites "a component" of performing one or more functions, it is to be understood that each function of the individual function can be performed by a single component or by any combination of more components. Therefore, the term "component" having a particular characteristic or performing a particular function can refer to "at least one of each component" having that characteristic or performing that function. A subsequent reference to "the component" in the claim, where the claim has been introduced by the article "a" or "an," can refer to any or all of the components. For example, a component introduced by the article "a" or "an" can be understood to mean "one or more components," and a subsequent reference to "the component" in the claim can be understood as a reference to "at least one of each of the one or more components." Similarly, a subsequent reference to "the component" introduced by the article "the" or "said" as "one or more components" can refer to any or all of the one or more components. For example, a subsequent reference to "the one or more components" in the claim can be understood as a reference to "at least one of each of the one or more components."

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

[0162] In the drawings, like components or features can have the same reference label. Also, various components of the same type can be distinguished by following the reference label by a dash and a second label that distinguishes among the components. If only 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.

[0163] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that can 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” over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, can be practiced without these specific details. In some instances, well-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 presented to enable any person skilled in the art to practice or use the present disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be 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

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Send a first registration request to register with the first mobile network; Receive a rejection message, the rejection message indicating a rejection of the first registration request, and the rejection is based on the location of the UE; A timer associated with the rejection message is started, the duration of which is associated with a time period during which the UE will avoid sending one or more subsequent registration requests to the first mobile network. as well as A second registration request is sent to the first mobile network in response to the detection that the mobile country code associated with the UE has changed after the first registration request was sent. The second registration request is sent regardless of the state of the timer.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: It has been determined that the timer has expired; and At least in part, this is based on the fact that the mobile country code associated with the UE did not change after the first registration request was sent, thus avoiding the sending of subsequent registration requests to the first mobile network.

3. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The scan is triggered at least in part based on one or more triggering conditions to detect the current mobile country code associated with the UE; and The scan is performed to detect the current mobile country code associated with the UE.

4. The UE of claim 3, wherein the one or more triggering conditions include one or more of the following: a change in the physical cell identifier set during idle mode mobility at the UE, a no-service condition at the UE, a change in the location of the UE based on a Global Navigation Satellite System (GNSS), a change in wireless local area network coverage detection, or any combination thereof.

5. The UE according to claim 4, wherein the wireless LAN coverage change detection includes one or more of Wi-Fi coverage change detection or Bluetooth coverage change detection.

6. The UE according to claim 3, wherein, In order to perform the scan to detect the current country code, the one or more processors can operate individually or jointly to execute the code so that the UE: 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 sent 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) Mobility Management (EMM) rejection message including a rejection reason indicating that a Public Land Mobile Network (PLMN) identifier associated with the first mobile network is not permitted to operate at the current location of the UE.

9. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Upon receiving the rejection message, the identifier of the first mobile network is added to the blocked mobile network list at the UE; and In response to the detection that the mobile country code associated with the UE has changed, the identifier of the first mobile network is removed from the list of blocked mobile networks at the UE.

10. The UE of claim 1, wherein the second registration request is sent via a non-terrestrial network in response 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 sent via a non-terrestrial network, and the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: In response to the second registration request, a connection is established with the first mobile network via the non-terrestrial network; and Sending or receiving one or more messages to or from the first mobile network via the non-terrestrial network.

12. A method for wireless communication by a user equipment (UE), the method comprising: Send a first registration request to register with the first mobile network; Receive a rejection message, the rejection message indicating a rejection of the first registration request, and the rejection is based on the location of the UE; A timer associated with the rejection message is started, the duration of which is associated with a time period during which the UE will avoid sending one or more subsequent registration requests to the first mobile network. as well as A second registration request is sent to the first mobile network in response to the detection that the mobile country code associated with the UE has changed after the first registration request was sent. The second registration request is sent regardless of the state of the timer.

13. The method according to claim 12, further comprising: It has been determined that the timer has expired; as well as At least in part, this is based on the fact that the mobile country code associated with the UE did not change after the first registration request was sent, thus avoiding the sending of subsequent registration requests to the first mobile network.

14. The method according to claim 12, further comprising: The scan is triggered at least in part based on one or more triggering conditions to detect the current mobile country code associated with the UE; as well as The scan is performed to detect the current mobile country code associated with the UE.

15. The method of claim 14, wherein the one or more triggering conditions include one or more of the following: a change in the physical cell identifier set during idle mode mobility at the UE, a no-service condition at the UE, a change in the location of the UE based on a Global Navigation Satellite System (GNSS), a change in wireless local area network coverage detection, or any combination thereof.

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

17. The method of claim 14, wherein performing the scan to detect the current country code comprises: Scan 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 sent 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) mobility management (EMM) rejection message including a rejection reason indicating that a Public Land Mobile Network (PLMN) identifier associated with the first mobile network is not permitted to operate at the current location of the UE.

20. The method according to claim 12, further comprising: Upon receiving the rejection message, the identifier of the first mobile network is added to the blocked mobile network list at the UE; as well as In response to the detection that the mobile country code associated with the UE has changed, the identifier of the first mobile network is removed from the list of blocked mobile networks at the UE.

21. The method of claim 12, wherein the second registration request is sent via a non-terrestrial network in response 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 sent via a non-terrestrial network, and wherein the method further comprises: In response to the second registration request, a connection is established with the first mobile network via the non-terrestrial network; as well as Sending 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 communication, the user equipment (UE) comprising: Components used to send a first registration request to register with a first mobile network; A component for receiving a rejection message, the rejection message indicating a rejection of the first registration request, and the rejection being based on the location of the UE; A component for starting a timer associated with the rejection message, the duration of which is associated with a time period during which the UE will avoid sending one or more subsequent registration requests to the first mobile network; and A component for sending a second registration request to register with the first mobile network, the second registration request being sent in response to the detection that the mobile country code associated with the UE has changed after the sending of the first registration request, regardless of the state of the timer.

24. The UE according to claim 23, further comprising: A component used to determine when the timer has expired; and The component is used to avoid sending subsequent registration requests to the first mobile network, based at least in part on the fact that the mobile country code associated with the UE has not changed after the first registration request was sent.

25. The UE according to claim 23, further comprising: A component for triggering a scan to detect the current mobile country code associated with the UE, based at least in part on one or more triggering conditions; and A component used to perform the scan to detect the current mobile country code associated with the UE.

26. The UE of claim 25, wherein the one or more triggering conditions include one or more of the following: a change in the physical cell identifier set during idle mode mobility at the UE, a no-service condition at the UE, a change in the location of the UE based on a Global Navigation Satellite System (GNSS), a change in wireless local area network coverage detection, or any combination thereof.

27. The UE of claim 25, wherein the component for performing the scan to detect the current country code comprises: A component used to scan 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 communication at a user equipment (UE), the code including instructions executable by one or more processors to: Send a first registration request to register with the first mobile network; Receive a rejection message, the rejection message indicating a rejection of the first registration request, and the rejection is based on the location of the UE; A timer associated with the rejection message is started, the duration of which is associated with a time period during which the UE will avoid sending one or more subsequent registration requests to the first mobile network. as well as A second registration request is sent to the first mobile network in response to the detection that the mobile country code associated with the UE has changed after the first registration request was sent. The second registration request is sent regardless of the state 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: It has been determined that the timer has expired; and At least in part, this is based on the fact that the mobile country code associated with the UE did not change after the first registration request was sent, thus avoiding the sending of subsequent registration requests to the first mobile network.

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

Images