WO2024199754A1

WO2024199754A1 - Non-transmit zones for uncrewed aerial vehicles

Info

Publication number: WO2024199754A1
Application number: PCT/EP2024/051563
Authority: WO
Inventors: Dimitrios Karampatsis; Genadi Velev
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2024-01-11
Filing date: 2024-01-23
Publication date: 2024-10-03
Anticipated expiration: 2026-07-11

Abstract

Various aspects of the present disclosure relate to a network entity for wireless communication, the network entity comprising instructions executable by at least one processor to cause the network entity to: obtain an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN); and transmit, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV.

Description

NON-TR ANSMIT ZONES FOR UNCREWED AERIAL VEHICLES

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to wireless communications relating to operation of uncrewed aerial vehicles (UAVs).

BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

SUMMARY

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

[0004] Some implementations of the method and apparatuses described herein may further include a network entity for wireless communication, the network entity comprising instructions executable by at least one processor to cause the network entity to obtain an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN), and to transmit, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV. The non-communication zones may for example be non-transmit zones.

[0005] The network entity may comprise one or more of an uncrewed aerial system (UAS) traffic management (UTM), UAS Service Supplier (USS), or an application function, (AF).

[0006] The second entity may comprise one or more of a UAS network function (NF) or a UAS network exposure function (NEF).

[0007] The set of non-communication zones may correspond to one or more geographical areas in which one or more radio frequency bands are prohibited for the UAV.

[0008] The modified policy may prohibit the one or more frequency bands for the UAV in the one or more geographical areas.

[0009] The policy may comprise a mapping of one or more radio access technology (RAT) frequency selection priority (RFSP) indexes to the one or more geographical areas to define the set of non-communication zones.

[0010] The instructions may be further executable by the at least one processor to cause the network entity to determine the set of non-communication zones based on at least in part on one or more of an identifier of the PLMN or a flight path of the UAV.

[0011] The indication may indicate that the UAV is authorized to access the PLMN to perform at least one UAV operation. [0012] The instructions may be further executable by the at least one processor to cause the network entity to determine that the UE is UAS service supplier (USS) authenticated and authorized based at least in part on the indication.

[0013] The instructions may be further executable by the at least one processor to cause the network entity to determine that the UE is authorized for communication in the PLMN, wherein the communication comprises command and control (C2) communication.

[0014] The indication may indicate that the UAV has entered at least one noncommunication zone of the set of non-communication zones.

[0015] In some implementations of the method and apparatuses described herein, a network entity may be provided for wireless communication. The network entity may comprise instructions executable by at least one processor to cause the network entity to receive, from a second network entity, a message comprising a set of modified policies associated with an uncrewed aerial vehicle (UAV), determine a set of radio access technology, RAT, Frequency Selection Priority, RFSP, policies associated with a set of non-communication zones for a public land mobile network (PLMN), and output, to a third network entity, the set of modified policies including the set of RFSP policies for the set of non-communi cation zones for the PLMN.

[0016] The network entity may comprise a policy control function (PCF). Alternatively or additionally, the second network entity may comprise a unified data management (UDM).

[0017] The network entity may comprise a policy control function (PCF). Alternatively or additionally, the third network entity may comprise an access and mobility function (AMF).

[0018] The instructions may be further executable by the at least one processor to cause the network entity to output the set of modified policies based at least in part on an indication that the UAV established a session for at least one UAV operation.

[0019] The third network entity may comprise a session management function (SMF). [0020] The instructions may be further executable by the at least one processor to cause the network entity to output the set of modified policies in response to an indication from the third network function that the UAV has entered at least one non-communication zone of the set of non-communication zones or is estimated to enter the at least one noncommunication zone of the set of non-communication zones, wherein the third network entity comprises an access and mobility function (AMF) or a location management function (LMF)

[0021] In some implementations of the methods and apparatuses described herein, a method is performed by a first network entity for wireless communication, the method comprising obtaining an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN), and transmitting, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV.

[0022] In some implementations of the methods and apparatuses described herein, a method is performed by a network entity for wireless communication, the method comprising receiving, from a second network entity, a message comprising a set of modified policies associated with an uncrewed aerial vehicle (UAV), determining a set of radio access technology, RAT, Frequency Selection Priority, RFSP, policies associated with a set of non-communication zones for a public land mobile network (PLMN), and outputting, to a third network entity, the set of modified policies including the set of RFSP policies for the set of non-communi cation zones for the PLMN.

BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0024] Figure 2 illustrates a network in accordance with aspects of the present disclosure. [0025] Figure 3 illustrates a communication flow in accordance with aspects of the present disclosure.

[0026] Figure 4 illustrates a communication flow in accordance with aspects of the present disclosure.

[0027] Figure 5 illustrates an example of a network entity (NE) in accordance with aspects of the present disclosure.

[0028] Figure 6 illustrate a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.

[0029] Figure 7 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0030] Some wireless communication systems may support operation of unmanned aerial systems that include an unmanned/uncrewed aerial vehicle (UAV) controller and a UAV, which may perform UAV operations, such as C2 operations. However, these wireless communication systems may be unable to comply with non-communication zones (also referred to as “non-transmit zones”), which may be enforced by a third-party entity. For example, non-communi cation zones may prohibit transmissions (e.g., on one or more frequency bands) within one or more geographical areas, for example, to mitigate or reduce interference to other UE, such as radars.

[0031] Various aspects of the present disclosure relate to enabling a UE, such as a UAV in a wireless communication system (e.g., a PLMN) to manage operation (e.g., refrain from performing transmission(s)) when the UAV is within at least one non-communication zone associated with at least one geographical area of the wireless communication system. The UAV may be configured with (e.g., indicated) the at least one non-communication zone associated with at least one geographical area of the wireless communication system as described herein.

[0032] Aspects of the present disclosure are described in the context of a wireless communications system. [0033] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0034] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network entity, a network function, a network element, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0035] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. One or more of these UEs may for example be UAVs as discussed elsewhere herein. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0036] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0037] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over 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, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0038] An NE 102 may support communications with the CN 106, or with another NE

102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs). [0039] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0040] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0041] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies. [0042] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., /r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0043] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0044] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /r=0, jU=l , /r=2, jU=3, /r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0045] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations 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, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0046] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0047] In the wireless communication system 100, a UE 104 may be, for example, a UAV configured to manage operation (e.g., refrain from performing transmission(s)) when the UE 104 is within at least one non-communi cation zone associated with at least one geographical area of the wireless communication system 100. The UE 104 may be configured with (e.g., indicated) the at least one non-communi cation zone associated with at least one geographical area of the wireless communication system 100 as described herein with reference to Figures 2 through 4.

[0048] Figure 2 illustrates a network for supporting UAS in accordance with aspects of the present disclosure. The network may implement or be implemented by aspects of the wireless communication system 100 as described herein with reference to Figure 1. For example, the network may include a UAV 205, which may be an example of a UE 104 as described herein with reference to Figure 1. The network may include an NE 210 associated with a first radio access technology (e.g., 5GNR) and a NE 215 associated with a second radio access technology (e.g., 4GLTE), which may be an example of a NE 102 as described herein with reference to Figure 1. It should be noted that the network may support radio access technologies beyond 4G LTE and 5G NR.

[0049] The UAV 205 may communicate (e.g., one or more of transmit or receive signaling, including control information or data) with one or more of the NE 210 or the NE 215 via one or more communication links (e.g., Uu interface). The NE 210 may communicate (e.g., one or more of transmit or receive signaling) with a CN 220 associated with the first radio access technology via a backhaul interface (e.g., in accordance with an SI, N2, N3, or other interface protocol) and may be an example of a CN 106 as described herein with reference to Figure 1. For example, the CN 220 may be a 5G core network (5GC). The NE 225 may communicate (e.g., one or more of transmit or receive signaling) with a CN 220 associated with the second radio access technology via a backhaul interface (e.g., in accordance with an SI, N2, N3, or other interface protocol) and may be an example of a CN 106 as described herein with reference to Figure 1. For example, the CN 225 may be an evolved packet core network (EPC).

[0050] One or more of the CN 220 or the CN 225 may communicate (e.g., one or more of transmit or receive signaling) with a data network 230. Additionally, or alternatively, the CN 220 may communicate (e.g., one or more of transmit or receive signaling) with a UAS network function (NF) or a UAS network exposure function (NEF) (herein referred to as UAS NF/NEF 235). The UAS NF/NEF 235 may communicate (e.g., one or more of transmit or receive signaling) with a UAS service supplier (USS) 240, which may be part of the data network 230. Additionally, the network may include a third party authorized entity (TPAE) 245, which may communicate (e.g., one or more of transmit or receive signaling) with the data network 230.

[0051] The UAS NF/NEF 235 (e.g., one or more of the UAS NF or the UAS NEF) may be configured to indicate (e.g., expose) to one or more of a UAS traffic management UTM or the USS 240 location information of the UAV 205. The location information may be based at least in part on location services (LCS) or information obtained from an AMF, for example, associated with one or more of the CN 220 or the CN 225. The UAS NF/NEF 235 (e.g., one or more of the UAS NF or the UAS NEF) may interfaces with one or more of a UTM or the USS 240 for performing an authentication and authorization of the UAV 205, for example, authorizing the UAV 205 to perform one or more UAV operations via the network (e.g. a 3GPP network).

[0052] The UAV 205, including a UAV controller (UAV-C) of the UAV 205, may be part of a UAS. The UAS may establish a user plane connectivity between the UAV 205 and a UTM/USS. Identification and tracking information may be exchanged (e.g., transmitted, received) over the user plane connectivity. The UAS may also establish a user plane connectivity between the UAV-C of the UAV 205 and the UAV 205 for C2. To support one or more UAV operations, the network may have a requirement for the UAS to be registered (or register) to a USS provider. The registration to the USS provider and/or establishment that the requirement has been met may, for example, be established with a non-3GPP procedure. In some implementations, the requirement may correspond to the UAS having a valid flight authorization provided by the USS provider. The requirement for the UAS to have the valid flight authorization may, for example, be established with a non-3GPP procedure.

[0053] In the example of Figure 2, the network may perform various operations, processes, tasks, or procedures in order to authorize the UAV 205 to access a network, for example, in conformance with 3 GPP TS 23.256. For example, the network may perform a USS UAV authorization/authenti cation (UUAA) procedure to verify that a UAS has a valid registration to a USS provider. The network may perform a C2 authorization procedure to authorize the UAV 205 to establish user plane connectivity via a 3GPP system for UAV operation. [0054] In some cases, an application function (AF) may trigger a change to one or more access and mobility (AM) management policies. Such an AF may be able to impact a change to the one or more AM policies associated with a service coverage and one or more throughput requirements. However, the AF may lack the capability or functionality to indicate one or more frequency bands, associated with prohibiting communications on the one or more frequency bands, in the one or more AM policies. In the examples of Figure 2, it may be desirable to enforce restrictions to one or more UAV operations of the UAV 205, for example, such as one or more non-communication zones (also referred to as nontransmit zones (NTZs)). An NTZ may be a geographical area, in which the UAV 205 may be prohibited (e.g., not allowed) to transmit on one or more frequency bands, for example, in order to reduce interference on similar or adjacent frequency bands. Aspects of the present disclosure allow the network to be configured with one or more NTZs, for example, by a USS/UTM operator. Aspects of the present disclosure allow a USS/UTM 240 to indicate one or more geographical areas (e.g., coverage areas of the network) corresponding to one or more NTZs with the requirements (e.g., one or more frequency bands on which the UAV 205 is not permitted to transmit).

[0055] Figure 3 shows a process flow 300 in accordance with aspects of the present disclosure. The process flow 300 may implement aspects of the wireless communications system 100 as described with reference to Figure 1. The process flow 300 may involve one or more of a UAV 205, a RAN 210, an AMF 305, a session management function (SMF) 310, an access and mobility policy control function (AM-PCF) 315, a session management policy control function (SM-PCF) 320, a unified data management/user data repository (UDM/UDR) 325, a NEF/UASNF 235, and a USS/UTM 240. In the following description of the process flow 300, the operations between one or more of the UAV 205, the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240 may be transmitted or received in a different order than the example order shown, or the operations performed by one or more of the UAV 205, the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240 may be performed in different order or at different times. Some operations may also be omitted from the process flow 300, and other operations may be added to the process flow 300. [0056] In the example of Figure 3, the UTM/USS 240 may trigger a change of one or more AM policies. The USS/UTM 240 may trigger a change of one or more AM policies based at least in part on the UTM/USS 240 determining that the UAV 205 is UUAA authorized. Additionally, or alternatively, the USS/UTM 240 may trigger the change of the one or more AM policies based at least in part on the UTM/USS 240 determining that the UAV 205 requested C2 communication. Additionally, or alternatively, the USS/UTM 240 may trigger the change of the one or more AM policies based at least in part on the UTM/USS 240 determining that the UAV 205 is located within with an NTZ.

[0057] At 1, the UAV 205 may perform a registration procedure, for example, with a network, which may involve one or more of the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, or the NEF/UASNF 235. In some implementations, the UAV 205 may transmit an indication that indicates a CAA-Level UAV identifier associated with the UAV 205 during the registration procedure. A CAA (Civil Aviation Administration)-Level UAV identifier may be an identifier that uniquely identifies a UAV within the scope of a USS.

[0058] At 2, one or more of the AMF 305 (UUAA-MM) or the SMF 310 (UUAA-SM) may perform a UUAA procedure, which may involve one or more of the UAV 205, the RAN 210, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240.

[0059] At 3, optionally, the UTM/USS 240 may determine one or more NTZ zones. In some implementations, the UTM/USS 240 may determine one or more NTZ zones in response to the UTM/USS 240 determining that the UAV 205 is UUAA authorized. For example, the UTM/USS 240 may determine that the UAV 205 is UUAA authorized based at least in part on a PLMN identifier.

[0060] At 3a, optionally, the UTM/USS 240 may subscribe to location changes associated with the UAV 205, for example by transmitting a subscription message to the NEF/UASNF 235. Put another way, the UTM/USS 240 may subscribe to be indicated of a change to a location of the UAV 205. In some implementations, in response to the UTM/USS 240 determining that the UAV 205 has entered (or is predicted to enter, for example, based at least in part on a flight path of the UAV 205) an NTZ, the UTM/USS 240 may trigger an AM policy influence process to update an AM policy.

[0061] At 4, the UAV 205 may determine a trigger to establish a communication session for C2. Put another way, the UAV 205 may be triggered to establish the communication session for C2, for example in respond to a command to establish C2. [0062] At 5 through 10, the UAV 205 performs an authorization for C2, including flight path information, via a PDU session establishment procedure (or a PDU session modification procedure). The UTM/USS 240 configures pairing policies for the UAV/UAV-C.

[0063] Specifically, at 5, the UAV 205 transmits a PDU session establishment/modification message, with a C2 aviation payload, to the AMF 305. At 6, the AMF 305 transmits a Nsmf_PDUSession_updatedSMcontext message with the C2 aviation payload to the SMF 310. At 7, the SMF 310 transmits a

Nnef Authentication AuthenticateAuthorize message with the C2 aviation payload to the NEF/UASNF 235. At 8, the NEF/UASNF 235 transmits a

Naf Authentication AuthenticateAuthorize message with the C2 aviation payload to the UTM/USS 240. At 9, the UAV re-authorises to the network. At 10, an AF session is established with quality of service (QoS) request/update.

[0064] At 11, optionally, once C2 is authorised the UTM/USS 240 determines one or more NTZ zones for the UAV 205. The determination may be based on a PLMN ID of the operator where the UAV 205 is registered. In an alternative example, the UTM/USS may determine the NTZ zones based on an authorised flight path of the UAV 205. The UTM/USS 240 sends the NTZ zone info by invoking 12 or 16 (as discussed below).

[0065] At 1 la, optionally, the UTM/USS 240 may request information regarding location changes for the UAV 205. When the UTM/USS 240 determines that the UAV 205 has entered (or is about to enter) an NTZ zone the UTM/USS 240 may trigger AM policy influence (as in 12 or 16 discussed below).

[0066] 12-18 will now be discussed. In examples, either 12-15, or 16-18 are performed.

12-15 relate to an indirect method and 16-18 relate to a direct method.

[0067] At 12, the UTM/USS 240 may invoke an Nnef_AMInfluence_Create service operation that includes a USS Identify/ AF identifier, GPSI, CAA-Level UAV ID and NTZ zone info. The NTZ zone info may include one or more permited and/or restricted frequency bands for one or more geographical areas.

[0068] In an alternative example, the UTM/USS 240 may invoke step 12 for a group of UAVs (including the UAV 205) that are UUAA or C2 authorized. In this example the UTM/USS 240 additionally includes a group identifier in the request in 12.

[0069] At 13, the UAS NF/NEF 235 may authorise the request.

[0070] At 14, the UAS NF/NEF 235 may update the UDM 325 with non-transmit zones for the UAV 205 or group of UAVs.

[0071] At 15, the UDM 325 may notify the AM-PCF 315 that it has subscribed to notification of AM policy changes.

[0072] At 16, the UTM/USS 240 may invoke an Nnef_AMPolicyAuthorisation_Request service operation that includes a USS Identify/ AF identifier, GPSI, CAA-Level UAV ID and NTZ zone info. The NTZ zone info may include one or more permited and/or restricted frequency bands for one or more geographical areas.

[0073] At 17, the UAS NF/NEF 235 may find the particular AM-PCF 315 which is serving the UAV 205.

[0074] At 18, the UAS NF/NEF 235 may forward the request to the AM-PCF 315.

[0075] At 19, the AM-PCF 315 may subscribe to the SM-PCF 320 (e.g. by way of a subscription request message) to be notified when a PDU session for UAV operations (e.g. C2 operations for the UAV 205) is established.

[0076] At 20, the AM-PCF 315 may determine a radio access technology (RAT) Frequency Selection Priority (RFSP) policy for the UAV 205 indicating to the UAV 205 to use frequency bands other than restricted bands in NTZ zones. The AM-PCF 315 may determine such RFSP policies based on the SM-PCF 320 indicating that a UAV 205 has established a PDU session for UAV operations and the AM-PCF 315 has NTZ zone info from the UDM. Alternatively or additionally, the AM-PCF 315 may determine such RFSP policies based on the AM-PCF 315 receiving updated NTZ zone info from the UDM 325 and based on the UAV 205 having entered or being about to enter an NTZ zone.

[0077] At 21 , the AM-PCF 315 may update the AM policy towards the RAN 210 for example as described in 23.502 clause 4.16.2. [0078] Figure 4 shows a process flow 400 in accordance to aspects of the present disclosure. The process flow 400 may implement aspects of the wireless communications system 100 as described with reference to Figure 1. The process flow 400 may involve one or more of a UAV 205, RAN 210, NEF/UASNF 235 and USS/UTM 240, AMF 305, SMF 310, AM-PCF 315, SM-PCF 320, UDM/UDR 325, as discussed above.

[0079] In the following description of the process flow 400, the operations between one or more of the UAV 205, the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240 may be transmitted or received in a different order than the example order shown, or the operations performed by one or more of the UAV 205, the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240 may be performed in different order or at different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0080] In the example of Figure 4, the UTM/USS 240 may provide flight directions. In this scenario it may be assumed that the 3 GPP core network is aware of the one or more NTZ zones. In this example, the UAS-NF may determines any NTZ zones in the flight path of the UAV.

[0081] At 1 , the UAV 205 may perform a registration procedure, for example, with a network, which may involve one or more of the RAN 210, the AMF 305, the SMF 310, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, or the NEF/UASNF 235. In some implementations, the UAV 205 may transmit an indication that indicates a CAA-Level UAV identifier associated with the UAV 205 during the registration procedure.

[0082] At 2, one or more of the AMF 305 (UUAA-MM) or the SMF 310 (UUAA-SM) may perform a UUAA procedure, which may involve one or more of the UAV 205, the RAN 210, the AM-PCF 315, the SM-PCF 320, the UDM/UDR 325, the NEF/UASNF 235, or the USS/UTM 240.

[0083] At 3, the UAV 205 is triggered to establish a communication session for C2. Put another way, the UAV 205 may be triggered to establish the communication session for C2, for example in respond to a command to establish C2. [0084] At 4 through 8, the UAV 205 performs an authorisation for C2 (which may include flight path information) via a PDU session establishment procedure (or a PDU session modification procedure). The UTM/USS 240 configures pairing policies for the UAV/UAV-C.

[0085] Specifically, at 4, the UAV 205 transmits a PDU session establishment/modification message, with a C2 aviation payload, to the AMF 305. At 5, the AMF 305 transmits a Nsmf_PDUSession_updatedSMcontext message with the C2 aviation payload to the SMF 310. At 6, the SMF 310 transmits a

Nnef Authentication AuthenticateAuthorize message with the C2 aviation payload to the NEF/UASNF 235. At 7, the NEF/UASNF 235 transmits a

Naf Authentication AuthenticateAuthorize message with the C2 aviation payload to the UTM/USS 240. At 8, the UAV re-authorises to the network.

[0086] At 9, the UTM/USS 240 may have information indicating aspects of the flight path of the UAV 205 and may include them in an AF session QoS request to be transmitted to the NEF/UASNF 235.

[0087] At 10, the UTM/USS 240 invokes an Nnef_AFsessionwithQoS create service operation with the NEF/UASNF 235, which may include the flight path info information.

[0088] At 11, the AF session with QoS procedure continues for example as per Figure 4.16.6.6-1 of23.502.

[0089] At 12, the UAS NF/NEF 235 may determine based on the flight path that the UAV 205 is in an NTZ zone or the flight path is via one or more NTZ zones. The UAS NF/NEF 235 may be aware of the NTZ zones based on configuration from an operations, administration and maintenance (0AM) function. Alternatively or additionally, the UAS NF/NEF 235 may receive a description of the NTZ zones from the UDM 325, in response to a request thereto.

[0090] The UAS NF/NEF 235 may then invoke either 13 to 14 or 15 to 16 as discussed below. 13-14 relate to an indirect method, and 15-16 relate to a direct method.

[0091] At 13, the UAS NF/NEF 235 may update the UDM 325 with a description of NTZs for the UAV 205, or a group of UEs including the UAV 205. [0092] At 14, the UDM 325 may notify the AM-PCF 315 that it has subscribed to notification of AM policy changes.

[0093] At 15, the UAS NF/NEF 235 may find the identity of the specific AM-PCF 315 serving the UAV 205.

[0094] At 16, a the UAS NF/NEF 235 may transmit a Npcf_AMPolicyAuthorisation_Request request to the AM-PCF 315; the request may include at least one of a USS and/or AF identifier, GPSI, CAA-Level UAA ID and NTZ zone information. The NTZ zone information may include one or more permitted and/or restricted frequency bands for one or more geographical areas.

[0095] At 17, the AM-PCF 315 may subscribe to the SM-PCF 320 to be notified when a PDU session for UAV operations (e.g. C2 operations) is established.

[0096] At 18, the AM-PCF 315 may determine one or more RFSP policies for the UAV 205 indicating to the UAV 205 to use frequency bands other than restricted bands in NTZ zones. The AM-PCF 315 may determine RFSP policies based at least in part on the SM- PCF 320 indicating that the UAV 205 has established a PDU session for UAV operations and the AM-PCF 315 has NTZ zone info from the UDM 325. Alternatively or additionally, the AM-PCF 315 may determine RFSP policies based at least in part on the AM-PCF 315 having received updated NTZ zone info from the UDM 325 and the UAV 205 having entered or being about to enter an NTZ zone.

[0097] At 19, the AM-PCF 315 may update the AM policy towards the RAN 210 for example as described in 23.502 clause 4.16.2.

[0098] In summary, the present disclosure provides for methods and apparatuses for configuring frequency- and geographically- specific non-transmit zones for a UAV operating as a UE in a mobile communications network.

[0099] Figure 5 illustrates an example of a network equipment (also termed “network entity) (NE) 500 in accordance with aspects of the present disclosure. The NE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0100] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0101] The processor 502 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the NE 500 to perform various functions of the present disclosure.

[0102] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the NE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0103] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the NE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the NE 500 in accordance with examples as disclosed herein. The NE 500 may be configured to support a means for performing the functions described in the present disclosure, in particular with reference to Figures 3 and 4. For example, the network equipment 500 may implement one or more network functions, such as a UTM/USS/AF 240, UAS NF/NEF 235, PCF 315, UDM 325 and/or AMF 305.

[0104] The controller 506 may manage input and output signals for the NE 500. The controller 506 may also manage peripherals not integrated into the NE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0105] In some implementations, the NE 500 may include at least one transceiver 508. In some other implementations, the NE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

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

[0107] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 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 like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0108] Figure 6 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein, for example a NE comprising a first network function such as a UTM/USS/AF 240. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0109] At 602, the method may include obtaining an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN).

[0110] At 604, the method may include transmitting, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV.

[0111] Figure 7 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. For example, the method may be implemented by a NE comprising a PCF 315. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0112] At 702, the method may include receiving, from a second network entity, a message comprising a set of modified policies associated with an uncrewed aerial vehicle (UAV).

[0113] At 704, the method may include determining a set of radio access technology, RAT, Frequency Selection Priority, RFSP, policies associated with a set of noncommunication zones for a public land mobile network (PLMN).

[0114] At 706, the method may include outputting, to a third network entity, the set of modified policies including the set of RFSP policies for the set of non-communication zones for the PLMN. [0115] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

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

Claims

CLAIMS What is claimed is:

1. A network entity for wireless communication, the network entity comprising instructions executable by at least one processor to cause the network entity to: obtain an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN); and transmit, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV.

2. The network entity of claim 1, wherein the network entity comprises one or more of an uncrewed aerial system (UAS) traffic management (UTM), UAS Service Supplier (USS), or an application function, (AF).

3. The network entity of claims 1 or 2, wherein the second entity comprises one or more of a UAS network function (NF) or a UAS network exposure function (NEF).

4. The network entity of any preceding claim, wherein the set of non-communication zones correspond to one or more geographical areas in which one or more radio frequency bands are prohibited for the UAV.

5. The network entity of claim 4, wherein the modified policy prohibits the one or more frequency bands for the UAV in the one or more geographical areas.

6. The network entity of claim 4 or claim 5, wherein the policy comprises a mapping of one or more radio access technology (RAT) frequency selection priority (RFSP) indexes to the one or more geographical areas to define the set of non-communication zones.

7. The network entity of any preceding claim, wherein the instructions are further executable by the at least one processor to cause the network entity to: determine the set of non-communication zones based on at least in part on one or more of an identifier of the PLMN or a flight path of the UAV.

8. The network entity of any preceding claim, wherein the indication indicates that the UAV is authorized to access the PLMN to perform at least one UAV operation.

9. The network entity of claim 8, wherein the instructions are further executable by the at least one processor to cause the network entity to: determine that the UE is UAS service supplier (USS) authenticated and authorized based at least in part on the indication.

10. The network entity of any preceding claim, wherein the instructions are further executable by the at least one processor to cause the network entity to: determine that the UE is authorized for communication in the PLMN, wherein the communication comprises command and control (C2) communication.

11. The network entity of any preceding claim, wherein the indication indicates that the UAV has entered at least one non-communi cation zone of the set of non-communi cation zones.

12. A network entity for wireless communication, the network entity comprising instructions executable by at least one processor to cause the network entity to: receive, from a second network entity, a message comprising a set of modified policies associated with an uncrewed aerial vehicle (UAV); determine a set of radio access technology, RAT, Frequency Selection Priority, RFSP, policies associated with a set of non-communication zones for a public land mobile network (PLMN); and output, to a third network entity, the set of modified policies including the set of RFSP policies for the set of non-communication zones for the PLMN.

13. The network entity of claim 12, wherein the network entity comprises a policy control function (PCF), and wherein the second network entity comprises a unified data management (UDM).

14. The network entity of claims 12 or 13, wherein the network entity comprises a policy control function (PCF), and wherein the third network entity comprises an access and mobility function (AMF).

15. The network entity of any of claims 12 to 14, wherein the instructions are further executable by the at least one processor to cause the network entity to: output the set of modified policies based at least in part on an indication that the UAV established a session for at least one UAV operation.

16. The network entity of claim 15, wherein the third network entity comprises a session management function (SMF).

17. The network entity of any of claims 12 to 16, wherein the instructions are further executable by the at least one processor to cause the network entity to: output the set of modified policies in response to an indication from the third network function that the UAV has entered at least one non-communication zone of the set of non-communi cation zones or is estimated to enter the at least one non-communication zone of the set of non-communi cation zones, wherein the third network entity comprises an access and mobility function (AMF) or a location management function (LMF)

18. A method performed by a first network entity for wireless communication, the method comprising: obtaining an indication that indicates an uncrewed aerial vehicle (UAV) accessing a public land mobile network (PLMN); and transmitting, to a second network entity, a request to modify a policy to include a set of non-communication zones associated with the PLMN for the UAV.

19. A method performed by a network entity for wireless communication, the method comprising: receiving, from a second network entity, a message comprising a set of modified policies associated with an uncrewed aerial vehicle (UAV); determining a set of radio access technology, RAT, Frequency Selection Priority, RFSP, policies associated with a set of non-communication zones for a public land mobile network (PLMN); and outputting, to a third network entity, the set of modified policies including the set of RFSP policies for the set of non-communi cation zones for the PLMN.