Managing data collection

Abstract

The present disclosure provides a method for managing data collection. The method is performed by a user equipment (UE). The method comprises receiving (102), from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE, and performing (104) the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

Description

MANAGING DATA COLLECTIONTECHNICAL FIELD

[0001] The present disclosure relates to methods for managing data collection, and a user equipment and network node configured to perform those methods.BACKGROUND

[0002] Artificial Intelligence (Al) and Machine Learning (ML) have been investigated, both in academia and industry, as promising tools to optimize the design of the air-interface in wireless communication networks. Example use cases include using autoencoders for Channel State Information (CSI) compression to reduce the feedback overhead and improve channel prediction accuracy; using deep neural networks for classifying Line-of-Sight (LOS) and Non- LOS (NLOS) conditions to enhance the positioning accuracy; and using reinforcement learning for beam selection at the network (NW) side and / or the User Equipment (UE) side to reduce the signaling overhead and beam alignment latency; using deep reinforcement learning to learn an optimal precoding policy for complex Multiple Input Multiple Output (MIMO) precoding problems.

[0003] In Third Generation Partnership Project (3 GPP) New Radio (NR) standardization work, a new Release 18 (Rel-18) study item on Al or ML (AI / ML) for the NR air interface started in May 2022. This study item will explore the benefits of augmenting the air-interface with features enabling improved support of AI / ML based algorithms for enhanced performance and / or reduced complexity / overhead. Through studying a few selected use cases (CSI feedback, beam management (BM), and positioning), this study item aims at laying the foundation for future air-interface use cases leveraging AI / ML techniques.

[0004] The analysis carried out during the Rel-18 is now considered in the context of Release 19 (Rel-19, or R19). Additionally, during the Rel-19, a new study item addressing AI / ML for mobility has been approved. In the context of this new study item, 3GPP will investigate methods for cell-level measurement predictions, and mobility event predictions. These mobility event predictions can, for example, comprise Radio Link Failure (RLF), handover failure (HOF), mobility-related events predictions such as A3 (neighbour becomes offset better than special cell (SpCell)) or A5 (SpCell becomes worse than threshold 1 and neighbour becomes better than threshold2), etc.

[0005] Data collection is a useful tool that allows the training entity to generate a model suitable for a specific device. In particular, related to the case of AI / ML applied to Radio Access Network (RAN) use cases (e.g. beam management, positioning accuracy enhancements, cell or frequency level measurement predictions, mobility event predictions, etc.), the AI / ML model may be UE-sided (e.g. tailored for specific UEs) or NW-sided (e.g. tailored for specific network nodes, such as specific NR Node Bs (gNBs). In order for RAN schemes based on AI / ML models to outperform conventional non-AI / ML based schemes, the device (UE or network node (e.g. gNB) in this case) may collect data so that the training entity can generate a model suitable for the device inference. Otherwise, if the collected data set during the training does not match the inputs during the inference, then it is proven that AI / ML may not provide the expected benefits.

[0006] There currently exist certain challenge(s).SUMMARY

[0007] One challenge that remains unresolved is in relation to when (and how) to trigger data collection. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0008] Accordingly, in one aspect, there is provided a first method for managing data collection. The first method is performed by a user equipment (UE). The first method comprises receiving, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE. The first method comprises performing the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0009] In another aspect, there is provided a second method for managing data collection at a UE. The second method is performed by a network node. The second method comprises transmitting, to the UE, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE. The one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0010] In another aspect, there is provided a method performed by a system. The method performed by the system comprises the first method and the second method.

[0011] In another aspect, there is provided a UE comprising processing circuitry configured to cause the UE to receive, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE, and perform the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0012] In another aspect, there is provided a network node comprising processing circuitry configured to cause the network node to transmit, to the UE, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE. The one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0013] In another aspect, there is provided a system comprising the wireless device and the network node.

[0014] In another aspect, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the first method and / or the second method.

[0015] In another aspect, there is provided a computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the first method and / or the second method.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0017] Fig. l is a flow chart illustrating a method in accordance with some embodiments;

[0018] Fig. 2 is a flow chart illustrating a method in accordance with some embodiments;

[0019] Fig. 3 shows an example of a communication system in accordance with some embodiments;

[0020] Fig. 4 shows a user equipment in accordance with some embodiments;

[0021] Fig. 5 shows a network node in accordance with some embodiments;

[0022] Fig. 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0023] Fig. 7 is a signalling diagram illustrating a method in accordance with some embodiments.DETAILED DESCRIPTION

[0024] 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. Additional information may also be found in the document(s) provided in the Appendix.

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

[0026] Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0027] As described earlier, data collection is a useful tool that allows the training entity to generate a model suitable for a specific device. The AI / ML model may be UE-sided (e.g. tailored for specific UEs) or NW-sided (e.g. tailored for specific network nodes, such as specific NR Node Bs (gNBs).

[0028] Related to NW-side models, it has been assumed so far in 3GPP that the network node (e.g. gNB) and / or the Operation Administration and Maintenance (0AM) node can be in charge of collecting data from the radio access network (RAN) for the purpose of NW-side model training. If the network node (e.g. gNB) is responsible, it is assumed that the network node may configure the UE with a set of resources (e.g. Channel State Information Reference Signal (CSLRS) resources or Synchronization Signal Block (SSB) resource sets) in which the UE is to collect measurements, such as for a certain amount of time. Then, the UE can report what it has measured to the network node (e.g. gNB), such as via Radio Resource Control(RRC) signaling. The training can be performed in the network node (e.g. gNB) itself, or in another node controlled by the network node (e.g. gNB) vendor such as an Over-the-Top (OTT) server handled by the network node vendor.

[0029] A similar approach can apply for the case in which the 0AM does the NW-side training. In this case, the 0AM may request the network node (e.g. gNB) to provide to the UE a certain configuration according to which the UE is to perform certain measurements, and collect data. Once the data collection is completed, the UE can transfer the collected data to the 0AM, e.g. using the Minimization of Drive Tests (MDT) framework such as the immediate MDT or the logged MDT.

[0030] From an operation point of view, performing data collection implies that the UE logs the data intended for the NW-side model training, and stores them in the local memory. Since this type of data does not have any stringent latency requirement, it is beneficial for the UE and for the network (e.g. in terms of UE power consumption, or spectral efficiency) if the UE can log the measured data (e.g. the beam, cell, and / or frequency level qualities), and transmit that data at a later point in time, rather than transmitting the data immediately upon performing the corresponding measurement (as it is, for example, for conventional Layer 1 (LI) measurements, which are transmitted on Uplink Control Information (UCI)). This reduces the power consumed by the UE to continuously access the channel to transmit data that does not have stringent latency requirements, and also reduces the impact on the spectral efficiency, which instead can be used for transmission of data that has a higher priority or more stringent latency requirements.

[0031] The logged LI measurements (or beam level measurements) can be transmitted via RRC signaling (e.g. periodically, or based on events, or upon network request). The logging of measurements can imply that the UE is to send this logged data in multiple RRC messages, particularly in case the logged data is larger in size than the maximum supported size of a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) that conveys the RRC message. In some cases, all the data logged while connected to a certain network node (e.g. gNB) can be transmitted to such a network node (e.g. gNB) prior to performing a mobility procedure, and some other data (e.g. the data not yet transmitted) can be transmitted later to the target network node (e.g. gNB).

[0032] The need to collect data from the UE to support AI / ML training for a NW-sided model has been identified to support Al-based optimizations (e.g. positioning, beam management, and CSI enhancements). An efficient data collection framework lends itself to a careful consideration to reduce the cost of data collection as well as processing, training, etc.In particular, the need to collect data periodically or upon fulfillment of events may enable a more efficient data collection framework for the AI / ML. However, it is not clearly indicated which events are to be supported, and how to support them. In light of the above, the following has been agreed in the RAN2#127bis.

[0033] There is the possibility of a method at a UE for enabling the data collection from a UE using a Layer 3 (L3) reporting configuration for at least one AI / ML model associated with / to a functionality based on an LI measurement configuration. The method is focused merely on defining the LI measurement configuration without discussing the data collection characteristics. There is also the possibility of a method to “report” the logged data under certain triggering events. The issue of logging the data for the AI / ML use cases under certain conditions has not been addressed.

[0034] As mentioned earlier, one challenge that remains unresolved is in relation to when (and how) to trigger data collection or, more particularly when (and based on what condition or event) to trigger logging the LI measurement data collection at the UE without data collection being impaired with the fluctuations of the LI measurements in particular in case of event-based data collection. In other words, the LI data collection for the AI / ML purpose becomes more important as the fluctuations of the LI measurements may negatively impair the data collection process when it comes to the event triggered data collection. For example, if the UE is configured to collect the LI data based on an LI measurement threshold (e.g. when the LI measurement goes below a certain threshold) the LI rapid fluctuation of the LI measurements may not allow the UE to collect proper measurements which is of interest for the network.

[0035] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0036] There are disclosed herein improved methods for managing data collection. The data referred to herein can comprise one or more measurements (e.g. one or more CSI measurements). Thus, herein, the terms “data” and “measurement(s)” may be used interchangeably.

[0037] Fig. 1 depicts a first method in accordance with particular embodiments. The first method may be performed by a UE or wireless device (e.g. the UE 312 or UE 400 as described later with reference to Figs. 3 and 4 respectively). The first method is for managing data collection. The first method begins at step 102 with receiving, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE. At step 104, the first method comprises performing the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0038] The second layer may be a higher layer than the first layer. The first layer may be a physical layer or Layer 1 (LI). The second layer may be a Radio Resource Control (RRC) layer or Layer 3 (L3).

[0039] It may be that receiving the one or more conditions from the network node comprises receiving a first configuration from the network node. The first configuration may comprise the one or more conditions.

[0040] Although not illustrated in Fig. 1, the first method may comprise monitoring the second layer to determine whether the second layer fulfils the one or more conditions.

[0041] Although not illustrated in Fig. 1, the first method may comprise performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions for a first predefined length of time.

[0042] The one or more conditions may be indicative of a radio link quality measured in a cell in which the data collection is started or stopped. The one or more conditions may comprise any one or more of: a condition that a first parameter indicative of a radio link quality of a Synchronization Signal Block (SSB) configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a Channel State Information Reference Signal (CSR-RS) configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold. Any one or more of the first parameter, the second parameter, and the third parameter may comprise any one or more of: a Reference Signal Received Power (RSRP); a Reference Signal Received Quality (RSRQ); aSignal-to-Interference-plus-Noise Ratio (SINR); and a Reference Signal Strength Indicator (RSSR).

[0043] The one or more conditions may comprise one or more first conditions, and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions may comprise starting the data collection when the second layer fulfils the one or more first conditions. It may be that starting the data collection comprises logging one or more measurement results in a memory of the UE. It may be that starting the data collection comprises starting the data collection for a first time, or starting the data collection for a subsequent time (i.e. resuming the data collection). It may be that performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises stopping the data collection when the second layer no longer fulfils the one or more first conditions.

[0044] The one or more conditions may comprise one or more second conditions, and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions may comprise stopping the data collection when the second layer fulfils the one or more second conditions. It may be that stopping the data collection comprises stopping logging one or more measurement results in a memory of the UE. It may be that stopping the data collection comprises stopping the data collection permanently (i.e. terminating the data collection), or stopping the data collection temporarily (i.e. pausing the data collection).

[0045] Although not illustrated in Fig. 1, the first method may comprise performing the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions. The one or more third conditions comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of an SSB configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a CSR-RS configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold. Any one or more of the fourth parameter, the fifth parameter, and the sixth parameter may comprise any one or more of: an RSRP; an RSRQ; an SINR; and an RSSR.

[0046] Although not illustrated in Fig. 1, the first method may comprise performing the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.

[0047] Although not illustrated in Fig. 1, the first method may comprise transmitting the data to the network node in response to a request from the network node.

[0048] The data may be for training an artificial intelligence or machine learning (AI / ML) model. The first configuration may be associated with the AI / ML model.

[0049] Fig. 2 depicts a second method in accordance with particular embodiments. The second method may be performed by a network node (e.g. the network node 310 or network node 500 as described later with reference to Figs. 3 and 5 respectively). The second method is for managing data collection at a UE. The second method begins at step 202 with transmitting, to the UE, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE. The one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions. The second layer is a different layer from the first layer.

[0050] The second layer may be a higher layer than the first layer. The first layer may be a physical layer or L 1. The second layer may be an RRC layer or L3.

[0051] It may be that transmitting the one or more conditions to the UE comprises transmitting a first configuration to the UE. The first configuration may comprise the one or more conditions.

[0052] The one or more conditions may trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions for a first predefined length of time. The one or more conditions may be indicative of a radio link quality measured in a cell in which the data collection is started or stopped. The one or more conditions comprise any one or more of a condition that a first parameter indicative of a radio link quality of an SSB configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a CSR-RS configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold. Any one or more of the first parameter, the second parameter, and the third parameter may comprise any one or more of an RSRP; an RSRQ; an SINR; and an RSSR.

[0053] It may be that the one or more conditions comprise one or more first conditions, and the one or more conditions may trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by triggering the UE to start the data collection when the second layer fulfils the one or more first conditions. It may be that starting the data collection comprises logging one or more measurement results in a memoryof the UE. It may be that starting the data collection comprises starting the data collection for a first time, or starting the data collection for a subsequent time (i.e. resuming the data collection). The one or more conditions may trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by triggering the UE to stop the data collection when the second layer no longer fulfils the one or more first conditions.

[0054] The one or more conditions may comprise one or more second conditions, and the one or more conditions may trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by triggering the UE to stop the data collection when the second layer fulfils the one or more second conditions. It may be that stopping the data collection comprises stopping logging one or more measurement results in a memory of the UE. It may be that stopping the data collection comprises stopping the data collection permanently (i.e. terminating the data collection), or stopping the data collection temporarily (i.e. pausing the data collection).

[0055] Although not illustrated in Fig. 2, the second method may comprise triggering the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions. The one or more third conditions may comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of an SSB configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a CSR-RS configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold. Any one or more of the fourth parameter, the fifth parameter, and the sixth parameter may comprise any one or more of: an RSRP; an RSRQ; an SINR; and an RS SR. The one or more third conditions may trigger the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.

[0056] Although not illustrated in Fig. 2, the second method may comprise receiving the data from the UE in response to transmitting a request to the UE.

[0057] The data may be for training an artificial intelligence or machine learning, AI / ML, model. The first configuration may be associated with the AI / ML model.

[0058] Any reference herein to a parameter that meets a threshold can, for example, mean the parameter is above (i.e. greater than), below (i.e. less than), or equal to the threshold.

[0059] Thus, there are disclosed herein improved methods for managing data collection. More specifically, there are disclosed herein methods comprising using L3 measurements to trigger LI data collection, e.g. for an AI / ML model training.

[0060] In more detail, there is provided a method for the UE (or wireless terminal) to, for example:Monitor the fulfilment of a first set of one or more event(s) or threshold(s), wherein upon fulfillment of one or more events in the first set of event(s) or threshold(s), the UE may perform the following action: Start / pause / stop to log or store the AI / ML related LI related data or measurements for the LI parameters or resources included in a configuration.Transmit the logged data to the network, e.g. upon network request.

[0061] The first set of event(s) or threshold(s) may be based on any one or more of:1) An L3 radio link quality (e.g. any one or more of an L3 Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), and Reference Signal Strength Indicator (RS SR)) per one or more SSB reference signals;2) An L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RS SR) per one or more CSLRS reference signals;3) An L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) per one or more cells, such as one or more serving cells (e.g. any one or more of a primary cell (PCell), primary and secondary cell (PSCell), and secondary cell (SCell)) and / or one or more neighboring cells;4) Starting an L3 supervision timer upon fulfilment of configured conditions (e.g. T310, T312, beam failure detection timer) or upon an L3 supervision counter (e.g. N310, ), or Beam Failure Detection (BFd);5) An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more SSB reference signals;6) An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more CSLRS reference signals; and7) An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more cells, such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells.

[0062] Certain embodiments may provide one or more of the following technical advantage(s).

[0063] As described earlier, configuring the UE to perform event based LI data collection based on events associated with the Layer 1 measurement events might be inefficient due to rapid and abrupt fluctuations of the Layer 1 signal quality, e.g. the logging may be triggered upon instantaneous fulfilment of the event. The methods described herein allow the NW to collect the LI measurements for specific scenarios without impairment caused by the rapid fluctuation of the LI measurements.

[0064] The teachings of certain embodiments may improve the data rate, latency, and / or power consumption.

[0065] Herein, the terms “collected data” and “logged data” can be used interchangeably. They can refer to the operations at the UE for storing, in the UE memory, data associated with / to performed measurements. When transmitting the collected data to the network (e.g. a network node), the UE may transmit part(s) of the collected data, e.g. depending on the physical radio resources scheduled by the network. This means that part(s) of the collected data may remain in the UE memory, e.g. until they are transmitted.

[0066] There are provided methods for the network to configure the UE with triggering conditions to perform an action in relation to a data collection, such as to start, stop, pause, or terminate performing data collection. The data collection can be for training a model, e.g. for NW-side model training. The model may be an AI / ML model.

[0067] There are provided methods for the network to configure the UE with a measurement configuration for the UE to perform data collection. The configuration may be associated with / to one or more triggering events, thresholds, or conditions associated with / to higher layer measurements (e.g. Layer 3 measurements).

[0068] There are provided methods for the UE to start, stop, or pause performing lower layer (e.g. layer 1 measurements) data collection when one or more of the triggered triggering events, thresholds, or conditions are fulfilled.

[0069] Example procedure to start logging the LI measurements upon fulfilment of one or more configured event(s)

[0070] The is provided a method at a UE to start collecting, logging, or storing LI measurements upon fulfilment of one or more certain event(s) / threshold(s). The method may comprise any one or more of the following steps:

[0071] Step 1:

[0072] As described earlier with reference to step 102 of Fig. 1, the UE receives, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stackof the UE. For example, the UE (or UE device) may receive, from the network node, a first message comprising a first configuration including a data collection configuration. The data collection configuration may comprise:Optionally a measurement configuration that instructs the UE to perform, log, or collect measurements, such as measurements on one or more LI radio resources (e.g., reference signals), e.g. for AI / ML model training, o The UE can be configured with what lower layer (LI) measurements to log and / or how (e.g. periodic measurements, or event triggered), which may correspond to one or more parameters or resources for the UE to perform lower layer (e.g. Layer-1 (LI)) measurements.An event configuration with one or more triggering event(s) / thresholds(s) / condition(s) based on which the UE may perform an action in respect of the data collection such as start / suspend / stop the data collection. The event(s) / thresholds(s) / condition(s) can be based on one or more of the following higher layer measurements (e.g. L3 measurements) or lower layer measurements (e.g. LI measurements): o An L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RS SR) per one or more SSB reference signals; o An L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) per one or more CSLRS reference signals; o An L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) per one or more cell, such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells; o An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more SSB reference signals; o An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more CSLRS reference signals; and o An LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) per one or more cells, such as one or more serving cells (e.g. any one or more PCell, PSCell, and SCell) and / or one or more neighboring cells.Optionally, a configuration of a time period besides the one or more triggering event(s) / thresholds(s) / condition(s) based on which the UE may perform an action in respect of the data collection such as start / pause / stop / terminate the data collection. The data collection may be associated with / to one or more AI / ML models or functionalities.

[0073] Step 2:

[0074] As described earlier with reference to Fig. 1, the UE may monitor the second layer to determine whether the second layer fulfils the one or more conditions. For example, the UE (or UE device) may monitor one or more higher layer (e.g. L3) based event(s) / thresholds(s) / condition(s) configured for triggering collection or logging of lower layer (e.g. LI) measurements. The monitoring of the one or more event(s) / thresholds(s) / condition(s) may comprise any one or more of the following:• The measurement value(s) may be less or greater than the value(s) configured as part of the event(s) / thresholds(s) / condition(s). For example, any one or more of the following is possible: o The measured L3 radio link quality of the one or more of the configured SSB reference signals is less or greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more SSB reference signals received as part of the configuration. o The measured L3 radio link quality of the one or more of the configured CSR-RS reference signals is less or greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more CSI-RS reference signals received as part of the configuration. o The measured L3 radio link quality of the one or more of the configured cells is less or greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells) received as part of the configuration. o The measured LI radio link quality of the one or more of the configured SSB reference signals is less or greater than the LI radiolink quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more SSB reference signals received as part of the configuration. o The measured LI radio link quality of the one or more of the configured CSLRS reference signals is less or greater than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more CSLRS reference signals received as part of the configuration. o The measured LI radio link quality of the one or more of the configured cells is less or greater than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RSSR) associated with / to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells) received as part of the configuration.The measurement value(s) may be greater than the value(s) configured as part of the first set of event(s) / thresholds(s) / condition(s) and less than the value(s) configured as part of the second set of event(s) / thresholds(s) / condition(s). For example, any one or more of the following is possible: o The measured L3 radio link quality of the one or more of the configured SSB reference signals is greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the first set of events related to the one or more SSB reference signals received as part of the configuration and is less than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the second set of events related to the one or more SSB reference signals received as part of the configuration. o The measured L3 radio link quality of the one or more of the configured CSLRS reference signals is greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RSSR) associated with / to the first set of events related to the one or more CSLRS reference signals received as part of the configurationand is less than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RS SR) associated with / to the second set of events related to the one or more CSI-RS reference signals received as part of the configuration. The measured L3 radio link quality of the one or more of the configured cells is greater than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RS SR) associated with / to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells) and is less than the L3 radio link quality (e.g. any one or more of an L3 RSRP, RSRQ, SINR, and RS SR) associated with / to the second set of events related to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells) received as part of the configuration. The measured LI radio link quality of the one or more of the configured SSB reference signals is greater than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the first set of events related to the one or more SSB reference signals received as part of the configuration and is less than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the second set of events related to the one or more SSB reference signals received as part of the configuration. The measured LI radio link quality of the one or more of the configured CSLRS reference signals is greater than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the first set of events related to the one or more CSLRS reference signals received as part of the configuration and is less than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the second set of events related to the one or more CSLRS reference signals received as part of the configuration.o The measured LI radio link quality of the one or more of the configured cells is greater than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells) and is less than the LI radio link quality (e.g. any one or more of an LI RSRP, RSRQ, SINR, and RS SR) associated with / to the second set of events related to the one or more cells (such as one or more serving cells (e.g. any one or more of a PCell, PSCell, and SCell) and / or one or more neighboring cells received as part of the configuration.

[0075] Any of the embodiments described herein may, for example, require that the inequality condition(s) (e.g. the condition(s) that one or more measurements are less than or greater than a threshold, or that one or more measurements are less than a first set of one or more thresholds and greater than a second set of one or more thresholds) are to persist (i.e. event is fulfilled) for a time period configured beside the event(s) / thresholds(s) / condition(s).

[0076] The UE may, for example, start a supervision timer upon first fulfilment of the configured event(s) / thresholds(s) / condition(s) and may start collecting the lower layer data and / or measurement s) if the event(s) / thresholds(s) / condition(s) are fulfilled while (e.g. for the entire time) the supervision timer is running.

[0077] In another example, the UE may start a supervision timer upon first fulfillment of the configured event(s) / threshold(s) / condition(s) and may start collecting the lower layer data and / or measurement(s) if a certain number of samples fulfill the event(s) / threshold(s) / condition(s) while (e.g. for the entire time) the supervision timer is running. The number of samples can be configured by the network (e.g. the network node) or defined in a specification. Upon a certain number of samples fulfilling the configured event(s) / threshold(s) / condition(s), the UE may stop the supervision timer and start collecting the lower layer data and / or measurements.

[0078] Any of the embodiments described herein may, for example, require that an average value of the measurement(s) collected in a time interval configured beside the event(s) / thresholds(s) / condition(s) fulfils the inequality condition(s).

[0079] Step 3:

[0080] As described earlier with reference to step 104 of Fig. 1, the UE performs the one or more actions to control the data collection based on whether a second layer of the networkprotocol stack fulfils the one or more conditions. For example, the UE (or UE device) may start to collect or log lower layer data (e.g. one or more lower layer measurements, e.g. one or more lower layer CSI measurements) upon fulfilment of the one or more event(s) / thresholds(s) / condition(s). The lower layer data may comprise any one or more of:• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on the transmitted CSI-RS beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on the transmitted SSB beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on a certain set of the transmitted CSI-RS beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on a certain set of the transmitted SSB beams.

[0081] The UE (or UE device) may stop / pause / terminate the data collection process upon fulfilment of the one or more event(s) / thresholds(s) / condition(s) optionally fulfilled for a period of time.

[0082] Step 4:

[0083] As described earlier with reference to step 104 of Fig. 1, the UE performs the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions. For example, the UE (or UE device) may start to collect or log lower layer data (e.g. one or more lower layer measurements, e.g. one or more lower layer CSI measurements) upon fulfilment of the one or more event(s) / thresholds(s) / condition(s). The lower layer data may comprise any one or more of:• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on the transmitted CSI-RS beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on the transmitted SSB beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on a certain set of the transmitted CSI-RS beams.• Radio link measurements (e.g. any one or more of RSRP, RSRQ, SINR, and RSSR, etc.) on a certain set of the transmitted SSB beams.

[0084] The following embodiments are also provided, which may be performed by a UE or wireless device (e.g. the UE 312 or UE 400 as described later with reference to Figs. 3 and 4 respectively):Al . A method performed by the wireless terminal (so-called the UE) for triggering the data collection process for AI / ML model training, the method comprising:• receiving a first configuration associated to at least one AI / ML model / functionality, wherein the first configuration comprises a first set of one or more triggering events / thresholds / conditions associated to higher layers (e.g., layer-3) to be monitored by the UE to start performing the said data collection procedure wherein at least a part of the data is to be collected from the lower layers (Layer 1),• monitoring the fulfillment of the first set of one or more triggering events / thresholds / conditions based on the higher layers (e.g., Layer 3) measurements;• starting to perform data collection from lower layers (e.g., Layer 1) for AI / ML model training upon fulfillment of the one or more of the triggering conditions received as part of the first configuration.A2. A method of Al comprising the UE stopping, aborting, suspending or pausing lower layer (Layer 1) data collection when the first set of one or more triggering events / thresholds / conditions stops being fulfilled and / or when a second set of triggering conditions for stopping or pausing the data collection.A3. A method of A2 wherein the second set of triggering events / thresholds / conditions are equal or different from the first set of the triggering events / threshold / conditions.A4. A method of Al, A2, A3 wherein the first or second set of triggering events / thresholds / conditions are based on one or more of the following measurements o Layer 3 radio link quality such as L3 RSRP, RSRQ, SINR per one or more SSB reference signals o Layer 3 radio link quality such as L3 RSRP, RSRQ, SINR per one or more CSLRS reference signalso Layer 3 radio link quality such as L3 RSRP, RSRQ, SINR per one or more cell such as serving cell (PCell, PSCell, SCell ) or neighboring cells o Layer 1 radio link quality such as LI RSRP, RSRQ, SINR per one or more SSB reference signals o Layer 1 radio link quality such as LI RSRP, RSRQ, SINR per one or more CSLRS reference signals o Layer 1 radio link quality such as LI RSRP, RSRQ, SINR per cell such as serving cell (PCell, PSCell, SCell) or neighboring cellsA5. A method of Al, A2, A3, A4 where the UE monitors the first or second set of triggering events / thresholds / conditions for a certain supervision timer duration before starting / stopping / pausing / aborting data collection.A6. A method of A5 where UE considers a certain number of samples fulfilling the first or second set of triggering events / thresholds / conditions for a certain supervision timer duration before starting / stopping / pausing / aborting data collection.A7. A method of A6 where the UE stops supervision timer upon certain number of samples fulfilling the first or second set of triggering events / thresholds / conditions.A8. A method of Al comprising the UE stopping, aborting, suspending or pausing data collection upon reception of a message / request from the Network node.A9. A method of Al wherein the UE transmits a first indication to the network upon fulfillment of the one or more of the triggering conditions in a first set.A10. A method of A5, wherein the first indication indicates that the UE has started performing data collection or data collection is going to start, for the associated AIML model / functionality.Al 1. A method of A5, wherein the first indication indicates that the UE first set of events / thresholds / conditions is fulfilled and further include information about the condition being fulfilled e.g. one or more higher layer measurements per cell and / or beam and / or CSI-RS resource and / or S SB of a cell, etc.Al 2. A method of A5, wherein the first indication is transmitted to the network and, in response to that, the UE receives an activation command (e.g. an RRC message including one or more parameters or a Medium Access Control Element (MAC CE)) based on which the UE starts data collection for AI / ML model training.A 13. A method of Al, wherein the UE transmits a second indication to the network upon fulfillment of one or more second triggering events / thresholds / conditions (and / or when the first condition stops being fulfilled).Al 4. A method of Al, wherein the UE logs (stores e.g. in a UE variable) information related to the first triggering events / thresholds / conditions upon fulfillment of the first triggering events / thresholds / conditions e.g. while an event / threshold / condition is fulfilled.Al 5. A method of Al l, wherein the UE further indicates to the network an availability of the information stored, and in response the UE may receive a request to report the information, in response to which the UE transmit the one or more information which has logged about the triggering of the first event / threshold / condition.

[0085] There is also provided a method performed by a network node (e.g. the network node 310 or network node 500 as described later with reference to Figs. 3 and 5 respectively). The method can comprise any one or more of the steps described herein in respect of a network node. There is also provided a method performed by a system comprising any one or more of the steps described herein in respect of a UE and any one or more of the steps described herein in respect of a network node. There is also provided a system comprising a UE as described herein and a network node as described herein.

[0086] Fig. 3 shows an example of a communication system 300 in accordance with some embodiments.

[0087] In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). 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 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 telecommunication network 302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 302 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 nodes to implement one or more functionalities of any node in the telecommunication network 302, including one or more network nodes 310 and / or core network nodes 308.

[0088] 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 (RIC) (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 network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, 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 (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 O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0089] The network nodes 310 facilitate direct or indirect connection of user equipment (UE) (also referred to interchangeably herein as wireless device), such as by connecting UEs312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections. The network nodes 310 may be, for example, access points (APs) (e.g. radio access points), base stations (BSs) (e.g. radio base stations, Node Bs, evolved Node Bs (eNBs) and New Radio (NR) Node Bs (gNBs). Unless otherwise indicated, the term ‘network node’ as used herein refers to network nodes 310 and core network nodes 308.

[0090] 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 300 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 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0091] The UEs 312 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 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 312 and / or with other network nodes or equipment in the telecommunication network 302 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 302.

[0092] In the depicted example, the core network 306 connects the network nodes 310 to one or more host computing systems, such as host 316. 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 306 includes one more core network nodes (e.g., core network node 308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 308. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified DataManagement (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0093] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunication network 302. The host 316 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.

[0094] As a whole, the communication system 300 of Fig. 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other 2ndGeneration (2G), 3rdGeneration (3G), 4thGeneration (4G), 5thGeneration (5G) standards, or any applicable future generation standard (e.g. 6thGeneration (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0095] In some examples, the telecommunication network 302 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunications network 302 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 loT services to yet further UEs.

[0096] In some examples, the UEs 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. Additionally, a UE may be configured for operating in single- or multi- Radio Access Technology (RAT) ormulti-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC).

[0097] In the example, the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and / or 312d) and network nodes (e.g., network node 310b). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 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 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 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 314 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy Internet of Things (loT) devices.

[0098] The hub 314 may have a constant / persistent or intermittent connection to the network node 310b. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312c and / or 312d), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310b. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node310b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0099] Fig. 4 shows a UE 400 in accordance with some embodiments. The UE 400 presents additional details of some embodiments of the UE 312 of Fig. 3. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0100] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0101] The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 4. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0102] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructionsstored as machine-readable computer programs in the memory 410. The processing circuitry 402 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 402 may include multiple central processing units (CPUs). The processing circuitry 402 may be configured to cause the UE 402 to perform the methods as described with reference to Fig. 1, or any other methods described herein in respect of the UE.

[0103] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 400. 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.

[0104] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

[0105] The memory 410 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 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

[0106] The memory 410 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 Universal SIM (USIM) and / or Integrated SIM (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card’. The memory 410 may allow the UE 400 to access instructions, application programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0107] The processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may becoupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0108] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) or other Global Navigation Satellite System (GNSS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0109] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 412, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0110] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.[OHl] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT 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, asmoke 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. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 400 shown in Fig. 4.

[0112] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0113] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0114] Fig. 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR. NodeBs (gNBs)), Open-RAN (0-RAN) nodes or components of an 0-RAN node (e g., 0-RU, 0-DU, O-CU).

[0115] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, 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).

[0116] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0117] The network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 500 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB s. 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 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may beintegrated into the same or different chip or set of chips and other components within network node 500.

[0118] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 500 components, such as the memory 504, to provide network node 500 functionality. For example, the processing circuitry 502 may be configured to cause the network node to perform the methods as described with reference to Fig. 2, or any other methods described herein in respect of the network node.

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

[0120] The memory 504 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0121] The communication interface 506 is used in wired or wireless communication of signaling and / or data between network nodes, the access network, the core network, and / or UE.As illustrated, the communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0122] In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0123] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.

[0124] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any transmitting operations described herein as beingperformed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

[0126] Embodiments of the network node 500 may include additional components beyond those shown in Fig. 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500. In some embodiments providing a core network node, such as core network node 108 of FIG. 3, some components, such as the radio front-end circuitry 518 and the RF transceiver circuitry 512 may be omitted.

[0127] Fig. 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core networknode or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration (SMO) Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0128] Applications 602 (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.

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

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

[0131] In the context of NFV, a VM 608 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 608, and that part of hardware 604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 608 on top of the hardware 604 and corresponds to the application 602.

[0132] Hardware 604 may be implemented in a standalone network node with generic or specific components. Hardware 604 may implement some functions via virtualization. Alternatively, hardware 604 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 610, which, among others, oversees lifecycle management of applications 602. In some embodiments, hardware 604 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 612 which may alternatively be used for communication between hardware nodes and radio units.

[0133] Although the computing devices described herein (e.g., UEs, network nodes) 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.

[0134] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0135] Other embodiments of the present disclosure are defined in the following numbered statements:Group A EmbodimentsEmbodiment 1. A method performed by a user equipment, UE (e.g. the UE 312 or UE 400 as described later with reference to Figs. 3 and 4 respectively), for managing data collection, the method comprising: receiving, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE; and performing the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.Embodiment 2. The method of Embodiment 1, wherein: the second layer is a higher layer than the first layer.Embodiment 3. The method of Embodiment 1 or 2, wherein: the first layer is a physical layer or Layer 1, LI. the second layer is a Radio Resource Control, RRC, layer or Layer 3, L3.Embodiment 4. The method of any of the previous Embodiments, wherein: receiving the one or more conditions from the network node comprises: receiving a first configuration from the network node, wherein the first configuration comprises the one or more conditions.Embodiment 5. The method of any of the previous Embodiments, comprising: monitoring the second layer to determine whether the second layer fulfils the one or more conditions.Embodiment 6. The method of any of the previous Embodiments, comprising: performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions for a first predefined length of time.Embodiment 7. The method of any of the previous Embodiments, wherein: the one or more conditions comprise any one or more of: a condition that a first parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold.Embodiment 8. The method of Embodiment 7, wherein: any one or more of the first parameter, the second parameter, and the third parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.Embodiment 9. The method of any of the previous Embodiments, wherein: the one or more conditions comprise one or more first conditions; and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: starting the data collection when the second layer fulfils the one or more first conditions.Embodiment 10. The method of Embodiment 9, wherein: starting the data collection comprises: starting the data collection for a first time; starting the data collection for a subsequent time (i.e. resuming the data collection).Embodiment 11. The method of Embodiment 9 or 10, wherein: performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: stopping the data collection when the second layer no longer fulfils the one or more first conditions.Embodiment 12. The method of any of the previous Embodiments, wherein: the one or more conditions comprise one or more second conditions; and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: stopping the data collection when the second layer fulfils the one or more second conditions.Embodiment 13. The method of Embodiment 11 or 12, wherein: stopping the data collection comprises: stopping the data collection permanently (i.e. terminating the data collection); or stopping the data collection temporarily (i.e. pausing the data collection).Embodiment 14. The method of any of the previous Embodiments, comprising: performing the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions.Embodiment 15. The method of Embodiment 14, wherein: the one or more third conditions comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a ChannelState Information Reference Signal, CSR-RS, configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold.Embodiment 16. The method of Embodiment 15, wherein: any one or more of the fourth parameter, the fifth parameter, and the sixth parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.Embodiment 17. The method of any of Embodiments 14 to 16, comprising: performing the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.Embodiment 18. The method of any of the previous Embodiments, comprising: transmitting the data to the network node in response to a request from the network node.Embodiment 19. The method of any of the previous Embodiments, wherein: the data is for training an artificial intelligence or machine learning, AI / ML, model.Embodiment 20. The method of Embodiment 19, when directly or indirectly dependent on Embodiment 4, wherein: the first configuration is associated with the AI / ML model.Group B EmbodimentsEmbodiment 21. A method performed by a network node (e.g. the network node 310 or network node 500 as described later with reference to Figs. 3 and 5 respectively) for managing data collection at a user equipment, UE, the method comprising: transmitting, to the UE, one or more conditions for triggering the UE to perform one ormore actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE, wherein the one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.Embodiment 22. The method of Embodiment 21, wherein: the second layer is a higher layer than the first layer.Embodiment 23. The method of Embodiment 21 or 22, wherein: the first layer is a physical layer or Layer 1, LI. the second layer is a Radio Resource Control, RRC, layer or Layer 3, L3.Embodiment 24. The method of any of Embodiments 21 to 23, wherein: transmitting the one or more conditions to the UE comprises: transmitting a first configuration to the UE, wherein the first configuration comprises the one or more conditions.Embodiment 25. The method of any Embodiments 21 to 24, wherein: the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions for a first predefined length of time.Embodiment 26. The method of any of Embodiments 21 to 25, wherein: the one or more conditions comprise any one or more of: a condition that a first parameter indicative of a radio link quality of aSynchronization Signal Block, SSB, configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold.Embodiment 27. The method of Embodiment 26, wherein: any one or more of the first parameter, the second parameter, and the third parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.Embodiment 28. The method of any of Embodiments 21 to 27, wherein: the one or more conditions comprise one or more first conditions; and the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to start the data collection when the second layer fulfils the one or more first conditions.Embodiment 29. The method of Embodiment 28, wherein: starting the data collection comprises: starting the data collection for a first time; starting the data collection for a subsequent time (i.e. resuming the data collection).Embodiment 30. The method of Embodiment 28 or 29, wherein: the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to stop the data collection when the second layer no longer fulfils the one or more first conditions.Embodiment 31. The method of any of Embodiments 21 to 30, wherein: the one or more conditions comprise one or more second conditions; and the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to stop the data collection when the second layer fulfils the one or more second conditions.Embodiment 32. The method of Embodiment 30 or 31, wherein: stopping the data collection comprises: stopping the data collection permanently (i.e. terminating the data collection); or stopping the data collection temporarily (i.e. pausing the data collection).Embodiment 33. The method of any of Embodiments 21 to 32, comprising: triggering the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions.Embodiment 34. The method of Embodiment 33, wherein: the one or more third conditions comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold.Embodiment 35. The method of Embodiment 34, wherein: any one or more of the fourth parameter, the fifth parameter, and the sixth parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.Embodiment 36. The method of any of Embodiments 33 to 35, wherein: the one or more third conditions trigger the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.Embodiment 37. The method of any of Embodiments 21 to 36, comprising:receiving the data from the UE in response to transmitting a request to the UE.Embodiment 38. The method of any of Embodiments 21 to 37, wherein: the data is for training an artificial intelligence or machine learning, AI / ML, model.Embodiment 39. The method of Embodiment 38, when directly or indirectly dependent on Embodiment 24, wherein: the first configuration is associated with the AI / ML model.Group C EmbodimentsEmbodiment 40. A user equipment, UE, comprising processing circuitry configured to cause the UE to perform the method of any of the Group A embodiments.Embodiment 41. The UE of the previous embodiment, wherein the UE comprises at least one memory for storing instructions which, when executed by the processing circuitry, cause the UE to perform the method of any of the Group A embodiments.Embodiment 42. A network node comprising processing circuitry configured to cause the network node to perform the method of any of the Group B embodiments.Embodiment 43. The network node of the previous embodiment, wherein the network node comprises at least one memory for storing instructions which, when executed by the processing circuitry, cause the network node to perform the method of any of the Group B embodiments.Embodiment 44. A user equipment for managing data collection, comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.Embodiment 45. A network node for managing data collection, the network node comprising: processing circuitry configured to cause the network node to perform any of the stepsof any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.Embodiment 46. A user equipment (UE) for managing data collection, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.Group D EmbodimentsEmbodiment 47. A computer program comprising instructions which, when executed by processing circuitry of a user equipment, cause the user equipment to perform the method according to any of the Group A embodiments.Embodiment 48. A computer program comprising instructions which, when executed by processing circuitry of a network node, cause the network node to perform the method according to any of the Group B embodiments.Embodiment 49. A computer program product, embodied on a non-transitory machine- readable medium, comprising instructions which are executable by processing circuitry of a user equipment to cause the user equipment to perform the method according to any of the Group A embodiments.Embodiment 50. A computer program product, embodied on a non-transitory machine- readable medium, comprising instructions which are executable by processing circuitry of anetwork node to cause the network node to perform the method according to any of the Group B embodiments.

[0136] It should be noted that the above-mentioned embodiments illustrate rather than limit the idea, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.APPENDIX3GPP TSG-RAN WG2 #128 DocNumberOrlando, USA, 18th- 22ndNovember, 2024Agenda Item: 8.1.3Source: EricssonTitle: NW-side data collection for beam management and positioningDocument for: Discussion1 IntroductionThe discussion on the topic of NW-side data collection has progressed during the last RAN2 meetings. The discussion has focused on different technical aspects, such as when the UE should start / stop the NW-side data collection, how the UE should report the logged data, etc.In this paper, we addressed the FFSs captured in the meeting notes, and further details to be discussed in RAN2.2 Discussion on NW-side data collection for beam managementRelated to network side data collection, the following agreements were reached during the last RAN2#128 meeting.In the following, we further develop the expected technical impacts related to this topic, taking into account the above agreements and the online discussion during the last meeting.2.1 Configuration aspects and content of the data collection reportIn RAN2#127, it was agreed that when the network wants to perform NW-side data collection, it will transmit to the UE a measurement configuration for AI / ML-enabled features / FGs for data collection and logging of measurements. For the case of beam management, the NW may configure the UE with a specific set of CSI-RS / SSB resources specifically configured for training purposes. On such resources, the UE will then start performing layer-1 measurements and log the measurement results and any possible useful information associated to it.Going into more details on the necessary configuration, we know that from the point of view of the gNB, this set of CSI-RS / SSB resources used for training purposes may correspond to the set A and set B. However, unlike the case of UE-side data collection, the UE does not need to know that a certain resource set is a Set A or B, because that will be left to the NW implementation, and the UE just has to perform the same type of measurements in those sets of resources. The UE only needs to know that the purpose of this set of resources is to perform measurements for the purpose of NW-side data collection, rather than for conventional operations.RAN2 assumes that the radio resource configuration for the purpose of NW-side data collection consists of a set of CSI-RS / SSB resources on which the UE shall perform radio measurements and the related logging.Another aspect to be discussed is how to report the L1 measurements related to NW-side data collection purposes in case the UE does not support data logging. In this case in ourview, there is no motivation to support L3 reporting. The L3 reporting framework is very different from the L1 reporting framework in UCI, and if data logging cannot be supported by the UE, it does not make sense from a technical point of view to replicate the UCI framework over L3, also considering the high specification / design complexity.RAN2 assumes that if data logging is not supported by the UE, the L1 measurements results associated to the NW-side data collection are reported via UCI.Related to the content of the data collection report, in RAN2#127-bis, it was agreed that “at least L1-RSRPs and / or beam-IDs needs to be collected by UE”. In our view, along with such information, also the timestamp of the measurement might be beneficial, especially for the case of event-based measurements. The timestamp of a logged measurement is already included in the logged MDT report, as a tool to assist the network in retrieving NW operating conditions at the moment in which the measurement was taken by the UE. In the same way, in the context of Al ML, a timestamp would allow the network to correlate a given UE radio measurement with the NW conditions / configurations experienced at the network, which is critical to ensure a proper AIML model setup.Along with the L1-RSRP and beams IDs, the UE includes the timestamp related to the point in time in which a reported measurement was taken.However, all the above assumptions captured in 0, 0, 0 should be confirmed by RAN1.Ask RAN1 confirmation on the following topics, including any RAN2 related agreement: a. Radio resource configuration via CSI measurement framework for the purpose of NW-side data collection b. Reporting via UCI of the L1 measurements in case the data logging is not supported by the UE c. Content of the data collection report, including at least the L1-RSRPs, the associated measured beam IDs, the timestamp of the performed measurementA further topic discussed in RAN2#127 was on whether multiple configurations for NW-side data collection should be provided to the UE.On this regard, we first note that unlike the inference case, the data collection for NW-side model training does not have any reguirement on latency. Hence, whenever the network wants to configure the UE to perform radio measurements for the purpose of data collection in a different set of resources, the network can simply reconfigure the UE. Even if this reconfiguration causes a delay gap in the radio measurement, this is not a problem for the case of NW-side data collection. Hence, for the case of NW-side data collection, the NW cansimply de-configure the UE when data collection is no longer needed, and reconfigure it when needed, without the need for any activation / deactivation mechanism which would cost extra standardization effort.No need to introduce multiple configurations for NW-side data collection, and hence no need to introduce dynamic activation / deactivation mechanisms.2.2 When the UE should perform / stop the radio measurements for NW-side data collectionIn RAN2#127-bis, it was agreed that both periodic logging and event-triggered data logging will be supported.For the case of periodic logging, in our view, this means that the UE will start the data logging upon receiving the data collection configuration from the network.The UE starts the data collection upon receiving a L3 configuration for NW-side data collection.The logging periodicity as well as the logging duration can be configurable. In particular, related to the logging periodicity, that depends on the CSI-RS / SSB configuration which should be included as part of the CSI measurement configuration. Logging duration and logging periodicity can be considered both for the case of periodic data logging and event- triggered data logging.The logging periodicity / interval (for both periodic and event-triggered data collection) is given by the specific CSI measurement configuration.For the stopping of data collection, it was agreed in RAN2#127 that the data collection can be stopped once the UE faces issues such as becoming power limited. However, in general, the data collection, once started, can continue for a certain configurable time (as in logged MDT), for both the case of periodic and event triggered data collection; or it can continue until certain events are fulfilled, for the case of event-triggered data collection.Besides the case of memory limitation issues (already agreed in RAN2#127), UE stops the NW-side data collection procedure when: d. data collection has been done a certain configurable logging duration (as in logged MDT) e. the event that triggered the data collection is no longer fulfilled.Related to the event-triggered data collection, the triggering conditions were discussed in RAN2#127-bis. It was eventually agreed that “at least radio condition based event triggeredlogging will be supported”, and it is “FFS the details of radio condition based event”. In our view, it is kind of straightforward to assume that the measured level of L1-RSRP can be used as triggering condition, given the BM use case at hand. However, during the last meeting, it was argued that the L1-RSRP are not filtered (unlike the L3 measurements) and their values can fluctuate, so this may lead to the UE continuously starting and stopping the data collection. Given such considerations, RAN2 can discuss whether to consider alternative logging conditions. For example, the data logging can be anchored to the L3 measurements, i.e. when the L3 measurements drop above / below certain thresholds, the UE starts / stops logging the L1-RSRP, or to other L1 -driven events such as the UE starting T310 timers.A configurable level of the L1-RSRP is considered the baseline triggering condition for the UE to start / stop the NW-side data collection.RAN2 to consider the need to define alternative even-triggered conditions, such as based on the L3 filtered RSRP level, on the starting of T310 timer, etc.2.3 Design of the UElnformationResponse / Request framework for AIMLIn RAN2#127-bis, it was agreed that the UElnformationReguest / UEInformationResponse is used for on-demand reporting of AI / ML training data collection, and that an availability indication will be used by the UE signal the availability of collected data.The first issue to discuss is which SRB to use for the transmission of the UElnformationReguest / UEInformationResponse. The UElnformationReguest is already mapped to SRB1 , so in our view SRB1 can be reused. The UElnformationResponse is instead mapped to SRB1 or SRB2 (when logged measurement information is included).In legacy, the UElnformationReguest is mapped to SRB1 , and the UElnformationResponse is mapped to SRB1 or SRB2 (when logged measurement information is included).In last meeting, it was proposed that for the UElnformationResponse the SRB4 could be used. However, in our view this proposal is not very well motivated given that SRB4 is today used for Quality of Experience (QoE) which however uses a completely different data transmission mechanisms based on RRC segmentation, and not based on the “on-demand” framework that instead we have decided to adopt for the reporting of AIML collected data. On the other hand, SRB2 is used for the logged MDT that, as said, resembles very much the AIML use cases, both on the signalling mechanism (both based on “on-demand”) and on the prioritization (both logged MDT and AIML-related collected data can be assumed to have thesame priority from NW point of view).Hence, our preference is to reuse the SRB2, or a new SRB that can be assumed to be used for all the Al ML use cases from now on.The UElnformationRequest requesting AIML data is transmitted via SRB1 (as any other data request contained in such message), and the UElnformationResponse is transmitted via SRB2, or via a new defined SRB (to be used for all AIML use cases).Another FFS captured during the last meeting is the content of the UElnformationRequest / UEInformationResponse messages and the details of the availability indication.We first note that the UElnformationRequest / UEInformationResponse framework based on availability indication, is used also for retrieving SON and MDT-related reports. Hence, it is important to distinguish the signalling of the AIML-related use cases from the legacy use cases. This means that the availability indication should at least contain a reference to the type of data that are available for transmission, e.g. “NW-side collected data”, and in turn, the existing UElnformationRequest should be extended to include at least an indicator indicating that the gNB is requesting “NW-side collected data”.The availability indication transmitted by the UE should contain at least reference to the type of data that are available for transmission, and the UElnformationRequest should contain at least reference to the type of data that are requested, e.g. “AIML NW-side collected data”.How the availability indication is sent to the network is FFS. In our view, the network cannot always know when there are data available for transmission. This is particularly true for the event-triggered data collection. Additionally, the network cannot know if the UE has stopped the data collection, e.g. due to event-triggering conditions not being any longer fulfilled, or due to UE internal events such as UE memory becoming full. These are definitely information that the network should know as soon as possible, so that the network can start retrieving the data in order to free up the UE memory as soon as possible, thereby avoiding that the UE needs to skip the logging of some radio measurements. In our view, it is sufficient if the UE just signals to the network when it has stopped the data collection, so that the network can start retrieving the data.When the UE stops the data collection (e.g. due to fulfilling / unfulfilling of the event-triggered data collection, or UE internal conditions such as memory limitations), the UE informs the gNB about the availability of collected data.In legacy, the data availability indication is transmitted in any RRC complete message, such as RRCResumeComplete, RRCReconfigurationComplete, RRCReestablishmentComplete message. However, the classical SON / MDT reports are designed to be transmitted in gNBs different than the gNB in which the measurement was configured, or different from the gNB in which a certain event (such as RLF) occurred. For the BM use cases however we have not agreed yet on whether inter-gNB signalling for the transmission of AIML collected data is supported. Hence, as baseline we have to be assumed that the collected data should be at least transmitted to the gNB that configured the AIML NW-side data collection. This means that we cannot limit the transmission of the availability indication exclusively to the RRC complete messages that may be transmitted just sporadically when connected to a certain gNB. For this reason, we consider that as baseline the availability indication should be transmitted via UEAssistancelnformation.As baseline, the data availability indication is transmitted at least in the UEAssistancelnformation. Whether it can be transmitted also in RRC complete messages (as in SON / MDT) depends on the handling of collected data during mobility.2.3.1 How to handle the case of collected data exceeding single RRC message sizeIn RAN2#127, it was agreed that no standardized RRC segmentation procedure is needed, as for the logged MDT measurements. The UE implementation can determine how many entries to include in the list radio measurements information, such that the maximum PDCP SDU size is not exceeded.Then, with this agreement in place, RAN2 just need to discuss how to transmit the collected AIML data that could not fit into a single RRC message. Again, we can get some inspiration from the logged MDT and foresee the following options:• In each transmitted RRC message, the UE indicates to the gNB that there are still collected data available for transmission, and then the gNB further reguests the UE to transmit the next RRC message (via UElnformationReguest / Response); or• Once the gNB reguests the UE to transmit the AIML collected data, the UE continues the transmission of a certain amount of samples (as indicated by the gNB in the UElnformationReguest) in the following RRC UElnformationResponse messages. In such case, it would be useful for the network to get to know how many data are stored / left for transmission so that the gNB can allocate the necessary resources anddecide when to fetch those data and how many data (e.g. taking into account cell load).• Once the gNB requests the UE to transmit the AIML collected data, the UE continues the transmission of all the remaining samples in following RRC UElnformationResponse messages without any further request from the gNB. Also in such case, it would be useful for the network to get to know how many data are stored / left for transmission so that the gNB can allocate the necessary resources and decide when / whether to fetch those data taking into account cell load.In case all the collected data do not fit into a single RRC message, RAN2 to discuss the following options: f. In each transmitted RRC message, the UE indicates to the gNB that there are still collected data available for transmission, and then the gNB further reguests the UE to transmit the next RRC message (via UElnformationReguest / Response) (similar to logged MPT). g. The gNB indicates (i.e. in the UElnformationReguest) the amount of collected data the UE should transmit in the following RRC UElnformationResponse messages, or the amount of RRC UElnformationResponse messages the UE should transmit, without any further reguest from the gNB. h. The gNB indicates (i.e. in the UElnformationReguest) that all the remaining collected data should be transmitted by the UE in the following RRC UElnformationResponse messages without any further reguest from the gNB.As said above, in order to facilitate the gNB decisions of whether to fetch or postpone the fetching of the data, it would be beneficial if the UE could indicate as part of the availability indication, how many data the UE has collected or how many RRC messages are expected to be transmitted.The UE indicates in the availability indication how many data or RRC samples are available for transmission.2.4 UE memory capabilitiesDuring the last RAN2 meeting, we have agreed that the UE stores the logged training data at AS layer with a minimum AS layer memory size supported by the UE. FFS on the memory size. Before discussing the minimum value of the memory size, we propose waiting for more RAN1 inputs related to the data that the UE could log and report to the gNB, so that RAN2can do a more thorough analysis of such minimum requirement. Additionally, in our view if the UE supports more memory than this minimum memory size, that should be indicated by the UE.RAN2 to wait RAN1 inputs on the type of data to be logged by the UE, before discussing the minimum memory size for storing collected data.Define in a UE capability some different minimum memory values that a UE can support for the logging of collected data.2.5 Handling of collected data during mobilitySeveral contributions submitted to the last RAN2#127-bis meeting addressed the handling of AIML collected data during mobility. The discussion so far as mainly focused on aspects related to how to configure / start / stop the data collection, and how to report the collected data. It is the natural next step to start discussing what happens at the data collected but not yet transmitted, when certain mobility-related events occur, e.g. a handover is executed, or an RLF / HOF is detected, or an RRC state transition is performed. In our view, there are mainly two alternatives:1 . The UE discards / clears the collected data when performing a mobility procedure2. The UE retains the collected data, and possibly transmit them to a different node than the node configuring the data collection (e.g. the target gNB of the Handover (HO), or the gNB to which the UE reconnects / reestablishes after an RLF)Needless to say, that the option 2 above is certainly preferrable from a technical point of view, because it allows the source gNB to retrieve all the collected data, and it allows to fully capitalize on the reference signals transmitted for the data collection purpose, and on the power spent by the UE. However, the standardization effort of the option 2 should be also assessed in relationship to the time left for this Rel.19 Wl.For example, if option 2 is pursued, RAN2 should first discuss whether the data retaining should be supported in all mobility cases or only in some cases, e.g. the retaining of the data may be supported only in case of HO, whereas in case of RLF the UE may discard all the data. Then, it should be discussed how the UE is informed on whether it is allowed or not allowed to transmit the AIML collected data to another gNB, e.g the target gNB of the HO. Allowing the UE to always transmit the retained data to a target gNB may not be desirable considering that the target node could be of another vendor.Finally, since the node retrieving the data should transmit the collected data to the source gNB, some work on the Xn interface might be needed, and as such RAN3 involvement.Given the above considerations, we propose for simplicity to limit the scope of this discussion for Rel.19.For Rel.19, as baseline, RAN2 assumes that the UE discards / clears the AIML collected data at mobility events (e.g. handover to a different gNB than the source gNB, RLF / HOF, RRC state transitions).Nevertheless, if there is a strong preference to pursue optimizations in this area, we propose addressing the following aspects.If it is agreed to enable the UE to retain the AIML collected data at mobility events, RAN2 to discuss the following: i. Whether the retaining of the data should be supported for all mobility-related events, i.e. HO, RLF, RRC state transitions. j. How the UE is informed on whether it should retain the data or not when executing the mobility-related event. k. Consider Xn impact and RAN3 involvement2.6 OAM-centric data collectionFor the OAM-centric data collection, the RAN2 impact is guite limited. This is because the agreements reached so far are also suitable for the OAM-centric use cases. However, there might be more specific OAM-related aspects that should be addressed by RAN3 and SA5. For example, SA5 should consider whether to introduce other Mx measurement for the specific BM use cases. Additionally, RAN3 / SA5 could consider whether to enhance the management MDT for the selection of the UEs to perform the data collection.RAN2 can start by indicating the agreements reached so far by RAN2 on this topic, and ask RAN3 / SA5 to consider these agreements for their work.RAN2 to send a Liaison Statement (LS) to RAN3 / SA5 to indicate the agreements reached so far by RAN2 on the topic of NW-side data collection, and ask them to consider such agreements in their work.3 Discussion on NW-side data collection for positioningNetwork-side data collection for positioning occurs in the following network-based positioning methods:• Case 3a: NG-RAN node assisted / Location Management Function (LMF)-based positioning with gNB side model (direct positioning)• Case 3b: NG-RAN node assisted / LMF-based positioning with LMF-side model (assisted positioning)Case 3a and Case 3b both are based on Uplink (UL) measurements performed at the gNB and share similar flows as the legacy Uplink-Time Difference of Arrival (UL-TDOA) positioning method. As such the impact is primarily in RAN3 domain New Radio Positioning Protocol A (NRPPa).The main impact in terms of RAN2 is the RRC configuration for Sounding Reference Signal (SRS) which can follow the legacy mechanism. However, one additional aspect to consider is that for AI / ML model both measurements and label are needed. For the training, the necessary information is the gNB measurements (Relative Time of Arrival (RTOA)) and the label / ground truth is UE location or true RTOA. The LMF would have to configure the reporting of UE location coinciding the SRS transmission periodicity. The gNB for the case 3a can also obtain the UE location using RRC; that is there would be no requirement of having an LTE Positioning Protocol (LPP) session. This is already possible in legacy as below for MDT.— CommonLocationlnfoThe IE CommonLocationlnfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information.CommonLocationlnfo information element— ASN1 START— TAG-COMMONLOCAT IONINFO- STARTCommonLocationlnf o-rl 6 : : = SEQUENCE { gnss -TOD-msec-rl 6 OCTET STRING OPTIONAL ,locationTimestamp-rl 6 OCTET STRING OPTIONAL , locationCoordinate-rl 6 OCTET STRING OPTIONAL , locationError-rl 6 OCTET STRING OPTIONAL , locationSource-rl 6 OCTET STRING OPTIONAL , velocityEstimate-rl 6 OCTET STRING OPT IONAL }— TAG-COMMONLOCAT IONINFO-STOP— ASN1STOPUE sending ground truth UE location coordinate to gNB via RRC is more efficient compared to sending it first to LMF which further forwarding to gNB, especially when UE is requested to send updated location coordinate when moving.Fig. 7 is a signalling diagram illustrating an exchange of signals in accordance with an embodiment. As illustrated by arrow 704 of Fig. 7, the gNB 702 transmits an SRSconfiguration to the UE 700, and thus the UE 700 receives the SRS configuration from the gNB 702. As illustrated by arrow 706 of Fig. 7, the gNB 702 transmits, to the UE 700, a UE location reporting configuration (using an RRC reconfiguration), and thus the UE 700 receives the location reporting configuration from the gNB 702. As illustrated by block 708 of Fig. 7, the UE 700 transmits an SRS. As illustrated by arrow 710 of Fig. 7, the UE 700 provides, to the gNB 702, the current UE location during the SRS transmission occasion and thus the gNB 702 receives the current UE location from the UE 700. As illustrated by block 712 of Fig. 7, the gNB 702 performs measurements and obtains UE location (as labels) from the UE.Case 3a / 3b NW side data collection should be driven by RAN3 as it has primarily NRPPa impact. The main impact on RAN2 can be to align the gNB measurements and UE reporting of ground truth during training.UE sending ground truth UE location coordinate directly to gNB via RRC is an efficient way to support gNB-side data collection.A window to report UE ground truth coinciding with SRS transmission periodicity is configured.UE sends ground truth UE location coordinate to gNB via RRC for gNB-side data collection.4 ConclusionIn the previous sections we made the following observations:Observation 1 In legacy, the UElnformationReguest is mapped to SRB1 , and the UElnformationResponse is mapped to SRB1 or SRB2 (when logged measurement information is included).Observation 2 Case 3a / 3b NW side data collection should be driven by RAN3 as it has primarily NRPPa impact. The main impact on RAN2 can be to align the gNB measurements and UE reporting of ground truth during training.Observation 3 UE sending ground truth UE location coordinate directly to gNB via RRC is an efficient way to support gNB-side data collection.Based on the discussion in the previous sections we propose the following:Proposal 1 RAN2 assumes that the radio resource configuration for the purpose ofNW-side data collection consists of a set of CSI-RS / SSB resources in which the UE shall perform radio measurements and optionally loggingProposal 2 RAN2 assumes that if data logging is not supported by the UE, the L1 measurements results associated to the NW-side data collection are reported via UCI.Proposal 3 Along with the L1-RSRP and beams IDs, the UE includes the timestamp related to the point in time in which a reported measurement was taken.Proposal 4 Ask RAN1 confirmation on the following topics, including any RAN2 related agreement: a. Radio resource configuration via CSI measurement framework for the purpose of NW-side data collection b. Reporting via UCI of the L1 measurements in case the data logging is not supported by the UE c. Content of the data collection report, including at least the L1-RSRPs, the associated measured beam IDs, the timestamp of the performed measurementProposal 5 No need to introduce multiple configurations for NW-side data collection, and hence no need to introduce dynamic activation / deactivation mechanisms.Proposal 6 The UE starts the data collection upon receiving a L3 configuration for NW- side data collection.Proposal 7 The logging periodicity / interval (for both periodic and event-triggered data collection) is given by the specific CSI measurement configuration.Proposal 8 Besides the case of memory limitation issues (already agreed inRAN2#127), RAN2 to consider the following additional mechanisms for the stopping of the NW-side data collection procedure: a. The UE continues data collection for a certain configurable logging duration (as in logged MPT)b. The UE continues data collection until the event that triggered the data collection is fulfilled.Proposal 9 A configurable level of the L1-RSRP is considered the baseline triggering condition for the UE to start / stop the NW-side data collection.Proposal 10 RAN2 to consider the need to define alternative logging conditions, such as the L3 filtered RSRP level, the starting of T310 timer, etc.Proposal 11 The UElnformationReguest reguesting AIML data is transmitted via SRB1(as any other data reguest contained in such message), and theUElnformationResponse is transmitted via SRB2, or via a new definedSRB (to be used for all AIML use cases).Proposal 12 The availability indication transmitted by the UE should contain at least reference to the type of data that are available for transmission, and the UElnformationReguest should contain at least reference to the type of data that are reguested, e.g. “AIML NW-side collected data”.Proposal 13 When the UE stops the data collection (e.g. due to fulfilling / unfulfilling of the event-triggered data collection, or UE internal conditions such as memory limitations), the UE informs the gNB about the availability of collected data.Proposal 14 As baseline, the data availability indication is transmitted at least in theUEAssistancelnformation. Whether it can be transmitted also in RRC complete messages (as in SON / MDT) depends on the handling of collected data during mobility.Proposal 15 In case all the collected data do not fit into a single RRC message, RAN2 to discuss the following options: a. In each transmitted RRC message, the UE indicates to the gNB that there are still collected data available for transmission, and then the gNB further reguests the UE to transmit the next RRC message (viaUElnformationReguest / Response) (similar to logged MDT). b. The gNB indicates (i.e. in the UElnformationReguest) the amount of collected data the UE should transmit in the following RRCUElnformationResponse messages, or the amount of RRCUElnformationResponse messages the UE should transmit, without any further reguest from the gNB.The qNB indicates (i.e. in the UElnformationRequest) that all the remaining collected data should be transmitted by the UE in the following RRC UElnformationResponse messages without any further request from the qNB.Proposal 16 The UE indicates in the availability indication how many data or RRC samples are available for transmission.Proposal 17 RAN2 to wait RAN1 inputs on the type of data to be logged by the UE, before discussing the minimum memory size for storing collected data.Proposal 18 Define in a UE capability some different minimum memory values that aUE can support for the logging of collected data.Proposal 19 For Rel.19, as baseline, RAN2 assumes that the UE discards / clears theAIML collected data at mobility events (e.q. handover to a different qNB than the source qNB, RLF / HOF, RRC state transitions).Proposal 20 If it is agreed to enable the UE to retain the AIML collected data at mobility events, RAN2 to discuss the following: a. Whether the retaining of the data should be supported for all mobility- related events, i.e. HO, RLF, RRC state transitions. b. How the UE is informed on whether it should retain the data or not when executing the mobility-related event. c. Consider Xn impact and RAN3 involvementProposal 21 RAN2 to send an LS to RAN3 / SA5 to indicate the agreements reached so far by RAN2 on the topic of NW-side data collection, and ask them to consider such agreements in their work.Proposal 22 A window to report UE ground truth coinciding with SRS transmission periodicity is configured.Proposal 23 UE sends ground truth UE location coordinate to qNB via RRC for qNB- side data collection.

Claims

CLAIMS1. A method performed by a user equipment, UE, for managing data collection, the method comprising: receiving, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE; and performing the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.

2. The method of claim 1, wherein: the second layer is a higher layer than the first layer.

3. The method of claim 1 or 2, wherein: the first layer is a physical layer or Layer 1, LI. the second layer is a Radio Resource Control, RRC, layer or Layer 3, L3.

4. The method of any of the previous claims, wherein: receiving the one or more conditions from the network node comprises: receiving a first configuration from the network node, wherein the first configuration comprises the one or more conditions.

5. The method of any of the previous claims, comprising: performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions for a first predefined length of time.

6. The method of any of the previous claims, wherein: the one or more conditions are indicative of a radio link quality measured in a cell in which the data collection is started or stopped.

7. The method of any of the previous claims, wherein: the one or more conditions comprise any one or more of: a condition that a first parameter indicative of a radio link quality of aSynchronization Signal Block, SSB, configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold.

8. The method of claim 7, wherein: any one or more of the first parameter, the second parameter, and the third parameter comprise any one or more of a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.

9. The method of any of the previous claims, wherein: the one or more conditions comprise one or more first conditions; and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: starting the data collection when the second layer fulfils the one or more first conditions.

10. The method of claim 9, wherein: starting the data collection comprises logging one or more measurement results in a memory of the UE.

11. The method of claim 9 or 10, wherein: performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: stopping the data collection when the second layer no longer fulfils the one or more first conditions.

12. The method of any of the previous claims, wherein:the one or more conditions comprise one or more second conditions; and performing the one or more actions to control the data collection based on whether the second layer fulfils the one or more conditions comprises: stopping the data collection when the second layer fulfils the one or more second conditions.

13. The method of claim 11 or 12, wherein: stopping the data collection comprises stopping logging one or more measurement results in a memory of the UE.

14. The method of any of the previous claims, comprising: performing the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions.

15. The method of claim 14, wherein: the one or more third conditions comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold.

16. The method of claim 15, wherein: any one or more of the fourth parameter, the fifth parameter, and the sixth parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.

17. The method of any of claims 14 to 16, comprising:performing the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.

18. A method performed by a network node for managing data collection at a user equipment, UE, the method comprising: transmitting, to the UE, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE, wherein the one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.

19. The method of claim 18, wherein: the second layer is a higher layer than the first layer.

20. The method of claim 18 or 19, wherein: the first layer is a physical layer or Layer 1, LI. the second layer is a Radio Resource Control, RRC, layer or Layer 3, L3.

21. The method of any of claims 18 to 20, wherein: transmitting the one or more conditions to the UE comprises: transmitting a first configuration to the UE, wherein the first configuration comprises the one or more conditions.

22. The method of any claims 18 to 21, wherein: the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions for a first predefined length of time.

23. The method of any of claims 18 to 22, wherein: the one or more conditions are indicative of a radio link quality measured in a cell in which the data collection is started or stopped.

24. The method of any of claims 18 to 23, wherein: the one or more conditions comprise any one or more of: a condition that a first parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the second layer meets a first threshold; a condition that a second parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the second layer meets a second threshold; and a condition that a third parameter indicative of a radio link quality of one or more cells configured for the second layer meets a third threshold.

25. The method of claim 24, wherein: any one or more of the first parameter, the second parameter, and the third parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; and a Reference Signal Strength Indicator, RS SR.

26. The method of any of claims 18 to 25, wherein: the one or more conditions comprise one or more first conditions; and the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to start the data collection when the second layer fulfils the one or more first conditions.

27. The method of claim 26, wherein: starting the data collection comprises logging one or more measurement results in a memory of the UE.

28. The method of claim 26 or 27, wherein: the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to stop the data collection when the second layer no longerfulfils the one or more first conditions.

29. The method of any of claim 18 to 28, wherein: the one or more conditions comprise one or more second conditions; and the one or more conditions trigger the UE to perform the one or more actions based on whether the second layer fulfils the one or more conditions by: triggering the UE to stop the data collection when the second layer fulfils the one or more second conditions.

30. The method of claim 28 or 29, wherein: stopping the data collection comprises stopping logging one or more measurement results in a memory of the UE.

31. The method of any of claims 18 to 30, comprising: triggering the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils one or more third conditions.

32. The method of claim 31, wherein: the one or more third conditions comprise any one or more of: a condition that a fourth parameter indicative of a radio link quality of a Synchronization Signal Block, SSB, configured for the first layer meets a fourth threshold; a condition that a fifth parameter indicative of a radio link quality of a Channel State Information Reference Signal, CSR-RS, configured for the first layer meets a fifth threshold; and a condition that a sixth parameter indicative of a radio link quality of one or more cells configured for the first layer meets a sixth threshold.

33. The method of claim 32, wherein: any one or more of the fourth parameter, the fifth parameter, and the sixth parameter comprise any one or more of: a Reference Signal Received Power, RSRP; a Reference Signal Received Quality, RSRQ; a Signal-to-Interference-plus-Noise Ratio, SINR; anda Reference Signal Strength Indicator, RS SR.

34. The method of any of claims 31 to 33, wherein: the one or more third conditions trigger the UE to perform the one or more actions to control the data collection based on whether the first layer fulfils the one or more third conditions for a second predefined length of time.

35. A method performed by a system, the method comprising: the method as claimed in any of claims 1 to 17; and the method as claimed in any of claims 18 to 34.

36. A user equipment, UE, comprising processing circuitry configured to cause the UE to: receive, from a network node, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE; and perform the one or more actions to control the data collection based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.

37. The UE of claim 36, wherein the processing circuitry is configured to cause the UE to perform the method according to any of claims 2 to 17.

38. A network node comprising processing circuitry configured to cause the network node to: transmit, to the UE, one or more conditions for triggering the UE to perform one or more actions to control a data collection for collecting data from a first layer of a network protocol stack of the UE, wherein the one or more conditions trigger the UE to perform the one or more actions based on whether a second layer of the network protocol stack fulfils the one or more conditions, wherein the second layer is a different layer from the first layer.

39. The network node of claim 38, wherein the processing circuitry is configured to cause the network node to perform the method according to any of claims 19 to 34.

40. A system comprising: the wireless device as claimed in claim 36 or 37; and the network node as claimed in claim 38 or 39.

41. A computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method according to any of claims 1 to 35.

Images