Third party provisioning for non-transmission zone and band limitation for aircraft

Abstract

A method includes transmitting, by a network device of an unmanned aerial system (UAS) authorization entity, a non-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 unmanned aerial vehicle (UAV); and receiving, by the network device, a transaction reference identifier (ID) based on the transmission NTZ information provisioning request.

Description

Technical Field

[0001] Various example embodiments generally relate to wireless networks, and more specifically, to equipping aircraft with non-transmission zone (NTZ) and / or frequency band restrictions. Background Technology

[0002] Wireless networks offer significant advantages to user mobility. The ability to remain connected while on the move not only provides an advantage for users but also enhances efficiency and productivity for society as a whole. As user expectations become more demanding, such as for aircraft communications and aircraft-to-everything (A2X) services, the technologies used in wireless networks must keep pace. Therefore, continuous focus on improving wireless network technologies is essential. Summary of the Invention

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

[0004] According to various aspects of this disclosure, one method includes: a network device of an Unmanned Aircraft System (UAS) Authorized Entity transmitting a Non-Transmission Zone (NTZ) Information Configuration Request to configure NTZ Information to a core network, wherein the NTZ Information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aircraft (UAV); and the network device receiving a Transaction Reference Identifier (ID) based on the transmitted NTZ Information Configuration Request.

[0005] In one aspect of the method, the NTZ information provision request further includes a request for notification of the result of delivery of a UE policy configured based on the NTZ information for subscription, and the method further includes notification of the result of receiving the UE policy delivery by a network device based on the subscription.

[0006] In one aspect of the method, the method further includes transmitting an update request from the network device to update NTZ information at the core network, wherein the update request includes a transaction reference ID.

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

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

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

[0010] According to various aspects of this disclosure, a method includes: a network device of a Network Open Functions (NEF) entity associated with a core network receiving a Non-Transmission Zone (NTZ) information provision request from an Unmanned Aircraft System (UAS) Authorized Entity to provision NTZ information to the core network, wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for unmanned aircraft (UAVs); and the network device transmitting a Transaction Reference Identifier (ID) to the UAS Authorized Entity based on the received NTZ information provision request.

[0011] In one aspect of the method, the NTZ information provision request further includes a request for notification of the result of delivery of a UE policy configured based on the NTZ information for subscription, and the method further includes notification by the network device, based on the subscription, of the result of delivery of the UE policy to the UAS authorizing entity.

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

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

[0014] In one aspect of the method, the method further includes receiving an update request from a UAS authorizing entity by a network device to update NTZ information, wherein the update request includes a transaction reference ID; and updating the NTZ information stored at a UDR based on the received update request.

[0015] In one aspect of the method, the method further includes: receiving a deletion request from a UAS Authorized Entity to delete NTZ information by a network device, wherein the deletion request includes a Transaction Reference ID; and deleting the NTZ information from the UDR based on the receipt of the deletion request.

[0016] In one aspect of the method, the NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to the geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies.

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

[0018] According to various aspects of this disclosure, a method includes: configuring a user equipment (UE) policy for performing aircraft communications by a network device at the core network, wherein the policy is based at least in part on non-transmission zone (NTZ) information provided by an unmanned aerial system (UAS) authorized entity outside the core network; transmitting the UE policy, including the NTZ information, to the UE by the network device; receiving a response to the UE policy from the UE by the network device; and transmitting a notification of the response to the UE policy to a Network Open Function (NEF) entity associated with the core network by the network device.

[0019] In one aspect of the method, the method further includes receiving, by the network device, a notification of data changes associated with NTZ information from a unified data repository (UDR) entity in the core network, wherein UE policies are configured based on the data changes associated with the NTZ information.

[0020] In one aspect of the method, the NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to the geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies.

[0021] In one aspect of the method, NTZ information is provided for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

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

[0023] According to various aspects of this disclosure, in Example 20, a method includes: a user equipment (UE) receiving a UE policy for aircraft communications from a core network, the UE policy including non-transmission zone (NTZ) information; the UE receiving an updated UE policy including the updated NTZ information from the core network; and the UE transmitting a response to the core network in response to receiving the updated UE policy.

[0024] In one aspect of the method, the updated NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to the geographic area, information associated with one or more permitted transmission bands, or information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies.

[0025] In one aspect of the method, the method also includes the UE avoiding performing cell search or transmission in the geographical area.

[0026] One aspect of this method is that avoiding cell searches or transmissions in that geographic area is also based on this flag value.

[0027] In one aspect of the method, avoiding cell search or transmission in the geographical area includes the UE avoiding performing cell search or transmission in any transmission band within the one or more restricted transmission bands.

[0028] In one aspect of the method, avoiding cell search or transmission in the geographic area includes the UE avoiding cell search or transmission in the geographic area during the time period to which the NTZ applies.

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

[0030] In one aspect of the method, transmitting communication signals includes the UE transmitting communication signals using one or more frequency bands outside of the restricted transmission frequency bands during the time period in which the NTZ applies.

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

[0032] In one aspect of the method, transmitting communication signals includes the UE transmitting communication signals using frequency bands in one or more permitted transmission frequency bands during the time period in which the NTZ applies.

[0033] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

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

[0035] Figure 1 This is a diagram of an example embodiment of a wireless network between a network system and a user equipment (UE) according to an illustrative aspect of this disclosure; Figure 2 This is a diagram illustrating an example component of a network system according to an aspect of this disclosure; Figure 3 This is a diagram of an example network system providing services to unmanned aerial vehicles (UAVs) according to one aspect of this disclosure; Figure 4This is a diagram illustrating an example embodiment of operation for equipping non-transfer zone (NTZ) information according to one aspect of this disclosure; Figure 5 This is a diagram illustrating an example embodiment of an operation for updating UE configuration based on NTZ information, according to one aspect of this disclosure; Figures 6A to 6C The illustration shows an example NTZ information for UAV communication according to one aspect of this disclosure; Figure 7 This is a flowchart illustrating an example operation of a network device equipped with NTZ information according to one aspect of this disclosure; Figure 8 This is a flowchart illustrating an example operation of a network device equipped with NTZ information according to one aspect of this disclosure; Figure 9 This is a flowchart illustrating an example operation of a network device equipped with NTZ information according to one aspect of this disclosure; Figure 10 This is a flowchart illustrating an example operation of a UE receiving NTZ information updates according to one aspect of this disclosure; and Figure 11 This is a diagram illustrating an example embodiment of a component of a UE or network device according to one aspect of this disclosure. Detailed Implementation

[0036] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the art will recognize that the aspects can be practiced without one or more of these specific details or using 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 the description of the aspects.

[0037] Throughout this specification, the reference to "an aspect" or "aspect" means that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Therefore, the phrases "in an aspect" or "in one respect" appearing in various places throughout this specification do not necessarily refer to the same aspect. Furthermore, a particular feature, structure, or characteristic may be combined in one or more aspects in any suitable manner.

[0038] The embodiments described in this disclosure can be implemented in wireless network devices, such as, but not limited to, devices utilizing Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advanced, 6G (and beyond), and 802.11ax (Wi-Fi 6), and other wireless network systems. The term "eLTE" here refers to LTE evolution connected to a 5G core. LTE is also referred to as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0039] An unmanned 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 unmanned aerial system (UAS) may include one or more UAVs and one or more UAV controllers. Additionally, a UAS may communicate with an unmanned aerial system traffic management (UTM) system. A UTM system can integrate flying UAVs (multiple UAVs) with other airspace users. For example, a UTM system may provide a set of functions and services for managing a range of autonomous vehicle operations, such as certifying UAVs, authorizing UAS services, managing UAS policies, and controlling UAV traffic in the airspace.

[0040] UAS Network Functions (UAS NFs) are 3GPP (3rd Generation Partnership Project) network functions that provide services to UAVs, including authentication, flight authorization, tracking, and communications quality control. UAS Service Providers (USS) can support safe airspace use by providing services to UAS operators to meet UTM (Unified Management Module) requirements. Third-Party Authorized Entities (TPAEs) (e.g., ground control towers) can also play a role in UAS management, for example, for UAV traffic control.

[0041] In this disclosure, a UAV may include a mobile communication device capable of communicating with a wireless communication system, such as a 3GPP system (e.g., a 5G system (5GS)). The terms “UAV,” “aviation communication device,” “aircraft,” “aviation UE,” and “UAV-UE” are used interchangeably herein, such that a description referring to one of these terms should be considered as referring to the other terms as well. Furthermore, in some instances, UAV-UE may be simply referred to as UE.

[0042] In some scenarios, for spectrum compatibility purposes, it may be desirable to restrict the transmission of aeronautical communication devices (e.g., UAVs) in certain geographic areas and / or in certain frequency bands. For example, the European Conference on Postal and Telecommunications Regulation (CEPT) Decision 22 (07) outlines the technical conditions for the use of aeronautical UEs in several LTE and 5G NR bands that are harmonized for the purpose of harmonizing mobile / fixed communication networks (MFCNs), and specifically addresses operational restrictions on aeronautical UEs in the form of non-transmission zones (NTZs). According to CEPT, an NTZ is a geographic area in which aeronautical UEs are not permitted to transmit in a given MFCN band or a portion thereof for spectrum compatibility purposes. In addition to the harmonized technical conditions for MFCN bands, further definition of spectrum operational restrictions is required. For example, at the national level, NTZs may be defined for aeronautical UEs in relevant bands to ensure spectrum compliance. In some cases, it may also be necessary for the operation of aeronautical UEs to comply with relevant cross-border harmonization agreements. In one example, the LTE and 5G NR bands in 703-733 MHz, 832-862 MHz, 880-915 MHz, 1710-1785 MHz, 1920-1980 MHz, and 2500-2570 MHz, as well as the MFCN coordinated band in 2570-2620 MHz, can be considered the NTZ of an aeronautical UE. Typically, NTZ can refer to a total restriction on transmission (i.e., no permissible transmission band) or a restriction on transmission to one or more specific bands.

[0043] Given the existence of NTZs (defined by CEPT) and certain frequency bands (defined at the national level) that prohibit aviation UEs from transmitting, mechanisms are needed to ensure that aviation UEs comply with these NTZ and / or frequency band restrictions.

[0044] 3GPP Release 19 (Rel-19) introduces Enhanced Network Open Function (NEF) services to support Mobile Network Operator (MNO)-UTM data services. NEF services securely expose 3GPP core network capabilities to third parties and / or non-3GPP entities. These NEF services can assist in, but are not limited to, intelligent flight planning, monitoring, interfacing with UTM infrastructure (e.g., including multiple USSs), and Quality of Experience (QoE) estimation using 5GS. In one example, (multiple) enhanced NEF services can provide additional information to the UAV operator (or USS) to perform pre-flight preparation and in-flight operations (e.g., flight mission request, flight path recommendation, flight monitoring, and control). In another example, (multiple) enhanced NEF services can support enhanced UAV flight and / or route management based on network capacity and Quality of Service (QoS) information along the planned route. There are also recommendations from aviation industry organizations such as the GSMA and the Joint Activities for Aviation Connectivity (ACJA) to enhance service exposure to further support aviation operations.

[0045] Therefore, it may be expected that MNOs will use cellular networks as a reliable communications backbone for the aviation vertical to provide (multiple) service exposures to the aviation industry (e.g., UAS operators, UTMs, command and control connectivity service providers (C2CSPs), etc.), for example, supporting different air zones with different UAV settings and / or communication QoS.

[0046] One approach to configuring NTZ information for a UAV-UE is via an Aircraft-to-Everything (A2X) policy. For this purpose, the A2X policy can provide the UAV-UE with configuration parameters for A2X communication via a PC5 reference point (e.g., for sidelink communication) and / or via a Uu reference point (e.g., for direct communication). However, currently, 5GS does not allow A2X policies to be configured by external entities (non-3GPP entities). Furthermore, A2X policies are not currently stored in the 5GS's Unified Data Repository (UDR) but are manually configured at the 5GS's Policy Control Function (PCF) entity. Manual configuration may be unsuitable for configuring NTZ information at the 5GS because operators may not have prior knowledge of the NTZ information. Additionally, in some cases, it may be desirable to dynamically configure (or update) NTZ information based on changes in conditions (e.g., changes in conditions and / or requirements).

[0047] The terms “A2X strategy” and “UE strategy” are used interchangeably in this document, such that a description that refers to one of these terms should be regarded as referring to the other terms as well.

[0048] This disclosure provides techniques for a core network (e.g., a 5G core (5GC)) to control and manage UAV communications within NTZ and / or band-restricted areas along the UAV's flight path (e.g., pre-mission flight path and / or upcoming flight path). For example, a NEF entity associated with the core network can provide service operations (e.g., an application programming interface (API) for an external entity to equip the core network with NTZ information and store the equipped NTZ information at the UDR of the core network). A PCF entity at the core network can utilize the NTZ information stored at the UDR to configure (multiple) NTZ and / or (multiple) band restrictions for the UAV-UE. In this way, the UAV-UE can comply with the configured (multiple) NTZ and / or (multiple) band restrictions and adapt its behavior accordingly. For example, in one aspect, when the UAV-UE is in an NTZ, it can avoid performing cell search or transmission. In another aspect, when the UE is in an NTZ, the UAV-UE can transmit communication signals using frequency bands outside the restricted (multiple) transmission bands.

[0049] As used herein, the term "network function" can be a software instance executing on hardware (e.g., a network device) or a virtualized function instantiated on hardware. Furthermore, the terms "service operation" and "API" are used interchangeably herein, such that a description referring to one of these terms should be considered as referring to the other terms as well.

[0050] According to one aspect of this disclosure, a UAS Authorized Entity outside the core network can transmit an NTZ information provision request to a NEF entity within the core network to provision NTZ information to the core network. In some examples, the UAS Authorized Entity may be a USS or TPAE. The NTZ information can be configured by the core network to configure UE policies (e.g., A2X policies) for UAVs (UAV-UEs). The NTZ information may include at least one of the following: coordinate information indicating a geographic area (or airspace) (e.g., a list of coordinates including longitude, latitude, and / or altitude information), a flag value indicating whether the NTZ applies to the geographic area, frequency information associated with one or more permitted transmission bands, frequency information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies. In some instances, the geographic area may be along the UAV's pre-mission flight path. In other instances, the geographic area may be along the UAV's upcoming flight path. In all aspects, NTZ information can be provisioned for a single UE, a group of UEs (e.g., a class of UEs), or a Public Land Mobile Network (PLMN), and the UAV may correspond to a single UE, a group of UEs, or all UEs served by the PLMN. UAS authorized entities can receive transaction reference identifiers (IDs) based on transmissions (e.g., in response to) NTZ information.

[0051] The transaction reference ID can be included in multiple subsequent requests related to the NTZ information. For example, the UAS authorized entity can also transmit an update request to the NEF entity to update the NTZ information at the core network, and the transaction reference ID can be included in the update request. Additionally or alternatively, the UAS authorized entity can also transmit a deletion request to the NEF entity to delete the NTZ information from the core network, and the transaction reference ID can be included in the deletion request.

[0052] In various aspects, the NTZ information provisioning request may also include a request for notification of the delivery results of a subscribed UE policy (which is configured based on NTZ information). Based on (e.g., in response to) the subscription, the UAS authorizing entity may receive notification of the results of UE policy delivery. In an example, the result may indicate successful delivery of the UE policy to the UAV. Alternatively, the result may indicate a failure in the delivery of the UE policy and may also provide the reason for the failure (e.g., the UAV is unreachable).

[0053] In each aspect, when a NEF entity receives an NTZ information configuration request from a UAS authorized entity, the NEF entity can store the NTZ information at a UDR in the core network. In the example, the UDR can provide an API for installing or storing NTZ information at the UDR. In each aspect, when a NEF entity receives an update request from a UAS authorized entity, the NEF entity can update the NTZ information at the UDR. In the example, the UDR can provide an API for modifying the NTZ information stored at the UDR. In each aspect, when a NEF entity receives a deletion request from a UAS authorized entity, the NEF entity can delete the NTZ information from the UDR. In the example, the UDR can provide an API for removing NTZ information from the UDR.

[0054] In various aspects, the NEF entity can subscribe to multiple events of the PCF entity in the core network. For example, the NEF entity can subscribe to the delivery results of a UE policy (configured based on NTZ information and equipped by a UAS authorized entity outside the core network). Based on (e.g., in response to) the NEF entity's subscription, the NEF entity can receive PCF event notification messages from the PCF entity, including an indication of the UE policy delivery results. As mentioned above, an NTZ information equipment request (from the UAS authorized entity) can include a subscription to the UE policy delivery results associated with the NTZ information. Therefore, the NEF entity can also transmit the UE policy delivery results to the UAS authorized entity.

[0055] In various aspects, the PCF entity can subscribe to be notified of data changes associated with NTZ information at the UDR. Therefore, the PCF entity can receive notifications of data changes associated with NTZ information (equipped by the UAS Authorization Entity and stored at the UDR) from the UDR. Upon receiving such a notification, the PCF entity can configure UE policies for the UAV based on the NTZ information. Thus, the PCF entity can configure or generate UE policies for the UAV based on the NTZ information stored at the UDR. The PCF entity can transmit UE policies to the UAV (e.g., via the Access and Mobility Management (AMF) entity of the core network) and receive responses from the corresponding UAV (e.g., via the AMF). If the NEF entity (of the core network) has subscribed to event notifications at the PCF entity, the PCF entity can transmit the UAV's response to the NEF entity.

[0056] According to another aspect of this disclosure, a UE (e.g., a UAV) can receive a UE policy (e.g., an A2X policy) for aircraft communications from a core network, wherein the UE policy may include NTZ information. The UE can receive an updated UE policy from the core network, including (dynamically) updated NTZ information. The UE can transmit a response to the core network regarding the receipt of the updated UE policy. For example, the response may indicate successful reception of the UE policy. In various aspects, the updated NTZ information may include at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to a geographic area, frequency information associated with one or more permitted transmission bands, frequency information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies. In various aspects, the UE can avoid performing cell searches or transmissions in a geographic area. In various aspects, the avoidance of performing cell searches or transmissions in a geographic area may also be based on a flag value. In various aspects, as part of the avoidance, the UE can avoid performing cell searches or transmissions in a geographic area during the time period to which the NTZ applies. In all aspects, as part of the avoidance, when the UE is in a geographic area, the UE can avoid performing cell search or transmission in any of the restricted transmission frequency bands. In all aspects, when the UE is in a geographic area, the UE can use frequency bands outside of one or more restricted transmission frequency bands to transmit communication signals. In all aspects, when the UE is in a geographic area, the UE can use frequency bands in one or more permitted transmission frequency bands to transmit communication signals. These and other aspects will be described in more detail later in this document.

[0057] Various aspects of this disclosure can provide several benefits. For example, adding a NEF to provide service operations for external entities (e.g., USS, TPAE) to interface with the core network (e.g., 5GC) to equip, update, and / or delete NTZ information can enable the core network to control and manage the NTZ and band limits for each geographic area to meet spectrum compliance regulations or requirements for aircraft. While this disclosure is discussed in the context of enabling 3GPP 5GC to control and manage the NTZ and band limits for each geographic area used for UAV communications, various aspects of this disclosure are applicable to any suitable type of wireless communication system.

[0058] This disclosure may use the term "serving network device" to refer to a network node or network device (or part thereof) serving a UE. As used herein, the terms "transmit to," "receive from," and "cooperate with" (and variations thereof) include communication that may or may not involve communication through one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes acquiring in a first instance or re-acquiring after a first instance. The term "connection" may mean a physical connection or a logical connection.

[0059] This disclosure uses 5G NR as an example of a wireless network, and may use smartphones and / or unmanned aerial vehicles as examples of UEs. It is intended and should be understood that such examples are merely illustrative, and this disclosure applies to other wireless networks and user equipment.

[0060] Figure 1 This is a diagram illustrating an example of a wireless network 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 devices 130 (e.g., test devices). Network node 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 server 110, network node 120, network device 130, any of the foregoing components(s), and / or any other components(s) of the network system 100. Examples of network apparatuses include, but are not limited to, apparatuses for implementing various aspects of 5G NR. This disclosure describes embodiments related to 5G NR and embodiments relating to aspects defined by 3GPP. However, it is contemplated that embodiments related to other wireless network technologies are included within the scope of this disclosure.

[0061] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, a node that provides NR user plane and control plane protocol termination toward the UE and is connected to the 5G core (5GC) via an NG interface, such as, according to Section 3.2 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0062] gNB supports various protocol layers, such as Layer 1 (L1) physical layer, Layer 2 (L2) and Layer 3 (L3).

[0063] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which, for example: The physical layer provides a transmission channel to the MAC sublayer; The MAC sublayer provides logical channels to the RLC sublayer; The RLC sublayer provides RLC channels to the PDCP sublayer; The PDCP sublayer provides radio bearers to the SDAP sublayer; The SDAP sublayer provides QoS flows to 5GC; The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0064] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) according to Section 6 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0065] The gNB Central Unit (gNB-CU) comprises, for example, logical nodes that host, the gNB's RRC, Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols, or the en-gNB's RRC and PDCP protocols, and controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates at the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0066] A gNB Distributed Unit (gNB-DU) comprises, for example, a logical node that hosts the RLC, Media Access Control (MAC), and Physical (PHY) layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates at the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0067] As used herein, the term "network node" may refer to any one or any combination of gNB, gNB-CU, or gNB-DU. RAN (Radio Access Network) nodes or network nodes (such as, for example, gNB, gNB-CU, or gNB-DU, or portions thereof) may be implemented using means, for example, having at least one processor and / or at least one memory having processor-readable instructions ("program") configured to support and / or be equipped with and / or process CU and / or DU-related functionalities and / or features, and / or at least one protocol (sub)layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network). Different functional divisions between central and distributed units are possible. The following will combine... Figure 11 Examples to describe such devices and components.

[0068] The gNB-CU and gNB-DU portions can be co-located or physically separated, for example. The gNB-DU can even be further divided into, for example, two parts, one including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud RAN / Virtual RAN (BBU / REC / C-RAN / V-RAN), Open RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Headend / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various exemplary embodiments of this disclosure, a network node supporting at least one of the Central Unit functions or Layer 3 protocols of the radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Distributed Unit functions or Layer 2 protocols of the radio access network can be, for example, a gNB-DU.

[0069] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support serving cells for user equipment (UE), or candidate cells for handover, dual connectivity and / or carrier aggregation and other procedures.

[0070] UE 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, Internet of Things (IoT) devices, machine-to-machine (M2M) devices or UAVs, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to enable the device to perform at least certain operations, such as, for example, an RRC connection to the RAN. Figure 9 Examples of components of the UE are described below. In an embodiment, UE 150 may be configured to generate messages (e.g., including a cell ID) to be transmitted to the RAN via radio (e.g., to reach and communicate with the serving cell). In an embodiment, UE 150 may generate, transmit, and receive RRC messages containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0071] Continue to refer to Figure 1 In an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cells. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In embodiments, network node 120 may be referred to as a base station.

[0072] Figure 1 Examples are provided, and only network system 100 and UE 150 are illustrated. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user equipment can communicate with network system 100.

[0073] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below should also be applicable to other types of network systems. The network system can be configured according to... Figure 1The signals and connections shown operate to enable UE 150 to communicate with network system 100 via RAN 225. Furthermore, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein and can refer to instructions executed by and implemented by one or more processors.

[0074] The following describes example functionality of the components. This example functionality is merely illustrative, and it should be understood that additional operations and functions can be performed by the components described herein. Furthermore, connections between components can be virtual connections based on service interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" for any other component acting as a service "consumer," providing services for network functions.

[0075] For example, a control network (CN) 210 is described in the control plane of the network system. CN 210 includes Authentication Server Function (AUSF) 211, AMF 212, and Session Management Function (SMF) 213. CN 210 also includes Network Slice Selection Function (NSSF) 214, NEF 215, Network Repository Function (NRF) 216, and UDM 217, which may include UDR 224.

[0076] The additional components and functions of CN 210 include application function (AF) 218 ​​and PCF 219.

[0077] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted over the RAN 225. For example, the DN 227 identifies services from service providers, internet access, and third-party services.

[0078] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs PDU session management and manages session context with UPF 226.

[0079] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Auxiliary Information (NSSAI). This selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create private network services. NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

[0080] UDM 217 generates authentication vectors for use by AUSF 211 and AMF 212 and provides user identity processing. UDM 217 can be connected to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, as well as provide QoS and accounting functions. In some instances, UDM 217 and / or UDR 224 may be referred to as network data components.

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

[0082] According to various aspects of this disclosure, the UAS NF 230 can communicate with components of the CN 210 (e.g., UDM 217, UDR 224, PCF 219, and AMF 212) to enable third parties and / or non-3GPP entities to equip the CN 210 with NTZ parameters (e.g., NTZ and restricted frequency bands for each geographic area) to configure UE policies (e.g., A2X policies) for the UAV-UE. The mechanisms for enabling the core network to control and manage the NTZ parameters used for UAV communication will be discussed more fully below.

[0083] Figure 2 These are merely examples of components of a network system, and variations are contemplated within the scope of this disclosure. In embodiments, the network system may include... Figure 2 Other components not shown. In embodiments, the network system may not include... Figure 2 Each component is shown. In embodiments, components and connections can utilize [the following]. Figure 2The connections shown are implemented using different connections. These and other embodiments are considered to be within the scope of this disclosure.

[0084] Figure 3 This is a block diagram of an example network system providing services to UAVs according to one aspect of this disclosure. Figure 3 As shown, the network system includes UE 302, 5GS 320, and Evolved Packet System (EPS) 330. UE 302 can be a UAV as described above. UE 302 can perform communication by accessing 5GS 320 and / or EPS 330. In one example, UE 302 can be a 5G UE and can perform communication by accessing 5GS 320. In another example, UE 302 can be an LTE UE and can perform communication by accessing EPS 330. In yet another example, UE 302 can be a dual-connectivity UE and can perform communication by accessing 5GS 320 and EPS 330 (e.g., switching between 5GS 320 and EPS 330).

[0085] The 5GS 320 may include NG RAN 304 and 5GC 310. In one example, NG RAN 304 may correspond to RAN225, and 5GC 310 may include network components, such as those referenced above. Figure 2 The components of UPF 226 and CN 210 are discussed. In the context of 3GPP, NG RAN 304 can communicate with 5GC 310 via the N3 interface.

[0086] EPS 330 may include a (Radio) Access Network ((R)AN) 306 and an Evolved Packet Core (EPC) 312. (R)AN 306 may include a combination of... Figure 1 The network nodes, network components, and / or base stations described. In one example, (R)AN 306 could be EUTRAN. EPC 312 can perform the same operations as referenced above. Figure 2 The CN 210 and UPF 226 discussed are essentially similar in operation. However, the EPC 312 can be compared with... Figure 2 The network system shown has different divisions of core network functions, and may include functions similar to those of other networks. Figure 2 The components shown are different from those in the standard EPC 312. Generally, EPC 312 may include components configured to manage session state, authenticate and track UE 302 across EPS 330, and route data packets via (R)AN 306. In the context of 3GPP, (R)AN 306 can communicate with EPC 312 via the S1 interface.

[0087] like Figure 3As further illustrated, the network system includes a UAS NF 308, which is the NEF associated with the 5GC 310. The UAS NF 308 can communicate with various components of the 5GC 310. In the context of 3GPP, the UAS NF 308 can communicate with the 5GC 310 via interfaces N29, N30, N51, N15, and N36. The UAS NF 308 can perform network functions that expose the services or capabilities of the 5GC 310 to the USS 316 in DN 318. In the context of 3GPP, the UAS NF 308 can communicate with the USS 316 via the N33 interface. In this example, the UAS NF 308 and DN 318 can respectively correspond to... Figure 2 The UAS NF230 and DN 227. USS 316 can support secure airspace use by providing services to UAS operators to meet UTM requirements. Figure 3 In the example shown, UAS NF 308 and USS 316 are outside of 5GS 320. However, in some instances, UAS NF 308 and / or USS 316 may be part of 5GS 320. Additionally or alternatively, UAS NF 308 may operate as a Service Capability Exposure Function (SCEF) to communicate with various components of EPC 312 and perform network functions to expose the services or capabilities of EPC 312 to USS 316.

[0088] like Figure 3 As further shown, TPAE 314 can communicate with 5GS 320 and EPS 330 via DN 318. TPAE 314 can function in UAS management, for example, for UAV traffic control. In the context of 3GPP, TPAE 314 can communicate with 5GC 310 via the N6 interface and with EPC 312 via the SGi interface.

[0089] According to various aspects of this disclosure, UAS NF 308 can provide services to USS 316 and / or TPAE 314 to equip 5GC 310 (or EPC 312) with NTZ information, dynamically update the NTZ information stored at 5GC 310, and / or delete NTZ information from 5GC 310 (or EPC 312). The NTZ information can indicate NTZ and / or frequency band restrictions for each geographic area, for example, to meet certain spectrum compliance requirements. The NTZ information can be configured by 5GC 310 (or EPC 312) to configure UE policies for UE 302 (UAV), enabling UE 302 to avoid transmission in those NTZ and / or restricted frequency bands.

[0090] Figure 3These are merely examples of components of a network system, and variations are contemplated within the scope of this disclosure. In embodiments, the network system may include... Figure 3 Other components not shown. In embodiments, the network system may not include... Figure 3 Each component is shown. In embodiments, components and connections can utilize [the following]. Figure 3 The connections shown are implemented using different connections. These and other embodiments are considered to be within the scope of this disclosure.

[0091] The following describes an example operation for NTZ information provisioning. Figure 4 Example signals and operations for NTZ information are shown. Figure 5 Example signals and operations for updating UE configuration based on NTZ information are shown. Figures 6A to 6C Example NTZ information is shown. Figure 7 Example operation of a network device of a UAS authorized entity such as USS or TPAE is shown. Figure 8 Example operation of a network device of a UAS NF entity is shown. Figure 9 Example operation of a network device of a PCF entity is shown. Figure 10 Example operation of a UE (e.g., UAV-UE) is shown.

[0092] Figure 4 This is a diagram illustrating an example embodiment of operation for equipping NTZ information according to one aspect of this disclosure. It should be understood that the described signals may have associated operations, and the described operations may have associated signals. Therefore, the described signals may also relate to operations, and the described operations may also relate to signals. Additionally, Figure 4 This will describe the signals between various network components and the operations performed by these components, such as... Figure 4 Those shown at the top. Specifically, the components include UE 401, (R)AN 402, AMF 403, PCF 404, UDM 405, UDR 406, NEF 407, and UAS Authorized Entity 408. UE 401 can be a UAV as described above, and can be similar to... Figure 1 UE 150 and / or Figure 3 UE302. AMF 403, PCF 404, UDM 405, and UDR 406 can be similar to Figure 2 CN 210 and / or Figure 3 It is part of the 5GC 310 core network 409. For example, AMF 403, PCF 404, UDM 405, and UDR 406 can be similar to... Figure 2AMF 212, PCF 219, UDM 217, and UDR 224. (R)AN 402 can be similar to... Figure 2 RAN 225 and / or Figure 3 NGRAN 304. NEF 407 can be similar to Figure 2 UAS NF 230 and / or Figure 3 UAS NF 308. UAS authorized entity 408 can be similar to Figure 3 The USS 316 or TPAE 314. Network components are illustrative, and other components are envisioned to involve signals or perform operations. In some examples, each network component in the network assembly may use components with, for example, […]. Figure 11 The apparatus of the components shown is used to implement the operation. One or more of the following operations can be implemented in conjunction with the operations of this disclosure, as referenced above. Figures 1 to 3 Examples of discussion.

[0093] At operation 410, UE 401 can perform a UE registration procedure with core network 409 via (R)AN 402. At operation 412, as part of the UE registration procedure, AMF 403 can interact with PCF 404 to perform policy association. For example, PCF 404 can provide AMF 403 with access and mobility management related policies to trigger policy rules for UE 401. At operation 414, PCF 404 can transmit, and UDR 406 can receive, a subscription to a notification of data changes at UDR 406. In the example, PCF 404 can invoke the Nudr_DM_subscribe service operation provided by UDR 406 as part of the transmission subscription. Those skilled in the art will understand the Nudr_DM_subscribe service operation.

[0094] At operation 416, UAS Authorization Entity 408 can create an AF request to equip the core network 409 with NTZ information. The NTZ information can be configured by the core network 409 to configure UE policies for UAV communication (e.g., at least for UE 401). See below for reference. Figures 6A to 6CMore comprehensively, NTZ information may include indications of the NTZ and / or restricted transmission bands for each geographic area. At operation 418, as part of creating an AF request, UAS Authorization Entity 408 may transmit an NTZ information configuration request, and NEF 407 may receive the NTZ information configuration request. In one example, UAS Authorization Entity 408 may invoke the Nnef_NTZParameter_Create request service operation provided by NEF 407 as part of transmitting the NTZ information configuration request. The Nnef_NTZParameter_Create request service operation may have input parameters, such as, but not limited to, NTZ parameters, an indication of the time period to which the NTZ parameters may be applied or valid (i.e., no transmission restrictions may be time-limited), a target identifier to which the NTZ parameters are to be configured, and / or subscription parameters. In some instances, the indication of the time period may be included as part of the NTZ parameters.

[0095] In various respects, the UAS Authorization Entity 408 may be interested in reports regarding whether UE policies configured with NTZ information have been successfully delivered to the corresponding UE. Therefore, the UAS Authorization Entity 408 may include a request to subscribe to notifications of the results of UE policy delivery (e.g., A2X policy delivery) in the NTZ information provision request.

[0096] In various aspects, the UAS Authorized Entity 408 may configure NTZ information at the individual UE level (e.g., specifically for UE 401), at the UE group level (e.g., for a group of UEs including UE 401), or at the PLMN level (e.g., for all UEs including UE 401 in the PLMN). Accordingly, the NTZ information configuration request may include a target ID identifying the individual UE, UE group, or PLMN for which NTZ information is to be configured. For example, if configuring NTZ information for a single UE, the NTZ information configuration request may include a target UE ID containing a Common Public Subscription Identifier (GPSI). If configuring NTZ information for a group of UEs, the NTZ information configuration request may include a target UE ID containing an external group ID. If configuring NTZ information for a PLMN, the NTZ information configuration request may include the PLMN ID.

[0097] At operation 420, upon receiving an NTZ information configuration request, NEF 407 can interact with UDM 405 to obtain information for performing identifier mapping. In the example, NEF 407 can invoke the Nudm_SDM_Get service operation provided by UDM 405 to request information from UDM 405. Those skilled in the art will understand the Nudm_SDM_Get request service operation. For example, if the NTZ information configuration request includes a target UE ID for a single UE, NEF 407 can map the GPSI in the target ID to a Subscription Permanent Identifier (SUPI) based on the information received from UDM 405. The SUPI is an ID assigned by the 3GPP system. Alternatively, if the NTZ information configuration request includes target UE IDs for a group of UEs, NEF 407 can map the external group ID in the target UE ID to an internal group ID based on the information received from UDM 405. Generally, a UAS-UE (e.g., UE401) can be identified by the UAS Authorized Entity 408 using a Civil Aviation Administration (CAA) level ID (e.g., GPSI, External Group ID) and by the 3GPP system (e.g., Core Network 409) using a 3GPP UAV ID (e.g., SUPI or Internal Group ID). Those skilled in the art will understand the Nudm_SDM_Get service operation.

[0098] At operation 422, NEF 407 can interact with UDM 405 to authorize a service-specific parameter configuration request with UDM 405. More specifically, NEF 407 can interact with UDM 405 to authorize an NTZ information configuration request (received from UAS Authorization Entity 408). In the example, NEF 407 can invoke the Nudm_ServiceSpecificAuthorization_Create service operation provided by UDM 405 as part of the authorization. Those skilled in the art will understand the Nudm_ServiceSpecificAuthorization_Create service operation.

[0099] At operation 424, upon successful authorization of the NTZ information provisioning request, NEF 407 stores the NTZ information at UDR 406. NEF 407 can store the NTZ information in UDR 406 in association with SUPI (when the NTZ information is used for a single UE), External Group ID (when the NTZ information is used for a group of UEs), or PLMN ID (when the NTZ information is used for all UEs in the PLMN). For example, as part of storing the NTZ information, a UDR data element named "Dataset" can be set to "UE Policy Set (UEPolicySet)," and a UDR data element named "Data Subset" can be set to "A2X NTZ Info (A2XNTZ Info)," and UDR 406 can store the NTZ information and assign a transaction reference ID to the storage of the NTZ information. Typically, UDR 406 can use any suitable data structure to store the NTZ information.

[0100] In operation 426, NEF 407 transmits, and UAS Authorization Entity 408 receives a response to the NTZ information provisioning request. In one example, NEF 407 may invoke the Nnef_NTZParameter_Create response service operation to provide a response to UAS Authorization Entity 408. The response may include an assigned transaction reference ID. As will be discussed more fully below, the transaction reference ID may be included in subsequent requests related to the NTZ information. The Nnef_NTZParameter_Create response service operation may have one or more input parameters, including, but not limited to, the transaction reference ID and / or the result of the Nnef_NTZParameter_Create service operation (e.g., success or failure).

[0101] Creating and storing NTZ information at UDR 406 in operation 424 can trigger a data change event at UDR 406. If UE 401 is registered to core network 409, and PCF 404 has subscribed to the data modified in UDR 406 by calling Nudr_DM_Subscribe (USS / TPAE NTZ Parameter Configuration Information, SUPI, dataset set to "UEPolicySet", data subset set to "A2X NTZ Information") in operation 410, then operations 428-434 can be performed. Otherwise, operations 428 to 434 can be omitted.

[0102] In operation 428, UDR 406 transmits data, and PCF receives a notification of a data change occurring at UDR 406 due to NTZ information (provided by UAS Authorized Entity 408). In this example, as part of receiving the notification, PCF 404 may receive a Nudr_DM_Notify notification from UDR 406. Those skilled in the art will understand the Nudr_DM_Notify service operation.

[0103] As described above, in some instances, the UAS Authorization Entity 408 can provide NTZ information to a group of UEs. In such instances, the PCF 404 does not need to subscribe to be notified of NTZ information for each UE (e.g., application-specific information). Instead, the PCF 404 can subscribe to be notified of NTZ information for that group of UEs. For example, when the PCF 404 receives NTZ information for that group of UEs, the PCF 404 can deliver the same NTZ information to each UE in that group.

[0104] At operation 430, upon receiving notification of newly created NTZ information at UDR 406, PCF 404 initiates a UE policy transmission procedure. For example, PCF 404 can configure the NTZ information as part of a UE policy (e.g., an A2X policy), deliver the UE policy to UE 401 via AMF 403, and receive the result of the UE policy delivery via AMF 403. The following will refer to... Figure 5 A more comprehensive discussion of the mechanisms used to execute UE policy delivery.

[0105] If the UAS Authorized Entity 408 has subscribed to notifications regarding UE policy delivery results resulting from NTZ parameter configuration for a single UE (e.g., UE 401), and notifies the PCF 404 of the UE policy delivery results, then the PCF 404 can notify the NEF 407 of the UE delivery results. For example, at operation 432, the PCF 404 transmits and the NEF 407 receives notifications of the delivery results of UE policies configured based on 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 results included in the UE policy container as the result of the UE policy delivery process to the NEF 407 by sending an Npcf_EventExposure_Notify notification (indicating the result). Those skilled in the art will understand the Npcf_EventExposure_Notify notification.

[0106] If PCF 404 is notified of the UE policy delivery failure from AMF 403 due to UE 401 being unreachable, PCF 404 can determine to retry the UE policy delivery procedure at operation 430 when UE 401 becomes reachable. In this case, PCF 404 can report the temporary state (e.g., UE is temporarily unreachable) to NEF 407 as a result of the procedure by sending an Npcf_EventExposoure_Notify notification (indicating a temporary state).

[0107] If PCF 404 determines at operation 430 that the UE policy delivery process has failed, PCF 404 can notify NEF 407 of the failure and the reason for the failure (e.g., UE unreachable) as a result of the process by sending an Npcf_EventExposure_Notify notification (indicating the failure and the reason for the failure).

[0108] If the UAS Authorization Entity 408 has already subscribed to the results of UE policy delivery, then NEF 407 transmits a notification to the UAS Authorization Entity 408 regarding the results of UE policy delivery received from PCF 404. As shown in the figure, at operation 434, upon receiving the Npcf_EventExposure_Notify notification, NEF 407 transmits an Nnef_ServiceParameter_Notify message to the UAS Authorization Entity 408. In the example, NEF 407 can perform information mapping, for example, mapping the AF (USS / TPAE) transaction internal ID provided in the notification-related ID to the AF (USS / TPAE) transaction ID and / or mapping SUPI to GPSI. In other words, NEF 407 can perform a reverse mapping to map the 3GPP UAV ID to an ID known to the UAS Authorized Entity 408, and the Nnef_ServiceParameter_Notify message can include the GPSI, external ID, or (received as part of the NTZ Information Provisioning Request at Operation 418) PLMN ID, depending on the target recipient of the UE policy delivery, the transaction reference ID (provided at Operation 426), and the result of the UE policy delivery.

[0109] In some instances, UAS Authorization Entity 408 may indicate a resource (e.g., identified by a Uniform Resource Identifier (URI)) in which UAS Authorization Entity 408 may receive notification of subscription. In an example, UAS Authorization Entity 408 may include the indication of a resource as part of a subscription request included in an NTZ Information Provisioning Request transmitted at Operation 418.

[0110] In various aspects, UAS Authorized Entity 408 may optionally update the NTZ information at Core Network 409 based on various conditions or changes. For example, in operation 440, UAS Authorized Entity 408 transmits, and NEF 407 receives, an update request to update the NTZ information at Core Network 409. In the example, UAS Authorized Entity 408 may invoke the Nnef_NTZParameter_Update request service operation and provide the transaction reference ID (at operation 426) to UAS Authorized Entity 408 in the Nnef_NTZParameter_Create response message. The Nnef_NTZParameter_Update request service operation may have input parameters, such as, but not limited to, multiple NTZ update parameters, the transaction reference ID, and / or the result of the Nnef_NTZParameter_Update service operation (e.g., success or failure).

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

[0112] At operation 444, based on (e.g., in response to) an update of the NTZ information at UDR 406, UDR 406 transmits and PCF 404 receives a notification of data changes at UDR 406 due to the NTZ information update. In the example, as part of receiving the notification of data changes associated with the NTZ information update, PCF 404 may receive a Nudr_DM_Notify notification from UDR 406. Based on (e.g., in response to) this notification, PCF 404 may trigger a UE policy update procedure, as will be referred to below. Figure 5 Discussed.

[0113] In operation 446, NEF 407 transmits, and UAS Authorization Entity 408 receives a response to the NTZ information update request. In the example, NEF 407 may invoke the Nnef_NTZParameter_Update response service operation to provide a response to UAS Authorization Entity 408. The Nnef_NTZParameter_Update response service operation may have one or more input parameters, such as, but not limited to, the transaction reference ID and update status (e.g., pass or fail).

[0114] In various aspects, UAS Authorized Entity 408 may optionally remove NTZ information at Core Network 409 based on various conditions or changes. For example, in operation 450, UAS Authorized Entity 408 transmits, and NEF 407 receives, a deletion request to remove NTZ information from Core Network 409. In the example, UAS Authorized Entity 408 may invoke the Nnef_NTZParameter_Delete request service operation and provide the transaction reference ID (at operation 426) to UAS Authorized Entity 408 in the Nnef_NTZParameter_Create response message. The Nnef_NTZParameter_Delete request service operation may have one or more input parameters, such as, but not limited to, the transaction reference ID.

[0115] At operation 452, upon receiving a deletion request, NEF 407 deletes the NTZ information from UDR 406. For example, NEF 407 can use SUPI, internal group ID, or PLMN ID as a data key to search the UDR and delete the corresponding NTZ information associated with the data key from UDR 406. As part of deleting the NTZ information, NEF 407 can request UDM 405 to remove the authorization provided by sending the service-specific parameters (NTZ information) of the Nudm_ServiceSpecificAuthoriation_Remove service operation.

[0116] At operation 454, based on (e.g., in response to) the deletion of NTZ information from UDR 406, UDR 406 transmits and PCF 404 receives a notification of data change occurring at UDR 406 due to the deletion of NTZ information. In the example, as part of receiving the notification of data change associated with the deletion of NTZ information, PCF 404 may receive a Nudr_DM_Notify notification from UDR 406. Based on (e.g., in response to) this notification, PCF 404 may trigger a UE policy update procedure, as will be referred to below. Figure 5 Discussed.

[0117] In operation 456, NEF 407 transmits, and UAS Authorization Entity 408 receives a response to the NTZ information deletion request. In the example, NEF 407 may invoke the Nnef_NTZParameter_Delete response service operation to provide a response to UAS Authorization Entity 408. The Nnef_NTZParameter_Delete response service operation may have one or more input parameters, such as, but not limited to, the transaction reference ID and / or deletion status (e.g., successful or failed).

[0118] Figure 4These are merely examples of signals and operations, and variations are considered to be within the scope of this disclosure. In embodiments, signals and operations may include... Figure 4 Other signals and operations not shown. In embodiments, signals and operations may not include... Figure 4 Each signal and operation is shown. In an embodiment, the signals and operations can be used with... Figure 4 The connections shown are implemented using different connections. These and other embodiments are considered to be within the scope of this disclosure.

[0119] Figure 5 This is a diagram illustrating an example embodiment of an operation for updating a UE configuration based on new NTZ information, according to one aspect of this disclosure. It should be understood that the described signals may have associated operations, and the described operations may have associated signals. Therefore, the described signals may also relate to operations, and the described operations may also relate to signals. Additionally, Figure 5 This will describe the signals between various network components and the operations performed by these components, such as... Figure 5 Those shown at the top. Specifically, the components include UE 401, (R)AN 402, AMF 403, and PCF 404. The network components are illustrative, and other components are envisioned to involve signaling or executable operations. One or more of the following operations may be implemented in conjunction with the operations of this disclosure, as referenced above. Figure 4 Examples discussed. For instance, UE 401, (R)AN 402, AMF 403, and PCF404 can be executed. Figure 5 The operation shown is as Figure 4 This is part of operation 430.

[0120] PCF 404 can typically provide policy control functions to (or register with) multiple UEs associated with (or registered with) core network 409. As an example, PCF 404 can determine policy rules for UE 401. PCF 404 can divide the UE policy for UE 401 into one or more policy segments (or policy containers), each policy segment including one or more policy rules for UE 401. PCF 404 can assign a Policy Segment Identifier (PSI) to each policy segment. PCF 404 can deliver UE policy information to UE 401, whereby the UE policy information may include the content of each policy segment (e.g., (multiple) rules) and the corresponding PSI. PCF 404 can maintain an up-to-date list of PSIs delivered to UE 401 and can update the up-to-date list of PSIs in UDR 406, for example, by invoking the Nudr_DM_Update(SUPI, Policy Data, Policy Set Entry, Updated PSI Data) service operation. When a UE policy is received at UE 401, UE 401 may store multiple PSIs and their corresponding content at UE 401. Therefore, the multiple PSIs and their corresponding content at UE 401 are synchronized with the multiple PSIs and their corresponding content known at PCF 404 and stored at UDR 406. However, PCF 404 may subsequently update the UE policy for UE 401 based on changes in conditions and / or requirements (e.g., when new NTZ information becomes available).

[0121] In operation 510, due to the new NTZ information available at core network 409 (or more specifically, UDR 406), PCF 404 decides to update the A2X policy (e.g., UE policy). The new NTZ information can be provided by the UAS Authorized Entity 408 outside core network 409, as referenced above. Figure 4 The PCF 404 can determine the A2X policy update based on various triggering conditions. In one example, the triggering condition could be when UE 401 performs initial registration with core network 409. In another example, core network 409 could be part of 5GS (e.g., 5GS 320), and the triggering condition could be when UE 401 moves from EPS (e.g., EPS 330) to 5GS. In yet another example, the triggering condition could be based on notification of data changes associated with NTZ information stored at UDR 406.

[0122] In the case of initial registration or 5GS registration (due to UE 401 moving from EPS to 5GS), PCF 404 can compare the list of policy PSIs included in the A2X policy information provided in the Npcf_UEPolicyControl_Create request (received from AMF 403) with the list of PSIs stored at UDR 406. For example, as part of registration, UE 401 may transmit the list of PSIs stored at UE 401 via AMF 403, and when the Npcf_UEPolicyControl_Create request is transmitted to PCF 404, AMF 403 may include the list of PSIs stored at UE 401 in the A2X policy information. In some instances, there may be no PSIs stored at UE 401, and therefore the A2X policy information in the Npcf_UEPolicyControl_Create request may not include any PSIs (e.g., an empty PSI list). In the example, new NTZ information may be stored at UDR 406 in association with new PSIs. Therefore, PCF 404 can determine updated A2X policy information for UE 401 based on the new PSI (for NTZ information). PCF 404 can deliver A2X policy information, including NTZ information and the corresponding PSI, to UE 401 via AMF 403. In the example, AMF 403 can use downlink (DL) non-access stratum (NAS) transmission messages to provide updated A2X policy information to UE 401.

[0123] In the event of a network-triggered UE policy update (e.g., due to a change in UE location), PCF 404 can examine the latest PSI list delivered to UE 401 and stored at UDR 406 to determine which A2X policies must be transmitted to UE 401. For example, based on UE 401's new location, PCF 404 can determine that new PSIs for policy segments including NTZ information will be delivered to UE 401.

[0124] At operation 512, if PCF 404 has not yet subscribed to the response from AMF 403 to UE 401 regarding updates to UE policy information, then PCF 404 subscribes to AMF 403 to be notified of the response from AMF 403 to updates to UE policy information.

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

[0126] At operation 516, network-triggered service requests can be executed by AMF 403. For example, if UE 401 is registered and reachable by AMF 403, AMF 403 can transparently transmit the A2X policy container to UE 401 via (R)AN 402 through the registered access. However, if AMF 403 is not reachable from UE 401, AMF 403 can initiate a network-triggered service request to make UE 401 reachable.

[0127] At operation 518, if UE 401 accesses a connection via 3GPP using Connection Management (CM), AMF 403 can transparently deliver or transmit the A2X policy container (including UE policy information such as NTZ information) received from PCF 404 to UE 401. Upon receiving the A2X policy container, UE 401 updates the A2X policy and corresponding NTZ information provided by PCF 404. See below for reference. Figures 6A to 6C More comprehensively, UE 401 may comply with NTZ information (e.g., (multiple) configured NTZ and / or (multiple) band limits) and adjust the behavior of UE 401 accordingly.

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

[0129] At operation 522, AMF 403 uses the Namf_Communication_N1MessageNotify notification to forward the response of UE 401 to PCF 404.

[0130] Subsequently, PCF 404 can maintain the latest PSI list delivered to UE 401 and update the latest PSI list in UDR 406 by calling the Nudr_DM_Update(SUPI, policy data, policy set entry, updated PSI data) service operation.

[0131] Figure 5 These are merely examples of signals and operations, and variations are considered to be within the scope of this disclosure. In embodiments, signals and operations may include... Figure 5 Other signals and operations not shown. In embodiments, signals and operations may not include... Figure 5 Each signal and operation is shown. In an embodiment, the signals and operations can utilize [the following]. Figure 5 The connections shown are implemented using different connections. These and other embodiments are considered to be within the scope of this disclosure.

[0132] Figures 6A to 6C The illustration depicts an example NTZ information for UAV communication according to one aspect of this disclosure. (Combined with...) Figure 4 discuss Figures 6A to 6C .like Figure 6A As shown, NTZ information 600 may include NTZ parameter fields 610, 620, and 630. In various aspects, NTZ information 600 may correspond to... Figure 4 Operation 418 is provided by NTZ information from UAS authorized entity 408.

[0133] NTZ parameter field 610 is related to geographic area information. For example, NTZ parameter field 610 can instruct UE 401 to use a region not covered by RAN (e.g., EUTRA (such as...)). Figure 3 (R)AN 306) or NG RAN (such as Figure 3 The geographic area served by NG RAN 304. Figure 6B As shown, the NTZ parameter field 610 can include a list of coordinates 612, each coordinate including indications of longitude, latitude, and altitude. The coordinate information can indicate the boundaries of a geographic area or airspace.

[0134] NTZ Parameter Field 620 relates to radio parameters. For example, NTZ Parameter Field 620 can indicate radio parameters such as which frequency bands(s)(s) are permitted to transmit by UAV-UE (e.g., UE 150, 302, and / or 401) and / or which frequency bands(s) are restricted from transmission by UAV-UE (e.g., UE 150, 302, and / or 401) in a specific geographic area specified by NTZ Parameter Field 620. Figure 6BAs shown, the NTZ parameter field 620 may include a flag value 622 (or parameter 622) indicating whether the NTZ is applicable to a specific geographic area (e.g., the geographic area indicated by the NTZ parameter field 610). For example, the flag value 622 may be set to a value of 1 to indicate that the NTZ is applicable to the geographic area, or set to a value of 0 to indicate that the NTZ is not applicable to the geographic area, and vice versa. Additionally or alternatively, the NTZ parameter field 620 may include a list 624 (or parameters 624) of the transmission bands(s) that the UAV-UE is allowed or not allowed to perform transmissions. In other words, 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.

[0135] NTZ parameter field 630 may include information associated with the time period to which the NTZ applies for a specific geographic area (e.g., the geographic area indicated by NTZ parameter field 610). In an example, NTZ parameter field 630 may include an indication of the start and / or end times (e.g., time of day) for which the NTZ applies in that geographic area. As an example, NTZ parameter field 630 may indicate 10:00–11:00. As another example, NTZ parameter field 630 may indicate 10:00–11:00 and 00:00–06:00. Typically, NTZ parameter field 630 may indicate any suitable number of time periods to which the NTZ applies (e.g., 1, 2, 3, 4, or more) and / or use any suitable time format. In some instances, NTZ parameter field 630 may be optional.

[0136] In various aspects, UE 401 can receive NTZ information 600 and adapt its behavior based on NTZ information 600. To this end, UE 401 can determine its current location, for example, based on a Global Navigation Satellite System (GNSS) or Global Positioning System (GPS) receiver at UE 401. UE 401 can check whether it is within or outside the geographic area indicated by NTZ information 600, for example, based on a comparison of UE 401's location with a list of coordinates 612 or based on the radial distance between UE 401's location and a single coordinate in coordinates 612. If UE 401 is within the NTZ geographic area, UE 401 can check whether all transmissions are prohibited (i.e., no permitted transmission bands) or whether some bands are restricted. When UE 401 is within the geographic area, UE 401 can perform or not perform transmission and / or cell search based on NTZ information 600.

[0137] In various aspects, NTZ information 600 may include at least NTZ parameter field 610 (indicating a geographic area), and may optionally include one or more parameters from NTZ parameter fields 620 and / or 630. In the first example, NTZ information 600 may include an indication of a geographic area (e.g., a list of coordinates 612), and an exclusion flag value 622 and a list 624 of allowed or disallowed frequency bands(s). Such NTZ information 600 may indicate a general restriction on transmission (i.e., no allowed transmission frequency bands). Therefore, UE 401 may (completely) avoid performing cell search or transmission in the geographic area. In other geographic areas (outside the geographic area indicated by NTZ parameter field 610), UE 401 may perform transmission based on the frequency band information provided to UE 401 (e.g., in an A2X policy). If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), UE 401 may (completely) avoid performing cell search or transmission in that geographic area during the indicated time period.

[0138] In the second example, NTZ information 600 may include an indication of a geographic area (e.g., a list of coordinates 612) and a flag value 622, and a list 624 of excluded or disallowed frequency bands(s). If flag value 622 indicates that NTZ applies, UE 401 may (completely) avoid performing cell searches or transmissions in the geographic area. If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), UE 401 may (completely) avoid performing cell searches or transmissions in the geographic area during the indicated time period. If flag value 622 indicates that NTZ does not apply, UE 401 may not restrict its transmissions in the geographic area.

[0139] In the third example, NTZ information 600 may include an indication of a geographic area (e.g., a list of coordinates 612) and a parameter 624 indicating restricted (disallowed) transmission bands(s), and an exclusion flag value 622. Based on such NTZ information 600, when UE 401 is in the geographic area, UE 401 can avoid performing cell search or transmission in any of the restricted transmission bands(s). Additionally or alternatively, UE 401 may use frequency bands outside the restricted transmission bands(s) to transmit communication signals. If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), UE 401 may avoid performing cell search or transmission in any of the restricted transmission bands(s) and / or use frequency bands outside the restricted transmission bands(s) to transmit communication signals during the indicated time period.

[0140] In the fourth example, NTZ information 600 may include an indication of a geographic area (e.g., a list of coordinates 612) and a parameter 624 indicating permitted transmission bands(s), and an exclusion flag value 622. Based on such NTZ information 600, UE 401 can transmit communication signals using frequency bands in the permitted transmission bands(s). Alternatively or additionally, UE 401 can avoid performing cell search or transmission in any band outside the permitted transmission bands. If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), UE 401 can use frequency bands in the permitted transmission bands to transmit communication signals and / or avoid performing cell search or transmission in any band outside the permitted transmission bands during the indicated time period.

[0141] In the fifth example, NTZ information 600 may include an indication of a geographic area (e.g., a list of coordinates 612), a flag value 622, and a list 624 of permitted or prohibited frequency bands. If flag value 622 indicates that NTZ applies, then the frequency band(s) in parameter 624 are restricted transmission band(s) (not permitted for transmission). Therefore, when UE 401 is in a geographic area, UE 401 can avoid performing cell search, lateral link discovery / advertising, or transmission in any of the restricted transmission bands(s), where the avoidance is based on flag value 622 indicating that NTZ applies. Additionally or alternatively, UE 401 may use frequency bands outside the restricted transmission bands(s) to transmit communication signals. If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), then UE 401 may avoid performing cell search or transmission in any of the restricted transmission bands(s) and / or use frequency bands outside the restricted transmission bands(s) to transmit communication signals during the indicated time period. However, if flag value 622 indicates that NTZ is not applicable, then the frequency band(s) in parameter 624 are the permitted transmission frequency band(s). Therefore, UE 401 can use frequency band(s) from the permitted transmission frequency band(s) to transmit communication signals. Alternatively or additionally, UE 401 can avoid performing cell search or transmission in any frequency band(s) outside the permitted transmission frequency band(s). If NTZ information 600 also includes timing information (e.g., NTZ parameter field 630), then UE 401 can use frequency band(s) from the permitted transmission frequency band(s) to transmit communication signals and / or avoid performing cell search or transmission in any frequency band(s) outside the permitted transmission frequency band(s) during the indicated time period.

[0142] In various aspects, the UAS Authorized Entity 408 may be unaware of the frequency bands used (or permitted) by the Public Land Mobile Network (PLMN) serving UE 401. For example, the PLMN may configure UE 401 to transmit using certain frequency bands. If parameter 624 indicates permitted transmission frequency bands (e.g., in the fourth and fifth examples described above, where flag value 622 indicates that NTZ is not applicable), then the core network 409, the corresponding RAN, and UE 401 may have to restrict UE 401's transmissions to a portion of the permitted transmission frequency bands indicated by parameter 624 and a portion of the frequency bands configured by the PLMN.

[0143] In other words, NTZ information 600 can coordinate information indicating a geographic area (e.g., coordinates 612) and may optionally include one or more of the following: a flag value indicating whether NTZ is applicable to the geographic area (e.g., flag value 622), information associated with one or more permitted transmission bands (e.g., parameters 624), information associated with one or more restricted transmission bands (e.g., parameters 624), or information associated with the time period to which NTZ applies (e.g., timing information in NTZ parameter field 630).

[0144] Figures 6A to 6C The NTZ information 600 is merely illustrative, and variations are considered to be within the scope of this disclosure. Typically, the parameters in the NTZ information 600 can be arranged in any suitable order. Furthermore, in some instances, the NTZ information 600 may indicate multiple geographic areas (e.g., 2, 3, 4 or more) and include radio parameter(s) and / or timing validity information for each geographic area(s).

[0145] Figure 7 This is a flowchart illustrating an example operation of a network device equipped with NTZ information according to one aspect of this disclosure. In one aspect, the network device may be a UAS authorized entity (such as those mentioned above). Figure 4 The device or network node discussed is the UAS Authorized Entity 408. In some examples, the network device can use a device with, for example, Figure 11 The device shown implements the operation using the components. Figure 7 The operations can include those described in the reference above. Figures 1 to 5 A similar mechanism is discussed. As shown in the figure, Figure 7 It includes several enumerated steps, but Figure 7 The aspects of the operation may include additional steps before, after, and between the listed steps. Within each aspect, one or more of the listed steps may be omitted or performed in a different order.

[0146] In box 702, the network device of the UAS Authorizing Entity transmits an NTZ Configuration Request to the core network, wherein the NTZ information is configured by the core network to configure UE policies for UAV. In some instances, the UAS Authorizing Entity may correspond to UAS Authorizing Entity 408, which may be, for example... Figure 3 USS 316 or such Figure 3 The TPAE 314. In some instances, the core network can correspond to... Figure 2 CN 210, Figure 3 5GC 310 and / or Figure 4 The core network is 409. In some instances, the UAV can correspond to... Figure 1 UE 150 Figure 3 UE 302 and / or Figure 4 UE 401. In one example, the network device can transmit an NTZ information provisioning request by invoking the Nnef_NTZParameter_Create request service operation provided by the NEF entity of the core network (e.g., UAS NF 230, UAS NF 308 and / or NEF 407).

[0147] In all aspects, NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether NTZ applies to a geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which NTZ applies, for example, as referenced above. Figures 6A to 6C The discussion focuses on the following: In each aspect, the UAS authorizing entity can equip an individual UE (e.g., a specific UAV-UE), a group of UEs (e.g., a class of UAV-UEs), or a PLMN with NTZ information, and a UAV can correspond to a single UE served by the PLMN, the group of UEs, or all UEs (UAV-UEs). For example, if NTZ information is equipped for a group of UEs, then the UAV is one of the UEs in that group. If NTZ information is equipped for the PLMN, then the UAV is one of the UEs served by the PLMN.

[0148] At box 704, the network device receives a transaction reference ID based on (e.g., in response to) a transmission NTZ information configuration request. In the example, the network device may receive the transaction reference ID via an Nnef_NTZParameter_Create response service operation provided by a NEF entity in the core network.

[0149] In various aspects, the NTZ information provision request at box 702 also includes a request for notification of the result of delivery of a UE policy configured based on the NTZ information for subscription, and the network device also receives notification of the result of UE policy delivery based on (e.g., in response to) the subscription. In the example, the network device may receive the notification from the NEF entity via an Nnef_ServiceParameter_Notify message.

[0150] In various aspects, the network device also transmits update requests to update NTZ information at the core network, where the update request includes the transaction reference ID obtained at box 704. In the example, the network device may transmit the update request via the Nnef_NTZParameter_Update request service operation provided by the NEF entity.

[0151] In various aspects, the network device also transmits a delete request over the network to remove NTZ information from the core network, wherein the delete request includes the transaction reference ID obtained at box 704. In the example, the network device may transmit the delete request via the Nnef_NTZParameter_Delete request service operation provided by the NEF entity.

[0152] Figure 8 This is a flowchart illustrating one aspect of the operation of a network device equipped with NTZ information, according to an illustrative aspect of this disclosure. In one aspect, the network device may be a NEF entity (such as those described above, referred to separately). Figure 2 , Figure 3 and / or Figure 4 The discussion focuses on devices or network nodes (UAS NF 230, UAS NF 308, and / or NEF 407). In some examples, network devices can use devices with features such as... Figure 11 The device shown implements the operation using the components. Figure 8 The operations can include those described in the reference above. Figures 1 to 5 A similar mechanism is discussed. As shown in the figure, Figure 8 It includes several enumerated steps, but Figure 8 The aspects of the operation may include additional steps before, after, and between the listed steps. Within each aspect, one or more of the listed steps may be omitted or performed in a different order.

[0153] In box 802, the network device of the NEF entity associated with the core network receives an NTZ information provisioning request from the UAS Authorized Entity to provision NTZ information to the core network, wherein the NTZ information is configured by the core network to configure UE policies for UAV. In some instances, the NEF entity may correspond to Figure 2 UAS NF 230, Figure 3UAS NF 308 and / or Figure 4 The NEF 407. In some instances, the core network can correspond to... Figure 2 CN 210, Figure 3 5GC 310 and / or Figure 4 The core network is 409. In some instances, the UAS Authorization Entity can correspond to UAS Authorization Entity 408, which can be, for example... Figure 3 USS 316 or such Figure 3 The TPAE of 314. In some instances, the UAV may correspond to... Figure 1 UE 150 Figure 3 UE302 and / or Figure 4 UE 401. In the example, the network device can receive an NTZ information configuration request via the Nnef_NTZParameter_Create request service operation.

[0154] In all aspects, NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether NTZ applies to a geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which NTZ applies, for example, as referenced above. Figures 6A to 6C The discussion focuses on the following: In various aspects, NTZ information can be provided for a single UE (e.g., a specific UAV-UE), a group of UEs (e.g., a class of UAV-UEs), or a PLMN, and a UAV can correspond to a single UE served by the PLMN, the group of UEs, or all UEs (UAV-UEs). For example, if NTZ information is provided for a group of UEs, then the UAV is one of the UEs in that group. If NTZ information is provided for the PLMN, then the UAV is one of the UEs served by the PLMN.

[0155] At box 804, the network device transmits a transaction reference ID to the UAS authorizing entity based on (for example, in response to) receiving an NTZ information provisioning request. In the example, the network device may transmit the transaction reference ID via the Nnef_NTZParameter_Create response service operation.

[0156] In various aspects, the NTZ information provisioning request at block 802 also includes a subscription to a notification of the delivery result of the UE policy configured based on the NTZ information, and the network device also transmits the notification of the UE policy delivery result to the UAS authorizing entity based on (e.g., in response to) the subscription. In various aspects, the network device can receive a PCF event notification message including the result of the UE policy delivery from the PCF entity of the core network, and the result transmitted to the UAS authorizing entity can correspond to the result in the PCF event notification message.

[0157] In all aspects, upon receiving NTZ information in block 802, the network device stores the NTZ information associated with the UE policy at the UDR in the core network. In all aspects, the network device also receives an update request from the UAS authorizing entity to update the NTZ information, wherein the update request includes a transaction reference ID, and updates the NTZ information stored at the UDR based on the received update request. In the example, the network device may receive the update request via the Nnef_NTZParameter_Update request service operation.

[0158] In various aspects, the network device also receives a delete request from the UAS Authorized Entity to delete NTZ information, where the delete request includes the Transaction Reference ID, and deletes the NTZ information from the UDR based on the received delete request. In the example, the network device may receive the delete request via the Nnef_NTZParameter_Delete request service operation.

[0159] Figure 9 This is a flowchart illustrating one aspect of the operation of a network device equipped with NTZ information, according to an illustrative aspect of the present disclosure. In one aspect, the network device may be a PCF entity (such as those described above, referred to separately). Figure 2 or Figure 4 The device or network node discussed (PCF 219 or PCF 404). In some examples, the network device can use devices with features such as Figure 11 The device shown implements the operation using the components. Figure 9 The operations can include those described in the reference above. Figures 1 to 5 A similar mechanism is discussed. As shown in the figure, Figure 9 It includes several enumerated steps, but Figure 9 The aspects of the operation may include additional steps before, after, and between the listed steps. Within each aspect, one or more of the listed steps may be omitted or performed in a different order.

[0160] At box 902, the network apparatus of the PCF entity in the core network configures UE policies (e.g., A2X policies) for the UE (e.g., UAV-UE) to perform aircraft communications, wherein this configuration is based at least in part on NTZ information provided by a UAS authorized entity outside the core network. In some instances, the PCF entity may correspond to Figure 2 PCF 219 and / or Figure 4 PCF 404. In some instances, the core network can correspond to... Figure 2 CN 210, Figure 3 5GC 310 and / or Figure 4The core network is 409. In some instances, the UAS Authorization Entity can correspond to UAS Authorization Entity 408, which can be, for example... Figure 3 USS 316 or such Figure 3 The TPAE of 314. In some instances, the UE may correspond to Figure 1 UE 150 Figure 3 UE 302 and / or Figure 4 UE 401.

[0161] In all aspects, NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether NTZ applies to a geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which NTZ applies, for example, as referenced above. Figures 6A to 6C The discussion focuses on the following: In each aspect, NTZ information can be provided for a single UE (e.g., a specific UAV-UE), a group of UEs (e.g., a class of UAV-UEs), or a PLMN, and a UE can correspond to a single UE served by the PLMN, the group of UEs, or all UEs (UAV-UEs). For example, if NTZ information is provided for a group of UEs, then the UAV is one of the UEs in that group. If NTZ information is provided for the PLMN, then the UAV is one of the UEs served by the PLMN.

[0162] At box 904, network devices (e.g., AMF entities via the network, such as...) Figure 2 AMF 212 or Figure 4-5 The AMF 403 transmits UE policies, including NTZ information, to the UE.

[0163] At box 906, the network device receives a response to the UE policy from the UE (e.g., via an AMF entity).

[0164] At box 908, the network device transmits a notification of the response to the UE policy to the NEF entity associated with the core network.

[0165] In various aspects, the network device further receives notifications of data changes associated with NTZ information from the UDR entity in the core network, wherein UE policies are configured based on these data changes. In some instances, the UDR entity may correspond to... Figure 2 UDR 224 or Figure 4 UDR 406.

[0166] Figure 10 This is a flowchart illustrating an example operation of a UE receiving NTZ information updates according to one aspect of this disclosure. In one aspect, the UE may refer to the above-described embodiments respectively. Figures 1 to 2 , Figure 3 or Figures 4 to 5 The discussion focuses on UE 150, UE 302, or UE 401. In some examples, the UE can use devices with features such as... Figure 11 The device shown implements the operation using the components. Figure 10 The operations can include those described in the reference above. Figures 1 to 5 A similar mechanism is discussed. As shown in the figure, Figure 10 It includes several enumerated steps, but Figure 10 The aspects of the operation may include additional steps before, after, and between the listed steps. Within each aspect, one or more of the listed steps may be omitted or performed in a different order.

[0167] In box 1002, the UE receives a UE policy for aircraft communication from the core network, which includes NTZ information.

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

[0169] In box 1006, the UE transmits a response to the core network regarding the receipt of the updated UE policy.

[0170] In all aspects, the updated NTZ information includes at least one of the following: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to a geographic area, information associated with one or more permitted transmission bands, information associated with one or more restricted transmission bands, or information associated with the time period to which the NTZ applies, for example, as referenced above. Figures 6A to 6C The following are discussed aspects. In each aspect, the UE also avoids performing cell searches or transmissions within a geographic area. In each aspect, the avoidance of performing cell searches or transmissions within a geographic area is also based on a flag value. In each aspect, as part of the avoidance, the UE avoids performing cell searches or transmissions within the geographic area during the applicable NTZ period. In each aspect, as part of the avoidance, the UE avoids performing cell searches or transmissions in any restricted transmission band within a restricted transmission band (when the UE is in a geographic area). In each aspect, the UE also transmits communication signals using frequency bands outside of one or more restricted transmission bands. In each aspect, the UE also transmits communication signals using frequency bands within one or more permitted transmission bands (when the UE is in a geographic area).

[0171] Now for reference Figure 11This diagram illustrates a block diagram of example components of a UE or network device. The device includes an electronic storage device 1110, a processor 1120, a memory 1150, and a network interface 1140. The various components can be communicatively coupled to each other. The processor 1120 can 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-a-chip (SoC), or any other type of processor. The memory 1150 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 1150 includes processor-readable instructions executable by the processor 1120 to cause the device to perform various operations, including those mentioned herein, such as... Figures 4 to 5 and Figures 7 to 10 The operation.

[0172] Electronic storage device 1110 can be and includes any type of electronic storage device for storing data, such as hard disk drives, solid-state drives, and / or optical disks, as well as other types of electronic storage devices. Electronic storage device 1110 stores processor-readable instructions for causing the device to perform its operations, and stores data associated with such operations, such as data related to the 5G NR standard and other data. Network interface 1140 can implement wireless network technologies, such as 5G NR and / or other wireless network technologies.

[0173] Figure 11 The components shown are merely examples, and those skilled in the art will understand that the apparatus includes other components not shown, and may include multiples of any of the components shown. These and other embodiments are considered to be within the scope of this disclosure.

[0174] Typically, the various operations of the methods described herein can be performed by any suitable component element (e.g., processor 1120 and memory 1150) capable of performing the corresponding operations. Components may include various hardware(s) and / or software components and / or modules(s), including but not limited to... Figure 11 Components.

[0175] Other embodiments of this disclosure include the following examples.

[0176] Example 1.1. A method comprising: A network device of an Unmanned Aerial System (UAS) authorized entity transmits a Non-Transfer Zone (NTZ) information provision request to the core network to provision NTZ information, wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aerial Vehicle (UAV); and The network device receives the transaction reference identifier (ID) based on the NTZ information transmission configuration request.

[0177] Example 1.2. The method of Example 1.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and This method also includes: The network device receives notifications of the results of UE policy delivery based on the subscription.

[0178] The methods in Example 1.3 and Example 1.2 also include: The network device transmits an update request to update the NTZ information at the core network, wherein the update request includes the transaction reference ID.

[0179] The methods of any one of Examples 1.1-1.3 in Example 1.4 also include: A deletion request is transmitted by a network device to delete NTZ information from the core network, wherein the deletion request includes a transaction reference ID.

[0180] Example 1.5. A method of any one of Examples 1.1-1.4, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0181] Example 1.6. A method of any of Examples 1.1-1.5, wherein the NTZ information is provided for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0182] Example 2.1. A method comprising: A network device of a Network Open Functions (NEF) entity associated with the core network receives a Non-Transmission Zone (NTZ) information provision request from an Unmanned Aerial System (UAS) authorized entity to provision NTZ information to the core network, wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for unmanned aerial vehicles (UAVs); and The network device transmits the Transaction Reference Identifier (ID) to the UAS Authorized Entity based on the received NTZ Information Configuration Request.

[0183] Example 2.2. The method of Example 2.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and The method further includes: The network device transmits notifications of the results of UE policy delivery to the UAS authorizing entity based on the subscription.

[0184] Example 2.3. The methods of Example 2.1 or Example 2.2 also include: The network device receives a PCF event notification message from the Policy Control Function (PCF) entity in the core network, which includes the result of UE policy delivery.

[0185] Example 2.4. The methods of any one of Examples 2.1-2.3, and also include: NTZ information is stored in association with UE policies at the Unified Data Repository (UDR) in the core network.

[0186] The methods in Example 2.5 and Example 2.4 also include: The network device receives an update request from the UAS authorizing entity to update the NTZ information, wherein the update request includes a transaction reference ID; and Based on the received update request, update the NTZ information stored in the UDR.

[0187] The methods in Example 2.6 and Example 2.4 also include: The network device receives a deletion request from the UAS authorized entity to delete NTZ information, wherein the deletion request includes a transaction reference ID; and Based on the received deletion request, the NTZ information is deleted from the UDR.

[0188] Example 2.7. A method of any one of Examples 2.1-2.6, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0189] Example 2.8. A method of any of Examples 2.1-2.7, wherein the NTZ information is provided for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0190] Example 3.1. A method comprising: The network apparatus at the core network is configured to configure UE policies for user equipment (UE) to perform aircraft communications, wherein the configuration is based at least in part on non-transmission zone (NTZ) information provided by an authorized entity of the unmanned aerial system (UAS) outside the core network; UE policy that transmits NTZ information from the network device to the UE; The network device receives a response to the UE policy from the UE; and The network device transmits a notification of the response to the UE policy to the Network Open Function (NEF) entity associated with the core network.

[0191] Example 3.2. The method in Example 3.1 also includes: The network device receives notifications of data changes associated with NTZ information from the Unified Data Repository (UDR) entity in the core network. The UE policy is configured based on data changes associated with NTZ information.

[0192] Example 3.3. The method of Example 3.1 or Example 3.2, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

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

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

[0195] Example 4.1. A method comprising: The user equipment (UE) receives UE policies for aircraft communication from the core network. The UE policies include non-transmission zone (NTZ) information. The updated UE policy, including updated NTZ information, is received by the UE from the core network; and The UE transmits a response to the core network regarding the receipt of the updated UE policy.

[0196] Example 4.2. The method of Example 4.1, wherein the updated NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0197] The methods in Example 4.3 and Example 4.2 also include: The UE avoids performing cell searches or transmissions within a geographical region.

[0198] Example 4.4. The method of Example 4.3, in which avoiding performing cell search or transmission in that geographic area is also based on the flag value.

[0199] Example 4.5. A method from any of Example 4.3 or Example 4.4, wherein avoiding cell search or transmission within a geographic area includes: The UE is instructed to avoid performing cell search or transmission in any of the one or more restricted transmission bands.

[0200] Example 4.6. Methods of any of Examples 4.3-4.5, wherein avoiding cell search or transmission within a geographic area includes: The UE should avoid performing cell search or transmission in the geographic area during the time period in which the NTZ applies.

[0201] The methods of any one of Examples 4.2-4.6 in Example 4.7 also include: The UE transmits communication signals using frequency bands outside of one or more restricted transmission frequency bands.

[0202] Example 4.8. The method of Example 4.7, wherein transmitting communication signals includes: The UE transmits communication signals using one or more frequency bands outside the restricted transmission frequency bands during the applicable time period of the NTZ.

[0203] The methods of any one of Examples 4.2-4.8 in Example 4.9 also include: The UE transmits communication signals using frequency bands in one or more permitted transmission frequency bands.

[0204] Example 4.10. The method of Example 4.9, wherein transmitting communication signals includes: During the applicable time period of the NTZ, the UE transmits communication signals using frequency bands in one or more permitted transmission frequency bands.

[0205] Example 5.1. An apparatus comprising: At least one processor; and At least one memory storing instructions that, when executed by a processor, cause the device to execute at least the following: A network device of an Unmanned Aerial System (UAS) authorized entity transmits a Non-Transfer Zone (NTZ) information provision request to the core network to provision NTZ information, wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aerial Vehicle (UAV); and The network device receives the transaction reference identifier (ID) based on the NTZ information transmission configuration request.

[0206] Example 5.2. The apparatus of Example 5.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and The device also includes: The network device receives notifications of the results of UE policy delivery based on the subscription.

[0207] Example 5.3. The apparatus of Example 5.2 further includes: The network device transmits an update request to update the NTZ information at the core network, wherein the update request includes the transaction reference ID.

[0208] Example 5.4. The apparatus of any one of Examples 5.1-5.3 further includes: A deletion request is transmitted by a network device to delete NTZ information from the core network, wherein the deletion request includes a transaction reference ID.

[0209] Example 5.5. An apparatus of any of Examples 5.1-5.4, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0210] Example 5.6. An apparatus of any of Examples 5.1-5.5, wherein the NTZ information is configured for a single UE, a group of UEs, or a Public Land Mobile Network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0211] Example 6.1. An apparatus comprising: At least one processor; and At least one memory storing instructions that, when executed by a processor, cause the device to execute at least the following: The device receives a Non-Transmission Zone (NTZ) information provision request from an Unmanned Aircraft System (UAS) Authorized Entity to provide NTZ information to the core network, wherein the device is associated with a Network Open Functions (NEF) entity associated with the core network, and wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aircraft (UAV); and Based on the received NTZ information provision request, the transaction reference identifier (ID) is transmitted to the UAS authorized entity.

[0212] Example 6.2. The apparatus of Example 6.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and The device also includes: Notifications regarding the results of UE policy delivery are transmitted to the UAS Authorized Entity based on the subscription.

[0213] Example 6.3. The apparatus of Example 6.1 or Example 6.2 further includes: Receive PCF event notification messages from the core network's Policy Control Function (PCF) entity, including the results of UE policy delivery.

[0214] Example 6.4. The apparatus of any one of Examples 6.1-6.3 further includes: NTZ information is stored in association with UE policies at the Unified Data Repository (UDR) in the core network.

[0215] The apparatus of Example 6.5. Example 6.4 further includes: Receive update requests from the UAS authorizing entity to update NTZ information, where the update request includes the transaction reference ID; and Based on the received update request, update the NTZ information stored in the UDR.

[0216] The apparatus of Example 6.6.4 further includes: Receive a deletion request from the UAS authorized entity to delete NTZ information, wherein the deletion request includes the transaction reference ID; and Based on the received deletion request, the NTZ information is deleted from the UDR.

[0217] Example 6.7. An apparatus of any one of Examples 6.1-6.6, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0218] Example 6.8. An apparatus of any of Examples 6.1-6.7, wherein the NTZ information is configured for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0219] Example 7.1. An apparatus comprising: At least one processor; and At least one memory storing instructions that, when executed by a processor, cause the device to execute at least the following: Configure UE policies for user equipment (UE) to perform aircraft communications, wherein the configuration is based at least in part on non-transmission zone (NTZ) information provided by an unmanned aerial system (UAS) authorized entity outside the core network, wherein the device is located at the core network; UE policy for transmitting NTZ information to the UE; Receive responses to UE policies from the UE; and Transmit notifications of responses to UE policies to Network Open Function (NEF) entities associated with the core network.

[0220] Example 7.2. The apparatus of Example 7.1 further includes: Receive notifications of data changes associated with NTZ information from the Unified Data Repository (UDR) entity in the core network. The UE policy is configured based on data changes associated with NTZ information.

[0221] Example 7.3. An apparatus of Example 7.1 or Example 7.2, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0222] Example 7.4. An apparatus of any of Examples 7.1-7.3, wherein NTZ information is provided for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0223] Example 7.5. An apparatus of any of Examples 7.2-7.19, wherein the apparatus includes a policy control function (PCF) entity for the core network.

[0224] Example 8.1. A user equipment, comprising: At least one processor; and At least one memory storing instructions that, when executed by a processor, cause the device to execute at least the following: Receive UE policies for aircraft communication from the core network. The UE policies include non-transmission zone (NTZ) information. Receive updated UE policies from the core network, including updated NTZ information; and Transmit a response to the core network regarding the receipt of the updated UE policy.

[0225] Example 8.2. The apparatus of Example 8.1, wherein the updated NTZ information includes at least one of the following: Indicates the coordinate information of the geographic region, and indicates whether the NTZ is applicable to the geographic region's flag values. Information associated with one or more permitted transmission frequency bands, or Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0226] The apparatus of Example 8.3.2 further includes: The UE avoids performing cell searches or transmissions within a geographical region.

[0227] Example 8.4. The apparatus of Example 8.3, wherein avoiding cell search or transmission in that geographic area is also based on the flag value.

[0228] Example 8.5. An apparatus of any one of Example 8.3 or Example 8.4, wherein avoiding performing cell search or transmission in a geographic area includes: The UE is instructed to avoid performing cell search or transmission in any of the one or more restricted transmission bands.

[0229] Example 8.6. An apparatus of any one of Examples 8.3-8.5, wherein avoiding cell search or transmission in a geographic area includes: During the NTZ applicable time period, avoid performing cell searches or transmissions in the geographic area.

[0230] The apparatus of any one of Examples 8.2-8.6, as described in Example 8.7, further includes: The UE transmits communication signals using frequency bands outside of one or more restricted transmission frequency bands.

[0231] Example 8.8. The apparatus of Example 8.7, wherein transmitting communication signals includes: During the applicable NTZ period, communication signals are transmitted using frequency bands outside of one or more restricted transmission frequency bands.

[0232] Example 8.9. The apparatus of any one of Examples 8.2-8.8 further includes: The UE transmits communication signals using frequency bands in one or more permitted transmission frequency bands.

[0233] Example 8.10. The apparatus of Example 8.9, wherein transmitting communication signals includes: During the applicable time period of NTZ, communication signals are transmitted using frequency bands in one or more permitted transmission frequency bands.

[0234] Example 9.1. An apparatus comprising: Components for transmitting Non-Transmission Zone (NTZ) information provision requests from network devices of an Unmanned Aerial System (UAS) authorized entity to provision NTZ information to the core network, wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aerial Vehicle (UAV); and A component for receiving a transaction reference identifier (ID) from a network device based on a request to transmit NTZ information.

[0235] Example 9.2. The apparatus of Example 9.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and The device also includes: Receive notifications of the results of UE policy delivery based on subscription.

[0236] The apparatus of Example 9.3.2 further includes: A component for transmitting update requests from network devices to update NTZ information at the core network, wherein the update request includes a transaction reference ID.

[0237] Example 9.4. The apparatus of any one of Examples 9.1-9.3 further includes: A component for transmitting deletion requests by network devices to remove NTZ information from the core network, wherein the deletion request includes a transaction reference ID.

[0238] Example 9.9. An apparatus of any of Examples 9.1-9.4, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0239] Example 9.6. An apparatus of any of Examples 9.1-9.5, wherein the NTZ information is configured for a single UE, a group of UEs, or a Public Land Mobile Network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0240] Example 10.1. An apparatus comprising: Components for receiving a Non-Transmission Zone (NTZ) information provision request from an Unmanned Aircraft System (UAS) authorized entity to provision NTZ information to the core network, wherein the device is associated with a Network Open Functions (NEF) entity associated with the core network, and wherein the NTZ information is configured for use by the core network to configure User Equipment (UE) policies for the Unmanned Aircraft (UAV); and A component used to transmit a transaction reference identifier (ID) to a UAS authorized entity based on a received NTZ information configuration request.

[0241] Example 10.2. The apparatus of Example 10.1, The NTZ information provisioning request also includes a request for notification of the results of the delivery of UE policies configured based on NTZ information for subscription, and The device also includes: Notifications regarding the results of UE policy delivery are transmitted to the UAS Authorized Entity based on the subscription.

[0242] Example 10.3. The apparatus of Example 10.1 or Example 10.2 further includes: A component for receiving PCF event notification messages, including the results of UE policy delivery, from the core network's Policy Control Function (PCF) entity.

[0243] Example 10.4. The apparatus of any one of Examples 10.1-10.3 further includes: The component used to store NTZ information in association with UE policies at the Unified Data Repository (UDR) in the core network.

[0244] The apparatus of Example 10.5.Example 10.4 further includes: The component used to receive update requests from the UAS authorizing entity to update NTZ information, wherein the update request includes a transaction reference ID; and A component used to update the NTZ information stored at the UDR based on received update requests.

[0245] The apparatus of Example 10.6. Example 10.4 further includes: The component used to receive deletion requests from the UAS authorizing entity to delete NTZ information, wherein the deletion request includes a transaction reference ID; and A component for deleting NTZ information from the UDR based on a received deletion request.

[0246] Example 10.7. An apparatus of any one of Examples 10.1-10.6, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0247] Example 10.8. An apparatus of any of Examples 10.1-10.7, wherein the NTZ information is configured for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0248] Example 11.1. An apparatus comprising: Components for configuring UE policies for user equipment (UE) to perform aircraft communications by network devices at the core network, wherein the configuration is based at least in part on non-transmission zone (NTZ) information provided by an unmanned aerial system (UAS) authorized entity outside the core network; Components used to transmit UE policies, including NTZ information, to the UE; Components for receiving responses to UE policies from the UE; and A component used to transmit notifications of responses to UE policies to Network Open Function (NEF) entities associated with the core network.

[0249] Example 11.2. The apparatus of Example 11.1 further includes: A component used to receive notifications of data changes associated with NTZ information from the Unified Data Repository (UDR) entity in the core network. The UE policy is configured based on data changes associated with NTZ information.

[0250] Example 11.3. An apparatus of Example 11.1 or Example 11.2, wherein the NTZ information includes at least one of the following: Indicates the coordinate information of a geographic region. A flag value indicating whether NTZ applies to a geographic area. Information associated with one or more permitted transmission frequency bands, Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0251] Example 11.4. An apparatus of any of Examples 11.1-11.3, wherein NTZ information is provided for a single UE, a group of UEs, or a Public Land Mobile Network (PLMN), and wherein the UE corresponds to a single UE, a group of UEs, or a UE served by the PLMN.

[0252] Example 11.5. An apparatus of any of Examples 11.2-11.19, wherein the network apparatus includes a policy control function (PCF) entity of the core network.

[0253] Example 12.1. A user equipment, comprising: A component for receiving UE policies for aircraft communications from the core network, the UE policies including non-transmission zone (NTZ) information; A component for receiving updated UE policies, including updated NTZ information, from the core network; and A component used to transmit a response to the core network for receiving an updated UE policy.

[0254] Example 12.2. The apparatus of Example 12.1, wherein the updated NTZ information includes at least one of the following: Indicates the coordinate information of the geographic region, and indicates whether the NTZ is applicable to the geographic region's flag values. Information associated with one or more permitted transmission frequency bands, or Information associated with one or more restricted transmission frequency bands, or Information related to the time period to which NTZ applies.

[0255] Example 12.3. The apparatus of Example 12.2 further includes: A component used by the UE to avoid performing cell search or transmission in a geographical area.

[0256] Example 12.4. The apparatus of Example 12.3, wherein the components for avoiding cell search or transmission in a geographic area are also based on flag values.

[0257] An apparatus according to any one of Examples 12.5, 12.3, or 12.4, wherein the components for avoiding cell search or transmission within a geographic area include: A component used by the UE to avoid performing cell search or transmission in any of one or more restricted transmission bands.

[0258] Example 12.6. An apparatus of any one of Examples 12.3-12.5, wherein the components for avoiding cell search or transmission in a geographic area include: A component used to avoid performing cell searches or transmissions in a geographic area during the time period in which NTZ applies.

[0259] Example 12.7. The apparatus of any one of Examples 12.2-12.6 further includes: A component used by a UE to transmit communication signals using frequency bands outside of one or more restricted transmission frequency bands.

[0260] Example 12.8. The apparatus of Example 12.7, wherein the components for transmitting communication signals include: A component for transmitting communication signals using frequency bands outside of one or more restricted transmission frequency bands during the applicable time period of NTZ.

[0261] Example 12.9. The apparatus of any one of Examples 12.2-12.8 further includes: A component used by a UE to transmit communication signals using frequency bands in one or more permitted transmission frequency bands.

[0262] Example 12.10. The apparatus of Example 12.9, wherein transmitting communication signals includes: A component for transmitting communication signals using frequency bands in one or more permitted transmission frequency bands during the time period applicable to the NTZ.

[0263] Example 13. A non-transitory processor-readable medium comprising program code that, when executed by one or more processors, causes the one or more processors to perform at least one of the methods described in Examples 1.1-1.6.

[0264] Example 14. A non-transitory processor-readable medium comprising program code that, when executed by one or more processors, causes the one or more processors to perform at least one of the methods described in Examples 2.1-2.8.

[0265] Example 15. A non-transitory processor-readable medium comprising program code that, when executed by one or more processors, causes the one or more processors to perform at least one of the methods described in Examples 3.1-3.5.

[0266] Example 16. A non-transitory processor-readable medium comprising program code that, when executed by one or more processors, causes the one or more processors to perform at least one of the methods described in Examples 4.1-4.10.

[0267] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to employ this disclosure differently with virtually any suitable detailed structure. Throughout the description of the accompanying drawings, the same reference numerals may refer to similar or identical elements.

[0268] The phrases “in one aspect,” “in all aspects,” “in all dimensions,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects under this disclosure. The phrase “multiple” may refer to two or more.

[0269] The phrases “in one embodiment,” “in an embodiment,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments according to this disclosure. The phrase in the form of “A or B” means “(A), (B), or (A and B)”. The phrase in the form of “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)”.

[0270] Any method, program, algorithm, or code described herein can be translated into or expressed in a programming language or computer program. As used herein, the terms “programming language” and “computer program” each include any language used to specify instructions to a computer, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages ​​that specify their own programs, and all first-, second-, third-, fourth-, fifth-, and more generation computer languages. Databases and other data schemas, and any other meta-languages, are also included. There is no distinction between languages ​​that are interpreted, compiled, or use compilation and interpretation methods. There is no distinction between compiled and source versions of a program. Therefore, a reference to a program in which a programming language can exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. A reference to a program can encompass the actual instructions and / or the intent of those instructions.

[0271] While various aspects of this disclosure have been shown in the accompanying drawings, they are not intended to be limited thereto, as the scope of this disclosure is intended to be as broad as will be permitted in the art, and similarly, when reading the specification. Therefore, the above description should not be construed as restrictive, but merely as an example of particular aspects. Other modifications within the scope and spirit of the appended claims will be contemplated by those skilled in the art.

Claims

1. A method of an unmanned aircraft system (UAS) authorization entity, the method comprising: transmitting a non-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 unmanned aerial vehicle (UAV); and receiving a transaction reference identifier (ID) based on transmitting the NTZ information provisioning request.

2. The method of claim 1, wherein the NTZ information provisioning request further comprises a request for a subscription to a notification of a result of a delivery of the UE policy configured based on the NTZ information, and wherein the method further comprises: receiving the notification of the result of the delivery of the UE policy based on the subscription.

3. The method of 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 of 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 of any one of claims 1 to 4, wherein the NTZ information comprises at least one of: coordinate information indicating a geographic area, a flag value indicating whether a NTZ applies to a geographic area, information associated with one or more allowed transmission frequency bands, information associated with one or more restricted transmission frequency bands, or information associated with a time period for which the NTZ applies.

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

7. A method of a network exposure function (NEF) entity associated with a core network, the method comprising: receiving a non-transmission zone (NTZ) information provisioning request from an unmanned aircraft system (UAS) authorization entity 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 unmanned aerial vehicle (UAV); and transmitting a transaction reference identifier (ID) to the UAS authorization entity based on receiving the NTZ information provisioning request.

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

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

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

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

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

13. The method of any of claims 7-12, wherein the NTZ information includes at least one of: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to the geographic area, information associated with one or more allowed transmission frequency bands, information associated with one or more restricted transmission frequency bands, or information associated with a time period for which the NTZ applies.

14. The method of any of claims 7-13, wherein the NTZ information is provisioned for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UAV corresponds to the single UE, the group of UEs, or a UE 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 aircraft communications, wherein the configuring is based at least in part on non-transmission zone (NTZ) information provisioned by an unmanned aircraft system (UAS) authorization entity external to the core network; transmitting the UE policy including the NTZ information to the UE; receiving a response to the UE policy from the UE; and transmitting a notification of the response to the UE policy to a network exposure function (NEF) entity associated with the core network.

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

17. The method of claim 15 or claim 16, wherein the NTZ information includes at least one of: coordinate information indicating a geographic area, a flag value indicating whether the NTZ applies to the geographic area, information associated with one or more allowed transmission frequency bands, information associated with one or more restricted transmission frequency bands, or information associated with a time period for which the NTZ applies. ​ 18. The method of any one of claims 15 to 17, wherein the NTZ information is provisioned for a single UE, a group of UEs, or a public land mobile network (PLMN), and wherein the UE corresponds to the single UE, the group of UEs, or UEs served by the PLMN.

19. The method of 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 for a UE of an unmanned aerial vehicle (UAV), the method comprising: receiving, from a core network, a UE policy for aerial communications, the UE policy for aerial communications comprising NTZ information regarding a non-transmission zone (NTZ) in which cell search or transmission is allowed or disallowed to be performed by the UE; receiving, from the core network, an updated UE policy comprising an update to the NTZ information; and transmitting, to the core network, a response to the receiving of the updated UE policy.

21. The method of claim 20, wherein the update to the NTZ information comprises at least one of: coordinate information indicating a geographic region, a flag value indicating whether an NTZ applies to the geographic region, 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 in which the NTZ applies.

22. The method of claim 21, further comprising: avoiding, based on the update to the NTZ information, performing a cell search or transmission in the geographic region.

23. The method of claim 22, wherein the update to the NTZ information comprises the flag value, wherein avoiding performing the cell search or the transmission in the geographic region is based on the flag value.

24. The method of any one of claim 22 or claim 23, wherein avoiding performing a cell search or the transmission in the geographic region comprises: avoiding performing the cell search or the transmission in any of the one or more restricted transmission bands in the geographic region.

25. The method of any one of claims 22 to 24, wherein avoiding performing the cell search or the transmission in the geographic region comprises: avoiding performing the cell search or the transmission in the geographic region during the time period in which the NTZ applies.

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

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

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

29. The method of claim 28, wherein transmitting the communication signal using the frequency band of the one or more allowed transmission frequency bands comprises: transmitting the communication signal using the frequency band of the one or more allowed transmission frequency bands during the time period for which the NTZ applies.

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

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

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

33. A user equipment (UE) for an unmanned aerial vehicle (UAV), the UE comprising: at least one processor; and at least one memory storing instructions that, when executed by the processor, cause the UE to perform at least the method of any one of claims 20-29.

Images