Network nodes and methods therein for enhanced movement tracking

Abstract

The present disclosure provides a method (100) in a network function for mobility management. The method (100) includes: receiving (110), from a network exposure function or an Uncrewed Aerial Vehicle, UAV, management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path; and transmitting (120) the notification to the network exposure function or the UAV management network function.

Description

[0001] NETWORK NODES AND METHODS THEREIN FOR ENHANCED MOVEMENT TRACKING

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to communication technology, and more particularly, to network nodes and methods therein for enhanced movement tracking.

[0004] BACKGROUND

[0005] The 3rdGeneration Partnership Project (3GPP) System Architecture 2 (SA2) is progressing the work on Study on Phase 3 for Uncrewed Aerial System (UAS), Uncrewed Aerial Vehicle (UAV) and Urban Air Mobility (UAM). This study item includes the objective on how to enhance Network Exposure Function (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 a UAV’s flight route goes across geographical areas administrated by different UAS Service Suppliers (USS-s). For further details, reference can be made to the 3GPP Technical report (TR) 23.700-59, VI.0.0, which is incorporated herein by reference in its entirety.

[0006] SUMMARY

[0007] It is an object of the present disclosure to provide network nodes and methods therein, capable of providing enhanced movement tracking for a UAV.

[0008] According to a first aspect of the present disclosure, a method in a network function for mobility management is provided. The method may include: receiving, from a network exposure function or an UAV management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The method may further include: transmitting the notification to the network exposure function or the UAV management network function.

[0009] According to a second aspect of the present disclosure, a method in a network exposure function or UAV management network function is provided. The method may include: transmitting, to a network function for mobility management, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The method may further include: receiving the notification from the network function for mobility management.

[0010] According to a third aspect of the present disclosure, a method in a USS is provided. The method may include transmitting, to a network exposure function or UAV management network function, information for an assigned flight path of a UAV.

[0011] According to a fourth aspect of the present disclosure, a method in a data management function is provided. The method may include: receiving, from a network exposure function or UAV management network function, a parameter provisioning request containing information for an assigned flight path of a UAV. The method may further include: transmitting, to a network function for mobility management, subscription data of the UAV. The subscription data of the UAV contains the information.

[0012] According to a fifth aspect of the present disclosure, a network node is provided. The network node may include a communication interface, a processor, and a memory. The memory may contain instructions executable by the processor whereby the network node is operative to, when implementing a network function for mobility management, perform the method according to the above first aspect, or when implementing a network exposure function or UAV management network function, perform the method according to the above second aspect, or when implementing a USS, perform the method according to the above third aspect, or when implementing a data management function, perform the method according to the above fourth aspect.

[0013] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium may have computer-readable instructions stored thereon. The computer-readable instructions, when executed by a processor of a network node, may configure the network node to, when implementing a network function for mobility management, perform the method according to the above first aspect, or when implementing a network exposure function or UAV management network function, perform the method according to the above second aspect, or when implementing a USS, perform the method according to the above third aspect, or when implementing a data management function, perform the method according to the above fourth aspect.

[0014] According to a seventh aspect of the present disclosure, a computer program product is provided. The computer program product may include computer-readable instructions which, when executed by a processor of a network node, configure the network node to, when implementing a network function for mobility management, perform the method according to the above first aspect, or when implementing a network exposure function or UAV management network function, perform the method according to the above second aspect, or when implementing a USS, perform the method according to the above third aspect, or when implementing a data management function, perform the method according to the above fourth aspect.

[0015] With certain embodiments of the present disclosure, a network function for mobility management can receive a subscription request from a network exposure function or UAV management network function. The subscription request requests for notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. When the UAV deviates from the assigned flight path and / or moves across segments, the network function for mobility management can transmit the notification to the network exposure function or the UAV management network function accordingly. In this way, an enhanced movement tracking and reporting for a UAV can be provided, thereby allowing network functions to be notified, in a timely manner, of potential abnormal behaviors of the UAV and / or facilitating changeover of the UAV from one USS to another when the assigned flight path is served by different USS-s.

[0016] BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other objects, features and advantages will be more apparent from the following description of embodiments with reference to the figures, in which:

[0018] Fig. 1 is a flowchart illustrating a method in a network function for mobility management according to an embodiment of the present disclosure;

[0019] Fig. 2 is a flowchart illustrating a method in a network exposure function or UAV management network function according to an embodiment of the present disclosure;

[0020] Fig. 3 is a flowchart illustrating a method in a USS according to an embodiment of the present disclosure;

[0021] Fig. 4 is a flowchart illustrating a method in a data management function according to another embodiment of the present disclosure;

[0022] Fig. 5 is a schematic diagram showing a procedure of UAV changeover from one USS to another serving different geographical areas;

[0023] Fig. 6 is a schematic diagram showing another procedure of UAV changeover from one USS to another serving different geographical areas;

[0024] Figs. 7-10 are block diagrams of network nodes according to embodiments of the present disclosure; and

[0025] Fig. 11 is a block diagram of a network node according to another embodiment of the present disclosure.

[0026] DETAILED DESCRIPTION In the present disclosure, a network function, or NF, can 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. on a cloud infrastructure. The term “network node” refers to any physical or virtual node configured to implement a network function.

[0027] The term “UE” refers to any end device that can access a wireless communication network and receive services therefrom. In some embodiments, the UE may refer to a UAV, and the terms “UE” and “UAV” may be used interchangeably.

[0028] References in the specification to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0029] It shall be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0030] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0031] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0032] Fig. 1 is a flowchart illustrating a method 100 according to an embodiment of the present disclosure. The method 100 can be performed by a network function for mobility management, e.g., an Access and Mobility Management Function (AMF), a Mobility Management Entity (MME), or any network function for mobility management in a future evolved network.

[0033] At block 110, the network function for mobility management receives, from a network exposure function or a UAV management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Optionally, different segments are served by different USS-s.

[0034] In an example, the network exposure function may be a Network Exposure Function (NEF), a Service Capability Exposure Function (SCEF), or any network function for network / service exposure in a future evolved network. The UAV management network function may be a UAS Network Function (UAS NF).

[0035] At block 120, the network function for mobility management transmits the notification to the network exposure function or the UAV management network function, e.g., when the UAV deviates from the assigned flight path and / or the UAV moves across segments in the assigned flight path.

[0036] In an example, the network function for mobility management may obtain information for the assigned flight path of the UAV from the subscription request. Alternatively, the network function for mobility management may receive, from a data management function, subscription data of the UAV. The subscription data of the UAV may contain information for the assigned flight path of the UAV. Here, the data management function may be e.g., a Unified Data Management (UDM), a Home Subscriber Server (HSS), or any network function for data management in a future evolved network. Alternatively, e.g., in the UAV’s mobility procedure from an old network function for mobility management to a new network function for mobility management, the new network function for mobility management may receive information for the assigned flight path of the UAV from the old network function for mobility management. Accordingly, the old network function for mobility management may transmit the information for the assigned flight path of the UAV to the new network function for mobility management.

[0037] Here, in an example, the information for the assigned flight path of the UAV may include: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path. Alternatively or additionally, the information may include a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS. The information may include, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

[0038] In an example, the UAV deviating from the assigned flight path may include at least one of: the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information. Here, optionally, the term “location area” may refer to a geographical area or 3GPP identification area (e.g., TA or cell) on the earth surface and may not involve the concept of altitude or height. Or alternatively the term “location area” can be implemented as not only including 3 GPP identification area (e.g., TA or cell) on the earth surface, but also including the concept of altitude or height.

[0039] As an example, the subscription request may be an Namf_EventExposure_Subscribe request, and the notification may be an Namf_EventExposure_Notify message. For the purpose of this notification, an event filter “Location Report” defined in Table 5.2.2.3.1-1 of the 3GPP Technical Specification (TS) 23.502, V18.6.0, which is incorporated herein by reference in its entirety, can be extended, or a new event filter “Assigned trajectory” can be added, as shown in Table 1 below. It is to be noted here that, the term “assigned trajectory”, “assigned (flight) path”, “planned (flight) path”, “expected trajectory”, or the like is used interchangeably with “expected (flight) path” in the context of the present disclosure. A UAV may have a primary flight path and one or more secondary / altemative flight paths.

[0040] Table 1: Example of Event Filters for AMF exposure events

[0041] In addition, the AMF event types defined in Table 6.2.6.3.3-1 of the 3GPP TS 29.518,

[0042] VI 8.6.0, which is incorporated herein by reference in its entirety, can be extended to include a new AMF event type, e.g., “UE MOVE TRACKING REPORT” as defined in Table 2 below.

[0043] Table 2: Enumeration AmfEventType

[0044] When the information for the assigned flight path of the UAV is included in the

[0045] Namf_EventExposure_Subscribe request, the AMF events defined in Table 6.2.6.2.3-1 of the 3 GPP TS 29.518, VI 8.6.0 can be extended as shown in Table 3 below.

[0046] Table 3 : Definition of type AmfEvent

[0047] When the information for the assigned flight path of the UAV is included in the subscription data received from the UDM, the subscription data, or subscription data change, may be included in e.g., an Nudm_SDM_Notifi cation, which may include ExpectedUeBehaviorData in AccessAndMobilitySubscriptionData. Accordingly, the Type ExpectedUeBehaviourData defined in Table 6.1.6.2.49-1 of the 3GPP TS 29.503, VI 8.6.0, which is incorporated herein by reference in its entirety, can be extended, as shown in Table 4 below.

[0048] Table 4: Definition of type ExpectedUeBehaviourData

[0049] The Type Trajectory Segment is defined in Table 5 below.

[0050] Table 5: Definition of type Trajectory Segment

[0051] Also, the Type LocationArea defined in Table 6.5.6.2.10-1 of the 3GPP TS 29.503, V18.6.0 can be extended, as shown in Table 6 below. Table 6: Definition of type LocationArea

[0052] Accordingly, the type ExpectedUeBehaviour defined in Table 6.5.6.2.8-1 of the 3GPP TS 29.503, V18.6.0, can be extended as shown in Table 7 below.

[0053] Table 7: Definition of type ExpectedUeBehaviour

[0054] In an example, when the UAV is to be served by a new AMF, the information for the assigned flight path of the UAV may be passed from an old AMF to the new AMF in Namf_Communication_CreateUeContext service request, the type ExpectedUeBehavior defined in Table 6.1.6.2.51-1 of the 3GPP TS 29.518, VI 8.6.0 can be extended as shown in Table 8 below. Table 8: Definition of type ExpectedUeBehavior

[0055] The Type Trajectory Segment is defined in Table 9 below, which may be added under clause

[0056] 6.1.6.2 in 3GPP TS 29.518, as a new table 6.1.6.2.xx-l

[0057] Table 9: Definition of type Trajectory Segment

[0058] The Type ExpectedUeLocation is defined in Table 10 below, which may be added under clause 6.1.6.2 in 3GPP TS 29.518, as a new table 6.1.6.2.yy-l.

[0059] Table 10: Definition of type ExpectedUeLocation

[0060] Fig. 2 is a flowchart illustrating a method 200 according to an embodiment of the present disclosure. The method 200 can be performed by a network exposure function (which may be e.g., an NEF, an SCEF, or any network function for network / service exposure in a future evolved network) or UAV management network function (which may be e.g., a UAS NF).

[0061] At block 210, the network exposure function or UAV management network function transmits, to a network function for mobility management (which may be e.g., an AMF, an MME, or any network function for mobility management in a future evolved network), a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Optionally, different segments are served by different USS-s.

[0062] At block 220, the network exposure function or UAV management network function receives the notification from the network function for mobility management, e.g., when the UAV deviates from the assigned flight path and / or the UAV moves across segments in the assigned flight path.

[0063] As an example, the subscription request may be an Namf_EventExposure_Subscribe request, and the notification may be an Namf_EventExposure_Notify message, as described above in connection with the method 100.

[0064] In an example, the network exposure function or UAV management network function may receive, from a USS (e.g., a serving USS of the UAV), information for the assigned flight path, and transmit the information to the network function for mobility management or a data management function (which may be e.g., a UDM, an HSS, or any network function for data management in a future evolved network).

[0065] Here, in an example, the information for the assigned flight path of the UAV may include: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

[0066] Alternatively or additionally, the information may include a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS. The information may include, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

[0067] In an example, the UAV deviating from the assigned flight path may include at least one of: the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information. Here, optionally, the term “location area” may refer to a geographical area or 3GPP identification area (e.g., TA or cell) on the earth surface and may not involve the concept of altitude or height. Or alternatively the term “location area” can be implemented as not only including 3 GPP identification area (e.g., TA or cell) on the earth surface, but also including the concept of altitude or height.

[0068] In an example, when the information for the assigned flight path is transmitted to the network function for mobility management, the information may be contained in the subscription request in the block 210. In particular, the AMF events defined in Table 3 can be used.

[0069] Alternatively, when the information for the assigned flight path is transmitted to the data management function, the information may be transmitted / included in a parameter provisioning request. For example, the parameter provisioning request may be an Nudm ParameterProvision Update request for updating ExpectedUeBehaviourData. The Type ExpectedUeBehaviourData defined in Table 6.1.6.2.49-1 of the 3GPP TS 29.503, V18.6.0 can be extended, referring to Tables 4-7 above.

[0070] In an example, the network exposure function or UAV management network function may further transmit, to the USS or another USS related to the UAV’s deviation or movement (e.g,. a target USS for a USS changeover of the UAV), a further notification indicating that the UAV deviates from the assigned flight path and / or that the UAV moves across segments in the assigned flight path.

[0071] Fig. 3 is a flowchart illustrating a method 300 according to an embodiment of the present disclosure. The method 300 can be performed by a USS.

[0072] At block 310, the USS transmits, to a network exposure function (which may be e.g., an NEF, an SCEF, or any network function for network / service exposure in a future evolved network) or UAV management network function (which may be e.g., a UAS NF), information for an assigned flight path of a UAV.

[0073] Here, in an example, the information for the assigned flight path of the UAV may include: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path. Alternatively or additionally, the information may include a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS. The information may include, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

[0074] In an example, the USS may further receive, from the network exposure function or UAV management network function, a notification indicating that the UAV deviates from the assigned flight path and / or that the UAV moves across segments in the assigned flight path, wherein different segments are served by different USS-s.

[0075] In an example, the UAV deviating from the assigned flight path may include at least one of: the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information. Here, optionally, the term “location area” may refer to a geographical area or 3GPP identification area (e.g., TA or cell) on the earth surface and may not involve the concept of altitude or height. Or alternatively the term “location area” can be implemented as not only including 3 GPP identification area (e.g., TA or cell) on the earth surface, but also including the concept of altitude or height.

[0076] Fig. 4 is a flowchart illustrating a method 400 according to an embodiment of the present disclosure. The method 400 can be performed by a data management function (which may be e.g., a UDM, an HSS, or any network function for data management in a future evolved network).

[0077] At block 410, the data management function receives, from a network exposure function (which may be e.g., an NEF, an SCEF, or any network function for network / service exposure in a future evolved network) or UAV management network function (which may be e.g., a UAS NF), a parameter provisioning request containing information for an assigned flight path of a UAV. In particular, the parameter provisioning request may be an Nudm ParameterProvision Update request for updating ExpectedUeBehaviourData, referring to Tables 4-7 above. At block 420, the data management function transmits, to a network function for mobility management (which may be e.g., an AMF, an MME, or any network function for mobility management in a future evolved network), subscription data of the UAV. The subscription data of the UAV contains the information. In particular, the subscription data, or subscription data change, may be included in e.g., an Nudm_SDM_Notification, which may include ExpectedUeBehaviorData in AccessAndMobilitySubscriptionData, referring to Tables 4-7 above.

[0078] Here, in an example, the information for the assigned flight path of the UAV may include: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

[0079] Alternatively or additionally, the information may include a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS. The information may include, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

[0080] The above methods 100-400 will be further explained with reference to Figs. 5 and 6.

[0081] Fig. 5 shows a procedure of UAV changeover from one USS to another serving different geographical areas. This procedure utilizes Solution #1 of the NEF-assisted pre-mission flight planning as specified in clause 6.1 of TR 23.700-59 and includes the following main steps.

[0082] 1. The UAV (or UAV controller (UAV-C)) establishes a Packet Data Unit (PDU) Session for communication with a serving USS (USS 1).

[0083] 2. The UAV (or via its paired UAV-C) requests a Pre-mission flight planning service from the serving USS, if needed. The request message includes an identifier of the UAV, 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. Otherwise, continues in step 3. 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, OAM, other proprietary means, etc. that are not in scope of the study but assumed), the serving USS (USS 1) determines target USS (one or more) that may serve as a target USS. Once USS 1 pre-selects suitable target US S-s (USS 2), USS 1 triggers communication with each of the target USS to determines candidate border-crossing point(s) for the UAV.

[0084] 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 will leave serving USS area) that can be used by the 5thGeneration Core (5GC) to provide flight planning assistance information. This information 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.

[0085] 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, 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 (e.g. requirements on the flight path, candidate flight path(s), accuracy level of predictions relevant to the flight planning).

[0086] 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 border-crossing point(s) in form of geographical coordinates, the NEF maps them to a list of border cell IDs / TAIs.

[0087] 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. Network Data Analytics Function (NWDAF) analytics service for Movement Behaviour analytics, Gateway Mobile Location Center (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 / as signed trajectory). 6. The NEF / UAS NF invokes service operations towards the identified NFs as described in Steps 8-12 of the procedure for the NEF-assisted pre-mission flight planning in clause 6.1.3.1 of TR 23.700-59.

[0088] 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 Next Generation Radio Access Network (NG-RAN) nodes in all identified border cell(s) / TA(s); for that the NEF / UAS NF uses the Nnrf_NFDiscovery service from Network Repository Function (NRF). Once the AMF(s) information is retrieved, the NEF / UAS NF invokes an Namf_EventExposure_Subscribe request to subscribe to the UE / UAV's presence in the area of interest wherein the area of interest is set to a cell ID / TAI of every identified border cell / TA.

[0089] 8. Once the NEF receives the relevant information from the determined 5GC NFs in Steps 3-7, the NEF / UAS NF responds to the Pre-mission flight planning assistance request from the USS 1 with the collected information. This information is for UAV's flight path between the starting point and all candidate USS border-crossing points.

[0090] 9. Once the serving USS receives a response to its Pre-mission flight planning assistance request, USS 1 determines / selects a target USS from a list of pre-selected 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) to the destination point in the geographical area served by USS 2.

[0091] 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.

[0092] 11. The target USS (USS 2) provides the serving USS (USS 1) information about UAV's flight path(s) from a border cell(s) / TA(s) to the destination point (e.g. primary flight path, secondary / altemative flight path).

[0093] 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 border-crossing points and cells / TAs.

[0094] 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.

[0095] 12a. After the serving USS determines the primary, secondary etc. flight paths for the UAV, the serving USS sends this information to the NEF / UAS NF; for that the USS may re-use the existing service operation as specified in Step 4 or anew service operation (e.g. Nnef_PreMissionFlighPlanning_InfoNotify). In this request, the serving USS may also include additional flight path information for each of the geographical segments (served by US SI and USS2), for instance, UAV’s speed, flight height / altitude and / or time schedule for crossing / spending at each of the TAs / cells.

[0096] During the UAV flight (and to perform the changeover from USS 1 to USS 2):

[0097] 13. Once the NEF / UAS NF receives information from the serving USS about the planned flight path for the UAV (in Step 12a), the NEF / UAS NF may invoke additional services 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. The trajectory may possibly include multiple segments where each segment is served by a different USS instance.

[0098] The NEF / UAS NF uses the AMF event exposure service to subscribe to get notified when the UAV does not follow (i.e., deviates from) the flight plan. In order to detect a deviation, additional parameters (such as time schedule and height as well as acceptable deviations) are considered. For this purpose, either of the following two alternatives can be implemented:

[0099] Alternative#!: Anew AMF event exposure event may be introduced or the existing one, e.g. Location Report, may be reused. In any case, the NEF sends the AMF event exposure subscription request to the serving AMF with the planned flight path information, which consists of a list of 3GPP locations (i.e. TAIs or cell IDs) together with the time schedule describing when the UE shall be present at these locations (and optionally, acceptable deviations, e.g. UE is not arriving on time). The AMF shall send a notification if the UE is not following (i.e., deviating from) the flight plan / route.

[0100] If the existing event exposure event is reused, the AMF event exposure event filter is extended with UAV’s flight height and time schedule information so that the AMF exploits the additional flight path information as provided by the serving USS (via the NEF / UAS NF). The event filters for AMF event exposure are extended as shown in Table 1.

[0101] Altemative#2 (not shown in Fig. 5 and will be described in detail with reference to Fig. 6): the existing Expected UE Behaviour parameters specified in clause 4.15.6.3 of TS 23.502 are reused. Specifically, NEF1 invokes the parameter provisioning service from the UDM (i.e., Nudm ParameterProvision Update) to provision the planned flight path information, which consists of a list of 3GPP locations (i.e. TAIs or cell IDs and, optionally, height / altitude information) together with the time schedule describing when the UE shall be present at these locations (and optionally, error range, e.g. UE is not arriving on time or UE is above / below the expected flight altitude). Additionally, the definitions of the expected UE behavior are further enhanced to cover multiple-USS scenario when a flight path / trajectory and time schedule is provided on a per segment basis, where each geographical segment is served by a different USS (see clause 6.5.6.2.8 / 10 of TS 29.503 and Tables 6 and 7). Through the internal process, the UDM will update the expectedUeBehaviourData in the AccessAndMobilitySubscriptionData (see clause 6.1.6.2.4 of TS 29.503), which triggers the UDM to send a notification to the AMF about the subscription change. Additionally, after receiving the notification from the UDM, the AMF may use a Location Report event to report if the UAV is not following the route.

[0102] In either alternative, if the trajectory consists with multiple segments where each segment is served by a different USS instance, a new event filter will be supported for AMF to report event when UAV moving between different segments.

[0103] 14. If NEF1 / UAS NF1 subscribes (in Step 7) to UAV’s presence in the borders cells / TAs, then 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); or when the NEF / UAS NF1 has subscribed for event reporting when UE deviating from expected / assigned trajectory and / or moving across different segments, the AMF notifies the NEF / UAS NF1 when any event is detected.

[0104] 14a. When the NEF1 / UAS NF1 received a report from the AMF indicating the UE is deviating the route, NEF1 / UAS NF1 may further invoke the Ngmlc_Location_ProvideLocation service request on GMLC to get the accurate position of the UAV.

[0105] 14b. The GMLC performs 5G Mobile Terminated Location Request (5G-MT-LR) procedure to retrieve the accurate UAV location via AMF / LMF and provide the UAV location to the NEF1 / UAS NF1 in Ngmlc_Location_ProvideLocation service response.

[0106] 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 notification to USS 1 that the UAV will leave the area; for that purpose, the NEF / UAS NF may use a new service operation (e.g.

[0107] Nnef_PreMissionFlightPlanning_InfoNotify or Nnef_PreMissionFlightPlanning_Notify) that can be send in response to the Nnef_PreMissionFlightPlanning_Get or Nnef_PreMissionFlightPlanning_Subscribe (assuming that they are used to request Pre-mission flight planning assistance in step 4). Inside this 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. 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 the target USS the information regarding which exposure services / notification are of relevance for the UAV, information about UAV's identifiers 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.

[0108] 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.

[0109] The NEF / UAS NF notifies the USS 2 about this event using e.g. a Nnef_PreMissionFlightPlanning_InfoNotify request that can be introduced and used for this purpose.

[0110] 20. The source USS (USS 1) informs the UAV about the changeover to the new USS (USS 2) and, if required, informs the UAV that it needs to reconnect with the target USS (USS 2) and triggers the exposure services towards 5GC NFs similar to what the previous serving USS (USS 1) had before the changeover.

[0111] 21. After receiving all the required information from the source USS, the target USS responds to the Nnef_PreMissionFlightPlanning_InfoNotify request in such a way completing the changeover for the UAV.

[0112] Fig. 6 shows another procedure of UAV changeover from one USS to another serving different geographical areas. This procedure includes the following main steps.

[0113] 0a. UE / UAV performs the registration procedure and, as a part of it, retrieves the “Access and Mobility Subscription Data” from the UDM. Afterwards, the AMF subscribes to changes in the UE’s subscription using the Nudm_SDM_Subscribe requests (as described in clause 4.2.2.2 of TS 23.502, Step 14c).

[0114] Ob. PDU session establishment

[0115] 1.-12. Actions as described in Steps 1-12 in clause 6.10.3 of TR 23.700-59 (see Fig. 5)

[0116] 12a. After the serving USS determines the primary, secondary etc. flight paths for the UAV, the serving USS sends this information to the NEF / UAS NF; for that the USS may re-use the existing service operation as specified in Step 4 or a new service operation (e.g.

[0117] Nnef_PreMissionFlighPlanning_InfoNotify). In this request, the serving USS may also include additional flight path information for each of the segments (served by USS1 and USS2) and the serving USS per segment, for instance, UAV’s speed, flight height / altitude and / or time schedule for crossing / spending at each of the TAs / cells.

[0118] 12b. Alternatively, each USS may provision the segment served by itself. I.e., in step 12a, the US SI provisions the path segment served by US SI and in step 12b, USS2 provisions the path segment served by USS2.

[0119] 12c. The NEF / UAS NF uses an Nudm_ParameterProvision_Update request to update the ExpectedUeBehaviourData (Table 6.1.6.2.49-1 in TS 29.503) parameter so that the “expectedUmts” attribute (as defined in Table 6.5.6.2.8-1 in TS 29.503) could be provided considering multiple segments of UAV’s paths served by different USS-s and specifying the USS-assigned flight plan and time schedule using the LocationArea attributes (as defined in Table 6.5.6.2.10-1 in TS 29.503). Note that both parameters (i.e. “expectedUmts” and “LocationArea”) are enhanced to accommodate the required functionality (see Tables 4-7).

[0120] If each USS provide the segment served by itself, the NEF / UAS NF will aggregated the segments from different USS-s when providing to UDM.

[0121] 12d. Once receiving the Nudm_ParameterProvision_Update request from the NEF with the new parameters, the UDM updates the expectedUeBehaviourData in the AccessAndMobilitySubscriptionData (Table 6.1.6.2.4-1 in TS 29.503), which triggers the UDM to send a notification (i.e. Nudm_SDM_Notification) to the AMF about the subscription change.

[0122] 13. The NEF / UAS NF subscribes with the AMF to event exposure to get notified when the UAV deviates from the assigned flight plan (including time schedule) specified via ExpectedUeBehaviourData and / or when UE moving across segments.

[0123] 14-15. In case the UAV deviated from the assigned flight plan (including time schedule) or when UE moving across segments, the AMF notifies the subscribed NEF / UAS NF about the event. Based on the received notification, the NEF / UAS NF determines which USS might be affected and therefore needs to be informed about UAV’s deviation from the assigned flight plan (e.g., USSl or USS2).

[0124] 14a. The NEF / UAS NF based on the information provided from the USS-s, determines which USS will be interested for the event, i.e. the serving USS of the related segments, e.g. the UE is deviating from which segment, or the UE is leaving / entering which segments.

[0125] For further details of some steps in Figs. 5 and 6, reference can be made to TR 23.700-59.

[0126] Correspondingly to the method 100 as described above, a network function for mobility management is provided. Fig. 7 is a block diagram of a network node 700 according to an embodiment of the present disclosure. The network node 700 is configured to implement a network function for mobility management. As shown in Fig. 7, the network node 700 includes a receiving unit 710 configured to receive, from a network exposure function or an UAV management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The network node 700 further includes a transmitting unit 720 configured to transmit the notification to the network exposure function or the UAV management network function. For other optional operations by the units 710 and 720 and other units of the network node 700, reference can be made to the operations described above in connection with the method 100.

[0127] The units 710 and 720 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 1.

[0128] Correspondingly to the method 200 as described above, a network exposure function or UAV management network function is provided. Fig. 8 is a block diagram of a network node 800 according to an embodiment of the present disclosure. The network node 800 is configured to implement a network exposure function or UAV management network function.

[0129] As shown in Fig. 8, the network node 800 includes a transmitting unit 810 configured to transmit, to a network function for mobility management, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The network node 800 further includes a receiving unit 820 configured to receive the notification from the network function for mobility management. For other optional operations by the units 810 and 820 and other units of the network node 800, reference can be made to the operations described above in connection with the method 800.

[0130] The units 810 and 820 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 2.

[0131] Correspondingly to the method 300 as described above, a USS is provided. Fig. 9 is a block diagram of a network node 900 according to an embodiment of the present disclosure. The network node 900 is configured to implement a USS. As shown in Fig. 9, the network node 900 includes a transmitting unit 910 configured to transmit, to a network exposure function or UAV management network function, information for an assigned flight path of a UAV. For other optional operations by the unit 910 and other units of the network node 900, reference can be made to the operations described above in connection with the method 300.

[0132] The unit 910 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 3.

[0133] Correspondingly to the method 400 as described above, a data management function is provided. Fig. 10 is a block diagram of a network node 1000 according to an embodiment of the present disclosure. The network node 1000 is configured to implement a data management function.

[0134] As shown in Fig. 10, the network node 1000 includes a receiving unit 1010 configured to receive, from a network exposure function or UAV management network function, a parameter provisioning request containing information for an assigned flight path of a UAV. The network node 1000 further includes a transmitting unit 1020 configured to transmit, to a network function for mobility management, subscription data of the UAV. The subscription data of the UAV contains the information. For other optional operations by the units 1010 and 1020 and other units of the network node 1000, reference can be made to the operations described above in connection with the method 400.

[0135] The units 1010 and 1020 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 4.

[0136] Fig. 11 is a block diagram of a network node 1100 according to an embodiment of the present disclosure.

[0137] The network node 1100 includes a communication interface 1110, a processor 1120 and a memory 1130.

[0138] The memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a network function for mobility management, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 1. Particularly, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a network function for mobility management: receive, from a network exposure function or an UAV management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the network function for mobility management: transmit the notification to the network exposure function or the UAV management network function. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the network function for mobility management, perform other optional operations and / or implement other optional features described above in connection with Fig. 1 and the method 100.

[0139] Alternatively, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a network exposure function or UAV management network function, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 2. Particularly, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a network exposure function or UAV management network function: transmit, to a network function for mobility management, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path. Different segments are served by different USS-s. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the network exposure function or UAV management network function: receive the notification from the network function for mobility management. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the network exposure function or UAV management network function, perform other optional operations and / or implement other optional features described above in connection with Fig. 2 and the method 200.

[0140] Alternatively, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a USS, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 3. Particularly, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a USS: transmit, to a network exposure function or UAV management network function, information for an assigned flight path of a UAV. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the USS, perform other optional operations and / or implement other optional features described above in connection with Fig. 3 and the method 300.

[0141] Alternatively, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a data management function, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 4. Particularly, the memory 1130 may contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing a data management function: receive, from a network exposure function or UAV management network function, a parameter provisioning request containing information for an assigned flight path of a UAV. The method further includes: transmit, to a network function for mobility management, subscription data of the UAV. The subscription data of the UAV contains the information. The memory 1130 may further contain instructions executable by the processor 1120 whereby the network node 1100 is operative to, when implementing the data management function, perform other optional operations and / or implement other optional features described above in connection with Fig. 4 and the method 400.

[0142] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory and a hard drive. The computer program product includes a computer program. The computer program includes: code / computer readable instructions, which when executed by the processor 1120 causes the network node 1100 to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 1, 2, 3, or 4.

[0143] The computer program product may be configured as a computer program code structured in computer program modules. The computer program modules could essentially perform the actions of the flow illustrated in Fig. 1, 2, 3, or 4.

[0144] The processor may be a single CPU (Central Processing Unit), but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and / or related chips sets and / or special purpose microprocessors such as Application Specific Integrated Circuits (ASICs). The processor may also comprise board memory for caching purposes. The computer program may be carried in a computer program product connected to the processor. The computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random Access Memory (RAM), a Read-Only Memory (ROM), or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories. The disclosure has been described above with reference to embodiments thereof. It should be understood that various modifications, alternations and additions can be made by those skilled in the art without departing from the spirits and scope of the disclosure. Therefore, the scope of the disclosure is not limited to the above particular embodiments but only defined by the claims as attached.

Claims

CLAIMS1. A method (100) in a network function for mobility management, comprising:- receiving (110), from a network exposure function or an Uncrewed Aerial Vehicle, UAV, management network function, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path; and- transmitting (120) the notification to the network exposure function or the UAV management network function.

2. The method (100) of claim 1, wherein transmitting (120) the notification to the network exposure function or the UAV management network function comprises:- transmitting (120) the notification to the network exposure function or the UAV management network function when the UAV deviates from the assigned flight path and / or the UAV moves across segments in the assigned flight path.

3. The method (100) of claim 1 or 2, wherein different segments are served by different UAS Service Suppliers, USS-s.

4. The method (100) of any one of claims 1 to 3, further comprising:- obtaining information for the assigned flight path of the UAV from the subscription request; or- receiving, from a data management function, subscription data of the UAV, wherein the subscription data of the UAV contains information for the assigned flight path of the UAV; or- receiving information for the assigned flight path of the UAV from another network function for mobility management.

5. The method of claim 4, further comprising:- transmitting the information for the assigned flight path of the UAV to another network function for mobility management, wherein the UAV is to be served by the other network function for mobility management.

6. The method (100) of claim 4 or 5, wherein the information for the assigned flight path of the UAV comprises:a list of Tracking Area Identifiers, TAIs, or cell Identifiers, IDs, each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; and / or expected altitude information.

7. The method (100) of claim 6, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

8. The method (100) of any one of claims 4-7, wherein the information for the assigned flight path of the UAV comprises: a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS.

9. The method (100) of claim 8, wherein the information for the assigned flight path of theUAV comprises, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; and / or expected altitude information.

10. The method (100) of claim 9, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

11. The method (100) of claim 7 or 10, wherein the UAV deviating from the assigned flight path comprises at least one of:the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information.

12. A method (200) in a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, comprising:- transmitting (210), to a network function for mobility management, a subscription request for a notification indicating that a UAV deviates from an assigned flight path and / or that the UAV moves across segments in the assigned flight path; and- receiving (220) the notification from the network function for mobility management.

13. The method (200) of claim 12, wherein receiving (220) the notification from the network function for mobility management when the UAV deviates from the assigned flight path and / or the UAV moves across segments in the assigned flight path.

14. The method (200) of claim 12 or 13, wherein different segments are served by different UAS Service Suppliers, USS-s.

15. The method (200) of any of claims 12 to 14, further comprising:- receiving, from a UAS Service Supplier, USS, information for the assigned flight path; and- transmitting the information to the network function for mobility management or a data management function.

16. The method (200) of claim 15, wherein the information is contained in the subscription request.

17. The method (200) of claim 15, wherein said transmitting the information to the data management function comprises:transmitting, to the data management function, the information in a parameter provisioning request.

18. The method (200) of any of claims 15 to 17, wherein the information comprises: a list of Tracking Area Identifiers, TAIs, or cell Identifiers, IDs, each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; and / or expected altitude information.

19. The method (200) of claim 18, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

20. The method (200) of any of claims 15-19, wherein the information comprises: a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS.

21. The method (200) of claim 20, wherein the information comprises, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; and / or expected altitude information.

22. The method (200) of claim 21, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

23. The method (200) of claim 19 or 22, wherein the UAV deviating from the assigned flight path comprises at least one of: the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information.

24. The method (200) of any one of claims 12-23, further comprising:- transmitting, to the USS or another USS related to the UAV’s deviation or movement, a further notification indicating that the UAV deviates from the assigned flight path and / or that the UAV moves across segments in the assigned flight path.

25. A method (300) in an Uncrewed Aerial System ‘UAS’ Service Supplier, USS, comprising:- transmitting (310), to a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, information for an assigned flight path of a UAV.

26. The method (300) of claim 25, wherein the information comprises: a list of Tracking Area Identifiers, TAIs, or cell Identifiers, IDs, each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; and / or expected altitude information.

27. The method of claim 26, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

28. The method (300) of any one of claims 25-27, wherein the information comprises:a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one USS.

29. The method (300) of claim 28, wherein the information for the assigned flight path of the UAV comprises, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; and / or expected altitude information.

30. The method of claim 29, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

31. The method (300) of any one of claims 25-30, further comprising:- receiving, from the network exposure function or UAV management network function, a notification indicating that the UAV deviates from the assigned flight path and / or that the UAV moves across segments in the assigned flight path.

32. The method (300) of claim 31, wherein different segments are served by different USS-s.

33. The method (300) of claim 31 or 32, wherein the UAV deviating from the assigned flight path comprises at least one of: the UAV arriving at a location area represented by a TAI or cell ID that is not included in the list indicated in the information, the UAV arriving at or being present in a location area in the assigned flight path at time different from the time indicated in the information or outside the range of time indicated in the information, or the UAV being located, when present in a location area in the assigned flight path, at an altitude lower than the lowest altitude indicated in the information or higher than the highest altitude indicated in the information.

34. A method (400) in a data management function, comprising:- receiving (410), from a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, a parameter provisioning request containing information for an assigned flight path of a UAV; and transmitting (420), to a network function for mobility management, subscription data of the UAV, wherein the subscription data of the UAV contains the information.

35. The method (400) of claim 34, wherein the information comprises: a list of Tracking Area Identifiers, TAIs, or cell Identifiers, IDs, each representing a location area the UAV is expected to visit in the assigned flight path; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the assigned flight path; and / or expected altitude information.

36. The method (400) of claim 35, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the assigned flight path.

37. The method (400) of any one of claims 34-36, wherein the information comprises: a list of segments each containing one or more TAIs or cell IDs representing one or more location areas along the assigned flight path, each segment being served by one UAS Service Supplier, USS.

38. The method (400) of claim 37, wherein the information for the assigned flight path of the UAV comprises, for each segment: a list of TAIs or cell IDs each representing a location area the UAV is expected to visit in the segment; time or a range of time at which the UAV is expected to arrive at or present in at least one location area in the segment; and / or expected altitude information.

39. The method (400) of claim 38, wherein the expected altitude information comprises: a lowest altitude at which the UAV is expected to be located when present in at least one location area in the segment; and / or a highest altitude at which the UAV is expected to be located when present in at least one location area in the segment.

40. Anetwork node (1100), comprising a communication interface (1110), a processor (1120), and a memory (1130), the memory (1130) comprising instructions executable by the processor (1120) whereby the network node (1100) is operative to, when implementing a network function for mobility management, perform the method according to any of claims 1-11, or when implementing a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, perform the method according to any of claims 12-24, or when implementing an Uncrewed Aerial System ‘UAS’ Service Supplier, USS, perform the method according to any of claims 25-33, or when implementing a data management function, perform the method according to any of claims 34-39.

41. A computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of a network node, configure the network node to, when implementing a network function for mobility management, perform the method according to any of claims 1-11, or when implementing a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, perform the method according to any of claims 12-24, or when implementing an Uncrewed Aerial System ‘UAS’ Service Supplier, USS, perform the method according to any of claims 25-33, or when implementing a data management function, perform the method according to any of claims 34-39.

42. A computer program product, comprising computer-readable instructions which, when executed by a processor of a network node, configure the network node to, when implementing a network function for mobility management, perform the method according to any of claims 1-11, or when implementing a network exposure function or Uncrewed Aerial Vehicle, UAV, management network function, perform the method according to any of claims 12-24, or when implementing an Uncrewed Aerial System ‘UAS’ Service Supplier, USS, perform the method according to any of claims 25-33, or when implementing a data management function, perform the method according to any of claims 34-39.

Images