WO2025172944A1

WO2025172944A1 - Network exposure function (nef) service for supporting flight planning and monitoring

Info

Publication number: WO2025172944A1
Application number: PCT/IB2025/051639
Authority: WO
Inventors: Jing Yue; Shabnam Sultana; Richárd BÁTORFI; Qian Chen; Aleksejs UDALCOVS
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2024-02-16
Filing date: 2025-02-14
Publication date: 2025-08-21
Anticipated expiration: 2026-08-16

Abstract

A method, core network node and network node for enhanced NEF service for supporting flight planning and monitoring are disclosed. According to one aspect, a NEF node (36) is provided where the NEF node (36) is configured to: receive, from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management, a flight assistance request comprising one of in-flight assistance information or pre-flight assistance information for a user equipment, UE (22), that is configured as a UAV (22), determine: one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services; and transmit at least one response to the external AF node, the at least one response comprising location information.

Description

NETWORK EXPOSURE FUNCTION (NEF) SERVICE FOR SUPPORTING FLIGHT PLANNING AND MONITORING

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to enhanced network exposure function (NEF) service for supporting flight planning and monitoring.

BACKGROUND

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

Recently, a new 3GPP Technical Specification Group Service and System Aspects SA2 Release 19 key issue on enhancement of NEF services to support service exposure and interactions between mobile network operator (MNOs) and unmanned aircraft system traffic management (UTM) functions has been considered.

Key Issue on enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions (corresponds to clause 5.1 in Technical Report (TR) 23.700-59 (VO.1.0).)

In this key issue, the following aspects are required to be studied:

- whether and how to enhance NEF services to support service exposure and interactions between Mobile Network Operators (MNOs) and unmanned aircraft systems traffic management (UTM) functions for supporting, i.e.;

Pre-mission flight planning and in-mission flight monitoring for unmanned or uncrewed aerial vehicles (UAVs);

C2 communication reliability; and

The scenario of multiple Uncrewed Aerial System Service Supplier (USS) serving different geographical areas corresponding to the UAV flight path.

NOTE: In the scope of this key issue, UTM may represent any authorized aviation application function (AF) that may require interaction with the MNO for the functions listed above. There is no existing mechanism to address the challenges listed above directly.

Although the new SA2 Release 19 key issue on enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions was considered, there is no existing mechanism to address the challenges of the listed study aspects, e.g., whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for supporting pre-mission flight planning and in-mission flight monitoring for UAVs.

SUMMARY

Some embodiments advantageously provide methods, core nodes and network nodes for enhanced NEF service for supporting flight planning and monitoring.

Some embodiments solve problems considered by the study aspect “Pre-mission flight planning and in-mission flight monitoring for UAVs” proposals to enhance NEF with new services. Some embodiments address:

• Pre-mission flight planning assist service; and/or

• In-mission flight monitoring assist service.

The corresponding procedures by using the assist service for supporting premission flight planning and in-mission flight monitoring for UAVs are given.

Some embodiments solve problems considered by the study aspect “Pre-mission flight planning and in-mission flight monitoring for UAVs”, proposals to enhance NEF with new services, include pre-mission flight planning assist service and in-mission flight monitoring assist service.

Some embodiments use the assist service for supporting pre-mission flight planning and in-mission flight monitoring for UAVs.

The NEF with new services may be used to assist the USS/UTM plan flight routes/paths and monitor in-mission flights, e.g., UAV location monitoring, fight route/path monitoring, flight environment monitoring, Ranging/Sidelink positioning location monitoring.

The solution on Support Pre-Mission Planning and In-Mission Monitoring Flight (Solution#!) has been approved and added to 3GPP Technical Report (TR) 23.700-59 (VO.2.0).

Some embodiments disclosed herein enhance Solution#! in TR 23.700-59 (VO.2.0) by: ■ Adding description on subscription request to the new services provided by the NEF for In-mission flight monitoring assist; and/or by

■ Enhancing the Movement Behavior Analytics parameters.

Some embodiments enhance the Solution#! in 3GPP TR 23.700-59 (VO.2.0) by adding description on subscription request to the new services provided by the NEF for In-mission flight monitoring assist, and enhancing the Movement Behavior Analytics parameters.

According to one aspect of the present disclosure, a method implemented by a network exposure function, NEF, node is provided. A flight assistance request comprising one of in-flight assistance information or pre-flight assistance information for a user equipment, UE, that is configured as a UAV is received from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management. The following are determined: one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services. At least one response to the external AF node is transmitted where the at least one response comprises location information.

According to one or more embodiments of this aspect, the determining of one or more services comprising sending a movement behavior analytics request to an analytics network function to request movement behavior information related to the UE where the movement behavior analytics request comprises one or more of: an analytics identifier; a preferred orientation of location information; a granularity of location information; analytics filter information; a preferred level of accuracy of analytics; and an analytics target period indicating a time period over which statistics are requested.

According to one or more embodiments of this aspect, the movement behavior analytics request is a subscription type request or a single notification type request.

According to one or more embodiments of this aspect, the granularity of location information comprising one or more of a longitude, a latitude, an altitude and a height level.

According to one or more embodiments of this aspect, the preferred orientation of location information comprises one or more of horizontal information, vertical information and a number of objects.

According to one or more embodiments of this aspect, the analytics network function is a network data analytics function, NWDAF. According to one or more embodiments of this aspect, the flight assistance request is a subscription type request or a single notification type request.

According to one or more embodiments of this aspect, the in-flight assistance information comprises one or more of: a location of the UE; an indication of whether the UE is following an assigned flight path; a presence of the UE in a geographic area; and information of aerial UEs in the geographic area.

According to one or more embodiments of this aspect, the pre-flight assistance information comprising an indication of at least one flight path from a plurality of flight paths.

According to one or more embodiments of this aspect, the one or more services comprising one or both of a UAV tracking service and Gateway Mobile Location Center, GMLC, location service.

According to one or more embodiments of this aspect, the in-flight assistance information is configured to assist the external AF node in monitoring a UAV in flight; the pre-flight assistance information is configured to assist the external AF node in planning a flight path for a UAV; and the external AF node is one of an uncrewed aerial system, UAS, service supplier, USS or an uncrewed aerial system traffic management, UTM.

According to one or more embodiments of this aspect, one or more services correspond to one or more third-generation partnership projects, 3GPP, services provided by at least one network that is associated with the NEF node.

According to another aspect of the present disclosure, a network exposure function, NEF, node is provided. The NEF node is configured to receive, from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management, a flight assistance request comprising one of in-flight assistance information or pre-flight assistance information for a user equipment, UE, that is configured as a UAV, and determine: one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services, and transmit at least one response to the external AF node, the at least one response comprising location information.

According to one or more embodiments of this aspect, the analytics network function is a network data analytics function, NWDAF.

According to one or more embodiments of this aspect, the flight assistance request is a subscription type request or a single notification type request.

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

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

FIG. 2 is a block diagram of several entities of the communication system of FIG. 1 according to some embodiments of the present disclosure;

FIG. 3 is a flowchart of an example process in a core node for enhanced NEF service for supporting flight planning and monitoring;

FIG. 4 is a flowchart of an example process in a network node for enhanced NEF service for supporting flight planning and monitoring;

FIG. 5 is a flowchart of another example process in a core node for enhanced NEF service for supporting flight planning and monitoring;

FIG. 6 is a flowchart of another example process in a network node for enhanced NEF service for supporting flight planning and monitoring;

FIG. 7 is a flowchart of another example process in a core node according to some embodiments of the present disclosure;

FIG. 8 is a block diagram of a network configuration for enhanced NEF service for supporting flight planning and monitoring;

FIG. 9 is a flow diagram for enhanced NEF service for supporting flight planning and monitoring; and

FIG. 10 is another flow diagram for enhanced NEF service for supporting flight planning and monitoring.

DETAILED DESCRIPTION

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to enhanced NEF service for supporting flight planning and monitoring.

Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description. As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

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

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

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

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) and UAV are used interchangeably, and may be referred to as UAV UE. As used herein, a UE may be or may be installed on an unmanned aerial vehicle or uncrewed aerial vehicle (UAV), such that, the UE may be an aerial UE or a UE with an aerial subscription.. The UE herein may be any type of UAV, wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

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

Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and/or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide enhanced NEF service for supporting flight planning and monitoring.

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

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

The communication system 10 includes intermediate network 30 that may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

A network node 16 may be configured to include a flight planning unit 32 which may be configured to perform one or more network node 16 functions as described herein such as, for example, determine pre-mission flight planning service information for a premission flight planning assistance request. A core node 36 in the core network 14 may include a NEF unit 34 that may be configured to perform one or more core node 36 functions as described herein. For example, the NEF unit 34 may be configured to determine services to fulfill a pre-mission flight planning assistance request and network functions to fulfill the request. In one or more embodiments, the core node 36 is a NEF (also referred to herein as “NEF node”), where the NEF may include a uncrewed aerial system network function, UAS NF, i.e., the UAS NF is part of the NEF. As used herein, “pre-mission flight planning” may be referred to as “pre-flight planning.” As used herien, “in-mission flight monitoring” may be referred to as “in-flight monitoring.”

Example implementations, in accordance with an embodiment, of the UE 22, core node 36 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2. The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the UE 22 and other entities in communication system 10. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection that may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

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

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include a flight planning unit 32 which may be configured to perform one or more network node 16 functions described herein such as, for example, determining pre-mission flight planning service information for a pre-mission flight planning assistance request.

The communication system 10 includes the core node 36 already referred to. Core node 36 may include similar hardware and/or software as described with respect to network node 16. For example, the core node 36 includes processing circuitry 94 which may include a processor and memory. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor may be configured to access (e.g., write to and/or read from) memory, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Processing circuitry 94 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by core node 36. In some embodiments, the processing circuitry 94 may execute computer instructions provided by software that causes a processor and/or processing circuitry 94 to perform the processes described herein with respect to core node 36. The software may be executable by the processing circuitry 94.

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

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

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

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to UE 22.

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

In FIG. 2, the wireless connection 64 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the UE 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the UE 22.

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

The network node 16 includes hardware enabling it to communicate with UE 22 and other entities in communication system 10. A connection may be direct or pass through a core network (like core network 14 in FIG. 1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 22 includes hardware and software, which is stored in or accessible by UE 22 and executable by the UE’s processing circuitry 84. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 22.

FIG. 3 is a flowchart of an example process in a core node 36 for enhanced NEF service for supporting flight planning and monitoring. One or more blocks described herein may be performed by one or more elements of core node 36 such as by one or more of processing circuitry 94 (including the NEF unit 34). Core node 36 is configured to receive a request for pre-mission flight planning assistance for a UE 22 configured as an unmanned aerial vehicle, UAV 22 (e.g., uncrewed aerial vehicle) (Block SI 16). The process includes determining services to fulfill the request and network functions to fulfill the request (Block SI 18).

In some embodiments, the core node 36 is further configured to reject the request when predictions relative to flight planning are unavailable. In some embodiments, the process includes mapping a geographical area to a cell. In some embodiments, the process includes receiving movement behavior analytics from a network data analytics function, NWDAF. In some embodiments, the process includes generating assistance information for pre-mission flight planning.

FIG. 4 is a flowchart of an example process in a network node 16 for enhanced NEF service for supporting flight planning and monitoring. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the flight planning unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to determine pre-mission flight planning service information for a pre-mission flight planning assistance request (Block S120). The process includes sending a request for premission flight planning assistance to a network exposure function, NEF (Block S122).

In some embodiments, the request includes at least one of a start and end point of a flight, route candidates and route requirements. In some embodiments, receiving from the NEF (e.g., core node 36) a response to the request, the response including one of acceptance and rejection of the request. In some embodiments, receiving flight planning assistance information from the NEF. In some embodiments, the flight assistance planning information includes an indication of services related to the request.

FIG. 5 is a flowchart of an example process in a core node 36 for enhanced NEF service for supporting flight planning and monitoring. One or more blocks described herein may be performed by one or more elements of core node 36 such as by one or more of processing circuitry 94 (including the NEF unit 34). Core node 36 is configured to receive, from one of an uncrewed aerial system service supplier, USS, and an unmanned aircraft system traffic management, UTM, function, an assist request and a subscription request for pre-mission flight planning assistance for a UE 22 configured as an unmanned aerial vehicle, UAV 22 (Block S124). The process includes determining services to fulfill the request and network functions to fulfill the request (Block S126). The process further includes transmitting responses to the one of the USS and the UTM, the responses including location information (Block S128).

In some embodiments, the core node 36 is further configured to reject the request when predictions relative to flight planning are unavailable. In some embodiments, the method includes mapping a geographical area to a cell. In some embodiments, the method includes receiving movement behavior analytics from a network data analytics function, NWDAF. In some embodiments, the method includes generating assistance information for pre-mission flight planning. In some embodiments, the process includes determining a preferred granularity of the location information. In some embodiments, the process includes determining a preferred orientation of the location information.

FIG. 6 is a flowchart of an example process in a network node 16 for enhanced NEF service for supporting flight planning and monitoring. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the flight planning unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to determine pre-mission flight planning service information for a pre-mission flight planning assistance or subscription request (Block S130). The process includes sending the assist request or the subscription request for pre-mission flight planning assistance to a network exposure function, NEF (e.g., core node 36) (Block S132). The process also includes receiving responses from the NEF, the responses including location information and indicating services determined to fulfill the one of the assistance request or the subscription request (Block S134).

In some embodiments, the request includes at least one of a start and end point of a flight, route candidates and route requirements. In some embodiments, receiving from the NEF a response to the request, the response including one of acceptance and rejection of the request. In some embodiments, the process includes receiving flight planning assistance information from the NEF. In some embodiments, the flight assistance planning information includes an indication of services related to the request. In some embodiments, the process includes determining a preferred granularity of the location information. In some embodiments, the process includes determining a preferred orientation of the location information.

FIG. 7 is a flowchart of another example process in a core node 36 (e.g., NEF) according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of core node 36 such as by one or more of processing circuitry 94 (including the NEF unit 34). Core node 36 is configured to receive (Block S136), from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management, a flight assistance request comprising one of inflight assistance information or pre-flight assistance information for a user equipment, UE 22, that is configured as a UAV 22, as described herein. Core node 36 is configured to determine (Block S138): one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services, as described herein.

Core node 36 is configured to transmit at least one response to the external AF node, the at least one response comprising location information.

According to one or more embodiments, the determining of one or more services comprising sending a movement behavior analytics request to an analytics network function to request movement behavior information related to the UE, where the movement behavior analytics request comprising one or more of: an analytics identifier; a preferred orientation of location information; a granularity of location information; analytics filter information; a preferred level of accuracy of analytics; and an analytics target period indicating a time period over which statistics are requested.

According to one or more embodiments, the movement behavior analytics request is a subscription type request or a single notification type request.

According to one or more embodiments, the granularity of location information comprising one or more of a longitude, a latitude, an altitude and a height level.

According to one or more embodiments, the preferred orientation of location information comprises one or more of horizontal information, vertical information and a number of objects.

According to one or more embodiments, the analytics network function is a network data analytics function, NWDAF.

According to one or more embodiments, the flight assistance request is a subscription type request or a single notification type request. According to one or more embodiments, the in-flight assistance information comprises one or more of: a location of the UE 22; an indication of whether the UE 22 is following an assigned flight path; a presence of the UE in a geographic area; and information of aerial UEs 22 in the geographic area.

According to one or more embodiments, the pre-flight assistance information comprising an indication of at least one flight path from a plurality of flight paths.

According to one or more embodiments, the one or more services comprising one or both of a UAV 22 tracking service and Gateway Mobile Location Center, GMLC, location service.

According to one or more embodiments, the in-flight assistance information is configured to assist the external AF node in monitoring a UAV 22 in flight; the pre-flight assistance information is configured to assist the external AF node in planning a flight path for a UAV 22; and the external AF node is one of an uncrewed aerial system, UAS, service supplier, USS or an uncrewed aerial system traffic management, UTM.

According to one or more embodiments, one or more services correspond to one or more third-generation partnership projects, 3GPP, services provided by at least one network that is associated with the NEF node.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for enhanced NEF service for supporting flight planning and monitoring.

One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, flight planning unit 32, communication interface 60, etc. One or more UE 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, radio interface 82, etc. One or more core node 36 functions described below may be performed by one or more of processing circuitry 94, NEF unit 34, etc.

Referring to FIG. 8, an UAV 22 (or via its paired UAV-C 22) (which is or may be part of a UE 22) may communicate with the USS 102/UTM 103. USS 102 is an entity that is or may be provided in a network node 16 (hence its reference as USS 102/UTM 103) that provides services to support the safe and efficient use of airspace by providing services to the operator/pilot of a unmanned aerial system (UAS) in meeting UTM operational requirements. A USS 102 may provide any subset of functionality to meet the provider's business objectives (e.g. UTM, Remote Identification). UTM 103 is a system that may safely and efficiently integrate the flying UAV 22 along with other airspace users. It provides a set of functions and services for managing a range of autonomous vehicle operations (e.g., authenticating UAV 22, authorizing UAS services, managing UAS policies, and controlling UAV 22 traffics in the airspace).

The USS 102/UTM 103 may request service from NEF (e.g., from the UAS NF of the NEF) for supporting the application layer services. The NEF 104 may interact with 5GC NFs (e.g. GMLC 108, NWDAF 106) to collect information/analytics and generate assistance information to fulfill the request from the USS 102/UTM 103.

Enhanced NEF with new services are proposed, including:

• Pre-mission flight planning assist service; and/or

• In-mission flight monitoring assist service.

Procedures for using the assist service for supporting pre-mission flight planning and in-mission flight monitoring for UAVs 22 are given and are explained with reference to FIG. 9, using the enumerated steps as follows:

1. The UAV 22 (or UAV-C 22) establishes a PDU Session for communication with the USS 102/UTM 103, for example, as described in clause 5.2.3 of 3GPP Technical Standard (TS) 23.256;

2. The UAV 22 (or via its paired UAV-C 22) requests Pre-mission flight planning service from USS 102/UTM 103. The request message includes identifier of the UAV 22 (e.g., generic public subscription identifier (GPSI), Civil Aviation Administration (CA)A-Level UAV ID), information of the starting and ending points for the flight, requirements on the flight route (e.g. on time), and may include candidate flight route(s) if available; For example, inside the request for pre-mission flight planning (i.e., pre-flight planning request), the USS 102 may provide “requirements on the flight path (e.g., on time, fastest, shortest), candidate flight path(s) (either received from the UAV 22 or locally derived at the USS 102/UTM 103) and accuracy level of predictions relevant to the flight planning;

3. The USS 102/UTM 103 derives information for the Pre-mission flight planning request and decides to request assistance information from NEF 104;

NOTE: The content of Pre-mission flight planning service information derived at USS 102 is beyond the scope of this disclosure.

4. The USS 102/UTM 103 sends Pre-mission flight planning assist request to NEF 104. The request message includes identifier of the UAV(s) 22 (e.g., GPSI(s)), information of the starting and ending points for the flight, requirements on the flight route (e.g. on time), candidate flight route(s) (received from the UAV 22 or local derived at the USS 102/UTM 103), and accuracy level of predictions relevant to the flight planning;

5. The NEF 104 maps parameters included in the request from the USS 102/UTM 103 to information used by the 3GPP system (e.g., map the geographical area into an area of interest that is represented by a list of Cell IDs, gNB IDs or tracking area identity (TAIs)). The NEF 104 determines services needed for the request and relevant NFs, e.g. NEF service on UAV 22 tracking and mode (List of Aerial UEs 22 in a geographic area), network data analytics function (NWDAF 106) analytics service (Movement Behaviour analytics), and gateway mobile location center (GMLC 108) location service. For example, based on the maps parameters, NEF 104 determines one or more of TAs, cells, etc., in order to collect data using the selected NEF services;

6. If the NEF 104 cannot satisfy the requirements on flight planning (e.g. cannot get predictions relevant to the flight planning from NWDAF 106 with the required accuracy level), the NEF 104 responds to the USS 102/UTM 103 to reject the Pre-mission flight planning assist request, and may include the detailed reason;

7. If receiving the reject response in step 6, the USS 102/UTM 103 responses to the UAV 22 (or its paired UAV-C 22) to reject the Pre-mission flight planning request, may include the detailed reason if available;

8. The NEF 104 performs steps 2-5 in clause 5.3.4 of 3GPP TS 23.256, and filtered list of UAVs 22 in the interest areas;

9. The NEF 104 subscribes/requests for notification on Movement Behavior analytics provided by NWDAF 106, for example, as defined in clause 6.21.4 of 3GPP TS 23.288. The subscribe/request message includes an identifier of the UAV(s) 22 (e.g., GPSI(s)) in the interest areas obtained in step 4. The other parameters included in the request are described in clause 6.2.3;

10. The NEF 104 may request location services from GMLC 108 (e.g., request for GMLC service(s)), for example as defined in 3GPP TS 23.273, for additional location information if the information/analytics obtained from steps 8 and 9 is not sufficient; 11. The NEF 104 generates assistance information for pre-mission flight planning based on the information and analytics from steps 4 and 5. The assistance information may be the best matched route among the ones provided from the USS 102/UTM 103 in step 2. For example, once the NEF 104 has collected data/received responses from the invoked services and NFs, the NEF 104 may select data that is relevant from the candidate flight paths previously provided by the USS 102 in the request or the NEF 104 can make a “suggestion” as to a suitable flight path for the USS 102 provided start and destination points from 5GS point of view. In one or more embodiments, “best matched route” may correspond to a route or path for a UAV 22 (e.g., from starting point to destination point) with the least potential collisions with other UAV(s) 22, among various paths provided by the USS 102/UTM 103;

12. The NEF 104 responses to the USS 102/UTM 103 with the assistance information;

13. The USS 102/UTM 103 decides flight planning by using the assistance information and flight planning mechanism which is out of scope; and/or

14. The USS 102/UTM 103 sends a response to the UAV 22 (or its paired UAV-C 22) with the planned flight route.

In this clause, the Solution#! in TR 23.700-59 [1] is enhanced by adding description on subscription request to the new services provided by the NEF 104 for Inmission flight monitoring assist, and enhancing the Movement Behavior Analytics parameters.

FIG. 10 is a flowchart showing an example procedure for NEF 104 assist of inmission flight monitoring, and is described with reference to the following steps:

1. The USS 102/UTM 103 sends In-mission flight monitoring assist request or subscription request to NEF 104 (e.g., core node 36). The request message includes identifier of the UAV 22 (e.g., GPSI) and information of the flight route, monitoring mode (e.g., UAV location monitoring, fight route monitoring, flight environment monitoring, Ranging/Sidelink positioning location monitoring), report requirements (e.g., report format (event triggered or periodically), report monitoring results, report assist information based the monitoring results);

2. NEF 104 maps parameters included in the request from the USS 102/UTM 104 to information used by the 3 GPP system. The NEF 104 determines services needed for the request and relevant NFs, e.g. NEF service on UAV tracking (UAV location reporting mode, UAV presence monitoring mode, List of Aerial UEs 22 in a geographic area), GMLC service (SL-MT-LR for periodic, triggered Location Events);

3. If the NEF 104 cannot provide the request assist for In-mission flight monitoring, the NEF responses to the USS 102/UTM 103 to reject the Inmission flight monitoring assist request, may include the detail reason if available;

4. For UAV location monitoring, the NEF 104 performs steps 2-5 in clause 5.3.2 of 3GPP TS 23.256;

5. For fight route monitoring, the NEF 104 performs steps 2-4 in clause 5.3.3 of 3GPP TS 23.256. Upon to the request in step 1, the NEF 104 may compare the monitored flight route with the planned fight route (if provided in step 1);

6. For flight environment monitoring, the NEF 104 performs steps 2-5 in clause 5.3.4 of 3GPP TS 23.256;

7. For Ranging/Sidelink positioning location monitoring, the NEF 104 requests GLMC service for Ranging/Sidelink Positioning location results as described in clause 6.20.4 of 3GPP TS 23.273, the procedure of sidelink mobile terminating location request (SL-MT-LR) for periodic, triggered Location Events; and/or

8. The NEF 104 responds or notifies the USS 102/UTM 103 the monitoring results (e.g. USS 102/UTM 103 the location of the target UAV 22, and sends an indication on whether the UAV 22 is flight in right route, the UAV presence in a geographic area, the information of aerial UEs 22 in the same geographic area of the UAV 22).

Parameters in Request for Movement Behavior Analytics

The USS 102 acting as an Application Function communicates with the NEF 104 which, for example, corresponds to the NF consumer in clause 6.21.4 of 3GPP TS 23.288.

The USS 102 may either subscribe to notifications from the NEF 104 (i.e., a Subscribe-Notify model) or request a single notification from the NEF 104 (i.e., a Request-Response model). The USS 102 request may contain one or more of the following parameters:

Analytics ID = "movement behaviour";

- Target of Analytics Reporting: any UE 22; - Analytics Filter Information:

Area of Interest (AOI): restricts the scope of the movement behaviour analytics to the provided area. The AOI may be described as shown in clause 5.5 of 3GPP TS 23.273;

Optionally, the list of analytics subsets that are requested among those specified in clause 6.21.3 of 3GPP TS 23.288;

- An Analytics target period indicates the time period over which the statistics or predictions are requested;

- Optionally, preferred level of accuracy of the analytics;

- Optionally, preferred level of accuracy per analytics subset (see clause 6.21.3 of 3GPP TS 23.288);

- Optionally, preferred granularity of location information: "longitude, latitude and height level";

Optionally, preferred orientation of location information: ("horizontal", "vertical", “height”, “all”)"; and/or- Optionally, maximum number of objects.

Some Examples

Example Al. A network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive, from one of an uncrewed aerial system service supplier, USS, and an unmanned aircraft system traffic management, UTM, function, an assist request and a subscription request for pre-mission flight planning assistance for a UE configured as an unmanned aerial vehicle, UAV; determine services to fulfill the request and network functions to fulfill the request; and transmit responses to the one of the USS and the UTM, the responses including location information.

Example A2. The network node of Example Al, wherein the network node, radio interface and/or processing circuitry are further configured to reject the request when predictions relative to flight planning are unavailable.

Example A3. The network node of any of Examples Al and A2, wherein the network node, radio interface and/or processing circuitry are configured to map a geographical area to a cell. Example A4. The network node of any of Examples A1-A3, wherein the network node, radio interface and/or processing circuitry are further configured to receive movement behavior analytics from a network data analytics function, NWDAF.

Example A5. The network node of any of Examples A1-A4, wherein the network node, radio interface and/or processing circuitry are further configured to generate assistance information for pre-mission flight planning.

Example A6. The network node of any of Examples A1-A5, wherein the network node, radio interface and/or processing circuitry are further configured to determine a preferred granularity of the location information.

Example A7. The network node of any of Examples A1-A6, wherein the network node, radio interface and/or processing circuitry are further configured to determine a preferred orientation of the location information.

Example Bl. A method implemented in a network node, the method comprising: receiving, from one of an uncrewed aerial system service supplier, USS, and an unmanned aircraft system traffic management, UTM, function, an assist request and a subscription request for pre-mission flight planning assistance for a UE configured as an unmanned aerial vehicle, UAV; determining services to fulfill the request and network functions to fulfill the request and transmitting responses to the one of the USS and the UTM, the responses including location information.

Example B2. The method of Example Bl, further comprising rejecting the request when predictions relative to flight planning are unavailable.

Example B3. The method of any of Examples B 1 and B2, further comprising mapping a geographical area to a cell.

Example B4. The method of any of Examples B 1-B3, further comprising receiving movement behavior analytics from a network data analytics function, NWDAF.

Example B5. The method of any of Examples B 1-B4, further comprising generating assistance information for pre-mission flight planning.

Example B6. The method of any of Examples B 1-B5, further comprising determining a preferred granularity of the location information.

Example B7. The method of any of Examples B 1-B6, further comprising determining a preferred orientation of the location information. Example Cl. A network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine pre-mission flight planning service information for a pre-mission flight planning assistance or subscription request; and send the assist request or the subscription request for pre-mission flight planning assistance to a network exposure function, NEF; and receive responses from the NEF, the responses including location information and indicating services determined to fulfill the one of the assistance request or the subscription request.

Example C2. The network node of Example Cl, wherein the request includes at least one of a start and end point of a flight, route candidates and route requirements.

Example C3. The network node of any of Examples Cl and C2, wherein receiving from the NEF a response to the request, the response including one of acceptance and rejection of the request.

Example C4. The network node of any of Examples C1-C3, wherein the network node, radio interface and/or processing circuitry are configured to receive flight planning assistance information from the NEF.

Example C5. The network node of Example C4, wherein the flight assistance planning information includes an indication of services related to the request.

Example C6. The network node of any of Examples C1-C5, wherein the network node, radio interface and/or processing circuitry are further configured to determine a preferred granularity of the location information.

Example C7. The network node of any of Examples C1-C6, wherein the network node, radio interface and/or processing circuitry are further configured to determine a preferred orientation of the location information.

Example DI. A method implemented in a network node, the method comprising: determining pre-mission flight planning service information for a pre-mission flight planning assistance or subscription request; and sending the assist request or the subscription request for pre-mission flight planning assistance to a network exposure function, NEF; and receiving responses from the NEF, the responses including location information and indicating services determined to fulfill the one of the assistance request or the subscription request. Example D2. The method of Example DI, wherein the request includes at least one of a start and end point of a flight, route candidates and route requirements.

Example D3. The method of any of Examples DI and D2, wherein receiving from the NEF a response to the request, the response including one of acceptance and rejection of the request.

Example D4. The method of any of Examples D1-D3, further comprising receiving flight planning assistance information from the NEF.

Example D5. The method of Example D4, wherein the flight assistance planning information includes an indication of services related to the request.

Example D6. The method of any of Examples D1-D5, further comprising determining a preferred granularity of the location information.

Example D7. The method of any of Examples D1-D6, further comprising determining a preferred orientation of the location information.

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

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

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

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

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

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

STANDARDIZING THE PROPOSED SOLUTIONS

Below are non-limiting examples of how certain aspects of the proposed solutions could be implemented within the framework of a specific communication standard. In particular, the description below provides non-limiting examples of how the proposed solutions could be implemented within the framework of a 3 GPP TSG RAN standard. The changes described below are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3 GPP Specification and in other specifications or standards.

Some of the proposed change below include added material (indicated by underline) and removed material (indicated by strikethrough).

1. Discussion

The KI#1 in TR 23.700-59 on enhancement of NEF services to support service exposure and interactions between MNOs and UTM 103 functions is documented as follows: In this key issue, the following aspects are required to be studied: whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM 103 functions for supporting i.e.

Pre-mission flight planning and in-mission flight monitoring for UAVs 22. C2 communication reliability.

The scenario of multiple USS 102 serving different geographical areas corresponding to the UAV flight path.

NOTE: In the scope of this key issue, UTM 103 can represent any authorized aviation AF that may require interaction with the MNO for the functions listed above. This solution focuses on the study aspect “Pre-mission flight planning and in-mission flight monitoring for UAVs”, proposes to enhance NEF 104 for supporting pre-mission flight planning assist and in-mission flight monitoring assistance services.

2. Proposal

It is proposed to agree the following changes to 23.700-59 VO.1.0.

References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.

For a specific reference, subsequent revisions do not apply.

For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".

[3] ECC Decision (22)07 (cept.org): "Harmonised technical conditions for the usage of aerial UE for communications based on LTE and 5G NR in the bands 703-733 MHz, 832-862 MHz, 880-915 MHz, 1710- 1785 MHz, 1920-1980 MHz, 2500-2570 MHz and 2570- 2620 MHz harmonised for MFCN". 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services ".

IY21 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".

6.0 Mapping of Solutions to Key Issues

Table 6.0-1: Mapping of Solutions to Key Issues

6.X Solution #X: Support Pre-Mission Planning and In-Mission Monitoring Flight 6.X.1 Key Issue mapping

This solution addresses KI#1 aspects.

6.X.2 Description

Pre-mission flight planning and in-mission flight monitoring for UAVs 22 is one of the study aspects in KI#1. This solution proposes to enhance NEF services to provide assistance information for supporting pre-mission flight planning and in-mission flight monitoring.

6.X.3 Procedures and Parameters

6.X.3.1Procedure for NEF Assist Pre-mission Flight Planning

Procedure for NEF Assist Pre-mission Flight Planning is illustrated in FIG. 9.

1. The UAV 22 (or UAV-C) establishes a PDU Session for communication with the USS 102/UTM 103 as described in clause 5.2.3 of TS 23.256 [2],

2. The UAV 22 (or via its paired UAV-C) requests Pre-mission flight planning service from USS 102/UTM 103. The request message includes identifier of the UAV 22 (e.g. GPSI, CAA-Level UAV ID), information of the starting and ending points for the flight, requirements on the flight route (e.g. on time), and may include candidate flight route(s) if available.

3. The USS 102/UTM 103 derives information for the Pre-mission flight planning request and decides to request assistance information from NEF 104.

NOTE:The content of Pre-mission flight planning service information derived at USS 102 is out of scope.

4. The USS 102/UTM 103 sends Pre-mission flight planning assist request to NEF 104. The request message includes identifier of the UAV(s) 22 (e.g., GPSI(s)), information of the starting and ending points for the flight, requirements on the flight route (e.g. on time), candidate flight route(s) (received from the UAV 22 or local derived at the USS 102/UTM 103), and accuracy level of predictions relevant to the flight planning.

5. The NEF 104 maps parameters included in the request from the USS 102/UTM 103 to information used by the 3GPP system (e.g., map the geographical area into an area of interest that is represented by a list of Cell IDs, gNB IDs or TAIs). The NEF 104 determines services needed for the request and relevant NFs 104, e.g. NEF service on UAV tracking and mode (List of Aerial UEs 22 in a geographic area), NWDAF analytics service (Movement Behaviour analytics), GMLC location service. 6. If the NEF 104 cannot satisfy the requirements on flight planning (e.g. cannot get predictions relevant to the flight planning from NWDAF with the required accuracy level), the NEF 104 responses to the USS 102/UTM 103 to reject the Pre-mission flight planning assist request, and may include the detail reason.

7. If receiving the reject response in step 6, the USS 102/UTM 103 responses to the UAV 22 (or its paired UAV-C) to reject the Pre-mission flight planning request, may include the detail reason if available.

8. The NEF 104 performs steps 2-5 in clause 5.3.4 of TS 23.256 [2], and filter list of UAVs 22 in the areas of interest.

9. The NEF 104 subscribes/requests for notification on Movement Behaviour analytics provided by NWDAF as defined in clause 6.21.4 of TS 23.288 [Yl] . The subscribe/request message include identifier of the UAV(s) 22 (e.g., GPSI(s)) in the interest areas obtained in step 4. The other parameters included in the request are described in clause 6.X.3.3. The list of UAVs 22 in the areas of interest output from step 8 can be used as inputs for the NEF to request the NWDAF on Movement Behaviour analytics.

10. The NEF 104 may request GMLC service(s), e.g. Ranging/Sidelink positioning location as defined in clause 6.20.3 of TS 23.273. The list of UAVs 22 in the areas of interest output from step 8 can be used as inputs for the NEF 104 to request the GLMC service on Ranging/Sidelink Positioning location.

11. The NEF 104 generates assistance information for pre-mission flight planning based on the information and analytics from steps 8-10. The assistance information may be the best matched route among the ones provided from the USS 102 /UTM 103 in step 2, or potential flight route(s) if candidate flight route(s) is not provided in step 2.

12. The NEF 104 responses to the USS 102/UTM 103 with the assistance information.

13. The USS 102/UTM 103 decides flight planning by using the assistance information and flight planning mechanism which is out of scope.

14. The USS 102/UTM 103 sends response to the UAV 22 (or its paired UAV-C) with the planned flight route.

NOTE: USS 102/UTM 103 are used to represent the consumer of the enhanced NEF services in FIG. 9, the consumer can also be other entities, e.g., TPAE.

Procedure for NEF Assist In-mission Flight Monitoring

A procedure for NEF 104 assist in-mission flight monitoring is illustrated in FIG. 10. NOTE: The NFs 104 in FIG. 10 is used to represent all the other NFs 104 involved in the procedure.

1. The USS 102/UTM 103 sends In-mission flight monitoring assist request to NEF 104. The request message includes identifier of the UAV 22 (e.g., GPSI) and information of the flight route, monitoring mode (e.g., UAV location monitoring, fight route monitoring, flight environment monitoring, Ranging/Sidelink positioning location monitoring), report requirements (e.g., report format (event triggered or periodically), report monitoring results, report assist information based the monitoring results).

2. NEF 104 maps parameters included in the request from the USS 102/UTM 103 to information used by the 3GPP system. The NEF 104 determines services needed for the request and relevant NFs 104, e.g. NEF service on UAV tracking (UAV location reporting mode, UAV presence monitoring mode, Fist of Aerial UEs 22 in a geographic area), GMLC service (SE-MT-LR for periodic, triggered Eocation Events).

3. If the NEF 104 cannot provide the request assist for In-mission flight monitoring, the NEF 104 responses to the USS 102/UTM 103 to reject the In-mission flight monitoring assist request, may include the detail reason if available.

4. For UAV location monitoring, the NEF 104 performs steps 2-5 in clause 5.3.2 of TS 23.256 [2],

5. For fight route monitoring, the NEF 104 performs steps 2-4 in clause 5.3.3 of TS 23.256 [2]. Upon to the request in step 1, the NEF 104 may compare the monitored flight route with the planned fight route (if provided in step 1).

6. For flight environment monitoring, the NEF 104 performs steps 2-5 in clause 5.3.4 of TS 23.256 [2],

7. For Ranging/Sidelink positioning location monitoring, the NEF 104 requests GLMC service for Ranging/Sidelink Positioning location results as described in clause 6.20.4 of TS 23.273 [Y2], the procedure of SL-MT-LR for periodic, triggered Location Events (steps 1-20 for initiation the monitoring, steps 21-31 for monitoring periodic). The list of UAVs 22 in the areas of interest output from step 6 can be used as inputs to step 7 for NEF 104 to request GLMC service for Ranging/Sidelink Positioning location, if the UAVs 22 is unknown in the areas of interest. 8. The NEF 104 notifies the USS 102/UTM 103 the monitoring results (e.g., the location of the target UAV 22, indication on whether the UAV 22 is flight in right route, the UAV 22 presence in a geographic area, the information of aerial UEs 22 in the same geographic area of the UAV 22).

Steps 4-8 may repeat for report monitoring results periodically.

NOTE: USS 102/UTM 103 are used to represent the consumer of the enhanced NEF services in FIG. 10, the consumer can also be other entities, e.g., TPAE.

6.X.3.3Parameters in Request for Movement Behaviour Analytics

The USS 102 acting as an Application Function communicates with the NEF 104 which corresponds to the NF consumer in clause 6.21.4 of TS 23.288 [Yl].

The USS 102 can either subscribe to notifications from the NEF 104 (i.e., a Subscribe- Notify model) or request a single notification from the NEF 104 (i.e. a Request-Response model). The USS 102 request contains the following parameters:

Analytics ID = "movement behaviour";

Target of Analytics Reporting: any UE 22;

Analytics Filter Information:

Area of Interest (AOI): restricts the scope of the movement behaviour analytics to the provided area. The AOI may be described as shown in clause 5.5 of TS 23.273 [Y2];

Optionally, the list of analytics subsets that are requested among those specified in clause 6.21.3 of TS 23.288 [Yl];

An Analytics target period indicates the time period over which the statistics or predictions are requested;

Optionally, preferred level of accuracy of the analytics;

Optionally, preferred level of accuracy per analytics subset (see clause 6.21.3 of TS 23.288 [Yl]);

Optionally, preferred granularity of location information: "longitude and latitude level";

Optionally, preferred orientation of location information: ("horizontal", "vertical", "both")"; and

Optionally, maximum number of objects.

6.X.4 Impacts on services, entities and interfaces

UAS NF/NEF 104:

■ Enhance for supporting pre-mission flight planning assistance service. ■ Enhance for supporting in-mission flight monitoring assistance service.

NWDAF:

■ Enhance the inputs and the outputs of Movement Behaviour Analytics. USS 102/ AF:

■ Enhance for supporting UAV/UAV-C trigger pre-mission flight planning service.

■ Enhance for supporting in-mission flight monitoring service.

Note: it is FFS other possible impacts related to services, entities and interfaces.

1A. Discussion

Solution #1 proposed to enhance NEF services to support service exposure and interactions between MNOs and UTM 103 functions for supporting pre-mission flight planning and in-mission flight monitoring for UAVs 22.

The description below proposes to update the solutions by adding description on subscription request to the new services provided by the NEF 104 for In-mission flight monitoring assist, and to solve the EN on “The final list of parameters is FFS.” by enhancing the Movement Behaviour Analytics parameters.

2A. Proposal

It is proposed to agree the following changes to TR 23.700-59 V0.2.0.

6.1.3.2 Procedure for NEF Assist In-mission Flight Monitoring

A procedure for NEF assist in-mission flight monitoring is illustrated in FIG. 10.

NOTE 1: The NFs 110 in FIG. 10 represents all the other NFs beside GMLC 108 and

NEF/UAS NF 104 involved in the procedure.

1. The USS/UTM sends In-mission flight monitoring assist request or subscription request to NEF 104. The request message includes identifier of the UAV 22 (e.g., GPSI) and information of the flight route, monitoring mode (e.g., UAV location monitoring, fight route monitoring, flight environment monitoring, Ranging/Sidelink positioning location monitoring), report requirements (e.g. report format (event triggered or periodically), assistance information (e.g., the monitoring results, information generated from the monitoring results)), and may include planned fight route if fight route monitoring, list of UAVs 22 in the areas of interest if flight environment monitoring, preset value for distance if Ranging/Sidelink positioning location monitoring.

2. NEF 104 maps the parameters in the request from the USS 102/UTM 103 to information used by the 3GPP system. The NEF 104 determines services needed for the request and relevant NFs, e.g. NEF service on UAV tracking (UAV location reporting mode, UAV presence monitoring mode, List of Aerial UEs 22 in a geographic area), GMLC service (Ranging/Sidelink Positioning location).

3. If the NEF 104 cannot provide the requested assistance information for In-mission flight monitoring, the NEF 104 responses to the USS 102 /UTM 103 to reject the Inmission flight monitoring assistance request, may include the detail reason if available.

4. For UAV location monitoring, the NEF 104 executes steps 2-5 in clause 5.3.2 of TS 23.256 [2] to obtain the location of the target UAV 22.

5. For fight route monitoring, the NEF 104 executes steps 2-4 in clause 5.3.3 of

TS 23.256 [2]. Upon to the request in step 1 for reporting, the NEF 104 may compare the monitored flight route with the planned fight route (if provided in step 1) and generate assistance information on whether the UAV 22 is flight in right route.

6. For flight environment monitoring, the NEF 104 executes steps 2-5 in clause 5.3.4 of TS 23.256 [2] to obtain the information of aerial UEs 22 in the same geographic area of the target UAV.

7. For Ranging/Sidelink positioning location monitoring, the NEF requests GLMC service for Ranging/Sidelink Positioning location results as described in clause 6.20.4 of TS 23.273 [7], the procedure of SL-MT-LR for periodic, triggered Location Events (steps 1-20 for initiation the monitoring, steps 21-31 for monitoring periodic). The list of UAVs 22 in the areas of interest output from step 6 can be used as inputs to step 7 for NEF 104 to request GLMC service for Ranging/Sidelink Positioning location, if the UAVs is unknown in the areas of interest.

8. The NEF 104 responses or notifies the USS 102/UTM 103 the monitoring results (e.g. the location of the target UAV 22, indication on whether the UAV 22 is flight in right route, the target UAV 22 presence in areas of interest, the information of aerial UEs 22 in the same geographic area of the target UAV 22, the distance of other UAVs 22 and the target UAV 22 and whether the distance is smaller than a preset value).

Steps 4-8 may be repeated for report monitoring results periodically.

NOTE 2: USS 102/UTM 103 are used to represent the consumer of the enhanced

NEF services in FIG. 10, the consumer can also be other entities, e.g., TPAE.

6.1.3.3 Parameters in Request for Movement Behaviour Analytics

The USS 102 acting as an Application Function communicates with the NEF 104 which corresponds to the NF consumer in clause 6.21.4 of TS 23.288 [6].

Editor's note: The final list of parameters is FFS. The USS 102 can either subscribe to notifications from the NEF 104 (i.e., a Subscribe- Notify model) or request a single notification from the NEF 104 (i.e., a Request-Response model). The USS 102 request contains the following parameters:

Analytics ID = "movement behaviour";

Target of Analytics Reporting: any UE 22;

Analytics Filter Information:

Area of Interest (AOI): restricts the scope of the movement behaviour analytics to the provided area. The AOI may be described as shown in clause 5.5 of TS 23.273 [7];

Optionally, the list of analytics subsets that are requested among those specified in clause 6.21.3 of TS 23.288 [6];

Optionally, preferred level of accuracy of the analytics;

Optionally, preferred level of accuracy per analytics subset (see clause 6.21.3 of TS 23.288 [6]);

Optionally, preferred granularity of location information: "longitude, and latitude^

Optionally, preferred orientation of location information: ("horizontal",

"vertical", "height", “both” "all"); and

Optionally, maximum number of objects.

NOTE: During the nomative phase, additional parameters can be considered if required.

Abbreviations that may be used in the preceding description include:

Abbreviation Explanation

GMLC Gateway Mobile Location Centre

NF Network Function

NWDAF Network Data Analytics Function

0AM Orchestration and Management

PDU Protocol Data Unit

SL-MT-LR Sidelink Mobile Terminating Location Request

UAS Uncrewed Aerial System

UAV Uncrewed Aerial Vehicle

UAV Unmanned Aerial Vehicle

UAV-C Uncrewed Aerial Vehicle Controller USS UAS Service Supplier

UTM Uncrewed Aerial System Traffic Management

5GC 5G Core Network

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

Claims

CLAIMS:

1. A method implemented by a network exposure function, NEF, node (104), the method comprising: receiving (S136), from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management, a flight assistance request comprising one of in-flight assistance information or pre-flight assistance information for a user equipment, UE (22), that is configured as a UAV (22); determining (S 138 ) : one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services; and transmitting (S140) at least one response to the external AF node, the at least one response comprising location information.

2. The method of Claim 1, wherein the determining of one or more services comprises sending a movement behavior analytics request to an analytics network function to request movement behavior information related to the UE (22), the movement behavior analytics request comprising one or more of: an analytics identifier; a preferred orientation of location information; a granularity of location information; analytics filter information; a preferred level of accuracy of analytics; and an analytics target period indicating a time period over which statistics are requested.

3. The method of Claim 2, wherein the movement behavior analytics request is a subscription type request or a single notification type request.

4. The method of any one of Claims 2-3, wherein the granularity of location information comprises one or more of a longitude, a latitude, an altitude and a height level.

5. The method of any one of Claims 2-4, wherein the preferred orientation of location information comprises one or more of horizontal information, vertical information and a number of objects.

6. The method of any one of Claims 2-5, wherein the analytics network function is a network data analytics function, NWDAF (106).

7. The method of any one of Claims 1-6, wherein the flight assistance request is a subscription type request or a single notification type request.

8. The method of any one of Claims 1-7, wherein the in-flight assistance information comprises one or more of: a location of the UE (22); an indication of whether the UE (22) is following an assigned flight path; a presence of the UE (22) in a geographic area; and information of aerial UEs (22) in the geographic area.

9. The method of any one of Claims 1-8, wherein the pre-flight assistance information comprises an indication of at least one flight path from a plurality of flight paths.

10. The method of any one of Claims 1-9, wherein the one or more services comprises one or both of a UAV tracking service and Gateway Mobile Location Center, GMLC (108), location service.

11. The method of any one of Claims 1-10, wherein the in-flight assistance information is configured to assist the external AF node in monitoring a UAV (22) in flight; the pre-flight assistance information is configured to assist the external AF node in planning a flight path for a UAV (22); and the external AF node is one of an uncrewed aerial system, UAS, service supplier, USS (102), or an uncrewed aerial system traffic management, UTM (103).

12. The method of any one of Claims 1-11, wherein one or more services correspond to one or more third-generation partnership projects, 3GPP, services provided by at least one network that is associated with the NEF node (104).

13. A network exposure function, NEF, node (104), configured to: receive, from an external application function, AF, node providing uncrewed aerial vehicle, UAV, flight management, a flight assistance request comprising one of in-flight assistance information or pre-flight assistance information for a user equipment, UE (22), that is configured as a UAV (22); determine: one or more services to fulfill the flight assistance request; and one or more network functions to fulfill the one or more services; and transmit at least one response to the external AF node, the at least one response comprising location information.

14. The NEF node (104) of Claim 13, wherein the determining of one or more services comprises sending a movement behavior analytics request to an analytics network function to request movement behavior information related to the UE (22), the movement behavior analytics request comprising one or more of: an analytics identifier; a preferred orientation of location information; a granularity of location information; analytics filter information; a preferred level of accuracy of analytics; and an analytics target period indicating a time period over which statistics are requested.

15. The NEF node (104) of Claim 14, wherein the movement behavior analytics request is a subscription type request or a single notification type request.

16. The NEF node (104) of any one of Claims 14-15, wherein the granularity of location information comprises one or more of a longitude, a latitude, an altitude and a height level.

17. The NEF node (104) of any one of Claims 14-15, wherein the preferred orientation of location information comprises one or more of horizontal information, vertical information and a number of objects.

18. The NEF node (104) of any one of Claims 14-17, wherein the analytics network function is a network data analytics function, NWDAF (106).

19. The NEF node (104) of any one of Claims 13-18, wherein the flight assistance request is a subscription type request or a single notification type request.

20. The NEF node (104) of any one of Claims 13-19, wherein the in-flight assistance information comprises one or more of: a location of the UE (22); an indication of whether the UE (22) is following an assigned flight path; a presence of the UE (22) in a geographic area; and information of aerial UEs (22) in the geographic area.

21. The NEF node (104) of any one of Claims 13-20, wherein the pre-flight assistance information comprises an indication of at least one flight path from a plurality of flight paths.

22. The NEF node (104) of any one of Claims 13-21, wherein the one or more services comprising one or both of a UAV tracking service and Gateway Mobile Location Center, GMLC (108), location service.

23. The NEF node (104) of any one of Claims 13-22, wherein the in-flight assistance information is configured to assist the external AF node in monitoring a UAV (22) in flight; the pre-flight assistance information is configured to assist the external AF node in planning a flight path for a UAV (22); and the external AF node is one of an uncrewed aerial system, UAS, service supplier, USS (102), or an uncrewed aerial system traffic management, UTM (103).

24. The NEF node (104) of any one of Claims 13-23, wherein one or more services correspond to one or more third-generation partnership projects, 3GPP, services provided by at least one network that is associated with the NEF node (104).