Determination of transmission region for ue

Abstract

Various aspects of the disclosure relate to a UE, a processor for wireless communication, a network entity, a method, and a computer readable medium for determining a transmission zone for a UE. The UE receives, from a network entity, not transmit zone (NTZ) information for an NTZ; determines, based on the NTZ information, whether the UE is in the NTZ; and refrains, based on the determination that the UE is in the NTZ, from transmitting in the NTZ. In this way, the UE can be indicated of information regarding the NTZ in a simple and effective manner, and refrain from transmitting in the NTZ.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to user equipment (UE) in a prohibited transmission zone for a UE, network entities, processors, methods for wireless communications, and computer-readable media. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may also support wireless communication across various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies after 5G (e.g., sixth-generation W (6G)).

[0003] In 5G, the UAV (Unmanned Aerial Vehicle) UE (User Equipment) feature was introduced in Release 18. For Release 19, the handling of UAV UEs needs to consider the No-Transmit Zone (NTZ), which is defined as a geographical area where, for spectrum compatibility purposes, a UAV UE is not allowed to transmit within a given Coordinated Mobile / Fixed Communication Network (MFCN) frequency band or a portion thereof. In other words, for a specific geographical area and a specific frequency band, a UAV UE is not allowed to transmit. This differs from traditional no-fly zones. A UAV UE can still fly within the NTZ and can monitor and receive signaling from the network, but is not permitted to transmit. Several issues regarding the NTZ still require further investigation. Summary of the Invention

[0004] This invention relates to a UE, a network entity, a processor, a method for wireless communication, and a computer-readable medium for a no-transmission zone (NTZ) for a UE. According to embodiments of this disclosure, the UE can be instructed with information about the NTZ in a simple and effective manner, and transmission within that NTZ can be prevented.

[0005] In a first aspect, a UE is provided. The UE includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive NTZ information of a forbidden transmission zone (NTZ) from a network entity via the transceiver; determine, based on the NTZ information, whether the UE is in the NTZ; and, based on the determination that the UE is in the NTZ, prevent the UE from transmitting in the NTZ.

[0006] In a second aspect, a network entity is provided, comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit NTZ information of a forbidden transmission zone (NTZ) to a user equipment (UE) via the transceiver; and determine, based on the UE being in the NTZ, to prevent the UE from transmitting in the NTZ.

[0007] In a third aspect, a processor for wireless communication is provided. The processor includes at least one memory; and a controller coupled to the at least one memory, and is configured such that the controller: receives NTZ information of a forbidden transmission zone (NTZ) from a network entity; determines, based on the NTZ information, whether a UE is in the NTZ; and, based on the determination that the UE is in the NTZ, prevents the UE from transmitting in the NTZ.

[0008] In a fourth aspect, a method performed by a user equipment (UE) is provided, the method comprising: receiving NTZ information of a forbidden transmission zone (NTZ) from a network entity; determining, based on the NTZ information, whether the UE is in the NTZ; and, based on determining that the UE is in the NTZ, preventing the UE from transmitting in the NTZ.

[0009] In the fifth aspect, a method performed by a network entity is provided, the method comprising: sending NTZ information of a forbidden transmission zone (NTZ) to a user equipment (UE); and determining, based on the UE being in the NTZ, to prevent the UE from transmitting in the NTZ.

[0010] In a sixth aspect, a computer-readable medium is provided having instructions stored thereon that, when executed by a processor of a device, cause the device to perform the method according to the fourth or fifth aspect of this disclosure.

[0011] In some implementations of methods, UEs, and network entities, NTZ information can indicate the geographical area of ​​the NTZ.

[0012] In some implementations of methods, UEs, and network entities, NTZ information may include one of the following: a geographic region index; a series of geographic points; or a reference location and its corresponding radius.

[0013] In some implementations of the method, UE, and network entity, the NTZ information may also indicate at least one of the following: at least one altitude range; and at least one prohibited frequency band.

[0014] In some implementations of the method, UE, and network entity, the UE can determine whether it is in the NTZ based on the determination that the triggering condition is met.

[0015] In some implementations of the method, UE, and network entity, the triggering condition may include at least one of the following: when the NTZ information is received; when the cell is selected or reselected; during handover; when the unified access control (UAC) procedure is performed; or when the unmanned aerial vehicle (UAV) service is initiated.

[0016] In some implementations of the method, UE, and network entity, the UE can periodically determine whether it is in the NTZ or after it has traveled a certain distance since the last determination.

[0017] In some implementations of the method, UE, and network entity, the UE can determine whether the UE is in the NTZ based on certain conditions, including at least one of the following: whether the UE's geographical location is within the geographical area indicated in the NTZ information; whether the UE's altitude is within the altitude range indicated in the NTZ information; and whether the frequency band used is included in the frequency band list indicated in the NTZ information.

[0018] In some implementations of the method, UE, and network entity, the UE may define a unified access control (UAC) configuration that includes NTZ information; and determine whether the UE is in the NTZ by performing a UAC procedure based on the UAC configuration.

[0019] In some implementations of the method, UE, and network entity, the UAC configuration may include blocking parameters that include NTZ information associated with the UE’s Access Identifier (AI) and Access Class (AC).

[0020] In some implementations of the method, UE, and network entity, the UE can change its communication frequency band to the supported frequency band based on the determination that the UE supports a frequency band that does not belong to the NTZ.

[0021] In some implementations of the method, UE, and network entity, the UE can report to the network entity that the UE is in the NTZ via dedicated radio resource control (RRC) signaling; and change the communication frequency band to a supported frequency band based on handover or redirection messages from the network entity.

[0022] In some implementations of the method, UE, and network entity, the UE can enter Radio Resource Control Idle (RRC_IDLE) mode based on the determination that the UE does not support frequency bands other than those belonging to the NTZ.

[0023] In some implementations of the method, UE, and network entity, the UE can report to the network entity that the UE is in the NTZ via a new reason in the RRC recovery request message; and enter RRC_IDLE mode based on a rejection or release message from the network entity.

[0024] In some implementations of the method, UE, and network entity, the UE can prevent the UE from initiating an RRC connection or returning to the cell on the prohibited frequency band based on the determination that the UE is in the NTZ and the UE is in RRC_IDLE mode.

[0025] In some implementations of the method, UE, and network entity, the UE can start a timer based on determining that the UE is not in the NTZ; and after the timer expires, determine that the UE has left the NTZ, wherein the timer is reset based on determining that the UE is in the NTZ.

[0026] In some implementations of methods, UEs, and network entities, the UE can be an unmanned aerial vehicle (UAV) UE.

[0027] In some implementations of the method, UE, and network entity, the network entity may receive a report from the UE via dedicated RRC signaling, which indicates that the UE is in the NTZ; or it may determine that the UE is in the NTZ based on the UE's location information and NTZ information.

[0028] In some implementations of the method, UE, and network entity, the network entity may send a handover or redirection message to the UE based on the determination that the UE supports a frequency band that does not belong to the NTZ. The handover or redirection instructs the UE to change the communication frequency band to the supported frequency band.

[0029] In some implementations of the method, UE, and network entity, the network entity may send a rejection or release message to the UE based on determining that the UE does not support frequency bands other than those belonging to the NTZ. The rejection or release message instructs the UE to enter Radio Resource Control Idle (RRC_IDLE) mode, in which the UE is not allowed to initiate RRC connections or recover to the cell on the prohibited frequency bands. Attached Figure Description

[0030] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are shown.

[0031] Figure 2A schematic diagram of existing problems with the No-Transmission Zone (NTZ) for UAV UEs is shown.

[0032] Figure 3 Examples of process flows for NTZ are shown according to some exemplary embodiments of this disclosure.

[0033] Figures 4A-4C A schematic diagram illustrating an example of NTZ information according to some exemplary embodiments of this disclosure is shown.

[0034] Figure 5 Examples of devices suitable for implementing some embodiments of this disclosure are shown.

[0035] Figure 6 Examples of processors suitable for implementing some embodiments of this disclosure are shown.

[0036] Figure 7 A flowchart of a method performed by a user equipment according to aspects of this disclosure is shown.

[0037] Figure 8 A flowchart is shown of a method performed by a network entity according to aspects of this disclosure.

[0038] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0039] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0040] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment necessarily must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) such a feature, structure, or characteristic may affect such a feature, structure, or characteristic within the scope of their knowledge.

[0041] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that selection can be made from a number of functional alternatives used, and that these selections are not necessarily better, smaller, higher, or otherwise preferred than other selections.

[0042] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “comprising,” and / or “containing,” when used herein, specify the presence of said features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0043] For version 19, the handling of UAV UEs needs to consider the Forbidden Transmission Zone (NTZ), which is defined as a geographical area where, for spectrum compatibility purposes, a UAV UE is not allowed to transmit within a given Coordinated Mobile / Fixed Communications Network (MFCN) frequency band or a portion thereof. The UAV UE can fly within the NTZ and can monitor and receive signaling from the network, but is not permitted to transmit or transmit within the Forbidden Zone.

[0044] To instruct UAV UEs in the NTZ context, it is proposed to introduce a bit as a UAV UE-specific cell blocking parameter in System Information Block 1 (SIB1) broadcast by the cell in the NTZ. The UAV UE is then prohibited from accessing cells within the NTZ. However, it is still possible for a UAV UE in the NTZ to access cells at a distance and perform transmissions within the NTZ; however, a UAV UE located outside the NTZ, if it receives such a blocking parameter, will be unintentionally prohibited from accessing cells within the NTZ.

[0045] In view of the above, this disclosure proposes a solution to the aforementioned problems. According to an embodiment of this disclosure, the UE can receive NTZ information from a network entity. The UE determines whether it is in the NTZ based on this NTZ information. Based on the determination that the UE is in the NTZ, the UE is prevented from transmitting within the NTZ.

[0046] Details will be provided below regarding how the network instructs the NTZ information to the UE, how the UE determines its presence in the NTZ based on the network's instructions, and what the UE's behavior is when it enters or leaves the NTZ.

[0047] The aspects of this disclosure are described in the context of wireless communication systems. Figure 1 Examples of wireless communication systems 100 that may be implemented in accordance with some embodiments of this disclosure are shown. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Wireless communication system 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0048] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more network entities among the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface. In a 3GPP non-terrestrial network (NTN), network entity 102, in the form of a satellite, may communicate directly with UE 104 using an NR / LTE Uu interface. This satellite may be a transparent satellite or a regenerated satellite. For an NTN with a transparent satellite, a terrestrial base station may communicate with the UE via the satellite. For an NTN with a regenerated satellite, the base station may be located on the satellite and communicate directly with the UE.

[0049] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0050] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0051] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0052] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0053] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as wireless heads, smart wireless heads, or transmit-receive points (TRPs).

[0054] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0055] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0056] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0057] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0058] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, supported by corresponding network entities 102 communicating via such communication links.

[0059] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core network (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0060] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0061] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0062] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0063] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0064] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ=4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technology. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technology. It should be understood that for the first digital technology (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0065] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0066] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ=2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0067] Figure 2 A schematic diagram illustrates the existing problems with the No-Transmit Zone (NTZ) for UAV UEs. According to existing methods for handling NTZ for UAV UEs, the network entity (e.g., a base station) of the cell in the NTZ broadcasts a blocking parameter (e.g., a 1-bit indication) in the SIB. When the UAV UE is flying in the NTZ, it receives this blocking parameter and is prohibited from accessing the cell in the NTZ. However, this method has several problems.

[0068] like Figure 2 As shown, UAV UE#1 is flying within the NTZ, but may access cells located in distant areas. That is, even if UAV UE#1 is flying within the NTZ, it can access cells outside the NTZ and still perform transmissions within the NTZ. On the other hand, UAV UE#2 is flying outside the NTZ, but may receive blocking parameters from cells within the NTZ. Therefore, UAV UE#2, flying outside the NTZ, is incorrectly prohibited from accessing cells within the NTZ.

[0069] Figure 3 An example of a process flow 300 for NTZ is shown according to some exemplary embodiments of the present disclosure. Process flow 300 may involve a UE 301 and a network entity (e.g., a base station) 302. Process flow 300 may refer to... Figure 1 Applied to the wireless communication system 100, for example, UE 201 can be any of UE 104, and network entity 302 can be any of network entity 102. In some embodiments, UE 301 can be a UAV UE. It should be understood that process flow 300 can be applied to other communication scenarios.

[0070] At 310, network entity 302 can send NTZ information 315 of the prohibited transmission zone (NTZ) to UE 301. Accordingly, UE 301 can receive NTZ information 315 from network entity 302. Network entity 302 can be located within or outside the NTZ. In some embodiments, network entity 302 can configure or indicate NTZ information to UE 301 via, for example, broadcast messages or dedicated Radio Resource Control (RRC) signaling. More specifically, the NTZ information indicated by the network entity can indicate the following: which geographical areas(s) belong to the NTZ, and optionally which altitude ranges(s) corresponding to the NTZ(s) geographical areas(s) belong to the NTZ, and optionally which frequency bands(s) within a specific NTZ geographical area belong to the NTZ, i.e., in that NTZ area, UAV transmission is prohibited on that frequency band.

[0071] In some embodiments, the NTZ geographic region can be indicated via a geographic region index. Figure 4A A schematic diagram illustrating an example of a geographic region index according to some exemplary embodiments of this disclosure is shown.

[0072] like Figure 4A As shown, the region index can be calculated based on the configured length (L) and width (W) of the region, and the geodesic distance of the UE's current location from the geographic coordinates (0,0), which can be defined according to the WGS84 model. The length (L), width (W), and distance can be expressed in units such as meters and kilometers. Furthermore, information for regions larger than the region can be indicated, such as indexes for districts, cities, provinces, etc., indicating which larger region the region belongs to. For example, UE 301 can determine its region index as follows: x 1 = FLOOR ( x / L) Mod Nx ; y 1 = FLOOR ( y / W) Mod Ny ; Zone_id = y 1 Nx + x 1. Where W / L represents the configured region width / length. Nx / Ny Configured by the network to indicate how many times the region index can be reused on longitude / latitude. x / yThis is the geodesic distance in longitude / latitude between the UE's current location and its geographic coordinates (0,0), for example, according to the WGS84 model. If... N x=2, N If y=3, then the regional index is as follows: Figure 4A As shown in the figure. In some embodiments, the NTZ geographic region list may be indicated via multiple regional indexes.

[0073] Alternatively or alternatively, the NTZ geographic area can be indicated by a series of geographic points. Figure 4B A schematic diagram illustrating an example of a geographic point according to some exemplary embodiments of this disclosure is shown.

[0074] For example, such as Figure 4B As shown, four geographic points can represent a square area, where one point is indicated by geodetic latitude and longitude, or the point field is defined in TS37.355. Ellipsoid-Point Similarly. Alternatively, NTZ geographic regions can also be represented by other numbers of points, such as 3 points, 5 points, 6 points, etc., for a triangular region. In some embodiments, the list of NTZ geographic regions can be indicated by a network, and the list can include multiple series of geographic points.

[0075] Alternatively, or as an alternative location, the NTZ geographic area can be indicated by a reference location and a corresponding radius. Figure 4C A schematic diagram illustrating an example of an NTZ geographic region defined by a circle according to some exemplary embodiments of this disclosure is shown. Figure 4C In this context, the reference location can be geodetic longitude and latitude, or the reference location field can be the same as defined in TS37.355. Ellipsoid-Point Same. The radius indicates the radius of the NTZ region.

[0076] Reference Figure 3 At 330, UE 301 determines whether it is in the NTZ based on NTZ information. UE 301 can trigger this determination by comparing its location, the frequency band it uses, and / or its flight altitude with the received NTZ information 315. UE 310 can trigger this determination based on the fulfillment of a determination triggering condition. More specifically, UE 301 can trigger this determination when it receives (new) NTZ information from network entity 302. Alternatively, UE 301 can trigger this determination during cell selection or reselection. Alternatively, UE 301 can trigger this determination during handover. Alternatively, UE 301 can trigger this determination during a unified access control (UAC) procedure. Alternatively, UE 301 can also trigger this determination when initiating (multiple) UAV services.

[0077] In some embodiments, UE 301 may also trigger the determination periodically. UE 301 may trigger the determination at certain travel distances, that is, after the UE has traveled a certain distance since the last determination, it will start checking again whether it is in the NTZ. The period or distance used for determination may be configured by network entity 302 or other network entities.

[0078] When performing this determination, UE 301 can compare its geographic location, flight altitude, and the frequency band(s) it supports or is using with NTZ information received from the network. If the following conditions are met, it is determined that it is in the NTZ: whether the UE's geographic location is in the NTZ geographic area indicated by the network configuration; whether the flight altitude is within the altitude range indicated by the NTZ (if configured); and whether the frequency band(s) it uses is in the frequency band list of the NTZ (if configured).

[0079] In some embodiments, UE 301 and the network can determine whether it is in the NTZ based on a UAC scheme. The network and UE 301 can configure NTZ information and block the UE from accessing the network. More specifically, a new Access Identifier (AI) or a legacy AI reserved for future use can be defined for UE 301 targeting UAV type devices. An existing Access Class (AC) is also used for UE 301, or a new Access Class (AC) can be defined, for example, for access attempts targeting UAV services for UAV UEs. Specific blocking parameters associated with the AC and AI used for the UE can be configured by the network for the AI ​​and AC, where NTZ information is included. Along with the NTZ information, the network can also configure corresponding waiting times or other information for the AI ​​and AC.

[0080] UE 301 can perform UAC based on UAC configuration to determine whether the UE is in the NTZ. When performing UAC, if AI and AC are indicated, UE 301 can determine whether it is in the NTZ by comparing its location, frequency band, and / or flight altitude with the NTZ information configured by the network-configured UAC. If UE 301 determines that it is in the NTZ, it considers the access attempt to be blocked. The UAV UE can optionally enable a timer based on a configured wait time.

[0081] Alternatively, the UE may send its location information to network entity 302 to request network entity 302 to perform the determination. Network entity 302 may determine whether UE 301 is in the NTZ based on the location information and NTZ information. Then, network entity 302 may indicate the determination result to UE 301.

[0082] At point 340, based on the determination that the UE is in the NTZ, UE 301 can prevent the UE from transmitting in the NTZ. At point 350, based on the determination that the UE is in the NTZ, network entity 302 can also prevent the UE from transmitting in the NTZ. (UE and network entity). In this document, "preventing" means that the UE is not allowed to transmit on at least one or more prohibited frequency bands, but may be allowed to transmit on frequency bands not belonging to the NTZ. Note that the operations in points 310 and 350 can be implemented at the same network entity or different network entities.

[0083] The determination of whether the UE is in the NTZ can be aligned between UE 301 and network entity 302 to control the UE's behavior, making UE 301 silent in the indicated NTZ. Different processing will be applied to UEs in different RRC states, and to whether the UE supports frequency bands other than the NTZ.

[0084] In some embodiments, once it is determined that the UE is in or entering an NTZ, if the UE supports a frequency band other than that belonging to the NTZ, the UE can change its communication frequency band to another frequency band not belonging to the NTZ based on its RRC status. For example, for a UE in RRC_CONNECTED mode, the UE can report its location information to the network entity, and the network entity determines whether the UAV UE is in the NTZ; alternatively, the UE can determine on its own that it is entering or in the NTZ and report its presence in the NTZ to the network entity via dedicated RRC signaling (e.g., a UE auxiliary information message). The network entity can then hand over the UE to another carrier or cell. For a UE in RRC_INACTIVE mode, the UE can report its entry into the NTZ or its location information to the network entity in an RRCResumeRequest message, which may include a new reason to indicate to the network entity that this message was caused by the NTZ. Upon receiving such a message, the network entity can release the UE and redirect it to another carrier or cell. For example, the network entity can send a handover or redirection message to the UE instructing it to change its communication frequency band to a supported frequency band.

[0085] If the UE does not support frequency bands other than those not belonging to the NTZ, the UE can enter RRC_IDLE mode. For a UE in RRC_CONNECTED mode, the UE can report its location information to the network entity, which determines whether the UE is entering or in the NTZ. Alternatively, the UE can determine whether it is entering or in the NTZ itself and report this to the network entity. The network entity can then release the UE into RRC_IDLE mode. For a UE in RRC_INACTIVE mode, the UE can report its entry into or in the NTZ, or its location information, to the network entity via an RRCResumeRequest message. The UE can include a new reason to indicate that the message was caused by the NTZ. Upon receiving such a message, the network entity can reject the UE, and the UE will enter RRC_IDLE mode. For example, the network entity can send a reject or release message to the UE, which instructs the UE to enter RRC_IDLE mode. If the UE is in RRC_IDLE mode and the UE determines that it is in the NTZ, the UE is not allowed to initiate (multiple) RRC connections or recover to the cell on the prohibited frequency band.

[0086] In some embodiments, if the UE supports frequency bands other than those belonging to the NTZ, and if the NTZ does not allow the UE to camp on that cell, then for a UE in RRC_IDLE mode, the UE can trigger a cell (re)selection on the cell in other supported frequency bands not belonging to the NTZ.

[0087] To mitigate ping-pong behavior when a UE is leaving the NTZ area, a timer can be introduced. The UE can start a timer based on the determination that it is not in the NTZ (e.g., its geographical location is not in the NTZ). If the UE is determined to be in the NTZ, the timer is reset. The timer value can be configured by the network. After the timer expires, the UE can determine that it has left the NTZ.

[0088] According to the reference Figure 3 and Figures 4A to 4C In some of the embodiments discussed, the UE can be instructed about NTZ information in a simple and effective manner, and transmission in NTZ can be prevented.

[0089] Figure 5Examples of devices suitable for implementing some embodiments of this disclosure are shown. Device 500 may be an example of UE 104 or network entity 102 as described herein. Device 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 502, memory 504, transceiver 506, and (optionally) I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0090] Processor 502, memory 504, transceiver 506, or various combinations thereof or components thereof may be examples of parts for performing various aspects of the present disclosure as described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof or components thereof may support methods for performing one or more operations described herein.

[0091] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 504 by processor 502).

[0092] For example, processor 502 may support wireless communication at device 500 according to examples disclosed herein. Processor 502 may be an example of UE 104. In this case, processor 502 may be configured to support: components for receiving NTZ information of a forbidden transmission zone (NTZ) from a network entity; components for determining whether a UE is in the NTZ based on the NTZ information; and components for preventing the UE from transmitting in the NTZ based on the determination that the UE is in the NTZ.

[0093] Device 500 may be an example of network entity 102, such as a network entity. In this case, processor 502 may be configured to support: components for sending NTZ information of the prohibited transmission zone (NTZ) to the user equipment (UE); and components for determining, based on the UE being in the NTZ, to prevent the UE from transmitting in the NTZ.

[0094] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0095] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0096] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device 500. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor (such as processor 506). In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0097] In some implementations, device 500 may include a single antenna 810. However, in other implementations, device 500 may have more than one antenna 810 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that can concurrently transmit or receive multiple wireless transmissions. Transceiver 506 can communicate bidirectionally via one or more antennas 810, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 810 for transmission, and demodulating packets received from one or more antennas 810. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0098] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 810 for transmitting the amplified signal over the air or wireless medium.

[0099] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 810 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0100] Figure 6Examples of processor 600 suitable for implementing some embodiments of the present disclosure are shown. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0101] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 600)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0102] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations as described herein. For example, controller 602 can operate as a control unit of processor 600 to generate control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0103] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, enabling processor 600 to support various operations as described herein. Controller 602 may be configured to track memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operation to be performed and its operands. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600, enabling processor 600 to support various operations as described herein. Alternatively or additionally, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0104] Memory 604 may include one or more caches (e.g., local to processor 600 or included in processor 600) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside inside or on the processor chipset (e.g., local to processor 600). In other implementations, memory 604 may reside outside the processor chipset (e.g., remote from processor 600).

[0105] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions (e.g., functions or tasks supporting transmit power prioritization). For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0106] One or more ALU 606s can be configured to support various operations as described herein. In some implementations, one or more ALU 606s may reside within or on a processor chipset (e.g., processor 600). In other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 606s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively or otherwise, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0107] Processor 600 may support wireless communication according to examples disclosed herein. Processor 600 may be implemented at UE 104. In this case, processor 600 may be configured to support: components for receiving NTZ information of a forbidden transmission zone (NTZ) from a network entity; components for determining whether a UE is in the NTZ based on the NTZ information; and components for preventing the UE from transmitting in the NTZ based on the determination that the UE is in the NTZ.

[0108] The processor 600 may be implemented at network entity 102, such as a base station. In this case, the processor 600 may be configured to support: components for transmitting forbidden transmission zone (NTZ) information to user equipment (UE); and components for preventing the UE from transmitting in the NTZ based on the determination that the UE is in the NTZ.

[0109] Figure 7 A flowchart of method 700 performed by a UE according to aspects of this disclosure is shown. Operation of method 700 may be implemented by a device or its components as described herein. For example, operation of method 800 may be performed by a UE 104 as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the function.

[0110] At 710, the method may include: receiving NTZ information of a forbidden transmission zone (NTZ) from a network entity. The operation at 710 can be performed according to the examples described herein. In some implementations, aspects of the operation at 710 may be provided by reference to [reference needed]. Figure 1 The UE 104 described is executed.

[0111] At 720, the method may include: determining whether the UE is in the NTZ based on NTZ information. The operation at 720 can be performed according to the examples described herein. In some implementations, aspects of the operation at 720 may be as described in the references... Figure 1 The UE 104 described is executed.

[0112] At 730, the method may include: based on determining that the UE is in the NTZ, preventing the UE from transmitting in the NTZ. The operation at 730 can be performed according to the examples described herein. In some implementations, aspects of the operation at 730 may be as described in the references... Figure 1 The UE 104 described is executed.

[0113] Figure 8 A flowchart of method 800 performed by a network entity according to aspects of this disclosure is shown. The operation of method 800 may be implemented by a device or components thereof as described herein. For example, the operation of method 800 may be performed by network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the function.

[0114] At 810, the method may include: sending NTZ information of a forbidden transmission zone (NTZ) to a user equipment (UE). The operation of 810 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1210 may be derived from references... Figure 1 The network entity 102 described is executed.

[0115] At 820, the method may include: based on determining that the UE is in the NTZ, preventing the UE from transmitting in the NTZ. The operation at 820 can be performed according to the examples described herein. In some implementations, aspects of the operation at 820 may be as described in the references... Figure 1 The network entity 102 described is executed.

[0116] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0117] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The 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 combined with a DSP core, or any other such configuration).

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

[0119] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0120] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two 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). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0121] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as A transceiver, the transceiver being coupled to the processor, The processor is configured as follows: The transceiver receives NTZ information of the forbidden transmission zone (NTZ) from the network entity. Based on the NTZ information, determine whether the UE is in the NTZ; as well as Based on the determination that the UE is in the NTZ, the UE is prevented from transmitting in the NTZ.

2. The UE according to claim 1, wherein the NTZ information indicates the geographical region of the NTZ.

3. The UE according to claim 2, wherein the NTZ information includes one of the following: Geographic region index; A series of geographical points; or Reference location and corresponding radius.

4. The UE of claim 2, wherein the NTZ information further indicates at least one of the following: At least one height range; and At least one prohibited frequency band.

5. The UE according to claim 1, wherein the processor is configured to determine whether the UE is in the NTZ based on the determination that a trigger condition is met.

6. The UE according to claim 5, wherein the triggering condition includes at least one of the following: When receiving the NTZ information; When selecting or reselecting a community; During switching; When executing the Unified Access Control (UAC) procedure; or When initiating a UAV (Unmanned Aerial Vehicle) service.

7. The UE of claim 1, wherein the processor is configured to periodically determine whether the UE is in the NTZ or after the UE has traveled a certain distance since the last determination.

8. The UE of claim 1, wherein the processor is configured to: determine whether the UE is in the NTZ based on determining conditions, the determining conditions including at least one of the following: Whether the geographical location of the UE is within the geographical area indicated in the NTZ information; Is the height of the UE within the height range indicated in the NTZ information? Whether the frequency band used is included in the frequency band list indicated in the NTZ information.

9. The UE of claim 1, wherein the processor is configured to determine whether the UE is in the NTZ by: Define a unified access control (UAC) configuration, wherein the UAC configuration includes the NTZ information; and The UE is determined to be in the NTZ by performing the UAC procedure based on the UAC configuration.

10. The UE of claim 1, wherein the UAC configuration includes blocking parameters, the blocking parameters including the NTZ information associated with the Access Identifier (AI) and Access Class (AC) for the UE.

11. The UE of claim 1, wherein the processor is configured to prevent the UE from transmitting in the NTZ by: Based on the determination that the UE supports a frequency band that does not belong to the NTZ, the communication frequency band of the UE is changed to the supported frequency band.

12. The UE of claim 11, wherein changing the communication frequency band of the UE comprises: The UE is reported to the network entity in the NTZ via dedicated radio resource control (RRC) signaling; as well as Based on the switching or redirection message from the network entity, the communication frequency band is changed to the supported frequency band.

13. The UE of claim 1, wherein the processor is configured to prevent the UE from transmitting in the NTZ by: Based on the determination that the UE does not support any frequency bands other than the NTZ, it enters the Radio Resource Control (RRC) Idle mode.

14. The UE of claim 13, wherein entering RRC_IDLE mode comprises: The network entity is notified that the UE is in the NTZ via a new reason in the RRC recovery request message; as well as Based on the rejection or release message from the network entity, enter RRC_IDLE mode.

15. The UE of claim 13, wherein the processor is further configured to: Based on the determination that the UE is in the NTZ and the UE is in RRC_IDLE mode, the UE is prevented from initiating an RRC connection or returning to the cell on the prohibited frequency band.

16. The UE of claim 1, wherein the processor is further configured to: Based on the determination that the UE is not in the NTZ, a timer is started; and After the timer expires, it is determined that the UE has left the NTZ, and the timer is reset based on the determination that the UE is in the NTZ.

17. A network entity, comprising: processor; as well as A transceiver, the transceiver being coupled to the processor, The processor is configured as follows: The transceiver transmits NTZ information of the forbidden transmission zone (NTZ) to the user equipment (UE); and Based on the determination that the UE is in the NTZ, the UE is prevented from transmitting in the NTZ.

18. The network entity of claim 17, wherein the NTZ information indicates the geographic region of the NTZ and includes one of the following: a geographic region index; a series of geographic points; or a reference location and a corresponding radius; and The NTZ information also indicates at least one of the following: at least one altitude range; or at least one prohibited frequency band.

19. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured such that the controller: Receive NTZ information from network entities in the forbidden transmission zone (NTZ). Based on the NTZ information, determine whether the UE is in the NTZ; as well as Based on the determination that the UE is in the NTZ, the UE is prevented from transmitting in the NTZ.

20. A method performed by a user equipment (UE), the method comprising: Receive NTZ information from network entities in the forbidden transmission zone (NTZ). Based on the NTZ information, determine whether the UE is in the NTZ; as well as Based on the determination that the UE is in the NTZ, the UE is prevented from transmitting in the NTZ.

Images