Measurement and reporting at a radio terminal apparatus

Dynamic prioritization policies for UE-side data logging and reporting at radio terminal apparatuses address the inefficiencies in large-scale data transfer for AIML models, enhancing prediction performance and resource use.

WO2026233979A1PCT designated stage Publication Date: 2026-11-12NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/062902
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-05
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing measurement and reporting approaches at radio terminal apparatuses are not optimal for large-scale data transfer required by network-based artificial intelligence/machine learning (AIML) models, leading to insufficient or redundant information, inefficient resource use, and suboptimal memory management.

Method used

Implementing dynamic prioritization policies for UE-side data logging and reporting, which include configuring policies with mobility-dependent conditions, buffering requirements, and reporting criteria to optimize the logging and reporting of downlink radio measurements, enabling efficient batch reporting suitable for AIML models.

Benefits of technology

Improves prediction performance for network-based AIML models, enhances memory management for larger-scale data, and optimizes network radio resource use by prioritizing and managing data transfer effectively.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026062902_12112026_PF_FP_ABST
    Figure EP2026062902_12112026_PF_FP_ABST
Patent Text Reader

Abstract

An apparatus comprising means for: receiving from a network a configuration for configuring the apparatus with a policy for prioritization of logging time-series downlink radio measurements for batch reporting, wherein the policy for prioritization associates a mobility-dependent condition, a downlink radio measurement to be logged as a time-series, a buffering requirement for logging the downlink radio measurement as a time-series for batch reporting, monitoring fulfilment of the mobility-dependent condition; in dependence upon fulfilment of the mobility-dependent condition, applying to a buffer the buffering requirement for logging the DL radio measurement as a time-series for batch reporting; accumulating a time-series of downlink radio measurements in the buffer in accordance with the buffering requirement; reporting, as a batch report, the time-series of downlink radio measurements from the buffer.
Need to check novelty before this filing date? Find Prior Art

Description

[0001]

[0002] TITLE

[0003] Measurement and reporting at a radio terminal apparatus

[0004] TECHNOLOGICAL FIELD

[0005] Examples of the disclosure relate to larger scale measurement and reporting at a radio terminal apparatus. This has relevance for AIML models.

[0006] BACKGROUND

[0007] In a radio network, for example a cellular radio network, a terminal apparatus takes measurements and reports those measurements to the network.

[0008] In some examples, the network will send a measurement (and reporting) configuration to the terminal apparatus that specifies what to measure and report.

[0009] If there are too few measurements, the network lacks sufficient information. If there are too many measurements, there is redundant information that unnecessarily uses resources.

[0010] With the emergence of ‘big data’ and in particular artificial intelligence / machine learning (AIML) models at the network, there is a demand for more measurements, in quantity and type, to be transferred from the terminal to the network.

[0011] The existing approaches for measurement (and reporting) are not optimal for this larger scale measurement and reporting

[0012] BRIEF SUMMARY

[0013] The following disclosure presents new approaches for measurement (and reporting) from a radio terminal apparatus to the network that are better suited for large scale measurement and reporting, for example as associated with the use of network-based AIML models at the network

[0014] Examples enable dynamic changing of a prioritization policy for prioritization-based UE-side data logging (and reporting).

[0015] Examples improve prediction performance for a network-based AIML model..

[0016] Examples improve memory management for larger-scale data at a UE.

[0017] Examples improve network radio resource use for larger-scale data.

[0018] According to various, but not necessarily all, embodiments there is provided examples as claimed in the appended claims.

[0019] While examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is

[0020]

[0021] contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all the features described in respect of other examples of the disclosure, and vice versa. Also, it is to be appreciated that any one or more or all the features, in any combination, may be implemented by / comprised in / performable by an apparatus, a method, and / or instructions as desired, and as appropriate. The description of a function should additionally be considered to also disclose any means suitable for performing that function

[0022] BRIEF DESCRIPTION

[0023] Some examples will now be described with reference to the accompanying drawings in which:

[0024] FIG. 1 to 11 to show an example of the subject matter described herein.

[0025] The figures are not necessarily to scale. Certain features and views of the figures can be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aid explication. Similar reference numerals are used in the figures to designate similar features. For clarity, all reference numerals are not necessarily displayed in all figures.

[0026] DETAILED DESCRIPTION

[0027] Fig. 1 illustrates an example of a network 100 comprising a plurality of network entities including terminal apparatus 110, node apparatus 120 and one or more network apparatus 130. The terminal apparatus 110 and node apparatus 120 communicate 124 with each other. The one or more network apparatus 130 communicate 128 with the node apparatus 120.

[0028] In some examples the one or more network apparatus 130 communicate with the terminal apparatus 110. The one or more network apparatus 130 can, in some examples, communicate with each other. The one or more node apparatus 120 can, in some examples, communicate 126 with each other.

[0029] The network 100 can be a cellular network comprising a plurality of cells 122 each served by a node apparatus 120. In this example, the interface between the terminal apparatus 110 and a node apparatus 120 defining a cell 122 is a wireless interface 124. The node apparatus 120 comprises one or more cellular radio transceivers. The terminal apparatus 110 comprises one or more cellular radio transceivers.

[0030]

[0031] In the example illustrated the cellular network 100 is a third generation Partnership Project (3GPP) network in which the terminal apparatus 110 are user equipment (UE) and the node apparatus 120 can be access nodes such as base stations.

[0032] A user equipment comprises a mobile equipment. Where reference is made to user equipment that reference includes and encompasses, wherever possible, a reference to mobile equipment.

[0033] In some examples, during operation, a user equipment 110 comprises a mobile equipment comprising a smart card forauthentication / encryption etc. such as a Subscriber Identity Module (SIM). In some examples, during operation, a user equipment 110 comprises mobile equipment comprising circuitry embedded as part of the user equipment 110 for authentication / encryption such as software SIM.

[0034] The node apparatus 120 can be any suitable access node such as a base station or transmission reception point. The node apparatus 120 can be a network element responsible for radio transmission and reception in one or more cells 122, to or from the UE 110. The node apparatus 120 can be a network element in a Radio Access Network (RAN), an Open-Radio Access Network (O-RAN) or any other suitable type of network. The network apparatus 130 can be part of a core network. The network apparatus 130 can be configured to manage functions relating to connectivity for the UEs 110. For example, the network apparatus 130 can be configured to manage functions such as connectivity, mobility, authentication, authorization, and / or other suitable functions. In some examples the network apparatus 130 can comprise an Access and Mobility management Function (AMF) and / or a User Plane Function (UPF) or any other suitable entities.

[0035] In the example of Fig. 1 the network apparatus 130 is shown as a single entity. In some examples the network apparatus 130 could be distributed across a plurality of entities. For example, the network apparatus 130 could be cloud based or distributed in any other suitable manner. The network apparatus 130 can be a core network node.

[0036] The network 100 can be a 4G or 5G network, for example. It can for example be a New Radio (NR) network that uses gNB or eNB as access nodes 120. New Radio is the 3GPP name for 5G technology. In such cases the node apparatus 120 can comprise gNodeBs (gNBs) 120 configured to provide user plane and control plane protocol terminations towards the UE 110 and / or to perform any other suitable functions. The gNBs 120 are

[0037]

[0038] interconnected with each other by means of an X2 / Xn interface 126. The gNBs are also connected by means of the N2 interface 128 to the network apparatus 130. The gNBs can be connected to an AMF or any other suitable network apparatus 130. Other types of networks and interfaces could be used in other examples. Other types of network could comprise next generation mobile and communication network, for example, a 6G network. Referring to FIG 2A, in examples, an apparatus 110 is configured with a policy 300 for prioritization of logging (as illustrated in subsequent FIGs) time-series 240 downlink radio measurements 220 for batch reporting 218.

[0039] The example policy 300 for prioritization associates:

[0040] a policy (or priority) identifier 302;

[0041] a mobility-dependent condition 308;

[0042] a downlink radio measurement 220 to be logged as a time-series 240;

[0043] a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0044] a reporting requirement 304 for controlling reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 logged in the buffer 230.

[0045] In some examples, the time-series 240 of downlink radio measurement 220 are mobility procedure measurements 220 that measure measurements that change with mobility of the apparatus 110. In some examples, the time-series 240 of downlink radio measurement 220 are downlink reference signal measurements 220.

[0046] In some examples the reporting requirement 304 defines a trigger for reporting 218 the batch report 219 and / or a format for the batch report 219. The trigger for reporting 218 the batch report 219 can for example be an amount of logged data in the buffer for the measurement..

[0047] In some examples, the buffering requirement 306 defines one or more of priority of access to the buffer 230; a logging bit-rate; a required buffer size; a measurement interval; a measurement bit size.

[0048] The measurement bit size is the number of bits used to represent a measurement.220. The greater the bit-size the greater the resolution for the measurement but the greater the amount of buffering required, particularly for batch reporting.

[0049]

[0050] The measurement interval is a period of time between measurement.220 in the time series. The smaller the measurement interval the greater the time-resolution for the measurement but the greater the amount of buffering required, particularly for batch reporting.

[0051] The logging bit-rate is the rate at which measurements are logged measured in bits. It can be zero if there is no logging for an associated measurement 220. It increases as a measurement interval decreases. It increases as measurement bit size increases. The required buffer size is the size of buffer required to log measurements. It can be increased when the accumulation time period for batch reporting increases. It can be increased if there is an increase in logging bit-rate (or decrease in measurement interval or increase in measurement bit size).

[0052] The buffering requirement can for example specify that the buffer size and / or logging bit rate increases for one measurement 220 but decreases for another different measurement 220.

[0053] The priority identifier 308 associated with a downlink radio measurement 220 can be included in the batch report 219 for that downlink radio measurement 220. The batch report 219 comprises the priority identifier 308 that identifies the policy 300 for prioritization in use for logging the time-series downlink radio measurements 220 included in the batch report 219.

[0054] In some examples, the batch report 219 identifies the time-series of downlink radio measurements 220 as measurements for AIML-based prediction at the network 120. In some examples, the batch report 219 is sent using Signaling Radio Bearers (SRBs). A common SRB can be used for all batch reports 219. Alternatively, different SRBs can be used for different batch reports 219 (different prioritization levels).

[0055] The policy 300 can be created from one or more received configurations.

[0056] In some examples, a prioritization policy configuration can comprise:

[0057] the policy (or priority) identifier 302;

[0058] logging parameters that define the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218; measurement parameters for identifying the downlink radio measurement 220 to be logged as a time-series 240;

[0059]

[0060] prioritization policy selection parameters that define, for example a selection condition for an apparatus 110 selecting a particular prioritization policy (This can be used to define the mobility-dependent condition 308);

[0061] reporting parameter that define the reporting requirement 304 for controlling reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 logged in the buffer 230.

[0062] The policy configuration can be arranged as a hierarchy of information elements, where an information element (IE) for the prioritization policy comprises the policy (priority) identifier 302 and includes (or references) an IE for logging parameters; an IE for measurement parameters;

[0063] an IE for prioritization policy selection parameters (e.g. mobility-dependent condition 308); an IE for reporting parameters.

[0064] These policies can be pre-configured by the network 120 so that they can be easily selected later by the apparatus 110 in accordance with the selection condition. The selection condition can, for example, specify that the apparatus 110 autonomously selects a policy based on a particular mobility-dependent condition 308. The selection condition can, for example, specify that the apparatus 110 selects a policy based on a particular received indication from the network 120.

[0065] A prioritization policy can map one measurement to one buffering requirement, one reporting requirement and one selection condition (e.g. one mobility-dependent condition).

[0066] Alternatively, a prioritization policy can map a combination of a buffering requirement and a reporting requirement to multiple measurements. In some examples, these are associated with the same or different selection conditions, for example, the same or different mobility-dependent conditions 308

[0067] As illustrated in FIG 2B, it is possible to have different prioritization policies 300 for the same measurement 220 that, for example, define different buffering requirements. The different buffering requirement can be associated with the same or different selection conditions (e.g. same or different mobility-dependent conditions). The different buffering requirement can be associated with the same or different reporting

[0068] requirements.

[0069]

[0070] The policies can be pre-configured by the network so that they can be easily and flexibly (re)selected and applied later by the apparatus 110.

[0071] This enables optimized logging and reporting.

[0072] Thus in some examples, as illustrated in FIG 2B, a configuration 201 enables configuration of a first policy 300_1 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, that associates a higher priority to a first downlink measurement 220 to be logged as a time-series 240 and a lower priority to a second downlink measurement 220 to be logged as a time-series 240, wherein, in accordance with the first policy 300_1 , if applied, greater buffer 230 resources are allocated to logging a time series 240 data for the first measurement 220 than the second measurement 220, and

[0073] enables configuration of a second policy 300_2 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, that associates a lower priority to a first downlink measurement 220 to be logged as a time-series 240 and a higher priority to a second downlink measurement 220 to be logged as a time-series 240, wherein, in accordance with the second policy 300_1 , if applied, greater buffer 230 resources are allocated to logging time series 240 data for the second measurement 220 than the first measurement 220.

[0074] Subsequently, the apparatus 110 can select and apply the first policy 300_1 , and subsequently select and apply the second policy (r vice versa).

[0075] In some examples, the first policy 300_1 is for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, that associates a mobilitydependent condition 308, a downlink radio measurement 220 to be logged as a timeseries 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218. The buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218 is applied when the mobility-dependent condition 308 is determined as fulfilled. A timeseries 240 of downlink radio measurements 220 is accumulated in the buffer 230 in accordance with the buffering requirement 306. The

[0076] time-series 240 of downlink radio measurements 220 from the buffer 230. is subsequently reported 218, as a batch report 219, for example, in dependence upon a reporting requirement, also associated with the first policy.

[0077]

[0078] In some examples, the second policy 300_2 is for prioritization of logging time-series of second downlink radio measurements 220 for batch reporting 218, that associates a second mobility-dependent condition 308, a second downlink radio measurement 220 to be logged as a time-series 240, a second buffering requirement 306 for logging the second downlink radio measurement 220 as a time-series 240 for batch reporting 218. The second buffering requirement 306 for logging the second downlink radio measurement 220 as a time-series 240 for batch reporting 218 is applied when the second mobility-dependent condition 308 is determined as fulfilled. A time-series 240 of second downlink radio measurements 220 is accumulated in the buffer 230 in accordance with the second buffering requirement 306. The

[0079] time-series 240 of second downlink radio measurements 220 from the buffer 230. is subsequently reported 218, as a second batch report 219, for example, in dependence upon a second reporting requirement, also associated with the second policy.

[0080] In some examples, the apparatus 110 is configured to transmit to the network 120 a capability indication 206 that indicates a capability of the apparatus 110 to support configuring a policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218.

[0081] In some examples, the batch report 219 identifies the time-series 240 of downlink radio measurements 220 for handover preparation or for handover execution.

[0082] FIG 3A illustrates an example of an apparatus 110 comprising means for: receiving from a network 120 a configuration 201 for configuring the apparatus 110 with a policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0083] monitoring 210 fulfilment of the mobility-dependent condition;

[0084] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0085] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306;

[0086]

[0087] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0088] The apparatus 110 is configured to autonomously apply 212, in dependence upon fulfilment of the mobility-dependent condition 308, without reception of any network trigger, to the buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218.

[0089] The apparatus comprises means for receiving from the network 120 a configuration 201 for configuring the apparatus 110 with a second policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, wherein the second policy 300 for prioritization associates a second mobility-dependent condition 308, the downlink radio measurement 220 to be logged as a time-series 240, and a second buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0090] monitoring 210 fulfilment of the mobility-dependent condition;

[0091] in dependence upon fulfilment of the second mobility-dependent condition 308, applying 212

[0092] to the buffer 230 the second buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218 instead of the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0093] accumulating 214 a second time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the second buffering requirement 306;

[0094] reporting 218, as a batch report 219, the second time-series 240 of downlink radio measurements 220 from the buffer 230.

[0095] In some examples, the mobility-dependent condition 308 is a downlink radio condition 308_1 308 for the downlink radio measurement 220

[0096] In some examples, the mobility-dependent condition 308 is a downlink radio condition 308_1.

[0097] In some examples, the apparatus 110 comprises means for:

[0098] receiving from a network 120 a configuration 201 for configuring the apparatus 110 with a policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization

[0099]

[0100] associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0101] monitoring 210 fulfilment of the mobility-dependent condition 308, wherein the mobility-dependent condition 308 is a downlink radio condition 308_1;

[0102] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0103] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0104] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0105] In some examples, the mobility-dependent condition 308 is based on one or more of: measurement of reference signal(s) 222, for example, with respect to a threshold value;

[0106] measurements associated with the switching of radio environments, including cell edge and cell-center, low speed and high speed, event triggers, or failure counting. round-trip-time;

[0107] movement relative to cell edge;

[0108] radio link quality.

[0109] In one example, the mobility-dependent condition 308 is based on radio link quality and in particular is triggered when the radio link UE radio link quality [serving cell] is lower than a threshold, Qout or Qout.LR.

[0110] In one example, the threshold used for measurement of reference signal(s) 22 can be s-MeasConfig threshold. In another example, this threshold or thresholds can be cellcenterevaluation conditions (s-SearchThreshoIdP and s-SearchThresholdQ). In another example, this threshold can also be low speed threshold, e.g., s-SearchDeltaP.

[0111] In some examples, the mobility-dependent condition 308 is based on measurement of reference signal received power (RSRP). In some examples, the mobility-dependent condition 308 is a measurement event trigger, for example, event A1 , A2, A3 or B1 , B2.

[0112]

[0113] In some examples, the mobility-dependent condition 308 is based on measurement of interference such as reference signal received quality (RSRQ) and signal interference plus noise ratio (SINR).

[0114] In some examples, the mobility-dependent condition 308 associated with a policy 300 is based on measurements 220 associated with the policy 300 that would be logged if the mobility-dependent condition 308 is fulfilled.

[0115] In some examples, the mobility-dependent condition 308 associated with a policy 300 is based on measurements 220 that are not associated with the policy 300 and will not be logged if the mobility-dependent condition 308 is fulfilled.

[0116] In some examples, the mobility-dependent condition 308 is based on a carrier frequency of at least one downlink radio measurement 220.

[0117] In some examples, the apparatus 110 comprises means for:

[0118] receiving from a network 120 a configuration 201 for configuring the apparatus 110 with a policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0119] monitoring 210 fulfilment of the mobility-dependent condition 308, wherein the mobility-dependent condition 308 is based on carrier frequency of at least one downlink radio measurement 220;

[0120] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0121] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0122] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0123] In some examples, the mobility-dependent condition 308 is based on a carrier frequency of measured signals 222 from serving and / or neighboring cell / beam and / or is based on a frequency difference between carrier frequencies corresponding to the serving and neighbor cells.

[0124]

[0125] In some examples, the mobility-dependent condition 308 is based on a frequency difference between carrier frequencies corresponding to a measured signal and a signal that will have a measurement predicted, for example by a AIML model, which can be network based.

[0126] FIG 3B illustrates an example of an apparatus 110 comprising means for: receiving from a network 120 a configuration 201 for configuring the apparatus 110 with a policy 300 for prioritization of logging time-series 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a downlink radio measurement 220 to be logged as a time-series 240, and a buffering requirement 306 for logging the downlink radio measurement 220 as a timeseries 240 for batch reporting 218,

[0127] receiving 204, from the network 120, a prioritization indication 206 indicating the policy 300 associating the downlink radio measurement 220 to be logged as a timeseries 240, and the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218 ;

[0128] in dependence upon receiving the prioritization indication 206, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0129] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0130] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0131] In examples, the network 120 uses layer 1 (L1) and / or layer 2 ( L2) signaling to provide the prioritization indication 206 that instructs the UE to select or re-select prioritization.

[0132] In examples, the prioritization indication 206 is sent as a medium access control control element (MAC CE).

[0133] In examples, the prioritization indication 206 is sent via downlink control information (DCI).

[0134] In examples the apparatus 110 comprises means for:

[0135] receiving from the network 120 a configuration 201 for configuring the apparatus 110 with a second policy 300 for prioritization of logging time-series 240 downlink radio

[0136]

[0137] measurements 220 for batch reporting 218, wherein the second policy 300 for prioritization associates a second mobility-dependent condition 308, the downlink radio measurement 220 to be logged as a time-series 240, and a second buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0138] upon receiving a prioritization indication 206 indicating the second policy 300, applying 212

[0139] to the buffer 230 the second buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218 instead of the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0140] accumulating 214 a second time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the second buffering requirement 306;

[0141] reporting 218, as a batch report 219, the second time-series 240 of downlink radio measurements 220 from the buffer 230.

[0142] In FIGs 6 to 10, the reference numerals of previous FIGs are re-used where appropriate, with a bold font.

[0143] Artificial Intelligence (Al) and / or Machine Learning (ML) is referred to as AIML in this document. This is consistent with current study items in Rel.193GPP specifications . Prediction accuracy is an important evaluation parameter for an AIML model. Lifecycle management of the AIML model, based on performance, can also be important. In examples, time series data is batch reported 218 to the network by a user equipment (UE) 110 fortraining an AIML model or for inference using a network-based AIML model. Data (measurements 220) is used by an AIML model during training of the model. Data is used as an input to a trained AIML model during inference.

[0144] AIML can be used for mobility enhancement, for example in RRC_CONNECTED mode over air interface.

[0145] In some but not necessarily all examples, the handover decision is always made in network side.

[0146] In some but not necessarily all examples, mobility relates to a PCell change. In other examples, mobility relates to a PCell and / or SCell switch.

[0147]

[0148] In some but not necessarily all examples, PCell changes are performed via network triggered L3-based handover.

[0149] In some but not necessarily all examples, reporting for AIML mobility can be based on the radio resource management measurement framework

[0150] The mobility enhancements can, for example, include Radio Resource Management (RRM) measurement and event prediction. This can include: cell-level measurement prediction including intra and inter-frequency; inter-cell Beam-level measurement prediction for L3 Mobility, for example using a UE-sided AIML model in addition to a network-side AIML model; handover failure prediction and / or radio link failure (RLF) prediction, for example, using a UE sided AIML model. Measurement events prediction, for example, using a UE sided AIML model.

[0151] The mobility enhancements can for example include mobility management, for example: Handover Procedures; Cell Reselection; Beam Management.

[0152] The data (measurements 220) used by an AIML at the network can use data accumulated at a user equipment 110. This data can be accumulated using measurement procedures, for example, Reference Signal Received Power (RSRP) measurement; Reference Signal Received Quality (RSRQ) measurement; : Channel State Information (CSI); Interference Measurements.

[0153] A measurement configuration can be used to define measurements 220, for example measurements 220 relating to a serving cell and / or a target candidate cell.

[0154] In examples, each measurement 220 is not reported individually. Multiple measurements 220 are accumulated 214 over time and reported together 218 using a batch report 219.

[0155] A distinction, based on priority, is introduced in relation to the logging and / or reporting of different measurements 220.

[0156] The UE prioritizes logging of data (measurements 220) for the network side AIML model.

[0157] The UE reduces logging and reporting of unimportant data (measurements 220) for the network side AIML model.

[0158] The allocation of priority can be based on the dynamic application of previously configured 301 prioritization policies 300.

[0159]

[0160] The dynamic application of previously configured 301 prioritization policies 300 can be based on an autonomous UE decision, for example, based on fulfilment of a monitored 210 condition.

[0161] The dynamic application of previously configured prioritization policies can be based on network transmission of an indication 206 of a prioritization policy.

[0162] Examples of configuration parameters for prioritization-based UE data logging ( buffering) include:

[0163] Buffer size per prioritization type / ID: the higher prioritization level in the logged / buffered data, the higher buffer size (e.g., in Mb) shall be configured. Different buffer sizes can be configured for different prioritization IDs.

[0164] Logging / buffering interval per prioritization type / ID: the higher prioritization level in the logged / buffered data, the higher logging resolution or smaller logging intervals (e.g., in ms or slots) shall be configured. Different logging intervals can be configured for different prioritization IDs.

[0165] Examples of configuration parameters for prioritization-based UE logged data reporting include:

[0166] Buffer report thresholds per prioritization type / ID: the higher prioritization level in the logged / buffered data, the higher reporting threshold based on the buffer size (e.g., in Mb) shall be configured. Different report thresholds can be configured for different prioritization IDs.

[0167] Data report format per prioritization type / ID: the higher prioritization level in the logged / buffered data, the higher quantized bit size shall be configured. Different report formats can be configured for different prioritization IDs.

[0168] Other configuration parameters are UE assistance information (UAI)Zother UE UL indication signals: this is used for network triggered reporting. The options of UE sided UL indication signals may include data availability indication, UE low power indication, UE overheating indication, or other types of UAls, etc.

[0169] Each prioritization type can be configured with a specific prioritization ID to buffer the data. The prioritization IDs can be formulated according to the data prioritization levels per prioritization type as discussed above. The identification for logged data can be sorted either with descending or ascending orders.

[0170] Conditions for selecting a prioritization policy include:

[0171]

[0172] Condition 1: when UE starts to measure neighbor cell, SS-RSRP < s-measureConfig. Condition 2: when serving cell RSRP is lower than a threshold, i.e., Event A2 is triggered.

[0173] Condition 3: when UE is moving towards the cell edge and cellEdgeEvaluation is satisfied.

[0174] Condition 4: UE radio link quality [serving] is lower than a threshold, Qout or Qout.LR. Condition 5: measurement gap is configured for inter-frequency measurements.

[0175] Condition 6: when HO execution is started at the UE, i.e., RRC reconfiguration with HO command or MAC CE cell switch command is received by the UE.

[0176] UE mobility may encounter challenging radio environment changes. Measurements associated with the switching of radio environments, such as cell edge / cell-center, low / high speed, event triggers, or failure counting, need to be specifically handled. This is not explicitly addressed in AI / ML for PHY use cases.

[0177] RRM measurement prediction may also be conducted in the frequency domain, where measurements might be performed for both intra- and inter-frequency when SMTC and measurement gaps are configured.

[0178] The prioritization selection can based on carrier frequency layers, i.e., higher the carrier frequency, higher the measurement data prioritization. This case is specifically valuable for frequency domain measurement reduction. For AI / ML-based RRM measurement prediction, one of the most critical use case is to study how far AI / ML can accurately predict the frequency domain. As the frequency gap between the two bands of inference input and inference output increases, the difference in radio propagation characteristics becomes more significant, which makes the prediction more challenging. Therefore, the higher the frequency gap with respect to the serving cell carrier, the higher prioritization should be considered.

[0179] The prioritization selection can be based on the frequency correlations of the measurement, i.e., higher the correlation metrics, higher the measurement data prioritization. This case is specifically valuable for frequency domain measurement reduction.

[0180] The prioritization selection can be based on the beam or cell / RAT correlations of the measurement, i.e., higher the correlation metrics among the measured beams, higher the

[0181]

[0182] measurement data prioritization. This case is specifically valuable for spatial domain measurement reduction.

[0183] The prioritization selection can be based on radio resource management (RRM) temporal case B prediction patterns, e.g., the measurements with higher measurement reduction rate in time domain (MRRTs) in general is with higher data prioritization.

[0184] The prioritization selection can be based on the UE radio conditions, e.g., the measurements taken at the cell-edge or higher speed categories are assigned higher priorities.

[0185] The prioritization selection can be based on the critical UE behaviors during mobility, e.g., the measurements taken when s-measureConfig or Qout threshold is verified, when event A2 / A3 TTT is triggered, when failure related timers T310 or Beam Failure Detection (BFD) timers are triggered are assigned higher priorities.

[0186] In some examples, new RRC configuration Information Elements (lEs) are introduced to define the prioritization levels in the UE logging (buffering) and reporting processes. FIG 4 illustrates a high-level implementation example of data buffers 230 per prioritization identities (IDs) at the UE. For each prioritization ID, the UE is using different buffer size, logging intervals and report formats.

[0187] FIG 5 illustrates an example of a method 400.

[0188] At block 402, the UE receives RRC configuration of data buffering / logging and reporting based on prioritization.

[0189] At block 404, the UE applies the configured parameters for data buffering / logging: prioritization type

[0190] prioritization ID

[0191] logging interval T1

[0192] buffer report threshold Th1

[0193] At block 406, it is determined if the buffer report condition is triggered.

[0194] In this example, it is determined if the buffered data volume >= threshold Th1 for each prioritization ID (in at least some examples, for each measurement 220).

[0195] If YES, then the method moves to block 408 where the UE reports the buffered data with the prioritization ID and N bits format.

[0196] If NO, then the method moves to block 410 where the UE evaluates the configuration switching conditions:

[0197]

[0198] Condition 1: when UE starts to measure neighbor cell, SS-RSRP < s-measureConfig. Condition 2: when serving cell RSRP is lower than a threshold, i.e., Event A2 is triggered.

[0199] Condition 3: when UE is moving towards the cell edge and cellEdgeEvaluation is satisfied.

[0200] Condition 4: UE radio link quality is lower than a threshold, Qout or Qout.LR.

[0201] Condition 5: measurement gap between measurement and prediction is configured for inter-frequency measurements. The measurement gap can be configured to perform interfrequency measurements.

[0202] At block 412, it is determined if a configuration switching condition is fulfilled. OR a network switching indication is received.

[0203] If NO, then the method moves to block 410.

[0204] If YES, then the method moves to block 414, where the UE switches to the configured parameters for data buffering / logging;

[0205] prioritization type

[0206] prioritization ID

[0207] logging interval T2

[0208] buffer report threshold Th2

[0209] At block 416, it is determined if the buffer report condition triggered.

[0210] In this example, it is determined if the buffered data volume >= threshold Th2 for each prioritization ID (in at least some examples, for each measurement 220).

[0211] If YES, then the method moves to block 418 where the UE reports the buffered data with the prioritization ID and N bits format.

[0212] If NO, then the method moves to block 410.

[0213] In some examples, block 404 involves receiving from a network 120 a configuration 201 for configuring the apparatus 110 with a policy 300 for prioritization of logging timeseries 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218.

[0214]

[0215] In some examples, block 410 involves monitoring 210 fulfilment of a priority selection condition, for example, a mobility-dependent condition.

[0216] In some examples, block 414 involves applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218, in dependence upon fulfilment of the mobility-dependent condition 308, and then accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306. In some examples, block 416 involves reporting 218, as a batch report 219, the timeseries 240 of downlink radio measurements 220 from the buffer 230.

[0217] FIG 6 illustrates an example of a method 500 comprising UE initiated reporting for the network sided data collection based on the prioritization IDs.

[0218] At step 502, the UE 110 exchanges capability information with the gNB 120. In some examples, a new UE capability information element (IE) is introduced, which includes the types of measurements it can perform and the data it can prioritize to log / buffer.

[0219] At step 504, the gNB 120 sends the RRC configuration to the UE 110. This configuration includes measurement configuration (measConfig) with data prioritization ID, type, and report parameters.

[0220] Measurement gap configuration might be included for UE 110 to perform interfrequency measurements. In particular, the monitoring conditions for switching the prioritization order by the UE 110 are also configured.

[0221] At steps 506, 508, the gNB 120 performs beam sweeping and transmits Reference Signals (RS) to the UE 110. These signals can be SSB or CSI-RS.

[0222] At step 510, the UE 110 performs downlink (DL) L1 and / or L3 measurements.

[0223] The L3 filtering coefficient is configured at Step 502 in case L3 measurements are performed and prioritized.

[0224] At step 512, the gNB 120 sends a data logging indication to the UE 110 for different prioritization IDs. This indication can be in the form of MAC CE or DCI. The UE 110 is instructed to log / buffer measurements based on the prioritization IDs.

[0225] In one implementation example, the indication signal can be an extension of DCI format 0_1 DataLoggingTriggerFlag with 1 bit field value, where 0 = no trigger, 1 = trigger on UE 110 sided data buffering / logging.

[0226]

[0227] In another implementation example, the indication signal can also use a dedicated 1 octet or 2 octet MAC CE carried in a DL grant (DCI Format 2_0) or via PHICH.

[0228] At step 514, the UE 110 logs measurements according to the prioritization types and / or prioritization IDs with the buffer size B1, logging interval In1, and buffering reporting threshold Th1, etc.

[0229] The detailed configuration parameters have been mention above.

[0230] At step 516 , the UE 110 sends the buffer status of the logged data to the gNB 120 when the amount of data is greater than the threshold Th1.

[0231] At step 518, the gNB 120 sends UL grant based on the buffer status of the UE 110 sided data. Alternatively, if configured grant (CG) is used for transferring the buffered data at step 1 , then this UL grant transmission from the gNB 120 to the UE 110 is not required. At step 520, the UE 110 reports the logged data to the network by using N-bits UL signal as per the gNB 120 grant.

[0232] At step 522, the gNB 120 performs data collection procedures.

[0233] At step 524, The UE 110 monitors pre-configured prioritization switching conditions. The condition may include at least one of the following:

[0234] Condition 1: when UE 110 starts to measure neighbor cell, SS-RSRP < s-measureConfig.

[0235] Condition 2: when serving cell RSRP is lower than a threshold, i.e., Event A2 is triggered.

[0236] Condition 3: when UE 110 is moving towards the cell edge and cellEdgeEvaluation is satisfied.

[0237] Condition 4: UE 110 radio link quality is lower than a threshold, Qout orQout.LR. Other conditions related to the HO procedures are discussed in embodiment 3 At step 526, the UE 110 logs measurements according to the prioritization types and / or prioritization IDs with the buffer size B2, logging interval IT2, and buffering reporting threshold Th2, etc.

[0238] At step 528, the UE 110 sends the buffer status of the logged data to the gNB 120 when the amount of data is greater than the threshold Th2.

[0239] At step 530 (optional), the gNB 120 sends UL grant based on the buffer status of the UE 110 sided data.

[0240]

[0241] Similarly, if configured grant (CG) is used for transferring the buffered data at step 1 , then this UL grant transmission from the gNB 120 to the UE 110 is not required.

[0242] At step 532, the UE 110 reports the logged data to the network by using M-bits UL signal as per the gNB 120 grant.

[0243] FIG 7 illustrates an example of a method 500 comprising network triggered reporting for the network sided data collection based on the prioritization IDs.

[0244] The steps 502 to 520 are as previously described with reference to FIG 6. However, since this embodiment relates to network control, the UE monitoring conditions are not included in the received configuration.

[0245] At step 522, the gNB 120 performs data collection procedures.

[0246] At step 523, the gNB 120 monitors data prioritization switching conditions based on the network logging status. In one example, the network sided buffer is reaching the buffer limit or the network load condition is higher than a threshold.

[0247] At step 525, the gNB 120 sends a data logging prioritization switching indication to the UE 110 based on the network conditions. This indication can be in the form of MAC CE or DCI. To ensure the fast-signaling reactions between the UE 110 and the gNB 120, we slightly prefer the usage of DCI.

[0248] In one implementation example, the indication signal can be an extension of DCI format 0_1 DataLoggingSwitchFlag with 1 bit field value, where 0 = no switch, 1 = switch on UE 110 sided data buffering / logging to a different prioritization level.

[0249] At step 526, the UE 110 logs measurements according to the prioritization types and / or prioritization IDs with the buffer size B2, logging interval IT2, and buffering reporting threshold Th2, etc.

[0250] At step 528, the UE 110 sends the buffer status of the logged data to the gNB 120 when the amount of data is greater than the threshold Th2.

[0251] At step 530, (optional), the gNB 120 sends UL grant based on the buffer status of the UE 110 sided data. Similarly, if configured grant (CG) is used for transferring the buffered data at step 1, then this UL grant transmission from the gNB 120 to the UE 110 is not required.

[0252] At step 532, the UE 110 reports the logged data to the network by using M-bits UL signal as per the gNB 120 grant.

[0253]

[0254] FIG 8 illustrates an example of a method 500 comprising UE initiated reporting for the network sided data collection based on the prioritization IDs. It is similar to FIG 6 and only the different blocks are illustrated. This method 500 relates to prioritization switching during handover preparation. The UE switches prioritization when event A3 is triggered 514 during the handover preparation phase.

[0255] Steps 502 to 512 are the same as FIG 6. However, in this example the HO preparation relies on the event A3 configuration and network-side data collection disables the legacy measurement report. In at least some examples, the UE 110 is configured with the event A3 configuration to prioritize data without the legacy measurement reporting at step 514. Also, at steps 506, 508, the source gNB 120 performs beam sweeping and transmits Reference Signals (RS) to the UE 110 and the target gNB 120 performs beam sweeping and transmits Reference Signals (RS) to the UE 110. These reference signals can be SSB or CSI-RS, for example.

[0256] At step 514, the UE 110 switches the data logging / buffering configuration when the Event A3 is verified to be true after the TTT (time-to-trigger) expiry time.

[0257] At steps 516-520, the UE 110 logs measurements according to the prioritization types and / or prioritization IDs with the buffer size B2, logging interval IT2, and buffering reporting threshold Th2, etc. The UE 110 sends the buffer status of the logged data to the gNB 120 when the amount of data is greater than the threshold Th2. Optionally , the gNB 120 sends UL grant based on the buffer status of the UE 110 sided data. Similarly, if configured grant (CG) is used for transferring the buffered data at step 1, then this UL grant transmission from the gNB 120 to the UE 110 is not required. The UE 110 reports the logged data to the network by using M-bits UL signal as per the gNB 120 grant.

[0258] At step 602, the source gNB 120 makes a HO decision based on the UE 110 reported data (instead of event triggered measurement report) and determines a target gNB 120 for HO.

[0259] At step 604, the source gNB 120 sends a HO request to the target gNB 120, including data transfer with different prioritization levels / IDs. For example, the source gNB 120 may transfer only the data with higher prioritization IDs to the target.

[0260] At step 522, the target gNB 120 starts to collect the source gNB 120 reported data with different prioritization IDs.

[0261]

[0262] At step 606, the target gNB 120 sends a HO request acknowledgment to the source gNB 120.

[0263] At step 608, the source gNB 120 clears the collected data after the HO request acknowledgement.

[0264] At step 610, the source gNB 120 sends a RRC reconfiguration with HO command to the UE 110.

[0265] At step 612, the UE 110 clears the data buffer based on different prioritization IDs. For instance, during the HO execution, the UE 110 may reduce or discard data with lower prioritization to conserve power.

[0266] FIG 9 illustrates an example of a method 500 comprising UE initiated reporting for the network sided data collection based on the prioritization IDs. It is similar to FIG 7 and only the different blocks are illustrated. This method 500 relates to prioritization switching during handover execution. The UE switches prioritization upon receiving the handover command.

[0267] Compared to FIG 8, the UE 110 at step 610, 525 switches the prioritization configuration based on the RRC reconfiguration handover command (or RRC reconfiguration with ReconfigurationWithSync).

[0268] The data reporting is then directed to the target gNB 120 after the HO.

[0269] In another embodiment, if the lower layer triggered mobility (LTM) is configured, then the UE 110 switches the prioritization configuration based on the MAC CE cell switch command. The data reporting is then directed to the target gNB 120-DU after the cell switch.

[0270] Fig 10 illustrates an example of a controller 400 suitable for use in an apparatus 110. Implementation of a controller 400 may be as controller circuitry. The controller 400 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).

[0271] As illustrated in Fig 10 the controller 400 may be implemented using instructions that enable hardware functionality, for example, by using executable instructions 406 in a general-purpose or special-purpose processor 402 that may be stored on a machine readable storage medium (disk, memory etc.) to be executed by such a processor 402. The processor 402 is configured to read from and write to the memory 404. The processor 402 may also comprise an output interface via which data and / or commands

[0272]

[0273] are output by the processor 402 and an input interface via which data and / or commands are input to the processor 402.

[0274] The memory 404 stores instructions, program, or code 406 that controls the operation of the apparatus 110 when loaded into the processor 402. The instructions, program, or code 406, provide the logic and routines that enables the apparatus 110 to perform the methods illustrated in the accompanying FIGs. The processor 402 by reading the memory 404 is configured to load and execute the instructions, program, or code 406. As illustrated in Fig 11, the instructions, program, or code 406 may arrive at the apparatus 110 via any suitable delivery mechanism 408. The delivery mechanism 408 may be, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a solid-state memory, an article of manufacture that comprises or tangibly embodies the instructions 406. The delivery mechanism may be a signal configured to reliably transfer the instructions 406. The apparatus 110 may propagate or transmit the instructions406 as a data signal.

[0275] The term “non-transitory” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0276] The instructions 406 cause the apparatus 110 to perform one or all of the following (i) to (iv) and / or the apparatus 110 comprises: at least one processor 402; and at least one memory 404 storing instructions that, when executed by the at least one processor 402, cause the apparatus at least to perform one or all of the following (i) to (iv):

[0277] (i) configuring the apparatus 110 with a policy 300 for prioritization of logging timeseries 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0278] monitoring 210 fulfilment of the mobility-dependent condition;

[0279] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0280]

[0281] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306;

[0282] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0283] (ii) configuring the apparatus 110 with a policy 300 for prioritization of logging timeseries 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0284] monitoring 210 fulfilment of the mobility-dependent condition 308, wherein the mobility-dependent condition 308 is a downlink radio condition 308_1;

[0285] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0286] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0287] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0288] (iii) configuring the apparatus 110 with a policy 300 for prioritization of logging timeseries 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a mobility-dependent condition 308, a downlink radio measurement 220 to be logged as a time-series 240, a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0289] monitoring 210 fulfilment of the mobility-dependent condition 308, wherein the mobility-dependent condition 308 is based on carrier frequency of at least one downlink radio measurement 220;

[0290] in dependence upon fulfilment of the mobility-dependent condition 308, applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0291]

[0292] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0293] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0294] (iv) configuring the apparatus 110 with a policy 300 for prioritization of logging timeseries 240 downlink radio measurements 220 for batch reporting 218, wherein the policy 300 for prioritization associates a downlink radio measurement 220 to be logged as a time-series 240, and a buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0295] in dependence upon receiving 204, from the network 120, a prioritization indication 206 indicating the policy 300 associating the downlink radio measurement 220 to be logged as a time-series 240, and the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218,

[0296] applying 212 to a buffer 230 the buffering requirement 306 for logging the downlink radio measurement 220 as a time-series 240 for batch reporting 218;

[0297] accumulating 214 a time-series 240 of downlink radio measurements 220 in the buffer 230 in accordance with the buffering requirement 306; and

[0298] reporting 218, as a batch report 219, the time-series 240 of downlink radio measurements 220 from the buffer 230.

[0299] The instructions 406 may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some but not necessarily all examples, the instructions 406 may be distributed over more than one computer program.

[0300] Although the memory 404 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable and / or may provide permanent / semi-permanent / dynamic / cached storage.

[0301] Although the processor 402 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable. The processor 402 may be a single core or multi-core processor. References to ‘computer-readable storage medium’, ‘computer program product’, ‘tangibly embodied computer program’ etc. or a ‘controller’, ‘computer’, ‘processor’ etc.

[0302]

[0303] should be understood to encompass not only computers having different architectures such as single / multi- processor architectures and sequential (Von Neumann) / parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry including quantum processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.

[0304] As used in this application, the term ‘circuitry’ may refer to one or more or all the following:

[0305] (a) hardware-only circuitry implementations (such as implementations in analog, digital and / or quantum circuitry) and

[0306] (b) combinations of hardware circuit(s) and software, such as (as applicable):

[0307] i. a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and

[0308] ii. any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device or server, to perform various functions and

[0309] (c) any or all portions of hardware circuit(s), such as a microprocessor(s) and / or quantum processors , that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation.

[0310] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0311]

[0312] The blocks illustrated in the accompanying Figs may represent steps in a method and / or sections of code in the instructions 406. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted.

[0313] As used here ‘module’ refers to a unit or apparatus that excludes certain parts / components that would be added by an end manufacturer or a user. The apparatus 110 can, for example be a module. A controller 400 of the apparatus 110 can, for example be a module.

[0314] Where a structural feature has been described, it may be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described.

[0315] The above-described examples find application as enabling components of: automotive systems; telecommunication systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and / or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things; virtualized networks; and related software and services.

[0316] The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore,

[0317]

[0318] devices can readily employ examples of the present disclosure regardless of their intent to provide mobility.

[0319] The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X may comprise only one Y or may comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning then it will be made clear in the context by referring to ‘comprising only one...’ or by using ‘consisting.’

[0320] In this description, the wording ‘connect’, ‘couple’ and ‘communication’ and their derivatives mean operationally connected / coupled / in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e. , to provide direct or indirect connection / coupling / communication. Any such intervening components can include hardware and / or software components.

[0321] As used herein, the term "determine / determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database, or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory), obtaining and the like. Also, " determine / determining" can include resolving, selecting, choosing, establishing, and the like.

[0322] In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ‘example’ or ‘for example’ or ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some of or all other examples. Thus ‘example’, ‘for example’, ‘can’, or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible

[0323]

[0324] be used in that other example as part of a working combination but does not necessarily have to be used in that other example.

[0325] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0326] Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.

[0327] Features described in the preceding description may be used in combinations other than the combinations explicitly described above.

[0328] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.

[0329] The description of a feature, such as an apparatus or a component of an apparatus, configured to perform a function, or for performing a function, should additionally be considered to also disclose a method of performing that function. For example, description of an apparatus configured to perform one or more actions, or for performing one or more actions, should additionally be considered to disclose a method of performing those one or more actions with or without the apparatus.

[0330] Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not.

[0331] The term ‘a’, ‘an’ or ‘the’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a / an / the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’, ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.

[0332] The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the

[0333]

[0334] same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result.

[0335] In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described.

[0336] As used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or mor” respectively.

[0337] The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein above and which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure.

[0338] Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance the Applicant may seek protection via the claims in respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not emphasis has been placed thereon.

[0339] l / we claim:

Claims

32CLAIMS1. An apparatus comprising means for:receiving from a network a configuration for configuring the apparatus with a policy for prioritization of logging time-series downlink radio measurements for batch reporting, wherein the policy for prioritization associates a mobility-dependent condition, a downlink radio measurement to be logged as a time-series, a buffering requirement for logging the downlink radio measurement as a time-series for batch reporting,monitoring fulfilment of the mobility-dependent condition;in dependence upon fulfilment of the mobility-dependent condition, applyingto a buffer the buffering requirement for logging the DL radio measurement as a timeseries for batch reporting;accumulating a time-series of downlink radio measurements in the buffer in accordance with the buffering requirement;reporting, as a batch report, the time-series of downlink radio measurements from the buffer.

2. The apparatus as claimed in claim 1, configured to autonomously applying, without reception of any network trigger, to the buffer, the buffering requirement for logging the downlink radio measurement as a time-series for batch reporting, in dependence upon fulfilment of the mobility-dependent condition.

3. The apparatus as claimed in claim 1 or 2, comprising means for receiving from the network a configuration for configuring the apparatus with a second policy for prioritization of logging time-series downlink radio measurements for batch reporting, wherein the second policy for prioritization associates a second mobility-dependent condition, the downlink radio measurement to be logged as a time-series, and a second buffering requirement for logging the downlink radio measurement as a time-series for batch reporting,monitoring fulfilment of the mobility-dependent condition;in dependence upon fulfilment of the second mobility-dependent condition, applying33to the buffer the second buffering requirement for logging the DL radio measurement as a time-series for batch reporting instead of the buffering requirement for logging the DL radio measurement as a time-series for batch reporting;accumulating a second time-series of downlink radio measurements in the buffer in accordance with the second buffering requirement;reporting, as a batch report, the second time-series of downlink radio measurements from the buffer.

4. The apparatus as claimed in claim 1, 2 or 3 wherein the mobility-dependent condition is a downlink radio condition for the downlink radio measurement.

5. The apparatus as claimed in any preceding claim, wherein the batch report comprises an indicator of the policy for prioritization in use for logging the time-series downlink radio measurements included in the batch report.

6. The apparatus as claimed in any preceding claim,wherein the configuration configuring a policy for or prioritization of logging time-series downlink radio measurements for batch reporting, additionally associates a reporting requirement with the downlink radio measurement, wherein reporting, as a batch report, the time-series of downlink radio measurements from the buffer is controlled in accordance with the reporting requirement.

7. The apparatus as claimed in claim 6, wherein the reporting requirement defines a trigger for reporting and / or a format for the batch report.

8. The apparatus as claimed in any preceding claim, wherein the buffering requirement defines priority of access to the buffer; and / Zor a logging bit-rate and / or a required buffer size and / or a measurement interval and / or a measurement bit size.

9. The apparatus as claimed in any preceding claim, wherein the buffering requirements prevent or reduce buffering for a different measurement.

10. The apparatus as claimed in any preceding claim, wherein the configuration configuring a policy for prioritization of logging time-series downlink radio measurements for batch reporting, additionally associates a prioritization identifier with the downlink radio measurement and wherein the batch report comprises the prioritization identifier.

11. The apparatus as claimed in any preceding claim, wherein the configuration configuring a policy for prioritization of logging time-series downlink radio measurements for batch reporting, comprises an information element defining a prioritization level that is associated with one or more measurements.

12. The apparatus as claimed in any preceding claim, wherein the apparatus is configured to transmit to the network a capability indication that indicates a capability of the apparatus to support configuring a policy for prioritization of logging time-series downlink radio measurements for batch reporting.

13. The apparatus as claimed in any preceding claim, wherein the batch report identifies the time-series of downlink radio measurements forAIML-based prediction at the network.

14. The apparatus as claimed in any preceding claim, wherein the batch report identifies the time-series of downlink radio measurements for handover preparation or for handover execution.

15. The apparatus as claimed in any preceding claim, wherein the time-series of downlink radio measurement are mobility procedure measurements and / or reference signal measurements.

16. The apparatus as claimed in any preceding claim, wherein the configuration enables configuration of a first policy for prioritization of logging time-series downlink radio measurements for batch reporting, that associates a higher priority to a first downlink measurement to be logged as a time-series and a lower priority to a second downlink measurement to be logged as a time-series, wherein, in accordance with the first policy,if applied, greater buffer resources are allocated to logging a time series data for the first measurement than the second measurement, andenables configuration of a second policy for prioritization of logging time-series downlink radio measurements for batch reporting, that associates a lower priority to a first downlink measurement to be logged as a time-series and a higher priority to a second downlink measurement to be logged as a time-series, wherein, in accordance with the second policy, if applied, greater buffer resources are allocated to logging time series data for the second measurement than the first measurement.

17. A method comprising:receiving from a network a configuration for configuring the apparatus with a policy for prioritization of logging time-series downlink radio measurements for batch reporting, wherein the policy for prioritization associates a mobility-dependent condition, a downlink radio measurement to be logged as a time-series, a buffering requirement for logging the downlink radio measurement as a time-series for batch reporting,monitoring fulfilment of the mobility-dependent condition;in dependence upon fulfilment of the mobility-dependent condition, applyingto a buffer the buffering requirement for logging the DL radio measurement as a timeseries for batch reporting;accumulating a time-series of downlink radio measurements in the buffer in accordance with the buffering requirement;reporting, as a batch report, the time-series of downlink radio measurements from the buffer.

18. A computer program comprising instructions that when executed by one or more processors of an apparatus cause:configuring the apparatus with a policy for prioritization of logging time-series downlink radio measurements for batch reporting, wherein the policy for prioritization associates a mobility-dependent condition, a downlink radio measurement to be logged as a timeseries, a buffering requirement for logging the downlink radio measurement as a timeseries for batch reporting,monitoring fulfilment of the mobility-dependent condition;36in dependence upon fulfilment of the mobility-dependent condition, applyingto a buffer the buffering requirement for logging the DL radio measurement as a timeseries for batch reporting;accumulating a time-series of downlink radio measurements in the buffer in accordance with the buffering requirement;reporting, as a batch report, the time-series of downlink radio measurements from the buffer.