Instructing aerial user equipments for altitude reporting

Abstract

A method performed by a network node (e.g., an Uncrewed Aerial System (UAS) Network Function (NF)) for preflight planning and / or in-flight monitoring is provided. The method includes mapping flight path information into a set of tracking areas (TAs) and flight altitude corridors. The method includes deriving one or more threshold values for height reporting for the UAV based on the flight altitude corridors. The method includes sending the one or more threshold values towards a UAS Service Supplier (USS).

Description

INSTRUCTING AERIAL UES FOR ALTITUDE REPORTINGTECHNICAL FIELD

[0001] This disclosure relates to instructing aerial user equipments (UEs) for altitude reporting.BACKGROUND

[0002] The 3rd Generation Partnership Project (3GPP) Service and Systems Aspect (SA) Working Group 2 (SA2) has completed the study phase of Study on Phase 3 for Uncrewed Aerial System (UAS), Uncrewed Aerial Vehicle (UAV), Urban Air Mobility (UAM) (SP-231801 ), where one of the key issues was about Network Exposure Function (NEF) service enhancements to support pre-flight mission planning and in-flight monitoring. Work is ongoing in Pre-flight Planning and In-flight Monitoring for UAVs.

[0003] Clause 5.12.2 of 3GPP Technical Specification (TS) 23.256 v19.0.0, for example, refers to Pre-flight Planning and In-flight Monitoring for UAVs. As shown there, a UAV establishes a PDU Session for communication with the USS / UTM. The UAV requests (via application layer) pre-flight planning service from USS / UTM. The USS / UTM derives information for the pre-flight planning request and decides to request assistance information from NEF. The USS / UTM sends pre-flight planning assist request to NEF. The request message includes identifier of the UAV (e.g. GPSI), 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 or local derived at the USS / UTM), and accuracy level of predictions relevant to the flight planning. The NEF maps parameters included in the request from the USS / UTM 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 determines services needed for the request and relevant NFs, e.g. NEF service on UAV tracking and mode (UAV location reporting mode, UAV presence monitoring mode, List of Aerial UEs in a geographic area), NWDAF analytics service (Movement Behaviour analytics, and / or CoS Sustainability Analytics), GMLC service (e.g. Ranging / Sidelink Positioning location).

[0004] If the NEF 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 responses to the USS / UTM to reject the pre-flight planning assist request, and may include the detail reason. If being rejected, the USS / UTM may response to the UAV to reject the pre-flight planning request, may include the detail reason if available. The NEF and filter list of UAVs in the areas of interest. The NEF subscribes / requests for notification on Movement Behaviour analytics provided by NWDAF. The subscribe request message include identifier of the UAV (e.g. GPSI) and height information of UAV. The list of UAVs in the areas of interest can be used as inputs for the NEF to request the NWDAF on Movement Behaviour analytics.

[0005] The NEF subscribes / requests for notification on QoS Sustainability analytics provided by NWDAF. The subscribe / request message include identifier of the UAV (e.g. GPSI) and the UAV flight path information defined as 3D location waypoints. The list of UAVs in the areas of interest can be used as inputs for the NEF to request the NWDAF on QoS Sustainability analytics. The NEF may request GMLC service(s), e.g. Ranging / Sidelink positioning location. The list of UAVs in the areas of interest can be used as inputs for the NEF to request the GLMC service on Ranging / Sidelink Positioning location. The NEF generates assistance information for pre-flight planning based on the information and analytics. The assistance information may be the best matched route among the ones provided from the USS / UTM, or potential flight route(s) if candidate flight route(s) is not provided. The NEF responses to the USS / UTM with the assistance information. The USS / UTM decides flight planning by using the assistance information and flight planning mechanism. The USS / UTM sends response to the UAV with the planned flight route.

[0006] When it comes to flight information that, for instance, a USS / UTM may send to a core network via NEF / UAS Network Function (NF), the flight information may include candidate flight route(s). After the USS completes the pre-flight planning from the UAVs starting point to its destination point, the UAS Service Supplier (USS)ZUncrewed Aerial System Traffic Management (UTM) also provides the UAV information about the planned flight route. When it comes to the format of the flight path information, it is expected that it will include also altitude / height information. It is expected that the USS / UTM provides flight path information using a set of cuboids and, if available, corresponding timestamps / time schedule. Each of the cuboids is identified, e.g., by a set of the lowest / highest latitude, lowest / highest longitude and lowest / highest height above the sea level in which the UAV is supposed to fly from its starting point to its next point in the assigned flight path.

[0007] Flight planning is also of key importance for USS changeover, i.e., when a UAV requests flight planning across the geographical area that is served in part by one USS and in part by another USS. In such case, the UAV flight path needs to be planned and, more importantly, the UAV progress along the planned fight path needs to be monitored and reported when the UAV deviates from the assigned trajectory.

[0008] The NEF / UAS NF may invoke additional services with 5GC NFs: with AMF to determine the UAV deviation from the expected UAVs flight trajectory (e.g. primary / secondary flight paths); with UDM to update the Expected UE Behaviour parameters via the parameter provision; with the NWDAF for the Movement Behaviour analytics of the UE / UAV to determine whether the UAV will likely leave the USS area and continue following the flight path or not. The expected UAVs flight trajectory may possibly consist of multiple segments where each of the segments are identified by geographical areas that are served by a different USSs (e.g. the currently serving USS and the target USS for the changeover). The NEF / UAS NF may use the AMF event exposure service to get notified when the UAV does not follow (i.e. deviates from) the assigned flight plan.

[0009] Event Filters for AMF exposure events may be provided for different events, for example, for the following events: Location Report, UE moving in or out of Area of Interest, Access Type, Location, Assigned Trajectory, Reachability Filter, Total number of Transactions, and Number of UEs present in a geographical area.

[0010] Consequently, if the aforementioned Access and Mobility Management Function (AMF) service is used to track that the UAV follows the assigned trajectory (i.e., not deviating), the next generation (NG) Radio Access Network (RAN) (NG-RAN) (and later the respective AMF) needs to be aware of UAV / UE's height when it moves across a specific tracking area (TA). Therefore, the aerial UE (UAV / UE) needs to perform its altitude reporting.

[0011] In the existing specifications (when it comes to altitude reporting), the aerial UEs perform altitude reporting to NG-RAN nodes, such as specified in clause 16.18.3 of TS 38.300 v18.2.0. An Aerial UE can be configured with altitude-dependent, event-based measurement reporting (i.e., eventFU and eventH2). An Aerial UE sends a measurement report when its altitude becomes higher or lower than configured threshold. The UE includes its altitude and location information in the measurement report if configured to do so by NG-RAN. RSRP / RSRQ / SINR measurement results are always reported when height reporting is configured. The Aerial UE can also be configured to trigger measurement reporting only when both an altitude-dependent condition and an RSRP / RSRQ / SINR-based condition are met (i.e., eventA3H1 , eventA3H2, eventA4H1 , eventA4H2, eventA5H1 and eventA5H2, commonly denoted as eventAxHy). For the content of eventAxHy measurement report, the same rules as described above for eventFU and eventH2 apply.

[0012] As specified above, aerial UEs report their altitude on an event-basis. Such UEs can be configured with altitude thresholds, and moreover, there can be more than one configuration. For example, an Aerial UE can be configured with multiple altitude-dependent configurations, each of which is applied in its corresponding altitude range. Altitude-dependent configurations can be provided independently in measurement object (i.e. SSB- ToMeasureAltitudeBased) and an Aerial UE uses those when in RRC_CONNECTED.

[0013] Events for altitude measurement reporting are specified in clause 5.5.4 of TS TS 38.331 v18.2.0. Of note there are Event H1 and Event H2.

[0014] Event H1 concerns when the Aerial UE altitude becomes higher than a threshold . The UE shall consider the entering condition for this event to be satisfied when condition H1 -1 , as specified below, is fulfilled; and consider the leaving condition for this event to be satisfied when condition H1 -2, as specified below, is fulfilled. Inequality H1 -1 (Entering condition) is Ms - Hys > Thresh; and inequality H1 -2 (Leaving condition) is Ms + Hys < Thresh. The variables in the formula are defined as follows: Ms is the Aerial UE altitude relative to the sea level. Hys is the hysteresis parameter for this event (i.e. h 1 -Hysteresis as defined within reportConfig NR for this event). Thresh is the threshold parameter for this event (i.e. hi -Threshold as defined within reportConfig NR for this event). Ms, Hys, Thresh are expressed in meters.

[0015] Event H2 concerns when the Aerial UE altitude becomes lower than a threshold.

[0016] The UE shall consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled; and consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled. Inequality H2-1 (Entering condition) is Ms + Hys < Thresh; and inequality H2-2 (Leaving condition) is Ms - Hys > Thresh. The variables in the formula are defined as follows: Ms is the Aerial UE altitude relative to the sea level. Hys is the hysteresis parameter for this event (i.e. h2-Hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. h2-Threshold as defined within reportConfigNR for this event). Ms, Hys, Thresh are expressed in meters.SUMMARY

[0017] Certain challenges presently exist. For example, aerial UEs (referred to also as UAVs or, sometimes, UAV UEs) currently report their altitude / height information on per event basis and only when the UAVs altitude exceeds the configured thresholds (Event H1 and Event H2). However, this reporting is not sufficient now when the 5G System (5GS) is assisting (via NEF exposure services) a USS / UTM with USS changeovers and / or inflight monitoring (both may involve tracking the UAVs deviations from the assigned trajectory). Furthermore, certain embodiments disclosed herein also address how RAN or UAV / UE provides height information to AMF. Currently there is no existing mechanism for how the 5G Core (5GC) determines and requests the NG-RAN / UE to report the altitude information, and there is no existing mechanism for the NG-RAN node / UE to report to the 5GC the altitude information.

[0018] In order for a 5G network to perform in-flight UAV monitoring (clause 5.12.3) and assistance with USS changeover (clause 5.13), NFs are required to know UAVs altitude information (for instance, to detect and report UE's deviation from the assigned trajectory, which includes TAs information and altitude values for each of the TAs). However, there is no mechanism that (1) configures aerial UEs (UAVs) for altitude reporting to NG-RAN nodes, and (2) reports UAVs altitude information to a core network NF (e.g. AMF); moreover, the CN needs to be informed when a UAV crosses the certain altitudes that are of relevance for a UAVs flight path. Certain embodiments disclosed herein address these two aspects.

[0019] Accordingly, in some embodiments of this disclosure, mechanisms to provide for requesting reporting of altitude information, and for reporting of the altitude information, are provided. In some embodiments, configuration (altitude threshold values, periodicity information) is sent to an aerial UE over the application layer from the USS / UTM after the UAS NF determines these parameters. In some embodiments, node-level signaling using either UE-associated signaling or non-UE-associated signaling is used.

[0020] More specifically, in one aspect, there is provided a method for preflight planning and / or in-flight monitoring. The method includes mapping flight path information into a set of tracking areas (TAs) and flight altitude corridors. The method includes deriving one or more threshold values for height reporting for the UAV based on theflight altitude corridors. The method includes sending the one or more threshold values towards a UAS Service Supplier (USS).

[0021] In a different aspect, there is provided a method for preflight planning and / or in-flight monitoring. The method includes receiving from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV). The height reporting information includes threshold values. The method includes transferring the threshold values in the height reporting information towards the UAV.

[0022] In a different aspect, there is provided a method for preflight planning and / or in-flight monitoring. The method includes deriving a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information. The method includes deriving one or more threshold values for height reporting for the UAV based on the flight altitude corridor. The method includes sending the one or more threshold values towards a UAS Service Supplier (USS).

[0023] In a different aspect, there is provided a method for authorization of a UAV via a UUAA procedure. The method includes receiving altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV. The method includes triggering, as a result of receiving the altitude threshold values for the UAV, a UUAA procedure. The request for the UUAA procedure includes the altitude threshold values. The method includes receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload. The UUAA Authorization payload comprises authorized threshold values. The method includes sending the UUAA Authorization Payload towards the UAV.

[0024] In a different aspect, there is provided a method for preflight planning and / or in-flight monitoring. The method includes requesting a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition.

[0025] In a different aspect, there is provided a method for preflight planning and / or in-flight monitoring. The method includes receiving a request to report altitude information for a uncrewed aerial vehicle (UAV). The request includes a reporting condition. The method includes directing one or more UAVs to report altitude information based on the request. The method includes forwarding a report containing reported altitude information to an Access and Mobility Management Function (AMF) node.

[0026] In a different aspect, there is provided a computer program comprising instructions which when executed by processing circuitry cause the processing circuitry to perform the method of any one of the above embodiments.

[0027] In a different aspect, there is provided a carrier containing the computer program of the above embodiment. The carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

[0028] In a different aspect, there is provided an apparatus comprising processing circuitry and a memory.The memory contains instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of the above embodiments.

[0029] Certain embodiments provide a mechanism for the 5GC to impact altitude measurement reporting, which enables the 5GC to request the NG-RAN / aerial UEs to make reporting based on the flight path provided by the USS / UTM via NEF / UAS NF.BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0031] FIG. 1 shows a message diagram according to some embodiments.

[0032] FIG. 2 shows flight path information and tracking areas according to some embodiments.

[0033] FIG. 3 shows a message diagram according to some embodiments.

[0034] FIG. 4 shows a message diagram according to some embodiments.

[0035] FIG. 5 shows a message diagram according to some embodiments.

[0036] FIG. 6 shows a message diagram according to some embodiments.

[0037] FIGS. 7A and 7B shows a message diagram according to some embodiments.

[0038] FIG. 8 shows a process according to some embodiments.

[0039] FIG. 9 shows a process according to some embodiments.

[0040] FIG. 10 shows a process according to some embodiments.

[0041] FIG. 11 shows a process according to some embodiments.

[0042] FIG. 12 shows a process according to some embodiments.

[0043] FIG. 13 shows a process according to some embodiments.

[0044] FIG. 14 shows an apparatus according to some embodiments.

[0045] FIG. 15 shows a message diagram according to some embodiments.

[0046] FIG. 16 shows a message diagram according to some embodiments.DETAILED DESCRIPTION

[0047] In certain embodiments, based on the received flight path information (which, for instance, includes a set of cuboids for the description of the UAV's flight route) from a USS / UTM, the NEF / UAS NF determines altitude / height thresholds for each of the tracking areas (TAs) the UAV will fly over and / or cross. The NEF / UAS NF may report these identified thresholds back to the USS for delivering via application layer mechanisms (outside the scope of the 3GPP) or send them further via node-level signaling to the relevant AMFs which in turn may notify the NG-RAN and the target UAV(s) about new altitude threshold(s) for reporting. Additionally, the NEF / UAS NF may decide what kind of altitude measurement reporting it requires, and the AMF may request the relevant NG-RAN node(s) to report the altitude information for the given UE, e.g., as on demand, periodic, event-based, and / or thresholds based. A flight path may include several cuboids and each of the cuboids may include its own "highest height value.” Furthermore, the USS might provide several flight paths. Thus, there may, in some embodiments, be a set of "highest height” values; based on all these values, UAS NF would determine the altitude thresholds. Some of the determined altitude thresholds can be the same as some of the "highest height values” of the cuboids. Additionally, these values may come with some uncertainty and / or accuracy values, which may be taken into account in deriving altitude thresholds.

[0048] Additionally, the AMF, instead of sending a request to each aerial UE (i.e. with a UAV subscription), may request the relevant NG-RAN node to make the UAV's altitude reporting whenever a UAV is present in a certain area identified by a RAN node, Public Land Mobile Network (PLMN), Tracking Area (TA), or even cell, i.e., the reporting can be set per NG-RAN node, within PLMN, per Tracking Area, or per cell. Alternatively, the reporting can be requested only when a UAV changes its area, for instance, when a UAV moves out of the cell or Tracking Area.

[0049] Based on the Core Network (CN) request, one or more NG-RAN nodes may send the altitude measurement request to the target aerial UE. With this request, the NG-RAN node may change the existing configurations of the UAV for altitude information reporting or apply a new configuration. Beforehand, the NG-RAN node and AMF may handshake on the events and thresholds to be used for the altitude reporting over Radio Resource Control (RRC) messaging based on the inputs from the USS / UTM and the CN. The UE altitude information can be associated with time stamps at the time when the UAV reports to the NG-RAN node or at the time when the NG-RAN node reports to the CN.

[0050] Both AMF and NG-RAN nodes can stop / pause the UE altitude information reporting.

[0051] The following describes the USS and CN NF interactions according to some embodiments.

[0052] UAS Service Supplier (USS) may include information about the planned flight path of the aerial UE(i.e., UAV) when requesting from the 5GS assisting with (1) pre-flight planning, (2) in-flight monitoring, and (3) USS changeover. These procedures are specified in clauses 5.12.2, 5.12.3, and 5.13.2 of TS 23.256 [5], respectively, and will be used to describe the respective parts of some embodiments.

[0053] FIG. 1 illustrates a procedure for NEF Assisted Pre-flight Planning according to some embodiments.The process involves UAV UE 102, Network Data Analytics Function (NWDAF) 104, NFs / Operations, Administration, and Maintenance (OAM) 106, Gateway Mobile Location Center (GMLC) 108, UAS NF I NEF 110, and USS / UTM 112.

[0054] Steps 1-15 are described in clause 5.12.2 of TS 23.256, which is also extracted above. The process is modified as described here, including with respect to steps 101, 103, 105, and 107 described below.

[0055] 101: In some embodiments, the USS may provide one or more candidate flight paths (e.g., expressed as a set of cuboids) with respect to a UAV UE 102. For example, the USS may provide the candidate flight paths to the NEF / UAS NEF 110 in step 4. If so, the NEF / UAS NF 110 may map the candidate flight paths to a list of TAs that the UAV UE 102 will need to cross (if any one of the candidate paths is selected) and may determine a flight altitude corridor (e.g., a minimum and maximum height value for the UAV) for each of the determined TAs.

[0056] 103: In some embodiments, if the USS / UTM does not include candidate flight path information in the request in step 4, or the NEF / UAS NF 110 otherwise needs any outputs from steps 8-11 for determining suitable altitude corridors for the UAV's flight, the NEF / UAS NF 110 may use the obtained pre-flight assistance information from steps 8-11 to derive the altitude corridor(s).

[0057] 105: Once the NEF / UAS NF 110 determines the altitude corridor for the flight path(s) (whether using the candidate flight paths, the pre-flight assistance information, or both), the NEF / UAS NF 110 may use its knowledge to identify threshold values for the UAV's height reporting, e.g., inside the Nnef_RetrievelnfoUAVFIight_Get response to the USS / UTM 112.

[0058] 107: If the USS / UTM 112 receives the identified threshold values for the UAV's height reporting, the USS / UTM 112 may include them inside the response to the pre-flight planning request that is sent over the application layer to the UAV UE 102 for consumption.

[0059] In some embodiments, the NEF Assisted Pre-flight Planning procedure may include the NEF / UAS NF 110 mapping (or translating) candidate flight path information into a set or list of tracking areas (TAs) and flight altitude corridors. The flight path information may be provided as a set of cuboids, e.g., where each of the cuboids include the lowest / highest latitude, lowest / highest longitude, and lowest / highest height above the sea level in which the UAV is supposed to fly from its starting point to its next point in the assigned flight path . The cuboids may be rectangular cuboids, or of other types, such as a right isosceles-trapezoidal prism. The provided latitude / longitude coordinates may be mapped into a list of TAs (if needed, the approximation may be done to contain a cuboid withing a TA's boundaries) and height intervals may be fitted so that the same value can be used when the UAV flies across a specific TA.

[0060] The table below illustrates example flight path representations using a set of cuboids (shown at (a)) and the result of mapping / translating the cuboids into TAs and altitude corridor of the flight (shown at (b)).

[0061] FIG. 2 illustrates a diagram of flight paths using a set of cuboids with a mapping into TAs and altitude corridors of the flight path, according to an embodiment. As shown, there are a set of TAs 208a associated with USS 1 (202) and a set of TAs 208b associated with USS 2 (204). The cuboids 206 represent the flight path 210 of a UAV.

[0062] FIG. 3 illustrates a procedure for NEF Assisted in-flight monitoring according to some embodiments. The process involves NFs 106, GMLC 108, UAS NF I NEF 110, and USS I UTM 112.

[0063] Steps 1-9 are described in clause 5.12.3 of TS 23.256, which is also extracted above. The process is modified as described here, including with respect to steps 301 and 303 described below.

[0064] 301: If the USS / UTM 112 includes the information (e.g., a set of cuboids and time schedule) about the planned flight path in the request for in-flight monitoring of the UAV, the NEF / UAS NF 110 may map this information into TAs and the altitude corridors for the UAV's flight.

[0065] 303: The NEF / UAS NF 110 may use the determined altitude corridors to derive thresholds for theUAV's height reporting. The NEF / UAS NF 110 may send the derived thresholds in the response to the in-flight monitoring request to the USS / UTM 112 for consumption.

[0066] In some embodiments, the NEF Assisted in-flight monitoring procedure may include the NEF / UAS NF 110 deriving the flight altitude corridor (e.g., a minimum and maximum height values over a certain TA) based on the planned flight path information (e.g., a set of cuboids as shown in FIG. 2) included in the in-flight monitoring request from the USS / UTM 112. The NEF / UAS NF 110 may derive threshold values for the UAV's height reporting and include the threshold values inside a response to the in-flight monitoring request to the USS / UTM 112 for the consumption (e.g., transferring to the target UAV over the application layer as shown in FIG. 1 or for (replanning of the UAV's flight path).

[0067] FIGS. 4-5 illustrate a procedure for UAV changeover from one USS to another serving different geographical areas according to some embodiments. The process involves UAV 102, AMF 402, NWDAF 104, GMLC 108, UAS NF / NEF 110, USS 1 (402), and USS 2 (404). Steps 1 -11 are shown in FIG. 4, and the remaining steps 12-22 are continued in FIG. 5.

[0068] Steps 1-22 are described in clause 5.13.2 of TS 23.256, portions of which are also extracted above.The process is modified as described here, including with respect to steps 401, 403, 405, 501, 503, and 505 described below.

[0069] 401 : As described with respect to some other embodiments, threshold values for a UAV's height reporting may be derived based on the candidate flight path information included in the pre-flight planning request.

[0070] 403: As described with respect to some other embodiments, the USS / UTM derived threshold values may be reported back for the UAV's height reporting for USS / UTM consumption (e.g., including flight re-planning and transferring to the UAV).

[0071] 405: As described with respect to some other embodiments, threshold values for the UAV's height reporting may be derived, e.g., based on the planned flight path information included in (a) the in-flight monitoring request and / or (b) USS change over assistance information.

[0072] 501 : As described with respect to some other embodiments, the derived altitude threshold values for the UAV's height reporting may be delivered over the application layer from the USS / UTM to the UAV.

[0073] 503: The NEF / UAS NF 110 may re-use the existing service operations or a new service may be introduced to deliver the NEF / UAS NF 110 derived altitude threshold values for the UAV's height reporting to the AMF for further transfer to relevant UAVs.

[0074] 505: The altitude threshold values for the UAV's height reporting may be delivered to the NG-RAN nodes, for example, as specified in other embodiments.

[0075] In some embodiments, the UAV changeover procedure may include the NEF / UAS NF 110 using node-level signaling to deliver the derived altitude threshold values to the relevant AMF(s) (e.g., based on the geographical area the UAV's flight is intended to take place over). This may be in addition to other embodiments that describe deriving altitude threshold values for a UAV's height reporting. The NEF / UAS NF 110 may either reuse the existing signaling between AMFs and NEFs (e.g., Namf_EventExposure service) or a new signaling can be introduced. The AMF may provide the altitude threshold values to NG-RAN nodes as described in embodiments below.

[0076] The following describes the AMF / USS and UE interactions according to some embodiments.

[0077] FIG. 6 illustrates a procedure for UAV USS Authentication and Authorization (UUAA) procedure. The process involves UE 102, AMF 402, UAS NF / NEF 110, and USS / UTM 112.

[0078] Steps 1-11 are described in clause 5.2.2.2 of TS 23.256. The process is modified as described here, including with respect to steps 601, 603, and 605 described below.

[0079] 601 : If the AMF 402 receives derived altitude threshold values for a UAV's height reporting, theAMF 402 triggers a UUAA procedure. The altitude threshold values are included in the request made toward the USS / UTM 112 via the UAS NF / NEF 110.

[0080] 603: The USS / UTM 112 adds the received altitude threshold values to the UUAA AuthorizationPayload that is now included in the Naf_Authentication_AuthenticateAuthorize Response message. The USS / UTM 112 may use the included altitude threshold values as an (e.g., additional) criterion for the authorization of the UAV and / or authorize the altitude thresholds.

[0081] 605: The AMF 402 sends the (USS-authorized) altitude thresholds inside the UUAA AuthorizationPayload for UAV consumption in the Non-access Stratum (NAS) Mobility Management (MM) Transport message.

[0082] In some embodiments, the UUAA procedure may include the AMF deciding to trigger the UUAA procedure once it receives (e.g., from a CN NF, such as NEF / UAS NF) altitude threshold values for a UAV's height reporting configuration. Alternatively, the NEF / UAS NF may decide to trigger the UUAA procedure once it derives the altitude threshold values based on the request information (such as described earlier in other embodiments). In any case, the AMF (or NEF / UAS NF) may include the received / derived altitude threshold values in the message sent to the NEF / UAS NF and / or USS / UTM, i.e., in this example, an Nnef_Authentication_AuthenticateAuthorize message and / or an Naf_Authentication_AuthenticateAuthorize message (as shown in Steps 2 and 3 in FIG. 6). Note that in some embodiments the respective service operations / messages of the UUAA procedure specified in clause 5.2.2.2. of TS 23.256 [5] may be complemented with the altitude threshold values. Once the USS / UTM receives the derived altitude thresholds (e.g., in the Naf_Authentication_AuthenticateAuthorize message), the USS / UTM may use the included altitude threshold values as an (e.g., additional) criterion for the authorization of the UAV, and / or authorized the altitude thresholds. The USS / UTM may add the altitude threshold values to the UUAA Authorization Payload that is sent / included in the Naf_Authorization_AuthenticateAuthorize Response message together with the authorization result to the NEF / UAS NF. The NEF / UAS NF may respond to the authorization request from the AMF; the AMF may send the received UUAA Authorization Payload (containing, among other things, the (authorized) altitude threshold values for UAV's height reporting) inside the NAS MM Transport message for UAV's consumption.

[0083] The following describes the AMF and NG-RAN node interactions according to some embodiments.

[0084] In one embodiment, the AMF uses the UE-associated signaling to request NG-RAN node to report the UE altitude information per on demand, periodical, event triggered or per change of value, and / or change of area. The request from the CN (e.g. AMF) to an NG-RAN node may contain one or more of the following indications / instructions:• to report the UAV's altitude directly / periodically with a certain periodicity, e.g., every 10s, 30s, 1 min, 2min, etc.;• to report upon changes of the UAV's altitude or when it exceeds the defined thresholds (H1, H2);• to report the UAV's altitude upon the defined events;• to report the UAV's altitude once the UAV leaves / enters / stays in a certain area, e.g. a list of Cells, TA(s), PLMN;• to cancel / update the UAV's altitude reporting• a report ID;• time stamp;• a Routing ID, for example to indicate a specific NF Instance ID.

[0085] In one embodiment, the AMF uses non-UE associated signaling to request a NG-RAN node to report the UE's altitude information per area (such as NG-RAN node ID), per PLMN, per Tracking Area, and / or per cell. It can further be instructed whether the reporting is requested to be on on-time, on demand, periodic, or event based.

[0086] The request from the CN NF (e.g. AMF) to an NG-RAN node may contain (in addition to the reporting criteria, such as periodicity, area description, event thresholds etc.), for example:• an indication to perform UAV's altitude reporting for all UEs (or all aerial UEs, i.e., UAVs) in a specific gNB(s);• an indication to perform UAV's altitude reporting for all UEs (or for all aerial UEs, i.e. UAVs) in a set or list of TAs.

[0087] In one embodiment, the AMF uses non-UE associated signaling to request a NG-RAN node to report the UE's altitude information per specified group, such as a list of UEs, specific UE category, or for a specific service type.

[0088] The request from CN NF (e.g. AMF) to an NG-RAN node may contain (in addition to the reporting criteria, such as periodicity, area description, event thresholds etc.) for example:• a list of UEs identified, for example, by a list of SUPIs• indication about specific service types, e.g. certain QFI, XR

[0089] A NG-RAN node, upon the reception of such requests, will request the UEs (UAVs) to report the altitude information, may also request to stamp with a timestamp, if not started / requested the UE earlier, and will request to send the result back to the CN (e.g. AMF) accordingly.

[0090] The report from the NG-RAN node to the AMF may contain:• the altitude information;• a time stamp;• a report ID and / or a Routing ID;

[0091] In one embodiment, a NG-RAN node notifies a CN NF (e.g. AMF) that the altitude information report for a specific UE (or UAV) or for all the UEs / UAVs in the area (e.g., gNB, PLMN, TA etc.) has been stopped.

[0092] In one embodiment, AMF notifies the NG-RAN node that the altitude information reporting requested for a specific UE / UAV for all the UEs / UAVs in the area (e.g., gNB, PLMN, TA etc.) has been stopped.

[0093] In one embodiment, when the UE / UAV has indicated to the NG-RAN node that it has "invalid” path due to, for example, an obstacle in its path, in which case the NG-RAN node indicated to a CN NF (e.g. AMF) thatthe UE's current path is not available. The NG-RAN node can indicate to a CN NF (e.g. AMF) to pause the altitude information reporting; and the NG-RAN nodes resumes the reporting only when the UE's altitude information becomes available again.

[0094] In one embodiment, a NG-RAN node stores the UE's altitude information and reports to a CN NF (e.g. AMF) if the CN NF (e.g. AMF) request storing of the information. A NG-RAN node may generate its own reporting requirements towards the target UE(s) / UAV(s).

[0095] In one embodiment, a NG-RAN node can indicate to a CN NF (e.g. AMF) that the current UE's altitude information report is the last one it sends.

[0096] The following describes the NG-RAN node and UE interactions according to some embodiments.

[0097] In one embodiment, upon the reception of the UE's altitude information reporting request from the CN NF, the NG-RAN node initiates / instructs the UE to measure its altitude and provides the altitude measurement results in a report accordingly. The UE reports its altitude information on demand, periodically, or based on events.

[0098] The NG-RAN node may adjust the thresholds, for instance, for Event H1 / H2 (i.e., the Aerial UE altitude becomes higher than a threshold or the Aerial UE altitude becomes lower than a threshold as defined in TS 38.331 [8]).

[0099] In one embodiment, when a CN NF (e.g. AMF) cancels / stops the UE's altitude information reporting, the NG-RAN node requests the UE to perform the reporting using a scheme that better suits the NG-RAN node usage, for instance, by applying a longer periodicity than the requested or by reporting only when the altitude information has changed significantly (a separate threshold value can be applied by the NG-RAN node).

[0100] It is understood that the specification impact can be realized by introducing new procedures or by modifying the suitable existing procedures. Example of specification impact would be changes required in the NGAP to request / stop a NG-RAN node to report UE's altitude information (per UE).

[0101] FIG. 7A illustrates a UE Altitude information request procedure according to an embodiment. The purpose of the UE Altitude information request procedure allows the AMF to request the NG-RAN node to report the UE's altitude information while in CM-CONNECTED state. The procedure uses the UE-associated signaling. The UE Altitude Information Request can be included in the existing procedure, e.g. UE Context Setup Request / PDU Session Resource Setup Request. The UE Altitude Information Response can be included in the existing procedure, e.g. UE Context Setup Response / PDU Session Resource Setup Request.

[0102] UE Altitude Information Request message example (TS 38.413)

[0103] This message is used by the AMF to request the NG-RAN node to report the altitude information of the UE.

[0104] Direction:node

[0105] UE Altitude Information Report Request (all new)

[0106] This IE indicates the UE Altitude Information Report to be handled by the NG-RAN node.

[0107] Reuse of the existing procedure, for example, the Initial Context Setup Request.

[0108] TS 38.413: INITIAL CONTEXT SETUP REQUEST

[0109] This message is sent by the AMF to request the setup of a UE context.

[0110] Direction:node

[0111] Example of specification impact to report UE altitude information (NGAP)

[0112] FIG. 7B illustrates a UE Altitude reporting procedure according to an embodiment.

[0113] FIG. 8 shows a process 800 performed by a UAS NF 110 for preflight planning and / or in-flight monitoring. The process 800 may begin with step s802. The step s802 comprises mapping flight path information into a set of tracking areas (TAs) and flight altitude corridors. The step s804 comprises deriving one or more threshold values for height reporting for the UAV based on the flight altitude corridors. The step s806 comprises sending the one or more threshold values towards a UAS Service Supplier (USS).

[0114] In some embodiments, the flight path information comprises information for multiple potential flight paths. In some embodiments, the flight path information comprises information regarding an uncertainty value associated with the potential flight paths. In some embodiments, the method further includes obtaining additionalflight path information including one or more of movement behavior analytics for the UAV, quality of service (QoS) sustainability analytics, and ranging and / or sidelink positioning location, and the additional flight path information is used to determine the flight altitude corridors in the step of mapping the flight path information into the set of TAs and the flight altitude corridors. In some embodiments, the flight path information includes a set of cuboids where each of the cuboids in the set of cuboids includes boundary information delimiting a space in which the UAV is supposed to fly. In some embodiments, sending the one or more threshold values towards a UAS Service Supplier (USS) comprises sending a response message responsive to a pre-mission flight request, the response message containing the one or more threshold values. In some embodiments, the response message comprises a Nnef_RetrievelnfoUAVFIight_Get response and / or a Nnef_UAVFIightAssistance_Notify request

[0115] In some embodiments, the method further includes sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes. In some embodiments, the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV. In some embodiments, sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling. In some embodiments, sending the one or more threshold values towards the one or more AMF nodes comprises using a Namf_Communication_NonUeN2MessageTransfer request. In some embodiments, the method further includes triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, where the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.

[0116] FIG. 9 shows a process 900 performed by a USS 112 for preflight planning and / or in-flight monitoring. The process 900 may begin with step s902. The step s902 comprises receiving from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV). The height reporting information includes threshold values. The step 904 comprises transferri ng the threshold values in the height reporting information towards the UAV.

[0117] In some embodiments, the message is responsive to a pre-flight planning request. In some embodiments, the method further includes receiving a request for a UAV USS Authentication and Authorization (UUAA) procedure comprising altitude threshold values, the UUAA procedure being associated with a flight path for a UAV; determining a result for the request for the UUAA procedure based on the altitude threshold values; and sending the result toward the NEF and / or UAS NF node.

[0118] FIG. 10 shows a process 1000 performed by a UAS NF 110 for preflight planning and / or in-flight monitoring. The process 1000 may begin with step s1002. The step s1002 comprises deriving a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information. The step s1004 comprises derivingone or more threshold values for height reporting for the UAV based on the flight altitude corridor. The step s1006 comprises sending the one or more threshold values towards a UAS Service Supplier (USS).

[0119] In some embodiments, the method further includes receiving a monitoring request from the USS containing the planned flight path information, and where the one or more threshold values are sent towards the USS in reply to the monitoring request. In some embodiments, the planned flight information comprises a set of cuboids where each of the cuboids in the set of cuboids includes boundary information comprising a lowest latitude, a highest latitude, a lowest longitude, a highest longitude, a lowest height above sea level, and a highest height above sea level, the boundary information delimiting a space in which the UAV is supposed to fly. In some embodiments, the flight altitude corridor comprises a minimum height and a maximum height for the UAV over a tracking area (TA). In some embodiments, the method further includes sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes. In some embodiments, the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV.

[0120] In some embodiments, sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling. In nsome embodiments, sending the one or more threshold values towards the one or more AMF nodes comprises using a Namf_Communication_NonUeN2MessageTransfer request. In some embodiments, the method further includes triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.

[0121] FIG. 11 shows a process 1100 performed by an AMF 402 for authorization of a UAV via a UUAA procedure. The process 1100 may begin with step s1102. The step s1102 comprises receiving altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV. The step s1104 comprises triggering, as a result of receiving the altitude threshold values for the UAV, a UUAA procedure. The request for the UUAA procedure includes the altitude threshold values. The step s1106 comprises receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values. The step s1108 comprises sending the UUAA Authorization Payload towards the UAV.

[0122] In some embodiments, the request for the UUAA procedure comprises a Nnef_Authentication_AuthenticateAuthorize message. In some embodiments, the UUAA Authorization Payload is sent towards the UAV in a Non-Access Stratum (NAS) Mobility Management (MM) Transport message.

[0123] FIG. 12 shows a process 1200 performed by a RAN node to report altitude information for a UAV.The process 1200 may begin with step s1202. The step s1202 comprises requesting a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV). The request includes a reporting condition.

[0124] In some embodiments, the reporting condition is one of (I) on demand, (ii) a periodicity for which the reporting is to be carried out, and (ill) an event indicator indicating an event for which the reporting is to be triggered. In some embodiments, the event indicator indicates one or more altitude thresholds which trigger the reporting. In some embodiments, the event indicator indicates a change in altitude triggers the reporting. In some embodiments, the event indicator indicates an area such that the reporting is triggered when the UAV leaves, enters, and / or stays in the area. In some embodiments, the request further includes an area indication indicating that altitude information is to be reported for any UAV in the indicated area. In some embodiments, the area indication includes one or more gNBs and / or one or more tracking areas (TAs). In some embodiments, the request further includes a group indication indicating that altitude information is to be reported for any UAV in the indicated group. In some embodiments, the group indication includes one or more of (I) a list of UAVs, (ii) a category of UAVs, and (ill) a service type.

[0125] FIG. 13 shows a process 1300 performed by a RAN node for preflight planning and / or in-flight monitoring. The process 1300 may begin with step s1302. The step s1302 comprises receiving a request to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition . The step s1304 comprises directing one or more UAVs to report altitude information based on the request. The step s 1306 comprises forwarding a report containing reported altitude information to an Access and Mobility Management Function (AMF) node.

[0126] In some embodiments, the report further contains a time stamp, a report identifier, and / or a routing identifier. In some embodiments, the report contains an indication that reporting has been stopped.

[0127] FIG. 14 is a block diagram of a node 1400, according to some embodiments. Note that the block diagram only shows certain components of the node 1400. In other words, the block diagram does not show all components of the node 1400. Node 1400 may include any of the network nodes discussed in this disclosure, including the UAS NF, USS, AMF, and RAN nodes.

[0128] As shown in FIG. 14, node 1400 may comprise: processing circuitry (PC) 1402, which comprises one or more processors (P) 1455 (e.g., a general purpose microprocessor and / or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed; a network interface 1468 comprising a transmitter (Tx) 1465 and a receiver (Rx) 1467 for enabling the node 1400 to transmit data to and receive data from other nodes connected to a network 1410 (e.g., RAN) to which network interface 1468 is connected; communication circuitry 1448 (e.g., radio transceiver circuitry comprising an Rx 847 and a Tx 845) coupled to an antenna system 1449 for wireless communication with UEs or other nodes; anda storage unit (a.k.a., "data storage system”) 1408, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments where PC 1402 includes a programmable processor, a computer readable storage medium (CRSM) 1442 may be provided. CRSM 1442 may store a computer program (CP) 1443 comprising computer readable instructions (CRI) 1444. CRSM 1442 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CR1 1444 of computer program 1443 is configured such that when executed by PC 1402, the CRI causes the node 1400 to perform steps described herein (e.g., steps described herein with reference to one or more flow charts). In other embodiments, the node 1400 may be configured to perform steps described herein without the need for code. That is, for example, PC 1402 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and / or software.

[0129] FIG. 15 illustrates a process for the 5GS instructing aerial UEs (UAVs) to perform altitude reporting, considering requests from a USS / UTM for assistance with the UAVs flight. This procedure can be used in conjunction with the NEF-assisted pre-flight planning, in-flight monitoring, and USS changeover as specified in clause 5.12.2, 5.12.3 and 5.13, respectively. The process involves UAV 102, NG-RAN 1502, AMF 402, NFs 106, UAS NF / NEF 110, USS 112.

[0130] 1. UAS NF / NEF 110 assists the USS / UTM 112 with pre-flight planning, in-flight monitoring and / orUSS changeover based on the received request, which may be either a Nnef_RetrievelnfoUAVFIight_Get or a Nnef_UAVFIightAssistance_Create, as specified in clauses 5.12 or 5.13 of TS 23.256.

[0131] 2. Based on the flight path information included in Step 1 and other information obtained as a result of either of the procedures (i.e., NEF-assisted pre-flight planning specified in clause 5.12.2, NEF-assisted in-flight monitoring specified in clause 5.12.3, or USS changeover specified in clause 5.13.2), the UAS NF / NEF 110 determines minimum and maximum values of altitudes (an altitude range) for the UAVs flight across each of the determined tracking areas (TAs) from the starting point to the destination point.

[0132] - The determined minimum and maximum altitude values (i.e., altitude range) for each of the UAVs is used by the UAS NF / NEF 110 to derive altitude thresholds for altitude reporting events.

[0133] NOTE X2: Event H1 and H2 for altitude-based reporting is specified in clause 5.5.4.21 and clause 5.5.4.22 of TS 38.331 can serve as an example for deriving altitude thresholds and event-based reporting.

[0134] Additionally, the UAS NF / NEF 110 determines whether to request the aerial UE 102 to report its altitude information periodically (e.g. every 5s, 15s, 30s, 1 min, 2min etc.), threshold -based (e.g. altitude becomes a higher / lower than the provided threshold) or event-based (e.g. change of a tracking area / NG-RAN node).

[0135] 3. Delivering the UAS NF / NEF-derived altitude thresholds and, optionally, the indication about reporting periodicity (i.e., threshold-based, event-based, or periodic) for UE's altitude reporting to the aerial UE(s)may be performed by the application layer (Option A) and / or node-level signaling (Option B).

[0136] Option A: Application layer.

[0137] 3a. The UAS NF / NEF 110 may send the derived altitude threshold values and provide indication about the periodicity of the reporting (on demand, event-triggered, periodic, or per change of the altitude, or change of a specific geographical area) to the serving USS / UTM 112 either in a Nnef_Retrievel nfoU AVFIight_Get response message (shown as 3a-1) or in a Nnef_UAVFIightAssistance_Notify message (shown as 3a-2) depending on the procedure that has triggered the UAS NF 110 to derive the altitude thresholds for the aerial UE.

[0138] 4a. The USS / UTM 110 may send the altitude reporting thresholds and, optionally, an indication about reporting periodicity (and any additional information required to perform the reporting, e.g., a list of TA(s) / NG- RAN node identifier(s) for event-based reporting, periodicity value (e.g. 5s, 15s, 30s, 1 min, 2 min etc.) for periodic reporting) to the UAV over the application layer for the UAV's consumption.

[0139] Option B: Node-level signalling.

[0140] 3b-4b. The UAS NF / NEF sends an Namf_EventExposure_Subscribe request to the AMF(shown as 3b-1) to get notified about events of UAV's deviation from the assigned trajectory (i.e., Event ID = "Assigned Trajectory") as specified in clause 5.2.2.3.1 of TS 23.502. Inside the subscription request, the UAS NF / NEF 110 includes the derived altitude thresholds and indication about reporting periodicity for the UE's altitude reporting.

[0141] The AMF 402 may send the received altitude thresholds and indication about reporting periodicity for the UE's altitude reporting to the aerial UE inside a NAS MM Transport message (shown as 4b-1).

[0142] Alternatively, the UAS NF / NEF invokes an Namf_Communication_NonUeN2MessageTransfer request to the AMF (shown as 3b-2). Inside this request, the UAS NF / NEF includes an N2 Container indicating to the NG-RAN to instruct aerial UEs to perform altitude reporting based on the included altitude thresholds and reporting periodicity. Additionally, in this request the UAS NF I NEF may include an indication to perform UE's altitude reporting for all aerial UEs in a specific TA(s) or NG-RAN node(s).

[0143] The AMF sends the corresponding N2 messages to all applicable NG-RAN node(s) (shown as 4b- 2).

[0144] 5b. The NG-RAN node(s) 1502 may instruct the relevant UE(s) to perform altitude reporting per provided altitude thresholds and reporting periodicity.

[0145] FIG. 16 illustrates a process for reporting an aerial UE's altitude information to the core network. The reporting may be by the aerial UE based on the received altitude reporting thresholds and indication about reporting periodicity (e.g., as described with respect to FIG. 15 and other embodiments). The process involves UAV 102, NG-RAN 1502, AMF 402, NFs 106, UAS NF / NEF 110, USS 112.

[0146] 0. An aerial UE receives a request to perform its altitude information reporting, e.g., as specified inconnection with FIG. 15 and other embodiments. The request may include altitude reporting thresholds and, optionally, an indication about reporting periodicity.

[0147] 1. UE's flight altitude meets the previously provided altitude reporting conditions (i.e., altitude thresholds and, optionally, reporting periodicity). Once this event is determined to occur, reporting may proceed by application layer (Option A) and / or node-level signaling (Option B).

[0148] Option A: Application layer.

[0149] 2a. The UE may report the altitude information over the application layer to the serving USS / UTM in case the USS / UTM has provided altitude reporting threshold and, optionally, an indication about reporting periodicity (e.g., as in Step 4a of FIG. 15).

[0150] 3a. The USS may invoke the Nnef_UAVFIightAssistance_Notify to inform the UAS NF / NEF aboutUE's altitude.

[0151] Option B: Node-level signalling.

[0152] 2b. The UE may provide a report with the altitude information to the NG-RAN. The report may contain the altitude information and, for instance, a time stamp or a report ID indicating when the UE has measured the altitude information that is being reported.

[0153] The NG-RAN node may include the received UE's altitude information in an N2 message to the AMF, and may add the UE's identifier (e.g. SUPI) if the target for UE's altitude reporting is a specific UE, or a list of UE identifiers if the target is all UEs in a specific TA / NG-RAN node.

[0154] 3b. Notifying the subscriber (i.e., UAS NF / NEF) about UE's altitude information.

[0155] 3b-1. In case the UAS NF / NEF has subscribed to UE's deviation from the assigned trajectory from the AMF via Namf_EventExposure_Subscribe service (see e.g. Step 14a in clause 5.13.2 of TS 23.256), the AMF provides the UAS NF / NEF the altitude information report inside a Namf_EventExposure_Notify request.

[0156] 3b-2. In case the UAS NF / NEF invokes the Namf_Communication_NonUeN2lnfoSubscribe after deliverying the derived altitude reporting thresholds in a Namf_Communication_NonUeN2MessageTransfer (see e.g. step 3b in FIG. 15), the AMF notifies the UAS NF / NEF about UE's altitude information using a Namf_Communication_NonUeN2lnfoNotify request.

[0157] 4. The UAS NF / NEF determines the impact on UAV's flight path based on the received altitude information report.

[0158] Summary of EmbodimentsA1. A method performed by a network node (e.g., an Uncrewed Aerial System (UAS) Network Function (NF)) for preflight planning and / or in-flight monitoring, the method comprising: mapping flight path information into a set of tracking areas (TAs) and flight altitude corridors;deriving one or more threshold values for height reporting for the UAV based on the flight altitude corridors; and sending the one or more threshold values towards a UAS Service Supplier (USS).A1a. The method of embodiment A1, wherein the flight path information comprises information for multiple potential flight paths.A1b. The method of any one of embodiment A1a, wherein the flight path information comprises information regarding an uncertainty value associated with the potential flight paths.A2. The method of embodiment A1, further comprising obtaining additional flight path information including one or more of movement behavior analytics for the UAV, quality of service (QoS) sustainability analytics, and ranging and / or sidelink positioning location, and wherein the additional flight path information is used to determine the flight altitude corridors in the step of mapping the flight path information into the set of TAs and the flight altitude corridors.A3. The method of any one of embodiments A1-A2, wherein the flight path information includes a set of cuboids where each of the cuboids in the set of cuboids includes boundary information delimiting a space in which the UAV is supposed to fly.A4. The method of any one of embodiments A1-A3, wherein sending the one or more threshold values towards a UAS Service Supplier (USS) comprises sending a response message responsive to a pre-mission flight request, the response message containing the one or more threshold values.A4a. The method of embodiment A4, wherein the response message comprises a Nnef_RetrievelnfoUAVFIight_Get response and / or a Nnef_UAVFIightAssistance_Notify request.A5. The method of any one of embodiments A1-A4, further comprising sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes.A6. The method of embodiment A5, wherein the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV.A7. The method of any one of embodiments A5-A6, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling.A7a. The method of any one of embodiments A5-A7, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using a Namf_Communication_NonUeN2MessageTransfer request.A8. The method of any one of embodiments A1-A7, further comprising: triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.B1 . A method performed by a network node (e.g., a Uncrewed Aeria System (UAS) Service Supplier (USS)) for preflight planning and / or in-flight monitoring, the method comprising: receiving from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV), wherein the height reporting information includes threshold values; and transferring the threshold values in the height reporting information towards the UAV.B2. The method of embodiment B 1 , wherein the message is responsive to a pre-flight planning request.B3. The method of any one of embodiments B1-B2, further comprising: receiving a request for a UAV USS Authentication and Authorization (UUAA) procedure comprising altitude threshold values, the UUAA procedure being associated with a flight path for a UAV; determining a result for the request for the UUAA procedure based on the altitude threshold values; and sending the result toward the NEF and / or UAS NF node.C1. A method performed by a network node (e.g., a Network Exposure Function (NEF) and / or an Uncrewed Aerial System (UAS) Network Function (NF)) for preflight planning and / or in-flight monitoring, the method comprising: deriving a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information;deriving one or more threshold values for height reporting for the UAV based on the flight altitude corridor; and sending the one or more threshold values towards a UAS Service Supplier (USS).C2. The method of embodiment C1 , further comprising receiving a monitoring request from the USS containing the planned flight path information, and wherein the one or more threshold values are sent towards the USS in reply to the monitoring request.C3. The method of any one of embodiments C1-C2, wherein the planned flight information comprises a set of cuboids where each of the cuboids in the set of cuboids includes boundary information comprising a lowest latitude, a highest latitude, a lowest longitude, a highest longitude, a lowest height above sea level, and a highest height above sea level, the boundary information delimiting a space in which the UAV is supposed to fly.C4. The method of any one of embodiments C1-C3, wherein the flight altitude corridor comprises a minimum height and a maximum height for the UAV over a tracking area (TA).C5. The method of any one of embodiments C1-C4, further comprising sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes.C6. The method of embodiment C5, wherein the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV.C7. The method of any one of embodiments C5-C6, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling.C8. The method of any one of embodiments C1-C7, further comprising: triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.D1. A method performed by a network node (e.g., an Access and Mobility Management Function (AMF) node) for authorization of an Uncrewed Aerial Vehicle (UAV) via a UAV Uncrewed Aerial System (UAS) Service Supplier (USS) Authentication and Authorization (UUAA) procedure, the method comprising: receiving altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV; triggering, as a result of receiving the altitude threshold values for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the altitude threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards the UAV.D2. The method of embodiment D1, wherein the request for the UUAA procedure comprises a Nnef_Authentication_AuthenticateAuthorize message.D3. The method of any one of embodiments D1-D2, wherein the UUAA Authorization Payload is sent towards the UAV in a Non-Access Stratum (NAS) Mobility Management (MM) Transport message.E1. A method performed by a network node (e.g., an Access and Mobility Management Function (AMF) node) for preflight planning and / or in-flight monitoring, the method comprising: requesting a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition.E2. The method of embodiment E1, wherein the reporting condition is one of (I) on demand, (ii) a periodicity for which the reporting is to be carried out, and (ill) an event indicator indicating an event for which the reporting is to be triggered.E3. The method of embodiment E2, wherein the event indicator indicates one or more altitude thresholds which trigger the reporting.E4. The method of any one of embodiments E2-E3, wherein the event indicator indicates a change in altitude triggers the reporting.E5. The method of any one of embodiments E2-E4, wherein the event indicator indicates an area such that the reporting is triggered when the UAV leaves, enters, and / or stays in the area.E6. The method of any one of embodiments E1-E5, wherein the request further includes an area indication indicating that altitude information is to be reported for any UAV in the indicated area.E7. The method of embodiment E6, wherein the area indication includes one or more gNBs and / or one or more tracking areas (TAs).E8. The method of any one of embodiments E1-E7, wherein the request further includes a group indication indicating that altitude information is to be reported for any UAV in the indicated group.E9. The method of embodiment E8, wherein the group indication includes one or more of (i) a list of UAVs, (ii) a category of UAVs, and (ill) a service type.F1. A method performed by a network node (e.g., a radio access network (RAN) node) for preflight planning and / or in-flight monitoring, the method comprising: receiving a request to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition; directing one or more UAVs to report altitude information based on the request; and forwarding a report containing reported altitude information to an Access and Mobility Management Function (AMF) node.F2. The method of embodiment F1, wherein the report further contains a time stamp, a report identifier, and / or a routing identifier.F3. The method of any one of embodiments F1-F2, wherein the report contains an indication that reporting has been stopped.G1. A computer program (1443) comprising instructions (1444) which when executed by processing circuitry (1402) cause the processing circuitry to perform the method of any one of embodiments A1-F3.G2. A carrier containing the computer program of embodiment G1, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.H1. A node (1400), the node being configured to:map flight path information into a set of tracking areas (TAs) and flight altitude corridors; derive one or more threshold values for height reporting for the UAV based on the flight altitude corridors; and send the one or more threshold values towards a UAS Service Supplier (USS).H2. A node (1400), the node being configured to: receive from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV), wherein the height reporting information includes threshold values; and transfer the threshold values in the height reporting information towards the UAV.H3. A node (1400), the node being configured to: derive a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information; derive one or more threshold values for height reporting for the UAV based on the flight altitude corridor; and send the one or more threshold values towards a UAS Service Supplier (USS).H4. A node (1400), the node being configured to: receive altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV; trigger, as a result of receiving the altitude threshold values for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the altitude threshold values; receive a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and send the UUAA Authorization Payload towards the UAV.H5. A node (1400), the node being configured to: request a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition.H6. A node (1400), the node being configured to: receive a request to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition;direct one or more UAVs to report altitude information based on the request; and forward a report containing reported altitude information to an Access and Mobility Management Function (AMF) node. H7. The node of any one of embodiments H1-H6, wherein the node is configured to perform the method of any one of embodiments A2-F3.11. An apparatus (1400) comprising: processing circuitry (1402); and a memory (1441), said memory containing instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of embodiments A1-F3.

[0159] Abbreviations:

[0160] While various embodiments are described herein, it should be understood that they have beenpresented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0161] As used herein transmitting a message "to” or "toward” an intended recipient encompasses transmitting the message directly to the intended recipient or transmitting the message indirectly to the intended recipient (i.e., one or more other nodes are used to relay the message from the source node to the intended recipient). Likewise, as used herein receiving a message "from” a sender encompasses receiving the message directly from the sender or indirectly from the sender (i.e., one or more nodes are used to relay the message from the sender to the receiving node). Further, as used herein "a” means "at least one” or "one or more.”

[0162] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

[0163] Additionally, an Appendix is provided below, which gives an example of how the standard may be modified. The proposed modification, for example, indicates how the core network may be configure aerial UEs for altitude reporting, considering a flight path information received from a USS / UTM, and illustrates further embodiments.

Claims

CLAIMS1 . A method performed by a network node for preflight planning and / or in-flight monitoring, the method comprising: mapping (s802) flight path information into a set of tracking areas (TAs) and flight altitude corridors; deriving (s804) one or more threshold values for height reporting for the UAV based on the flight altitude corridors; and sending (s806) the one or more threshold values towards a Uncrewed Aerial System (UAS) Service Supplier (USS).

2. The method of claim 1 , wherein the flight path information comprises information for multiple potential flight paths.

3. The method of claim 2, wherein the flight path information comprises information regarding an uncertainty value associated with the potential flight paths.

4. The method of claim 1 , further comprising obtaining additional flight path information including one or more of movement behavior analytics for the UAV, quality of service (QoS) sustainability analytics, and ranging and / or sidelink positioning location, and wherein the additional flight path information is used to determine the flight altitude corridors in the step of mapping the flight path information into the set of TAs and the flight altitude corridors.

5. The method of any one of claims 1-4, wherein the flight path information includes a set of cuboids where each of the cuboids in the set of cuboids includes boundary information delimiting a space in which the UAV is supposed to fly.

6. The method of any one of claims 1-5, wherein sending the one or more threshold values towards a UAS Service Supplier (USS) comprises sending a response message responsive to a pre-mission flight request, the response message containing the one or more threshold values.

7. The method of claim 6, wherein the response message comprises a Nnef_Retrievel nfoU AVFIight_Get response and / or a NnefJJ AVFIightAssistance_Notify request.

8. The method of any one of claims 1-6, further comprising sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes.Page 30 of 379. The method of claim 8, wherein the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV.

10. The method of any one of claims 8-9, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling.11 . The method of any one of claims 8-10, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using a Namf_Communication_NonUeN2MessageTransfer request.

12. The method of any one of claims 1-10, further comprising: triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.

13. A method performed by a network node for preflight planning and / or in-flight monitoring, the method comprising: receiving (s902) from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV), wherein the height reporting information includes threshold values; and transferring (s904) the threshold values in the height reporting information towards the UAV.

14. The method of claim 13, wherein the message is responsive to a pre-flight planning request.

15. The method of any one of claims 13-14, further comprising: receiving a request for a UAV USS Authentication and Authorization (UUAA) procedure comprising altitude threshold values, the UUAA procedure being associated with a flight path for a UAV; determining a result for the request for the UUAA procedure based on the altitude threshold values; and sending the result toward the NEF and / or UAS NF node.Page 31 of 3716. A method performed by a network node for preflight planning and / or in-flight monitoring, the method comprising: deriving (s1002) a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information; deriving (s1004) one or more threshold values for height reporting for the UAV based on the flight altitude corridor; and sending (s1006) the one or more threshold values towards a UAS Service Supplier (USS).

17. The method of claim 16, further comprising receiving a monitoring request from the USS containing the planned flight path information, and wherein the one or more threshold values are sent towards the USS in reply to the monitoring request.

18. The method of any one of claims 16-17, wherein the planned flight information comprises a set of cuboids where each of the cuboids in the set of cuboids includes boundary information comprising a lowest latitude, a highest latitude, a lowest longitude, a highest longitude, a lowest height above sea level, and a highest height above sea level, the boundary information delimiting a space in which the UAV is supposed to fly.

19. The method of any one of claims 16-18, wherein the flight altitude corridor comprises a minimum height and a maximum height for the UAV over a tracking area (TA).

20. The method of any one of claims 16-19, further comprising sending the one or more threshold values towards one or more Access and Mobility Function (AMF) nodes.21 . The method of claim 20, wherein the one or more AMF nodes are associated with the UAV based on a geographical area corresponding to a flight path of the UAV.

22. The method of any one of claims 20-21, wherein sending the one or more threshold values towards the one or more AMF nodes comprises using Namf_EventExposure_Subscribe service signaling.

23. The method of any one of claims 16-22, further comprising: triggering, as a result of deriving one or more threshold values for height reporting for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the threshold values; receiving a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; andPage 32 of 37sending the UUAA Authorization Payload towards an Access and Mobility Management Function (AMF) node.

24. A method performed by a network node for authorization of an Uncrewed Aerial Vehicle (UAV) via a UAV Uncrewed Aerial System (UAS) Service Supplier (USS) Authentication and Authorization (UUAA) procedure, the method comprising: receiving (s1102) altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV; triggering (s1104), as a result of receiving the altitude threshold values for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the altitude threshold values; receiving (s1106) a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and sending (s1108) the UUAA Authorization Payload towards the UAV.

25. The method of claim 24, wherein the request for the UUAA procedure comprises a Nnef_Authentication_AuthenticateAuthorize message.

26. The method of any one of claims 24-25, wherein the UUAA Authorization Payload is sent towards the UAV in a Non-Access Stratum (NAS) Mobility Management (MM) Transport message.

27. A method performed by a network node for preflight planning and / or in-flight monitoring, the method comprising: requesting (s1202) a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition.

28. The method of claim 27, wherein the reporting condition is one of (I) on demand, (ii) a periodicity for which the reporting is to be carried out, and (ill) an event indicator indicating an event for which the reporting is to be triggered.

29. The method of claim 28, wherein the event indicator indicates one or more altitude thresholds which trigger the reporting.

30. The method of any one of claims 28-29, wherein the event indicator indicates a change in altitude triggers the reporting.Page 33 of 3731 . The method of any one of claims 28-30, wherein the event indicator indicates an area such that the reporting is triggered when the UAV leaves, enters, and / or stays in the area.

32. The method of any one of claims 27-31, wherein the request further includes an area indication indicating that altitude information is to be reported for any UAV in the indicated area.

33. The method of claim 32, wherein the area indication includes one or more gNBs and / or one or more tracking areas (TAs).

34. The method of any one of claims 27-33, wherein the request further includes a group indication indicating that altitude information is to be reported for any UAV in the indicated group.

35. The method of claim 34, wherein the group indication includes one or more of (I) a list of UAVs, (ii) a category of UAVs, and (ill) a service type.

36. A method performed by a network node for preflight planning and / or in-flight monitoring, the method comprising: receiving (s1302) a request to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition; directing (s1304) one or more UAVs to report altitude information based on the request; and forwarding (s1306) a report containing reported altitude information to an Access and Mobility Management Function (AMF) node.

37. The method of claim 36, wherein the report further contains a time stamp, a report identifier, and / or a routing identifier.

38. The method of any one of claims 36-37, wherein the report contains an indication that reporting has been stopped.

39. A computer program (1443) comprising instructions (1444) which when executed by processing circuitry (1402) cause the processing circuitry to perform the method of any one of claims 1-38.Page 34 of 3740. A carrier containing the computer program of claim 39, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

41. A node (1400), the node being configured to: map flight path information into a set of tracking areas (TAs) and flight altitude corridors; derive one or more threshold values for height reporting for the UAV based on the flight altitude corridors; and send the one or more threshold values towards a UAS Service Supplier (USS).

42. A node (1400), the node being configured to: receive from an Uncrewed Aerial System (UAS) Network Function (NF) node a message including height reporting information for an uncrewed aerial vehicle (UAV), wherein the height reporting information includes threshold values; and transfer the threshold values in the height reporting information towards the UAV.

43. A node (1400), the node being configured to: derive a flight altitude corridor for an uncrewed aerial vehicle (UAV) based on planned flight path information; derive one or more threshold values for height reporting for the UAV based on the flight altitude corridor; and send the one or more threshold values towards a UAS Service Supplier (USS).

44. A node (1400), the node being configured to: receive altitude threshold values for an uncrewed aerial vehicle (UAV) from height reporting information associated with the UAV; trigger, as a result of receiving the altitude threshold values for the UAV, a UUAA procedure, wherein the request for the UUAA procedure includes the altitude threshold values; receive a response to the request for the UUAA procedure comprising a UUAA Authorization Payload, wherein the UUAA Authorization payload comprises authorized threshold values; and send the UUAA Authorization Payload towards the UAV.

45. A node (1400), the node being configured to: request a radio access network (RAN) node to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition.Page 35 of 3746. A node (1400), the node being configured to: receive a request to report altitude information for a uncrewed aerial vehicle (UAV), wherein the request includes a reporting condition; direct one or more UAVs to report altitude information based on the request; and forward a report containing reported altitude information to an Access and Mobility Management Function (AMF) node.

47. The node of any one of claims 41-46, wherein the node is configured to perform the method of any one of claims 2-38.

48. An apparatus (1400) comprising: processing circuitry (1402); and a memory (1441), said memory containing instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of claims 1-38.Page 36 of 37

Images