No-transmit zones for aerial user equipments (UES)

Abstract

A method implemented in a user equipment, UE, includes: receiving No-Transmit Zone, NTZ, information sufficient to cause the UE's compliance with an NTZ when a location of the UE is in the NTZ; and operating in accordance with the NTZ information.

Description

[0001] NO-TRANSMIT ZONES FOR AERIAL USER EQUIPMENTS (UES)

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to support of no-transmit zones in aerial user equipments (UEs).

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] 3GPP Technical Specification Group (TSG) Service and System Aspects (SA) (SA2) has started the work on “Study on Phase 3 for UAS, UAV and UAM,”, and this FS_UAS_Ph3 items includes the objective on how to support no-transmit zones for Uncrewed Aerial Vehicles (UAVs) UE (i.e., UE with aerial subscription (UAV UE)). This objective is considered due to the fact that the European Conference of Postal and Telecommunications (CEPT) Decision 22(07) on harmonized technical conditions for the usage of aerial UEs for communications based on LTE and 5G NR in several bands harmonized for Mobile / Fixed Communications Networks (MFCN) includes the requirement related to operational restrictions in the form no-transmit zones (NTZs). Regarding this aspect, TSG RAN agreed that the NTZ requirement will be addressed and sent Liaison Statements (LS) on support of no-transmit zones for UAVs to SA2. Therefore, support of no-transmit zones for UAVs needs to be considered.

[0007] In this regard, SA2 has started work that is being documented in, e.g., 3GPP Technical Report (TR) 23.700-59. The following has been formulated:

[0008] Excerpt from clause 5.3 of TR 23.700-59:

[0009] 5.3 Key Issue #3: Support of No Transmit Zones

[0010] 5.3.1 Description

[0011] This key issue relates to the introduction by CEPT ECC Decision 22(07) of No Transmit Zones for aerial UEs. The ECC Decision asserts that a mechanism is necessary to ensure that aerial UEs respect no-transmit zones in order to protect incumbent radio systems from potential interference from aerial UEs.

[0012] Since the ECC Decision does not identify any specific RAT, NTZs can be supported by both LTE and NR.

[0013] This key issue addresses the following aspects:

[0014] How to ensure an aerial UE respects no-transmit zones, including: whether a mobile network cells overlapping completely or partially with the NTZ and using the restricted frequency bands of the NTZ; whether mechanisms are needed to differentiate aerial UEs that support functions defined for NTZs in Rel. 19 and aerial UEs that don't; what if any, specific aerial UE behaviour when the aerial UE approaches, enters, or exits the NTZ.

[0015] Whether and how to enable configuration of NTZ information in the aerial UE.

[0016] Whether to allow the enforcement of no-transmit zone(s) for both aerial UEs in connected mode and aerial UEs in idle mode and if yes then how.

[0017] Editor's note: Interaction with potential other regulatory services is TBD.

[0018] NOTE: Any potential solutions developed shall be coordinated with RAN VPG.s or progressed together with RAN VPG.s input.

[0019] Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking has been specified in, e.g., 3GPP Release 18 (Rel-18) Technical Specification (TS) 23.256, however, there is no support for no-transmit zones. Therefore, no mechanism exist that can fulfil and address Electronic Communications Committee (ECC) decision for enforcement of NTZs in 3GPP networks.

[0020] SUMMARY

[0021] Some embodiments advantageously provide methods, systems, and apparatuses for support of no-transmit zones in UAV UEs.

[0022] Some embodiments may relate to:

[0023] (i) Delivering NTZ information from the Application Function (AF) / Uncrewed Aerial System Traffic Management (UTM) to RAN nodes (gNB / eNB)

[0024] (ii) Delivering NTZ information from RAN nodes to UEs with the corresponding subscription

[0025] (iii) Delivering NTZ information updates from AF / UTM 110 (iv) Ensuring the differentiation of aerial UEs compliant and non-compliant with NTZ requirements

[0026] (v) Notifying AF / UTM 110 about UEs not complying to NTZ requirements

[0027] (vi) Blocking UL data traffic for UEs in NTZ zones

[0028] All together these aspects ensure that UAV UEs respect no-transmit zones.

[0029] Some embodiments may assume that an aerial UE indicates its capability to respect no-transmit zones (NTZ), and UE’s subscription data has a record of that, as Operators may have to enforce the NTZ respect, and the subscription-based approach is one possibility, as described below.

[0030] Several options / alternatives are considered when comes to obtaining NTZ information, including preconfiguration at the relevant network nodes (e.g., gNodeB (gNB) / eNodeB(eNB), AMF / MME) as well as a network-based configuration of NTZ parameters (e.g. geographical area in form of coordinates (i.e., latitude and longitude), restricted frequency band(s), altitude / elevation etc.).

[0031] To perform network-based configuration of NTZ parameters, it may be assumed that there may need to be operator’s AF with trust relation for this purpose. This AF can be part of Uncrewed Aerial System Traffic Management (UTM) , which is outside operator’s trust domain, and therefore, the AF will invoke a service operation towards an UAS NF / NEF so that the NTZ information can be transferred towards RAN nodes (i.e., gNBs in case of 5GC and eNB in case of EPC), core network (CN) entities and to the affected aerial UEs. Finally, depending on whether this type of UEs is allowed to transmit uplink (UL) data for emergency support or only allowed to receive downlink (DL) data, the UAV UE could send the updated registration or deregister / register to remove the UAV registration and become a regular UE and make emergency access in such cases if / where it can transmit UL.

[0032] Existing approaches assume that the aerial UEs will not require emergency services support and, if such a UE exists that serves as a normal UE, then the UE must deactivate UAV operation in order to invoke such services.

[0033] Until otherwise indicated, in some cases it may be assumed that the NTZ does not allow UEs to send uplink data but allows reception of downlink data from the network node. Also, aerial UEs within NTZ(s) are able to communicate with the network node for mobility / registration procedures for the purposes of keeping connectivity with the network. According to one aspect of the present disclosure, a method implemented in a UE is provided. The method includes: receiving No-Transmit Zone, NTZ, information sufficient to cause the UE’s compliance with an NTZ when a location of the UE is in the NTZ; and operating in accordance with the NTZ information.

[0034] According to one or more embodiments of this aspect, the NTZ information is one of: received via Radio Resource Control signaling; received in response to requesting registration; or received from a Policy Control Function, PCF, over a PC5 interface.

[0035] According to one or more embodiments of this aspect, the NTZ information is received from a network node, the NTZ information being one of: propagated to the network node via node-level signalling; configured at the network node by Operation and Maintenance; or configured at the network node by an Access and Mobility Function, AMF.

[0036] According to one or more embodiments of this aspect, the NTZ information is propagated to the network node via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE.

[0037] According to one or more embodiments of this aspect, the method further includes receiving an indication that the UE is in non-compliance with the NTZ.

[0038] According to one or more embodiments of this aspect, the method further includes receiving an update to the NTZ information based on a change occurring to the NTZ.

[0039] According to one or more embodiments of this aspect, receiving the update to the NTZ information includes the UE being woken from an idle state as part of a Network Triggered Service Request procedure.

[0040] According to another aspect of the present disclosure, a UE is provided. UE is configured to receive NTZ information sufficient to cause the UE’s compliance with an NTZ when a location of the UE is in the NTZ; and operate in accordance with the NTZ information.

[0041] According to one or more embodiments of this aspect, the NTZ information is one of: received via Radio Resource Control signaling; received in response to requesting registration; or received from a PCF over a PC5 interface.

[0042] According to one or more embodiments of this aspect, the NTZ information is received from a network node, the NTZ information being one of: propagated to the network node via node-level signalling; configured at the network node by Operation and Maintenance; or configured at the network node by an AMF. According to one or more embodiments of this aspect, the NTZ information is propagated to the network node via node-level signalling, and the NTZ information is based on a policy decision by a PCF that takes into account a capability of the UE.

[0043] According to one or more embodiments of this aspect, UE is further configured to receive an indication that the UE is in non-compliance with the NTZ.

[0044] According to one or more embodiments of this aspect, UE is further configured to receive an update to the NTZ information based on a change occurring to the NTZ.

[0045] According to one or more embodiments of this aspect, receiving the update to the NTZ information includes the UE being woken from an idle state as part of a Network Triggered Service Request procedure.

[0046] According to another aspect of the present disclosure, a method implemented in a network node configured to communicate with a UE is provided. The method includes: configuring the UE with NTZ information sufficient to cause the UE’s compliance with an NTZ when a location of the UE is in the NTZ; and operating in accordance with the NTZ information.

[0047] According to one or more embodiments of this aspect, one of: configuring the UE with the NTZ information includes transmitting the NTZ information to the UE via Radio Resource Control signaling; the NTZ information is determined by a PCF; or configuring the UE with the NTZ information includes causing the NTZ information to be transmitted to the UE in response to the UE requesting registration.

[0048] According to one or more embodiments of this aspect, one of: the method includes receiving the NTZ information via node-level signalling; the NTZ information is configured at the network node by Operation and Maintenance; or the NTZ information configured at the network node by an AMF.

[0049] According to one or more embodiments of this aspect, the NTZ information is received by the network node via node-level signalling, and the NTZ information is based on a policy decision by a PCF that takes into account a capability of the UE.

[0050] According to one or more embodiments of this aspect, the method further includes transmitting an indication that the UE is in non-compliance with the NTZ.

[0051] According to one or more embodiments of this aspect, the method further includes transmitting, to the UE, an update to the NTZ information based on a change occurring to the NTZ.

[0052] According to another aspect of the present disclosure, a network node is provided. Network node is configured to: configure a UE with NTZ information sufficient to cause the UE’s compliance with an NTZ when a location of the UE is in the NTZ; and operate in accordance with the NTZ information.

[0053] According to one or more embodiments of this aspect, one of: configuring the UE with the NTZ information includes transmitting the NTZ information to the UE via Radio Resource Control signaling; the NTZ information is determined by a PCF; or configuring the UE with the NTZ information includes causing the NTZ information to be transmitted to the UE in response to the UE requesting registration.

[0054] According to one or more embodiments of this aspect, one of: the network node is configured to receive the NTZ information via node-level signalling; the NTZ information is configured at the network node by Operation and Maintenance; or the NTZ information configured at the network node by an AMF.

[0055] According to one or more embodiments of this aspect, the NTZ information is received by the network node via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE.

[0056] According to one or more embodiments of this aspect, the network node is further configured to transmit an indication that the UE is in non-compliance with the NTZ.

[0057] According to one or more embodiments of this aspect, the network node is further configured to transmit, to the UE, an update to the NTZ information based on a change occurring to the NTZ.

[0058] BRIEF DESCRIPTION OF THE DRAWINGS

[0059] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0060] FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure;

[0061] FIG. 2 is a block diagram of a network node in communication with a user equipment over an at least partially wireless connection according to some embodiments of the present disclosure;

[0062] FIG. 3 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0063] FIG. 4 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0064] FIG. 5 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0065] FIG. 6 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure;

[0066] FIG. 7 is a diagram of an example procedure to provision RAN nodes according to some embodiments of the present disclosure;

[0067] FIG. 8 is a diagram of an example procedure for providing UEs with the NTZ information according to some embodiments of the present disclosure; and

[0068] FIG. 9 is a diagram of an example procedure to support UE compliance with the provided NTZ information according to some embodiments of the present disclosure.

[0069] DETAILED DESCRIPTION

[0070] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to support of no-transmit zones in aerial UEs. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0071] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0072] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0073] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0074] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), a node encompassing functionalities such as Access Management Function (AMF), Network Repository Function (NRF), Unified Data Management (UDM), Network Exposure Function (NEF), Application Function (AF), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0075] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc. Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0076] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0077] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0078] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0079] Unless otherwise defined, all terms (including 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 belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0080] Some embodiments provide for support of no-transmit zones in aerial UEs. Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0081] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0082] A network node 16 is configured to include a support unit 32, which is configured to perform one or more network node 16 functions described herein, including functions related to support of no-transmit zones in aerial UEs. A user equipment 22 is configured to include a NTZ Unit 34, which is configured to perform one or more user equipment 22 functions described herein, including functions related to support of no-transmit zones in aerial UEs.

[0083] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 will now be described with reference to FIG. 2.

[0084] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the UE 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0085] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0086] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include support unit 32 configured to perform one or more network node 16 functions described herein, including functions related to support of no-transmit zones in aerial UEs.

[0087] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0088] The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0089] Thus, the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the UE 22.

[0090] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 84 of the user equipment 22 may include a NTZ Unit 34 configured to perform one or more UE 22 functions described herein, including functions related to support of no-transmit zones in aerial UEs.

[0091] In some embodiments, the inner workings of the network node 16, UE 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0092] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0093] Although FIGS. 1 and 2 show various “units” such as support unit 32, and NTZ Unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0094] FIG. 3 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the support unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to receive information corresponding to an NTZ (Block SI 16). Network node 16 is configured to determine a location of the UE 22 in relation to the NTZ (Block SI 18). Network node 16 is configured to transmit NTZ information to the UE 22 to cause the UE's 22 compliance with the NTZ when the location of the UE 22 is in the NTZ (Block S120).

[0095] In some embodiments, the network node 16 is further configured to determine when the UE is in non-compliance with the NTZ. In some embodiments, the network node 16 is further configured to transmit an update to the NTZ information based on a change occurring to the NTZ. In some embodiments, the network node 16 is further configured to cause the UE to initiate a Network Triggered Service Request procedure.

[0096] FIG. 4 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the NTZ Unit 34), processor 86, radio interface 82 and / or communication interface 60. User equipment 22 is configured to receive NTZ information sufficient to cause the UE's 22 compliance with an NTZ when a location of the UE is in the NTZ (Block SI 22). User equipment 22 is configured to communicate with the network node 16 based on the NTZ information (Block S124).

[0097] In some embodiments, user equipment 22 is configured to receive an indication that the UE 22 is in non-compliance with the NTZ. In some embodiments, user equipment 22 is configured to receive an update to the NTZ information based on a change occurring to the NTZ. In some embodiments, user equipment 22 is configured to initiate a Network Triggered Service Request procedure.

[0098] FIG. 5 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the support unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to configure (Block S125) a UE 22 with No-Transmit Zone, NTZ, information sufficient to cause the UE’s 22 compliance with an NTZ when a location of the UE 22 is in the NTZ. Network node 16 is configured to operate (Block S126) in accordance with the NTZ information.

[0099] In some embodiments, one of: configuring the UE 22 with the NTZ information comprises transmitting the NTZ information to the UE 22 via Radio Resource Control signaling; the NTZ information is determined by a Policy Control Function, PCF 102; or configuring the UE 22 with the NTZ information comprises causing the NTZ information to be transmitted to the UE 22 in response to the UE 22 requesting registration.

[0100] In some embodiments, one of: the network node 16 is configured to receive the NTZ information via node-level signalling; the NTZ information is configured at the network node 16 by Operation and Maintenance; or the NTZ information configured at the network node 16 by an Access and Mobility Function, AMF 100.

[0101] In some embodiments, the NTZ information is received by the network node 16 via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, 102 that takes into account a capability of the UE 22.

[0102] In some embodiments, the network node 16 is further configured to transmit an indication that the UE 22 is in non-compliance with the NTZ.

[0103] In some embodiments, the network node 16 is further configured to transmit, to the UE 22, an update to the NTZ information based on a change occurring to the NTZ.

[0104] FIG. 6 is a flowchart of another example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the NTZ Unit 34), processor 86, radio interface 82 and / or communication interface 60. UE 22 is configured to receive (Block S127) NoTransmit Zone, NTZ, information sufficient to cause the UE’s 22 compliance with an NTZ when a location of the UE 22 is in the NTZ. UE 22 is configured to operate (Block S128) in accordance with the NTZ information.

[0105] In some embodiments, the NTZ information is one of: received via Radio Resource Control signaling; received in response to requesting registration; or received from a Policy Control Function, PCF, 102 over a PC5 interface. In some embodiments, the NTZ information is received from a network node 16, the NTZ information being one of: propagated to the network node 16 via node-level signalling; configured at the network node 16 by Operation and Maintenance; or configured at the network node 16 by an Access and Mobility Function, AMF 100.

[0106] In some embodiments, the NTZ information is propagated to the network node 16 via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, 102 that takes into account a capability of the UE 22.

[0107] In some embodiments, UE 22 is further configured to receive an indication that the UE 22 is in non-compliance with the NTZ.

[0108] In some embodiments, UE 22 is further configured to receive an update to the NTZ information based on a change occurring to the NTZ.

[0109] In some embodiments, receiving the update to the NTZ information comprises the UE 22 being woken from an idle state as part of a Network Triggered Service Request procedure.

[0110] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for support of no-transmit zones in aerial UEs. One or more UE 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, NTZ Unit 34, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, support unit 32, etc.

[0111] Some embodiments relate to the below principles:

[0112] 1. Provisioning RAN (e.g., network node 16 such as gNB / eNB) with a set of NTZ information (e.g., geographical area in form of coordinates (i.e., latitude and longitude), restricted frequency band(s), altitude / elevation etc.), see, e.g., FIG. 7 described in detail below.

[0113] Option 1(a). RAN is provided with NTZ information via a node-level signaling from operator’s AF via UAS NF / NEF 108, PCF 102 and AMF 100 using the AM Policy Association Establishment / Modification procedures (as described, e.g., in clauses 4.16.1 and 4.16.2 of 3GPP TS 23.502).

[0114] Option 1(b). RAN node(s) are configured by Operation and Maintenance (0AM) with the existing NTZ information that can be requested by the AF / UTM 110 from network nodes 16 in the area they serve (e.g., based on RAN node location, Tracking Area(s) identified by a list of tracking area identities (TAI) or a list of cell identities) Option 1(c): Access and Mobility Function (AMF) 100 / MME is preconfigured (e.g., local configuration) with NTZ information; and AMF 100 / Mobility Management Entity (MME) provides the NTZ information to relevant network nodes 16 via non-UE associated signaling (e.g., during NG interface Setup / Reconfiguration procedure), UE-associated signaling (e.g., during Initial Context Setup / Modification procedure or Protocol Data Unit (PDU) session resource management procedures).

[0115] To provide RAN nodes with new / updated NTZ information from the UTM (i.e. triggered by UTM), a node-level signaling from operator’s AF / UTM 110 can be used for Option 1(a), 1(b) and 1(c), whereas reprovisioning via 0AM may in some cases only be done only for Option 1(b).

[0116] 2. UE’s 22 subscription data include and an additional record at UDM, indicating that the UE / UAV (e.g., UE 22) is compliant to NTZs requirements. This allows the operator and the network to enforce NTZ respect and to deliver the NTZ information only to UEs with the corresponding subscription. This indication is made available / delivered to RAN nodes (e.g., network node 16 such as gNB / eNB) so they can enforce the NTZ respect. Additionally, UE’s 22 subscription data at UDM 106 can indicate which set(s) of NTZ are allowed to be disobeyed by high-priority UEs (e.g., first responders).

[0117] 3. Providing the NTZ information to a UE 22 with the corresponding subscription:

[0118] 3(a). RAN (e.g., network node 16 such as gNB / eNB) sends the NTZ information to a UE 22 using the Radio Resource Control (RRC) protocol (dedicated signaling).

[0119] 3(b). The NTZ information is sent to a UE 22 from a core network node (e.g. UAS NF / NEF 108 via an AMF 100 / MME) or from the serving AMF 100 / MME using Non-Access Stratum (NAS) signaling during UE’s 22 registration in a Registration Accept message.

[0120] 3(c). The NTZ information is sent to a UE / UAV from a serving Policy Control Function (PCF) 102 together with a policy update information using a direct communication over PC5 interface.

[0121] The UE / UAV (e.g., UE 22) stores the received NTZ information until the new NTZ information is provided or deleted, e.g., by explicit signaling from the core network (for instance, via AMF 100 / MME NAS signaling) due to request from the AF / UTM 110.

[0122] The main procedural steps to provision RAN nodes (e.g., network node 16 such as gNB / eNB) with the NTZ information is shown in FIG. 7, which depicts a procedure to provision RAN nodes (e.g., network node 16 such as gNB / eNB) with the NTZ information.

[0123] Option 1: node-level signaling.

[0124] 1. An AF (UTM) sends (Block S 130) to the U AS NF / NEF 108 an Naf_Authentication_Notification request to provide new / updated information about NTZ for the UE / UAV (e.g., UE 22). The AF / UTM 110 includes Generic Public Subscription Identifier (GPSI), Civil Aviation Authority (CAA)-Level UAV ID, PDU Session Internet Protocol (IP) address if available, and the NTZ information in the re- authentication / authentication data update request.

[0125] It should be noted that the similar request can be used by the AF / UTM 110 to send an update about the NTZ information when, e.g., the AMF 100 / MME is preconfigured with the set of NTZ information or when the previously delivered information is not valid anymore.

[0126] 2. The UAS NF / NEF 108 translates (Block S132) the AF-provided NTZ information (e.g., geographical area in the form of coordinates (i.e., latitude and longitude), restricted frequency band(s), altitude / elevation) into 3GPP identifiers, e.g., a list of Tracking Area Identifiers (TAIs) or a list of cell IDs, RAT Frequency Selection Priority (RSFP) Index.

[0127] Options 3 A and 3B (collectively with Option 3C, Block SI 34). The UAS NF / NEF 108 discovers a PCF 102 handling AM Policy for the UE (Option 3 A) or a serving AMF 100 (Option 3B); for that the NEF 108 invokes the NRF 104 discovery service and uses UE’s 22 identity.

[0128] Option 3C. The UAS NF / NEF 108 uses Unified Data Management (UDM) 106 service (Nudm_UECM_Get operation, e.g., as specified in clause 5.2.3.2.4 of 3GPP TS 23.502) to get an NF ID of the AMF 100 serving the UE 22, i.e. with UE Context. In combination with that, the UAS NF may invoke another service operation to UDM 106 to retrieve UE’s 22 subscription data and check whether the UE 22 is compliant with NTZs requirements allowing the operator and the network to enforce NTZs.

[0129] If the UE’s 22 subscription does not have the NTZ indication, the UAS NF notifies the AF / UTM 110 by sending the response message and including the information about the results inside this message. It should be noted that it may be up to UTM to decide for which purpose this information can be used.

[0130] 4A. The UAS NF / NEF 108 sends (collectively with 4B and 4C, Block S136) to the discovered PCF 102 an Npcf_AMPolicyAuthorization_Create / Update request containing the translated NTZ information, e.g. a list of TAs / Cell IDs, and the original AF-provided NTZ information (prior the translation by the NEF 108).

[0131] 5A. After receiving the NTZ information, the PCF 102 takes (Block S140) policy decision and then may initiate the AM Policy Association Modification procedure for the UE / UAV, as described, e.g., in clause 4.16.2.2 of 3GPP TS 23.502 to provide the AMF 100 with the NTZ information.

[0132] The PCF 102 does not initiate the AM Policy Associations Modification and rejects (i.e., responds with the failure cause) the Npcf_AMPolicyAuthorization_Create / Update request in cases when the PCF 102 does not receive information about the UE’s 22 capability to respect NTZ during the AM Policy Association Establishment (see, e.g., Step 16 in clause 4.2.2.2.2 of 3GPP TS 23.502). The PCF 102 responds to the Npcf_AMPolicyAuthorization_Create / Update request (not shown in FIG. 7), and the UAS NF / NEF 108 responds to the AF (using Naf_Authentication_Notification response, not shown in FIG. 7) to inform the UTM that the UE / UAV (e.g., UE 22) does not have capability required.

[0133] 4B and 4C. If the UE’s 22 subscription data contains the indication that the UE

[0134] 22 is compliant with NTZ requirements, the UAS NF / NEF 108 sends an Nnef_Authentication_Notification request to the AMF / MME, containing the translated NTZ information, e.g. a list of TAs / Cell IDs, the original AF-provided NTZ information to the target AMF 100. If the UE 22 subscription does not indicate the NTZ compliance, the UAS NF / NEF 108 responds to the AF / UTM 110 to notify that the UE / UAV 22 does not have capability required.

[0135] 6A and 6B. If the UE 22 subscription check (i.e., compliance to NTZ requirements) has not been performed earlier in the procedure, the AMF 100 / MME checks (Block S140), based on the subscription data retrieved during the registration, whether the UE 22 is compliant with NTZ requirements.

[0136] 7. Based on the NTZ information, the AMF 100 determines (Block S142) the relevant RAN node IDs and then sends N2 messages containing the NTZ information and includes an indication to enforce (whenever required NTZ respect) to all applicable RAN nodes (e.g., network node 16 such as gNB / eNB). It should be noted that RAN can use the NTZ information to adjust information broadcasting, and prevent UEs 22 from moving from RRC_IDLE / INACTOVE states to RRC_CONNECTED state.

[0137] Option 2: QAM configuration.

[0138] 1. RAN node(s) (e.g., network nodes 16) are configured by OAM (Block

[0139] SI 44) with the existing NTZ information that can be requested by the AF / UTM 110 from network’s nodes 16 in the area they serve (e.g., based on RAN node location, Tracking Area(s) identified by a list of tracking area identities (TAI) or a list of cell identities).

[0140] 2. AMF 100 sends an N2 message with an indication that the RAN needs to enforce NRZ after the Registration Completion.

[0141] Option 3: AMF 100 preconfigure with NTZ information.

[0142] 0. AMF 100 is preconfigured (Block SI 46) with sets of NTZ information that can be requested by the AF / UTM 110.

[0143] 1. To request a specific NTZ requirements, the AF / UTM 110 may use (Block S148), e.g., an index (a number) to a specific set; Steps (some or all) of 3B / C, 4B / C, 6A, and 7 as described above with respect to Option 1 are executed.

[0144] 2. Delivery (Block SI 50) of the NTZ information together with the indication to enforce NTZ during NG interface Setup / Reconfiguration procedure, during Initial Context Setup / Modification procedure or PDU session resource management procedures.

[0145] The main procedural steps to provide UEs 22 with the NTZ information are shown in FIG. 8, which depicts a procedure for providing UEs 22 with the NTZ information.

[0146] Option 1: RRC protocol

[0147] 1. UE 22 performs (Block S152) registration procedure as described, e.g., in clause 4.2.2.2.2 of 3GPP TS 23.502.

[0148] 2. AMF 100 / MME retrieves (Block S154) the subscription data from the UDM 106 and checks whether the UE 22 is compliant with NTZ requirements. If so, the AMF 100 / MME sends N2 message with the indication to RAN that it shall enforce the NTZ whenever required.

[0149] 3. RAN (e.g., network node 16 such as gNB / eNB) sends (Block S156) the received NTZ information using RRC protocol.

[0150] Option 2: Registration Accept

[0151] 1. UE 22 to RAN: UEs 22 sends (Block S158) a Registration Request message and includes parameters as specified, e.g., in clause 4.2.2.2.2 of 3GPP TS 23.502. Additionally, if the UE 22 has capabilities to respect no-transmit zones, the UE 22 includes the indication about this capability to the network.

[0152] 2. RAN to AMF 100: Once RAN selects an AMF 100, the RAN sends (Block SI 60) an N2 message containing N2 parameters (e.g., as specified in Step 3 of clause 4.2.2.2.2 of 3GPP TS 23.502) and the received Registration Request message from the RAN (as described in Step 1). The AMF 100 stores information UE’s 22 support for NTZ consideration in the UE 22 Context.

[0153] 3. If AMF 100 sees in the registration request information about UEs 22 capability to respect NTZ, the AMF 100 checks (Block SI 62) whether UE 22 subscription data includes indication about UEs 22 compliance with NTZ requirements. If the UE 22 is compliant with NTZs, the AMF 100 may verify the UE’s 22 location before replying with a Registration Accept / Reject message.

[0154] 4. If the UE 22 is allowed to operate at its present location, the AMF 100 sends (Block SI 64) to the UE 22 a Registration Accept message and includes inside the message the previously received NTZ information.

[0155] If the UE 22 is not allowed to operate at its present location, the AMF 100 may either: (1) send a Registration Reject message with a cause value indicating that the UE 22 is not allowed to operate at the present UE 22 location, or alternatively, (2) send a Registration Accept message in which the AMF 100 includes a UE 22 Radio Capability ID and / or RSFP Index the UE 22 is allowed to operate.

[0156] 5. If the UE 22 receives (Block S166) a Registration Reject message with a cause value indicating the UE / UAV (e.g., UE 22) is not allowed to operate in the present location due to NTZ requirements, the UE 22 may attempt to perform an Emergency Registration.

[0157] Option 3: NTZ delivery to UE 22

[0158] 1. NTZ information is delivered (Block S168) to the PCF 102 using, e.g., steps S130-S136 as depicted in FIG. 7, or in case of AMF 100 pre-configuration using the Association Modification (AM) initiated by AMF 100 procedure (e.g., as specified in 3GPP TS 23.502 clause 4.16.2.1.2)

[0159] 2. NTZ information is delivered (Block S170) to the UE 22 using direct communication over PC5 interface.

[0160] The overall NTZ procedure for supporting UE compliance is as shown in FIG. 9, and it includes:

[0161] 1. NTZ information and the indication to enforce NTZ delivery (Block S172) to the relevant RAN nodes as described in FIG. 7. 2. NTZ information delivery (Block S174) to UEs 22 with the corresponding subscription, as described in FIG. 8.

[0162] 3. UE 22 location determination (Block S176). As an option, and depending on UTM requirements, the AMF 100 may use the UE 22 mobility event notifications to get information about UE’s 22 presence in Area(s) of Interest, as specified, e.g., in clause 5.3.4.4 of 3GPP TS 23.501.

[0163] 4. In case of UE’s 22 presence in the Aol: once the AMF 100 detects the UE’s 22 presence in the NTZ, the AMF 100 sends (Block S178) an N2 message with a new value of 'Index to RAT / Frequency Selection Priority' (RFSP Index) to RAN nodes. Based on the received RSFP Index, the NG-RAN nodes (e.g., network nodes 16) decide about redirecting UEs 22 to different frequency layers or RATs (as specified, e.g., in clause 5.3.4.3.1 of 3GPP TS 23.501)

[0164] Furthermore, when UE 22 transmits in NTZ but is not allowed, it may be necessary to report to the SMF and UPF so that the UPF can block the UE traffic.

[0165] 5. If there is any change in the provisioned NTZ information, the RAN nodes, e.g., network node 16, and UEs 22 may need to be re-provisioned with the newest NTZ information (Block SI 80).

[0166] 6. For UEs / UAV (e.g. , UE 22) in CM_CONNECT with R RC_IN ACTI V E state or in CM_IDLE, the AMF 100 may initiate (Block SI 82), based on the local policy, the Network Triggered Service Request procedure as described, e.g., in clause 4.2.3.3 of 3GPP TS 23.502 before executing Step 3-5. If the UE 22 is not updated while it was in IDLE, the AMF 100 / MME updates the UE 22 next time it becomes available again (e.g., RRC_CONNECTED).

[0167] Impacts on services, entities and interfaces

[0168] Impact depends on which option / alternatives will be selected for delivering NTZ information to UEs 22 and RAN nodes (e.g., network nodes 16) and for updating them about any change from the AF / UTM 110. Overall, the impacts could be the following. AF 110:

[0169] Invoking a Naf_Authentication_Notification or a new service to request NTZ compliance from the network

[0170] Receiving notifications when UEs 22 enter or disobey NTZ requirements

[0171] UAS NF / NEF 108:

[0172] Discovering a PCF 102 handling AM policy,

[0173] Discovering AMF 100 serving the UE 22 Retrieving information about UE’s 22 subscription and checking whether the UE 22 can comply with NTZ

[0174] Translating the NTZ information to 3GPP identifiers such as TA, NG-RAN node identifiers, cell IDs.

[0175] PCF:

[0176] Invoking AM Policy Association Modification due to NTZ

[0177] AMF:

[0178] Determining UE’s 22 location / presence in the area of interest

[0179] Checking UE’s 22 subscription for NTZ compliance

[0180] Informing PCF 102 about UE’s 22 capability to respect NTZ

[0181] Informing RAN nodes (e.g., network nodes 16) about enforcing NTZ requirements Informing PCF 102 about UE’s 22 capability to respect NTZ

[0182] Sending notifications when UE 22 enters the NTZ

[0183] RAN (e.g., network node 16): delivering NTZ information to the relevant UEs 22

[0184] Enforcing NTZ compliance

[0185] UE / UAY (e.g., UE 22): respecting NTZ requirements announces its capability to comply with NTZ requirements

[0186] UPF: blocking UL data traffic for UEs 22 in NTZ

[0187] Example Embodiments:

[0188] Example Al. A network node 16 configured to communicate with a UE 22, the network node 16 configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: receive information corresponding to a no-transmit zone, NTZ; determine a location of the UE 22 in relation to the NTZ; and transmit NTZ information to the UE 22 to cause the UE’s compliance with the NTZ when the location of the UE 22 is in the NTZ.

[0189] Example A2. The network node 16 of Example Al, wherein the network node 16 and / or the radio interface and / or the processing circuitry are further configured to determine when the UE 22 is in non-compliance with the NTZ.

[0190] Example A3. The network node 16 of any one of Examples Al and A2, wherein the network node 16 and / or the radio interface and / or the processing circuitry are further configured to transmit an update to the NTZ information based on a change occurring to the NTZ.

[0191] Example A4. The network node 16 of any one of Examples Al -A3, wherein the network node 16 and / or the radio interface and / or the processing circuitry are further configured to cause the UE 22 to initiate a Network Triggered Service Request procedure.

[0192] Example Bl. A method implemented in a network node 16, the method comprising: receiving information corresponding to a no-transmit zone, NTZ; determining a location of a user equipment, UE, in relation to the NTZ; and transmitting NTZ information to the UE 22 to cause the UE’s compliance with the NTZ when the location of the UE 22 is in the NTZ.

[0193] Example B2. The method of Example Bl, further comprising determining when the UE 22 is in non-compliance with the NTZ.

[0194] Example B3. The method of any one of Examples Bl and B2, further comprising transmitting an update to the NTZ information based on a change occurring to the NTZ.

[0195] Example B4. The method of any one of Examples B1-B3, further comprising causing the UE 22 to initiate a Network Triggered Service Request procedure.

[0196] Example Cl. A user equipment (UE) configured to communicate with a network node 16, the UE 22 configured to, and / or comprising a radio interface and / or processing circuitry configured to: receive No-Transmit Zone, NTZ, information sufficient to cause the UE’s compliance with an NTZ when a location of the UE 22 is in the NTZ; communicate with the network node 16 based on the NTZ information.

[0197] Example C2. The UE 22 of Example Cl, wherein the UE 22 and / or the radio interface and / or the processing circuitry are further configured to receive an indication that the UE 22 is in non-compliance with the NTZ.

[0198] Example C3. The UE 22 of any one of Examples Cl and C2, wherein the UE 22 and / or the radio interface and / or the processing circuitry are further configured to receive an update to the NTZ information based on a change occurring to the NTZ.

[0199] Example C4. The UE 22 of any one of Examples C1-C3, wherein the UE 22 and / or the radio interface and / or the processing circuitry are further configured to initiate a Network Triggered Service Request procedure.

[0200] Example DI. A method implemented in a user equipment (UE), the method comprising: receiving No-Transmit Zone, NTZ, information sufficient to cause the UE’s compliance with an NTZ when a location of the UE 22 is in the NTZ; communicating with the network node 16 based on the NTZ information. Example D2. The method of Example DI, further comprising receiving an indication that the UE 22 is in non-compliance with the NTZ.

[0201] Example D3. The method of any one of Examples DI and D2, further comprising receiving an update to the NTZ information based on a change occurring to the NTZ.

[0202] Example D4. The method of any one of Examples D1-D3, further comprising initiating a Network Triggered Service Request procedure.

[0203] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0204] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0205] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0206] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0207] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0208] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0209] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0210] Abbreviations that may be used in the preceding description include:

[0211] Abbreviation Explanation

[0212] AF Application Function

[0213] AMF Access and Mobility Function

[0214] CN Core Network

[0215] NEF Network Exposure Function

[0216] NF Network Function

[0217] NG- RAN Next generation radio access network

[0218] NRF Network Repository Function

[0219] NTZ No-Transmit Zone

[0220] OAM Operation and Maintenance

[0221] PCF Policy Control Function

[0222] UAS NF Uncrewed Aerial System NF

[0223] UAV Uncrewed Aerial Vehicle

[0224] UDM Unified Data Management

[0225] UE User Equipment

[0226] UTM Uncrewed Aerial System Traffic Management

[0227] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method implemented in a user equipment, UE, (22), the method comprising: receiving (S127) No-Transmit Zone, NTZ, information sufficient to cause the UE’s (22) compliance with an NTZ when a location of the UE (22) is in the NTZ; and operating (S128) in accordance with the NTZ information.

2. The method of Claim 1, wherein the NTZ information is one of: received via Radio Resource Control signaling; received in response to requesting registration; or received from a Policy Control Function, PCF, over a PC5 interface.

3. The method of any one of Claims 1-2, wherein the NTZ information is received from a network node (16), the NTZ information being one of: propagated to the network node (16) via node-level signalling; configured at the network node (16) by Operation and Maintenance; or configured at the network node (16) by an Access and Mobility Function, AMF.

4. The method of Claim 3, wherein the NTZ information is propagated to the network node (16) via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE (22).

5. The method of any one of Claims 1-4, further comprising receiving an indication that the UE (22) is in non-compliance with the NTZ.

6. The method of any one of Claims 1-5, further comprising receiving an update to the NTZ information based on a change occurring to the NTZ.

7. The method of Claim 6, wherein receiving the update to the NTZ information comprises the UE (22) being woken from an idle state as part of a Network Triggered Service Request procedure.

8. A user equipment, UE, (22), comprising processing circuitry configured to:receive No-Transmit Zone, NTZ, information sufficient to cause the UE’s (22) compliance with an NTZ when a location of the UE (22) is in the NTZ; and operate in accordance with the NTZ information.

9. The UE of Claim 8, wherein the NTZ information is one of: received via Radio Resource Control signaling; received in response to requesting registration; or received from a Policy Control Function, PCF, over a PC5 interface.

10. The UE of any one of Claims 8-9, wherein the NTZ information is received from a network node (16), the NTZ information being one of: propagated to the network node (16) via node-level signalling; configured at the network node (16) by Operation and Maintenance; or configured at the network node (16) by an Access and Mobility Function, AMF.

11. The UE of Claim 10, wherein the NTZ information is propagated to the network node (16) via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE (22).

12. The UE of any one of Claims 8-11, wherein the processing circuitry is further configured to receive an indication that the UE (22) is in non-compliance with the NTZ.

13. The UE of any one of Claims 8-12, wherein the processing circuitry is further configured to receive an update to the NTZ information based on a change occurring to the NTZ.

14. The UE of Claim 13, wherein receiving the update to the NTZ information comprises the UE (22) being woken from an idle state as part of a Network Triggered Service Request procedure.

15. A method implemented in a network node (16) configured to communicate with a user equipment, UE, (22), the method comprising:configuring (SI 25) the UE (22) with No-Transmit Zone, NTZ, information sufficient to cause the UE’s (22) compliance with an NTZ when a location of the UE (22) is in the NTZ; and operating (S126) in accordance with the NTZ information.

16. The method of Claim 15, wherein one of: configuring the UE (22) with the NTZ information comprises transmitting the NTZ information to the UE (22) via Radio Resource Control signaling; the NTZ information is determined by a Policy Control Function, PCF; or configuring the UE (22) with the NTZ information comprises causing the NTZ information to be transmitted to the UE (22) in response to the UE (22) requesting registration.

17. The method of any one of Claims 15-16, wherein one of: the method includes receiving the NTZ information via node-level signalling; the NTZ information is configured at the network node (16) by Operation and Maintenance; or the NTZ information configured at the network node (16) by an Access and Mobility Function, AMF.

18. The method of Claim 17, wherein the NTZ information is received by the network node (16) via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE (22).

19. The method of any one of Claims 15-18, further comprising transmitting an indication that the UE (22) is in non-compliance with the NTZ.

20. The method of any one of Claims 15-19, further comprising transmitting, to the UE (22), an update to the NTZ information based on a change occurring to the NTZ.

21. A network node (16) comprising processing circuitry configured to: configure a UE (22) with No-Transmit Zone, NTZ, information sufficient to cause the UE’s (22) compliance with an NTZ when a location of the UE (22) is in the NTZ; andoperate in accordance with the NTZ information.

22. The network node (16) of Claim 21, wherein one of: configuring the UE (22) with the NTZ information comprises transmitting the NTZ information to the UE (22) via Radio Resource Control signaling; the NTZ information is determined by a Policy Control Function, PCF; or configuring the UE (22) with the NTZ information comprises causing the NTZ information to be transmitted to the UE (22) in response to the UE (22) requesting registration.

23. The network node (16) of any one of Claims 21-22, wherein one of: the network node (16) is configured to receive the NTZ information via node-level signalling; the NTZ information is configured at the network node (16) by Operation and Maintenance; or the NTZ information configured at the network node (16) by an Access and Mobility Function, AMF.

24. The network node (16) of Claim 23, wherein the NTZ information is received by the network node (16) via node-level signalling, and the NTZ information is based on a policy decision by a Policy Control Function, PCF, that takes into account a capability of the UE (22).

25. The network node (16) of any one of Claims 21-24, wherein the processing circuitry is further configured to transmit an indication that the UE (22) is in non- compliance with the NTZ.

26. The network node (16) of any one of Claims 21-25, wherein the processing circuitry is further configured to transmit, to the UE (22), an update to the NTZ information based on a change occurring to the NTZ.

Images