Operations and transmission restrictions for restricted transmission areas

Aerial UEs in wireless communication systems can identify and navigate NTZs by indicating capabilities and receiving restrictions, allowing compliant operation within NTZs to avoid interference.

WO2025174459A1PCT designated stage Publication Date: 2025-08-21QUALCOMM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/US2024/061537
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-02-15
Filing Date
2024-12-20
Publication Date
2025-08-21

AI Technical Summary

Technical Problem

Current wireless communication systems do not support aerial user equipment (UE) in identifying and navigating no transmit zones (NTZs) where transmissions are restricted, leading to potential interference with sensitive equipment like radio telescopes.

Method used

Aerial UEs indicate their capability to support transmission restrictions, receive geographic area boundaries and frequency bands to avoid, and perform procedures based on their location to comply with NTZ restrictions, including refraining from transmissions and cell connectivity.

Benefits of technology

Enables aerial UEs to operate within NTZs without causing interference, ensuring compliance with transmission restrictions and maintaining network connectivity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2024061537_21082025_PF_FP_ABST
    Figure US2024061537_21082025_PF_FP_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communications are described. An aerial user equipment (UE) may transmit a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The aerial UE may receive a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE. The aerial UE may perform a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.
Need to check novelty before this filing date? Find Prior Art

Description

OPERATIONS AND TRANSMISSION RESTRICTIONS FOR RESTRICTED TRANSMISSION AREASCROSS REFERENCE

[0001] The present Application for Patent claims the benefit of Greek. Patent Application No. 20240100103 by FACCIN et al., entitled “OPERATIONS AND TRANSMISSION RESTRICTIONS FOR RESTRICTED TRANSMISSION AREAS,” filed February 15, 2024, assigned to the assignee hereof, and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The present disclosure relates to wireless communications, including operations and transmission restrictions for restricted transmission areas.BACKGROUND

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

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support operations and transmission restrictions for restrictedtransmission areas. For example, the described techniques provide for an aerial user equipment (UE) to enter and operate in a geographical area with transmission restrictions. In some examples, the described techniques provide for an aerial UE to support idle mode mobility- operations in a geographical area with transmission restrictions. For example, the aerial UE may indicate a capability to support operations and transmission restrictions within a geographical transmission restricted area. The network may indicate restrictions for the geographical transmission restricted area to the aerial UE based on the capability- of the aerial UE. In some examples, the network may indicate boundaries or dimensions for the geographical transmission restricted area, such as by indicating a two-dimensional or three-dimensional geographic polygon for the geographical transmission restricted area. For example, the network may indicate one or more radio frequency spectrum bands, and the aerial UE may not transmit using the indicated radio frequency spectrum bands while within the geographical transmission restricted area.

[0005] A method for wireless communications by an aerial UE is described. The method may include transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas, receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE, and performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0006] An aerial UE for wireless communications is described. The aerial UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the aerial UE to transmit a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas, receive a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE, and perform a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0007] Another aerial UE for wireless communications is described. The aerial UE may include means for transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas, means for receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE, and means for performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas, receive a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE, and perform a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0009] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the second message indicates a restricted transmission configuration for the first restricted transmission geographic area.

[0010] Some examples of the method. UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a request for information for the first restricted transmission geographic area, where the second message indicates a presence of the first restricted transmission geographic area and receiving, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area.

[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the request may be transmitted based on the second message indicating a tracking area that includes the first restricted transmission geographic area.

[0012] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, the second message indicates UE assistance information for transmitting the request for the information.

[0013] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the second message may be received via non-access stratum signaling from an access and mobility function, received from a policy and charging control entity, or received from an application function, or any combination thereof.

[0014] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, the second message indicates one or more radio frequency spectrum ranges where the aerial UE may be not allowed to transmit while in the first restricted transmission geographic area.

[0015] In some examples of the method. UEs, and non-transitory computer-readable medium described herein, the second message identifies a first transmission restriction or a first geographical boundary of the first restricted transmission geographic area.

[0016] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a system information block that identifies the first restricted transmission geographic area.

[0017] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for operating in the first restricted transmission geographic area in accordance with being barred from establishing connectivity with a cell associated with the first restricted transmission geographic area.

[0018] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, the system information block includes a field indicating the first restricted transmission geographic area and the field may be associated with one or more public land mobile networks or one or more non-public networks, or both.

[0019] In some examples of the method. UEs, and non-transitory computer-readable medium described herein, the first message may be transmitted via a mobility management capability message or during a cell registration procedure.

[0020] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for refraining from transmitting emergency signaling orresponding to paging signaling while the aerial UE may be located in the first restricted transmission geographic area.

[0021] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for deactivating an access stratum at the aerial UE while the aerial UE may be located in the first restricted transmission geographic area.

[0022] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for triggering a public land mobile network search prior to or upon entering the first restricted transmission geographic area.

[0023] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for performing a tracking area update prior to entering the first restricted transmission geographic area.

[0024] In some examples of the method. UEs. and non-transitory computer-readable medium described herein, performing the procedure may include operations, features, means, or instructions for performing a tracking area update prior to entering the first restricted transmission geographic area.BRIEF DESCRIPTION OF THE DRAWINGS

[0025] FIG. 1 shows an example of a wireless communications system that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0026] FIG. 2 shows an example of a wireless communications system that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0027] FIG. 3 shows an example of a process flow that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0028] FIGs. 4 and 5 show block diagrams of devices that support operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0029] FIG. 6 shows a block diagram of a communications manager that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0030] FIG. 7 shows a diagram of a system including a device that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.

[0031] FIGs. 8 and 9 show flowcharts illustrating methods that support operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0032] A wireless communications system may support aerial user equipment (UE), such as unmanned aerial vehicles (UAVs), drones, air taxis, and the like. In some cases, a geographical area may be deemed as a no transmit zone (NTZ), where aerial user equipment (UE) are not allowed to operate in a certain radio frequency spectrum band. For example, a geographical area around a highly sensitive radio telescope which scans using radio waves may be deemed an NTZ for aerial UEs, as transmissions from the aerial UEs may cause interference to the radio telescope. In some examples, restrictions for an NTZ for aerial UEs may be extensive, such as not allowing any transmission in specific radio frequency spectrum bands while an aerial UE is in an NTZ. Current systems do not support an aerial UE identifying an NTZ or mobility for an aerial UE into an NTZ.

[0033] A wireless communications system described herein supports techniques for an aerial UE to enter an NTZ. For example, an aerial UE may indicate a capability to support operations in an NTZ. In some examples, the aerial UE may indicate support for one or more transmission restrictions in an NTZ or support for operating in an idle mode while in an NTZ. The network may indicate restrictions for the NTZ to the aerial UE based on the capability of the aerial UE. In some examples, the network mayindicate a geographical area for the NTZ, such as by indicating a two-dimensional or three-dimensional geographic polygon for the NTZ. For example, the network may indicate one or more radio frequency spectrum bands where the aerial UE is not allowed to transmit, or the network may indicate one or more device types that are not allowed to transmit while in the NTZ. In some examples, the UE may receive the indication of the transmission restrictions from a network node, such as a network entity, an access and mobility function (AMF), a policy and charging control (PCC) function, or an application function. In some examples, the UE may receive an indication of a presence of the NTZ and information for an entity’ from which the UE may receive additional NTZ information. The UE may request information from the entity for the transmission restrictions based on the presence of the NTZ. In some examples, the UE may not transmit any signaling while in the NTZ, including emergency signaling or responses to paging signals. In some examples, the UE may treat any cells associated with the NTZ as though the UE is barred from or unsuitable for the cells while the UE is in the NTZ.

[0034] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to operations and transmission restrictions for restricted transmission areas.

[0035] FIG. 1 shows an example of a wireless communications system 100 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The wireless communications sy stem 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0044] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g.. a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g.. including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0045] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s)104), and a DU interface (e g., a DU 165) may provide a Uu interface for a parent TAB node to signal to a child IAB node or UE 115.

[0046] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0047] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g.. base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may. in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0065] Some UEs 1 15, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0066] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowbandcommunications), or a combination of these techniques. For example, some UEs 1 15 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g.. set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a earner, or outside of a carrier.

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

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

[0069] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to- everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105. base stations 140, RUs 170) using vehicle-to- network (V2N) communications, or with both.

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

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

[0072] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

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

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

[0075] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial lay ers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

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

[0077] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 1 15) a beam direction for later transmission or reception by the network entity 105.

[0078] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g.. a direction associated with the receiving device, such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0079] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may usea combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI- RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g.. a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

[0080] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g.. a network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening7’ according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0081] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0082] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g.. using a cyclic redundancy check (CRC)), forward error correction (FEC). and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0083] Some wireless communications systems may support a non-allowed area. In anon-allowed area, a UE 115 may be allowed to initiate a registration procedure but no other communication. A service area restriction may define areas in which a UE 115 may or may not initiate communication with the network. In an allowed area, a UE 115 may be permitted to initiate communication with the network as permitted by a subscription of the UE 115. A non-allowed area may be a serv ice area restricted based on subscription. The UE 115 and the network (e.g., for the UE 115) may not initiateservice requests or any connection requests for user plane data, control plane data, exception data reporting, or session management signaling to obtain user services that are not related to mobility. RRC procedures while the UE 115 is in a non-allowed area and operating in an RRC inactive state may be unchanged compared to when the UE 115 is in an allowed area. The radio management procedures may be unchanged compared to when the UE 115 is in an allowed area. In some cases, a UE 1 15 in a nonallowed area may respond to core network paging or NAS notification messages from with service request and RAN paging. A UE 115 in a non-allowed area may initiate session establishment or activation. For a UE 115. the core network may determine mobility restrictions based on UE subscription information, UE location, and local policy. When an AMF assigns a limited allowed area to a UE 115, the AMF may provide the UE 115 with service area restrictions including allowed areas or nonallowed areas. The allowed areas included in the service area restrictions may be preconfigured or dynamically assigned by the AMF. A unified data management (UDM) may store the service area restrictions of the UE 115 as part of the subscription data of the UE 115. A policy control function (PCF) in the serving network may (e g., based on varying conditions such as a location of the UE 115. application in use, time, and date) adjust service area restrictions of the UE 115, either by expanding an allowed area or by reducing a non-allowed area or increasing a maximum quantity of tracking areas. The UDM and PCF may update the service area restrictions of the UE 115 at any time. For a UE 115 in a connected mode state, the AMF may update the UE and RAN. For a UE 115 in an idle state, the AMF may page the UE or store the updated service area restriction and update the UE 115 during a next signaling interaction.

[0084] The wireless communications system 100 may support aerial UEs 115. In some examples, the wireless communications system 100 may support harmonized technical conditions for usage of aerial UEs 115 for communications based on some RATs, such as LTE and 5GNR. in bands harmonized for mobile or fixed communications networks (MFCN). For example, the wireless communications system 100 may support operation restrictions for aerial UEs 115 using NTZs. An NTZ may be a geographical area where aerial UEs 115 are not allowed to operate in certain frequency bands. In some examples, an aerial UE 115 may not perform any transmission in the banned or restricted frequencies while in an NTZ.

[0085] For example, an aerial UE 115 operating in a radio frequency spectrum band between 703 and 733 MHz may not transmit when less than 30 meters above ground level to avoid interference to digital terrestrial television receivers. In some examples, there may be NTZs around radio astronomy service (RAS) sites operating in 1400 to 1427 MHz for aerial UEs 115 operating in the 703 to 718 MHz radio frequency band. There may be an NTZ around RAS sites operating in 1660 to 1670 MHz for aerial UEs 115 operating in the 823 to 837 MHz frequency band. There may be an NTZ around RAS sites operating in 2690 to 2700 MHz for aerial UEs operating in the 2500 to 2570 MHz band or 2570 to 2720 MHz band. There may be an NTZ around radars operating in 2700 to 2900 MHz for aerial UEs 115 operating in the 2500 to 2570 MHz band or 2570 to 2620 MHz band. In some examples, a different frequency band than 703 to 733 MHz may be used for landing and takeoff. Similar NTZs may be configured or determined for other conditions and radio frequency bands. In some examples, the terms “radio frequency spectrum band” and “radio frequency band” may be used interchangeably herein.

[0086] The wireless communications system 100 may support techniques for an aerial UE 115 to identify and implement transmission restrictions when in an NTZ. The aerial UE 115 may transmit an indication of a capability to support one or more transmission restrictions in NTZs. The aerial UE 115 may transmit the indication of the capability while registering to a cell, network node, or network. In some examples, the aerial UE 115 may indicate the capability via mobility management capability' information. The aerial UE 115 may receive an indication of transmission restrictions for an NTZ. In some examples, the UE 115 may receive an indication of a two- dimensional or three-dimensional geographic area where transmission is restricted. In some examples, the cells corresponding to the NTZ may be defined as a non-allowed area. In some examples, cells corresponding to the NTZ may be barred for UEs 115 of specific UE categories, such that an aerial UE 115 may not consider the cells as suitable cells. In some examples, an aerial UE 1 15 may be configured with a list of radio frequency spectrum bands and a geo-fence where transmission is not allowed.

[0087] FIG. 2 shows an example of a wireless communications system 200 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The wirelesscommunications system 200 may include a UE 1 15-a and a network entity 105-a. The UE 115-a may be an example of a UE 115 described herein, such as an aerial UE 115. The network entity 105 -a may be an example of a network node or a network entity' 105 described herein.

[0088] The wireless communications system 200 may include an NTZ 205. The NTZ 205 may correspond to a geographical area where transmission from certain devices on certain radio frequency spectrum bands is restricted. For example, the UE 115-a may be restricted from transmitting on a radio frequency spectrum band which the UE 115-a uses for communications (e.g., LTE or NR communications) while the UE 115-a is in the NTZ 205. The wireless communications system 200 may support techniques for the UE 115-a to identify the NTZ 205 and operate in the NTZ 205 according to transmission restrictions.

[0089] For example, the UE 115-a may transmit a capability' message 210 indicating one or more capabilities of the UE 115-a. The capability’ message 210 may indicate that the UE 115-a supports transmission restriction, NTZs (e.g., the NTZ 205), or transmission restrictions while operating in NTZ. The UE 115-a may receive restriction information 215, which may indicate transmission restrictions for the NTZ 205. In some examples, the restriction information 215 may identify’ one or more radio frequency bands where transmission by the UE 115-b is restricted or prohibited within the NTZ 205. In some examples, the UE 115-a may transmit the capability7message 210 to the network entity7105-a. In some examples, the network entity’ 105-a may transmit the restriction information 215 to the UE 115-a. In some other examples, separate devices, nodes, or entities may transmit and receive the capability message 210 or the restriction information 215. In some examples, the restriction information 215 may be referred to as an NTZ configuration, NTZ information, and the like.

[0090] In some examples, cells corresponding to the NTZ 205 may correspond to a non-allowed area. The wireless communication network may receive NTZ information and map the NTZ to a restricted transmission area. In some examples, the core network may receive the NTZ via an operations, administration, and management (0AM) entity from an external party (e.g., a government or entity enforcing the NTZ 205). The core network may configure the UE 115-a with the restricted transmission area. For example,the network entity 105-a may transmit control signaling to configure the UE 1 15-a with the restricted transmission area.

[0091] In some examples, the restricted transmission area may be implemented using a non-allowed area. In some examples, a configuration for the non-allowed area may indicate that the non-allowed area correspond to an NTZ. In some examples, the restriction information may indicate NTZ boundaries. The NTZ boundaries may correspond to or define a two-dimensional boundary or a three-dimensional boundary. For a two-dimensional boundary, the NTZ 205 may have, effectively, an infinite height. For a three-dimensional boundary, the NTZ 205 may be a box, sphere, cylinder, ellipsoid, etc. In some examples, the NTZ 205 may be limited in an altitude axis. For example, for an NTZ around an airport, the NTZ may extend to 500 meters in the air. Above 500 meters, there may not be an NTZ above the airport.

[0092] In some examples, the UE 115 may indicate a capability to support of NTZ restrictions. For example, the UE 115 may indicate support of NTZ restrictions via mobility management signaling. The network may indicate the restriction information to the UE 115 based on the capability of the UE 115. If the UE 115 does not indicate the capability to support NTZ restrictions to the network, the network may deregister the UE 115. In some examples, the network may provide a cause code or a backoff timer to indicate for the UE 115 to not re-register for a period of time to a public land mobile network (PLMN) of the network.

[0093] The UE 115 may not be capable of transmission, or prevented from transmitting, while in the restricted transmission area. In some examples, the restriction on transmission while in the restricted transmission area may be specific to certain radio frequency spectrum bands. When providing NTZ information as a non-allowed area, an AMF may be configured with the NTZ information and provide a RAN tracking area (RTA) to the UE 115-a based on the NTZ information after the AMF determines that the AMF is supporting an aerial UE and that such UE supports NTZ restrictions. For example, the UE 115-a may indicate NTZ restriction support, and the AMF may determine that the UE 115-a is an aerial UE 115 based on an aerial subscription and a successful UAV authentication procedure. In some examples, the AMF may not have any NTZ information, and the AMF may create a restricted transmission area based on UDM information. During registration, the PCF may adjust the restricted transmissionarea created by the AMF or create a restricted transmission area based on NTZ information configured in the PCF, location of the UE 115-a, a permanent equipment identifier of the UE 115-a, and network policies. If the PCF modifies the restricted transmission area or creates a restricted transmission area, the PCF may indicate the restricted transmission area is for an NTZ. The AMF may indicate the restricted transmission area to the UE 115-a with an indication of the NTZ 205 based on the NTZ information.

[0094] The UE 115 -a may operate based on the restrictions when entering the NTZ 205. In some examples, operation of the UE 115-a in the NTZ 205 may be referred to as an idle mode or an NTZ idle mode. While in the NTZ 205, the UE 115-a may not at least transmit on radio frequency bands corresponding to the NTZ 205. For example, the UE 115-a may not initiate an sendee, request, or signaling, including emergency services. When entering a non-allowed area marked as an NTZ (e.g., the NTZ 205), the UE 115-a may operate as a UE 115 without a suitable serving cell, banned from performing any emergency services. In some examples, the UE 1 15-a may not respond to any paging from the network when operating in the NTZ 205. When entering the NTZ 205, the UE 115-a may trigger PLMN reselection.

[0095] In some examples, the UDM and the PCF may update the serv ice area restrictions of the UE 115-a. If the UE 115-a operate in an idle state while in the NTZ 205, the AMF may store the updated service area restriction and update the UE 115-a during a next communication with the UE 115-a. In some examples, if the UE 115-a is located in the NTZ 205, the AMF may not initiate paging for the UE 115-a to update service area restrictions with a generic UE configuration update procedure.

[0096] In some examples, cells corresponding to the NTZ 205 may be barred for specific types of UE 115. For example, the cells may be barred for UEs 115 of specific UE categories. For example, based on the NTZ information, the UE 115-a may not consider the barred cells as suitable cells, or cells configured by 0AM in a RAN.

[0097] In some examples, there may be three categories or types of UEs. A first type of UE 115 may be an aerial UE 115 that supports NTZ restriction functionality. The first type of UE 115 may consider cells corresponding to the NTZ 205 as barred. The first type of UE 115 may indicate the ability to support NTZ restrictions to thenetwork. The core network and RAN may be aware that a UE 1 15 is the first type of UE 115 based on a subscription for the UE 115 being an aerial subscription. A second type of UE 115 may be non-aerial UEs 115. The second type of UE 115 may consider the cells corresponding to the NTZ 205 as allowed. A third type of UE 115 may be aerial UEs 115 which do not support NTZ restriction functionality.

[0098] For the first type of UE 115 and the second type of UE 115, a field in a system information block (SIB) may indicate the NTZ 205 or one or more NTZ restrictions. For example, a cell may transmit a SIB. such as SIB1, and an NTZ restricted information element in the SIB (e.g., ntzRestricted’) may indicate whether the cell corresponds to an NTZ. For example, if a cell broadcasts that ‘ntzRestricted’ is true, the cell status is indicated as not barred and not reserved for operator use, all UEs 115 configured with or supporting NTZ restriction may treat the cell as if the cell status is barred. Other UEs 115 may treat the cell as a candidate cell during cell selection and cell reselection procedures. For example, the first type of UE 115 may be barred from the cell, and other types of UEs 115 may be allowed to use the cell.

[0099] For the third type of UE 115, the cells operating in the restricted radio frequency spectrum groups may be defined as cell access group (CAG) cells. The network may indicate the CAG list to the third type of UEs 115. For example, when a cell broadcasts any CAG identifiers or network identifiers and the cell status is indicated as not barred and not reserved for operator use, non-public network (NPN) capable UEs 115 may treat the cell as a candidate cell during cell selection and cell reselection procedures, and other UEs 115 may treat the cell as barred. If the cell does not broadcast any CAG identifiers or network identifiers, or the cell does not broadcast any CAG identifiers and a UE 115 is not operating in a standalone NPN access mode, the UE 115 may treat the cell as if the cell is barred.

[0100] In some examples, the UE 115-a may receive a message indicating a geographical area and radio frequency spectrum bands which the UE 115-a is not allowed to use for transmission while in the geographical area. For example, the network may configure the UE 115-a with a geofence where one or more certain radio frequencies are not allowed for transmission by the UE 115-a. The indication may be similar to a PC5 policy configuration, but instead of indicating frequencies where communications are allowed, the configuration for the NTZ 205 may indicatefrequencies where transmission by the UE 1 15-a is not allowed. In some examples, a tracking area for the geofence may be normal (e.g., not non-allowed). In some examples, the UE 115-a may receive an indication of a presence of the NTZ 205, and the UE 115-a may request restriction information for the NTZ 205 based on the indication of the presence of the NTZ 205. For example, the UE 115-a may transmit a request 220 for the restriction information 215 or an NTZ configuration.

[0101] In some examples, the UE 115-a may receive the NTZ information from an AMF. For example, the UE 115-a may receive the NTZ information from the AMF via NAS signaling. In some examples, the UE 115-a may receive the NTZ information via a registration acceptance message. The NTZ information may indicate geographical information for the NTZ 205, such as a geo-area or dimensions of a polygon corresponding to the NTZ 205.

[0102] In some examples, the UE 115-a may receive the NTZ information from a PCC. For example, the UE 115-a may be operating in a tracking area with an NTZ. and the UE 115-a may have an aerial UE 115 subscription. The UE 115-a may request policy information from the PCC including the NTZ information for the NTZ 205 in the tracking area. For example, the UE 115-a may receive an indication that there are one or more NTZs in a registration area when the UE 115-a registers, which may trigger the UE 115-a to request information for the one or more NTZs. In some examples, the AMF may indicate the presence of the one or more NTZs to the UE 1 15-a via a registration acceptance message. For example, the UE 115-a may receive a presence indicator 225. The registration acceptance message may include a parameter to indicate the presence of one or more NTZs in the registration area. The AMF may be configured by an 0AM to indicate that a tracking area has one or more NTZs. In some examples, the AMF may indicate the presence of the NTZ 205 to the PCF. Based on the indication of the presence of the NTZ 205, the PCF may trigger an indication of NTZ information and policies related to the NTZ 205.

[0103] In some examples, the UE 115-a may receive the NTZ information from an application function. In some examples, the UE 115-a may receive the NTZ information from an application function associated with a mobile network operator (MNO), an external application function via a network exposure function, or an external user plane. The UE 115-a may be triggered to request the NTZ information based on an indicationthat a tracking area includes the NTZ 205. Tn some examples, an AMF may indicate assistance information to the UE 115-a, such as a uniform resource locator (URL), to reach the application function and transmit the request 220. In some examples, the request 220 may have higher priority than other policy requests received at the PCF. In some cases, the UE 115-a may use an existing user plane connection or establish an appropriate user plane connection (e.g., UE may be configured with a specific DNN / S- NSSAI for such connectivity) to the AF and use application layer signaling to retrieve the NTZ information.

[0104] The UE 115-a may receive the NTZ information and may deactivate an access stratum at the UE 115-a or cease transmission when entering the NTZ 205. In some examples, the UE 115-a may refrain from operating the access stratum while in the NTZ 205 (e.g., based on geographical positioning information or a list of available cells). In some examples, the UE 115-a may perform a tracking area update prior to entering the NTZ 205. In some examples, the UE 115-a may perform a tracking area update based on entering (e.g., right after entering) the NTZ 205. The network may consider the UE 115-a as unreachable but registered. The UE 115-a may perform reregistration when exiting the NTZ 205.

[0105] In some examples, indicating a geofence and non-allowed radio frequency spectrum bands may prevent the UE 115-a from performing transmission or reception while in the NTZ 205. In some examples, the PCC may provide policy to the RAN for when the UE 115-a is in connected mode to enable the UE 115-a to perform reception while in the NTZ 205. When the UE 115-a enters the tracking area and retrieves policy information for the NTZ 205 for the tracking area but before the UE 115-a enters the geofence, the UE 115-a may re-register and indicates that the UE 115-a is entering the NTZ 205. The UE 115-a may perform reselection to another band and may indicate a change of radio capabilities (e.g., a temporary change of radio capabilities). When the UE 115-a switches to a connected mode, the UE 115-a may not operating in the nonallowed frequencies. The UE 115-a may transmit the registration request based on a trigger, such as when the UE 115-a is about to enter or approaching the NTZ 205 based on a current location of the UE 115-a, and the UE 115-a has received policy information with respect to the NTZ 205.

[0106] In some examples, some operations or processes of the network may be based on radio capabilities of UE 115-a. The UE 115-a may report a capability indicating whether the UE 115-a supports other frequency bands besides the frequency bands that are not allowed within the NTZ 205. If the UE 115-a does not support other frequency bands, the network may consider the UE 115-a unreachable. If the UE 1 15-a does support other bands, the network may consider the UE 115-a reachable and available for at least downlink signaling. In some examples, the UE 115-a may receive paging signaling on the other bands which do not correspond to the NTZ 205. After the UE 115-a transmits a registration request and enters the NTZ 205, the UE 115-a may locally modify the radio capabilities of the UE 115-a and reselects to another band that does not correspond to the NTZ 205. The UE 115-a may perform idle mode procedures for cell reselection after reselecting to a band that does not correspond to the NTZ 205.

[0107] FIG. 3 shows an example of a process flow 300 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The process flow 300 may implement aspects of wireless communications system 100 or a wireless communications system 200. For instance, the process flow 300 may illustrate operations between a UE 115-b and a network entity 105-b, which may be respective examples of a UE 115 and a network entity 105 described herein. In the following description of the process flow 300, the operations between the UE 115-b and the network entity 105-b may be transmitted in a different order than the example order shown, or the operations performed by the UE 115-b and the network entity 105-b may be performed in different orders or at different times. Some operations also may be omitted from the process flow 300, and other operations may be added to the process flow 300.

[0108] The UE 115-b may be an example of an aerial UE 115. For example, the UE 115-b may have an aerial UE subscription. The network entity 105-b may be an example of or include aspects of an AMF, an application function, a PCC, a RAN node, or any combination thereof. In some examples, the network entity 105-b may provide one or more cells which are associated with an NTZ or a geographical transmission restricted area. Additionally, or alternatively, the network entity' 105-b may correspond to a tracking area which includes one or more NTZs or geographical transmission restricted areas.

[0109] At 310, the UE 1 15-b may transmit a first message indicating a capability of the UE 115-b to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. In some examples, the UE 115-b may transmit a mobility management capability’ message indicating the capability of the UE 115-b. In some examples, the UE 115-b may indicate the capability of the UE 115-b during a cell registration procedure (e.g., while registering with the network entity 105-b).

[0110] At 315, the UE 115-b may receive a second message indicating a first restricted transmission geographic area based on the capability of the UE 115-b. In some examples, the second message may indicate a restricted transmission configuration for the first restricted transmission geographic area. In some examples, the second message may be received via NAS signaling from an AMF, received from a PCC entity, or requested by the UE 115-b and received from an application function, provided by an indication in a SIB from the network entity 105-b. or any combination thereof. In some examples, the second message may identify a first transmission restriction or a firs geographical boundary’ of the first restricted transmission geographic area. For example, the second message may indicate one or more radio frequency bands which the UE 115-b is not allowed to use to transmit while in the first restricted transmission geographic area. In some examples, the second message may indicate boundaries of the first restricted transmission geographic area. For example, the second message may indicate dimensions or parameters for a tw o-dimensional or three- dimensional boundary or polygon corresponding to the first restricted transmission geographic area.

[0111] In some examples, the second message may indicate a presence of the first restricted transmission geographic area. At 320, the UE 115-b may transmit a request for information for the first restricted transmission geographic area. In some examples, the second message may include assistance information for transmitting the request for the information. For example, the second message may include a URL, and the UE 115-b may communicate with an application function based on the URL to obtain NTZ information or restriction information for the first restricted transmission geographic area. For example, the UE 115-b may communicate with the application function using new or existing user plane connectivity.

[0112] In some examples, the UE 115-b may receive information for the first restricted transmission geographic area in response to the request. For example, at 325, the UE 115-b may receive, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area. For example, the UE 115-b may receive NTZ information or an NTZ configuration for the first restricted transmission geographic area. In some examples, the NTZ information received at 325 may indicate geographical boundaries of the first restricted transmission geographic area or one or more radio frequency bands associated with the first restricted transmission geographic area, or both. In some examples, the UE 115-b may receive NTZ information from multiple entities. For example, the UE 115-b may receive first NTZ information at 315, and the UE 115-b may receive second NTZ information at 325. The UE 115-b may prioritize NTZ information based on a source of the NTZ information. For example, NTZ information received from an application function may have a higher priority than NTZ information received from a PCC or an AMF. In some examples, NTZ information received from a PCC may have higher priority than NTZ information received from an AMF. Priority7may correspond to the NTZ information by which the UE 115-b operates. For example, if first NTZ information received from an application function is different from second NTZ information received from an AMF, the UE 115-b may operate according to the NTZ information received from the application function.

[0113] At 330, the UE 115-b may operate according to the restriction information for the first restricted transmission geographic area. For example, the UE 115-b may perform a procedure based on a current geolocation of the UE 1 15-b relative to the first restricted transmission geographic area. In some examples, the UE 115-b may operate in an idle mode while the geolocation of the UE 115-b is within the first restricted transmission geographic area. In some examples, the UE 115-b may not transmit using a radio frequency band associated with the first restricted transmission geographic area while the geolocation of the UE 115-b is within the first restricted transmission geographic area. For example, the UE 115-b may refrain from transmitting emergency signaling or responding to paging signaling while the UE 115-b is located in the first restricted transmission geographic area. In some examples, the UE 115-b maydeactivate an access stratum at the UE 1 15-b while the UE 1 15-b is located in the first restricted transmission geographic area.

[0114] In some examples, the UE 115-b may trigger a PLMN search prior to or upon entering the first restricted transmission geographic area. In some examples, the UE 115-b may perform a tracking area update prior to entering the first restricted transmission geographic area. In some examples, the UE 115-b may indicate to the network (e.g., via the network entity 105-b) that the UE 115-b is entering the first restricted transmission geographic area, and the UE 115-b is, or will be, temporarily unavailable while in the first restricted transmission geographic area.

[0115] In some examples, the UE 115-b may receive a SIB based on the first restricted transmission geographic area. For example, at 305, the UE 1 15-b may receive a SIB indication that identifies the first restricted transmission geographic area. In some examples, the SIB indication may indicate that a current cell (e.g., a cell that transmitted the SIB) is restricted. In some examples, the network may send the SIB indication using all cells corresponding to or containing the first restricted geographic area. For example, any network entity 105 that provides a cell corresponding to or containing the first restricted geographic area may transmit a SIB indication via the cell which indicates the cell is restricted. In some examples, the SIB may indicate that a tracking area includes one or more restricted transmission geographic areas. In some examples, the SIB may include a field indicating the first restricted transmission geographic area, and the field may be associated with one or more PLMNs or NPNs. At 330, the UE 115-b may operate in the first restricted transmission geographic area in accordance with being barred from establishing connectivity with a cell associated with the first restricted transmission geographic area. For example, the UE 115-b may treat the network entity 105-b, or a cell provided by the network entity' 105-b, as though the UE 115-b were barred from the network entity 105-b, or the cell provided by the network entity 105-b.

[0116] FIG. 4 shows a block diagram 400 of a device 405 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. The device 405, or one or more components of the device 405 (e.g.. the receiver 410. the transmitter 415, the communicationsmanager 420), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0117] The receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to operations and transmission restrictions for restricted transmission areas). Information may be passed on to other components of the device 405. The receiver 410 may utilize a single antenna or a set of multiple antennas.

[0118] The transmitter 41 may provide a means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to operations and transmission restrictions for restricted transmission areas). In some examples, the transmitter 415 may be co-located with a receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a set of multiple antennas.

[0119] The communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be examples of means for performing various aspects of operations and transmission restrictions for restricted transmission areas as described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0123] The communications manager 420 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 420 is capable of, configured to, or operable to support a means for transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The communications manager 420 is capable of, configured to, or operable to support a means for receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE. The communications manager 420 is capable of, configured to, or operable to support ameans for performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0124] By including or configuring the communications manager 420 in accordance with examples as described herein, the device 405 (e.g., at least one processor controlling or otherwise coupled with the receiver 410, the transmitter 415. the communications manager 420, or a combination thereol) may support techniques for reduced power consumption and improved compliance within a wireless communications sy stem.

[0125] FIG. 5 shows a block diagram 500 of a device 505 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a device 405 or a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0126] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to operations and transmission restrictions for restricted transmission areas). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

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

[0128] The device 505, or various components thereof, may be an example of means for performing various aspects of operations and transmission restrictions for restricted transmission areas as described herein. For example, the communications manager 520 may include a capability component 525, an NTZ indication component 530, an NTZ procedure component 535, or any combination thereof. The communications manager 520 may be an example of aspects of a communications manager 420 as described herein. In some examples, the communications manager 520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0129] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. The capability component 525 is capable of, configured to, or operable to support a means for transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The NTZ indication component 530 is capable of, configured to, or operable to support a means for receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE. The NTZ procedure component 535 is capable of, configured to, or operable to support a means for performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0130] In some cases, the capability component 525, the NTZ indication component 530, and the NTZ procedure component 535 may each be or be at least a part of a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled with memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the capability component 525, the NTZ indication component 530, and the NTZ procedure component 535 discussed herein. A transceiver processor may becollocated with and / or communicate with (e.g., direct the operations of) a transceiver of the device. A radio processor may be collocated with and / or communicate with (e.g., direct the operations of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of the device. A transmitter processor may be collocated with and / or communicate with (e.g.. direct the operations of) a transmitter of the device. A receiver processor may be collocated with and / or communicate with (e.g., direct the operations of) a receiver of the device.

[0131] FIG. 6 shows a block diagram 600 of a communications manager 620 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520, or both, as described herein. The communications manager 620, or various components thereof, may be an example of means for performing various aspects of operations and transmission restrictions for restricted transmission areas as described herein. For example, the communications manager 620 may include a capability component 625, an NTZ indication component 630, an NTZ procedure component 635, an NTZ configuration request component 640, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0132] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The capability component 625 is capable of, configured to, or operable to support a means for transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The NTZ indication component 630 is capable of, configured to, or operable to support a means for receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE. The NTZ procedure component 635 is capable of, configured to, or operable to support a means for performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0133] In some examples, the second message indicates a restricted transmission configuration for the first restricted transmission geographic area. In some examples, the NTZ configuration request component 640 is capable of, configured to, or operable to support a means for transmitting a request for information for the first restricted transmission geographic area, where the second message indicates a presence of the first restricted transmission geographic area. In some examples, the NTZ configuration request component 640 is capable of, configured to, or operable to support a means for receiving, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area.

[0134] In some examples, the request is transmitted based on the second message indicating a tracking area that includes the first restricted transmission geographic area. In some examples, the second message indicates UE assistance information for transmitting the request for the information.

[0135] In some examples, the second message is received via non-access stratum signaling from an access and mobility function, received from a policy and charging control entity, or received from an application function, or any combination thereof.

[0136] In some examples, the second message indicates one or more radio frequency spectrum ranges where the aerial UE is not allowed to transmit while in the first restricted transmission geographic area. In some examples, the second message identifies a first transmission restriction or a first geographical boundary of the first restricted transmission geographic area.

[0137] In some examples, the NTZ indication component 630 is capable of, configured to, or operable to support a means for receiving a system information block that identifies the first restricted transmission geographic area.

[0138] In some examples, to support performing the procedure, the NTZ procedure component 635 is capable of, configured to, or operable to support a means for operating in the first restricted transmission geographic area in accordance with being barred from establishing connectivity with a cell associated with the first restricted transmission geographic area.

[0139] In some examples, the system information block includes a field indicating the first restricted transmission geographic area. In some examples, the field is associated with one or more public land mobile networks or one or more non-public networks, or both. In some examples, the first message is transmitted via a mobility’ management capability7message or during a cell registration procedure.

[0140] In some examples, to support performing the procedure, the NTZ procedure component 635 is capable of, configured to, or operable to support a means for refraining from transmitting emergency signaling or responding to paging signaling while the aerial UE is located in the first restricted transmission geographic area.

[0141] In some examples, to support performing the procedure, the NTZ procedure component 635 is capable of, configured to, or operable to support a means for deactivating an access stratum at the aerial UE yvhile the aerial UE is located in the first restricted transmission geographic area.

[0142] In some examples, to support performing the procedure, the NTZ procedure component 635 is capable of, configured to. or operable to support a means for triggering a public land mobile network search prior to or upon entering the first restricted transmission geographic area. In some examples, to support performing the procedure, the NTZ procedure component 635 is capable of, configured to, or operable to support a means for performing a tracking area update prior to entering the first restricted transmission geographic area.

[0143] In some cases, the capability component 625, the NTZ indication component 630, the NTZ procedure component 635, and the NTZ configuration request component 640 may each be or be at least a part of a processor (e g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor maybe coupled with memory and execute instructions stored in the memory7that enable the processor to perform or facilitate the features of the capability component 625, the NTZ indication component 630, the NTZ procedure component 635, and the NTZ configuration request component 640 discussed herein.

[0144] FIG. 7 shows a diagram of a system 700 including a device 705 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The device 705 may bean example of or include components of a device 405, a device 505, or a UE 1 15 as described herein. The device 705 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 720, an input / output (I / O) controller, such as an I / O controller 710, a transceiver 715, one or more antennas 725, at least one memory7730, code 735, and at least one processor 740. These components may be in electronic communication or otherwise coupled (e.g.. operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

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

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

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

[0148] The at least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)). one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 740. The at least one processor 740 may be configured to execute computer-readable instructions stored in a memory' (e.g., the at least one memory' 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting operations and transmission restrictions for restricted transmission areas). For example, the device 705 or a component of the device 705 may include at least one processor 740 and at least one memory 730 coupled with or to the at least one processor 740, the at least one processor 740 and the at least one memory' 730 configured to perform various functions described herein. In some examples, the at least one processor 740 may include multiple processors and the at least one memory 730may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 740 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 740) and memon circuitry (which may include the at least one memory 730)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 740 or a processing system including the at least one processor 740 may be configured to, configurable to, or operable to cause the device 705 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 735 (e.g., processor-executable code) stored in the at least one memory' 730 or otherwise, to perform one or more of the functions described herein.

[0149] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a means for transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The communications manager 720 is capable of, configured to, or operable to support a means for receiving a second message indicating a first restricted transmission geographic area based on the capability' of the aerial UE. The communications manager 720 is capable of, configured to, or operable to support a means for performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0150] By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 may support techniques for reduced power consumption and improved coordination betyveen devices.

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

[0152] FIG. 8 shows a flowchart illustrating a method 800 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The operations of the method 800 may be implemented by a UE or its components as described herein. For example, the operations of the method 800 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0153] At 805, the method may include transmitting a first message indicating a capability’ of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The operations of 805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 805 may be performed by a capability' component 625 as described with reference to FIG. 6.

[0154] At 810, the method may include receiving a second message indicating a first restricted transmission geographic area based on the capability of the aerial UE. The operations of 810 may be performed in accordance w ith examples as disclosed herein. In some examples, aspects of the operations of 810 may be performed by an NTZ indication component 630 as described with reference to FIG. 6.

[0155] At 815, the method may include performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area. The operations of 815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 815 may be performed by an NTZ procedure component 635 as described with reference to FIG. 6.

[0156] FIG. 9 shows a flowchart illustrating a method 900 that supports operations and transmission restrictions for restricted transmission areas in accordance with one or more aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0157] At 905, the method may include transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas. The operations of 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by a capabi lily component 625 as described with reference to FIG. 6.

[0158] At 910, the method may include receiving a second message indicating a first restricted transmission geographic area based on the capability' of the aerial UE. The operations of 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by an NTZ indication component 630 as described with reference to FIG. 6.

[0159] At 915, the method may include transmitting a request for information for the first restricted transmission geographic area, where the second message indicates a presence of the first restricted transmission geographic area. The operations of 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by an NTZ configuration request component 640 as described with reference to FIG. 6.

[0160] At 920, the method may include receiving, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area. The operations of 920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed by an NTZ configuration request component 640 as described with reference to FIG. 6.

[0161] At 925, the method may include performing a procedure based on a current geolocation of the aerial UE relative to the first restricted transmission geographic area. The operations of 925 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 925 may be performed by an NTZ procedure component 635 as described with reference to FIG. 6.

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

[0163] Aspect 1 : A method for wireless communications at an aerial UE, comprising: transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas; receiving a second message indicating a first restricted transmission geographic area based at least in part on the capability of the aerial UE; and performing a procedure based at least in part on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

[0164] Aspect 2: The method of aspect 1, wherein the second message indicates a restricted transmission configuration for the first restricted transmission geographic area.

[0165] Aspect 3: The method of any of aspects 1 through 2, further comprising: transmitting a request for information for the first restricted transmission geographic area, wherein the second message indicates a presence of the first restricted transmission geographic area; and receiving, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area.

[0166] Aspect 4: The method of aspect 3, wherein the request is transmitted based at least in part on the second message indicating a tracking area that comprises the first restricted transmission geographic area.

[0167] Aspect 5: The method of any of aspects 3 through 4. wherein the second message indicates UE assistance information for transmitting the request for the information.

[0168] Aspect 6: The method of any of aspects 1 through 5, wherein the second message is received via non-access stratum signaling from an access and mobility7function, received from a policy and charging control entity, or received from an application function, or any combination thereof.

[0169] Aspect 7: The method of any of aspects 1 through 6. wherein the second message indicates one or more radio frequency spectrum ranges where the aerial UE is not allowed to transmit while in the first restricted transmission geographic area.

[0170] Aspect 8: The method of any of aspects 1 through 7, wherein the second message identifies a first transmission restriction or a first geographical boundary7of the first restricted transmission geographic area.

[0171] Aspect 9: The method of any of aspects 1 through 8, further comprising: receiving a system information block that identifies the first restricted transmission geographic area.

[0172] Aspect 10: The method of aspect 9, yvherein performing the procedure comprises: operating in the first restricted transmission geographic area in accordance with being barred from establishing connectivity7with a cell associated with the first restricted transmission geographic area.

[0173] Aspect 11 : The method of any of aspects 9 through 10, yvherein the system information block comprises a field indicating the first restricted transmission geographic area, and the field is associated yvith one or more public land mobile networks or one or more non-public networks, or both.

[0174] Aspect 12: The method of any of aspects 1 through 11 , wherein the first message is transmitted via a mobility management capability message or during a cell registration procedure.

[0175] Aspect 13: The method of any of aspects 1 through 12, wherein performing the procedure comprises: refraining from transmitting emergency signaling or responding to paging signaling while the aerial UE is located in the first restricted transmission geographic area.

[0176] Aspect 14: The method of any of aspects 1 through 13, wherein performing the procedure comprises: deactivating an access stratum at the aerial UE while the aerial UE is located in the first restricted transmission geographic area.

[0177] Aspect 15: The method of any of aspects 1 through 14, wherein performing the procedure comprises: triggering a public land mobile network search prior to or upon entering the first restricted transmission geographic area.

[0178] Aspect 16: The method of any of aspects 1 through 15, wherein performing the procedure comprises: performing a tracking area update prior to entering the first restricted transmission geographic area.

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

[0180] Aspect 18: An aerial UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 16.

[0181] Aspect 19: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 16.

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

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

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

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

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

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

[0188] As used herein, including in the claims, “or’" as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the presentdisclosure. 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.”

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

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

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

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

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

Claims

CLAIMSWhat is claimed is:1 . An aerial user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the aerial UE to: transmit a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas; receive a second message indicating a first restricted transmission geographic area based at least in part on the capability of the aerial UE; and perform a procedure based at least in part on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

2. The aerial UE of claim 1, wherein the second message indicates a restricted transmission configuration for the first restricted transmission geographic area.

3. The aerial UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the aerial UE to: transmit a request for information for the first restricted transmission geographic area, wherein the second message indicates a presence of the first restricted transmission geographic area; and receive, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area.

4. The aerial UE of claim 3, wherein the request is transmitted based at least in part on the second message indicating a tracking area that comprises the first restricted transmission geographic area.

5. The aerial UE of claim 3, wherein the second message indicates UE assistance information for transmitting the request for the information.

6. The aerial UE of claim 1, wherein the second message is received via non-access stratum signaling from an access and mobility function, received from a policy and charging control entity, or received from an application function, or any combination thereof.

7. The aerial UE of claim 1, wherein the second message indicates one or more radio frequency spectrum ranges where the aerial UE is not allowed to transmit while in the first restricted transmission geographic area.

8. The aerial UE of claim 1, wherein the second message identifies a first transmission restriction or a first geographical boundary7of the first restricted transmission geographic area.

9. The aerial UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the aerial UE to: receive a system information block that identifies the first restricted transmission geographic area.

10. The aerial UE of claim 9, wherein, to perform the procedure, the one or more processors are individually or collectively operable to execute the code to cause the aerial UE to: operate in the first restricted transmission geographic area in accordance with being barred from establishing connectivity with a cell associated with the first restricted transmission geographic area.

11. The aerial UE of claim 9, wherein: the system information block comprises a field indicating the first restricted transmission geographic area, and the field is associated with one or more public land mobile networks or one or more non-public networks, or both.

12. The aerial UE of claim 1, wherein the first message is transmitted via a mobility management capability message or during a cell registration procedure.

13. The aerial UE of claim 1, wherein, to perform the procedure, the one or more processors are individually or collectively operable to execute the code to cause the aerial UE to: refrain from transmitting emergency signaling or responding to paging signaling while the aerial UE is located in the first restricted transmission geographic area.

14. The aerial UE of claim 1, wherein, to perform the procedure, the one or more processors are individually or collectively operable to execute the code to cause the aerial UE to: deactivate an access stratum at the aerial UE while the aerial UE is located in the first restricted transmission geographic area.

15. The aerial UE of claim 1, wherein, to perform the procedure, the one or more processors are individually or collectively operable to execute the code to cause the aerial UE to: trigger a public land mobile network search prior to or upon entering the first restricted transmission geographic area.

16. The aerial UE of claim 1, wherein, to perform the procedure, the one or more processors are individually or collectively operable to execute the code to cause the aerial UE to: perform a tracking area update prior to entering the first restricted transmission geographic area.

17. A method for wireless communications at an aerial user equipment (UE), comprising: transmitting a first message indicating a capability of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas; receiving a second message indicating a first restricted transmission geographic area based at least in part on the capability of the aerial UE; and performing a procedure based at least in part on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

18. The method of claim 17, wherein the second message indicates a restricted transmission configuration for the first restricted transmission geographic area.

19. The method of claim 17, further comprising: transmitting a request for information for the first restricted transmission geographic area, wherein the second message indicates a presence of the first restricted transmission geographic area; and receiving, in response to the request, a third message indicating a restricted transmission configuration for the first restricted transmission geographic area.

20. An aerial user equipment (UE) for wireless communications, comprising: means for transmitting a first message indicating a capability' of the aerial UE to support one or more transmission restrictions associated with one or more restricted transmission geographic areas; means for receiving a second message indicating a first restricted transmission geographic area based at least in part on the capability of the aerial UE; and means for performing a procedure based at least in part on a current geolocation of the aerial UE relative to the first restricted transmission geographic area.

Citation Information

Patent Citations

  • Limited capability zones for wireless devices

    WO2022154730A1