FLIGHT INFORMATION REPORTING FOR AIRBORNE UEs TECHNICAL FIELD [0] Embodiments of the present disclosure relate to methods, apparatus and computer-readable media for information reporting for User Equipment (UE), and particularly to flight information reporting for airborne UEs. BACKGROUND [1] The world is witnessing widespread and increasing use of drones, otherwise known as Unmanned Aerial Vehicles (UAV), in many segments of the economy and in daily life. There are numerous use cases of UAVs in industry, such as goods transportation and delivery, surveillance, media production, etc. [2] Traditionally, UAVs can only be flown by a controller within the visual line of sight (VLoS). To realize the potential associated with connecting drones beyond visual line of sight (BVLoS) via cellular networks, the 3rd Generation Partnership Project (3GPP) have specified multiple features in Long-Term Evolution (LTE) Rel-15, with the aim of improving the efficiency and robustness of terrestrial LTE network for providing aerial connectivity services, particularly for low altitude UAVs. These features target both command-and-control traffic for flying the drone and the data (also known as payload) traffic from the drone to the cellular network. The key features specified include: - Support for subscription-based identification - Height reporting when UAV crosses height threshold. The report includes height, location (3D), horizontal and vertical speed. - Reference Symbol/Signal Received Power (RSRP) reporting per event of N cells’ signal power above a threshold. The report includes RSRP/Reference Symbol/Signal Received Quality (RSRQ)/location(3D). - UE-specific Uplink (UL) power control. - Flight path information provided from UE to eNB. This includes network polling and list(s) of waypoints (3D location), and time stamps, if available. [3] Flight path reporting for UAVs in LTE Rel-15 [4] A Technical Specification entitled “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2” (TS 36.300, V 17.1.0, available at https://portal.3gpp.org/desktopmodules/Specifications/Specif icationDetails.aspx?specific ationId=2430 as of 24 July 2023) provides an overview and overall description of the E- UTRAN radio interface protocol architecture. Section “23.17.5 Flight path information reporting” explains the following: [5] “E-UTRAN can request a UE to report flight path information consisting of a number of waypoints defined as 3D locations as defined in TS 36.355 [78]. A UE reports up to configured number of waypoints if flight path information is available at the UE. The report can consist also time stamps per waypoint if configured in the request and if available at the UE.” [6] The signaling is over Radio Resource Control (RRC) and is specified in a Technical Specification entitled “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification” (TS 36.331, V 17.1.0, uploaded to https://portal.3gpp.org/desktopmodules/Specifications/Specif icationDetails.aspx?specific ationId=2440 on 20.7.2022). This technical specification specifies the RRC protocol for the radio interface between UE and E-UTRAN as well as for the radio interface between RN and E-UTRAN. A UE is assumed to receive the flight path plan from unmanned aircraft systems traffic management (UTM) or that it is preconfigured by a user before the flight and hence before the RRC connection. [7] Flight path configuration and report in TS 36.331 V17.1.020.7.2022: [8] This Information Element (IE) configures, for the UE, the max number of waypoints that the UE can report back. It also configures the UE to report time stamps, if these are wanted by the network:  [9] FlightPathInfoReportConfig information element -- ASN1START FlightPathInfoReportConfig-r15 ::= SEQUENCE { maxWayPointNumber-r15 INTEGER (1..maxWayPoint-r15), includeTimeStamp-r15 ENUMERATED {true} OPTIONAL } -- ASN1STOP FlightPathInfoReportConfig field descriptions maxWayPointNumber includeTimeStamp Indicates whether time stamp of each way point can be reported in the flight path information report if time stamp information is available at the UE. [10] This IE corresponds to the report itself: FlightPathInfoReport-r15 ::= SEQUENCE { flightPath-r15 SEQUENCE (SIZE (1..maxWayPoint-r15)) OF WayPointLocation-r15 OPTIONAL, dummy SEQUENCE {} OPTIONAL } WayPointLocation-r15 ::= SEQUENCE { wayPointLocation-r15 LocationInfo-r10, timeStamp-r15 AbsoluteTimeInfo- r10 OPTIONAL } [11] And these are the elements in the report: [12] – LocationInfo [13] The IE LocationInfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information. LocationInfo information element -- ASN1START LocationInfo-r10 ::= SEQUENCE { locationCoordinates-r10 CHOICE { ellipsoid-Point-r10 OCTET STRING, ellipsoidPointWithAltitude-r10 OCTET STRING, ..., ellipsoidPointWithUncertaintyCircle-r11 OCTET STRING, ellipsoidPointWithUncertaintyEllipse-r11 OCTET STRING, ellipsoidPointWithAltitudeAndUncertaintyEllipsoid-r11 OCTET STRING, ellipsoidArc-r11 OCTET STRING, polygon-r11 OCTET STRING }, horizontalVelocity-r10 OCTET STRING OPTIONAL, gnss-TOD-msec-r10 OCTET STRING OPTIONAL, ..., [[ verticalVelocityInfo-r15 CHOICE { verticalVelocity-r15 OCTET STRING, verticalVelocityAndUncertainty-r15 OCTET STRING } OPTIONAL ]] } -- ASN1STOP LocationInfo field descriptions ellipsoidArc Parameter EllipsoidPointWithAltitude defined in TS 36.355 [54]. The first/leftmost bit of the first Parameter EllipsoidPointWithAltitudeAndUncertaintyEllipsoid defined in TS 36.355 [54]. The first/leftmost bit of the first octet contains the most significant bit. ellipsoidPointWithUncertaintyCircle Parameter Ellipsoid-PointWithUncertaintyCircle defined in TS 36.355 [54]. The first/leftmost bit of the first octet contains the most significant bit. ellipsoidPointWithUncertaintyEllipse Parameter EllipsoidPointWithUncertaintyEllipse defined in TS 36.355 [54]. The first/leftmost bit of the first octet contains the most significant bit. gnss-TOD-msec Parameter Gnss-TOD-msec defined in TS 36.355 [54]. The first/leftmost bit of the first octet contains the most significant bit. horizontalVelocity Parameter HorizontalVelocity defined in TS 36.355 [54]. The first/leftmost bit of the first octet ns the most significant bit. on Parameter Polygon defined in TS 36.355 [54]. The first/leftmost bit of the first octet contains the Parameter verticalVelocityAndUncertainty corresponds to . [14] AbsoluteTimeInfo [15] The IE AbsoluteTimeInfo indicates an absolute time in a format YY-MM-DD HH:MM:SS and using Binary-Coded Decimal (BCD) encoding. The first/ leftmost bit of the bit string contains the most significant bit of the most significant digit of the year and so on. AbsoluteTimeInfo information element -- ASN1START AbsoluteTimeInfo-r10 ::= BIT STRING (SIZE (48)) -- ASN1STOP [16] Flight path reporting for UAVs in 5G New Radio (NR) [17] In RAN#94-e, a new Rel-18 Work Item (WI) for supporting UAV in NR was approved in RP-123600 (RP-123600, New WID on NR support for UAV (Uncrewed Aerial Vehicles), RAN#94, Dec 2021) and one objective is to specify flight path reporting signaling for NR over RRC. The framework of flight path reporting in LTE Rel-15 is the baseline for the Release 18 discussions. [18] In addition, in Rel-18, 3GPP is also working on a RAN4 work item to support air-to- ground communications (i.e., providing cellular connection to commercial airliners using ground base stations). Among other things, flight path reporting from airplanes to network is also being discussed. [19] The existing location information in NR below can be used as a starting point for UAV/airplane flight path reporting. [Text from TS 38.331: 3GPP TS 38.331 V17.1.0 (2022-06)] – LocationInfo The IE LocationInfo is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE. LocationInfo information element -- ASN1START -- TAG-LOCATIONINFO-START LocationInfo-r16 ::= SEQUENCE { commonLocationInfo-r16 CommonLocationInfo-r16 OPTIONAL, bt-LocationInfo-r16 LogMeasResultListBT-r16 OPTIONAL, wlan-LocationInfo-r16 LogMeasResultListWLAN-r16 OPTIONAL, sensor-LocationInfo-r16 Sensor-LocationInfo-r16 OPTIONAL, ... } -- TAG-LOCATIONINFO-STOP -- ASN1STOP – CommonLocationInfo The IE CommonLocationInfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information. CommonLocationInfo information element -- ASN1START -- TAG-COMMONLOCATIONINFO-START CommonLocationInfo-r16 ::= SEQUENCE { gnss-TOD-msec-r16 OCTET STRING OPTIONAL, locationTimestamp-r16 OCTET STRING OPTIONAL, locationCoordinate-r16 OCTET STRING OPTIONAL, locationError-r16 OCTET STRING OPTIONAL, locationSource-r16 OCTET STRING OPTIONAL, velocityEstimate-r16 OCTET STRING OPTIONAL } -- TAG-COMMONLOCATIONINFO-STOP -- ASN1STOP

CommonLocationInfo field descriptions TOD [20] Unmanned Aircraft Systems (UAS) Traffic Management (UTM) [21] A key goal is to keep the airspace safe and accessible. Therefore, a system called UTM is being developed in different parts of the world to manage the traffic of the UAS (a UAS is composed of a UAV and a UAV controller used by an operator with unique credentials and identities.) According to the National Aeronautics and Space Administration (NASA), UTM is a collaborative, automated, and federated airspace management approach that enables safe, efficient, and equitable small UAS operations at scale. The concept of UTM is being adopted and implemented by many countries and regions in the world, e.g., in the US, Europe, Japan, Australia, etc. [22] According to TS 36.300 Section “23.17.5 Flight path information reporting” V17.1.0, the UTM provides many flight-related functions for UAVs and UAV operators, for example: - Remote identification: enabling UAV identification. - Operation planning: flight planning considering various aspects e.g., UAV performance, whether condition. - Operator messaging: message exchange between operators for e.g., position and status information. - Federal Aviation Administration (FAA) messaging: providing on-demand, periodic, or event-triggered communications with FAA systems to meet regulatory requirements. - Mapping: information about airspace restrictions, obstacles, and sensitive regions. - Conflict advisory: real-time alerting for collision avoidance. [23] Mobile networks can enable reliable connectivity between the UAV and its controller. Meanwhile, UTM can connect to the UAV and the UAV controller through the core network and the radio access network. An illustration of UAS-to-UTM connectivity is provided in Figure 1 (see TS 36.300 Section “23.17.5 Flight path information reporting” V17.1.0). SUMMARY [24] There currently exist certain challenge(s). For example, while flight path reporting was specified in LTE (which is to be used as baseline for NR UAV WI), there is room for improvement when considering the reporting for NR. [25] A first limitation of the LTE flight path reporting is the limited information it provides. For example, it can be difficult to successfully manage real-time flight path changes (e.g., due to an unexpected blocking of certain airspace zones for emergency aerial search or rescue operations, based on the current information elements of waypoints and timestamps. [26] A second limitation of the legacy flight path information lies in the fact in LTE, flight path information comprises, among other things, of a list of waypoints with possibly associated timestamps, which are well suited for automated drone operations having high- precision mission planning. However, the list of waypoints and timestamps reporting is not suitable for semi-automated drone missions and remote-piloted operations, in which a remote pilot takes full control of a drone, for at least some part of the mission. An example of such a case could be semi-automated infrastructure inspection with a fraction of the mission being controlled by a remote operator capturing more details of a zone of interest in the infrastructure. In such a case, the drone plan cannot be represented by a waypoint. [27] For aerial UEs, aspects related to altitude (and height) are important. This is considered in the current NR specifications. However, the representation of 3D volumes is limited to 3D ellipsoids, in the form of an uncertainty ellipsoid. Having only one 3D volume representation can introduce representation errors due to a transformation between different 3D volume representations. For example, if a UE wants to report a volume that is the intersection of several 3D volumes, then this volume is very unlikely to be represented exactly by a 3D ellipsoid. To report this volume to the network, the UE needs to find a 3D ellipsoid that best represents the original 3D volume, and this introduces representation errors due to the addition and removal of volume due the difference in volume representations. [28] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments herein propose additional information that may be provided by a UAV to the network in order to improve tracking of the UAV, and safety in the event that the UAV malfunctions or loses power. [29] In a first aspect of the disclosure, a method is performed by a UAV. The method comprises sending a first message to a first network node in a communications network. The first message comprises at least one of the following options: a first waypoint and an indication of a first duration of time in which the first waypoint is valid; an indication of a switch in a measurement mode of the UAV; information related to operating conditions of the UAV; a reliability metric; an indication of a landing spot to be used by the UAV in case of an emergency landing; and an indication of an area or volume in which the UAV intends to remain. [30] In a second aspect of the disclosure, a method is performed by a first network node in a communications network. The method comprises receiving a first message from a UAV. The first message comprises at least one of the following options: a first waypoint and an indication of a first duration of time in which the first waypoint is valid; an indication of a switch in a measurement mode of the UAV; information related to operating conditions of the UAV; a reliability metric; an indication of a landing spot to be used by the UAV in case of an emergency landing; and an indication of an area or volume in which the UAV intends to remain. [31] In a third aspect of the disclosure, a UAV comprises processing circuitry configured to cause the UAV to send a first message to a first network node in a communications network. The first message comprises at least one of the following options: a first waypoint and an indication of a first duration of time in which the first waypoint is valid; an indication of a switch in a measurement mode of the UAV; information related to operating conditions of the UAV; a reliability metric; an indication of a landing spot to be used by the UAV in case of an emergency landing; and an indication of an area or volume in which the UAV intends to remain. [32] In a fourth aspect of the disclosure, a first network node comprises processing circuitry configured to cause the first network node to receive a first message from a UAV. The first message comprises at least one of the following options: a first waypoint and an indication of a first duration of time in which the first waypoint is valid; an indication of a switch in a measurement mode of the UAV; information related to operating conditions of the UAV; a reliability metric; an indication of a landing spot to be used by the UAV in case of an emergency landing; and an indication of an area or volume in which the UAV intends to remain. [33] Certain embodiments may provide one or more of the following technical advantage(s). [34] It is an object of some embodiments to provide additional information in the flight path reports that may help the network to optimize the use of radio resources for UAV communication in scenarios such as when real-time changes in flight paths are performed, e.g. due to scenarios such as emergency closure of airspace. [35] It is a further object of some embodiments herein to incorporate volume or area information in flight paths, representing the region in which the aerial vehicle is allowed to fly. This is advantageous over waypoints and time stamp information in scenarios, for example, where a remote pilot operates the drone for reconnaissance, in which case, a highly specific way point information cannot be planned in advance. [36] It is a further object of some embodiments herein to provide additional representations of 3D volumes (compared to the simple ellipsoids described above). This may help to mitigate errors due to the transformation from a first volume representation to a second volume representation. BRIEF DESCRIPTION OF THE DRAWINGS [37] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which: Fig.1 shows an example of UAS to UTM connectivity; Fig.2 is a flow chart illustrating a method in accordance with some embodiments; Fig.3 is a flow chart illustrating a method in accordance with some embodiments; Fig. 4 shows an example of a communication system in accordance with some embodiments; Fig.5 shows a UE in accordance with some embodiments; Fig.6 shows a network node in accordance with some embodiments; Fig.7 is a block diagram of a host; Fig. 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and Fig.9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION [38] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [39] Embodiments here relate to new types of information that can be added to messages such as flight path reports to improve the usefulness of the report. As described in more detail below, examples of the new contents include, but are not limited to: various indications of the reliability of the reported information, information about the operating condition of the UE, information about the measurement mode at the UE, or quantities to enable new representations of a UE’s waypoint in 3 dimensions. [40] The proposed solutions help improve the quality of the flight path information provided by the UE, thereby making the information more useful for the network, e.g., in dimensioning radio resources for the airborne UE communication. [41] The disclosure herein relates to Unmanned Aerial Vehicles (UAVs). A UAV may be any type of aerial or airborne User Equipment (UE), including but not limited to UEs installed on or carried by crewed or uncrewed drones or aircraft such as uncrewed aerial vehicles (UAV), air taxies, air buses, helicopters, commercial airliners, or any other type of UAV. The term UE may be used interchangeably with UAV herein. [42] Figure 2 shows a method in a UAV according to some embodiments herein. The method 2 may be performed by a UAV or wireless device (e.g. the UE 412 or UE 500 as described later with reference to Figures 4 and 5 respectively). [43] In a first step 202 the method 2 comprises: sending a first message to a first network node in a communications network, the first message comprising at least one of the following options: a) a first waypoint and an indication of a first duration of time in which the first waypoint is valid; b) an indication of a switch in a measurement mode of the UAV; c) information related to operating conditions of the UAV; d) a reliability metric; e) an indication of a landing spot to be used by the UAV in case of an emergency landing; and f) an indication of an area or volume in which the UAV intends to remain. [44] It will be appreciated that the first message may comprise any one, or any combination of the options a) to f). [45] In some embodiments, the first message is a flight path report. A flight path report may comprise a flight path. Generally as referred to herein a flight path comprises an indication of an intended route that will be taken by a UAV. A flight path may be expressed in terms of a sequence of waypoints, whereby each waypoint corresponds to (3D) co-ordinates of a point on the flight path. Each waypoint may be associated with a time stamp indicating the time at which the UAV intends to be at the coordinates of the waypoint. Thus, in some examples, a flight path is specified by means of waypoint and timestamp pairs. It is noted that timestamps are not essential, and a flight path may equally be represented merely by a sequence of waypoints. [46] A flight path may be received by the UAV from a UTM, or it may be received from a user of the UAV (e.g. a user-configured flight plan). [47] A flight path report comprises the flight path. A flight path report may comprise one or more Information Elements (IE)s. A flight path report may be represented as one of the IEs described above. [48] In some embodiments, the first message comprises a first waypoint and an indication of a first duration of time e.g. a first time window in which the first waypoint is valid. In other words, a validity timer. The first duration of time may indicate how long, or until when the first waypoint is considered valid. [49] It will be appreciated that the first message may comprise a plurality of waypoints and a plurality of validity timers (e.g. a plurality of time windows in which each of a plurality of corresponding waypoints is valid), one for each way point. In other embodiments, the first duration of time may apply to more than one waypoint in a flight path. [50] It will further be appreciated that in embodiments where the flight path that has first, second, third, and n:th waypoints, each of these may be individually associated with a time window and/or one or more one of options b)-f) described below. For example, a measurement mode, operating conditions, reliability metrics, landing spots in case of emergency and/or volumes may be defined for each of a plurality of way points. [51] In other embodiments, there may be a list of waypoints and one or more of b)-f) may further be specified, that is common to all waypoints in the list. [52] In some embodiments, the first message may further comprise an indication of a starting time point (e.g. time instance or epoch) at which the first waypoint is valid from. Thus, in combination, the first duration of time and the starting timepoint may define a specific time window in which the waypoint is valid (e.g. a specific time window in which the UAV is scheduled to pass through the first way point). [53] Thus, in some embodiments, a flight path report comprises a timer (e.g., a validity timer) indicating for how long or until when the one or more reported waypoints is considered valid, that is a time window is defined. The validity timer can be the same for multiple waypoints or be different for different waypoints. Additionally, the flight path report can also contain an indicator of the time instance (e.g., an epoch) at which the timer is started. This means the timer is started from the epoch and when the timer expires the report waypoint(s) is no longer valid. Typically, the epoch indicates an absolute time after the flight report has been sent to the network. A starting time and timer is one way to define a time window. Another example is to give the starting and ending time as absolute times. It may be configurable, in which form the UE gives the time information associated to the flight path report, and whether UE is informing the network at all about the timing information. [54] The time window for the flight path, or to a certain waypoint, is particularly suitable for the use cases in which the aerial UE is supposed to be in certain location or area during a certain time duration to complete a planned task and move on to a new location after the task in the area is completed. For example, a drone can be sent to examine a specific part of a power grid or a specific base station of a cellular network during a certain time window and move on to the next part of the power grid or a next base station after that. [55] Turning now to other embodiments and option b) in step 202. In some embodiments where the first message comprises an indication of a switch (e.g. change) in a measurement mode of the UAV according to option b), the indication of the switch in the measurement mode may comprise: an indication that the switch has (already) taken place; or a second waypoint at which the switch is to take place. [56] The method 2 may further comprise the UAV determining that the measurement switch has taken place. [57] The method 2 may further comprise the UAV making the measurement switch at the second waypoint. E.g. during the flight when the second waypoint is reached. [58] The measurement mode may be a mode (e.g. configuration) for making channel or cell quality measurements. For example, RSRP, RSRQ or Signal-to-Interference-plus-Noise Ratio (SINR) measurements. The measurement mode may include the information about the number of carriers and/or cells and/or beams to be measured and/or the time period over which the measurements should be performed. Thus, in this way, the UAV can indicate when it intends to switch its measurement mode. [59] In one embodiment, the UE reports to the network, in the flight path report or in a separate report or message, that UE has switched the measurement mode (e.g., switching from relaxed measurement mode to legacy (reference) measurement mode) where the measurements are performed over an extended measurement period in the former mode compared to the latter mode. In a similar example, the former mode comprises UE not measuring on any neighbour cells or measuring on fewer carriers compared to the latter mode where UE measures on more or all detected neighbour cells or configured carriers. In a related embodiment, UE may inform network, that certain parts or waypoints of the flight path will result in the UE changing the measurement mode. [60] By sending the intent to change measurement modes to the network, the network is better able to optimize the use of radio resources for UAV communication. For example, based on the measurement mode indicated by the UE, the network can schedule an appropriate amount of uplink resources for the UE to send the measurements. [61] Turning now to option c) of step 202, and embodiments where the first message comprises information related to operating conditions of the UAV. In some embodiments, the information related to operating conditions comprises at least one of: information about weather conditions experienced by the UAV; information on the battery status or battery life of the UAV; and/or information on malfunction or errors associated with the UAV. [62] In some examples, the method 2 may comprise the UE determining the weather conditions (e.g. by making measurements thereof), the battery status or malfunctions or errors (e.g. in the manner of a diagnostic). [63] Thus, in this way, the UAV can indicate (e.g. within a flight path report) information related to the operating conditions of the UAV. For example, the UAV can include information about the weather condition (e.g., wind direction and velocity) or the battery status of the UAV in the flight path report to help the network judge the reliability and/or validity of other information in the report (e.g., waypoint(s) and/or time stamps). Alternatively, the information related to the operating conditions of the UAV can be sent in a separate report or message from the UAV. It may be configurable, whether the UAV includes the battery lifetime or weather conditions, or other flight related drone operation specific details. [64] As noted above, the UAV can indicate within the first message (which as noted above may be a flight path report or a separate message) information related to UAV equipment failure. The failure could be of any kind, e.g., mechanical, electrical, temperature-related (overheating), etc. This information could be expressed, e.g., using a single bit of information (1 to report malfunctioning and 0 to report normal flight operation or vice versa) or using multiple bits of information–one for each of the abovementioned categories (mechanical, electrical, etc.)–so that the network has more information about the malfunctioning and hence the potential harm that such a malfunctioning aerial node could cause to human beings or to certain infrastructure. For example, a potential aerial drone explosion due to temperature overheat when the drone is flown close to an electric grid installation could be potentially dangerous. When the network receives information related to aerial node malfunctioning in the flight path report, it could react by steering the node, when possible, in the context of aerial node malfunctioning, to a remote location in order to minimize potential damages, [65] Turning now to option d) and embodiments where the first message comprises a reliability metric. [66] As an example, where the first message comprises a flight path and where flight path plan comprises a set of coordinates (e.g. a first waypoint) and possibly a time stamp, a reliability metric may also be reported. The reliability can be associated with either the waypoint or time stamp or both. For example, the reliability indicates the likelihood that the UE will be at a reported waypoint at the corresponding reported timestamp. In another example, the reliability indicates the likelihood that the UE is at the reported waypoint during the corresponding reported time window. Yet in another example, the reliability indicates the likelihood that the UE is within a reported volume at the corresponding reported time stamp or time window. The reliability can be expressed in different ways. One option is that N bits are allocated to the reliability and each codepoint represents a percentage (likelihood). [67] Turning now to option e) and embodiments where the first message comprises an indication of a landing spot to be used in case of an emergency landing. In some embodiments, the first message further comprises at least one of: a time estimate of when the landing spot will be used; a second duration of time in which the landing spot will be used; an estimation of a likelihood that the landing spot will be used; and an indication of a battery life of the UAV. [68] Thus, in some embodiments, the UE reports to the network, (via the first message e.g. in the flight path report or in a separate report or message), a default landing spot to be used in case of an emergency landing (e.g., due to low battery or due to very bad weather conditions). This information may help the network to be prepared to maintain a good radio connection for an emergency landing of the UE. The landing spot report, or part of a flight path report may also include information on for example battery lifetime or a time when UE will need to potentially use landing spot. It may also give likelihood on the need to use the landing spot which the UE may derive from battery lifetime or weather conditions. The likelihood may be expressed for example with a value between 0 and 1 with time quantization. For example, if one bit is used, it may be that value 0 represents less likely than 50% and value 1 more likely than 50%. It may also be defined that the limit 70%. Similarly, the quantization may be even or non-even if more bits are used to represent the likelihood of using the spot. The likelihood may also be combined with a time. For example, it may be X minutes from the UL grant UE has sent the information to the network. This X minutes may be fixed in specification, or it may be configurable. [69] Turning now to option f) and embodiments where the first message comprises an indication of an area or volume in which the UAV intends to remain. [70] In some embodiments, the indication of the area or volume comprises a plurality of coordinates defining said area or volume. In other words a plurality of co-ordinates and an indication that the plurality of coordinates represent the area or volume in which the UAV intends to remain. [71] In other embodiments, the indication of the area or volume comprises a third waypoint and an indication of a manner in which to define the area or volume, respectively, around the third waypoint. [72] Thus, the first message (which as noted above may comprise a flight path) may express an area or volume within which the UAV is planning to stay. In this case, the flight path may consist of a set of coordinates and an indication that these coordinates express a volume or area. Alternatively, the flight path may be represented by a waypoint which includes an associated area or volume and a rule to associate the volume/area with the point. In some cases, the rule is predetermined e.g pre-configured. [73] In some embodiments, the first message (further) defines a plurality of volumes and a plurality of time-windows and/or entry times, wherein the time-windows define time intervals in which the UAV intends to remain in each respective volume and the entry times correspond to time points at which the UAV intends to enter into each respective volume. In other words, the first message may comprise a sequence of [volume, entry time, time interval] tuples that define the sequence volumes through which the UAV will travel and the entry points and duration of stay in each respective volume. [74] In other embodiments, a flight path may comprise a list with a mix of points, areas and volumes. Each list element having associated timestamps, and in the case of areas and volumes in the list, it may comprise associated time windows representing the time the UE plans to stay in the area or volume. This information is helpful in semi-automated mission having a part of the mission being non-autonomous and controlled by a remote pilot. [75] In another example, the first message (which may comprise a flight path, as described above) may comprise a waypoint with an associated area, say for example a circle, and the UE includes an altitude range associated with that waypoint. Then the area and the altitude range represent a volume. This gives the UE more volume representations options, which helps to reduce representation error when transforming from one volume representation to another one. [76] As noted above, in any of the preceding embodiments, the first message may comprise a flight path report. [77] However, it will be appreciated that the first message could be another type of message. For example, in embodiments wherein the first message comprises option e), the first message may be a landing spot report. In other examples, the first message may be any other type of message sent from a UAV to a first network node. [78] In some embodiments, the network may configure which of the options a) to f) the UAV is to send. For example, in some embodiments, the method 2 may further comprise receiving a second message from a second node in the communications network, wherein the second message comprises configuration information indicating which of options a), b), c), d), e) and f) are to be comprised in the first message. It will be appreciated that the second network node may be a different network node to the first network node. Alternatively, the first and second network nodes may be the same network node (e.g the same network node may configure the first message and receive it). [79] Turning now to the first network node, the method of Figure 3 shows an example method in a first network node according to some embodiments herein. In step 302, the method 3 comprises: receiving a first message from an Unmanned Aerial Vehicle, the first message comprising at least one of the following options: a) a first waypoint and an indication of a first duration of time in which the first waypoint is valid; b) an indication of a switch in a measurement mode of the UAV; c) information related to operating conditions of the UAV; d) a reliability metric; e) an indication of a landing spot to be used by the UAV in case of an emergency landing; and an indication of an area or volume in which the UAV intends to remain. [80] The method 3 may be performed by a network node (e.g. the network node 410 or network node 600 as described later with reference to Figures 4 and 6 respectively). [81] The first message and the options a), b), c), d), e) and f) were described in detail above and the detail therein will be understood to apply equally to the method 3. [82] In some embodiments, the method 3 may further comprise, in response to receiving information related to operating conditions of the UAV according to option c), where said information indicates malfunction or errors associated with the UAV: sending subsequent messages to the UAV to steer the UAV to a safe location. [83] The safe location, may for example, be the landing spot to be used by the UAV in case of an emergency landing, according to option e) above. Alternatively, the safe location may be any other location deemed to be safe to for the UAV, or neighboring people or infrastructure. [84] As noted above, the first node may configure the form of the first message. For example, the method 3 may further comprise sending a second message to the UAV, wherein the second message comprises configuration information indicating which of options a), b), c) d) e) and f) are to be comprised in the first message. As an example, the second message may be a RRCreconfiguration message. [85] Related to any of the above embodiments, the form in which the UE provides the flight path report may be network configurable. For example, this configuration may be given to the UE in a RRCreconfiguration message after RRC connection setup, or it may be broadcasted in the system information. [86] Figure 4 shows an example of a communication system 400 in accordance with some embodiments. [87] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3 ^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections. [88] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [89] The UEs 412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 402. [90] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one more core network nodes (e.g., core network node 408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [91] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [92] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [93] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [94] In some examples, the UEs 412 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi- standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). [95] In the example illustrated in Figure 4, the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412c and/or 412d) and network nodes (e.g., network node 410b). In some examples, the hub 414 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [96] The hub 414 may have a constant/persistent or intermittent connection to the network node 410b. The hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412c and/or 412d), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 410b. In other embodiments, the hub 414 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [97] Figure 5 shows a UE 500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [98] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [99] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, a memory 510, a communication interface 512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [100] The processing circuitry 502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 510. The processing circuitry 502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 502 may include multiple central processing units (CPUs). The processing circuitry 502 may be operable to provide, either alone or in conjunction with other UE 500 components, such as the memory 510, UE 500 functionality. For example, the processing circuitry 502 may be configured to cause the UE 502 to perform the methods as described with reference to Figure 2. [101] In the example, the input/output interface 506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [102] In some embodiments, the power source 508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied. [103] The memory 510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems. [104] The memory 510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 510 may allow the UE 500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 510, which may be or comprise a device-readable storage medium. [105] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately. [106] In some embodiments, communication functions of the communication interface 512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [107] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [108] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input. [109] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence on the intended application of the IoT device in addition to other components as described in relation to the UE 500 shown in Figure 5. [110] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [111] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [112] Figure 6 shows a network node 600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [113] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [114] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [115] The network node 600 includes processing circuitry 602, a memory 604, a communication interface 606, and a power source 608, and/or any other component, or any combination thereof. The network node 600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 600. [116] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 600 components, such as the memory 604, network node 600 functionality. For example, the processing circuitry 602 may be configured to cause the network node to perform the methods as described with reference to Figure 3. [117] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units. [118] The memory 604 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read- only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated. [119] The communication interface 606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. Radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front-end circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front- end circuitry 618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 620 and/or amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [120] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown). [121] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 610 may be coupled to the radio front- end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port. [122] The antenna 610, communication interface 606, and/or the processing circuitry 602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [123] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [124] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600. [125] Figure 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein. As used herein, the host 700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 700 may provide one or more services to one or more UEs. [126] The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and a memory 712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host 700. [127] The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 700 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [128] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [129] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [130] Hardware 804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808. [131] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [132] In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802. [133] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units. [134] Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 412a of Figure 4 and/or UE 500 of Figure 5), network node (such as network node 410a of Figure 4 and/or network node 600 of Figure 6), and host (such as host 416 of Figure 4 and/or host 700 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9. [135] Like host 700, embodiments of host 902 include hardware, such as a communication interface, processing circuitry, and memory. The host 902 also includes software, which is stored in or accessible by the host 902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 906 connecting via an over-the-top (OTT) connection 950 extending between the UE 906 and host 902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 950. [136] The network node 904 includes hardware enabling it to communicate with the host 902 and UE 906. The connection 960 may be direct or pass through a core network (like core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [137] The UE 906 includes hardware and software, which is stored in or accessible by UE 906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 906 with the support of the host 902. In the host 902, an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and host 902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 950. [138] The OTT connection 950 may extend via a connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906. The connection 960 and wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [139] As an example of transmitting data via the OTT connection 950, in step 908, the host 902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 906. In other embodiments, the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction. In step 910, the host 902 initiates a transmission carrying the user data towards the UE 906. The host 902 may initiate the transmission responsive to a request transmitted by the UE 906. The request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906. The transmission may pass via the network node 904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 914, the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902. [140] In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902. Accordingly, in step 916, the UE 906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904. In step 920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902. In step 922, the host 902 receives the user data carried in the transmission initiated by the UE 906. [141] One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments may improve the efficiency with which the network can process traffic from a UAV, and thereby provide benefits such as improved safety, planning and network optimisation. [142] In an example scenario, factory status information may be collected and analyzed by the host 902. As another example, the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 902 may store surveillance video uploaded by a UE. As another example, the host 902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 902 may be used for energy pricing, remote control of non- time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [143] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 950 between the host 902 and UE 906, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 902 and/or UE 906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc. [144] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [145] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally. [146] For the avoidance of doubt, the following numbered statements set out embodiments of the disclosure: 1. A method performed by an Unmanned Aerial Vehicle, UAV, the method comprising: sending a first message to a first network node in a communications network, the first message comprising at least one of the following options: a) a first waypoint and an indication of a first duration of time in which the first waypoint is valid; b) an indication of a switch in a measurement mode of the UAV; c) information related to operating conditions of the UAV; d) a reliability metric; e) an indication of a landing spot to be used by the UAV in case of an emergency landing; and f) an indication of an area or volume in which the UAV intends to remain. The method of embodiment 1 wherein the first message comprises the first waypoint and an indication of a first duration of time in which the first waypoint is valid according to option a); and wherein the first message further comprises an indication of a starting time point at which the first waypoint is valid from. The method of embodiment 1 or 2 wherein the first message comprises an indication of a switch in a measurement mode of the UAV according to option b); and wherein the indication of the switch in the measurement mode comprises: an indication that the switch has taken place; or a second waypoint at which the switch is to take place. The method of embodiment 1, 2 or 3 wherein the first message comprises information related to operating conditions of the UAV according to option c); and wherein the information related to operating conditions comprises at least one of: information about weather conditions experienced by the UAV; information on the battery status or battery life of the UAV; and information on malfunction or errors associated with the UAV. The method of embodiment 1, 2, 3, or 4 wherein the first message comprises an indication of a landing spot to be used in case of an emergency landing according to option e); and wherein the first message further comprises at least one of: - a time estimate of when the landing spot will be used; - a second duration of time in which the landing spot will be used; - an estimation of a likelihood that the landing spot will be used; and - an indication of a battery life of the UAV. The method of any of the previous embodiments wherein the first message comprises an indication of an area or volume in which the UAV intends to remain according to option f); and wherein the first message comprises: a plurality of co-ordinates and an indication that the plurality of coordinates represent the area or volume in which the UAV intends to remain; or a third waypoint and an indication of a manner in which to define the area or volume around the third waypoint. The method of any of the previous embodiments wherein the first message further defines a plurality of volumes and a plurality of time-windows and/or entry times, wherein the time-windows define time intervals in which the UAV intends to remain in each respective volume and the entry times correspond to time points at which the UAV intends to enter into each respective volume. The method of any of the previous embodiments wherein the first message is a flight path report. The method of any of the previous embodiments wherein the first message comprises option e) and wherein the first message is a landing spot report. The method of any of the previous embodiments further comprising: receiving a second message from a second node in the communications network, wherein the second message comprises configuration information indicating which of options a), b), c), d), e) and f) are to be comprised in the first message. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. A method performed by a first network node in a communications network, the method comprising: receiving a first message from an Unmanned Aerial Vehicle, the first message comprising at least one of the following options: a) a first waypoint and an indication of a first duration of time in which the first waypoint is valid; b) an indication of a switch in a measurement mode of the UAV; c) information related to operating conditions of the UAV; d) a reliability metric; e) an indication of a landing spot to be used by the UAV in case of an emergency landing; and f) an indication of an area or volume in which the UAV intends to remain. The method of embodiment 12, further comprising: in response to receiving information related to operating conditions of the UAV according to option c); and wherein the information indicates malfunction or errors associated with the UAV; wherein the method further comprises: sending subsequent messages to the UAV to steer the UAV to a safe location.   The method of embodiment 12 or 13 further comprising: sending a second message to the UAV, wherein the second message comprises configuration information indicating which of options a), b), c) d) e) and f) are to be comprised in the first message. The method of embodiment 14 wherein the second message is a RRCreconfiguration message. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. 17. An Unmanned Aerial Vehicle, UAV, comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of embodiments 1 to 11; and power supply circuitry configured to supply power to the processing circuitry. 18. A first network node, the first network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of embodiments 12 to 16; power supply circuitry configured to supply power to the processing circuitry. 19. An Unmanned Aerial Vehicle, UAV, the UAV comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of embodiments 1 to 11; an input interface connected to the processing circuitry and configured to allow input of information into the UAV to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UAV that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UAV. 20. A first network node, the first network node comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of embodiments 12 to 16; an input interface connected to the processing circuitry and configured to allow input of information into the first network node to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the first network node that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the first network node.