Telecommunication system assistance for support of multiple uncrewed aerial systems service suppliers (USS) for a UA vehicle

Abstract

Methods and nodes are provided to assist an Uncrewed Aerial System Service Supplier (USS) to perform a handover of an uncrewed Aerial Vehicle to another USS after determining flight assistance information from a telecommunication system via a network exposure function. The method comprises the USS transmitting to a network function in the telecommunication system information to enable the telecommunication system to provide flight planning assistance information for the UAV and the USS receiving from the telecommunication system a notification comprising the flight planning assistance information indicating the UAV is about to leave a geographical area served by the first USS.

Description

Telecommunication system Assistance for support of multiple Uncrewed Aerial Systems service suppliers (USS) for a UA vehicleRELATED APPLICATIONSThis application claims the benefit of provisional patent application serial number 63 / 575043 filed on 2024-04-05 the disclosure of which are hereby incorporated herein by reference in its entirety.Technical Field

[0001] The present disclosure relates to a cellular communications system and, more particularly, to communication systems supporting Uncrewed Aerial Systems (UAS), UAS Service Supplier (USS) and Uncrewed Aerial Vehicle (UAV).BackgroundThird Generation Partnership Project (3GPP) SA2 has started the work on “Study on Phase 3 for UAS, UAV and Urban Air Mobility (UAM)” (SP-231801 ), and the work item is identified as FS_UAS_Ph3 has few objectives including the objective to study whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for i.e. pre-mission flight planning, in-mission flight monitoring, command and control (02) communication reliability, interfacing with UTM (e.g. supporting the scenario of multiple USS serving the geographical areas corresponding to UAV flight path). The study includes the objective on how to enhance NEF services to support service exposure and interactions between mobile network operators (MNOs) and Uncrewed Aerial System Traffic Management (UTM) functions, and one of the enhancements aims at introducing support for the scenarios when UAV’s flight route goes across geographical areas administrated by different UAS service suppliers (USS-s).

[0002] In this regard, 3GPP SA2 has started the work that is being documented in TR 23.700-59 VO.2.0 where Key Issue (KI)#1 has been formulated by 3GPP to describe the aforementioned aspect:# — excerpt from clause 5.1 of TR 23.700-59 V0.2.0 —5.1 Key Issue #1: Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions5.1.1 DescriptionIn 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 functions for supporting i.e.- Pre-mission flight planning and in-mission flight monitoring for UAVs.- C2 communication reliability.- The scenario of multiple USS serving different geographical areas corresponding to the UAV flight path. NOTE: In the scope of this key issue, UTM can represent any authorized aviation AF that may require interaction with the MNO for the functions listed above.#— Summary

[0003] Some embodiments advantageously provide methods and nodes for enhanced NEF service for supporting scenarios when UAV's flight route goes across geographical areas administrated by different LIAS service suppliers (USS-s).Some embodiments solve the problem considered by the study with respect to scenarios when UAV’s flight route goes across geographical areas administrated by different UAS service suppliers (USSs).

[0004] According to some embodiments, a method performed by a first Uncrewed Aerial System Service Supplier (USS) is provided. The method comprises the step of transmitting to a network function in a telecommunication system information such as for example a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area or candidate border-crossing points for the UAV, to enable the telecommunication system to provide flight planning assistance information for an Uncrewed Aerial vehicle (UAV) and the step of receiving from the telecommunication system a notification comprising the flight planning assistance information indicating the UAV is about to leave a geographical area served by the first USS.

[0005] For example, the step of transmitting is performed in response to determining that a specified destination point of the UAV lies outside a geographical area of the first Uncrewed Aerial System Service Supplier (USS).

[0006] In one aspect, the method further comprises the step of determining by the first USS one or more target USS in the event of a needed changeover to support a UAV flight of the UAV to the specified destination.

[0007] In other aspect, the method further comprises the step of determining one or more target USS based on one of the specified destination point and one or more candidate flight paths for the UAV.

[0008] In one aspect, the notification received by the first USS further comprises which one or more border-crossing points will be used by the UAV.

[0009] In one aspect, the first USS performs the step of executing a changeover to a target USS which may comprise requesting a target USS to perform the flight planning for the UAV from the one or more border-crossing points.

[0010] According to another embodiment, a method performed by a network function of a telecommunication system supporting Uncrewed Aerial vehicles (UAVs) is provided. The method comprises the step of receiving from a first Uncrewed Aerial System Service Supplier (USS) a request for flight planning assistance information for an Uncrewed Aerial vehicle (UAV) and the step of transmitting to the first USS a notification comprising the flight planning assistance information indicating the UAV is about to leave the geographical area served by the USS.

[0011] For example, the request comprises at least one or more candidate bordercrossing points for the UAV or coordinates of the one or more candidate border-crossing points or a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.

[0012] In one aspect, the method further comprises the step of translating by the network function the one or more candidate border crossing-points or the coordinates of the one or more candidate border crossing-points to one or more cell identifiers or one or more tracking area identifiers of the telecommunication system.

[0013] In some aspect, the notification further comprises which one or more bordercrossing points will be used by the UAV or comprises flight planning assistance information indicating the UAV is about to leave the geographical area served by the first USS based on the confidence level.

[0014] According to an embodiment, a network node is provided and configured to perform any of the embodiments herein.According to an embodiment, a network node is provided comprising one or more processors and memory comprising instructions which when executed by the one or more processors enable the network node to perform any of the embodiments herein.

[0015] According to an embodiment, a computer readable memory is provided comprising instructions which when executed by one or more processors of one or more servers configures the one or more servers to perform any of the embodiments herein.Brief Description of the Drawings

[0016] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0017] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented;

[0018] Figures 2 and 3 illustrate example embodiments of the cellular communication system of Figure 1;

[0019] Figure 4 illustrates a cellular communication system of Figure 2 or 3 supporting UAV;

[0020] Figure 5 illustrates USS-serving serving different geographical areas confined within TAs;

[0021] Figures 6 illustrates a UAV changeover scenario for its mobility from TA3_1 to TA5_7 via TA3_2;

[0022] Figures 7 illustrates a procedure for USS changeover in cases when a serving USS triggers communication with a target USS to jointly determine UAV's flight path in accordance with an embodiment;

[0023] Figures 8 illustrates a flow chart of a method implemented in a network function (e.g., NEF / UAS NF) according with some embodiments;

[0024] Figures 9 illustrates a flow chart of a method implemented in a first USS according with some embodiments;

[0025] Figures 10, 11 are schematic block diagrams of example embodiments of a network node.

[0026] Figure 12 is a schematic block diagram of example embodiments of a network node.

[0027] Figures 13, 14 are schematic block diagrams of example embodiments of a wireless device.Technical Description

[0028] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0029] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0030] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0031] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless communication device.

[0032] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0033] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. The node can be a server or system of distributed servers. Some examples of a core network node include core network node implementing 5G network functions such as for e.g., an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Short message service function (SMSF), an Authentication Server Function (AUSF), a UAS NF, a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), o etc. as specified in 3GPP TS 23.501. Other examples of core network nodes include core nodes implementing similar 6G network functions or 7G and beyond. The Core network functions may be virtualized / containerized on a node, server, distributed servers, or implemented as a dedicated function on a dedicated physical node (compute, memory, and network).

[0034] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless or wireline connection.

[0035] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device, an unmanned aerial vehicle (UAV, e.g, drone). Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless connection.

[0036] Network Node: As used herein, a "network node" is any node that is either part of the RAN or the core network of a cellular communications network / system.

[0037] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0038] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0039] The embodiments in this document are described using the 5G system specified in 3GPP hereinafter. However, it will be apparent to a person skilled in the art that the embodiments herein can be applied to other equivalent future generation systems such as 6G, 7G supporting 6G, 7G Radio Access Technology (RAT) including both terrestrial and non-terrestrial access (Satellite). The embodiments also apply to 3GPP system supporting non-3GPP access networks such as WLAN access networks as a UAV can support any of the above access technology.

[0040] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108.

[0041] In particular when the NG-RAN consists of gNBs (5G NG-RAN node) connected to the 5G Core Network (5GC) through the NG interface, a gNB may further consist of a gNB-control unit (CU) and one or more gNB-Distribution Unit(s) (DU(s)).

[0042] The cellular communications system 100 includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0043] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs and as such sometimes referred to herein as UEs 112, but the present disclosure is not limited thereto.

[0044] Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1.

[0045] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5G Core network (5GC) NFs shown in Figure 2 includes but not limited to an an AUSF 204, a UDM 206, the AMF 200, a SMSF 220, a SMF 208, a PCF 210, a UAS NF 202, a NEF 216 and an Application Function (AF) 212.

[0046] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the LIE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. The SMSF 220 communicates with the AMF 200 over the N20 reference point, and with UDM 206 over the N21 reference point, and AMF 200 communicates with UDM 206 over the N8 reference point as illustrated in Figure 2. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208. N80 is the reference point between AMF 200 and NSACF 207 and N81 reference point is between SMF 208 and NSACF 207.

[0047] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, UAS NF 202, AUSF 204, and UDM 206, are in the CP. Separating the UP and CP guarantees each plane resource tobe scaled independently. It also allows LlPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0048] The 5G core network architecture is composed of modularized functions. For example, the AMF 200, SMF 208 and for example SMSF 220 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and ALISF 204 can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly.

[0049] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0050] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points / interfaces used in the 5G network architecture of Figure 2. However, the NFs of the 5GC described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g. Namf for the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, Nsmsf for service based interface exposing services of SMSF 220, etc. Any NFs depicted in Figure 2 can interact with the NEF 216 and / or NRF 218 of Figure 3 as necessary, though not explicitly indicated in Figure 2.

[0051] Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated toeach session to manage them individually and possibly provide different functionalities per session. The AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112. The Network Exposure Function (NEF 216) supports Exposure of capabilities and events, secure provision of information from external application to 3GPP network, translation of internal-external information, support of UAS NF 202 functionality, etc. A 3GPP UAS NF 202 support aerial functionality related to UAV identification, authentication / authorization and tracking, and to support Remote Identification. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar. Figure 4 illustrates an architecture of systems such as 5GS and EPS supporting UAV. The 5GC illustrated in Figure 4 corresponds to the 5GC NFs described in Figure 3 supporting UAV.

[0052] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0053] As stated in the introduction, there currently exist certain challenges as the existing solutions do not address the scenario fully and are reactive, i.e. focus on aspects what happens after a UAV has already left a geographical area of one USS and enters a geographical area of another USS. Moreover, they are very general and lack of specific procedures and service operations, see 3GPP S2-2402254 and 3GPP S2- 2402755.

[0054] The solution as described in the embodiments herein focuses on aspects related to:- Introducing a changeover-like procedure for UAS Service Suppliers (USS) that can be used in cases when a UAV crosses a geographical area that is being served by one USS and enters an area being served by another USS- Introducing a flight path planning for a UAV from a starting point to a destination point across geographical areas served by a different USS;- Notifying UAS NF (NEF) about a UAV's presence in a tracking area (TA) and / or a cell that borders with a TA and / or a cell under the responsibility / service of another USS;- Evaluating direction / trajectory where a UAV will go to determine which TA / cell the UAV will likely enter / leave.

[0055] All together these aspects ensure that LIAVs can plan a flight path across USS geographical area and request destinations in geographic areas served by any USS.

[0056] The embodiments herein are described in the context of 5G system, however it will be apparent to a person skilled in the art that the solution described herein can apply to any telecommunication system including 4G, 6G and beyond. In general, the solution has the following aspects: If a UAV uses a USS for pre-mission flight planning and indicates a destination "deep" inside a geographical area served by another USS, a serving USS triggers communication with a targeted USS to jointly determine a flight path / route to a targeted destination; the serving USS provides this information to the UAV after communication with the target USS. Furthermore, in order to ensure a smooth changeover from the serving USS to the target USS, the serving USS and the target USS can request (via NEFs / UAS NFs) the respective AMFs serving the border cells / TAs to get notified when the UAV leaves / enters the respective cells / TAs. During the changeover, the serving USS provides indications about exposure notifications / services of the UAV to the target USS. The target USS, after completion of the changeover from USS 1, may invoke the relevant exposure services via a serving NEF / UAS NF.

[0057] Some advantages of the solution described herein is to enable the underlying telecommunication network, such as a 5GC (but not limited thereto) to support for UAV by making a flight planning across geographical areas served by different USS-s and to perform a changeover from one USS to another and be part of the changeover process.

[0058] Certain aspects of the present disclosure will be described in details.

[0059] Figure 5 illustrates USS-s serving different geographical areas confined within tracking areas (TAs) in accordance with some embodiments. The focus in this scenario is with two USS-s - USS 1 serving a geographical area confined within tracking area (TA 1), TA 2 and TA 3 and USS 2 serving a geographical area confined within TA 4 and TA 5; each of the TAs has different number of cells etc., see Figure 5. Each USS in Figure 5 is responsible for its geographical area that does not identically match tracking areas (TAS) of a 3GPP network, however, it can be assumed that TAs and Cells IDs can be used to describe / map these geographical areas. Whenever required, a network exposure function (NEF) can be used to make a translation from a geographical description of an area to 3GPP identifiers such as TAs and cell IDs. In the considered scenario, there are border cells between areas served by USS 1 and USS 2 respectively.These cells are: TA1_9, TA1_8, TA3_2, TA3_3, TA2_6, TA4_1, TA4_2, TA4_3 and TA4_6. Whenever a UAV moves inside any of border cells, a changeover from one USS to another is triggered. For that an AMF IN 5gc needs to notify the associated NEF / UAS NF (note that NEF and UAS NF may be collocated or not) about the UAV presence in a border cell / TA so that the NEF / UAS NF could notify a serving USS about the event (i.e., that a UAV moves inside a border cell / TA). After receiving the notification from the NEF / UAS NF, the serving USS can initiate communication with a target USS to ensure a changeover of the UAV to the intended USS can be performed.

[0060] Based on the above, it is assumed that UAS Service Supplier (USS) is aware of neighboring USS-s, border areas that it has with its neighbor USS, possible UAV border-crossing points and can communicate with each other using any available means.

[0061] After receiving the notification about UAV's presence in a border cell / TA, the serving USS can perform a number of actions depending on USS capabilities, UAV flight path (e.g. a targeted destination, a specific border point, arrival time etc.) and other information relevant to the flight path.- If a UAV uses a USS for pre-mission flight planning and indicates a destination in a bordering cell / TA under responsibility of another USS (e.g. TA4_2 as shown in Figure 5), there is no need to perform the UAV changeover if it is assumed that both or several USS-s can serve cells / TAs within bordering region. However, if the UAV requested destination is farther than a border region (e.g. TA5_7) the changeover from a serving USS (USS 1 ) to a target USS (USS 2) is required. The situation is similarly when there is a strict separation between geographical areas served by each USS. For instance, when USS 1 cannot serve in TA4_1 , TA4_2, TA4_3 and TA4_6. It is assumed that when such multi-USS deployment is supported, the USS-s have pre- established knowledge (e.g. via pre-configuration, 0AM, other proprietary means etc. that are not in scope of the study but assumed) of the neighboring USS-s in order to perform changeover.- If a UAV uses a USS for pre-mission flight planning and indicates a destination “deep” inside a geographical area served by another USS (e.g., TA5_7, see Figure 6), there could be different ways how a serving USS could handle such case once it determines that UAV’s target destinations is outside its responsibility / service area:Option 1 : USS 1 plans a route only until a possible border-crossing point(s) in a border cell(s) / TA(s) (TA3_2 in this case) and triggers a changeover / comm unicateswith USS 2 only when the UAV enters TA3_2. Before doing so, after receiving the notification about the UAV’s presence in a border cell, additionally USS 1 may also trigger the service to determine whether UAV’s direction (which is estimated based on notifications for UAV’s deviation from the assigned / expected trajectory) is towards outside of its service area in which case USS1 starts the changeover process with a target USS.- Option 2: USS 1 plans a route until a possible border-crossing point(a) in a border cell(a) / TA(s) with USS 2 (similarly as in Option 1 ), however, when / if the UAV enters any cell / TA inside USS 2 service area, the UAV is required to make another request for the remaining route to its destination in TA5_7 or event to reconnect if the UAV moves to another PLMN (i.e. , USS 2 serves another PLMN). In any case, the UAV needs to communicate with a target USS (i.e., USS 2) in order to plan its route onwards to its target destination in TA5_7, and afterwards the target USS (USS 2) request a serving NEF / UAS NF for assistance with pre-mission flight planning for the remaining path to the destination point.- Option 3: USS 1 as a serving USS triggers communication with a targeted USS (USS 2) to jointly determine a flight path to a targeted destination in TA5_7. USS 1 with a help of a serving NEF / UAS NF makes flight paths (one or several possible) between the starting point and the selected border-crossing point(s), whereas USS 2 decides on suitable flight paths (one or several) across its area from the selected border crossing point(s) to the destination point. USS 2 provides this information to USS 1 , and USS 1 provides this information to the UAV. Furthermore, in order to ensure a smooth changeover from USS 1 to USS 2, USS 1 and USS 2 can request (via NEFs / UAS NFs) the respective AMFs (i.e., an AMF serving TA3_2 and an AMF serving TA4_2 assuming the planned route goes through them, see Figure 6) to get notified when the UAV leaves / enters the respective border cells / TAs. During the changeover a serving USS provides indications about exposure services of the UAV to a target USS. The target USS, after completion of the changeover from USS 1 , may invoke the relevant exposure services via a serving NEF / UAS NF.

[0062] Note that the serving USS may identify multiple potential USS(s) that may serve the UAV during its flight path, based on relevant criteria a serving USS need to select the most appropriate one for the UAV; and a USS may provide several flight paths (e.g., primary, secondary etc.) that can be used picked by a serving USS and reported to a UAV.Geographical area served by a USS is not restricted to the equivalent area served by an AMF.

[0063] Figure 7 illustrates a procedure for USS changeover in cases when a serving USS triggers communication with a target USS to jointly determine UAV's flight path based on the principles described in Figure 5 & 6.The procedure In Figure 7 includes the following main steps. Change of AMF is not always required, both USS1 and USS2 may be served by the same AMF(s) during the entire UAV flight from the starting point to the destination point via the USS-determined flight path(s).Step 1. The UAV (or UAV-C) establishes a PDU Session for communication with a serving USS (USS 1 ) as described in clause 5.2.3 of TS 23.256 v18.2.0.Step 2. The UAV (or via its paired UAV-C) requests a Pre-mission flight planning service from the serving USS. The request message includes identifier of the UAV (e.g. GPSI, CAA-Level UAV ID), information of the starting and destination points for the flight, requirements on the flight route (e.g. on time, shortest, highest, the farthest from a no-transmit zone) and may include candidate flight path(s) if available.Step 3. USS 1 determines that the UAV-specified destination point lies outside a geographical area of its responsibility. Based on the pre-established knowledge (e.g. via pre-configuration, 0AM, other proprietary means etc. that are not in scope of this document), the serving USS (USS 1 ) determines target USS (one or several) that may serve as a target USS. Once USS 1 pre-selects suitable target USS-s (USS 2), USS 1 triggers communication with each of the target USS to determines candidate border-crossing point(s) for the UAV.Note that a serving USS determines a target USS as well as a candidate border crossing points between the serving USS and the selected target USS by any means not described herein; for this purpose several criteria / metrics can be used, for instance, location of destination point, area that a specific USS serves, a number of UAVs in the area served by a specific USS, proximity to a no-transmit zone, USS load etc.- The serving USS in cooperation with the Uncrewed Aerial System Traffic Management (UTM) derives any other information (e.g. confidence level to be used by the NEF / UAS NF to determine likelihood that UAV leaves serving USS area) that can be used by 5GC to provide flight assistance information. Thisinformation from the serving USS / UTM, together with a target USS and candidate border-crossing points for the UAV, will be included in the Pre-mission flight planning assistance request that the serving USS will send to a serving NEF / UAS NF in Step 4.Note that the exact information that a USS can use for this purpose can be determined by any means known to a person skilled in the art, however, it can contain information about UAV capability, geographical coordinates of the candidate border-crossing point(s), indication to reconnect to the network once enter a cell / TA served by another USS, information about no-transmit zone (NTZ) etc.Step 4. The USS sends a Pre-mission flight planning assistance request (e.g. Nnef_PreMissionFlighPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe) to the UAS NF / NEF with the information derived by the serving USS / UTM in Step 3 in addition to UAV’s identifier (e.g. GPS I), information of the starting point for the flight, a list of candidate border-crossing point(s), indication that the UAV will cross a USS border, and other parameters listed in Step 4 of clause 6.1 .3.1 of TR 23.700-59 V0.2.0 (e.g., requirements on the flight path, candidate flight path(s), accuracy level of predictions relevant to the flight planning).Step 5. After receiving the Pre-mission flight planning assistance request from the serving USS, the NEF / UAS NF first translates / maps, if required, the parameters included in the USS request to 3GPP identifiers. For instance, the NEF determines a cell ID / tracking area identifier (TAI) of the cell / TA where the UAV-requested starting and destination points are located; similarly, if the request includes an indication that UAV will cross the USS-border and / or a list of the candidate bordercrossing points in form of geographical coordinates, the NEF maps them to a list of border cell IDs / TAIs.- Next, the NEF determines the relevant NFs and specific service operations the NEF needs to invoke to collect the required information for the serving USS for UAV flight planning (e.g. NWDAF analytics service for Movement Behaviour analytics, GMLC service for Ranging / Sidelink Positioning location, AMF for UAV’s presence in bordering cells / TAs, AMF service for UAV’s deviation for the expected / assigned trajectory (a flight path)).Step 6. The NEF / UAS NF invokes service operations towards NFs as described in Steps 8-12 of the procedure for NEF-assisted pre-mission flight planning in clause 6.1.3.1 of TR 23.700-59 V0.2.0.Step 7. For the UAV changeover purpose, if the NEF / UAS NF receives a list of candidate border-crossing points and / or the indication that the UAV will cross a USS border, the NEF / UAS NF identifies the AMF that serves NG-RAN nodes in all identified border cell(s) / TA(s); for that the NEF / UAS NF uses Nnrf_NFDiscovery service from the NRF see clause 5.2.7.3 of TS 23.502 v18.5.0. Once the AMF(s) information is retrieved, the NEF / UAS NF invokes Namf_EventExposure_Subscribe request to subscribe to the UE / UAV presence in the area of interest wherein the area of interest is set to a cell ID / tracking area identifier (TAI) of every identified border cell / TA.Step 8. Once the NEF receives the relevant information from the determined 5GC NFs in Steps 3-7, the NEF / UAS NF responds to the USS (USS 1 ) to the Premission flight planning assistance request with the collected information. The collected information is for UAV flight path between the starting point and all candidate USS border-crossing points. The response is a notification when the request is a subscription request.Step 9. Once the serving USS receives a response to its Pre-mission flight planning assistance request, the USS 1 determines a target USS from a list of preselected suitable USS in Step 3 and starts communication to request the target USS (USS 2) to perform the flight planning for the UAV from the border-crossing point(s) (i.e. , border cell(s) / TA(s)) to the destination point in the geographical area served by USS 2.Step 10. The target USS (USS 2) performs actions in Steps 4 - 8 to plan the UAV flight across its geographical area towards the UAV’s destination point.Step 11. The target USS (USS 2) provides the serving USS (USS 1 ) information about UAV’s flight plan(s) from a border cell(s) / TA(s) to the destination point (e.g., primary flight path, secondary / alternative flight path etc.).Step 12. Once the serving USS (USS 1 ) receives the information from the target USS (i.e., the flight path(s) for its part of the flight), the serving USS (USS 1 ) determines the primary, secondary etc. flight paths for the UAV from its starting point in USS 1 area to the destination point in USS 2 area; this includes all bordercrossing points and cells / TAs.- The serving USS sends a response to the UAV (or its paired UAV-C) with the planned flight paths for the entire flight from the starting point to the destination point.During the UAV flight (and to perform the changeover from USS 1 to USS 2):Step 13. Once the UAV enters a border cell / TA of the serving USS, the AMF notifies the NEF / UAS NF about the event (i.e. , UAV enters the Area of Interest)Step 14. If the NEF / UAS NF receives the notification about UAV entering a border cell / TA, the NEF / UAS NF may invoke additional service with the AMF to determine the UAV deviation from the expected trajectory (e.g. primary / secondary flight paths) and 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.Step 15-16. If the NEF / UAS NF determines that the UE will likely leave (within the confidence level provided by the USS in Step 3) the geographical area served by the serving USS (USS 1 ), the NEF / UAS NF sends a notification to the USS 1 that the UAV will leave the area. For that purpose, the NEF / UAS NF may use a new service operation (e.g., Nnef_PreMissionFlightPlanning_lnfoNotify or Nnef_PreMissionFlightPlanning_Notify) that can be send in response to and after Nnef_PreMissionFlightPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe, respectively, the latter two can be to request Pre-mission flight planning assistance in Step 4. Inside the notification, the NEF / UAS NF includes information about which border-crossing point will be used by the UAV; the NEF maps back the border cell ID / TAI triggering the event in step 14 to a specific border-crossing point from the list of candidate border-crossing points from Step 3.Step 17. The serving USS (USS 1 ) communicates with the target USS (USS 2) to execute the changeover for the UAV; this communication and details are outside 3GPP scope, however, it is expected that a serving USS pass a target USS the information which exposure services / notification are of relevance for the UAV, information about UAV’s identifiers (e.g. GPSI, CAA-Level UAV ID) as indicated in Step 2 or any other information is required by the target USS (or UAV itself) to establish the connection, see Step 1.Step 18-19. The AMF serving a border cell / TA on USS2’s side (the AMF can be the same or different as on USS 1 side) notifies a serving NEF / UAS NF (can be the same or different from the NEF / UAS NF that communicates with USS 1 ) about the UAV presence in the border cell / TA from USS 2’s side.- The NEF / UAS NF notifies the USS 2 using e.g., a Nnef_PreMissionFlightPlanning_lnfoNotify request about this event.Step 20. After receiving all the required information from the source USS, the target USS responds to the Nnef_PreMissionFlightPlanning_lnfoNotify request in such a way completing the changeover for the UAV.Step 21. The target USS (USS 2) informs the UAV about the changeover and, if required, informs the UAV that it needs to reconnect (if required by the USS) and triggers the exposure services towards 5GC NFs similar the previous serving USS had before the changeover.

[0064] Some of the impacts of the NFs to operate the invention are summarized below:AF / USS:- receiving notification when a UAV enters / leaves a border cell / TA under responsibility of the current serving USS,- providing information of suitable target USS candidates and candidate USS bordercrossing points for UAV flight path(s),- requesting and responding to the pre-mission flight planning with flight assistance information,- determining and providing information about the primary, secondary etc. flight paths for the UAV from its starting point in the geographical area served by a source USS to the destination point in a geographical area served by a target USS,- providing / requesting a confidence level to be used by the NEF / UAS NF to determine likelihood that a UAV will leave the geographical area serving by the USS.AMF:- sending notification about UAV’s presence in an area of interest that is set to a cell or TA,- determining UAV’s deviation for the expected flight trajectory / al located path.NEF / UAS NF:- determining whether a UAV will likely leave I enter a border cell / TA; for that, the NEF / UAS NF functionalities need to enhanced so that it can consider USS-provided confidence level for determining likelihood that a UAV leave will leave a geographical area served by USS,- communication with USS-s for pre-mission flight planning and triggering / completing changeovers from one USS to another, for instance, sending an Nnef_PreMissionFlightPlanning_lnfoNotify request to complete the changeover,- translating / mapping information about geographical areas served by USS-s to 3GPP identifiers (such as cell IDs and tracking area identifier (TAI)), specifically, some enhancements to maps back 3GPP identifier (e.g. border cell ID or TAI) to a specific border-crossing point coordinates that is understandable by a USS,- sending / forwarding information to / from a USS with pre-mission flight planning information. For this, enhancing requests / responses (i.e., Nnef_PreMissionFlightPlanning_lnfoNotify or Nnef_PreMissionFlightPlanning_Notify) to Nnef_PreMissionFlightPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe that are being considered for requesting Pre-mission flight planning assistance.

[0065] Figure 8 illustrates a flow chart of a method implemented in a network function in a telecommunication system, such as a network exposure function or UAS NF or a combined UAS NF and network exposure function in 5G system, or equivalent in 6G system or beyond, to facilitate the USS changeover of a UAV. The method comprises the step 805 of receiving a Pre-mission flight planning assistance request from a first USS. The request may comprise the first USS geographical area, and at least one of the following parameters: a confidence level to be used by the network function in the telecommunication system serving the UAV to determine the likelihood that the UAV leaving the first USS geographical area, the UAV's identifier (e.g. GPSI), information comprising UAV capability, list of candidate border-crossing point(s), geographical coordinates of the candidate (USS) border-crossing point(s), an indication to reconnect to the network once the UAV enters a cell / TA served by another USS (second / target USS), information about no-transmit zone (NTZ), starting point for the flight, destination point of the flight, an indication that the UAV will cross a USS border, and may include any of the following parameters: requirements on the flight path, candidate flight path(s), accuracy level of predictions relevant to the flight planning.

[0066] In one example, after receiving the Pre-mission flight planning assistance request from the serving USS, the network function first translates / maps, if required, some of the information included in the request to 3GPP identifiers. For instance, the network function determines a cell ID / tracking area identifier (TAI) of the cell / TA where the UAV-requested starting and destination points of the flight are located; similarly, if the request includes an indication that UAV will cross the USS-border and / or a list of the candidate border-crossing points in form of geographical coordinates, the network function maps them to a list of border cell IDs / TAIs.

[0067] For example, the network function determines the relevant other NFs in the telecommunication system serving the UAV and the specific service operations the network function needs to invoke to collect the required information for the first USS for UAV flight planning. For example, it may need to invoke various service operations in different NFs such as invoking the NWDAF analytics service for Movement Behaviour analytics, GMLC service for Ranging / Sidelink Positioning location, AMF for UAV's presence in bordering cells / TAs, AMF service for UAV's deviation for the expected / assigned trajectory (a flight path)).

[0068] If the network function had received a list of candidate border-crossing points and / or the indication that the UAV will cross a USS border in the request from the first USS, the network function identifies the other network function that provides access to the UAV via the NG-RAN, for example in the 5G system, it discovers the AMF(s) that serves NG-RAN nodes in all identified border cell(s) / TA(s). For that the network function may need to discover the AMFs using the Nnrf_NFDiscovery service from the NRF in the 5G system. Once the AMF(s) information is retrieved, the network function subscribes to the AMF(s) (using for example Namf_EventExposure_Subscribe request) to receive notification of the UE / UAV presence in the area of interest wherein the area of interest is identified by a cell ID / tracking area identifier (TAI) of every identified border cell / TA resulted from the translation.

[0069] Once the network function receives the relevant information from the AMF(s) and the other NFs (e.g., NWDAF, GMLC) the network function NF notifies at step 810 the first USS and provides the collected information for UAV flight path between the starting point and all candidate USS border-crossing points.

[0070] In more specific examples of the above, if the network function receives a notification from the AMF(s) that the UAV enters a border cell / TA of the first USS, (i.e., UAV enters the Area of Interest), the network function may invoke additional service with the AMF to determine the UAV deviation from the expected trajectory (e.g. primary / secondary flight paths) and 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.

[0071] If the network function determines that the UE / UAV will likely leave (within the confidence level provided by the first USS) the geographical area served by the firstUSS (which is the serving USS), the network function sends notification to the first USS that the UAV will leave the area. For that purpose, the network function may use a new service operation (e.g., Nnef_PreMissionFlightPlanning_InfoNotify or Nnef_PreMissionFlightPlanning_Notify) that can be send in response to and after Nnef_PreMissionFlightPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe, respectively, the latter two used to request Pre-mission flight planning assistance.

[0072] The network function includes in the notification information about which border-crossing point will be used by the UAV; the network function maps back the border cell ID / TAI triggering the event to a specific border-crossing point from the list of candidate border-crossing points received in the request from the first USS.

[0073] Figure 9 illustrates a flow chart in accordance of one or more embodiments of a method implemented by an application function in USS or any appropriate application server in a first USS of enabling USS changeover during a UAV flight for facilitating a UAV path to its specific destination. Although the steps are described for first USS, the first USS comprises an AF, another entity in the USS or one or more entities in USS performing the method) so for short, first USS is used. The method comprises the step 905 of determining by the first USS that the UAV-specified destination point lies outside a geographical area of its responsibility. Based on the pre-established knowledge (e.g., via pre-configuration, 0AM, other proprietary means etc. that are not in scope of this document), the first USS determines one or more target USSs that may serve as a target USS (second USS) in the event of a needed changeover to support the UAV flight to the specified destination. Once the first USS pre-selects suitable target USS-s, the first USS could trigger communication with each of the target USS to determines candidate border-crossing point(s) for the UAV.

[0074] For example, the first USS determines a target USS as well as a candidate border crossing points between the first USS and the selected target USS using several criteria / metrics including for instance, location of destination point, area that the first or the target USS serves, a number of UAVs in the area served by the first or the target USS, proximity to a no-transmit zone, the first or target USS load, the candidate flight paths of the UAV etc.

[0075] In other example, the first USS in cooperation with the Uncrewed Aerial System Traffic Management (UTM) derives any other information that can be used bythe telecommunication system serving the UAV to provide flight assistance information. The information includes for example a confidence level to be used by a third network function in a telecommunication system serving the UAV (e.g., NEF / UAS NF in 5GC) to determine the likelihood that the UAV leaves the first USS area). The information obtained from the UTM, together with additional information that may include the target USS, the UAV's identifier (e.g. GPSI), the first USS geographical area, other information comprising at least on of UAV capability, list of candidate border-crossing point(s), geographical coordinates of the candidate (USS) border-crossing point(s), an indication to reconnect to the network once the UAV enters a cell / TA served by another USS (second / target USS), information about no-transmit zone (NTZ), starting point for the flight, destination point of the flight, an indication that the UAV will cross a USS border and any of the following parameters: requirements on the flight path, candidate flight path(s), accuracy level of predictions relevant to the flight planning. The first USS transmits to the third network function (e.g., serving NEF / UAS NF in the 5GS) a Premission flight planning assistance request that the first USS transmits including any of the information and / or additional information described just above.

[0076] For example, the first USS sends a Pre-mission flight planning assistance request as a Nnef_PreMissionFlighPlanning_Get message or Nnef_PreMissionFlightPlanning_Subscribe message to the third network function.

[0077] At step 910, the first USS1 performs the step of receiving a notification from the third network function in response to transmitting the Pre-mission flight planning assistance request. The notification indicating the UAV enters or leaves or about to leave the geographical area of the first USS. For example the notification may be received from the NEF / UAS NF in 5G may be received in a Nnef_PreMissionFlightPlanning_InfoNotify or Nnef_PreMissionFlightPlanning_Notify sent in response and after Nnef_PreMissionFlightPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe, respectively.

[0078] The notification may include information indicating which border-crossing point from the list of candidate border-crossing will be used by the UAV.

[0079] At step 920, if for example the notification indicates the UAV leaves or about to leave the geographical area of the first USS and / or indicate the border crossing point, the first USS executes the changeover to the target USS (second USS) for the UAV. For example, the first USS executes the changeover by transmitting to the target USS(second USS) information related to which exposure services / notification are of relevance for the UAV, information about UAV's identifiers (e.g., GPSI, CAA-Level UAV ID) and / or any other information required by the target USS (or UAV itself) to establish the connection.Further Description

[0080] Figure 10 is a schematic block diagram of a network node 1100 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 1100 may be, for example, a core network node that implements a NF (e.g., one or more of the 5G network functions, or the like, as described herein). As illustrated, the network node 1100 includes a one or more processors 1104 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory 1106, and a network interface 1108. The one or more processors 1104 are also referred to herein as processing circuitry. The one or more processors 1104 operate to provide one or more functions of the network node 1100 as described herein (e.g., one or more functions of the e.g., one or more of the 5G network functions, or the like, as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 1106 and executed by the one or more processors 1104.

[0081] Figure 11 is a schematic block diagram that illustrates a virtualized embodiment of the network node 1100 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized" network node is an implementation of the network node 1100 in which at least a portion of the functionality of the network node 1100 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 1100 includes one or more processing nodes 1200 coupled to or included as part of a network(s) 1202. Each processing node 1200 includes one or more processors 1204 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1206, and a network interface 1208. In this example, functions 1210 of the network node 1100 described herein (e.g., one or more of the 5G network functions, or the like, as described herein) are implemented at the one or more processing nodes 1200 or distributed across the two or more processing nodes 1200 in any desired manner. In some particular embodiments, some or all of the functions1210 of the network node 1100 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environ ment(s) hosted by the processing node(s) 1200.

[0082] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 1100 or a node (e.g., a processing node 1200) implementing one or more of the functions 1210 of the network node 1100 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0083] Figure 12 is a schematic block diagram of the network node 1100 according to some other embodiments of the present disclosure. The network node 1100 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provide the functionality of the network node 1100 described herein. This discussion is equally applicable to the processing node 1200 of Figure 11 where the modules 1300 may be implemented at one of the processing nodes 1200 or distributed across multiple processing nodes 1200.

[0084] Figure 13 is a schematic block diagram of a UE 1000 according to some embodiments of the present disclosure. The UE being the UAV. As illustrated, the UE 1000 includes one or more processors 1002 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1004, and one or more transceivers 1006 each including one or more transmitters 1008 and one or more receivers 1010 coupled to one or more antennas 1012. The transceiver(s) 1006 includes radio-front end circuitry connected to the antenna(s) 1012 that is configured to condition signals communicated between the antenna(s) 1012 and the processor(s) 1002, as will be appreciated by on of ordinary skill in the art. The processors 1002 are also referred to herein as processing circuitry. The transceivers 1006 are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE 1000 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1004 and executed by the processor(s) 1002. Note that the UE 1000 may include additional components not illustrated in Figure 10 such as, e.g., one or more user interface components (e.g., aninput / output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and / or the like and / or any other components for allowing input of information into the UE 1000 and / or allowing output of information from the UE 1000), a power supply (e.g., a battery and associated power circuitry), etc.

[0085] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 1000 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0086] Figure 14 is a schematic block diagram of the UE 1000 according to some other embodiments of the present disclosure. The UE 1000 includes one or more modules 1100, each of which is implemented in software. The module(s) 1100 provide the functionality of the UE 1000 described herein.

[0087] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0088] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform theoperations in a different order, combine certain operations, overlap certain operations, etc.).

[0089] While processes in the figures (flow charts, procedures) may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0090] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0091] Some example embodiments of the present disclosure are as follows: Embodiment 1. A method performed by a first Uncrewed Aerial System Service Supplier (USS) comprising:- transmitting to a network function in a telecommunication system information to enable the telecommunication system to assist the first USS in initiating a changeover from the first USS to a target USS for facilitating an Uncrewed Aerial vehicle (UAV) flight path of a UAV to specific destination; and- receiving a notification from a telecommunication system comprising assistance information indicating the UAV is about to leave the geographical area served by the USS.Embodiment 2. The method of embodiment 1 wherein the step of transmitting is performed in response to determining that an Uncrewed Aerial vehicle (UAV) specified destination point lies outside a geographical area of the first Uncrewed Aerial System Service Supplier (USS).Embodiment 3. The method of any one of embodiment 1 and 2, wherein the method further comprises determining one or more target USS in the event of a needed changeover to support a UAV flight of the UAV to the specified destination.Embodiment 4. The method of embodiment 1 wherein the step of determining one or more target USS is based on one of the specified destination point and one or more candidate flight paths for the UAV.Embodiment 5. The method of embodiment 1 wherein the transmitted information to the telecommunication system comprises a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.Embodiment 6. The method of embodiment 1 wherein the transmitted information comprises candidate border-crossing points for the UAV.Embodiment 7. The method of embodiment 1 or 6 wherein the notification further comprises about which border-crossing point will be used by the UAV.Embodiment 8. The method of embodiment 1 wherein the method further comprises executing a changeover to a target USS.Embodiment 9. The method of embodiment 8 wherein executing the changeover comprises requesting a target USS to perform the flight planning for the UAV from the border-crossing point(s).Embodiment 10. A method performed by a network function of a telecommunication system supporting a UAV, the method comprising:- receiving from a first USS a request for assistance in initiating a changeover from the first USS to a target USS for facilitating an Uncrewed Aerial vehicle (UAV) flight path of a UAV to specific destination; and- transmitting a notification from a telecommunication system to the first USS comprising assistance information indicating the UAV is about to leave the geographical area served by the USS.Embodiment 11. The method of embodiment 10 wherein the request comprises at least one or one or more candidate border-crossing points for the UAV or coordinates of the one or more candidate border-crossing points.Embodiment 12. The method of embodiment 11, wherein the method further comprises translating the one or more candidate border crossing-points or the coordinates of the one or more candidate border crossing-points to cell identifier / tracking area identifier of the telecommunication system.Embodiment 13. The method of any one of embodiment 10-12 wherein the notification further comprises about which border-crossing point will be used by the UAV.Embodiment 14. The method of embodiment 10 wherein the request comprises a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.Embodiment 15. The method of embodiment 10 wherein the request comprises a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.Embodiment 16. The method of embodiment 15 wherein the notification comprising assistance information indicating the UAV is about to leave the geographical area served by the first USS is based on the confidence level.Embodiment 17. A network node configured to perform the method of any one of embodiments 10-16.Embodiment 18. A network node comprising one or more processors and memory comprising instructions which when executed by the one or more processors enable the network node to perform the method of any one of embodiments 10- 16.Embodiment 19. A computer readable memory comprising instructions which when executed by one or more processors of one or more servers configures the one or more servers to perform the method of any one of embodiments 10-16.

[0092] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.Abbreviation

Claims

Claims:

1. A method performed by a first Uncrewed Aerial System Service Supplier (USS) comprising:- transmitting to a network function in a telecommunication system information to enable the telecommunication system to provide flight planning assistance information for an Uncrewed Aerial vehicle (UAV); and- receiving from the telecommunication system a notification comprising the flight planning assistance information indicating the UAV is about to leave a geographical area served by the first USS.

2. The method of claim 1 wherein the step of transmitting is performed in response to determining that a specified destination point of the UAV lies outside a geographical area of the first Uncrewed Aerial System Service Supplier (USS).

3. The method of any one of claims 1 and 2, wherein the method further comprises determining one or more target USS in the event of a needed changeover to support a UAV flight of the UAV to the specified destination.

4. The method of claim 1 wherein the method further comprises determining one or more target USS based on one of the specified destination point and one or more candidate flight paths for the UAV.

5. The method of claim 1 wherein the transmitted information to the telecommunication system comprises a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.

6. The method of claim 1 wherein the transmitted information comprises candidate border-crossing points for the UAV.

7. The method of claim 1 or 6 wherein the notification further comprises which one or more border-crossing points will be used by the UAV.

8. The method of any one of claims 1 to 7 wherein the method further comprises executing a changeover to a target USS.

9. The method of claim 8 wherein executing the changeover comprises requesting a target USS to perform the flight planning for the UAV from the one or more border-crossing points.

10. A method performed by a network function of a telecommunication system supporting Uncrewed Aerial vehicles (UAVS), the method comprising:- receiving from a first Uncrewed Aerial System Service Supplier (USS) a request for flight planning assistance information for an Uncrewed Aerial vehicle (UAV); and- transmitting to the first USS a notification comprising the flight planning assistance information indicating the UAV is about to leave the geographical area served by the USS.

11. The method of claim 10 wherein the request comprises at least one or more candidate border-crossing points for the UAV or coordinates of the one or more candidate border-crossing points.

12. The method of claim 11, wherein the method further comprises translating the one or more candidate border crossing-points or the coordinates of the one or more candidate border crossing-points to one or more cell identifiers or one or more tracking area identifiers of the telecommunication system.

13. The method of any one of claims 10-12 wherein the notification further comprises which one or more border-crossing points will be used by the UAV.

14. The method of claim 10 wherein the request comprises a geographical area of the first USS and a confidence level of a likelihood the UAV will leave the geographical area.

15. The method of claim 10 and 14 wherein the notification comprising flight planning assistance information indicating the UAV is about to leave the geographical area served by the first USS is based on the confidence level.

16. A network node configured to perform the method of any one of claims 10-15.

17. A network node comprising one or more processors and memory comprising instructions which when executed by the one or more processors enable the network node to perform the method of any one of claims 10-15.

18. A computer readable memory comprising instructions which when executed by one or more processors of one or more servers configures the one or more servers to perform the method of any one of claims 10-15.

Images