Third party provisioning for no-transmission zone and band restriction for aerial vehicles

Abstract

A method includes transmitting, by a network apparatus of an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and receiving, by the network apparatus, based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

Description

THIRD PARTY PROVISIONING FOR NO-TRANSMISSION ZONE AND BAND RESTRICTION FOR AERIAL VEHICLESFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, to provisioning of no-transmission zone (NTZ) and / or band restriction for aerial vehicles.BACKGROUND

[0002] Wireless networking provides significant advantages for user mobility. A user’s ability to remain connected while on the move provides advantages not only for the user, but also provides greater efficiency and productivity for society as a whole. As user expectations for, e.g., aerial vehicle communications, aircraft-to-everything (A2X) services, become more demanding, technology for wireless networking must also keep pace with such expectations. Accordingly, there is continuing interest in improving wireless networking technology.SUMMARY

[0003] As used herein, the term “entity” may refer to a distinct component of an architecture or device, a network device, a network node, a network function, or any other devices (physical or virtual) in a communication network.

[0004] In accordance with aspects of the present disclosure, a method includes transmitting, by a network apparatus of an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, where the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and receiving, by the network apparatus, based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

[0005] In an aspect of the method, the NTZ information provisioning request further includes a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and where the method further includes receiving, by the network apparatus based on the subscription, the notification of the outcome of the UE policy delivery.

[0006] In an aspect of the method, the method further includes transmitting, by the network apparatus, an update request to update the NTZ information at the core network, where the update request includes the transaction reference ID.

[0007] In an aspect of the method, the method further includes transmitting, by the network apparatus, a deletion request to delete the NTZ information from the core network, where the deletion request includes the transaction reference ID.

[0008] In an aspect of the method, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or. information associated with a time period during which the NTZ is applicable.

[0009] In an aspect of the method, the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and where the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0010] In accordance with aspects of the present disclosure, a method includes receiving, by a network apparatus of a network exposure function (NEF) entity associated with a core network from an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to the core network, where the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and transmitting, by the network apparatus to the UAS authorization entity based on the receiving the NTZ information provisioning request, a transaction reference identifier (ID).

[0011] In an aspect of the method, the NTZ information provisioning request further includes a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and where the method further includes transmitting, by the network apparatus to the UAS authorization entity based on the subscription, the notification of the outcome of the UE policy delivery.

[0012] In an aspect of the method, the method further includes receiving, by the network apparatus from a policy control function (PCF) entity of the core network, a PCF event notification message including the outcome of the UE policy delivery.

[0013] In an aspect of the method, the method further includes storing, at a unified data repository (UDR) of the core network, the NTZ information in association with the UE policy.

[0014] In an aspect of the method, the method further includes receiving, by the network apparatus from the UAS authorization entity, an update request to update the NTZ information, where the update request includes the transaction reference ID; and updating, based on the receiving the update request, the NTZ information stored at the UDR.

[0015] In an aspect of the method, the method further includes receiving, by the network apparatus from the UAS authorization entity, a deletion request to delete the NTZ information, where the deletion request includes the transaction reference ID; and deleting, based on the receiving the deletion request, the NTZ information from the UDR.

[0016] In an aspect of the method, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0017] In an aspect of the method, the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and where the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0018] In accordance with aspects of the present disclosure, a method includes configuring, by a network apparatus at a core network, a user equipment (UE) policy for a UE to perform aerial vehicle communication, where the configuring is based at least in part on no-transmission zone (NTZ) information provisioned by an uncrewed aerial system (UAS) authorization entity external to the core network; transmitting, by the network apparatus to the UE, the UE policy including the NTZ information; receiving, by the network apparatus from the UE, a response to the UE policy; and transmitting, by the network apparatus to a network exposure function (NEF) entity associated with the core network, a notification of the response to the UE policy.

[0019] In an aspect of the method, the method further includes receiving, by the network apparatus from a unified data repository (UDR) entity of the core network, a notification of a data change associated with the NTZ information, where the configuring the UE policy is based on the data change associated with the NTZ information.

[0020] In an aspect of the method, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0021] In an aspect of the method, the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and where the UE corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0022] In an aspect of the method, the network apparatus includes a policy control function (PCF) entity of the core network.

[0023] In accordance with aspects of the present disclosure, In Example 20, A method including receiving, by a user equipment (UE) from a core network, a UE policy for aerial vehicle communication, the UE policy including no-transmission zone (NTZ) information; receiving, by the UE from the core network, an updated UE policy including updated NTZ information; and transmitting, by the UE to the core network, a response to the reception of the updated UE policy.

[0024] In an aspect of the method, the updated NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, or information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0025] In an aspect of the method, the method further includes refraining, by the UE, from performing a cell search or transmitting in the geographical.

[0026] In an aspect of the method, the refraining from performing a cell search or transmitting in the geographical area is further based on the flag value.

[0027] In an aspect of the method, the refraining from performing a cell search or transmitting in the geographical area includes refraining, by the UE, from performing a cell search or transmitting in any of the one or more restricted transmission bands.

[0028] In an aspect of the method, the refraining from performing a cell search or transmitting in the geographical area includes refraining, by the UE during the time period which the NTZ is applicable, from performing a cell search or transmitting in the geographical area.

[0029] In an aspect of the method, the method further includes transmitting, by the UE, a communication signal using a frequency band outside of the one or more restricted transmission bands.

[0030] In an aspect of the method, the transmitting the communication signal includes transmitting, by the UE during the time period which the NTZ is applicable, the communication signal using the frequency band outside of the one or more restricted transmission bands.

[0031] In an aspect of the method, the method further includes transmitting, by the UE, a communication signal using a frequency band in the one or more allowed transmission bands.

[0032] In an aspect of the method, the transmitting the communication signal includes transmitting, by the UE during the time period which the NTZ is applicable, the communication signal using the frequency band in the one or more allowed transmission bands.

[0033] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Some example embodiments will now be described with reference to the accompanying drawings.

[0035] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0036] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0037] FIG. 3 is a diagram of an example network system that provides services to uncrewed aerial vehicles (UAVs), according to one illustrated aspect of the disclosure;

[0038] FIG. 4 is a diagram of an example embodiment of operations for provisioning no-transmission zone (NTZ) information, according to one illustrated aspect of the present disclosure;

[0039] FIG. 5 is a diagram of an example embodiment of operations for updating a UE configuration based on NTZ information, according to one illustrated aspect of the present disclosure;

[0040] FIGS. 6A-6C illustrate example NTZ information for UAV communications, according to one illustrated aspect of the present disclosure;

[0041] FIG. 7 is a flow diagram of example operations of a network apparatus provisioning NTZ information, according to one illustrated aspect of the present disclosure;

[0042] FIG. 8 is a flow diagram of example operations of a network apparatus facilitating NTZ information provisioning, according to one illustrated aspect of the present disclosure;

[0043] FIG. 9 is a flow diagram of example operations of a network apparatus facilitating NTZ information provisioning, according to one illustrated aspect of the present disclosure;

[0044] FIG. 10 is a flow diagram of example operations of a UE receiving an NTZ information update, according to one illustrated aspect of the present disclosure; and

[0045] FIG. 11 is a diagram of example embodiment of components of a UE or of a network apparatus, according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0046] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0047] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0048] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband- code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0049] An uncrewed aerial vehicle (UAV) is an aircraft that operates without an onboard human pilot and can be remotely controlled by an operator using a UAV controller. Some UAVs may also have autonomous flight capabilities. In some examples, a UAV may be a drone. An uncrewed aerial system (UAS) may include one or more UAVs and one or moreUAV controllers. Additionally, the UAS may be in communication with an uncrewed aerial system traffic management (UTM) system. The UTM system may integrate flying UAV(s) along with other airspace users. For instance, the UTM system may provide a set of functions and services for managing a range of autonomous vehicle operations (e.g., authenticating a UAV, authorizing UAS services, managing UAS policies, and controlling UAV traffic in the airspace).

[0050] A UAS network function (UAS NF) is a 3rd Generation Partnership Project (3GPP) network function that may offer services to UAVs, for example, including authentication, flight authorization, tracking, and communication quality control. A UAS service supplier (USS) may support safe airspace use by providing services to UAS operators to meet UTM requirements. Third party authorized entities (TPAE) (e.g., ground control towers) may also play a role in UAS management, for example, for UAV traffic control.

[0051] In the present disclosure, a UAV may include a mobile communication device capable of communicating with a wireless communication system, such as a 3 GPP system (e.g., a 5G system (5GS)). The terms “UAV,” “aerial communication device,” “aerial vehicle,” “aerial UE,” and “UAV-UE” may be used interchangeably herein, such that a description referring to one of the terms shall be treated as though the description also referred to the other term. Further, in some instances, a UAV-UE may simply be referred to as a UE.

[0052] In some scenarios, it may be desirable to restrict aerial communication devices (e.g., UAVs) from transmissions in certain geographical area(s) and / or within certain frequency band(s) for spectrum compatibility purposes. For instance, the European conference of postal and telecommunications administrations (CEPT) decision 22(07) outlines technical conditions for using aerial UEs in several LTE and 5G NR bands that are harmonized for harmonized mobile / fixed communication networks (MFCNs), and specifically for operational restrictions on the aerial UEs in the form of no-transmit zones (NTZs). According to CEPT, an NTZ is a geographical area where an aerial UE is not allowed to transmit in a given MFCN band or part of a MFCN band for spectrum compatibility purposes. In addition to the harmonized technical conditions for MFCN bands, there is a need to further define spectrum operational restrictions. For instance, at a national level, NTZs may be defined for aerial UEs in relevant frequency bands to ensure spectral compliance. In some cases, operations of aerial UEs may also be required to meet respective cross-border coordination agreements. In an example, LTE and 5G NR bands in the 703-733 megahertz (MHz), 832-862 MHz, 880-915 MHz, 1710-1785 MHz, 1920-1980 MHz, 2500-2570 MHz and MFCN harmonized bands in 2570-2620 MHz may beconsidered as NTZs for aerial UEs. In general, an NTZ may refer to a total restriction on transmission (i.e., no allowable transmission band) or a transmission restriction on one or more particular frequency bands.

[0053] Considering that there are NTZs (defined by CEPT) and certain frequency bands (defined at a national level) where aerial UEs are not allowed to transmit, there is a need for mechanisms to ensure that aerial UEs respect these NTZs and / or band restrictions.

[0054] 3 GPP release- 19 (Rel-19) proposed enhanced network exposure function (NEF) services to support mobile network operator (MNO)-UTM data services. NEF services are services that securely expose 3GPP core network capabilities to third parties and / or non-3GPP entities. These NEF services may assist, for example, but not limited to, intelligent flight planning, monitoring, interfacing with UTM infrastructure (e.g., including multiple USSs), and quality of experience (QoE) estimation using 5GSs. In one example, enhanced NEF service(s) can provide additional information to an UAV operator (or USS) to execute pre-flight preparations and in-flight operations (e.g., flight mission application, flight path recommendation, flight monitoring and control). In another example, enhanced NEF service(s) can support enhanced UAV flight and / or route management based on network capacity and quality of service (QoS) information along a planned route. There are also recommendations from aviation industry bodies such as global system for mobile communications association (GSMA) and aerial connectivity joint activity (ACJA) to enhance service exposures to further assist aviation operations.

[0055] Accordingly, it may be desirable for MNOs to provide service exposure(s) to the aviation industry (e.g., UAS operators, UTM, command and control connectivity service providers (C2CSPs), etc.) using cellular networks as a reliable communication backbone for aviation vertical, e.g., supporting different aerial flight zones with varying UAV settings and / or communication QoS.

[0056] One approach to configuring NTZ information for UAV-UEs is via aircraft-to- everything (A2X) policies. To that end, A2X policy may provide configuration parameters to a UAV-UE for A2X communication over a PC5 reference point (e.g., for sidelink communication) and / or over a Uu reference point (e.g., for direct communication). However, currently, a 5GS does not allow A2X policies to be provisioned by an external entity (a non- 3GPP entity). Moreover, A2X policies are not currently stored at a unified data repository (UDR) of the 5GS, but manually configured at a policy control function (PCF) entity of the 5GS. Because NTZ information may not be known a priori to an operator, manualconfiguration may not be suitable for configuring NTZ information at a 5GS. Furthermore, in some situations, it may be desirable to provision (or update) NTZ information dynamically based on conditional changes (e.g., changes in conditions and / or requirements).

[0057] The terms “A2X policy” and “UE policy” may be used interchangeably herein, such that a description referring to one of the terms shall be treated as though the description also referred to the other term.

[0058] Aspects of the present disclosure provide techniques for a core network (e.g., a 5G core (5GC)) to control and manage UAV communications within NTZs and / or band-restricted areas along the UAVs’ flight paths (e.g., pre-mission flight paths and / or upcoming flight paths). For example, a NEF entity associated with the core network may provide service operations (e.g., application programming interfaces (APIs)) for an external entity to provision NTZ information to the core network and store the provisioned NTZ information at a UDR of the core network. A PCF entity at the core network may utilize the NTZ information stored at the UDR to configure NTZ(s) and / or band restriction(s) for a UAV-UE. In this way, the UAV-UE may adhere to the configured NTZ(s) and / band restriction(s) and adapt the UAV-UE’ s behavior accordingly. For example, in aspects, a UAV-UE may refrain from performing a cell search or transmitting when it is in an NTZ. In aspects, a UAV-UE may transmit a communication signal using a frequency band outside of restricted transmission band(s) while the UE is in the NTZ.

[0059] As used herein, the term “network function” may be a software instance executing on hardware (e.g., a network apparatus) or a virtualized function instantiated on hardware. Further, the terms “service operation” and “API” may be used interchangeably herein, such that a description referring to one of the terms shall be treated as though the description also referred to the other term.

[0060] According to an aspect of the present disclosure, a UAS authorization entity external to a core network may transmit, to a NEF entity of the core network, an NTZ information provisioning request to provision NTZ information to the core network. In some examples, the UAS authorization entity may be a USS or a TPAE. The NTZ information may be configured to be used by the core network to configure a UE policy (e.g., an A2X policy) for a UAV (UAV-UE). The NTZ information may include at least one of the following: coordinate information (e.g., a list of coordinates including longitude, latitude, and / or altitude information) indicative of a geographical area (or airspace), a flag value indicating whether an NTZ is applicable in the geographical area, frequency information associated with one or moreallowed transmission bands, frequency information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable. In some instances, the geographical area may be along a pre-mission flight path of the UAV. In other instances, the geographical area may be along an upcoming flight path of the UAV. In aspects, the NTZ information may be provisioned for an individual UE, a group of UEs (e.g., a category of UEs), or a public land mobile network (PLMN), and the UAV may correspond to the individual UE, the group of UEs, or all UEs served by the PLMN. The UAS authorization entity may receive, based on the transmitting (e.g., in response to) the NTZ information, a transaction reference identifier (ID).

[0061] The transaction reference ID may be included in subsequent request(s) related to the NTZ information. For instance, the UAS authorization entity may further transmit, to the NEF entity, an update request to update the NTZ information at the core network and may include the transaction reference ID in the update request. Additionally or alternatively, the UAS authorization entity may further transmit, to the NEF entity, a deletion request to delete the NTZ information from the core network and may include the transaction reference ID in the deletion request.

[0062] In aspects, the NTZ information provisioning request may further include a request for a subscription to a notification of an outcome of a delivery of the UE policy (that is configured based on the NTZ information). Based on (e.g., in response to) the subscription, the UAS authorization entity may receive the notification of the outcome of the UE policy delivery. In an example, the outcome may indicate a successful delivery of the UE policy to the UAV. Alternatively, the outcome may indicate a failure in delivering the UE policy and may further provide a cause of the failure (e.g., the UAV is unreachable).

[0063] In aspects, upon the NEF entity receiving the NTZ information provisioning request from the UAS authorization entity, the NEF entity may store the NTZ information at a UDR of the core network. In an example, the UDR may provide an API for installing or storing NTZ information at the UDR. In aspects, upon the NEF entity receiving the update request from the UAS authorization entity, the NEF entity may update the NTZ information at the UDR. In an example, the UDR may provide an API for modifying NTZ information stored at the UDR. In aspects, upon the NEF entity receiving the deletion request from the UAS authorization entity, the NEF entity may delete the NTZ information from the UDR. In an example, the UDR may provide an API for removing NTZ information from the UDR.

[0064] In aspects, the NEF entity may subscribe to event(s) of a PCF entity of the core network. For instance, the NEF entity may subscribe to an outcome of a delivery of the UE policy (that is configured based on the NTZ information and provisioned by the UAS authorization entity external to the core network). Based on (e.g., in response to) the NEF entity ’ s subscription, the NEF entity may receive, from the PCF entity, a PCF event notification message including an indication of the outcome of the UE policy delivery. As discussed above, the NTZ information provisioning request (from the UAS authorization entity) may include a subscription to the outcome of a UE policy delivery in association with the NTZ information. Accordingly, the NEF entity may further transmit the outcome of the UE policy delivery to the UAS authorization entity.

[0065] In aspects, the PCF entity may subscribe to be notified of a data change associated with NTZ information at the UDR. Accordingly, the PCF entity may receive, from the UDR, a notification of a data change associated with the NTZ information (provisioned by the UAS authorization entity and stored at the UDR). Upon receiving such a notification, the PCF entity may configure the UE policy for the UAV according to the NTZ information. Accordingly, the PCF entity may configure or generate the UE policy for the UAV according to the NTZ information stored at the UDR. The PCF entity may transmit the UE policy to the UAV (e.g., via an access and mobility management (AMF) entity of the core network) and receive a response from the respective UAV (e.g., via the AMF). If the NEF entity (of the core network) has subscribed to notifications of events at the PCF entity, the PCF entity may transmit the UAV’s response to the NEF entity.

[0066] According to a further aspect of the present disclosure, a UE (e.g., a UAV) may receive, from a core network, a UE policy (e.g., A2X policy) for aerial vehicle communications, where the UE policy may include NTZ information. The UE may receive, from the core network, an updated UE policy including (dynamically) updated NTZ information. The UE may transmit, to the core network, a response to the reception of the updated UE policy. For instance, the response may indicate a successful reception of the UE policy. In aspects, the updated NTZ information may include at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, frequency information associated with one or more allowed transmission bands, frequency information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable. In aspects, the UE may refrain from performing a cell search or transmitting in thegeographical area. In aspects, the refraining from performing the cell search or transmitting in the geographical area may be further based on the flag value. In aspects, as part of the refraining, the UE may refrain from performing the cell search or transmitting in the geographical area during the time period which the NTZ is applicable. In aspects, as part of the refraining, the UE may refrain from performing a cell search or transmitting in any one of the restricted transmission bands while the UE is in the geographical area. In aspects, the UE may transmit a communication signal using a frequency band outside of the one or more restricted transmission bands while the UE is in the geographical area. In aspects, the UE may transmit a communication signal using a frequency band in the one or more allowed transmission bands while the UE is in the geographical area. Such and other aspects will be described in more detail later herein.

[0067] Aspects of the present disclosure may provide several benefits. For example, the addition of a NEF to provide service operations for an external entity (e.g., USS, TPAE) to interface with a core network (e.g., 5GC) for provisioning, updating, and / or deleting NTZ information can enable the core network to control and manage NTZs and band restrictions per geographical area to meet spectral compliance regulations or requirements for aerial vehicles. While the present disclosure is discussed in the context of enabling a 3GPP 5GC to control and manage NTZs and band restrictions per geographical area for UAV communications, aspects of the present disclosure are applicable to any suitable type of wireless communication systems.

[0068] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0069] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or uncrewed aerial vehicles as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0070] FIG. l is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g.,test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3GPP. However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0071] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides NR user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021- 06) section 3.2, which is hereby incorporated by reference herein.

[0072] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0073] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g. : o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC QoS flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0074] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0075] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., RRC, service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interfaceconnected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0076] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., RLC, media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0077] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 11 below.

[0078] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open- RAN (0-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0079] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0080] The UE 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicleapparatus, an Internet of Things (loT) device, a machine-to-machine (M2M) device, or a UAV, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 9. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0081] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0082] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0083] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the RAN 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0084] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0085] For example, a control network (CN) 210 is described in the control plane of the network system. The CN 210 includes an authentication server function (AUSF) 211, an AMF 212, and a session management function (SMF) 213. The CN 210 also includes a network slice selection function (NSSF) 214, a NEF 215, a network repository function (NRF) 216, and a UDM 217, which may include UDR 224.

[0086] Additional components and functions of the CN 210 include an application function (AF) 218 and a PCF 219.

[0087] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 227 identifies services from service providers, Internet access, and third-party services, for example.

[0088] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts PDU session management, as well as manages session context with the UPF 226.

[0089] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination are utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0090] The UDM 217 generates authentication vectors for use by the AUSF 211 and AMF 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide QoS and charging functionality. In some instances, the UDM 217 and / or UDR 224 may be referred to as a network data component.

[0091] As further shown in FIG. 2, the network system further includes a UAS NF 230, which is a NEF that may securely expose capabilities of the CN 210 to third parties and / or non- 3GPP entities for providing services to UAVs (e.g., the UE 150). In the illustrated example of FIG. 2, the UAS NF 230 is outside of the CN 210. However, in other instances, the UAS NF 230 may be part of the CN 210. For example, the UAS NF 230 may be a NEF 215 within the CN 210.

[0092] According to aspects of the present disclosure, the UAS NF 230 may communicate with components of the CN 210, for example, the UDM 217, the UDR 224, the PCF 219, and the AMF 212 to enable third parties and / or non-3GPP entities to provision NTZ parameters (e.g., NTZs and restricted bands per geographical area) to the CN 210 for configuring UE policies (e.g., A2X policies) for UAV-UEs. Mechanisms for enabling a core network to control and manage NTZ parameters for UAV communication will be discussed more fully below.

[0093] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0094] FIG. 3 is a block diagram of an example network system that provides services to a UAV, according to one illustrated aspect of the disclosure. As shown in FIG. 3, the network system includes a UE 302, a 5GS 320, and an evolved packet system (EPS) 330. The UE 302 may be a UAV as discussed above. The UE 302 may perform communications by accessing the 5GS 320 and / or the EPS 330. In one example, the UE 302 may be a 5GUE and may perform communications by accessing the 5GS 320. In another example, the UE 302 may be an LTE UE and may perform communications by accessing the EPS 330. In a further example, the UE 302 may be a dual -connectivity UE and may perform communications by accessing the 5GS 320 and the EPS 330 (e.g., switching between the 5GS 320 and the EPS 330).

[0095] The 5GS 320 may include an NG-RAN 304 and a 5GC 310. In an example, the NG- RAN 304 may correspond to the RAN 225 and the 5GC 310 may include network components such as the UPF 226 and components of the CN 210 discussed above with reference to FIG. 2. In the context of 3GPP, the NG-RAN 304 may communicate with the 5GC 310 over a N3 interface.

[0096] The EPS 330 may include a (radio) access network ((R)AN) 306 and an evolved packet core (EPC) 312. The (R)AN 306 may include network nodes, network components, and / or base stations described in connection with FIG. 1. In an example, the (R)AN 306 may be a EUTRAN. The EPC 312 may perform substantially similar operations as the CN 210 and the UPF 226 discussed above with reference to FIG. 2. However, the EPC 312 may partition core network functionalities differently than the network system shown in FIG. 2 and may include different components than the components shown in FIG. 2. In general, the EPC 312 may include components configured to manage session states, authenticate and track the UE 302 across the EPS 330, and route data packets through the (R)AN 306. In the context of 3 GPP, the (R)AN 306 may communicate with the EPC 312 over an SI interface.

[0097] As further shown in FIG. 3, the network system includes a UAS NF 308, which is a NEF associated with the 5GC 310. The UAS NF 308 may communicate with various components of the 5GC 310. In the context of 3GPP, the UAS NF 308 may communicate with the 5GC 310 via N29, N30, N51, N15, N36 interfaces. The UAS NF 308 may perform a network function of exposing services or capabilities of the 5GC 310 to a USS 316 in a DN 318. In the context of 3GPP, the UAS NF 308 may communicate with the USS 316 over a N33 interface. In an example, the UAS NF 308 and the DN 318 may correspond to the UAS NF 230 and the DN 227 of FIG. 2, respectively. The USS 316 may support safe airspace use by providing services to UAS operators to meet UTM requirements. In the illustrated example of FIG. 3, the UAS NF 308 and the USS 316 are outside of the 5GS 320. However, in some instances, the UAS NF 308 and / or the USS 316 can be part of the 5GS 320. Additionally or alternatively, the UAS NF 308 may operate as a service capability exposure function (SCEF) to communicate with various components of the EPC 312 and perform network function of exposing services or capabilities of the EPC 312 to the USS 316.

[0098] As further shown in FIG. 3, a TPAE 314 may communicate with the 5GS 320 and the EPS 330 via the DN 318. The TPAE 314 may play a role in UAS management, for example, for UAV traffic control. In the context of 3 GPP, the TPAE 314 may communicate with the 5GC 310 via a N6 interface and communicate with the EPC 312 via an SGi interface.

[0099] According to aspects of the present disclosure, the UAS NF 308 may provide services for the USS 316 and / or the TPAE 314 to provision NTZ information to the 5GC 310 (or the EPC 312), dynamically update NTZ information stored at the 5GC 310, and / or delete NTZ information from the 5GC 310 (or the EPC 312). The NTZ information may indicate NTZs and / or band restrictions per geographical area, for example, to meet certain spectral compliance regulations. The NTZ information may be configured to be used by the 5GC 310 (or the EPC 312) to configure a UE policy for the UE 302 (the UAV) so that the UE 302 may avoid transmitting in those NTZs and / or restricted bands.

[0100] FIG. 3 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 3. In embodiments, the network system may not include every component illustrated in FIG. 3. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0101] The following will describe example operations for NTZ information provisioning. FIG. 4 shows example signals and operations for provisioning NTZ information. FIG. 5 shows example signals and operations for updating a UE configuration based on NTZ information. FIGS. 6A-6C show an example NTZ information. FIG. 7 shows example operations of a network apparatus of a UAS authorization entity such as a USS or a TPAE. FIG. 8 shows example operations of a network apparatus of a UAS NF entity. FIG. 9 shows example operations of a network apparatus of PCF entity. FIG. 10 shows example operations of a UE (e.g., a UAV-UE).

[0102] FIG. 4 is a diagram of an example embodiment of operations for provisioning NTZ information, according to one illustrated aspect of the present disclosure. It will be understood that a described signal may have associated operations and a described operation may have associated signals. Accordingly, a described signal may also involve an operation and a described operation may also involve a signal. Additionally, FIG. 4 will describe signals between and operations performed by various network components, such as those shown at the top of FIG. 4. Specifically, the components include a UE 401, a (R)AN 402, an AMF 403, a PCF 404, a UDM 405, a UDR 406, a NEF 407, and a UAS authorization entity 408. The UE 401 may be a UAV as discussed above and may be similar to the UE 150 of FIG. 1 and / or the UE 302 of FIG. 3. The AMF 403, the PCF 404, the UDM 405, and the UDR 406 may be partof a core network 409 similar to the CN 210 of FIG. 2 and / or the 5GC 310 of FIG. 3. For instance, the AMF 403, the PCF 404, the UDM 405, and the UDR 406 may be similar to the AMF 212, the PCF 219, the UDM 217, and the UDR 224 of FIG. 2, respectively. The (R)AN 402 may be similar to the RAN 225 of FIG. 2 and / or the NG-RAN 304 of FIG. 3. The NEF 407 may be similar to the UAS NF 230 of FIG. 2 and / or the UAS NF 308 of FIG. 3. The UAS authorization entity 408 may be similar to the US S 316 or the TPAE 314 of FIG. 3. The network components are illustrative, and it is contemplated that other components may be involved in the signals or may perform the operations. In some examples, each of the network components may implement the operations using an apparatus with components as shown in FIG. 11. One or more of the following operations may be implemented in connection with the operations of the present disclosure, such as the examples discussed above with reference to FIGS. 1-3.

[0103] At operation 410, the UE 401 may perform a UE registration procedure with the core network 409 via the (R)AN 402. At operation 412, as part of the UE registration procedure, the AMF 403 may interact with the PCF 404 to perform policy association. For instance, the PCF 404 may provide access and mobility management related policies for the AMF 403 to trigger policy rules on the UE 401. At operation 414, the PCF 404 may transmit, and the UDR 406 may receive a subscription to a notification of a data change at the UDR 406. In an example, the PCF 404 may invoke a Nudr DM subscribe service operation provided by the UDR 406 as part of transmitting the subscription. Persons skilled in the art will understand a Nudr_DM_sub scribe service operation.

[0104] At operation 416, the UAS authorization entity 408 may create an AF request to provision NTZ information to the core network 409. The NTZ information may be configured to be used by the core network 409 to configure a UE policy for UAV communications (e.g., for at least the UE 401). As will be discussed more fully below with reference to FIGS. 6A- 6C, the NTZ information may include indications of NTZs and / or restricted transmission bands per geographical area. At operation 418, as part of creating the AF request, the UAS authorization entity 408 may transmit, and the NEF 407 may receive an NTZ information provisioning request. In an example, the UAS authorization entity 408 may invoke a Nnef_NTZParameter_Create request service operation provided by the NEF 407 as part of transmitting the NTZ information provisioning request. The Nnef NTZParameter Create request service operation may have input parameters, for example, including but not limited to, NTZ parameters, an indication of a time period during which the NTZ parameters may be applicable or valid (i.e., the no-transmission restriction may be time-bound), a target identifierfor which the NTZ parameters are to be provisioned, and / or subscription parameters. In some instances, the indication of the time period can be included as part of the NTZ parameters.

[0105] In aspects, the UAS authorization entity 408 may be interested in a report about whether a UE policy configured with the NTZ information is delivered successfully to a respective UE. Accordingly, the UAS authorization entity 408 may include, in the NTZ information provisioning request, a request for a subscription to a notification of an outcome of a UE policy delivery (e.g., an A2X policy delivery).

[0106] In aspects, the UAS authorization entity 408 may provision NTZ information at an individual UE level (e.g., specifically for the UE 401), at a UE group level (e.g., for a group of UEs including the UE 401), or at a PLMN level (e.g., for all UEs including the UE 401 in the PLMN). Accordingly, the NTZ information provisioning request may include a target ID identifying an individual UE, a group of UEs, or a PLMN for which the NTZ information is to be provisioned. For instance, if the NTZ information is to be provisioned for an individual UE, the NTZ information provisioning request may include a target UE ID including a general public subscription identifier (GPSI). If the NTZ information is to be provisioned for a group of UEs, the NTZ information provisioning request may include a target UE ID including an external group ID. If the NTZ information is to be provisioned for a PLMN, the NTZ information provisioning request may include a PLMN ID.

[0107] At operation 420, upon receiving the NTZ information provisioning request, the NEF 407 may interact with the UDM 405 to obtain information for performing identifier mappings. In an example, the NEF 407 may invoke a Nudm SDM Get service operation provided by the UDM 405 to request information from the UDM 405. Persons skilled in the art will understand a Nudm SDM Get request service operation. For instance, if the NTZ information provisioning request includes a target UE ID for an individual UE, the NEF 407 may map the GPSI in the target ID into a subscription permanent identifier (SUPI) according to information received from UDM 405. A SUPI is an ID assigned by a 3GPP system. Alternatively, if the NTZ information provisioning request includes a target UE ID for a group of UEs, the NEF 407 may map the external group ID in the target UE ID into an internal group ID according to information received from UDM 405. In general, a UAV-UE (e.g., the UE 401) may be identified by the UAS authorization entity 408 using a civil aviation administration (CAA)-level ID (e.g., GPSI, external group ID) and identified by a 3GPP system (e.g., the core network 409) using a 3GPP UAV ID (e.g., SUPI or internal group ID). Persons skilled in the art will understand a Nudm SDM Get service operation.

[0108] At operation 422, the NEF 407 may interact with the UDM 405 to authorize a service specific parameter provisioning request with the UDM 405. More specifically, the NEF 407 may interact with the UDM 405 to authorize the NTZ information provisioning request (received from the UAS authorization entity 408). In an example, the NEF 407 may invoke a Nudm ServiceSpecificAuthorization Create service operation provided by the UDM 405 as part of the authorization. Persons skilled in the art will understand a Nudm ServiceSpecificAuthorization Create service operation.

[0109] At operation 424, upon a successful authorization of the NTZ information provisioning request, the NEF 407 stores the NTZ information at the UDR 406. The NEF 407 may store the NTZ information in the UDR 406 in association with the SUPI (when the NTZ information is for an individual UE), with the external group ID (when the NTZ information is for a group of UEs), or with a PLMN ID (when the NTZ information is for all UEs in a PLMN). For example, as part of storing the NTZ information, a UDR data element, named “Data Set”, may be set to "UEPolicySet" and a UDR data element, named “Data Subset”, may be set to "A2X NTZ Info," and the UDR 406 may store the NTZ information and assign a transaction reference ID to the storage of the NTZ information. In general, the UDR 406 may store the NTZ information using any suitable data structures.

[0110] At operation 426, the NEF 407 transmits, and the UAS authorization entity 408 receives a response to the NTZ information provisioning request. In an example, the NEF 407 may invoke a Nnef NTZParameter Create response service operation to provide the response to the UAS authorization entity 408. The response may include the assigned transaction reference ID. As will be discussed more fully below, the transaction reference ID may be included in subsequent request(s) related to the NTZ information. The Nnef NTZParameter Create response service operation may have one or more input parameters, for example, including but not limited to, the transaction reference ID and / or a result (e.g., success or failure) of the Nnef NTZParameter Create service operation.[OHl] The creation and storage of the NTZ information at the UDR 406 at operation 424 may trigger a data change event at the UDR 406. If the UE 401 is registered to the core network 409 and the PCF 404 has subscribed to be notified of data modified in the UDR 406 by invoking Nudr DM Sub scribe (USS / TPAE NTZ parameter provisioning information, SUPI, Data Set setting to "UEPolicySet", Data Subset setting to " A2X NTZ Info") at operation 410, the following operations 428-434 may be performed. Otherwise, the operations 428 to 434 may not be performed.

[0112] At operation 428, the UDR 406 transmits, and the PCF receives a notification of a data change at the UDR 406 due to the NTZ information (provisioned by the UAS authorization entity 408). In an example, as part of receiving the notification, the PCF 404 may receive a Nudr DM Notify notification from the UDR 406. Persons skilled in the art will understand a Nudr_DM_Notify service operation.

[0113] As discussed above, in some instances, the UAS authorization entity 408 may provision the NTZ information to a group of UEs. In such instances, the PCF 404 does not have to subscribe to be notified, for each UE, of the NTZ information (e.g., application specific information). Instead, the PCF 404 may subscribe to be notified of the NTZ information for the group of UEs. For example, when the PCF 404 receives NTZ information for the group of UEs, the PCF 404 may deliver the same NTZ information to every UE in the group.

[0114] At operation 430, upon receiving the notification of the newly created NTZ information at the UDR 406, the PCF 404 initiates a UE policy delivery procedure. For instance, the PCF 404 may configure the NTZ information as part of a UE policy (e.g., A2X policy), deliver the UE policy to the UE 401 via the AMF 403, and receive a result of the UE policy delivery via the AMF 403. Mechanisms for performing a UE policy delivery will be discussed more fully below with reference to FIG. 5.

[0115] If the UAS authorization entity 408 has subscribed to notifications about outcomes of UE policy deliveries due to NTZ parameter provisioning targeting a single UE (e.g., the UE 401) and the PCF 404 is notified of a result of the UE policy delivery, the PCF 404 may notify the NEF 407 of the UE delivery result. For instance, at operation 432, the PCF 404 transmits, and the NEF 407 receives a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information. More specifically, the PCF 404 may receive a UE policy container from the AMF 403 (e.g., as part of operation 430) and may transmit the UE policy delivery result included in the UE policy container as the outcome of the UE policy delivery procedure to the NEF 407 by sending a Npcf_EventExposure_Notify notification (indicating the outcome). Persons skilled in the art will understand a Npcf_EventExposure_Notify notification.

[0116] If the PCF 404 is notified about a UE policy delivery failure from the AMF 403 due to the UE 401 being not reachable, the PCF 404 may determine to retry the UE policy delivery procedure at operation 430 when the UE 401 becomes reachable. In such a case, the PCF 404 may report an interim status (e.g., UE is temporarily unreachable) as the outcome of theprocedure to NEF 407 by sending a Npcf_EventExposoure_Notify notification (indicating the interim status).

[0117] If the PCF 404 determines a failure of the UE policy delivery procedure at operation 430, the PCF 404 may notify the failure along with a cause of the failure (e.g., UE is unreachable) as the outcome of the procedure to the NEF 407 by sending a Npcf EventExposure Notify notification (indicating the failure and the cause of the failure).

[0118] If the UAS authorization entity 408 has subscribed to the outcome of the UE policy delivery, the NEF 407 transmits a notification of the outcome of the UE policy delivery received from the PCF 404 to the UAS authorization entity 408. As shown, at operation 434, upon receiving the Npcf_EventExposure_Notify notification, the NEF 407 transmits a Nnef_ServiceParameter_Notify message to the UAS authorization entity 408. In an example, the NEF 407 may perform information mapping, for example, mapping an AF(USS / TPAE) transaction internal ID provided in a notification correlation ID to an AF(USS / TPAE) transaction ID and / or mapping a SUPI to a GPSI. That is, the NEF 407 may perform a reverse mapping to map 3 GPP UAV IDs to IDs known to the UAS authorization entity 408, and the Nnef ServiceParameter Notify message may include the GPSI, the external ID, or the PLMN ID (received as part of the NTZ information provisioning request at operation 418) depending on the target recipient of the UE policy delivery, the transaction reference ID (provided at operation 426), and the outcome of the UE policy delivery.

[0119] In some instances, the UAS authorization entity 408 may indicate a resource (e.g., identified by a uniform resource identifier (URI)) where the UAS authorization entity 408 may receive a subscribed notification. In an example, the UAS authorization entity 408 may include the indication of the resource as part of the subscription request included in the NTZ information provisioning request transmitted at operation 418.

[0120] In aspects, the UAS authorization entity 408 may optionally update the NTZ information at the core network 409 based on various conditions or changes. For instance, at operation 440, the UAS authorization entity 408 transmits, and the NEF 407 receives an update request to update the NTZ information at the core network 409. In an example, the UAS authorization entity 408 may invoke a Nnef NTZParameter Update request service operation along with the transaction reference ID provided to the UAS authorization entity 408 in Nnef_NTZParameter_Create response message (at operation 426). The Nnef NTZParameter Update request service operation may have input parameters, forexample, including but not limited to, NTZ update parameter(s), the transaction reference ID, and / or a result (e.g., success or failure) of the Nnef NTZParameter Update service operation.

[0121] At operation 442, upon receiving the update request, the NEF 407 stores the updated NTZ information at the UDR 406. For instance, the NEF 407 may search the UDR using the SUPI, the internal group ID, or the PLMN ID as a data key and update the corresponding NTZ information associated with the data key. As part of updating the NTZ information, the NEF 407 may interact with the UDM 405 to authorize the update request using similar mechanism as discussed above with reference to operations 420 and 422.

[0122] At operation 444, based on (e.g., in response to) the update of the NTZ information at the UDR 406, the UDR 406 transmits, and the PCF 404 receives, a notification of a data change at the UDR 406 due to the NTZ information update. In an example, the PCF 404 may receive a Nudr DM Notify notification from the UDR 406 as part of receiving the notification of the data change associated with the NTZ information update. Based on (e.g., in response to) the notification, the PCF 404 may trigger a UE policy update procedure as will be discussed below with reference to FIG. 5.

[0123] At operation 446, the NEF 407 transmits, and the UAS authorization entity 408 receives a response to the NTZ information update request. In an example, the NEF 407 may invoke a Nnef NTZParameter Update response service operation to provide the response to the UAS authorization entity 408. The Nnef NTZParameter Update response service operation may have one or more input parameters, for example, including but not limited to, the transaction reference ID and the update status (e.g., pass or fail).

[0124] In aspects, the UAS authorization entity 408 may optionally remove the NTZ information at the core network 409 based on various conditions or changes. For instance, at operation 450, the UAS authorization entity 408 transmits, and the NEF 407 receives a deletion request to delete the NTZ information from the core network 409. In an example, the UAS authorization entity 408 may invoke a Nnef NTZParameter Delete request service operation along with the transaction reference ID provided to the UAS authorization entity 408 in Nnef_NTZParameter_Create response message (at operation 426). The Nnef NTZParameter Delete request service operation may have one or more input parameters, for example, including but not limited to, the transaction reference ID.

[0125] At operation 452, upon receiving the deletion request, the NEF 407 deletes the NTZ information from the UDR 406. For instance, the NEF 407 may search the UDR using the SUPI, the internal group ID, or the PLMN ID as a data key and delete the corresponding NTZinformation associated with the data key from the UDR 406. As part of deleting the NTZ information, the NEF 407 may request the UDM 405 to remove the authorization of the service specific parameters (the NTZ information) provisioned by sending a Nudm ServiceSpecificAuthorisation Remove service operation.

[0126] At operation 454, based on (e.g., in response to) the deletion of the NTZ information from the UDR 406, the UDR 406 transmits, and the PCF 404 receives, a notification of a data change at the UDR 406 due to the NTZ information deletion. In an example, the PCF 404 may receive a Nudr DM Notify notification from the UDR 406 as part of receiving the notification of the data change associated with the NTZ information deletion. Based on (e.g., in response to) the notification, the PCF 404 may trigger a UE policy update procedure as will be discussed below with reference to FIG. 5.

[0127] At operation 456, the NEF 407 transmits, and the UAS authorization entity 408 receives a response to the NTZ information deletion request. In an example, the NEF 407 may invoke a Nnef NTZParameter Delete response service operation to provide the response to the UAS authorization entity 408. The Nnef NTZParameter Delete response service operation may have one or more input parameters, for example, including but not limited to, the transaction reference ID and / or the deletion status (e.g., pass or fail).

[0128] FIG. 4 is merely an example of signals and operations, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the signals and operations may include others not illustrated in FIG. 4. In embodiments, the signals and operations may not include every signal and operation illustrated in FIG. 4. In embodiments, the signals and operations may be implemented with different connections than those illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0129] FIG. 5 is a diagram of an example embodiment of operations for updating a UE configuration based on new NTZ information, according to one illustrated aspect of the present disclosure. It will be understood that a described signal may have associated operations and a described operation may have associated signals. Accordingly, a described signal may also involve an operation and a described operation may also involve a signal. Additionally, FIG. 5 will describe signals between and operations performed by various network components, such as those shown at the top of FIG. 5. Specifically, the components include the UE 401, the (R)AN 402, the AMF 403, and the PCF 404. The network components are illustrative, and it is contemplated that other components may be involved in the signals or may perform theoperations. One or more of the following operations may be implemented in connection with the operations of the present disclosure, such as the examples discussed above with reference to FIG. 4. For instance, the UE 401, the (R)AN 402, the AMF 403, and the PCF 404 may perform the operations shown in FIG. 5 as part of the operation 430 of FIG. 4.

[0130] The PCF 404 may generally provide policy control functionalities to UE(s) associated (or registered) with the core network 409. As an example, the PCF 404 may determine policy rules for the UE 401. The PCF 404 may partition a UE policy for the UE 401 into one or more policy sections (or policy containers), each including one or more policy rules for the UE 401. The PCF 404 may assign a policy section identifier (PSI) for each policy section. The PCF 404 may deliver the UE policy information to the UE 401, where the UE policy information may include the content (e.g., rule(s)) of each policy section and a respective PSI. The PCF 404 may maintain the latest list of PSIs delivered to the UE 401 and may update the latest list of PSIs in the UDR 406, for example, by invoking a Nudr DM Update (SUPI, policy data, policy set entry, updated PSI data) service operation. Upon receiving the UE policy at the UE 401, the UE 401 may store the PSI(s) and corresponding contents at the UE 401. Accordingly, the PSI(s) and the respective content(s) at the UE 401 are synchronized to the PSI(s) and the respective content(s) known to the PCF 404 and stored at the UDR 406. However, the PCF 404 can subsequently update the UE policy for the UE 401 based on changes in conditions and / or requirements (e.g., when new NTZ information is available).

[0131] At operation 510, the PCF 404 decides to update an A2X policy (e.g., a UE policy) due to new NTZ information available at the core network 409 (or more specifically at the UDR 406). The new NTZ information may be provisioned by the UAS authorization entity 408 external to the core network 409 as discussed above with reference to FIG. 4. The PCF 404 may determine to update the A2X policy based on various triggering conditions. In one example, a triggering condition may be when the UE 401 performs an initial registration with the core network 409. In another example, the core network 409 may be part of a 5GS (e.g., the 5GS 320), and the triggering condition may be when the UE 401 moves from an EPS (e.g., the EPS 330) to the 5GS. In a further example, a triggering condition may be based on a notification of a data change associated with the NTZ information stored at the UDR 406.

[0132] In the case of an initial registration or a 5GS registration (due to the UE 401 moving from the EPS to the 5GS), the PCF 404 may compare a list of policy PSI(s) included in A2X policy information provided in a Npcf UEPolicyControl Create request (received from the AMF 403) to the list of PSI(s) stored at the UDR 406. For instance, the UE 401 may transmita list of PSIs stored at the UE 401 via the AMF 403 as part of the registration, and the AMF 403 may include the list of PSI(s) stored at the UE 401 in the A2X policy information when transmitting the Npcf UEPolicyControl Create request to the PCF 404. In some instances, there may be no PSIs stored at the UE 401, and thus the A2X policy information in the Npcf UEPolicyControl Create request may not include any PSI (e.g., an empty PSI list). In an example, the new NTZ information may be stored in association with a new PSI at the UDR 406. Accordingly, the PCF 404 may determine to update the A2X policy information for the UE 401 based on the new PSI (for the NTZ information). The PCF 404 may deliver the A2X policy information including the NTZ information and the corresponding PSI to the UE 401 via the AMF 403. In an example, the AMF 403 may provide the updated A2X policy information to the UE 401 using a downlink (DL) non-access stratum, (NAS) transport message.

[0133] In the case of a network triggered UE policy update (e.g., due to a change of UE location), the PCF 404 may check the latest list of PSIs delivered to the UE 401 and stored at the UDR 406 to determine which A2X policies have to be transmitted to the UE 401. For instance, based on the UE 401’s new location, the PCF 404 may determine that a new PSI for a policy section including NTZ information is to be delivered to the UE 401.

[0134] At operation 512, if the PCF 404 has not subscribed to be notified by the AMF 403 about the UE 401 ’s response to an update of UE policy information, the PCF 404 subscribes to the AMF 403 to be notified about the UE 401 ’ s response to an update of UE policy information.

[0135] At operation 514, the PCF 404 transmits, and the AMF 403 receives UE policy information including the NTZ information. In an example, the PCF 404 may invoke a Namf_Communication_NlN2MessageTransfer service operation provided by the AMF 403 to initiate the delivery of the UE policy information to the UE 401. For instance, the Namf_Communication_NlN2MessageTransfer message may include a SUPI (identifying the UE 401) and a UE policy container (or more specifically a A2X policy container) including the NTZ information.

[0136] At operation 516, a network triggered service request may be performed by the AMF 403. For instance, if the UE 401 is registered and reachable by the AMF 403, the AMF 403 may transfer transparently the A2X policy container to the UE 401 via the registered access through the (R)AN 402. If, however, the UE 401 is not reachable by the AMF 403, the AMF 403 may initiate a network-initiated service request to cause the UE 401 to be reachable.

[0137] At operation 518, if the UE 401 is connected over a 3GPP access using connection management (CM), the AMF 403 may deliver or transfer transparently the A2X policy container (including UE policy information such as NTZ information) received from the PCF 404 to the UE 401. Upon receiving the A2X policy container, the UE 401 updates the A2X policy and corresponding NTZ information provided by the PCF 404. As will be discussed more fully below with reference to FIGS. 6A-6C, the UE 401 may adhere to the NTZ information (e.g., configured NTZ(s) and / band restriction(s)) and adapt the UE 401’s behavior accordingly.

[0138] At operation 520, the UE 401 transmits, and the AMF 403 receives the result of the A2X policy delivery. For instance, the UE 401 may transmit the A2X policy container including the result of the delivery to the AMF 403.

[0139] At operation 522, the AMF 403 forwards the response of the UE 401 to the PCF 404 using a Namf_Communication_NlMessageNotify notification.

[0140] Subsequently, the PCF 404 may maintain the latest list of PSIs delivered to the UE 401 and update the latest list of PSIs in the UDR 406 by invoking a Nudr DM Update (SUPI, policy data, policy set entry, updated PSI data) service operation.

[0141] FIG. 5 is merely an example of signals and operations, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the signals and operations may include others not illustrated in FIG. 5. In embodiments, the signals and operations may not include every signal and operation illustrated in FIG. 5. In embodiments, the signals and operations may be implemented with different connections than those illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0142] FIGS. 6A-6C illustrate example NTZ information for UAV communications, according to one illustrated aspect of the present disclosure. FIGS. 6A-6C are discussed in connection with FIG. 4. As shown in FIG. 6A, NTZ information 600 may include NTZ parameter fields 610, 620, and 630. In aspects, the NTZ information 600 may correspond to the NTZ information provided by the UAS authorization entity 408 at operation 418 of FIG. 4.

[0143] The NTZ parameter field 610 is related to geographical area information. For instance, the NTZ parameter field 610 may indicate a geographical area where the UE 401 is not to be served by a RAN (e.g., an EUTRA such as the (R)AN 306 of FIG. 3 or a NG-RAN such as the NG-RAN 304 of FIG. 3). As shown in FIG. 6B, the NTZ parameter field 610 may include a list of coordinates 612, each including an indication of a longitude, a latitude, and analtitude. The coordinate information may indicate boundaries of a geographical area or an airspace.

[0144] The NTZ parameter field 620 is related to radio parameters. For instance, the NTZ parameter field 620 may indicate radio parameters such as which frequency band(s) are allowed for transmission and / or which frequency band(s) are restricted for transmission by a UAV-UE (e.g., the UE 150, 302, and / or 401) in a certain geographical area specified by the NTZ parameter field 620. As shown in FIG. 6B, the NTZ parameter field 620 may include a flag value 622 (or parameter 622) indicating whether an NTZ is applicable in certain geography (e.g., the geographical area indicated by the NTZ parameter field 610). For instance, the flag value 622 may be set to a value of 1 to indicate the NTZ is applicable in the geographical area or set to a value of 0 to indicate the NTZ is not applicable in the geographical area, or vice versa. Additionally or alternatively, the NTZ parameter field 620 may include a list of transmission band(s) 624 (or parameter(s) 624) allowed or not allowed for a UAV-UE to perform transmission. Stated differently, the NTZ parameter field 620 may include frequency information for one or more allowed transmission bands and / or one or more restricted transmission bands. In some instances, the NTZ parameter field 620 may be optional.

[0145] The NTZ parameter field 630 may include information associated with a time period during which the NTZ is applicable in certain geography (e.g., the geographical area indicated by the NTZ parameter field 610). In an example, the NTZ parameter field 630 may include an indication of a starting time and / or an ending time (e.g., time of day) during which the NTZ may be applicable in the geographical area. As an example, the NTZ parameter field 630 may indicate 10:00-11 :00. As another example, the NTZ parameter field 630 may indicate 10:00-11 :00 and 00:00-06:00. In general, the NTZ parameter field 630 can indicate any suitable number of time periods (e.g., 1, 2, 3, 4 or more) during which the NTZ is applicable and / or using any suitable time formats. In some instances, the NTZ parameter field 630 may be optional.

[0146] In aspects, the UE 401 may receive the NTZ information 600 and adapt the UE 401 ’s behavior based on the NTZ information 600. To that end, the UE 401 may determine a current location of the UE 401, for example, based on a global navigation satellite system (GNSS) or a global positioning system (GPS) receiver at the UE 401. The UE 401 may check whether the UE 401 is inside or outside the geographical area indicated by the NTZ information 600, for example, based on a comparison of the UE 401’ s location against the list of coordinates 612 or based on a radial distance between the UE 401’s location and a single coordinate of thecoordinates 612. If the UE 401 is inside the NTZ geographical area, the UE 401 may check if all transmissions are barred (i.e., no allowable transmission band) or some bands are restricted. The UE 401 may perform or not perform transmission and / or cell search according to the NTZ information 600 while the UE 401 is inside the geographical area.

[0147] In aspects, the NTZ information 600 may include at least the NTZ parameter field 610 (indicating the geographical area) and may optionally include one or more of the parameters in the NTZ parameter fields 620 and / or 630. In a first example, the NTZ information 600 may include an indication of the geographical area (e.g., the list of coordinates 612) and exclude the flag value 622 and the list of allowed or not allowed band(s) 624. Such NTZ information 600 may indicate a total restriction on transmission (i.e., no allowable transmission band). Accordingly, the UE 401 may refrain (completely) from performing a cell search or transmitting in the geographical area. In other geographical areas (outside of the geographical area indicated by the NTZ parameter field 610), the UE 401 may perform transmission according to band information (e.g., in a A2X policy) provided to the UE 401. If the NTZ information 600 further includes the timing information (e.g., the NTZ parameter field 630), the UE 401 may refrain (completely) from performing a cell search or transmitting in the geographical area during the indicated time period.

[0148] In a second example, the NTZ information 600 may include an indication of the geographical area (e.g., the list of coordinates 612) and the flag value 622 and exclude the list of allowed or not allowed band(s) 624. If the flag value 622 indicates the NTZ is applicable, the UE 401 may refrain (completely) from performing a cell search or transmitting in the geographical area. If the NTZ information 600 further includes the timing information (e.g., the NTZ parameter field 630), the UE 401 may refrain (completely) from performing a cell search or transmitting in the geographical area during the indicated time period. If the flag value 622 indicates the NTZ is not applicable, the UE 401 may not restrict the UE 401 ’s transmission in the geographical area.

[0149] In a third example, the NTZ information 600 may include an indication of the geographical area (e.g., the list of coordinates 612) and the parameter 624 indicating restricted (not allowed) transmission band(s) and exclude the flag value 622. Based on such NTZ information 600, the UE 401 may refrain from performing a cell search or transmitting in any of the restricted transmission band(s) while the UE 401 is in the geographical area. Additionally or alternatively, the UE 401 may transmit a communication signal using a frequency band outside of the restricted transmission band(s). If the NTZ information 600 further includes thetiming information (e.g., the NTZ parameter field 630), the UE 401 may refrain from performing a cell search or transmitting in any of the restricted transmission band(s) and / or transmit the communication signal using a frequency band outside of the restricted transmission band(s) during the indicated time period.

[0150] In a fourth example, the NTZ information 600 may include an indication of the geographical area (e.g., the list of coordinates 612) and parameter 624 indicating allowed transmission band(s) and exclude the flag value 622. Based on such NTZ information 600, the UE 401 may transmit a communication signal using a frequency band of the allowed transmission band(s). Additionally or alternatively, the UE 401 may refrain from performing a cell search or transmitting in any band outside of the allowed transmission band(s). If the NTZ information 600 further includes the timing information (e.g., the NTZ parameter field 630), the UE 401 may transmit the communication signal using a frequency band of the allowed transmission band(s) and / or refrain from performing a cell search or transmitting in any band outside of the allowed transmission band(s) during the indicated time period.

[0151] In a fifth example, the NTZ information 600 may include an indication of the geographical area (e.g., the list of coordinates 612), the flag value 622, and the list of allowed or not allowed bands 624. If the flag value 622 indicates the NTZ is applicable, the band(s) in the parameter 624 are restricted transmission band(s) (not allowed for transmission). Accordingly, the UE 401 may refrain from performing a cell search, sidelink discovery / announcement or transmitting in any of the restricted transmission band(s) while the UE 401 is in the geographical area, where the refraining is based on the flag value 622 indicating the NTZ is applicable. Additionally or alternatively, the UE 401 may transmit a communication signal using a frequency band outside of the restricted transmission band(s). If the NTZ information 600 further includes the timing information (e.g., the NTZ parameter field 630), the UE 401 may refrain from performing a cell search or transmitting in any of the restricted transmission band(s) and / or transmit the communication signal using a frequency band outside of the restricted transmission band(s) during the indicated time period. If, however, the flag value 622 indicates the NTZ is not applicable, the band(s) in the parameter 624 are allowed transmission band(s). Accordingly, the UE 401 may transmit a communication signal using a frequency band of the allowed transmission band(s). Additionally or alternatively, the UE 401 may refrain from performing a cell search or transmitting in any band outside of the allowed transmission band(s). If the NTZ information 600 further includes the timing information (e.g., the NTZ parameter field 630), the UE 401 may transmit thecommunication signal using a frequency band of the allowed transmission band(s) and / or refrain from performing a cell search or transmitting in any band outside of the allowed transmission band(s) during the indicated time period.

[0152] In aspects, the UAS authorization entity 408 may not be aware of frequency bands that are used (or allowed) by the public land mobile network (PLMN) serving the UE 401. For instance, the PLMN may configure the UE 401 to use certain frequency bands for transmission. If the parameter 624 indicates allowed transmission band(s) (e.g., in the fourth example and the fifth example with the flag value 622 indicating the NTZ is not applicable discussed above), the core network 409, corresponding RAN, and the UE 401 may have to restrict the UE 401’s transmission to be in transmission bands that part of the allowed transmission bands indicated by the parameter 624 and part of the PLMN configured frequency bands.

[0153] Stated differently, the NTZ information 600 may coordinate information (e.g., the coordinates 612) indicative of a geographical area and optionally include one or more of the following: a flag value (e.g., the flag value 622) indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands (e.g., the parameter(s) 624), information associated with one or more restricted transmission bands (e.g., the parameter(s) 624), or information associated with a time period during which the NTZ is applicable (e.g., the timing information in the NTZ parameter field 630).

[0154] The NTZ information 600 of FIGS. 6A-6C is merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In general, the parameters in the NTZ information 600 can be arranged in any suitable order. Further, in some instances, the NTZ information 600 can indicate a plurality of geographical areas (e.g., 2, 3, 4 or more) and include radio parameter(s) and / or timing validity information for each of the geographical areas.

[0155] FIG. 7 is a flow diagram of example operations of a network apparatus provisioning NTZ information, according to one illustrated aspect of the present disclosure. In an aspect, the network apparatus may be an apparatus or network node of a UAS authorization entity such as the UAS authorization entity 408 discussed above with reference to FIG. 4. In some examples, the network apparatus may implement the operations using an apparatus with components as shown in FIG. 11. The operations of FIG. 7 may include similar mechanisms as discussed above with reference to FIGS. 1-5. As illustrated, FIG. 7 includes a number of enumerated steps, but aspects of the operations in FIG. 7 may include additional steps before, after, and inbetween the enumerated steps. In aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0156] At block 702, a network apparatus of a UAS authorization entity transmits an NTZ provisioning request to provision NTZ information to a core network, where the NTZ information is configured to be used by the core network to configure a UE policy for a UAV. In some instances, the UAS authorization entity may correspond to the UAS authorization entity 408, which may be a USS such as the USS 316 of FIG. 3 or a TPAE such as the TPAE 314 of FIG. 3. In some instances, the core network may correspond to the CN 210 of FIG. 2, the 5GC 310 of FIG. 3, and / or the core network 409 of FIG. 4. In some instances, the UAV may correspond to the UE 150 of FIG. 1, the UE 302 of FIG. 3, and / or the UE 401 of FIG. 4. In an example, the network apparatus may transmit the NTZ information provisioning request by invoking a Nnef_NTZParameter_Create request service operation provided by a NEF entity (e.g., the UAS NF 230, the UAS NF 308, and / or the NEF 407) of the core network.

[0157] In aspects, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable, for example, as discussed above with reference to FIGS. 6A-6C. In aspects, the UAS authorization entity may provision the NTZ information for an individual UE (e.g., a specific UAV-UE), a group of UEs (e.g., a category of UAV UEs), or a PLMN, and the UAV may correspond to the individual UE, the group of UEs, or all UEs (UAV UEs) served by the PLMN. For instance, if the NTZ information is provisioned for the group of UEs, the UAV is one of the UEs in the group. If the NTZ information is provisioned for the PLMN, the UAV is one of the UEs served by the PLMN.

[0158] At block 704, the network apparatus receives, based on (e.g., in response to) the transmitting the NTZ information provisioning request, a transaction reference ID. In an example, the network apparatus may receive the transaction reference ID via a Nnef NTZParameter Create response service operation provided by the NEF entity of the core network.

[0159] In aspects, the NTZ information provisioning request at block 702 further includes a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and the network apparatus further receives, basedon (e.g., in response to) the subscription, the notification of the outcome of the UE policy delivery. In an example, the network apparatus may receive the notification via a Nnef_ServiceParameter_Notify message from the NEF entity.

[0160] In aspects, the network apparatus further transmits an update request to update the NTZ information at the core network, where the update request includes the transaction reference ID obtained at block 704. In an example, the network apparatus may transmit the update request via a Nnef NTZParameter Update request service operation provided by the NEF entity.

[0161] In aspects, the network apparatus further transmits transmitting, by the network a deletion request to delete the NTZ information from the core network, where the deletion request includes the transaction reference ID obtained at block 704. In an example, the network apparatus may transmit the deletion request via a Nnef NTZParameter Delete request service operation provided by the NEF entity.

[0162] FIG. 8 is a flow diagram of example operations of a network apparatus facilitating provisioning NTZ information, according to one illustrated aspect of the present disclosure. In an aspect, the network apparatus may be an apparatus or network node of a NEF entity such as the UAS NF 230, the UAS NF 308, and / or the NEF 407 discussed above with reference to FIG. 2, FIG. 3, and / or FIG. 4, respectively. In some examples, the network apparatus may implement the operations using an apparatus with components as shown in FIG. 11. The operations of FIG. 8 may include similar mechanisms as discussed above with reference to FIGS. 1-5. As illustrated, FIG. 8 includes a number of enumerated steps, but aspects of the operations in FIG. 8 may include additional steps before, after, and in between the enumerated steps. In aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0163] At block 802, a network apparatus of a NEF entity associated with a core network from a UAS authorization entity, an NTZ information provisioning request to provision NTZ information to the core network, where the NTZ information is configured to be used by the core network to configure a UE policy for a UAV. In some instances, the NEF entity may correspond to the UAS NF 230 of FIG. 2, the UAS NF 308 of FIG. 3, and / or the NEF 407 of FIG. 4. In some instances, the core network may correspond to the CN 210 of FIG. 2, the 5GC 310 of FIG. 3, and / or the core network 409 of FIG. 4. In some instances, UAS authorization entity may correspond to the UAS authorization entity 408, which may be a USS such as the USS 316 of FIG. 3 or a TPAE such as the TPAE 314 of FIG. 3. In some instances, the UAV may correspond to the UE 150 of FIG. 1, the UE 302 of FIG. 3, and / or the UE 401 of FIG. 4.In an example, the network apparatus may receive the NTZ information provisioning request via a Nnef_NTZParameter_Create request service operation.

[0164] In aspects, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable, for example, as discussed above with reference to FIGS. 6A-6C. In aspects, the NTZ information may be provisioned for an individual UE (e.g., a specific UAV-UE), a group of UEs (e.g., a category of UAV UEs), or a PLMN, and the UAV may correspond to the individual UE, the group of UEs, or all UEs (UAV UEs) served by the PLMN. For instance, if the NTZ information is provisioned for the group of UEs, the UAV is one of the UEs in the group. If the NTZ information is provisioned for the PLMN, the UAV is one of the UEs served by the PLMN.

[0165] At block 804, the network apparatus transmits, to the UAS authorization entity based on (e.g., in response to) the receiving the NTZ information provisioning request, a transaction reference ID. In an example, the network apparatus may transmit the transaction reference ID via a Nnef NTZParameter Create response service operation.

[0166] In aspects, the NTZ information provisioning request at block 802 further includes a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and the network apparatus further transmits, to the UAS authorization entity based on (e.g., in response to) the subscription, the notification of the outcome of the UE policy delivery. In aspects, the network apparatus may receive, from a PCF entity of the core network, a PCF event notification message including the outcome of the UE policy delivery and the outcome transmitted to the UAS authorization entity may correspond to the outcome in the PCF event notification message.

[0167] In aspects, upon receiving the NTZ information at block 802, the network apparatus stores, at a UDR of the core network, the NTZ information in association with the UE policy. In aspects, the network apparatus further receives, from the UAS authorization entity, an update request to update the NTZ information, wherein the update request includes the transaction reference ID, and updates, based on the receiving the update request, the NTZ information stored at the UDR. In an example, the network apparatus may receive the update request via a Nnef NTZParameter Update request service operation.

[0168] In aspects, the network apparatus further receives, from the UAS authorization entity, a deletion request to delete the NTZ information, where the deletion request includes the transaction reference ID, and deletes, based on the receiving the deletion request, the NTZ information from the UDR. In an example, the network apparatus may receive the deletion request via a Nnef NTZParameter Delete request service operation.

[0169] FIG. 9 is a flow diagram of example operations of a network apparatus facilitating provisioning NTZ information, according to one illustrated aspect of the present disclosure. In an aspect, the network apparatus may be an apparatus or network node of a PCF entity such as the PCF 219 or the PCF 404 discussed above with reference to FIG. 2 or FIG. 4, respectively. In some examples, the network apparatus may implement the operations using an apparatus with components as shown in FIG. 11. The operations of FIG. 9 may include similar mechanisms as discussed above with reference to FIGS. 1-5. As illustrated, FIG. 9 includes a number of enumerated steps, but aspects of the operations in FIG. 9 may include additional steps before, after, and in between the enumerated steps. In aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0170] At block 902, a network apparatus of a PCF entity at a core network configures a UE policy (e.g., an A2X policy) for a UE (e.g., a UAV-UE) to perform aerial vehicle communication, where the configuring is based at least in part on NTZ information provisioned by a UAS authorization entity external to the core network. In some instances, the PCF entity may correspond to the PCF 219 of FIG. 2 and / or the PCF 404 of FIG. 4. In some instances, the core network may correspond to the CN 210 of FIG. 2, the 5GC 310 of FIG. 3, and / or the core network 409 of FIG. 4. In some instances, UAS authorization entity may correspond to the UAS authorization entity 408, which may be a USS such as the USS 316 of FIG. 3 or a TPAE such as the TPAE 314 of FIG. 3. In some instances, the UE may correspond to the UE 150 of FIG. 1, the UE 302 of FIG. 3, and / or the UE 401 of FIG. 4.

[0171] In aspects, the NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable, for example, as discussed above with reference to FIGS. 6A-6C. In aspects, the NTZ information may be provisioned for an individual UE (e.g., a specific UAV-UE), a group of UEs (e.g., a category of UAV UEs), or a PLMN, and the UE may correspond to the individual UE, the group of UEs,or all UEs (UAV UEs) served by the PLMN. For instance, if the NTZ information is provisioned for the group of UEs, the UAV is one of the UEs in the group. If the NTZ information is provisioned for the PLMN, the UAV is one of the UEs served by the PLMN.

[0172] At block 904, the network apparatus transmits, to the UE (e.g., via an AMF entity of the network such as the AMF 212 of FIG. 2 or the AMF 403 of FIGS. 4-5), the UE policy including the NTZ information.

[0173] At block 906, the network apparatus receives, from the UE (e.g., via the AMF entity), a response to the UE policy.

[0174] At block 908, the network apparatus transmits, to a NEF entity associated with the core network, a notification of the response to the UE policy.

[0175] In aspects, the network apparatus further receives a notification of a data change associated with the NTZ information from a UDR entity of the core network, where the configuring the UE policy is based on the data change associated with the NTZ information. In some instances, the UDR entity may correspond to the UDR 224 of FIG. 2 or the UDR 406 of FIG. 4.

[0176] FIG. 10 is a flow diagram of example operations of a UE receiving an NTZ information update, according to one illustrated aspect of the present disclosure. In an aspect, the UE may correspond to the UE 150, the UE 302, or the UE 401 discussed above with reference to FIGS. 1-2, 3, or 4-5, respectively. In some examples, the UE may implement the operations using an apparatus with components as shown in FIG. 11. The operations of FIG. 10 may include similar mechanisms as discussed above with reference to FIGS. 1-5. As illustrated, FIG. 10 includes a number of enumerated steps, but aspects of the operations in FIG. 10 may include additional steps before, after, and in between the enumerated steps. In aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0177] At block 1002, a UE receives, from a core network, a UE policy for aerial vehicle communication, the UE policy including NTZ information.

[0178] At block 1004, the UE receives, from the core network, an updated UE policy including updated NTZ information.

[0179] At block 1006, the UE transmits, to the core network, a response to the reception of the updated UE policy.

[0180] In aspects, the updated NTZ information includes at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowedtransmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable, for example, as discussed above with reference to FIGS. 6A-6C. In aspects, the UE further refrains from performing a cell search or transmitting in the geographical area. In aspects, the refraining from performing a cell search or transmitting in the geographical area is further based on the flag value. In aspects, as part of the refraining, the UE refrains from performing a cell search or transmitting in the geographical area UE during the time period which the NTZ is applicable. In aspects, as part of the refraining, the UE refrains from performing a cell search or transmitting in any one of the restricted transmission bands (while the UE is in the geographical area).. In aspects, the UE further transmits, by the UE, a communication signal using a frequency band outside of the one or more restricted transmission bands. In aspects, the UE further transmits a communication signal using a frequency band in the one or more allowed transmission bands (while the UE is in the geographical area).

[0181] Referring now to FIG. 11, there is shown a block diagram of example components of a UE or a network apparatus. The apparatus includes an electronic storage 1110, a processor 1120, a memory 1150, and a network interface 1140. The various components may be communicatively coupled with each other. The processor 1120 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 1150 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 1150 includes processor-readable instructions that are executable by the processor 1120 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations of FIGS. 4-5 and 7-10.

[0182] The electronic storage 1110 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, and / or optical disc, among other types of electronic storage. The electronic storage 1110 stores processor-readable instructions for causing the apparatus to perform its operations and stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 1140 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[0183] The components shown in FIG. 11 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may includemultiples of any of the illustrated components. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0184] In general, the various operations of methods described herein may be performed by any suitable means (e.g., the processor 1120 and the memory 1150) capable of performing the corresponding operations. The means may include various hardware and / or software component s) and / or module(s), including, but not limited to the components of FIG. 11.

[0185] Further embodiments of the present disclosure include the following examples.

[0186] Example 1.1. A method comprising: transmitting, by a network apparatus of an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and receiving, by the network apparatus, based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

[0187] Example 1.2. The method of Example 1.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the method further comprises: receiving, by the network apparatus based on the subscription, the notification of the outcome of the UE policy delivery.

[0188] Example 1.3. The method of Example 1.2, further comprising: transmitting, by the network apparatus, an update request to update the NTZ information at the core network, wherein the update request comprises the transaction reference ID.

[0189] Example 1.4. The method of any one of Examples 1. 1-1.3, further comprising: transmitting, by the network apparatus, a deletion request to delete the NTZ information from the core network, wherein the deletion request comprises the transaction reference ID.

[0190] Example 1.5. The method of any one of Examples 1. 1-1.4, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in geographical area,information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or. information associated with a time period during which the NTZ is applicable.

[0191] Example 1.6. The method of any one of Examples 1. 1-1.5, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0192] Example 2.1. A method comprising: receiving, by a network apparatus of a network exposure function (NEF) entity associated with a core network from an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to the core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and transmitting, by the network apparatus to the UAS authorization entity based on the receiving the NTZ information provisioning request, a transaction reference identifier (ID).

[0193] Example 2.2. The method of Example 2.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the method further comprises: transmitting, by the network apparatus to the UAS authorization entity based on the subscription, the notification of the outcome of the UE policy delivery.

[0194] Example 2.3. The method of Example 2.1 or Example 2.2, further comprising: receiving, by the network apparatus from a policy control function (PCF) entity of the core network, a PCF event notification message comprising the outcome of the UE policy delivery.

[0195] Example 2.4. The method of any one of Example 2.1-2.3, further comprising: storing, at a unified data repository (UDR) of the core network, the NTZ information in association with the UE policy.

[0196] Example 2.5. The method of Example 2.4, further comprising: receiving, by the network apparatus from the UAS authorization entity, an update request to update the NTZ information, wherein the update request comprises the transaction reference ID; andupdating, based on the receiving the update request, the NTZ information stored at theUDR.

[0197] Example 2.6. The method of Example 2.4, further comprising: receiving, by the network apparatus from the UAS authorization entity, a deletion request to delete the NTZ information, wherein the deletion request comprises the transaction reference ID; and deleting, based on the receiving the deletion request, the NTZ information from the UDR.

[0198] Example 2.7. The method of any one of Examples 2.1-2.6, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0199] Example 2.8. The method of any one of Examples 2.1-2.7, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0200] Example 3.1. A method comprising: configuring, by a network apparatus at a core network, a user equipment (UE) policy for a UE to perform aerial vehicle communication, wherein the configuring is based at least in part on no-transmission zone (NTZ) information provisioned by an uncrewed aerial system (UAS) authorization entity external to the core network; transmitting, by the network apparatus to the UE, the UE policy comprising the NTZ information; receiving, by the network apparatus from the UE, a response to the UE policy; and transmitting, by the network apparatus to a network exposure function (NEF) entity associated with the core network, a notification of the response to the UE policy.

[0201] Example 3.2. The method of Example 3.1, further comprising: receiving, by the network apparatus from a unified data repository (UDR) entity of the core network, a notification of a data change associated with the NTZ information,wherein the configuring the UE policy is based on the data change associated with the NTZ information.

[0202] Example 3.3. The method of Example 3.1 or Example 3.2, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0203] Example 3.4. The method of any one of Examples 3.1-3.3, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0204] Example 3.5. The method of any one of Examples 3.2-3.19, wherein the network apparatus comprises a policy control function (PCF) entity of the core network.

[0205] Example 4.1. A method comprising: receiving, by a user equipment (UE) from a core network, a UE policy for aerial vehicle communication, the UE policy comprising no-transmission zone (NTZ) information; receiving, by the UE from the core network, an updated UE policy comprising updated NTZ information; and transmitting, by the UE to the core network, a response to the reception of the updated UE policy.

[0206] Example 4.2. The method of Example 4.1, wherein the updated NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, or information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0207] Example 4.3. The method of Example 4.2, further comprising: refraining, by the UE, from performing a cell search or transmitting in the geographical.

[0208] Example 4.4. The method of Example 4.3, wherein the refraining from performing a cell search or transmitting in the geographical area is further based on the flag value.

[0209] Example 4.5. The method of any of Example 4.3 or Example 4.4, wherein the refraining from performing a cell search or transmitting in the geographical area comprises: refraining, by the UE, from performing a cell search or transmitting in any of the one or more restricted transmission bands.

[0210] Example 4.6. The method of any one of Examples 4.3-4.5, wherein the refraining from performing a cell search or transmitting in the geographical area comprises: refraining, by the UE during the time period which the NTZ is applicable, from performing a cell search or transmitting in the geographical area.

[0211] Example 4.7. The method of any one of Examples 4.2-4.6, further comprising: transmitting, by the UE, a communication signal using a frequency band outside of the one or more restricted transmission bands.

[0212] Example 4.8. The method of Example 4.7, wherein the transmitting the communication signal comprises: transmitting, by the UE during the time period which the NTZ is applicable, the communication signal using the frequency band outside of the one or more restricted transmission bands.

[0213] Example 4.9. The method of any one of Examples 4.2-4.8, further comprising: transmitting, by the UE, a communication signal using a frequency band in the one or more allowed transmission bands.

[0214] Example 4.10. The method of Example 4.9, wherein the transmitting the communication signal comprises: transmitting, by the UE during the time period which the NTZ is applicable, the communication signal using the frequency band in the one or more allowed transmission bands.

[0215] Example 5.1. An apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform:transmitting, by a network apparatus of an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and receiving, by the network apparatus, based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

[0216] Example 5.2. The apparatus of Example 5.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the apparatus further comprises: receiving, by the network apparatus based on the subscription, the notification of the outcome of the UE policy delivery.

[0217] Example 5.3. The apparatus of Example 5.2, further comprising: transmitting, by the network apparatus, an update request to update the NTZ information at the core network, wherein the update request comprises the transaction reference ID.

[0218] Example 5.4. The apparatus of any one of Examples 5. 1-5.3, further comprising: transmitting, by the network apparatus, a deletion request to delete the NTZ information from the core network, wherein the deletion request comprises the transaction reference ID.

[0219] Example 5.5. The apparatus of any one of Examples 5. 1-5.4, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or. information associated with a time period during which the NTZ is applicable.

[0220] Example 5.6. The apparatus of any one of Examples 5. 1-5.5, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0221] Example 6.1. An apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform: receiving, from an uncrewed aerial system (UAS) authorization entity, a notransmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the apparatus is associated with a network exposure function (NEF) entity associated with the core network, and wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and transmitting, to the UAS authorization entity based on the receiving the NTZ information provisioning request, a transaction reference identifier (ID).

[0222] Example 6.2. The apparatus of Example 6.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the apparatus further comprises: transmitting, to the UAS authorization entity based on the subscription, the notification of the outcome of the UE policy delivery.

[0223] Example 6.3. The apparatus of Example 6. 1 or Example 6.2, further comprising: receiving, from a policy control function (PCF) entity of the core network, a PCF event notification message comprising the outcome of the UE policy delivery.

[0224] Example 6.4. The apparatus of any one of Example 6. 1-6.3, further comprising: storing, at a unified data repository (UDR) of the core network, the NTZ information in association with the UE policy.

[0225] Example 6.5. The apparatus of Example 6.4, further comprising: receiving, from the UAS authorization entity, an update request to update the NTZ information, wherein the update request comprises the transaction reference ID; and updating, based on the receiving the update request, the NTZ information stored at the UDR.

[0226] Example 6.6. The apparatus of Example 6.4, further comprising: receiving, from the UAS authorization entity, a deletion request to delete the NTZ information, wherein the deletion request comprises the transaction reference ID; anddeleting, based on the receiving the deletion request, the NTZ information from theUDR.

[0227] Example 6.7. The apparatus of any one of Examples 6. 1-6.6, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0228] Example 6.8. The apparatus of any one of Examples 6. 1-6.7, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0229] Example 7.1. An apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform: configuring a user equipment (UE) policy for a UE to perform aerial vehicle communication, wherein the configuring is based at least in part on no-transmission zone (NTZ) information provisioned by an uncrewed aerial system (UAS) authorization entity external to a core network, wherein the apparatus is at the core network; transmitting, to the UE, the UE policy comprising the NTZ information; receiving, from the UE, a response to the UE policy; and transmitting, to a network exposure function (NEF) entity associated with the core network, a notification of the response to the UE policy.

[0230] Example 7.2. The apparatus of Example 7.1, further comprising: receiving, from a unified data repository (UDR) entity of the core network, a notification of a data change associated with the NTZ information, wherein the configuring the UE policy is based on the data change associated with the NTZ information.

[0231] Example 7.3. The apparatus of Example 7. 1 or Example 7.2, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area,a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0232] Example 7.4. The apparatus of any one of Examples 7. 1-7.3, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0233] Example 7.5. The apparatus of any one of Examples 7.2-7.19, wherein the apparatus comprises a policy control function (PCF) entity of the core network.

[0234] Example 8. 1. A user equipment comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform: receiving, from a core network, a UE policy for aerial vehicle communication, the UE policy comprising no-transmission zone (NTZ) information; receiving, from the core network, an updated UE policy comprising updated NTZ information; and transmitting, to the core network, a response to the reception of the updated UE policy.

[0235] Example 8.2. The apparatus of Example 8.1, wherein the updated NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, or information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0236] Example 8.3. The apparatus of Example 8.2, further comprising: refraining, by the UE, from performing a cell search or transmitting in the geographical.

[0237] Example 8.4. The apparatus of Example 8.3, wherein the refraining from performing a cell search or transmitting in the geographical area is further based on the flag value.

[0238] Example 8.5. The apparatus of any ofExample 8.3 or Example 8.4, wherein the refraining from performing a cell search or transmitting in the geographical area comprises: refraining, by the UE, from performing a cell search or transmitting in any of the one or more restricted transmission bands.

[0239] Example 8.6. The apparatus of any one of Examples 8.3-8.5, wherein the refraining from performing a cell search or transmitting in the geographical area comprises: refraining, during the time period which the NTZ is applicable, from performing a cell search or transmitting in the geographical area.

[0240] Example 8.7. The apparatus of any one of Examples 8.2-8.6, further comprising: transmitting, by the UE, a communication signal using a frequency band outside of the one or more restricted transmission bands.

[0241] Example 8.8. The apparatus of Example 8.7, wherein the transmitting the communication signal comprises: transmitting, during the time period which the NTZ is applicable, the communication signal using the frequency band outside of the one or more restricted transmission bands.

[0242] Example 8.9. The apparatus of any one of Examples 8.2-8.8, further comprising: transmitting, by the UE, a communication signal using a frequency band in the one or more allowed transmission bands.

[0243] Example 8.10. The apparatus of Example 8.9, wherein the transmitting the communication signal comprises: transmitting, during the time period which the NTZ is applicable, the communication signal using the frequency band in the one or more allowed transmission bands.

[0244] Example 9.1. An apparatus comprising: means for transmitting, by a network apparatus of an uncrewed aerial system (UAS) authorization entity, a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); andmeans for receiving, by the network apparatus, based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

[0245] Example 9.2. The apparatus of Example 9.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the apparatus further comprises: receiving, based on the subscription, the notification of the outcome of the UE policy delivery.

[0246] Example 9.3. The apparatus of Example 9.2, further comprising: means for transmitting, by the network apparatus, an update request to update the NTZ information at the core network, wherein the update request comprises the transaction reference ID.

[0247] Example 9.4. The apparatus of any one of Examples 9. 1-9.3, further comprising: means for transmitting, by the network apparatus, a deletion request to delete the NTZ information from the core network, wherein the deletion request comprises the transaction reference ID.

[0248] Example 9.9. The apparatus of any one of Examples 9. 1-9.4, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or. information associated with a time period during which the NTZ is applicable.

[0249] Example 9.6. The apparatus of any one of Examples 9. 1-9.5, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0250] Example 10.1. An apparatus comprising: means for receiving, from an uncrewed aerial system (UAS) authorization entity, a notransmission zone (NTZ) information provisioning request to provision NTZ information to the core network, wherein the apparatus is associated with a network exposure function (NEF)entity associated with the core network, and wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and means for transmitting, to the UAS authorization entity based on the receiving the NTZ information provisioning request, a transaction reference identifier (ID).

[0251] Example 10.2. The apparatus of Example 10.1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the apparatus further comprises: transmitting, to the UAS authorization entity based on the subscription, the notification of the outcome of the UE policy delivery.

[0252] Example 10.3. The apparatus of Example 10.1 or Example 10.2, further comprising: means for receiving, from a policy control function (PCF) entity of the core network, a PCF event notification message comprising the outcome of the UE policy delivery.

[0253] Example 10.4. The apparatus of any one of Example 10.1-10.3, further comprising: means for storing, at a unified data repository (UDR) of the core network, the NTZ information in association with the UE policy.

[0254] Example 10.5. The apparatus of Example 10.4, further comprising: means for receiving, from the UAS authorization entity, an update request to update the NTZ information, wherein the update request comprises the transaction reference ID; and means for updating, based on the receiving the update request, the NTZ information stored at the UDR.

[0255] Example 10.6. The apparatus of Example 10.4, further comprising: means for receiving, from the UAS authorization entity, a deletion request to delete the NTZ information, wherein the deletion request comprises the transaction reference ID; and means for deleting, based on the receiving the deletion request, the NTZ information from the UDR.

[0256] Example 10.7. The apparatus of any one of Examples 10.1-10.6, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area,a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0257] Example 10.8. The apparatus of any one of Examples 10.1-10.7, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0258] Example 11.1. An apparatus comprising: means for configuring, by a network apparatus at a core network, a user equipment (UE) policy for a UE to perform aerial vehicle communication, wherein the configuring is based at least in part on no-transmission zone (NTZ) information provisioned by an uncrewed aerial system (UAS) authorization entity external to the core network; means for transmitting, to the UE, the UE policy comprising the NTZ information; means for receiving, from the UE, a response to the UE policy; and means for transmitting, to a network exposure function (NEF) entity associated with the core network, a notification of the response to the UE policy.

[0259] Example 11.2. The apparatus of Example 11.1, further comprising: means for receiving, from a unified data repository (UDR) entity of the core network, a notification of a data change associated with the NTZ information, wherein the configuring the UE policy is based on the data change associated with the NTZ information.

[0260] Example 11.3. The apparatus of Example 11.1 or Example 11.2, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0261] Example 11.4. The apparatus of any one of Examples 11.1-11.3, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

[0262] Example 11.5. The apparatus of any one of Examples 11.2-11.19, wherein the network apparatus comprises a policy control function (PCF) entity of the core network.

[0263] Example 12. 1. A user equipment comprising: means for receiving, from a core network, a UE policy for aerial vehicle communication, the UE policy comprising no-transmission zone (NTZ) information; means for receiving, from the core network, an updated UE policy comprising updated NTZ information; and means for transmitting, to the core network, a response to the reception of the updated UE policy.

[0264] Example 12.2. The apparatus of Example 12.1, wherein the updated NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, or information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

[0265] Example 12.3. The apparatus of Example 12.2, further comprising: means for refraining, by the UE, from performing a cell search or transmitting in the geographical.

[0266] Example 12.4. The apparatus of Example 12.3, wherein the means for refraining from performing a cell search or transmitting in the geographical area is further based on the flag value.

[0267] Example 12.5. The apparatus of any ofExample 12.3 or Example 12.4, wherein the means for refraining from performing a cell search or transmitting in the geographical area comprises: means for refraining, by the UE, from performing a cell search or transmitting in any of the one or more restricted transmission bands.

[0268] Example 12.6. The apparatus of any one of Examples 12.3-12.5, wherein the means for refraining from performing a cell search or transmitting in the geographical area comprises: means for refraining, during the time period which the NTZ is applicable, from performing a cell search or transmitting in the geographical area.

[0269] Example 12.7. The apparatus of any one of Examples 12.2-12.6, further comprising: means for transmitting, by the UE, a communication signal using a frequency band outside of the one or more restricted transmission bands.

[0270] Example 12.8. The apparatus of Example 12.7, wherein the means for transmitting the communication signal comprises: means for transmitting, during the time period which the NTZ is applicable, the communication signal using the frequency band outside of the one or more restricted transmission bands.

[0271] Example 12.9. The apparatus of any one of Examples 12.2-12.8, further comprising: means for transmitting, by the UE, a communication signal using a frequency band in the one or more allowed transmission bands.

[0272] Example 12.10. The apparatus of Example 12.9, wherein the transmitting the communication signal comprises: means for transmitting, during the time period which the NTZ is applicable, the communication signal using the frequency band in the one or more allowed transmission bands.

[0273] Example 13. A non-transitory processor-readable medium including program code, which when executed by one or more processors, causes the one or more processors at least to perform the method of any one of Examples 1.1-1.6.

[0274] Example 14. A non-transitory processor-readable medium including program code, which when executed by one or more processors, causes the one or more processors at least to perform the method of any one of Examples 2.1-2.8.

[0275] Example 15. A non-transitory processor-readable medium including program code, which when executed by one or more processors, causes the one or more processors at least to perform the method of any one of Examples 3.1-3.5.

[0276] Example 16. A non-transitory processor-readable medium including program code, which when executed by one or more processors, causes the one or more processors at least to perform the method of any one of Examples 4.1-4.10.

[0277] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may becombined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0278] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0279] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) .”

[0280] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0281] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely asexemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

CLAIMS:

1. A method of an uncrewed aerial system (UAS) authorization entity, the method comprising: transmitting a no-transmission zone (NTZ) information provisioning request to provision NTZ information to a core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and receiving based on the transmitting the NTZ information provisioning request, a transaction reference identifier (ID).

2. The method as claimed in claim 1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the method further comprises: receiving, based on the subscription, the notification of the outcome of the delivery of the UE policy.

3. The method as claimed in claim 2, further comprising: transmitting an update request to update the NTZ information at the core network, wherein the update request comprises the transaction reference ID.

4. The method as claimed in any one of claims 1 to 3, further comprising: transmitting a deletion request to delete the NTZ information from the core network, wherein the deletion request comprises the transaction reference ID.

5. The method as claimed in any one of claims 1 to 4, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, orinformation associated with a time period during which the NTZ is applicable.

6. The method as claimed in any one of claims 1 to 5, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

7. A method of a network exposure function (NEF) entity associated with a core network, the method comprising: receiving, from an uncrewed aerial system (UAS) authorization entity, a notransmission zone (NTZ) information provisioning request to provision NTZ information to the core network, wherein the NTZ information is configured to be used by the core network to configure a user equipment (UE) policy for an uncrewed aerial vehicle (UAV); and transmitting, to the UAS authorization entity, based on the receiving the NTZ information provisioning request, a transaction reference identifier (ID).

8. The method as claimed in claim 7, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of an outcome of a delivery of the UE policy that is configured based on the NTZ information, and wherein the method further comprises: transmitting, to the UAS authorization entity, based on the subscription, the notification of the outcome of the delivery of the UE policy.

9. The method as claimed in claim 7 or claim 8, further comprising: receiving, from a policy control function (PCF) entity of the core network, a PCF event notification message comprising the outcome of the delivery of the UE policy.

10. The method as claimed in any one of claims 7 to 9, further comprising: causing storing, at a unified data repository (UDR) of the core network, of the NTZ information in association with the UE policy.

11. The method as claimed in claim 10, further comprising: receiving, from the UAS authorization entity, an update request to update the NTZ information, wherein the update request comprises the transaction reference ID; and updating, based on the receiving the update request, the NTZ information stored at the UDR.

12. The method as claimed in claim 10, further comprising: receiving, from the UAS authorization entity, a deletion request to delete the NTZ information, wherein the deletion request comprises the transaction reference ID; and causing deleting, based on the receiving the deletion request, of the NTZ information from the UDR.

13. The method as claimed in any one of claims 7 to 12, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

14. The method as claimed in any one of claims 7 to 13, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

15. A method of a network apparatus of a core network, the method comprising: configuring a user equipment (UE) policy for a UE to perform aerial vehicle communication, wherein the configuring is based at least in part on no-transmission zone (NTZ) information provisioned by an uncrewed aerial system (UAS) authorization entity external to the core network; transmitting, to the UE, the UE policy comprising the NTZ information; receiving, from the UE, a response to the UE policy; andtransmitting, to a network exposure function (NEF) entity associated with the core network, a notification of the response to the UE policy.

16. The method as claimed in claim 15, further comprising: receiving, from a unified data repository (UDR) entity of the core network, a notification of a data change associated with the NTZ information, wherein the configuring the UE policy is based on the data change associated with the NTZ information.

17. The method as claimed in claim 15 or claim 16, wherein the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

18. The method as claimed in any one of claims 15 to 17, wherein the NTZ information is provisioned for an individual UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to the individual UE, the group of UEs, or UEs served by the PLMN.

19. The method as claimed in any one of claims 15 to 18, wherein the network apparatus comprises a policy control function (PCF) entity of the core network.

20. A method of a UE for an uncrewed aerial vehicle (UAV), the method comprising: receiving, from a core network, a UE policy for aerial vehicle communication, the UE policy for aerial vehicle communication comprising no-transmission zone (NTZ) information regarding a NTZ in which cell search or transmission is allowed or not allowed to be performed by the UE; receiving, from the core network, an updated UE policy comprising an update of the NTZ information; and transmitting, to the core network, a response to the reception of the updated UE policy.

21. The method as claimed in claim 20, wherein the update of the NTZ information comprises at least one of the following: coordinate information indicative of a geographical area, a flag value indicating whether an NTZ is applicable in the geographical area, information associated with one or more allowed transmission bands, information associated with one or more restricted transmission bands, or information associated with a time period during which the NTZ is applicable.

22. The method as claimed in claim 21, further comprising: refraining from performing a cell search or transmitting in the geographical area based on the update of the NTZ information.

23. The method as claimed in claim 22, wherein the update of the NTZ information comprises the flag value, wherein the refraining from the performing the cell search or the transmitting in the geographical area is based on the flag value.

24. The method as claimed in any of claim 22 or claim 23, wherein the refraining from the performing the cell search or the transmitting in the geographical area comprises: refraining from performing the cell search or the transmitting in the geographical area in any of the one or more restricted transmission bands.

25. The method as claimed in any one of claims 22 to 24, wherein the refraining from the performing the cell search or the transmitting in the geographical area comprises: refraining, during the time period in which the NTZ is applicable, from the performing the cell search or the transmitting in the geographical area.

26. The method as claimed in any one of claims 21 to 25, further comprising: transmitting, based on the update of the NTZ information, a communication signal using a frequency band outside of the one or more restricted transmission bands.

27. The method as claimed in claim 26, wherein the transmitting the communication signal using the frequency band outside of the one or more restricted transmission bands comprises: transmitting during the time period in which the NTZ is applicable, the communication signal using the frequency band outside of the one or more restricted transmission bands.

28. The method as claimed in any one of claims 21 to 27, further comprising: transmitting, based on the update of the NTZ information, a communication signal using a frequency band in the one or more allowed transmission bands.

29. The method as claimed in claim 28, wherein the transmitting the communication signal using the frequency band in the one or more allowed transmission bands comprises: transmitting, during the time period in which the NTZ is applicable, the communication signal using the frequency band in the one or more allowed transmission bands.

30. An uncrewed aerial system (UAS) authorization entity comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the UAS authorization entity at least to perform the method as claimed in any one of claims 1 to 6.

31. As network exposure function (NEF) entity for a core network, the apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the NEF entity at least to perform the method as claimed in any one of claims 7 to 14.

32. An apparatus for a core network, the apparatus comprising: at least one processor; and at least one memory storing instructions which, when executed by the processor, cause the apparatus at least to perform the method as claimed in any one of claims 15 to 19.

33. A user equipment (UE) for an uncrewed aerial vehicle (UAV), the UE comprising: at least one processor; andat least one memory storing instructions which, when executed by the processor, cause the UE at least to perform the method as claimed in any one of claims 20 to 29.

Images