Radio network node, first core network node, second core network node and methods performed thereby in wireless communication network

Abstract

A method performed by a radio network node (101) for controlling measurement reporting for an UAV UE (121) in a wireless communication network (100) is provided the radio network node (101) reports to a core network node (111, 112) an event related to measurement reporting for the UAV UE (121).

Description

[0001] RADIO NETWORK NODE, FIRST CORE NETWORK NODE, SECOND CORE NETWORK NODE AND METHODS PERFORMED THEREBY IN WIRELESS COMMUNICATION NETWORK TECHNICAL FIELD

[0002] Embodiments herein relate to a radio network node, a first core network node, a second core network node and methods performed therein regarding wireless communication.

[0003] Furthermore, a computer program and a carrier are also provided herein. Especially, embodiments herein relate to handling and / or controlling measurement reporting for UAV UEs in a wireless communication network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards buthave been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] UA V communications in 3GPP

[0010] The world is witnessing a widespread and increasing use of drones, or more technically the Unmanned Aerial Vehicles (UAV), in many segments of the economy and in our daily life. There are numerous use cases of UAVs in industry, goods transportation and delivery, surveillance, media production, etc.

[0011] Traditionally, the UAVs can only be flown by a controller within the visual line of sight (VLoS). Realizing the great potential of connecting drones beyond visual line of sight (BVLoS) via cellular network, 3GPP have specified multiple features in LTE Rel-15, aiming at 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:

[0012] • Support for subscription-based identification

[0013] • Height reporting when UAV crosses height threshold. The report includes height, location (3D), horizontal and vertical speed.

[0014] • RSRP reporting per event of N cells’ signal power above a threshold. The report includes RSRP / RSRQ / location(3D).

[0015] • UE-specific UL power control.

[0016] • Flight path information provided from UE to eNB. This includes network polling and list of waypoints (3D location), time stamp if available.These features were introduced targeting special needs when serving the UAVs by LTE network, e.g., the need for flying mode detection, interference detection, and interference mitigation. The first important issue was the flying mode detection, which is also related to interference detection as the interference conditions for flying aerial UEs are different from aerial UE in terrestrial mode. For interference detection, which may also serve as input to flying mode detection, an enhancement to existing events triggering of RSRP / RSRQ / RS-SINR reports was introduced in LTE Rel-15. The UE may be configured to trigger an event such as A3, A4, A5, which all consider neighbor cell measurements. In such event triggers, a measurement report is triggered when multiple cells’ measured RSRPs (RSRQs / RS-SINRs) are above a threshold.

[0017] Another input to flying mode detection is event triggered height and location reporting. A new configurable event within RRM with height threshold is introduced for Rel-15 Aerial UEs. When the UE is configured with an event, a report is triggered when UE’s altitude crosses the threshold altitude. In addition to flying mode detection, the exact height information is considered useful as the network may choose to reconfigure for example measurement reporting configurations for the UE when it crosses a height threshold. Figure 1 depicts this situation. In this figure, when the UE is below a height of 100m, the aerial UE is RRC configured with measurement reporting configurations and event triggered height / location reporting corresponding to a height threshold of 200m. As the aerial UE crosses a height threshold of 200m, a report is trigged from the UE to the network. After receiving the report from the aerial UE, the network RRC reconfigures the aerial UE with new measurement reporting configurations. See e.g., Figure 1.

[0018] In Rel-18, 3GPP was working on enhancements to 5G NR standards to support UAV communications. This includes serving the UAVs as aerial-UEs via uplink and downlink (i.e., the Uu interface) and supporting direct communication between UAVs (i.e., via the PC5 or sidelink interface).

[0019] In Rel-19, 3GPP has further enhanced service provided for aerial UEs, such as a UE with aerial subscription or an UAV UE, by 5GS. For example, NEF enhancements to support pre-flight planning and in-flight monitoring of UAV’s flight and support for multiple Unmanned / Uncrewed Aircraft / Aerial Systems (UAS) Service Supplier (USS) serving different geographical areas corresponding to the UAV flight path. The key issues are documented in 3GPP TR 23.700-59 [1], By now the study is completed and the normative work is almost completed (99% completion rate due to the existing dependence on the work by RAN WGs), and the solutions for the aforementioned key issues are now specified in 3GPP TS 23.256 [2],

[0020] Unmanned / Uncrewed Aircraft / Aerial Systems (UAS) Traffic Management (UTM)It is utmost important 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 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. The equivalent of UTM in Europe is called U-Space.

[0021] According to reference [1], the UTM provides many flight-related functions for UAVs and UAV operators, for example:

[0022] • Remote identification: enabling UAV identification.

[0023] • Operation planning: flight planning considering various aspects e.g., UAV performance, whether condition.

[0024] • Operator messaging: message exchange between operators for e.g., position and status information.

[0025] • FAA messaging: providing on-demand, periodic, or event-triggered communications with FAA systems to meet regulatory requirements.

[0026] • Mapping: information about airspace restrictions, obstacles, and sensitive regions. • Conflict advisory: real-time alerting for collision avoidance.

[0027] 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 2.

[0028] Flight Path Reporting requested by CN

[0029] When comes to the newly introduced procedure in 3GPP TS 23.256 v18.3.0, clauses 5.12, 5.13 and 5.16 are of particular interest for this invention:

[0030] • clause 5.12: “Pre-flight Planning and In-flight Monitoring for UAVs”;

[0031] • clause 5.13: “Multiple USS serving different geographical areas”:

[0032] • clause 5.16: “Altitude reporting for aerial UEs”.

[0033] Furthermore, the instructing a UAV UE to perform altitude reporting and configuring the reporting itself is a must - the essential part of the 5GC in order to enable flight path monitoring and detection when, for instance, a UAV UE deviates from the assigned flight path / trajectory.

[0034] #— excerpt from clause 5.16.1 of 3GPP TS 23.256 [2]—

[0035] 5.16.1 GeneralIn order to assist a USS / UTM with aerial UE's flight planning and monitoring, the 5GS may enable configuration of aerial UEs (UAVs) to perform altitude reporting. This may include providing aerial UEs with threshold values for altitude reporting and / or request reporting periodicity (e.g. threshold-based, event-based, periodic). Forthat, the 5GS may determine altitude thresholds and periodicity with which an aerial UE should report its altitude. Altitude thresholds can be derived, for instance, based on the flight path information provided by the serving USS / UTM during a pre-flight planning request or a USS changeover request. Delivery of the altitude thresholds and reporting periodicity can be done via application layer or via node-level signalling. The 5GS should forward the altitude measurements results to the AMF and NEF / UAS NF.

[0036] # —

[0037] In order to monitor when a UAV UE deviates from the assigned trajectory, a new event from the AMF-provided event exposure has been introduced for this purpose, see clause 5.2.2.3.1 of TS 23.502 [4]

[0038] #— excerpt from clause 5.2.2.3.1 of TS 23.502 [4]—

[0039] Table 5.2.2.3.1-1: Example of Event Filters for AMF exposure events

[0040] Event ID Event Filter (List of Parameter Values to Match)

[0041] Location Report < Parameter Type = LocationFilter, Value = TA1>

[0042] UE moving in or out of Area of Interest < Parameter Type = TAI, Value = TA1>

[0043] < Parameter Type = S-NSSAI, Value = S-NSSAI1>

[0044] < Parameter Type = NSI ID, Value = NSI ID1>

[0045] < Parameter Type = PRA ID, Value = PRA ID value>

[0046] < Parameter Type = RAN Node ID, Value = RAN Node ID value> < Parameter Type = Cell ID, Value = Cell ID value>

[0047] < Parameter Type = RAN timing synchronization status change event > (NOTE 1) (NOTE 2)

[0048]

[0049] < Parameter Type = Adjust Aol based on RA, Value = Yes or No> to indicate that AMF may adjust the received Aol depending on UE's current Registration Area. Absence of this parameter in the request is interpreted as " Aol remains unchanged".

[0050] < Parameter Type = Notify the consumer considering UE identity, Value = List of SUPIs or Internal Group ID > The parameter may be included when the request is targeted to Any UE. Absence of this parameter in the request is interpreted as " AMF reports an event regardless to UE's identity triggering the event".

[0051] (NOTE 2)

[0052] < Parameter Type = Notify the consumer considering DNN / S-NSSAI, Value = DNN and / or S-NSSAI> Absence of this parameter in the request is interpreted as " AMF reports the event without checking to which DNN / S-NSSAI the UE has PDU sessions established".

[0053] (NOTE 2)

[0054] Access Type < Parameter Type=AN Type,

[0055] Value=3GPP Access">

[0056] Location < Parameter Type=TAI,

[0057] Value=wildcard> (to report any TAI change) Location < Parameter Type=TAI Value=abnormal> (to report only when the TAI deviates from expected values based on Expected UE Moving Trajectory).

[0058] Assigned Trajectory < Parameter Type = Notify when the UE deviates from the assigned trajectory, Value=TAI, Scheduled Time in a particular TA and / or Height> (to report only when the UE deviates from the assigned values of

[0059]

[0060] TAI, Scheduled Time in a particular TA and / or moves outside the altitude range based on the assigned flight plan).

[0061] The assigned trajectory may consist of multiple segments identified by geographical areas that, for instance, are served by different UAV Service Suppliers. In this case, the information of each segment shall be provided.

[0062] (NOTE 4)

[0063] Reachability Filter Applicable to the event UE reachability.

[0064] Value = UE reachability status change or UE reachable for DL traffic. Absence of this parameter in UE reachability event request is interpreted as " UE reachability status change".

[0065] Total number of Transactions < Parameter Type = TAI, Value = TA1>

[0066] < Parameter Type = S-NSSAI, Value = S-NSSAI1>

[0067] Number of UEs present in a < Parameter Type = UE Type, Value = geographical area Aerial UE>

[0068] < Parameter Type = PDU session status, Value = PDU session established for DNN subject to aerial services>

[0069] < Parameter Type = LOS broadcasting assistance data type, Value = A bitmap indicates broadcast location assistance data types for which the UE is subscribed to receive ciphering keys to decipher broadcast assistance data (see Table 7.1-3 in clause 7.1 of TS 23.273

[0051] and

[0070] clause 6.1.6.2.72 of TS 29.503

[0052] )> (NOTE 3)

[0071] NOTE 1: The Parameter Type = RAN timing synchronization status change event can be present with Parameter Type defining a RAN Node ID.

[0072]

[0073] NOTE 2: The use of event filter parameters is described in clause 5.3.4.4 of

[0074] TS 23.501 [2],

[0075] NOTE 3: The mapping relationship between the LOS broadcasting assistance data element and corresponding positioning SIB type is described in clause 7.2 of

[0076] TS 37.355

[0056] ,

[0077] NOTE 4: Filter information for the events is provided as a set of TAI, Scheduled Time and / or Height values for each of the trajectory segments assigned to the UE / LIAV, see clause 5.13 of TS 23.256

[0080] ,

[0078] NOTE 5: Procedures related to reporting altitude information of aerial UEs are specified in clause 5.16 of TS 23.256

[0080] ,

[0079]

[0080] The following service operations are defined for the Namf_EventExposure service:

[0081] - Namf_EventExposure_Subscribe.

[0082] - Namf_EventExposure_UnSubscribe.

[0083] - Namf_EventExposure_Notify.

[0084] #—

[0085] To perform in-flight monitoring of the UAV UE’s flight progress and to detect in timely manner that the UAV UE deviates from the assigned trajectory, it is instrumental to configure altitude information reporting from the UAV UE accordingly. More specifically, the core network needs to provide a configuration / instruction on how and when the UAV UE needs to send altitude measurement results to a serving NG-RAN node, which would further provide this information to the core network function, AMF in this case, and further to UAS NF / NEF and, if required, to the USS. The respertive procedure are specified in clause 5.16.2 and 5.16.3 of 3GPP TS 23.256 [2],

[0086] #— excerpt from clause 5.16.2 of 3GPP TS 23.256 [2]—

[0087] 5.16.2 Instructing aerial UEs to perform altitude reporting

[0088] Procedure shown in Figure 5.16.2-1 specifies how the 5GS instructs the aerial UEs (UAVs) to perform altitude reporting, considering requests from a USS / UTM for assistance with UAV's flight. This procedure can be used in conjunction with the NEF-assisted pre-flight planning, in-flight monitoring and USS changeover as specified in clauses 5.12.2, 5.12.3 and 5.13, respectively.

[0089] 1. UAS NF / NEF assists the USS / UTM with pre-fligh planning, in-flight monitoring and / or USS changeover based on the received request, which is either aNnef_RetrievelnfoUAVFIight_Get or a Nnef_UAVFIightAssistance_Create, as specified in clauses 5.12 or 5.13.

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

[0091] The determined minimum and maximum altitude values for each of the UAV UE is used by the UAS NF / NEF to derive altitude thresholds for altitude reporting events.

[0092] NOTE 1: Event H1 and H2 for altitude-based reporting specified in clause 5.5.4.21 and clause 5.5.4.22 of TS 38.331

[0023] can be used for altitude thresholds and event-based reporting.

[0093] Additionally, the UAS NF / NEF determines whether to request the aerial UE to report its altitude information periodically, threshold-based (e.g. altitude becomes a higher / lower than the provided threshold, multiple threshold values can be provided) or event-based (e.g. change of a tracking area / NG-RAN node).

[0094] 3. Delivering the UAS NF / NEF-derived altitude thresholds and, optionally, the indication about reporting periodicity (i.e. threshold-based, event-based, or periodic) for UE's altitude reporting to the aerial UE(s).

[0095] Option A: Application layer.

[0096] 3a. The UAS NF / NEF sends the derived altitude threshold values and provides indication about the required periodicity of the reporting (on demand, event-triggered, periodic, or per change of the altitude, or change of a specific geographical area) to the serving USS / UTM either in a Nnef_RetrievelnfoUAVFIight_Get response message or in a Nnef_UAVFIightAssistance_Notify message depending on the procedure that has triggered the UAS NF / NEF to derive the altitude thresholds for the aerial UE.

[0097] 4a. The USS / UTM sends the altitude reporting thresholds and, optionally, indication about reporting periodicity (and any additional information required to perform the reporting, e.g. a list of TA(s) / NG-RAN node identifier(s) for event-based reporting, periodicity value for periodic reporting) to the UAV over the application layer for the UAV's consumption.

[0098] NOTE 2: Application layer reporting itself is outside of 3GPP scope.

[0099] Option B: Node-level signalling.

[0100] Editor's note: This requires RAN to provide further enhancement of the procedure under RAN responsibility.

[0101] 3b. The UAS NF / NEF may send an Namf_EventExposure_Subscribe request to the AMF to get notified about events of UAV's deviation from the assigned trajectory (i.e. EventID = " Assigned Trajectory") as specified in clause 5.2.2.3.1 of TS 23.502 [3], Inside the subscription request, the UAS NF / NEF may include the derived altitude thresholds and indication about reporting periodicity for the UE's altitude reporting.

[0102] Additionally, the UAS NF / NEF may also include an indication to perform UE's altitude reporting for all aerial UEs in a specific TA(s) or NG-RAN node(s).

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

[0104] 5b. The NG-RAN node(s) instructs the relevant UE(s) to perform altitude reporting as requested by the UAS NF / NEF (via AMF).

[0105] NOTE 3: Aspects related to AMF informing NG-RAN regarding instructing UEs to perform altitude reporting are specified in TS 38.413

[0024] ,

[0106] #— excerpt from clause 5.16.3 of 3GPP TS 23.256 [2]—

[0107] 5.16.3 Reporting UE's altitude information

[0108] A procedure for reporting aerial UE's altitude information to the core network is shown in Figure 5.16.3-1. The reporting can be done by the aerial UE based on the received altitude reporting thresholds and indication about reporting periodicity as specified in clause 5.16.2.

[0109] 0. An aerial UE receives request to perform its altitude information reporting as specified in clause 5.16.2. The request may include altitude reporting thresholds and, optionally, indication about reporting periodicity.

[0110] 1. UE's flight altitude meets the previously provided altitude reporting conditions (i.e. altitude thresholds and, optionally, reporting periodicity).

[0111] Option A: Application layer.

[0112] 2a. The UE may report the altitude information over the application layer to the serving USS / UTM in case the USS / UTM has provided altitude reporting threshold and, optionally, indication about reporting periodicity in step 4a in clause 5.16.2.

[0113] NOTE 1: Application layer reporting itself is outside of 3GPP scope.

[0114] 3a. The USS may invoke the Nnef_UAVFIightAssistance_Update to inform the UAS NF / NEF about UE's altitude.

[0115] Option B: Node-level signalling.

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

[0117] NOTE 2: Aspects related to a UE providing altitude information to an NG-RAN node are specified by RAN in TS 38.331

[0023] ,

[0118] The NG-RAN node includes the received UE's altitude information in an N2 message to the AMF.3b. The AMF provides the UAS NF / NEF the altitude information report inside a Namf_EventExposure_Notify request.

[0119] 4. The UAS NF / NEF together with the USS determines the impact on UAV's flight path based on the received altitude information report; this aspect is outside the scope of the 3GPP.

[0120] #—

[0121] Flight Path Cancellation

[0122] It was agreed in RAN2#123bis meeting that the UE can send an empty flight path indicating the cancellation of the existing flight path. The agreement is as follows:

[0123] Agreements on flight path reporting

[0124] 1. Distance and time thresholds for FP update can be (re)configured in RRCReconfiguration, but not in other messages like RRCResume, RRCSetup and RRCReestablisment.

[0125] 2. When UE moves to RRCJDLE the thresholds for triggering FP update, if configured, are released.

[0126] 3. When the UE is in INACTIVE it is released upon RRC Connection Resume procedure (rapporteur will check where it is the best place to capture) 4. For RRCSetupComplete and RRCResumeComplete, UE doesn't check for the threshold(s) configuration for indicating FP availability (i.e. it is always like new FP available indication).

[0127] 5. Capture in the spec that the UE can send an empty flight path to the network to indicate the flight path is no longer valid

[0128] When a flight path of a UAV UE is cancelled from either of sides (from the UE / NG-RAN or core network’s side), which could happen due to several reasons, for instance, UAV UE’s battery status, UAV UE’s presence in a no-transmit zone, a deviation from the assigned trajectory, changes to the assigned flight path due to DAA (Detect and Avoid) to avoid a potential collision, NG-RAN capabilities etc., there is no need for UAV UE’s altitude reporting at all or UAV UE’s altitude reporting needs to be changes. The later also requires the cancelling of the previous altitude reporting configuration at the UAV UE (and at the NG-RAN node) and new instructions from the core network.

[0129] When comes to the flight path cancellation from the CN side, The UAS NF I NEF and / or USS can decide to cancel a UAV UE’s altitude reporting also in cases when the UAV UE deviates from the assigned flight plan / trajectory as the result of in-flight monitoring (clause5.12.3) or USS changeover (clause 5.13.2) and / or to avoid a collision as the result of the DAA procedures (clause 5.14) if / when a new flight path is provided.

[0130] SUMMARY

[0131] An object of embodiments herein is to provide a mechanism to handle and / or control measurement reporting for UAV UEs in a wireless communication network in an efficient manner and improve the performance of the wireless communication network.

[0132] According to an aspect of embodiments herein, the object is achieved by a method performed by a radio network node for controlling measurement reporting for a UAV UE in a wireless communication network.

[0133] The radio network node reports an event related to measurement reporting for the UAV UE to a core network node.

[0134] According to another aspect of embodiments herein, the object is achieved by a method performed by a first core network node for controlling measurement reporting for a UAV UE in a wireless communication network.

[0135] The first core network node receives a report from a radio network node. The report comprises an event related to measurement reporting for the UAV UE.

[0136] The first core network node sends a second indication to the radio network node. The second indication requests the radio network node to stop and / or deactivate measurement reporting for the UAV UE.

[0137] According to another aspect of embodiments herein, the object is achieved by a method performed by a second core network node for controlling measurement reporting for a UAV UE in a wireless communication network.

[0138] The second core network node receives a report from a radio network node and / or a first core network node. The report comprises an event related to measurement reporting for the UAV UE.

[0139] The second core network node sends a second indication to the radio network node and / or the first core network node. The second indication requests the radio network node to stop and / or deactivate measurement reporting for the UAV UE.

[0140] It is furthermore provided herein a computer program, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the radio network node, the first core network node and the second core network node, respectively. It is additionally provided herein a carrier, having stored thereon a computer program comprising instructions which, when executed on at least one processor,cause the at least one processor to carry out the methods herein, as performed by the radio network node, the first core network node and the second core network node, respectively.

[0141] According to another aspect the object is achieved by providing a radio network node, a first core network node and a second core network node configured to perform the methods herein, respectively.

[0142] Thus, according to another aspect of embodiments herein, the object is achieved by a radio network node configured to control measurement reporting for a UAV UE in a wireless communication network.

[0143] The radio network node is configured to report an event related to measurement reporting for the UAV UE to a core network node.

[0144] According to another aspect of embodiments herein, the object is achieved by a first core network node configured to control measurement reporting for a UAV UE in a wireless communication network.

[0145] The first core network node is configured to receive a report from a radio network node. The report is adapted to comprise an event related to measurement reporting for the UAV UE.

[0146] The first core network node is configured to send a second indication to the radio network node. The second indication is adapted to request the radio network node to stop and / or deactivate measurement reporting for the UAV UE.

[0147] According to another aspect of embodiments herein, the object is achieved by a second core network node configured to control measurement reporting for a UAV UE in a wireless communication network.

[0148] The second core network node is configured to receive a report from a radio network node and / or a first core network node. The report is adapted to comprise an event related to measurement reporting for the UAV UE.

[0149] The second core network node is configured to send a second indication to the radio network node and / or the first core network node. The second indication is adapted to request the radio network node to stop and / or deactivate measurement reporting for the UAV UE.

[0150] BRIEF DESCRIPTION OF THE DRAWINGS

[0151] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0152] Figure 1 is a schematic diagram according to prior art.

[0153] Figure 2 is a schematic diagram according to prior art.

[0154] Figure 3 is a signalling diagram according to prior art.

[0155] Figure 4 is a schematic diagram illustrating a non-limiting example of a wireless communication network, according to embodiments herein.Figure 5 is a flowchart depicting embodiments of a method in a radio network node, according to embodiments herein.

[0156] Figure 6 is a flowchart depicting embodiments of a method in a first core network node, according to embodiments herein.

[0157] Figure 7 is a flowchart depicting embodiments of a method in a second core network node, according to embodiments herein.

[0158] Figure 8 is a schematic signalling diagram illustrating a non-limiting example according to embodiments herein.

[0159] Figure 9 is a schematic block diagram illustrating a non-limiting example of a radio network node, according to embodiments herein.

[0160] Figure 10 is a schematic block diagram illustrating a non-limiting example of a first core network node, according to embodiments herein.

[0161] Figure 11 is a schematic block diagram illustrating a non-limiting example of a second core network node, according to embodiments herein.

[0162] Figure 12 shows an example of a communication system QQ100 in accordance with some embodiments.

[0163] Figure 13 shows an example of a communication system QQ200 in accordance with some embodiments.

[0164] Figure 14 shows a wireless device QQ300 in accordance with some embodiments. Figure 15 shows a network node QQ400 in accordance with some embodiments.

[0165] Figure 16 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. Figure 17 is a schematic signalling diagram illustrating a non-limiting example according to embodiments herein.

[0166] Figure 18 is a schematic signalling diagram illustrating a non-limiting example according to embodiments herein.

[0167] Figure 19 is a schematic signalling diagram illustrating a non-limiting example according to embodiments herein.

[0168] Figure 20 is a schematic signalling diagram illustrating a non-limiting example according to embodiments herein.

[0169] DETAILED DESCRIPTION

[0170] Embodiments herein relate to controlling measurement reporting for a UAV UE in a wireless communication network.As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

[0171] NG-RAN node could stop the UAV measurements, e.g. in case of congestion, or in addition it may have to change the periodicity for the reporting to the Core Network. How to handle it should be specified.

[0172] The UAV can send an empty flight path to NG-RAN node to indicate canceling the previously reported flight path or indicate the flight path is no longer valid. UAV does this when UAV has low battery or has obstruction on the current path, or has obstruction on all possible paths.

[0173] NG-RAN node can poll the UE for the flight path information when the “Aerial UE subscription information” is send to NG-RAN node from Core Network and NG-RAN node is aware of the UAV.

[0174] If the Core Network has requested the gNB (via AMF) to report the UE flight Path information in order to perform, for instance, detection when the UAV UE deviates from the assigned flight plan / trajectory as the result of in-flight monitoring (clause 5.12.3) or USS changeover (clause 5.13.2) and / or to avoid a collision as the result of the DAA procedures (clause 5.14), when a UAV UE cancels the flight path or when the core network itself determines to cancel / changes the previously provided “UE’s altitude reporting” and / or “Flight path”, there is no method / mechanisms exist how to handle this scenarios in 5G gNB and 5GC.

[0175] During SA2#166AHE meeting, the altitude reporting cancellation in particular has been brought up, see S2-2500513r04 [2],

[0176] #— excerpt from S2-2500513r04 [2]—

[0177] 5.16.x Altitude reporting cancellation

[0178] Procedure shown in Figure 3 specifies how the 5GS cancels altitude reporting. When the aerial UE receives the request, it stops altitude reporting.

[0179] 1. The aerial UE reports the altitude as specified in clauses 5.16.3.

[0180] 2. The UAS NF / NEF determines to cancel the altitude reporting based on the flight path information.

[0181] Option A: Application layer.

[0182] 3a. The UAS NF / NEF invokes Nnef_UAVFIightAssistance_Notify to inform the USS / UTM to cancel the altitude reporting.

[0183] 4a. The USS / UTM sends the altitude reporting cancellation indication to the UAV over the application layer.NOTE X: Application layer reporting itself is outside of 3GPP scope.

[0184] Option B: Node-level signalling.

[0185] Editor's note: This requires RAN to provide further enhancement of the procedure under RAN responsibility and as such first needs to be confirmed by RAN WGs.

[0186] 3b. The UAS NF / NEF sends an Namf_EventExposure_UnSubscribe request to the AMF to unsubscribe the altitude reporting.

[0187] 4b. The AMF sends the corresponding N2 messages to NG-RAN node.

[0188] 5b. The NG-RAN node instructs the UE to cancel altitude reporting as requested by the UAS NF / NEF (via AMF).

[0189] NOTE Y: Aspects related to AMF informing NG-RAN regarding instructing UEs to perform altitude reporting are specified in TS 38.413

[0024] ,

[0190] #—

[0191] However, the contribution has not been approved, and it does not include interaction between the UAS NF I NEF and the USS. Additionally, it completely misses the RAN part, i.e., what happens if / when the 5GC cancels the flight path, including the previously configured UAV UE’s altitude information reporting.

[0192] According to examples of embodiments herein, methods for both NG-RAN node and Core Network to handle when UE has indicated that the flight path is cancelled and / or NG-RAN node has decided to stop the UAV UE measurements, are provided.

[0193] Examples of embodiments herein provides a new mechanism that allows cancelling UAV UE’s altitude information reporting based on the information / report received from the UAV UE / NG-RAN node and the decision made by the UAS NF I NEF or the USS. No such mechanism exists at the moment; leads to excessive usage of network resources and reduced UAV’s battery use (due to altitude measurements and frequent (unnecessary) signalling of UE’s altitude information to the NG-RAN node and etc.). Embodimnets herein may provide the advantage of battery saving for the UAV UE.

[0194] Embodiments herein relate to wireless communication networks in general. Figure 4 is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may be a 5G system, or a newer system supporting similar functionality, such as for example, a Sixth Generation (6G) system. In some examples, the wireless communication network may support, additionally or alternatively, a Long-Term Evolution (LTE) network and may support other technologies such as a for example, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-DuplexFrequency Division Duplex (HD-FDD), and LTE operating in an unlicensed band. The telecommunications system may also support other technologies, such as Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network / s (WLAN) or WiFi network / s, Worldwide Interoperability for Microwave Access (WiMax), IEEE 802.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide Area Network (LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

[0195] A number of network nodes operate in the wireless communication network 100 such as e.g. a radio network node 101. These nodes provide radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams.

[0196] The first network node 101 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a network controlled repeater or any other network unit capable of communicating with a wireless device within the service area served by the first network node 101 depending e.g. on the first radio access technology and terminology used. The first network node 101 may be referred to as a serving radio network node and / or target or candidate radio network node and communicates with a UE 121 with Downlink (DL) transmissions to the UE 121 and Uplink (UL) transmissions from the UE 121.

[0197] In some examples, the wireless communication network 100 may comprise an access network, such as a radio access network (RAN), and a core network, which may include one or more core network nodes. The access network may include one or more access network nodes, such as the first network node 101, e.g., which may be generally referred to as network nodes, or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a basebandportion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network may include one or more Open-RAN (ORAN) network nodes. An ORAN network node may be understood as a node in the telecommunication network that may support an ORAN specification, e.g., a specification published by the O-RAN Alliance, or any similar organization, and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network, including one or more network nodes and / or core network nodes.

[0198] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller, near-real time or non-real time, hosting software or software plug-ins, such as a near-real time control application, e.g., xApp, or a non-real time control application, e.g., rApp, or any combination thereof, the adjective “open” designating support of an ORAN specification. The radio network node 140 may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment, in which one or more network functions may be virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The radio network node 140 may facilitate direct or indirect connection of user equipment (UE), such as by connecting the device 130 to the core network over one or more wireless connections.

[0199] In the wireless communication network 100, one or more wireless devices operate, such as e.g. a UAV UE 121, which may also be referred to as UE 121. The UE 121 may be also known as a e.g., device, wireless device, mobile terminal, wireless terminal and / or mobile station, mobile telephone, cellular telephone, or laptop with wireless capability, an Internet of Things (IoT) device, or a Customer Premises Equipment (CPE), just to mention some further examples. The device 130 in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via a RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, a Machine-to-Machine (M2M) device, an Internet of Things (IoT) device, e.g., a sensor or a camera, a device equipped with a wireless interface, such as a printer or a file storage device, modem, Laptop Embedded Equipped (LEE), Laptop Mounted Equipment (LME), USB dongles, CPE or any other radio network unit capable of communicating over a radio link in the wireless communication network 100. The UE 121 maybe wireless, i.e., it may be enabled to communicate wirelessly in the wireless communication network 100 and, in some particular examples, may be able support transmission using beamforming. The communication may be performed e.g., between two devices, between a device and a radio network node, and / or between a device and a server. The communication may be performed e.g., via a RAN and possibly one or more core networks, comprised, respectively, within the wireless communication network 100.

[0200] The CN may comprise one or more CN nodes, such as a first core network node 111 and one or more second core network nodes 112. The first core network node may e.g., comprise an UAS Network Function (NF) and / or a Network Exposure Function (NEF). The second network core network node 112 may e.g., comprise a USS and / or an Application Function (AF). A third core network node 113 may e.g., comprise an Access and Mobility Function (AMF).

[0201] Methods herein may be performed by the radio network node 101 and the second network node 102. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 2, may be used for performing or partly performing the methods herein.

[0202] The above-described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0203] The above-described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination.

[0204] A method according to embodiments will now be described from the view of the first network node 101 together with Figure 5. Figure 5 shows example embodiments of a method performed by the radio network node 101 for controlling measurement reporting for the UAV UE 121 in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 5.

[0205] Action 501

[0206] In some embodiments, the radio network node 101 receives a first indication from the UAV UE 121. The indication indicates that a flight plan of the UAV UE 121 has been cancelled or a deviation from a flight plan for the UAV UE 121. The first indication may further indicatee.g., a current state of charge of a power source, such as a battery, of the UAV UE 121. A low state of charge may indicate to the first radio network node 101 to stop measurement reporting and / or adjust a periodicity of the measurement reporting.

[0207] Action 502

[0208] In some embodiments, the radio network node 101 detects an event related to measurement reporting for the UAV UE 121.

[0209] In some embodiments, the event comprises any one out of a failure to receive a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, or the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting. Thus, the event may comprise a location reporting failure.

[0210] The UAV UE 121 may be configured to send measurement reports periodically. Thus, detecting an event comprising a failure to receive a measurement report may comprise detecting that a measurement report expected to be received has not been received. In other words, the event comprising a failure to receive a measurement report may mean a location reporting failure.

[0211] The radio network node 101 may e.g., determine to stop UAV UE 121 measurement reporting or adjust the measurement reporting based on the failure to receive a measurement report or the received first indication.

[0212] Action 503

[0213] The radio network node 101 reports to a core network node, such as a first core network node 111 and / or a second core network node 112, any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121. As mentioned above, the event related to measurement reporting may comprise a location reporting failure, such as detecting that a measurement report expected to be received has not been received. The reporting may e.g., comprise sending or transmitting a message to the core network node, or towards the first core network node 111 and / or the second core network node 112 via one or more core network nodes. The report may thus inform the core network node, such as the first core network node 111 and / or the second core network node 112, and optionally any further core network nodes between the radio network node 101 and the core network node, of the detected event, the plan cancellation and / or the flight plan deviation. This may allow the core network node, or any of the further core network nodes, to take appropriate actions.

[0214] As mentioned above, the event may in some embodiments comprise any one our of a failure to receive a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, or the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.Action 504

[0215] In some embodiments, the radio network node 101 receives a second indication from the core network node. The second indication requests the radio network node 101 to stop and / or deactivate, such as pause, measurement reporting for the UAV UE 121. This may mean that a core network node has determined to stop and / or deactivate the measurement reporting for the UAV UE 121, e.g., based on the report sent by the radio network node 101. Alternatively, a core network node may have made the determination based on information, data, messages, or indication received directly from the UAV UE 121. The deactivation may be related to a timer, e.g., comprised in the second indication, meaning that the measurement reporting should be resumed at the expiry of the timer. Alternatively, the measurement reporting may only be resumed at an explicit order, such as request from a core network node, which may be indicated in the second indication. Alternatively, or additionally, the second indication may indicate an adjusted measurement reporting periodicity.

[0216] In some embodiments, deactivating measurement reporting for the UAV UE 121 comprises storing a configuration related to the measurement reporting for the UAV UE 121. The radio network node 101 may store the configuration for later resumption of the measurement reporting.

[0217] Action 505

[0218] In some embodiments, the radio network node 101 requests the UAV UE 121 to stop and / or deactivate measurements and / or measurement reporting. The request may be sent to the UAV UE 121, e.g., in response to the second indication received from the core network node. Alternatively, or additionally, the request may indicate an adjusted measurement reporting periodicity.

[0219] Action 506

[0220] In some embodiments, the radio network node 101 receives a third indication from the core network node. The third indication requests the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0221] This may comprise the radio network node 101 to retrieve and activate the stored configuration, and send a message to the UAV UE 121 requesting the UAV UE 121 to resume the measurement reporting.

[0222] Alternatively, or additionally, the third indication may indicate an adjusted measurement reporting periodicity. In this case, the radio network node 101 update the configuration for measurement reporting and send a message to the UAV UE 121 requesting the UAV UE 121 comprising the updated configuration.

[0223] A method according to embodiments will now be described from the view of the second network node 102 together with Figure 6. Figure 6 shows example embodiments of a methodperformed by the first core network node 111 for controlling measurement reporting for the UAV UE 121 in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 6.

[0224] Action 601

[0225] The first core network node 111 receives a report from the radio network node 101 or another core network node. The report comprises any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121. As mentioned above, the event related to measurement reporting may comprise a location reporting failure, such as detecting that a measurement report expected to be received has not been received. Thus, the event may comprise a location reporting failure event.

[0226] Thus, the report may be received directly from the radio network node 101, or the report may be sent by the radio network node 101 to the core network node via one or more further core network nodes located between the radio network node 101 and the core network node receiving the report.

[0227] In some embodiments, the event comprises any one out of a failure to receive, by the radio network node 101, a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, or the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting. In other words, the event comprising a failure to receive a measurement report may mean a location reporting failure.

[0228] Action 602

[0229] In some embodiments, the first core network node 111 determines to stop and / or deactivate the measurement reporting for the UAV UE 121. The determination is based on the received report.

[0230] Action 603

[0231] In some embodiments, a second core network node 112 may determine to stop and / or deactivate the measurement reporting for the UAV UE 121. The determination is based on the received report. In this embodiment, the first core network node 111 may forward the report the second core network node 112, and in response receive a second indication from the second core network node 112. The second indication requests the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0232] Action 604

[0233] The first core network node 111 sends a second indication to the radio network node 101. The second indication requesting the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.This may mean that the first core network node 111, or the second core network node 112, has determined to stop and / or deactivate the measurement reporting for the UAV UE 121, e.g., based on the report sent by the radio network node 101. Alternatively, a core network node may have made the determination based on information, data, messages, or indication received directly from the UAV UE 121. The deactivation may be related to a timer, e.g., comprised in the second indication, meaning that the measurement reporting should be resumed at the expiry of the timer. Alternatively, the measurement reporting may only be resumed at an explicit order, such as request from a core network node, which may be indicated in the second indication. Alternatively, or additionally, the second indication may indicate an adjusted measurement reporting periodicity.

[0234] Action 605

[0235] In some embodiments, the first core network node 111 sends a third indication to the radio network node 101. The third indication requests the radio network node 101 to resume measurement reporting for the UAV UE 121. Alternatively, or additionally, the third indication may indicate an adjusted measurement reporting periodicity. In this case, the radio network node 101 may update the configuration for measurement reporting and send a message to the UAV UE 121 requesting the UAV UE 121 comprising the updated configuration.

[0236] The third indication may be sent to the radio network node 101 in response to receiving the third indication from the second network node 112. Alternatively, the first network node 111 may determine to resume the measurements

[0237] A method according to embodiments will now be described from the view of the second network node 102 together with Figure 7. Figure 7 shows example embodiments of a method performed by the second core network node 112 for controlling measurement reporting for the UAV UE 121 in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 7.

[0238] Action 701

[0239] The second core network node 112 receives a report from the radio network node 101 and / or the first core network node 111, e.g., the forwarded by the first core network node 111. The report comprises any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121. As mentioned above, the event related to measurement reporting may comprise a location reporting failure, such as detecting that a measurement report expected to be received has not been received. Thus, the event may comprise a location reporting failure event.Thus, the report may be received directly from the radio network node 101, or the report may be sent by the radio network node to the second core network node 112 via one or more further core network nodes, such as the first core network node 111, located between the radio network node 101 and the second core network node 112 receiving the report.

[0240] In some embodiments, the event comprises any one out of a failure to receive, by the radio network node 101, a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, or the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting. In other words, the event comprising a failure to receive a measurement report may mean a location reporting failure.

[0241] Action 702

[0242] In some embodiments, the second core network node 112 determines to stop and / or deactivate the measurement reporting for the UAV UE 121. The determination is based on the received report. Alternatively, or additionally, the second core network node 112 may determine an adjusted periodicity for the measurement reporting.

[0243] Action 703

[0244] The second core network node 112 sends a second indication to the radio network node 101 and / or the first core network node 111, e.g., for the first core network node 111 to forward to the radio network node 101. The second indication requests the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0245] This may mean that the second core network node 112 has determined to stop and / or deactivate the measurement reporting for the UAV UE 121, e.g., based on the report sent by the radio network node 101. Alternatively, the second core network node 112 may have made the determination based on information, data, messages, or indication received directly from the UAV UE 121. The deactivation may be related to a timer, e.g., comprised in the second indication, meaning that the measurement reporting should be resumed at the expiry of the timer. Alternatively, the measurement reporting may only be resumed at an explicit order, such as request from a core network node, which may be indicated in the second indication.

[0246] Alternatively, or additionally, the second indication may indicate an adjusted measurement reporting periodicity.

[0247] Action 704

[0248] In some embodiments, the second core network node 112 sends a third indication to the radio network node 101 and / or the first core network node 111, e.g., for the first core network node 111 to forward to the radio network node 101. The third indication requests the radio network node 101 to resume measurement reporting for the UAV UE 121. Alternatively, or additionally, the third indication may indicate an adjusted measurement reporting periodicity. In this case, the radio network node 101 may update the configuration for measurement reportingand send a message to the UAV UE 121 requesting the UAV UE 121 comprising the updated configuration.

[0249] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0250] Examples of a method according to embodiments herein, may provide for an NG-RAN to report to 5GC that the UAV UE flight path is cancelled, comprising:

[0251] • When UAV indicates to RAN node that it has cancelled the flight path, NG-RAN node indicate to 5GC that the UE flight path is cancelled by UE.

[0252] This may e.g., mean that, according to examples of embodiments herein, a UAV UE, such as the UAV UE 121 may indicate to the NG-RAN, such as the radio network node 101, that a flight plan associated with the UAV UE 121 has been cancelled. The radio network node 101 may indicate, such as report, to the 5GC, such as a core network node, e.g., the first core network node 111 and / or the second core network node 112, the flight plan of UAV UE 121 has been cancelled.

[0253] Examples of a method according to embodiments herein, may provide for an NG-RAN to report to 5GC that the NG-RAN node has stopped the UAV UE measurements, comprising:

[0254] • When NG-RAN node has determined to stop the UAV UE measurements, NG-RAN node indicate to 5GC that the NG-RAN node has stopped the UAV UE measurement reporting.

[0255] This may e.g., mean that, according to examples of embodiments herein, the radio network node 101 may determine the stop the UAV UE measurements, and then indicate to the 5GC, such as the first core network node 111 and / or the second core network node 112, the radio network node 101 has stopped, or determined to stop, the measurements for the UAV UE 121.

[0256] The radio network node 101 may notify 5GC in a “Notify procedure”. Alternatively, or additionally, the radio network node 101 may notify 5GC that the UAV UE flight information reporting to 5GC is failed. The appropriate indication or failure cause may assist 5GC to take a correction and / or appropriate action.

[0257] Examples of a method according to embodiments herein, may provide for an NG-RAN to receive from the 5GC that the UAV UE flight path reporting is requested to be stopped, comprising:

[0258] • NG-RAN node receives the “stop” indication from the 5GC and stops any further report to 5GC for the specified UE.;• NG-RAN node may further stop the UAV UE measurement reporting / flight path reporting.

[0259] This may e.g., mean that, according to examples of embodiments herein, the radio network node 101 may receive an indication from the 5GC, e.g., the first core network node 111 and / or the second core network node 112. The indication may request, or indicate, the radio network node 101 to stop sending measurement reports associated with the UAV UE 121 to the 5GC and / or request the radio network node 101 to stop the measurements and / or measurement reporting for the UAV UE 121. The radio network node 101 may stop the UAV UE 121 to perform measurements and send measurement reports.

[0260] Examples of a method according to embodiments herein, may provide for an NG-RAN to receive from the 5GC that the UAV UE flight path reporting is requested to be “paused” and / or ’’resumed”, comprising:

[0261] • NG-RAN node receives the “pause” indication from the 5GC and stops the reporting.

[0262] But it stores the early received configuration on the UE flight information reporting request.

[0263] • When the 5GC later sends “resumed” indication, NG-RAN node uses the early stored configuration and start to send the UE flight information reporting.

[0264] This may e.g., mean that, according to examples of embodiments herein, the radio network node 101 receiving an indication from the 5GC, e.g., the first core network node 111 and / or the second core network node 112. The indication may indicate, or request, the radio network node 101 to pause, such as deactivate, UAV UE measurements and / or measurement reporting for the UAV UE 121. The radio network node 101 may store a configuration associated with the measurement and / or measurement reporting for the UAV UA 121. The radio network node 101 may further receive an indication from the 5GC to resume, such as activate, the UAV UE measurements and / or measurement reporting for the UAV UE 121. The radio network node 121 may then retrieve the stored configuration and possibly instruction the UAV UE 121 to resume the measurements and / or measurement reporting.

[0265] Examples of a method according to embodiments herein, may provide for an NG-RAN to report to the 5GC that the periodicity should be adjusted, due to e.g. that the UE is lacking of power, comprising:

[0266] • NG-RAN node to notify to 5GC that the requested reporting periodicity needs to be adjusted, as for example the UE has much long measurement reporting periodicity. NG-RAN node may further provide the appropriate periodicity.

[0267] This may e.g., mean that, according to examples of embodiments herein, the radio network node 101 requesting, the 5GC, e.g., the first core network node 111 and / or the second core network node 112, to adjust the periodicity of the measurement reporting for the UAV UE 121.Examples of a method according to embodiments herein, may provide for a 5GC to receive from the NG-RAN node that the UAV UE flight path is cancelled, comprising:

[0268] • AMF receives the indication from the NG-RAN node; AMF determines and distribute the information to the related network function.

[0269] This may e.g., mean that, according to examples of embodiments herein, the 5GC, e.g., the first core network node 111 and / or the second core network node 112, receives the report, or indication, from the radio network node 101. E.g., the AMF, such as a network node 113, may first receive the indication, or report from the radio network node 101, and the AMF may forward the indication, or report, to the first core network node 111 and / or second core network node 112.

[0270] Examples of a method according to embodiments herein, may provide for a 5GC to receive from the NG-RAN node that the UAV UE measurements is stopped by NG-RAN node, comprising:

[0271] • AMF receives the indication from the NG-RAN node; AMF determines and distribute the information to the related network function.

[0272] This may e.g., mean that, according to examples of embodiments herein, the 5GC, e.g., the first core network node 111 and / or the second core network node 112, may indicate, such as request, receives an indication that the radio network node 101 has stopped, or determined to stop or requesting the 5GC to stop, the measurements or measurement reporting for the UAV UE 121. E.g., the AMF, such as a network node 113, may first receive the indication from the radio network node 101, and the AMF may forward the indication to the first core network node 111 and / or second core network node 112.

[0273] Examples of a method according to embodiments herein, may provide for a 5GC to send to NG-RAN node that the UAV UE flight information reporting to 5GC is stopped, alternatively “paused” / ”resumed”, comprising:

[0274] • AMF determines to indicate to NG-RAN node that the UAV UE flight information is to be “stopped”, or “paused” or “resumed”;

[0275] • NG-RAN node takes the correspond action as described in Ax Method.

[0276] This may e.g., mean that, according to examples of embodiments herein, the 5GC, e.g., the first core network node 111 and / or the second core network node 112, may determine to stop, pause, such as deactivate, and / or resume the measurements and / or measurement reporting for the UAV UE 121. The 5GC, e.g., the first core network node 111 and / or the second core network node 112, may send an indication, or request, to the radio network node 101 informing the radio network node 101 of the decision. E.g., the AMF, such as a network node 113, may receive the indication from the first core network node 111 and / or the second core network node 112, and the AMF may forward the indication to the radio network node 101.Examples of a method according to embodiments herein, may provide for a 5GC to send to NG-RAN node that the UAV UE flight information reporting to 5GC is stopped, alternatively “paused” / ”resumed” in existing Location Reporting procedure with a new Event, or in a new procedure introduced for UAV UE flight information reporting.

[0277] Procedure shown in Figure 8 specifies how the 5GS instructs the aerial UEs to stop their altitude reporting, e.g., as a part of a location reporting procedure, due to a trigger from the UAV UE / NG-RAN and / or request from the USS.

[0278] 0. The UAV UE is requested to perform altitude information reporting as specified in clause 5.16.2, and the UAV UE performs its altitude information reporting as specified in clause 5.16.3.

[0279] 1. In case the UAV UE fails to report its altitude information and / or the NG-RAN receives the altitude information report, the network and / or the USS may decide to instruct the UAV UE to stop the previously configured altitude reporting.

[0280] NOTE 1: Events of a UAV UE failing to provide an altitude information report or an NG-RAN to receive an altitude information report as specified in TS 38.300 can be manifold and related, for instance, to a UAV UE battery status, its presence in an NTZ, a deviation from the assigned trajectory, NG-RAN capabilities etc.

[0281] Editor's note: This requires RAN to provide further enhancement of the procedure under RAN responsibility and as such first needs to be confirmed by RAN WGs.

[0282] NOTE 2: The UAS NF / NEF and / or USS can decide to cancel a UAV UE’s altitude reporting also in cases when the UAV UE deviates from the assigned flight plan / trajectory as the result of in-flight monitoring (clause 5.12.3) or USS changeover (clause 5.13.2) and / or to avoid a collision as the result of the DAA procedures (clause 5.14) if / when a new flight path is provided.

[0283] Option A: Application layer.

[0284] 2a. The UAV UE informs the USS over the application layer about an issue to provide altitude information reporting as requested / configured earlier.

[0285] 3a. The USS decides either to update the altitude reporting configuration at the UAV UE or to cancel the altitude information reporting. The respective request is sent by the USS to the UAV UE over the application layer.

[0286] 4a. The USS may invoke the Nnef_UAVFIightAssistance_Update / Delete service operation to inform the UAS NF / NEF about the altitude reporting of the UAV UE and / or to update / delete the UAV UE’s context.

[0287] Option B: Node-level signalling.

[0288] 2b. The NG-RAN node sends an N2 message to the AMF with information about an issue / event with the configured altitude information reporting.3b. The AMF invokes the Namd_EventExposure_Notify service operation towards UAS NF / NEF to inform about an issue / event with the configured altitude information reporting.

[0289] 4b. The UAS NF I NEF may decide to invoke the Nnef_UAVAssistance_Notify service operation to inform the USS about changes in altitude information reporting status. The UAS NF I NEF may also skipp this step and not inform the USS in case the UAS NF I NEF determines there is no longer a need for altitude information reporting from the UAV UE, for instance, when the UAV UE has reached the flight’s destination; in this case, the procedure proceeds with step 6b.

[0290] 5b. If the UAS NF / NEF informs the USS about changes in the UAV UE’s altitude information reporting, the USS may request the 5GS to cancel UAV UE’s altitude information reporting. The USS invokes the Nnef_UAVFIightAssistance_Update / Delete service operation with the indication to update / stop the altitude information reporting for this UAV UE.

[0291] 6b. The UAS NF / NEF invokes the Namf_EventExposure_Unsubscribe service operation to the AMF to unsubscribe from the altitude information reports; for this purpose, the UAS NF / NEF may include values of the altitude thresholds and / or periodicity, if applicable, indicating to stop the altitude information reporting.

[0292] NOTE 3: In order to indicate to the AMF to stop altitude information reporting, the UAS NF / NEF can indicate the AMF to stop altitude information reporting, for example, by setting the altitude thresolds and / or reporting periodicity to some maximum values; the exact details and attributes is expected to be defined by Stage 3.

[0293] 7b-8b. The AMF sends the corresponding N2 messaage to the NG-RAN node, and the NG-RAN instructs the UAV UE to stop the altitude reporting.

[0294] NOTE 4: Aspects related to AMF informing NG-RAN regarding instructing UEs to stop the altitude reporting are specified in TS 38.413.

[0295] NGAP impact

[0296] Implementation examples: that NG-RAN node to indicate to 5GC that the UAV UE reporting is failed. It can be implemented by introduce explicit indicator or by specific failure cause. Different failure causes can be introduced, e.g. if UE cancelled the flight path, or if NG-RAN node has stopped the UAV UE measurement, particularly when 5GC would have different action based on different failure cause.

[0297] TS 38.413, chapter 9.2.11.2, LOCATION REPORTING FAILURE INDICATION, example 1

[0298] Direction: NG-RAN node

[0299]

[0300] AMFlE / Group P R IE Se Crit Assigned Name resenc ange type and mantics icality Criticality e reference descripti

[0301] on

[0302] Message M 9.3.1.1 YE ignore Type S

[0303] AMF UE M 9.3.3.1 YE reject NGAP ID S RAN UE M 9.3.3.2 YE reject NGAP ID S

[0304] Cause M 9.3.1.2 YE ignore

[0305] S

[0306]

[0307] New Case is introduced:

[0308] Radio Network Layer Meaning

[0309] Cause

[0310] UAV UE flight The UAV UE flight information reporting to 5GC action information Reporting failed stopped in NG-RAN node.

[0311]

[0312] TS 38.413, chapter 9.2.11.2, LOCATION REPORTING FAILURE INDICATION, example 2

[0313] Direction: NG-RAN node

[0314]

[0315] AMF

[0316] lE / Group P R IE Se Crit Assigned Name resenc ange type and mantics icality Criticality e reference descripti

[0317] on

[0318] Message M 9.3.1.1 YE ignore Type S

[0319] AMF UE M 9.3.3.1 YE reject NGAP ID S RAN UE M 9.3.3.2 YE reject NGAP ID S

[0320] Cause M 9.3.1.2 YE ignore

[0321] S

[0322]

[0323] UAV UE 0 ENUM YE ignore flight ERATRED S

[0324] information (stopped, …)

[0325] reporting failed

[0326]

[0327] Implementation examples: that the 5GC indicates to NG-RAN node to stop the UAV UE flight information reporting towards the 5GC by introducing a new Event Type “stop UAV UE flight information reporting”

[0328] TS 38.413, chapter 9.3.1.65 Location Reporting Request Type, example 3

[0329] lE / Group P R IE type Semanti C A Name resenc ange and cs riticalit ssigne e reference description y d Critical ity Event Type M ENUM

[0330] ERATED

[0331] (direct,

[0332] change of

[0333] serving cell,

[0334] UE presence

[0335] in the area of

[0336] interest, stop

[0337] change of

[0338] serving cell,

[0339] stop UE

[0340] presence in

[0341] the area of

[0342] interest,

[0343] cancel

[0344] location

[0345] reporting for

[0346] the UE,...

[0347] change of

[0348] serving cell

[0349] and UE

[0350]

[0351] presence in

[0352] the area of

[0353] interest, flight

[0354] path

[0355] reporting,

[0356] stop UAV UE

[0357] flight

[0358] information

[0359] reporting)

[0360] Report Area M ENUM

[0361] ERATED

[0362] (cell,...)

[0363]

[0364] Figure 9 depicts an example of the arrangement that the radio network node 101 may comprise to perform the method described in Figure 9. The radio network node 101 may be understood to be for controlling measurement reporting for a UE, such as the UAV UE 121. The radio network node 101 is configured to operate in the wireless communication network 100.

[0365] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0366] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first network node 101 and will thus not be repeated here to simplify the description.

[0367] The radio network node 101 may comprise an input and output interface 10 configured to communicate with each other. The input and output interface 10 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0368] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 11 of a processing circuitry in the radio network node 101 depicted in Figure 9, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carriercarrying computer program code for performing the embodiments herein when being loaded into the radio network node 101. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the radio network node 101.

[0369] The radio network node 101 and / or processor 11 is e.g., configure to control measurement reporting for the UAV UE 121 in the wireless communication network 100.

[0370] The radio network node 101 and / or processor 11 is e.g., configure to report to a core network node any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121.

[0371] In some embodiments, the radio network node 101 and / or processor 11 may further be configured to receive a first indication from the UAV UE 121. The indication is adapted to indicate that the flight plan of the UAV UE 121 has been cancelled.

[0372] In some embodiments, the radio network node 101 and / or processor 11 may further be configured to detect an event related to measurement reporting for the UAV UE 121.

[0373] In some embodiments, the event is adapted to comprise a failure to receive a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, and the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0374] In some embodiments, the radio network node 101 and / or processor 11 may further be configured to receive a second indication from a core network node. The second indication is adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0375] In some embodiments, the radio network node 101 and / or processor 11 may further be configured to request the UAV UE 121 to stop and / or deactivate measurements and / or measurement reporting.

[0376] In some embodiments, deactivating measurement reporting for the UAV UE 121 comprises to store a configuration related to the measurement reporting for the UAV UE 121.

[0377] In some embodiments, the radio network node 101 and / or processor 11 may further be configured to receive a third indication from a core network node. The third indication is adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0378] The radio network node 101 may further comprise respective a memory 12 comprising one or more memory units. The memory 12 comprises instructions executable by the processor 11 in the radio network node 101.The memory 12 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, identifiers, configurations, events, reports, and applications to perform the methods herein when being executed in the radio network node 101.

[0379] In some embodiments, a computer program 13 comprises instructions, which when executed by the at least one processor 11, cause the at least one processor 11 of the radio network node 101 to perform the actions above.

[0380] In some embodiments, a respective carrier 14 comprises the respective computer program 13, wherein the carrier 14 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0381] Thus, embodiments herein may disclose the radio network node 101 configured to control measurement reporting for the UAV UE 121 in the wireless communication network 100. The radio network node 101 is configured to operate in the wireless communication network 100. The radio network node 101 comprises the processor 11 and the memory 12, said memory 12 comprising instructions executable by said processor 11 whereby said radio network node 101 is operative to perform any of the methods herein.

[0382] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0383] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0385] Figure 10 depicts an example of the arrangement that the first core network node 111 may comprise to perform the method described in Figure 10. The first core network node 111 may be understood to be for controlling measurement reporting for a UE, such as the UAV UE 121. The first core network node 111 is configured to operate in the wireless communication network 100.

[0386] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0387] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first core network node 111 and will thus not be repeated here to simplify the description.

[0388] The first core network node 111 may comprise an input and output interface 20 configured to communicate with each other. The input and output interface 20 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0389] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 21 of a processing circuitry in the first core network node 111 depicted in Figure 10, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first core network node 111. One such carrier may be in the form of a CD ROM disc. Itis however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first core network node 111.

[0390] The first core network node 111 and / or processor 21 is e.g., configured to control measurement reporting for an UAV UE 121 in the wireless communication network 100.

[0391] The first core network node 111 and / or processor 21 is e.g., configured to receive a report from a radio network node 101. The report is adapted to comprise any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121.

[0392] The first core network node 111 and / or processor 21 is e.g., configured to send a second indication to the radio network node 101. The second indication is adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0393] In some embodiments, the event is adapted to comprise a failure to receive a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, and the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0394] In some embodiments, the first core network node 111 and / or processor 21 may further be configured to send a third indication to the radio network node 101. The third indication is adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0395] In some embodiments, the first core network node 111 and / or processor 21 may further be configured to determine to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0396] In some embodiments, responsive to sending the report to a second core network node 112, the first core network node 111 and / or processor 21 may further be configured to receive the second indication from the second core network node 112.

[0397] The first core network node 111 may further comprise respective a memory 22 comprising one or more memory units. The memory 22 comprises instructions executable by the processor 21 in the first core network node 111.

[0398] The memory 22 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, identifiers, TA values, and applications to perform the methods herein when being executed in the first core network node 111.

[0399] In some embodiments, a computer program 23 comprises instructions, which when executed by the at least one processor 21, cause the at least one processor 21 of the first core network node 111 to perform the actions above.In some embodiments, a respective carrier 24 comprises the respective computer program 23, wherein the carrier 24 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0400] Thus, embodiments herein may disclose the first core network node 111 configured to control measurement reporting for the UAV UE 121 in the wireless communication network 100. The first core network node 111 is configured to operate in the wireless communication network 100. The first core network node 111 comprises the processor 21 and the memory 22, said memory 22 comprising instructions executable by said processor 21 whereby said first core network node 111 is operative to perform any of the methods herein.

[0401] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0402] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0404] Figure 11 depicts an example of the arrangement that the second core network node 112 may comprise to perform the method described in Figure 11. The second core network node 112 may be understood to be for controlling measurement reporting for a UE, such as the UAV UE 121. The second core network node 112 is configured to operate in the wireless communication network 100.

[0405] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0406] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the second core network node 112 and will thus not be repeated here to simplify the description.

[0407] The second core network node 112 may comprise an input and output interface 30 configured to communicate with each other. The input and output interface 30 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0408] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 31 of a processing circuitry in the second core network node 112 depicted in Figure 11, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second core network node 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second core network node 112.

[0409] The second core network node 112 and / or processor 31 is e.g., configured to control measurement reporting for the UAV UE 121 in the wireless communication network 100.The second core network node 112 and / or processor 31 is e.g., configured to receive a report from a radio network node 101 and / or a first core network node 112. The report is adapted to comprise any one out of a flight plan has been cancelled for the UAV UE 121, an event related to measurement reporting for the UAV UE 121, or a deviation from a flight plan for the UAV UE 121.

[0410] The second core network node 112 and / or processor 31 is e.g., configured to send a second indication to the radio network node 101 and / or the first core network node 112. The second indication is adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0411] In some embodiments, the event is adapted to comprise any one or more out of a failure to receive a measurement report from the UAV UE 121, the radio network node 101 having determined to stop the UAV UE 121 measurements, and the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0412] The second core network node 112 and / or processor 31 may further be configured to send a third indication to the radio network node 101. The third indication is adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0413] The second core network node 112 and / or processor 31 may further be configured to determine to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0414] The second core network node 112 may further comprise respective a memory 32 comprising one or more memory units. The memory 32 comprises instructions executable by the processor 31 in the second core network node 112.

[0415] The memory 32 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, identifiers, TA values, and applications to perform the methods herein when being executed in the second core network node 112.

[0416] In some embodiments, a computer program 33 comprises instructions, which when executed by the at least one processor 31, cause the at least one processor 31 of the second core network node 112 to perform the actions above.

[0417] In some embodiments, a respective carrier 34 comprises the respective computer program 33, wherein the carrier 34 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0418] Thus, embodiments herein may disclose the second core network node 112 configured to control measurement reporting for the UAV UE 121 in the wireless communication network 100. The second core network node 112 is configured to operate in the wireless communication network 100. The second core network node 112 comprises the processor 31and the memory 32, said memory 32 comprising instructions executable by said processor 31 whereby said second core network node 112 is operative to perform any of the methods herein.

[0419] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0420] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0422] EmbodimentsBelow, some example Embodiments 1-38 are shortly described. See e.g., Figures 4-20.

[0423] Embodiment 1. A method performed by a radio network node 101 for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the method comprising:

[0424] reporting 503 to a core network node any one out of:

[0425] - a flight plan has been cancelled for the UAV UE 121,

[0426] - an event related to measurement reporting for the UAV UE 121, or

[0427] - a deviation from a flight plan for the UAV UE 121.

[0428] Embodiment 2. The method according to embodiment 1, wherein the method further comprises:

[0429] receiving 501 a first indication from the UAV UE 121, the indication indicating that the flight plan of the UAV UE 121 has been cancelled.

[0430] Embodiment 3. The method according to any of embodiments 1-2, wherein the method further comprises:

[0431] detecting 502 an event related to measurement reporting for the UAV UE 121

[0432] Embodiment 4. The method according to any of embodiments 1-3, wherein the event comprises any one or more out of:

[0433] - a failure to receive a measurement report from the UAV UE 121,

[0434] - the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0435] Embodiment 5. The method according to any of embodiments 1-4, wherein the method further comprises:

[0436] receiving 504 a second indication from a core network node, the second indication requesting the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121, and

[0437] request 505 the UAV UE 121 to stop and / or deactivate measurements and / or measurement reporting.

[0438] Embodiment 6. The method according to embodiment 5, wherein deactivating measurement reporting for the UAV UE 121 comprises storing a configuration related to the measurement reporting for the UAV UE 121.Embodiment 7. The method according to any of embodiments 1-6, the method further comprising:

[0439] receiving 506 a third indication from a core network node, the third indication requesting the radio network node 101 to resume measurement reporting for the UAV UE 121,

[0440] Embodiment 8. A computer program 13 comprising instructions, which when executed by a processor 11, causes the processor 11 to perform actions according to any of the embodiments 1-7.

[0441] Embodiment 9. A carrier 14 comprising the computer program 13 of embodiment 8, wherein the carrier 14 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0442] Embodiment 10. A method performed by a first core network node 111 for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the method comprising:

[0443] receiving 601 a report from a radio network node 101, the report comprising any one or more out of:

[0444] - a flight plan has been cancelled for the UAV UE 121,

[0445] - an event related to measurement reporting for the UAV UE 121, or

[0446] - a deviation from a flight plan for the UAV UE 121,

[0447] sending 604 a second indication to the radio network node 101, the second indication requesting the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0448] Embodiment 11. The method according to embodiment 10, wherein the event comprises any one or more out of:

[0449] - a failure to receive a measurement report from the UAV UE 121,

[0450] - the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0451] Embodiment 12. The method according to any of embodiments 10-11, wherein the method further comprises:sending 605 a third indication to the radio network node 101, the third indication requesting the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0452] Embodiment 13. The method according to any of embodiments 10-12, wherein the method further comprises:

[0453] determining 602 to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0454] Embodiment 14. The method according to any of embodiments 10-13, wherein the method further comprises:

[0455] responsive to sending the report to a second core network node 112, receiving 603 the second indication from the second core network node 112.

[0456] Embodiment 15. A computer program 23 comprising instructions, which when executed by a processor 21, causes the processor 21 to perform actions according to any of the embodiments 10-14.

[0457] Embodiment 16. A carrier 24 comprising the computer program 23 of embodiment 15, wherein the carrier 24 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0458] Embodiment 17. A method performed by a second core network node 112 for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the method comprising:

[0459] receiving 701 a report from a radio network node 101 and / or a first core network node 112, the report comprising any one or more out of:

[0460] - a flight plan has been cancelled for the UAV UE 121,

[0461] - an event related to measurement reporting for the UAV UE 121, or

[0462] - a deviation from a flight plan for the UAV UE 121,

[0463] sending 703 a second indication to the radio network node 101 and / or the first core network node 112, the second indication requesting the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0464] Embodiment 18. The method according to embodiment 17, wherein the event comprises any one or more out of:

[0465] - a failure to receive a measurement report from the UAV UE 121,- the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0466] Embodiment 19. The method according to any of embodiments 17-18, wherein the method further comprises:

[0467] sending 704 a third indication to the radio network node 101, the third indication requesting the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0468] Embodiment 20. The method according to any of embodiments 17-19, wherein the method further comprises:

[0469] determining 702 to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0470] Embodiment 21. A computer program 33 comprising instructions, which when executed by a processor 31, causes the processor 31 to perform actions according to any of the embodiments 17-20.

[0471] Embodiment 22. A carrier 34 comprising the computer program 33 of embodiment 21, wherein the carrier 34 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0472] Embodiment 23. A radio network node 101 e.g., configure to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the method comprising:

[0473] report to a core network node any one or more out of:

[0474] - a flight plan has been cancelled for the UAV UE 121,

[0475] - an event related to measurement reporting for the UAV UE 121, or

[0476] - a deviation from a flight plan for the UAV UE 121.

[0477] Embodiment 24. The radio network node 101 according to embodiment 23, wherein the radio network node 101 is further configured to:

[0478] receive a first indication from the UAV UE 121, the indication adapted to indicate that the flight plan of the UAV UE 121 has been cancelled.Embodiment 25. The radio network node 101 according to any of embodiments 23-24, wherein the radio network node 101 is further configured to:

[0479] detect an event related to measurement reporting for the UAV UE 121.

[0480] Embodiment 26. The radio network node 101 according to any of embodiments 23-25, wherein the event is adapted to comprise any one or more out of:

[0481] - a failure to receive a measurement report from the UAV UE 121,

[0482] - the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0483] Embodiment 27. The radio network node 101 according to any of embodiments 23-26, wherein the radio network node 101 is further configured to:

[0484] receive a second indication from a core network node, the second indication adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121, and / or

[0485] request the UAV UE 121 to stop and / or deactivate measurements and / or measurement reporting.

[0486] Embodiment 28. The radio network node 101 according to embodiment 27, wherein deactivating measurement reporting for the UAV UE 121 comprises to store a configuration related to the measurement reporting for the UAV UE 121.

[0487] Embodiment 29. The radio network node 101 according to any of embodiments 1-6, the radio network node 101 is further configured to:

[0488] receive a third indication from a core network node, the third indication adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0489] Embodiment 30. A first core network node 111 e.g., configured to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the first core network node 111 further being configured to:

[0490] receive a report from a radio network node 101, the report adapted to comprise any one or more out of:

[0491] - a flight plan has been cancelled for the UAV UE 121,

[0492] - an event related to measurement reporting for the UAV UE 121, or

[0493] - a deviation from a flight plan for the UAV UE 121,send a second indication to the radio network node 101, the second indication adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0494] Embodiment 31. The first core network node 111 according to embodiment 31, wherein the event is adapted to comprise any one or more out of:

[0495] - a failure to receive a measurement report from the UAV UE 121,

[0496] - the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0497] Embodiment 32. The first core network node 111 according to any of embodiments SO-31, wherein the first core network node 111 is further configured to:

[0498] send a third indication to the radio network node 101, the third indication adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0499] Embodiment 33. The first core network node 111 according to any of embodiments SO- 32, wherein the first core network node 111 is further configured to:

[0500] determine to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0501] Embodiment 34. The first core network node 111 according to any of embodiments SO- 33, wherein the first core network node 111 is further configured to:

[0502] responsive to sending the report to a second core network node 112, receive the second indication from the second core network node 112.

[0503] Embodiment 35. A second core network node 112 e.g., configured to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE 121 in a wireless communication network 100, the second core network node 112 further being configured to:

[0504] receive a report from a radio network node 101 and / or a first core network node 112, the report adapted to comprise any one or more out of:

[0505] - a flight plan has been cancelled for the UAV UE 121,

[0506] - an event related to measurement reporting for the UAV UE 121, or

[0507] - a deviation from a flight plan for the UAV UE 121,send a second indication to the radio network node 101 and / or the first core network node 112, the second indication adapted to request the radio network node 101 to stop and / or deactivate measurement reporting for the UAV UE 121.

[0508] Embodiment 36. The second core network node 112 according to embodiment 35, wherein the event is adapted to comprise any one or more our of:

[0509] - a failure to receive a measurement report from the UAV UE 121,

[0510] - the radio network node 101 having determined to stop the UAV UE 121 measurements, - the radio network node 101 having determined to request an adjustment of a periodicity of the measurement reporting.

[0511] Embodiment 37. The second core network node 112 according to any of embodiments 35-36, wherein the second core network node 112 is further configured to:

[0512] send a third indication to the radio network node 101, the third indication adapted to request the radio network node 101 to resume measurement reporting for the UAV UE 121.

[0513] Embodiment 38. The second core network node 112 according to any of embodiments 35-37, wherein the second core network node 112 is further configured to:

[0514] determine to stop and / or deactivate the measurement reporting for the UAV UE 121 based on the received report.

[0515] ADDITIONAL EXPLANATION

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

[0517] Figure 12 shows an example of a communication system QQ100 in accordance with some embodiments.

[0518] In the example, the communication system QQ100 includes a telecommunications network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes or base stations of various types, access network nodes QQ110A and QQ110B are depicted (which may be collectively referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network QQ104 may include more than one access network technology. The network nodes QQ110 of access network QQ104 facilitate direct or indirectconnection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs QQ112A, QQ112B, QQ112C, and QQ112D (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0519] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network QQ102, including one or more access network nodes QQ110 and / or core network nodes QQ108.

[0520] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0521] The network nodes QQ110 facilitate direct or indirect connection of one or more UEs QQ112 to the core network QQ106 over one or more wireless connections. 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 QQ100 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 QQ100 mayinclude and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0522] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ108, QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network QQ102) with the UEs QQ112 and / or with other network nodes or equipment in the telecommunications network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network QQ102. More specifically, UEs QQ112 may send messages, data, and / or other signals to network nodes QQ108, QQ110 or other elements of the telecommunications network QQ102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes QQ108, QQ110 may send messages, data, and other signals to UEs QQ1122, other network nodes QQ108, QQ110, and other devices in telecommunications network QQ102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE QQ112 by transmitting the message to an access network node QQ110 that will then transmit the message to the intended UE QQ112. Similarly, a core network node 108 may receive a particular message from a UE QQ112 by receiving the message from an access network node QQ110 that itself received the message from the UE QQ112.

[0523] In the depicted example, the core network QQ106 connects elements of the access network QQ104 (e.g., one or more of the network nodes QQ110) to one or more host computing systems, such as host QQ116. 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 QQ106 includes one or more core network nodes (e.g., core network node QQ108) of various types, one or more of which may be generally referred to as network nodes QQ108. Network nodes QQ108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes provide 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).

[0524] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunications network QQ102. The host QQ116 may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as 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.

[0525] As a whole, the communication system QQ100 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system QQ100 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system QQ100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system QQ100 supporting different standards, protocols, or rule sets.

[0526] As one example, in certain embodiments, access network QQ104 may contain some access network nodes QQ110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes QQ110 support (or the same access network nodes QQ110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network QQ102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard

[0527] generations.Telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network QQ102. For example, the telecommunications network QQ102 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.

[0528] In some examples, one or more of the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard 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).

[0529] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112C and / or QQ112D) and network nodes (e.g., network node QQ110B). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114.

[0530] As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0531] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110B. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112C and / or QQ112D), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 isconnected to the core network QQ106 and / or one or more UEs via a wired connection.

[0532] Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110B. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0533] Figure 13 is another example of a communication system QQ200 according to some embodiments. As used herein, the communication system QQ200 includes multiple access points (APs) QQ210 (with four exemplary APs QQ210A, QQ210B, QQ210C, and QQ210D being depicted) and multiple wireless devices, referred to in the context of communication system QQ200 as stations (STAs) QQ212 (referred to individually as STA QQ212A, STA QQ212B, STA QQ212C, STA QQ212D, and STA QQ212E). STA QQ212A is served by AP QQ210A in a first basic service set (BSS) QQ220A. STA QQ210B and STA QQ210C are served by AP QQ210B in a second BSS, BSS QQ220B. STA QQ212D is served by AP QQ210C in a third BSS, BSS QQ220C. STA QQ212E is served by AP QQ210D in a fourth BSS, BSS QQ220D. Stations QQ212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations QQ212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0534] Each of STAs QQ212 may connect through a radio link to one of APs QQ210. For example, depending on location or channel conditions experienced by a given STA QQ212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0535] Each AP QQ210 may provide data connectivity to STAs QQ212 connected to a particular AP QQ210. As illustrated, APs QQ210 may be connected to a data network QQ230. In this way, APs QQ210 may also provide data connectivity between STAs QQ212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, userterminals, or the like. Accordingly, the radio link established between a given STA QQ212 and its serving AP QQ210 may be used for providing various kinds of services to STA QQ212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA QQ212 and / or on a device linked to STA QQ212. By way of example, Figure 13 illustrates an application service platform QQ232 provided in data network QQ230. The application(s) executed on STA QQ212 and / or on one or more other devices linked to STA QQ212 may use the radio link for data communication with one or more other STA QQ212 and / or the application service platform QQ232, thereby enabling utilization of the corresponding service(s) at STA QQ212.

[0536] Figure 14 shows a wireless device QQ300, which may be configured to operate in communication system QQ100 of Figure 12 or in communication system QQ200 of Figure 13. The wireless device QQ300 may be alternatively referred to as a UE QQ300, like a UE QQ112 within the context of communication system QQ100, or as a station (STA) QQ300 or as a non-access-point station (non-AP STA) QQ300, like a STA QQ212 within the context of the communication system QQ200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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 cameras, 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, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of 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.

[0537] A wireless device QQ300 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, wireless device QQ300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device QQ300 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, wireless device QQ300 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).In particular embodiments, wireless device QQ300 includes processing circuitry QQ302 that is operatively coupled via a bus QQ304 to an input / output interface QQ306, a power source QQ308, a memory QQ310, a communication interface QQ312, and / or any other component, or any combination thereof. Certain embodiments of wireless device QQ300 may include all or a subset of the components shown in Figure 14. The level of integration between the components may vary from one embodiment of wireless device QQ300 to another. In general, in a particular embodiment of wireless device QQ300, processing circuitry QQ302, input / output interface QQ306, power source QQ308, memory QQ310, and communication interface QQ312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device QQ300. Further, certain embodiments of wireless devices QQ300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0538] The processing circuitry QQ302 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 QQ310. The processing circuitry QQ302 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 QQ302 may include multiple central processing units (CPUs).

[0539] In the example, the input / output interface QQ306 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 wireless device QQ300. 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.In some embodiments, the power source QQ308 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 to supply power to circuitry or to charge an associated battery. The power source QQ308 may further include power circuitry for delivering power from the power source QQ308 itself, and / or an external power source, to the various parts of wireless device QQ300 via input circuitry or an interface such as an electrical power cable. Power source QQ308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device QQ300 to which power is supplied.

[0540] The memory QQ310 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 QQ310 includes one or more programs QQ314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ316. The memory QQ310 may store, for use by wireless device QQ300, any of a variety of various operating systems or combinations of operating systems.

[0541] The memory QQ310 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ310 may allow wireless device QQ300 to access instructions, 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 QQ310, which may be or comprise a device-readable storage medium.

[0542] The processing circuitry QQ302 may be configured to communicate with an access network or other network via or using the communication interface QQ312. The communication interface QQ312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ322. The communicationinterface QQ312 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 wireless device or a network node in an access network). Each transceiver may include a transmitter QQ318 and / or a receiver QQ320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).

[0543] Moreover, the transmitter QQ318 and receiver QQ320 may be coupled to one or more antennas (e.g., antenna QQ322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0544] In the illustrated embodiment, communication functions of the communication interface QQ312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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.

[0545] In particular embodiments, wireless device QQ300 may provide an output of data captured via a sensor, through its communication interface QQ312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device QQ300 can be communicated through a wireless connection to a network node via another wireless device QQ300. In particular embodiments, such 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).

[0546] As another example, wireless device QQ300 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, wireless device QQ300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.Wireless device QQ300, 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, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is 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 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. In particular embodiments, wireless device QQ300 represents an IoT device that comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the example embodiment of wireless device QQ300 shown in Figure 14.

[0547] As yet another specific example, in an IoT scenario, wireless device QQ300 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 wireless device and / or a network node. Wireless device QQ300 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, wireless device QQ300 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device QQ300 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.

[0548] In practice, any number of wireless devices QQ300 may be used together with respect to a single use case. For example, a first wireless device QQ300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device QQ300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device QQ300 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 wireless device QQ300 can also include more than one of the functionalities described above. For example, wireless device QQ300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Figure 15 shows a network node QQ400 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 telecommunications network. In accordance with respective embodiments, network node QQ400 may be configured to operate in communication system QQ100 of Figure 12, like network nodes QQ108 or QQ110, or in communication system QQ200 of Figure 13, like an AP QQ210 or a station QQ212. 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0549] Network nodes QQ400 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. Network node QQ400 may be a relay node or a relay donor node controlling a relay. Network nodes QQ400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) 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).

[0550] Other examples of network nodes QQ400 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).

[0551] In particular embodiments, network node QQ400 includes a processing circuitry QQ402, a memory QQ404, a communication interface QQ406, and a power source QQ408. In general, in a particular embodiment of network node QQ400, processing circuitry QQ402, memory QQ404, communication interface QQ406, and power source QQ408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node QQ400.

[0552] The network node QQ400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node QQ400 comprises multiple such entities (e.g., BTS and BSC), one or more of theseparate entities 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 QQ400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories QQ404 or portions of memory QQ404 for different RATs) and some components may be reused (e.g., a same antenna QQ410 may be shared by different RATs). The network node QQ400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 QQ400.

[0553] The processing circuitry QQ402 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 components, such as the memory QQ404, to provide network node QQ400 functionality.

[0554] In some embodiments, the processing circuitry QQ402 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ402 includes one or more of radio frequency (RF) transceiver circuitry QQ412 and baseband processing circuitry QQ414. In some embodiments, the RF transceiver circuitry QQ412 and the baseband processing circuitry QQ414 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 QQ412 and baseband processing circuitry QQ414 may be on the same chip or set of chips, boards, or units.

[0555] The memory QQ404 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 QQ402. The memory QQ404 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 circuitryQQ402 and utilized by the network node QQ400. The memory QQ404 may be used to store any calculations made by the processing circuitry QQ402 and / or any data received via the communication interface QQ406. In some embodiments, the processing circuitry QQ402 and memory QQ404 is integrated.

[0556] The communication interface QQ406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface QQ406 comprises port(s) / terminal(s) QQ416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node QQ300 may be capable of wireless communication and communication interface QQ406 may also include radio front-end circuitry QQ418 that may be coupled to, or in certain embodiments a part of, an antenna QQ410. Particular embodiments of radio front-end circuitry QQ418 include filter(s) QQ420 and amplifier(s) QQ422. The radio front-end circuitry QQ418 may be connected to an antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry QQ418 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 QQ418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters QQ420 and / or amplifiers QQ422. The radio signal(s) may then be transmitted via the antenna QQ410. Similarly, when receiving data, the antenna QQ410 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ418. The digital data may be passed to the processing circuitry QQ402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0557] In certain alternative embodiments, network node QQ400 may be capable of wireless communication but does not include separate radio front-end circuitry QQ418, instead, the processing circuitry QQ402 includes radio front-end circuitry and is connected to the antenna QQ410. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ412 is part of the communication interface QQ406. In still other embodiments, the communication interface QQ406 includes one or more ports or terminals QQ416, the radio front-end circuitry QQ418, and the RF transceiver circuitry QQ412, as part of a radio unit (not shown), and the communication interface QQ406 communicates with the baseband processing circuitry QQ414, which is part of a digital unit (not shown).

[0558] The antenna QQ410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ410 may be coupled to the radio front-end circuitry QQ418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ410 isseparate from the network node QQ400 and connectable to the network node QQ400 through one or more interfaces or ports.

[0559] The antenna QQ410, communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ410, the communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0560] The power source QQ408 provides power to the various components of network node QQ400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ400 with power for performing the functionality described herein. For example, the network node QQ400 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 QQ408. As a further example, the power source QQ408 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.

[0561] Embodiments of the network node QQ400 may include additional components beyond those shown in Figure 15 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 QQ400 may include user interface equipment to allow input of information into the network node QQ400 and to allow output of information from the network node QQ400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ400.

[0562] Figure 16 is a block diagram illustrating a virtualization environment QQ500 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 beimplemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0563] Applications QQ502 (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.

[0564] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and VM QQ508B (which may be collectively referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs QQ508.

[0565] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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.

[0566] In the context of NFV, each of the VMs QQ508 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 QQ508, and that part of hardware QQ504 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 of the VMs QQ508 on top of the hardware QQ504 and corresponds to an application QQ502.Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

[0568] 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 ordiscrete 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.

[0569] ABBREVIATIONS

[0570] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

[0571] 3GPP 3rd Generation Partnership Project

[0572] 5G 5th Generation

[0573] 6G 6th Generation

[0574] ABS Almost Blank Subframe

[0575] ARQ Automatic Repeat Request

[0576] AWGN Additive White Gaussian Noise

[0577] BCCH Broadcast Control Channel

[0578] BCH Broadcast Channel

[0579] CA Carrier Aggregation

[0580] CC Carrier Component

[0581] CCCH SDU Common Control Channel SDU

[0582] CDMA Code Division Multiplex Access

[0583] CE Control Element

[0584] CGI Cell Global Identity

[0585] CHO Conditional Handover

[0586] CIR Channel Impulse Response

[0587] CP Cyclic Prefix

[0588] CPICH Common Pilot Channel

[0589] CQI Channel Quality Information

[0590] C-RNTI Cell RNTI

[0591] CSI Channel State Information

[0592] DCCH Dedicated Control Channel

[0593] DL Downlink

[0594] DM Demodulation

[0595] DMRS Demodulation Reference Signal

[0596] DRX Discontinuous ReceptionDTX Discontinuous Transmission

[0597] DTCH Dedicated Traffic Channel

[0598] DUT Device Under Test

[0599] E-CID Enhanced Cell-ID (positioning method)

[0600] Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast Services

[0601] ECGI Evolved CGI

[0602] eNB E-UTRAN NodeB

[0603] ePDCCH Enhanced Physical Downlink Control Channel

[0604] E-SMLC Evolved Serving Mobile Location Center

[0605] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0606] FDD Frequency Division Duplex

[0607] FFS For Further Study

[0608] gNB Base station in NR

[0609] GNSS Global Navigation Satellite System

[0610] HARQ Hybrid Automatic Repeat Request

[0611] HO Handover

[0612] HOF Handover Failure

[0613] HSPA High Speed Packet Access

[0614] HRPD High Rate Packet Data

[0615] LOS Line of Sight

[0616] LPP LTE Positioning Protocol

[0617] LTE Long-Term Evolution

[0618] LTM L1 / L2 Triggered Mobility

[0619] MAC Medium Access Control

[0620] MAC Message Authentication Code

[0621] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe

[0622] MCG Master Cell Group

[0623] MDT Minimization of Drive Tests

[0624] MIB Master Information Block

[0625] MME Mobility Management Entity

[0626] MN Master Node

[0627] MRO Mobility Robustness Optimization

[0628] MSC Mobile Switching Center

[0629] Msg Message

[0630] NPDCCH Narrowband Physical Downlink Control ChannelNR New Radio

[0631] OCNG OFDMA Channel Noise Generator

[0632] OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System

[0633] OTDOA Observed Time Difference of Arrival O& M Operation and Maintenance

[0634] PBCH Physical Broadcast Channel

[0635] P-CCPCH Primary Common Control Physical Channel PCell Primary Cell

[0636] PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol

[0637] PDP Power Delay Profile

[0638] PDSCH Physical Downlink Shared Channel

[0639] PGW Packet Gateway

[0640] PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network

[0641] PMI Precoding Matrix Indicator

[0642] PRACH Physical Random Access Channel

[0643] PRS Positioning Reference Signal

[0644] PSCell Primary Secondary Cell

[0645] PSS Primary Synchronization Signal

[0646] PUCCH Physical Uplink Control Channel

[0647] PUSCH Physical Uplink Shared Channel

[0648] QAM Quadrature Amplitude Modulation

[0649] QCL Quasi Co-Location / Quasi Co-Located RA Random Access

[0650] RACH Random Access Channel

[0651] RAN Radio Access Network

[0652] RAR Random Access Response

[0653] RAT Radio Access Technology

[0654] RLC Radio Link Control

[0655] RLF Radio Link Failure

[0656] RLM Radio Link Monitoring

[0657] RNC Radio Network Controller

[0658] RNTI Radio Network Temporary IdentifierRRC Radio Resource Control

[0659] RRM Radio Resource Management

[0660] RS Reference Signal

[0661] RSCP Received Signal Code Power

[0662] RSRP Reference Symbol Received Power OR Reference Signal Received Power RSRQ Reference Signal Received Quality OR

[0663] Reference Symbol Received Quality

[0664] RSSI Received Signal Strength Indicator

[0665] RSTD Reference Signal Time Difference

[0666] SCH Synchronization Channel

[0667] Scell Secondary Cell

[0668] SCG Secondary Cell Group

[0669] SDAP Service Data Adaptation Protocol

[0670] SDU Service Data Unit

[0671] SFN System Frame Number

[0672] SGW Serving Gateway

[0673] SHR Successful Handover Report

[0674] SI System Information

[0675] SIB System Information Block

[0676] SN Secondary Node

[0677] SNR Signal to Noise Ratio

[0678] SON Self-Organizing Network

[0679] SPR Successful PSCell Report

[0680] SS Synchronization Signal

[0681] SSB Synchronization Signal Block (also know as SS / PBCH) SSS Secondary Synchronization Signal

[0682] sync I synch Synchronization

[0683] TA Timing Advance

[0684] TCI Transmission Configuration Indicator

[0685] TDD Time Division Duplex

[0686] TDOA Time Difference of Arrival

[0687] TOA Time of Arrival

[0688] TSS Tertiary Synchronization Signal

[0689] TTI Transmission Time Interval

[0690] UE User Equipment

[0691] UL UplinkUMTS Universal Mobile Telecommunications System

[0692] USIM Universal Subscriber Identity Module

[0693] UTDOA Uplink Time Difference of Arrival

[0694] WCDMA Wideband CDMA

[0695] WLAN Wireless Local Area Network

[0696] 3GPP contribution Support UA V UE Flight Information Reporting to CN

[0697] 1 Background

[0698] In the incoming LS [1], SA2 stated that:

[0699] SA2 is specifying a new feature “Pre-flight Planning and In-flight Monitoring for UAVs” in clause 5.12, and USS changeover in clause 5.13 in TS 23.256. In case of in-flight monitoring for UAV, USS / UTM, may request for flight assistance information and that network notifies the USS if UAV deviates from the defined flight path including the UAV altitude and velocity.

[0700] SA2 agrees that the UAV altitude and velocity can be received from NG-RAN, assuming to reuse the existing feature like eventH1 / H2 reporting together with additional trigger from the core network as specified in Rel-19.

[0701] Availability of such information is applicable to any UAV UE(s) that support the relevant procedures.

[0702]

[0703] ACTION: SA2 kindly asks RAN3 to take above information into consideration.

[0704] This paper discusses how to support the SA2 request in RAN3, and provide our feedback to SA2.

[0705] 2 Discussion

[0706] 2.1 Aerial information reporting from NG-RAN to CN

[0707] In TS 23.256, SA2 specified in the “Pre-flight Planning and In-flight Monitoring for UAVs” how to Reporting UE's altitude information:

[0708] Option B: Node-level signalling.

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

[0710] NOTE 2: Aspects related to a UE providing altitude information to an NG-RAN node are specified by RAN in TS 38.331

[0023] ,

[0711]

[0712] The NG-RAN node includes the received UE's altitude information in an N2 message to the AMF.

[0713] 3b. The AMF provides the UAS NF / NEF the altitude information report inside a Namf_EventExposure_Notify request.

[0714] 4. The UAS NF / NEF together with the USS determines the impact on UAV's flight path based on the received altitude information report; this aspect is outside the scope of the 3GPP.

[0715]

[0716] Our understanding of the feature is that NG-RAN node based on the existing aerial UE measurement reporting to build the aerial information to be reported from NG-RAN to CN. In TS 38.300, it is specified that:

[0717] An Aerial UE can be configured with altitude-dependent, event-based measurement reporting (i.e., eventHI and eventH2 as defined in TS 38.331

[0012] ). An Aerial UE sends a measurement report when its altitude becomes higher or lower than configured threshold. The UE includes its altitude and location information in the measurement report if configured to do so by NG-RAN. RSRP / RSRQ / SINR measurement results are always reported when height reporting is configured.

[0718] The Aerial UE can also be configured to trigger measurement reporting only when both an altitude-dependent condition and an RSRP / RSRQ / SINR-based condition are met (i.e., eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1 and eventA5H2 in TS 38.331

[0012] , commonly denoted as eventAxHy). For the content of eventAxHy measurement report, the same rules as described above for eventHI and eventH2 apply.

[0719]

[0720] We can conclude that NG-RAN node receives the Aerial UE Altitude Information in the measurement, Thus it can be a Mandatory IE to report to CN when it is requested by the CN.

[0721] SA2 mented Time Stamps. The UE does not include any Time Stamps in the measurement. However NG-RAN node could mark a time stamp when the measurement report is received over RRC. Therefore we could provide the Time Stamps as well as Mandatory IE to CN.

[0722] Related to the NGAP procedure to use, we propose to reuse the “Location Reporting Procedure”.

[0723] • In Location Reporting Control, CN will provide the thresholds together with the request to the Aerial UE. CN may at any time Stop the report request.• In Location Report, NG-RAN node will include the Aerial UE Altitude Information and Time Stamps when the condition is met to send the report. NG-RAN node stops reporting to CN when the “stop” request is received.

[0724] • In Location Reporting Failure Indication, NG-RAN node will inform CN that the aerial UE report request has failed or stopped. To be explicit, we propose an “UAV UE flight information reporting failed” indicator with Code Point “Stopped,...”, to differ from the existing other location reporting.

[0725] 2.2 Related to UAV Velocity

[0726] UAV Velocity: this information is not a part of UAV measurement reporting. Therefor we propose to reply to SA2 that the UAV Velocity will not be part of the reporting.

[0727] MDT could report velocity through it need UE consent. Other positioning procedure can also contain such information.

[0728] We could reply to SA2 that NG-RAN node could not provide UAV Velocity info as it is not in the Aerial UE measurement. RAN understanding that this information can be obtained from the position procedure. Please SA2 consider that the UAV Velocity is not needed to be include in the N2 reporting.

[0729] Proposal 1: RAN3 to discuss and agree that the UAV Altitude and Time Stamps information can be provided to CN for the Aerial UE.

[0730] Proposal 2: RAN3 to discuss and agree to use the existing Location Reporting procedure to start the Aerial UE flight information reporting, from CN, and to stop the reporting from both CN and NG-RAN (failure).

[0731] Proposal 3: RAN3 to reply to SA2 that the UAV UE altitude can be provided, the Time Stamp is when gNB receives the UAV UE measurement reporting and UAV Velocity is not included.

[0732] The CR for NGAP / XnAP and the Draft Reply LS are submitted in [2], [3], ]4]

[0733] 3 Proposals

[0734] Proposal 1: RAN3 to discuss and agree that the UAV Altitude and Time Stamps information can be provided to CN for the Aerial UE.

[0735] Proposal 2: RAN3 to discuss and agree to use the existing Location Reporting procedure to start the Aerial UE flight information reporting, from CN, and to stop the reporting from both CN and NG-RAN (failure).

[0736] Proposal 3: RAN3 to reply to SA2 that the UAV UE altitude can be provided, the Time Stamp is when gNB receives the UAV UE measurement reporting and UAV Velocity is not included.

[0737] The CR for NGAP / XnAP and the Draft Reply LS are submitted in [2], [3], ]4],

[0738] 4 Reference[1] R3-250022 Reply LS on UAV regulation

[0739] SA2(Samsung)

[0740] [2] R3-25xxxx Support UAV UE Flight Information Reporting to CN Ericsson

[0741] [3] R3-25xxxx Support UAV UE Flight Information Reporting to CN Ericsson

[0742] [4] R3-25xxxx Support UAV UE Flight Information Reporting to CN Ericsson

[0743] Changes to 3GPP TS 23.256 v19.2.0 follows below:

[0744]

[0745] »» Start of Changes ««

[0746] 5.X.1 Cancelling altitude reporting for aerial UEs

[0747] Procedure shown in Figure 17 specifies how the 5GS instructs the aerial UEs to stop their altitude reporting due to a trigger from NG-RAN and / or request from the USS.

[0748] 0. The UAV UE is requested to perform altitude information reporting as specified in clause 5.16.2, and the UAV UE performs its altitude information reporting as specified in clause 5.16.3.

[0749] 1. In case the UAV UE fails to report its altitude information and / or the NG-RAN receives the altitude information report, the network and / or the USS may decide to instruct the UAV UE to stop the previously configured altitude reporting.

[0750] NOTE X1: Events of a UAV UE failing to provide an altitude information report or an NG- RAN to receive an altitude information report as specified in TS 38.300 can be manifold and related, for instance, to a UAV UE battery status, its presence in an NTZ, a deviation from the assigned trajectory, NG-RAN capabilities etc.

[0751] Editor's note: This requires RAN to provide further enhancement of the procedure under RAN responsibility and as such first needs to be confirmed by RAN WGs. NOTE X2: The UAS NF / NEF and / or USS can decide to cancel a UAV UE’s altitude reporting also in cases when the UAV UE deviates from the assigned flight plan / trajectory as the result of in-flight monitoring (clause 5.12.3) or USS changeover (clause 5.13.2) and / or to avoid a collision as the result of the DAA procedures (clause 5.14) if / when a new flight path is provided.

[0752] Option A: Application layer.

[0753] 2a. The UAV UE informs the USS over the application layer about an issue to provide altitude information reporting as requested / configured earlier.3a. The USS decides either to update the altitude reporting configuration at the UAV UE or to cancel the altitude information reporting. The respective request is sent by the USS to the UAV UE over the application layer.

[0754] 4a. The USS may invoke the Nnef_UAVFIightAssistance_Update / Delete service operation to inform the UAS NF / NEF about the altitude reporting of the UAV UE and / or to update / delete the UAV UE’s context.

[0755] Option B: Node-level signalling.

[0756] 2b. The NG-RAN node sends an N2 message to the AMF with information about an issue / event with the configured altitude information reporting.

[0757] 3b. The AMF invokes the Namd_EventExposure_Notify service operation towards UAS NF / NEF to inform about an issue / event with the configured altitude information reporting.

[0758] 4b. The UAS NF I NEF may decide to invoke the Nnef_UAVAssistance_Notify service operation to inform the USS about changes in altitude information reporting status. The UAS NF / NEF may also skipp this step and not inform the USS in case the UAS NF / NEF determines there is no longer a need for altitude information reporting from the UAV UE, for instance, when the UAV UE has reached the flight’s destination; in this case, the procedure proceeds with step 6b.

[0759] 5b. If the UAS NF / NEF informs the USS about changes in the UAV UE’s altitude information reporting, the USS may request the 5GS to cancel UAV UE’s altitude information reporting. The USS invokes the Nnef_UAVFIightAssistance_Update / Delete service operation with the indication to update / stop the altitude information reporting for this UAV UE.

[0760] 6b. The UAS NF / NEF invokes the Namf_EventExposure_Unsubscribe service operation to the AMF to unsubscribe from the altitude information reports; for this purpose, the UAS NF / NEF may include values of the altitude thresholds and / or periodicity, if applicable, indicating to stop the altitude information reporting.

[0761] NOTE X3: In order to indicate to the AMF to stop altitude information reporting, the UAS NF / NEF can indicate the AMF to stop altitude information reporting, for example, by setting the altitude thresolds and / or reporting periodicity to some maximum values; the exact details and attributes is expected to be defined by Stage 3.

[0762] 7b-8b. The AMF sends the corresponding N2 messaage to the NG-RAN node, and the NG-RAN instructs the UAV UE to stop the altitude reporting.

[0763] NOTE X4: Aspects related to AMF informing NG-RAN regarding instructing UEs to stop the altitude reporting are specified in TS 38.413

[0024] ,

[0764]

[0765] »» End of Changes ««

[0766] Changes to 3GPP TS 38.413 v18.4.0 follows below. Changes are marked in bold and underline.

[0767] 8.12 Location Reporting Procedures

[0768] 8.12.1 Location Reporting Control

[0769] 8.12.1.1 GeneralThe purpose of the Location Reporting Control procedure is to allow the AMF to request the NG-RAN node to report the UE's current location, or the UE's last known location with time stamp, or the UE's presence in the area of interest while in CM-CONNECTED state, or the UAV UE’s flight information as specified in TS 23.501 [9] and TS 23.502

[0010] , The procedure uses UE-associated signalling.

[0770] 8.12.1.2 Successful Operation

[0771] The AMF initiates the procedure by sending a LOCATION REPORTING CONTROL message to the NG-RAN node, as shown in Figure 18. On receipt of the LOCATION REPORTING CONTROL message the NG-RAN node shall perform the requested location reporting control action for the UE.

[0772] The Location Reporting Request Type IE indicates to the NG-RAN node whether: to report directly;

[0773] to report upon change of serving cell;

[0774] to report UE presence in the area of interest;

[0775] to stop reporting at change of serving cell;

[0776] to stop reporting UE presence in the area of interest;

[0777] to cancel location reporting for the UE;

[0778] to report upon change of serving cell and to report UE presence in the area of interest.

[0779] to report UE altitude information for the UAV UE;

[0780] _ to cancel altitude information reporting for the UAV UE;

[0781] If the Area Of Interest List IE is included in the Location Reporting Request Type IE in the LOCATION REPORTING CONTROL message, the NG-RAN node shall store this information and use it to track the UE's presence in the area of interest as defined in TS 23.502

[0010] ,

[0782] NOTE: The NG-RAN reports the UE presence for all set of Location Reporting Reference IDs for inter-NG-RAN node handover.

[0783] If the Additional Location Information IE is included in the LOCATION REPORTING CONTROL message and set to " Include PSCell” then, if Dual Connectivity is activated, the NG-RAN node shall include the current PSCell in the report. If a report upon change of serving cell is requested, the NG-RAN node shall provide the report also whenever the UE changes the PSCell, and when Dual Connectivity is activated.

[0784] If reporting upon change of serving cell is requested, the NG-RAN node shall send a report immediately and shall send a report whenever the UE’s location changes.

[0785] If the Event Type IE is set to "stop UE presence in the area of interest", and if the Additional Cancelled Location Reporting Reference ID List IE is included in the LocationReporting Request Type IE within the LOCATION REPORTING CONTROL message, the NG-RAN node shall, if supported, stop reporting UE presence for all received Location Reporting Reference IDs.

[0786] If the UAV UE Flight Inforamtion report control IE is included in the Location Reporting Reguest Type IE in the LOCATION REPORTING CONTROL message, the NG-RAN node shall store this information and use it to report the UAV UE flight information as defined in TS 23.502 f101.

[0787] 8.12.1.3 Abnormal Conditions

[0788] Interactions with Location Reporting Failure Indication procedure:

[0789] If the NG-RAN node receives a LOCATION REPORTING CONTROL message containing several Location Reporting Reference ID IE set to the same value, the NG-RAN node shall send the LOCATION REPORTING FAILURE INDICATION message with an appropriate cause value.

[0790] If the Location Reporting Request Type IE in the received LOCATION REPORTING CONTROL message contains the Event Type IE set to neither " UE presence in the area of interest" nor "change of serving cell and UE presence in the area of interest", but the Area of Interest List IE is present, the NG-RAN node shall ignore the Area of Interest List IE. and proceed with the Location Reporting Procedure.

[0791] 8.12.2 Location Reporting Failure Indication

[0792] 8.12.2.1 General

[0793] The purpose of the Location Reporting Failure Indication procedure is to allow the NG-RAN node to inform the AMF that the location reporting request contained in the Location Reporting Control procedure, the Handover Resource Allocation procedure or the Initial Context Setup procedure has failed. The procedure uses UE-associated signalling.

[0794] 8.12.2.2 Successful Operation

[0795] The NG-RAN node initiates the procedure by sending a LOCATION REPORTING FAILURE INDICATION message to the AMF, as shown in Figure 19. Upon reception of the LOCATION REPORTING FAILURE INDICATION message the AMF shall, based on the failure reason indicated by the Cause IE, take appropriate action.

[0796] If the UAV UE measurement is stopped, the NG-RAN node initiates the procedure by sending a LOCATION REPORTING FAILURE INDICATION message to the AMF. Upon reception of the LOCATION REPORTING FAILURE INDICATION message the AMF shall, based on the UAV UE flight information reporting failed IE, take

[0797]

[0798] action 8.12.2.3 Abnormal Conditions

[0799] Void.

[0800] 8.12.3 Location Report8.12.3.1 General

[0801] The purpose of the Location Report procedure is to provide the UE's current location, the UE's last known location with time stamp, or the UE's presence in the area of interest to the AMF. The procedure uses UE-associated signalling. For UAV UE, the Location Reporting procedure is to provide the UE’s flight formation.

[0802] 8.12.3.2 Successful Operation

[0803] The NG-RAN node initiates the procedure by sending a LOCATION REPORT message to the AMF, as shown in Figure 20. The LOCATION REPORT message may be used as a response to the LOCATION REPORTING CONTROL message.

[0804] 8.12.3.3 Abnormal Conditions

[0805] Void.

[0806] ****************************** Skip to N ext ^>hsmge *******************************

[0807] 9.2.11 Location Reporting Messages

[0808] 9.2.11.1 LOCATION REPORTING CONTROL

[0809] This message is used by the AMF to request the NG-RAN node to report the location of the UE.

[0810] Direction: A

[0811]

[0812] MF NG-RAN node

[0813] lE / Group P R IE Semant C A Name resenc ange type and ics riticality ssigned e reference description Criticali ty Message M 9.3.1. Y i Type 1 ES gnore AMF UE M 9.3.3. Y r NGAP ID 1 ES eject RAN UE M 9.3.3. Y r NGAP ID 2 ES eject Location M 9.3.1. Y i Reporting Request 65 ES gnore Type

[0814]

[0815] 9.2.11.2 LOCATION REPORTING FAILURE INDICATION

[0816] This message is sent by the NG-RAN node and is used to indicate the failure of location reporting.

[0817] Direction: NG-RAN node AMFlE / Group P R IE Semant C A Name resenc ange type and ics riticality ssigned e reference description Criticali ty Message M 9.3.1. Y i Type 1 ES gnore AMF UE M 9.3.3. Y r NGAP ID 1 ES eject RAN UE M 9.3.3. Y r NGAP ID 2 ES eject Cause M 9.3.1. Y i 2 ES gnore UAV UE 0 ENU Y i flight information MERATED(s ES gnore reporting failed topped, ■■■)

[0818]

[0819] 9.2.11.3 LOCATION REPORT

[0820] This message is used to provide the UE's location.

[0821] Direction: NG-RAN node

[0822]

[0823] AMF

[0824] lE / Group P R IE Semant C A Name resenc ange type and ics riticality ssigned e reference description Criticali ty Message M 9.3.1. Y i Type 1 ES gnore AMF UE M 9.3.3. Y r NGAP ID 1 ES eject RAN UE M 9.3.3. Y r NGAP ID 2 ES eject User M 9.3.1. Y i Location Information 16 ES gnore UE Presence 0 9.3.1. Y i in Area of Interest 67 ES gnore List

[0825]

[0826] Location M 9.3.1. Contain Y i Reporting Request 65 s the Location ES gnore Type Reporting

[0827] Request Type

[0828] to which the

[0829] Location

[0830] Report refers.

[0831]

[0832] ****************************** Skip to N ext ^>hsmge *******************************

[0833] 9.3.1.16 User Location Information

[0834] This IE is used to provide location information of the UE and the flight information of the UAV UE.

[0835] lE / Group P R IE Semant C A Name resenc ange type and ics riticality ssigned e reference description Criticali ty CHOICE M

[0836] User Location

[0837] Information

[0838] > E-UTRA

[0839] user location

[0840] information

[0841] »E-UTRA M 9.3.1. - CGI 9

[0842] »TAI M 9.3.3. - 11

[0843] »Age of 0 Time Indicate

[0844] Location Stamp s the UTC time

[0845] 9.3.1. when the

[0846] 75 location

[0847] information

[0848] was generated.

[0849] »PSCell 0 NG- Y i Information RAN CGI ES gnore

[0850]

[0851] 9.3.1.

[0852] 73

[0853] > NR user

[0854] location information

[0855] »NR CGI M 9.3.1. - 7

[0856] »TAI M 9.3.3. This IE

[0857] 11 is ignored if the

[0858] NR NTN TAI

[0859] Information IE

[0860] is present.

[0861] »Age of 0 Time Indicate

[0862] Location Stamp s the UTC time

[0863] 9.3.1. when the

[0864] 75 location

[0865] information

[0866] was generated.

[0867] »PSCell 0 NG- Y i Information RAN CGI ES gnore 9.3.1.

[0868] 73

[0869] »NID 0 9.3.3. Y r 42 ES eject »NR NTN 0 9.3.3. Y i TAI Information 53 ES gnore »Mobile 0 9.3.1. Indicate Y i IAB-MT User 260 s the user ES gnore Location Information location

[0870] information of a

[0871] mobile IAB-MT,

[0872] which is colocated with the

[0873] mobile IAB-DU

[0874] which serves

[0875] the UE.

[0876]

[0877] »UAV UE 0 9.3.1. Y i Flight information XX ES gnore Reporting

[0878] > N3IWF user

[0879] location information

[0880] with port number

[0881] »IP M Trans UE's

[0882] Address port Layer local IP

[0883] Address address used

[0884] 9.3.2. to reach the

[0885] 4 N3IWF

[0886] »Port M OCTE UDP

[0887] Number T STRING source port

[0888] (SIZE( number if NAT

[0889] 2)) is detected.

[0890] »TAI 0 9.3.3. Y i 11 ES gnore > TNGF user Y i location information ES gnore »TNAP ID M TNAP

[0891] OCTET Identifier used

[0892] STRING to identify the

[0893] TNAP. Details

[0894] in TS 29.571

[0895]

[0035] ,

[0896] »IP M Trans UE's

[0897] Address port Layer local IP

[0898] Address address used

[0899] 9.3.2. to reach the

[0900] 4 TNGF.

[0901] »Port 0 OCTE UDP

[0902] Number T STRING source port

[0903] (SIZE( number if NAT

[0904] 2)) is detected.

[0905] »TAI 0 9.3.3. Y i 11 ES gnore

[0906]

[0907] > TWIF user Y i location information ES gnore »TWAP ID M OCTE TWAP

[0908] T STRING Identifier used

[0909] to identify the

[0910] TWAP. Details

[0911] in TS 29.571

[0912]

[0035] ,

[0913] »IP M Trans Non- Address port Layer 5G-Capable

[0914] Address over WLAN

[0915] 9.3.2. device's local

[0916] 4 IP address

[0917] used to reach

[0918] the TWIF.

[0919] »Port 0 OCTE UDP

[0920] Number T STRING source port

[0921] (SIZE( number if NAT

[0922] 2)) is detected.

[0923] »TAI 0 9.3.3. Y i 11 ES gnore > W-AGF Indicate Y i user location s the location ES gnore information information via

[0924] wireline access

[0925] as specified in

[0926] TS 23.316

[0034] ,

[0927] »W-AGF M 9.3.1.

[0928] user location 164

[0929] information

[0930] > N3IWF user Y i location information ES gnore without port number

[0931] »IP M Trans UE's

[0932] Address port Layer local IP

[0933] Address address used

[0934]

[0935] 9.3.2. to reach the

[0936] 4 N3IWF.

[0937] »TAI 0 9.3.3. - 11

[0938]

[0939] ****************************** Skip to N ext ^>hsmge *******************************

[0940] 9.3.1.65 Location Reporting Request Type

[0941] This IE indicates the type of location request to be handled by the NG-RAN node.

[0942] lE / Group P R IE Semant C A Name resenc ange type and ics riticality ssigned e reference description Criticali ty Event Type M ENUM

[0943] ERATED

[0944] (direct,

[0945] change of

[0946] serving cell,

[0947] UE presence

[0948] in the area of

[0949] interest, stop

[0950] change of

[0951] serving cell,

[0952] stop UE

[0953] presence in

[0954] the area of

[0955] interest,

[0956] cancel

[0957] location

[0958] reporting for

[0959] the UE,...

[0960] change of

[0961] serving cell

[0962] and UE

[0963]

[0964] presence in

[0965] the area of

[0966] interest,

[0967] altitude

[0968] information

[0969] reporting for

[0970] the UAVUE,

[0971] cancel

[0972] altitude

[0973] information

[0974] reporting for

[0975] the UAV UE)

[0976] Report Area M ENUM

[0977] ERATED (cell,

[0978] •••)

[0979] Area of 0 - Interest List..1

[0980] > Area of 1

[0981] Interest Item. <maxn

[0982] oofAol>

[0983] »Area of M 9.3.1.6 - Interest 6

[0984] » Location M 9.3.1.7

[0985] Reporting Reference 6

[0986] ID

[0987] Location C Locati

[0988] Reporting Reference on Reporting

[0989] ID to be Cancelled ifEvent Reference ID

[0990] TypeisS 9.3.1.7

[0991] topUEP 6

[0992] resinAo

[0993] 1

[0994] Additional 0 ENUM Y i Location Information ERATED ES gnore (Include

[0995] PSCell,...)

[0996]

[0997] Additional 0 Y r Cancelled Location..1 ES eject Reporting

[0998] Reference ID List

[0999] > Additional 1

[1000] Cancelled Location. <maxn

[1001] Reporting oofAolM

[1002] Reference ID Item inusOne

[1003] >

[1004] » Location M Locati

[1005] Reporting Reference on Reporting

[1006] ID to be Cancelled Reference ID

[1007] 9.3.1.7

[1008] 6

[1009] UAV UE 0 - flight information A

[1010] reporting control

[1011] > Altitude M OCTE Y r thresholds value T STRING ES eject (SIZE(

[1012] 2)1

[1013] »UAV UE M Locati Y r Reporting on Reporting ES eject Reference ID Reference ID

[1014] 9.3.1.7

[1015] 6

[1016] >report 0 INTEG Periodi Y r perodicity ER city expressed ES eject (0..640000, in units of 1

[1017] us.

[1018]

[1019] Range bound Explanation

[1020] maxnoofAol Maximum no. of areas of interest. Value is 64. maxnoofAolMinusOne Maximum no. of areas of interest minus one. Value is 63.

[1021]

[1022] Condition Explanation

[1023]

[1024] if EventT ypeisStopU EPr This IE shall be present if the Event Type IE is set to the esinAol value "stop UE presence in the area of interest".

[1025]

[1026] ****************************** Skip to N ext *******************************

[1027] 9.3.1,xx UAV UE Flight information Reporting

[1028] 5 This IE the UAV UE altitude reporting.

[1029] lE / Group Name P Ran IE type Semantics resenc ge and reference description

[1030] e

[1031] Altitude M OCTET UAV UE altitude STRING

[1032] (SIZE(2))

[1033] Time Stamp M OCTET It is the Time STRING Stamp when the gNB (SIZE(4)) receives the UAV UE measurement.

[1034] Encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905

[0025] ,

[1035]

[1036] -j Q ****************************** Skip to Next Change *******************************

[1037]

[1038] 9.3.4 PDU Definitions

[1039] - ASN1 START

[1040] **************************************************************

[1041] 15 - -- PDU definitions for XnAP.

[1042] **************************************************************XnAP-PDU-Contents {

[1043] itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

[1044] ngran-access (22) modules (3) xnap (2) versionl (1) xnap-PDU-Contents (1) }

[1045] DEFINITIONS AUTOMATIC TAGS::=

[1046] BEGIN

[1047] **************************************************************

[1048] -- IE parameter types from other modules.

[1049] **************************************************************

[1050] IMPORTS

[1051] ActivationlDforCellActivation,

[1052] AMF-Region-Information,

[1053] AMF-UE-NGAP-ID,

[1054] AS-Securitylnformation,

[1055] AssistanceDataForRANPaging, AerialUESubscriptionlnformation,

[1056] A2XPC5QoSParameters,

[1057] BitRate,

[1058] Cause,

[1059] CellAndCapacityAssistancelnfo-EUTRA, CellAndCapacityAssistancelnfo-NR,

[1060] CellAssistancelnfo-EUTRA,

[1061] CellAssistancelnfo-NR,

[1062] CHOinformation-Req,

[1063] CHOinformation-Ack,

[1064] CHOinformation-AddReq,

[1065] CHOinformation-AddReqAck,

[1066] CHOinformation-ModReq,

[1067] CHO-MRDC-EarlyDataForwarding,

[1068] CHO-MRDC-lndicator,

[1069] CPT ransportLayerlnformation,TNLA-To-Add-List,

[1070] TNLA-To-Update-List,

[1071] TNLA-To-Remove-List,

[1072] ****************************** Skip to N ext *******************************

[1073]

[1074] id-LocationlnformationSN,

[1075] id-LocationlnformationSNReporting,

[1076] id-LocationReportinglnformation,

[1077] id-LTEA2XServicesAuthorized,

[1078] id-LTEA2XUEPC5AggregateMaximumBitRate,

[1079] id-LTEUESidelinkAggregateMaximumBitRate,

[1080] id-LTEV2XServicesAuthorized,

[1081] id-MAC-l,

[1082] ****************************** Skip to Next Change *******************************

[1083]

[1084] 9.3.5 Information Element definitions

[1085] - ASN1 START

[1086] **************************************************************

[1087] -- Information Element Definitions

[1088] **************************************************************

[1089] XnAP-IEs {

[1090] itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

[1091] ngran-access (22) modules (3) xnap (2) versionl (1) xnap-IEs (2) }

[1092] DEFINITIONS AUTOMATIC TAGS::=

[1093] BEGIN

[1094] IMPORTSid-CNTypeRestrictionsForEquivalent,

[1095] id-CNTypeRestrictionsForServing,

[1096] id-Additional-UL-NG-U-TNLatUPF-List,

[1097] 9.3.7 Constant definitions

[1098] - ASN1 START

[1099] **************************************************************

[1100] -- Constant definitions

[1101] **************************************************************

[1102] XnAP-Constants {

[1103] itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

[1104] ngran-Access (22) modules (3) xnap (2) versionl (1) xnap-Constants (4) }

[1105] DEFINITIONS AUTOMATIC TAGS::=

[1106] BEGIN

[1107] IMPORTS

[1108] ProcedureCode,

[1109] Protocoll E-ID

[1110] FROM XnAP-CommonDataTypes;

[1111] ****************************** Skip to Next Change *******************************

[1112]

[1113] id-N6Jitterlnformation

[1114] ProtocollE-ID::= 449

[1115] id-ECNMarkingorCongestionlnformationReportingRequest

[1116] Protocoll E-ID::= 450

[1117] id-PDUSetbasedHandlinglndicator

[1118] ProtocollE-ID::= 451

[1119] id-TAISliceUnavailableCellList

[1120] ProtocollE-ID::= 452END

[1121] -- ASN1STOP

[1122] References

[1123] 1. 3GPP TR 23.700-59 v.19.0.0

[1124] 2. 3GPP TS 23.256 V19.1.0

[1125] 3. SA2#166AHE tdoc S2-2500513r04 01 / INBOX / Revisions / S2-2500513r04.zip ) 4. 3GPP TS 23.502 V19.2.0

Claims

CLAIMS1. A method performed by a radio network node (101) for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the method comprising:reporting (503) to a core network node (111, 112) an event related to measurement reporting for the UAV UE (121).

2. The method according to claim 1, wherein the method further comprises:detecting (502) an event related to measurement reporting for the UAV UE (121)3. The method according to any of claims 1-2, wherein the event comprises:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

4. The method according to any of claims 1-3, wherein the method further comprises: receiving (504) a second indication from a core network node (111, 112), the second indication requesting the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121), andrequest (505) the UAV UE (121) to stop and / or deactivate measurements and / or measurement reporting.

5. The method according to claim 4, wherein deactivating measurement reporting for the UAV UE (121) comprises storing a configuration related to the measurement reporting for the UAV UE (121).

6. The method according to any of claims 1-5, the method further comprising:receiving (506) a third indication from a core network node (111, 112), the third indication requesting the radio network node (101) to resume measurement reporting for the UAV UE (121),7. A computer program (13) comprising instructions, which when executed by a processor (11), causes the processor (11) to perform actions according to any of the claims 1-6.

8. A carrier (14) comprising the computer program (13) of claim 7, wherein the carrier (14) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

9. A method performed by a first core network node (111) for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the method comprising:receiving (601) a report from a radio network node (101), the report comprising an event related to measurement reporting for the UAV UE (121),sending (604) a second indication to the radio network node (101), the second indication requesting the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121).

10. The method according to claim 9, wherein the event comprises:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

11. The method according to any of claims 9-10, wherein the method further comprises: sending (605) a third indication to the radio network node (101), the third indication requesting the radio network node 101 to resume measurement reporting for the UAV UE (121).

12. The method according to any of claims 9-11, wherein the method further comprises: determining (602) to stop and / or deactivate the measurement reporting for the UAV UE (121) based on the received report.

13. The method according to any of claims 9-12, wherein the method further comprises: responsive to sending the report to a second core network node (112), receiving (603) the second indication from the second core network node (112).

14. A computer program (23) comprising instructions, which when executed by a processor (21), causes the processor (21) to perform actions according to any of the claims 9-13.

15. A carrier (24) comprising the computer program (23) of claim 14, wherein the carrier (24) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

16. A method performed by a second core network node (112) for controlling measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the method comprising:receiving (701) a report from a radio network node (101) and / or a first core network node (111), the report comprising an event related to measurement reporting for the UAV UE (121),sending (703) a second indication to the radio network node (101) and / or the first core network node (111), the second indication requesting the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121).

17. The method according to claim 16, wherein the event comprises:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

18. The method according to any of claims 16-17, wherein the method further comprises:sending (704) a third indication to the radio network node (101), the third indication requesting the radio network node (101) to resume measurement reporting for the UAV UE (121).

19. The method according to any of claims 16-18, wherein the method further comprises:determining (702) to stop and / or deactivate the measurement reporting for the UAV UE (121) based on the received report.

20. A computer program (33) comprising instructions, which when executed by a processor (31), causes the processor (31) to perform actions according to any of the claims 16-19.

21. A carrier (34) comprising the computer program (33) of claim 20, wherein the carrier (34) is one of an electronic signal, an optical signal, an electromagnetic signal, a magneticsignal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

22. A radio network node (101) e.g., configure to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the method comprising:report to a core network node (111, 112) an event related to measurement reporting for the UAV UE (121).

23. The radio network node (101) according to 22, wherein the radio network node (101) is further configured to:detect an event related to measurement reporting for the UAV UE (121).

24. The radio network node (101) according to any of claims 22-23, wherein the event is adapted to comprise:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

25. The radio network node (101) according to any of claims 22-24, wherein the radio network node (101) is further configured to:receive a second indication from a core network node (111, 112), the second indication adapted to request the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121), and / orrequest the UAV UE (121) to stop and / or deactivate measurements and / or measurement reporting.

26. The radio network node (101) according to claim 24, wherein deactivating measurement reporting for the UAV UE (121) comprises to store a configuration related to the measurement reporting for the UAV UE (121).

27. The radio network node (101) according to any of claims 22-26, the radio network node (101) is further configured to:receive a third indication from a core network node (111, 112), the third indication adapted to request the radio network node (101) to resume measurement reporting for the UAV UE (121).

28. A first core network node (111) e.g., configured to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the first core network node (111) further being configured to:receive a report from a radio network node (101), the report adapted to comprise an event related to measurement reporting for the UAV UE (121),send a second indication to the radio network node (101), the second indication adapted to request the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121).

29. The first core network node (111) according to claim 28, wherein the event is adapted to comprise:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

30. The first core network node (111) according to any of claims 28-29, wherein the first core network node (111) is further configured to:send a third indication to the radio network node (101), the third indication adapted to request the radio network node 101 to resume measurement reporting for the UAV UE (121).

31. The first core network node (111) according to any of claims 28-30, wherein the first core network node (111) is further configured to:determine to stop and / or deactivate the measurement reporting for the UAV UE (121) based on the received report.

32. The first core network node (111) according to any of claims 28-31, wherein the first core network node (111) is further configured to:responsive to sending the report to a second core network node (112), receive the second indication from the second core network node (112).

33. A second core network node (112) e.g., configured to control measurement reporting for an Unmanned Aerial Vehicle, UAV, User Equipment, UE (121) in a wireless communication network (100), the second core network node (112) further being configured to:receive a report from a radio network node (101) and / or a first core network node (111), the report adapted to comprise an event related to measurement reporting for the UAV UE (121),send a second indication to the radio network node (101) and / or the first core network node (111), the second indication adapted to request the radio network node (101) to stop and / or deactivate measurement reporting for the UAV UE (121).

34. The second core network node (112) according to claim 33, wherein the event is adapted to comprise:- a failure to receive a measurement report from the UAV UE (121),- the radio network node (101) having determined to stop the UAV UE (121) measurements,- the radio network node (101) having determined to request an adjustment of a periodicity of the measurement reporting.

35. The second core network node (112) according to any of claims 33-34, wherein the second core network node (112) is further configured to:send a third indication to the radio network node (101), the third indication adapted to request the radio network node (101) to resume measurement reporting for the UAV UE (121).

36. The second core network node (112) according to any of claims 33-35, wherein the second core network node (112) is further configured to:determine to stop and / or deactivate the measurement reporting for the UAV UE (121) based on the received report.

Images