Dynamic logging interval in ai / ML training data collection

By configuring UEs with variable logging periodicities based on measurement quantities and mobility, the solution addresses inefficiencies in data collection for network-sided AI/ML training, enhancing data relevance and reducing redundancy.

WO2026234644A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

Current frameworks for collecting data for network-sided AI/ML training in mobile communication are inefficient, particularly when UEs are in Idle/Inactive states, leading to sub-optimal data collection due to redundant samples and high battery consumption.

Method used

A network node configures UEs with variable logging periodicities based on measurement quantities, scaling factors, and mobility states to optimize data collection, reducing redundant samples and improving data relevance.

Benefits of technology

This approach enhances the efficiency of AI/ML training data collection by minimizing redundant data while maintaining data usefulness, thus optimizing resource utilization and battery life.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026054597_12112026_PF_FP_ABST
    Figure IB2026054597_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by a network node of a communication network for obtaining data collection from a user equipment (UE) The method comprises determining configuration information for logging the data collection at the UE, the configuration information comprising a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity. The method further comprises sending the configuration information to the UE and receiving a logging report from the UE, based on the data collection by the UE pursuant to the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

DYNAMIC LOGGING INTERVAL IN AI / ML TRAINING DATA COLLECTION TECHNICAL FIELD

[0001] Embodiments of the disclosure relate to the field of mobile communication; and more specifically, to operations related to data collection from a user equipment (UE).BACKGROUND

[0002] In 3GPP Rel-19 a study item for Artificial Intelligence / Machine Learning (AI / ML) for mobility was agreed. The study has as its goal to focus on mobility enhancement in Radio Resource Control_Connected (RRC_CONNECTED) mode over air interface by following existing mobility framework. That is, handover decision is always made on the network side. Mobility use cases focus on standalone New Radio (NR) Primary Cell (PCell) change. User Equipment (UE)-side and network-side AI / ML model can both be considered, respectively.

[0003] Study and evaluation of potential benefits and gains of AI / ML aided mobility for network triggered Layer 3 (L3)-based handover, consider the following aspects:• AI / ML based Radio Resource Management (RRM) measurement and event prediction, • Cell-level measurement prediction including intra and inter-frequency (UE sided and Network (NW) sided model) [Radio Access Network 2 (RAN2)];• Inter-cell Beam-level measurement prediction for L3 Mobility (UE sided and NW sided model) [RAN2];• Handover (HO) failure / Radio Link Failure (RLF) prediction (UE sided model) [RAN2];• Measurement events prediction (UE sided model) [RAN2].• Study the need / benefit of any other UE assistance information for the network side model [RAN2].• The evaluation of the AI / ML aided mobility benefits to consider HO performance Key Performance Indicators (KPIs) (e.g., Ping-pong HO, HOF / RLF, Time of stay, Handover interruption, prediction accuracy, and measurement reduction, etc.) and complexity tradeoffs [RAN2],• Potential Al mobility specific enhancement to be based on the Rel-19 AI / ML-air interface Work Item Description (WID) general framework (e.g. Life Cycle Management (LCM), performance monitoring etc.) [RAN2],• Potential specification impacts of AI / ML aided mobility [RAN2].• Evaluate testability, interoperability, and impact on RRM requirements and performance [RAN4].

[0004] To be able to do training of these AI / ML models that have been researched in the study item one would need to collect data from the network. One focus is on a solution for helping the network collect relevant data from the UEs it configures to collect data.

[0005] There currently exist certain challenge(s). There are no available framework to collect data for network sided model training in an efficient way especially when the UE is in an Idle / Inactive state. Using the logged MDT framework would not be ideal as the logging of the measurements is performed by the UEs without considering their mobility state i.e., the UEs would log the measurements with the pre-defined logging interval independent of the UE mobility state resulting in multiple samples from the same location when the UE is not mobile. This makes the AI / ML training data collection very sub-optimal from air interface resource and UE battery consumption point of viewSUMMARY

[0006] Certain aspects of the disclosure and the described embodiments may provide one or more solutions. The disclosed solution describes a network node to configure a UE with a variable logging periodicity. The periodicity is therefore changing over time which makes it possible for a network of the network node to collect more relevant data and limit redundant data samples. In one aspect, the collected data is used as training data to train an AI / ML associated with the network node.

[0007] In one aspect of the disclosed technique, a method is performed by a network node of a communication network for obtaining data collection from a UE by determining configuration information for logging the data collection at the UE, the configuration information including a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity; sending the configuration information to the UE; and receiving a logging report from the UE, based on the data collection by the UE pursuant to the configuration information.

[0008] In another aspect of the disclosed method for the network node, the configuration information also includes a scaling quantity for the measurement quantity, wherein the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

[0009] In another aspect of the disclosed method for the network node, the configuration information also includes an evaluation time to designate a time period that the scaling quantity is to be evaluated.

[0010] In another aspect of the disclosed method for the network node, the at least one scaling factor utilizes different scaling factors based on a frequency channel used by the UE.

[0011] In another aspect of the disclosed method for the network node, the at least one scaling factor utilizes different scaling factors based on a mobility of the UE.

[0012] In another aspect of the disclosed method for the network node, the configuration information includes different classes of objects to measure the measurement quantity and wherein different scaling factors are used for the different classes.

[0013] In another aspect of the disclosed method for the network node, the configuration information includes more than one logging object.

[0014] In another aspect of the disclosed method for the network node, the measurement quantity is one or more of:Reference Signal Received Power (RSRP);Reference Signal Received Quality (RSRQ);Signal to Interference and Noise Ratio (SINR); andsignal pathloss for the UE.

[0015] In another aspect of the disclosed method for the network node, further including sending the received logging report to an Artificial Intelligence / Machine Learning (AI / ML) function as training data for the AI / ML function.

[0016] In another aspect of the disclosed technique for the network node, a computing device of the network node performs the method described above for obtaining data collection from a UE.

[0017] In another aspect of the disclosed technique for the network node, a computer program containing instructions which, when executed by at least one processor, cause the network node to perform the method described above for obtaining data collection from a UE.

[0018] In another aspect of the disclosed technique, a method is performed by a UE of a communication network for obtaining data collection by receiving configuration information, from a network node, for logging the data collection at the UE, the configuration information including a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity; performing the logging of the data collection pursuant to the configuration information; and sending a logging report to the network node based on the data collection by the UE pursuant to the configuration information.

[0019] In another aspect of the disclosed method for the UE, the configuration information also includes a scaling quantity for the measurement quantity, wherein the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

[0020] In another aspect of the disclosed method for the UE, the configuration information also includes an evaluation time to designate a time period that the scaling quantity is to be evaluated.

[0021] In another aspect of the disclosed method for the UE, the at least one scaling factor utilizes different scaling factors based on a frequency channel used by the UE.

[0022] In another aspect of the disclosed method for the UE, the at least one scaling factor utilizes different scaling factors based on a mobility of the UE.

[0023] In another aspect of the disclosed method for the UE, the configuration information includes different classes of objects to measure the measurement quantity and wherein different scaling factors are used for the different classes.

[0024] In another aspect of the disclosed method for the UE, the configuration information includes more than one logging objects.

[0025] In another aspect of the disclosed method for the UE, the measurement quantity is one or more of:Reference Signal Received Power (RSRP);Reference Signal Received Quality (RSRQ);Signal to Interference and Noise Ratio (SINR); andsignal pathloss for the UE.

[0026] In another aspect of the disclosed method for the UE, the logging report is sent to an Artificial Intelligence / Machine Learning (AI / ML) function as training data for the AI / ML function.

[0027] In another aspect of the disclosed technique, a computing device of the UE performs the method described above for obtaining the data collection at the UE.

[0028] In another aspect of the disclosed technique, a computer program containing instructions which, when executed by at least one processor, cause the UE to perform the method described above at the UE for obtaining data collection at the UE.BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The disclosure may best be understood by referring to the following description and accompanying drawings that are used to illustrate embodiments of the disclosure. In the drawings:

[0030] FIG. 1 shows a signal flow diagram between a network node and a UE, in which the network node configures the UE for data collection according to some embodiments of the disclosure.

[0031] FIG. 2 shows a signal flow diagram of FIG. 1, in which the collected data is used as training data by an AI / ML according to some embodiments of the disclosure.

[0032] FIG.3 shows a flow diagram of a method performed by a network node for configuring an UE for data collection according to some embodiments of the disclosure.

[0033] FIG.4 shows a network node for configuring a UE for data collection according to some embodiments of the disclosure.

[0034] FIG. 5 shows a flow diagram of a method performed by a UE when receiving a configuration for data collection from a network node according to some embodiments of the disclosure.

[0035] FIG. 6 shows a UE for performing data collection when receiving a configuration for data collection from a network node according to some embodiments of the disclosure.

[0036] FIG.7 shows an example of a communication system according to some embodiments of the disclosure.

[0037] FIG. 8 shows another example of a communication system according to some embodiments of the disclosure.

[0038] FIG.9 illustrates a wireless device according to some embodiments of the disclosure.

[0039] FIG. 10 illustrates a network node according to some embodiments of the disclosure.

[0040] FIG.11 illustrates a diagram illustrating a virtualization environment in which functions may be virtualized according to some embodiments of the disclosure.DETAILED DESCRIPTION

[0041] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The idea is that a network node configures a user equipment (UE) with one or more scaling parameters that tell the UE how it should scale or changes the logging interval used when collecting data. Some of the parameters will relate to a quantity such as speed, Reference Signal Received Power (RSRP) variance or Signal to Interference and Noise Ratio (SINR) for example. And then the logging periodicity can be affected by the value of the quantity. Further, the UE stamps the applied scale in each collected data package indicating to the network the data were collected under fast or slow variant wireless condition.

[0042] A core of the disclosed solution is to let a network node configure a UE with a variable logging periodicity. The periodicity is therefore changing over time which makes it possible for the network to collect more relevant data and limit redundant data samples. Specifically, the part where scaling is made with a measurement quantity in mind, such as RSRP, RSRQ or SINR, is new. Some classification of UEs based on their cell switching patterns have been made in the past, but as disclosed herein, the UE uses measurement of other quantities to evaluate what loggingperiod it should have at the current moment and use that for data collection. Here are some of the configurations that a UE can obtain from the network.• UE gets configured with a set of parameters used in a formula to calculate the sampling periodicity at the current time.• UE measures the configured scaling quantity and are also configured with a set of scaling quantity -> scaling factor / logging periodicity pairs and from that result derives the logging periodicity.• UE use a specified scaling quantity and conduct measurement based on the scaling quantity to determine which class it is in and from a set of classes, in which scaling factor / logging periodicity pairs determine the logging periodicity it can use. • UE is configured with lists of cells that map to different scaling factors or logging periodicities. Then, when the UE is in one cell it will use the scaling / periodicity configured for that cell.• UE is configured with mapping between Absolute Radio Frequency Channel Number (ARFCN) and different scaling factors or logging periodicities. Then, when the UE logs in on one frequency channel the UE can use the factor / periodicity configured for that frequency channel.• UE is configured with two logging periods where one represents a stationary UE and the other one a moving UE, and depending on the mobility state, the UE takes the appropriate one.

[0043] An optional solution of the disclosure also dictates that the used logging periodicity is kept in the log record, so that when reading the log, it is clear what logging periodicity was used, or class or scaling quantity value were measured.

[0044] Certain embodiments may provide one or more of the following technical advantage(s). An advantage of the disclosure is to reduce redundant data collection of samples but keep the overall usefulness of the data logged. For example, if a UE is stationary, then it might be less useful for the network for the UE to log data often compared to when the UE is moving. With a higher movement speed of the UE, one would expect the samples to change more frequently and, therefore, the logged data that is captured would span a larger area of the whole possible data space that is relevant for the network to explore.

[0045] Some of the embodiments contemplated herein are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0046] An embodiment of the disclosure relates to a network node configuring a UE (also referred to as a terminal device or a mobile device) with data collection for logging. The network node then sends a configuration to the UE indicating the measurement quantity that is to be logged.The network node also indicates the logging interval and an associated scaling factor that can be used by the UE to determine how often to log the measurement quantities. The measurement quantity to be logged could be RSRP, RSRQ, SINR, and / or signal pathloss for the UE, for example but not limited to these. The scaling factor associated with the logging interval could be based on the mobility class of the UE (e.g., one value of scaling factor is applicable when the UE is slow moving and another value of the scaling factor is applicable when the UE is fast moving etc.) or the serving cell’s ARFCN value (e.g., one value of scaling factor is applicable when the UE is served by a cell in FR1 range and another value of the scaling factor is applicable when the UE is served by a cell in FR2 range etc.))

[0047] Upon receiving the corresponding configuration, the UE performs logging of the measurements(s) performed on the measurement quantity (or quantities) at time intervals adjusted based on the scaling factor. The UE measures this quantity with a logging time between each measurement and stores the data (e.g., in its memory) for later report of the data collected to the network node. The disclosure also describes a solution for a variable logging interval.

[0048] Figure 1 shows a signal flow diagram 100 between a network node and a UE. At operation 101, the network node wakes the UE to come to a connected mode, if the UE was not already awake. In one example, Radio Resource Control (RRC) signaling is used, such as RRC_Connected. At operation 102, the network node sends configuration information to the UE to configure the UE with logging and scaling information after determining the desired information to be retrieved from the UE. The configuration information can be sent by RRC signaling or by some other signaling. At operation 103, which is an optional step, the network node releases the UE, in which the UE may resort to the inactive state or mode. The release procedure is optional since the logging is typically done in the connected mode, but other scenarios can use logging in an inactive mode. Once the configuration information is received by the UE, the UE can perform the measurement(s) on its own.

[0049] At operation 104, the UE uses the received configuration information for logging to determine what measurement quantity or quantities is / are to be measured and logged based on the logging interval and the scaling factor provided in the configuration information. The logging interval is the sampling time periodicity for performing the measurement. The scaling factor is associated with the logging interval to vary a duration of the logging between the measurements. Thus, the scaling factor can shorten the sampling time periodicity, lengthen the sampling time periodicity, or not change the sampling time periodicity. As will be described below, the configuration information may also include a scaling quantity and / or evaluation time of the scaling quantity. Thus, the logging may consider the various factors described below regardingmeasurement quantity, scaling factor, scaling quantity, logging interval, etc. The logged data is collected by the UE and stored for later retrieval.

[0050] At operation 105, the network node requests the collected data from the UE. Any type of signaling can be used by the network node to request retrieval of the logged data. RRC signaling or a different signaling for data retrieval can be used. At operation 106 the UE sends the logged data to the network node. In some embodiment, operation 105 may be skipped, wherein the UE sends the logged data without being prompted by the network node.Calculation for deriving logging time

[0051] In one embodiment, the variable logging interval calculation operates as follows:resulting Logging Time = Logging Time x Scaling Factor x Value of Scaling Quantity

[0052] Following is a table (Table 1) with the introduced parameters in the above equation. Not all need to be implemented. In some scenarios a subset may be sufficient to make the solution possible. One or more of the parameters of Table 1 would be sent from the network node to the UE in the configuration information.Table 1

[0053] For example, in the equation above, the node might configure the UE with a logging periodicity of 400 ms and then a scaling factor of 0.5 and a quantity of RSRP variance, which is the scaling quantity. Then the UE logs the measurement that is configured with this information every 400 ms * 0.5 * RSRP Variance. The time that the variance is calculated over can also be configured by the network node in the Evaluation time.

[0054] The scaling factor is typically a numerical value, where a value of 1 keeps the sampling time periodicity for the measurement as the configured logging time interval. A fractional value shortens the sampling time periodicity and a value greater than 1 lengthens the sampling time periodicity. The scaling quantity is calculated by the UE based on some measurement performedby the UE over the evaluation time. For example, the scaling quantity can be the mean velocity of the UE, which is calculated by the UE movement (velocity) over an evaluation time of 10 seconds. Meaning that the UE calculates its mean velocity over the latest 10 seconds (evaluation time) and this is then used as the scaling quantity.

[0055] In another example, the network node might configure the UE with a logging periodicity (e.g., logging interval) of 640 milliseconds and then a scaling factors of 0.5 / 1 / 5 / 100, corresponding to the UE in a high speed / medium speed / low speed / stationary mobility states. Upon receiving such a configuration, the UE first determines its mobility state. For example, the mobility state determination could be based on measurements performed by the UE, such as a relative change in the RSRP values from a reference time within a duration or based on the number of handovers / reselections within a duration.

[0056] The scaling quantity could be something other than the quantity that is logged, but it could also be the same. One example is that the UE is configured to log RSRP and the logging time is scaled with the mean speed over the last Evaluation time. The UE then calculates the resulting logging time and uses that as the time between samples in the log that it keeps.

[0057] In another implementation the Evaluation time is fixed and are agreed upon between the network and the UE beforehand, so that there is nothing the network needs to configure for the Evaluation time. For example, in 5thGeneration (5G), it might be a fixed number of frames that is used as the evaluation time. If this is the case the parameter Evaluation time would not need to be configured by the network.A limited set of logging times

[0058] In another implementation, the resulting logging time is derived by the UE from a set of Scaling quantity Value and resulting logging time pairs which are configured by the network. A set where each Scaling quantity Value maps to a resulting logging time, {Scaling quantity Valuel: resulting logging timel, Scaling quantity Value2: resulting logging time2,..., Scaling quantity ValueN: resulting logging timeN}. The UE would then calculate the Scaling quantity and take the appropriate resulting logging time from the set, the appropriate time might refer to the one mapped to the Scaling quantity value with the smallest absolute difference between itself and the calculated Scaling quantity value. Another way to define the appropriate one is to define it as the largest Scaling quantity value in the set that is still smaller than the calculated one. Another way is to take the smallest Scaling quantity value in the set which is still larger than the calculated one. The UE could also linearly interpolate between the two closes points in the configured set. There is also other possible ways to determine the appropriate one to use.Scaling quantity is a set used for classification of UE

[0059] In another implementation, the network node configures the UE with a set as mentioned above, but this set is not a set of scaling quantity values as noted above. Instead, it is a set of classes mapping to a scaling factor. The classes could be high, medium and low mobility. The UE then derives in which class it is in and then uses the scaling factor for that class. The classes could also relate to a use case. For example, fixed wireless access node, car, mobile phone, etc. There are many other examples as to how the UE derives its class.Set of cells has different scaling factor / logging periodicities

[0060] In another implementation, the network node configures the UE with lists of cells where each set or list maps to different scaling factors or logging periodicities (e.g., interval). So, the UE could use the periodicity specified for the cells it currently is in, or in another implementation, the cell it is currently logging measurement for.Set of ARFCN has different scaling factor / logging periodicities

[0061] In another implementation, the network node configures the UE with lists of ARFCN, where each set or list maps to different scaling factors or logging periodicities. So, the UE could use the periodicity specified for the ARFCN for the current logging measurements.Scaling quantity is the same as the logged quantity

[0062] In another implementation, the scaling quantity is always the same as the logged quantity. In such a scenario the parameter Scaling quantity would be redundant and left out.Data collection configured in input / output pairs

[0063] When the implementation of the overall data collection framework is such that a UE might be configured with a pair of logging objects that represent an ObjectA and an ObjectB pair, which might be seen as an input output pair. In this instance, it might be unclear if the scaling should be done on the ObjectA or ObjectB quantity. Therefore, it may be of benefit for the network node to configure which should be used for the scaling. Thus, two following parameters could be introduced, as shown in Table 2.Table 2

[0064] Another implementation of this logic is that only one parameter is introduced, which is a Boolean flag that toggles either scale with ObjectA or ObjectB.Indication of scaling quantity in logged data

[0065] The application of scaling quantity can be indicated in the logged data to inform the network as to which scaling factor the data were collected under.Different logging times for stationery and mobile UE

[0066] In some embodiments, the UE can be configured with two logging periods. One logging periods is applied when the UE is stationary and the other logging time is applied when the UE is not stationary (e.g., when the UE is moving). Normally, a majority of the UEs are stationary and, thus, apply the logging time for stationary UEs. If the UE starts moving, it changes to the configured logging time for mobility and starts applying that logging time instead. A solution with two different logging times is simple, but it also provides gain in terms of reduced collection for the large number of UEs that are stationery.Obtaining scaling / Logging information for data collection

[0067] In some embodiments, the scaling factor to be used is provided in a dedicated message to the UE. One such example message could be in a RRC_Reconfiguration message. This embodiment would allow the possibility to configure different scaling factor values for different UEs to start with.

[0068] In some embodiments, the scaling factor to be used is provided in a broadcasted message to the UE. One such example message could be the System Information Block (SIB). This embodiment reduces the need to provide scaling factor for each UE individually. Also, this embodiment would enable the usage of scaling factor to determine the logging interval by the Idle and / or Inactive UEs as well.Further Description of Figure 1

[0069] Referring again to Figure 1, the signal flow could also start with the UE indicating that it supports variable logging frequency, by either before being configured, it indicates support of this feature in a message when coming to the connected state; or after it receives the logging and scaling information, answers the network node that it does not support this feature.

[0070] The following description relates to the iteration part in the signal flow diagram of Figure 1. The following is a description on how this could be implemented in the UE. The following logic are achieved once every base logging time in some embodiments:1. Derive the current Resulting logging time2. If time since last logging is more than Resulting logging time:Log the latest recorded measurement3. Else:Do nothing4. Wait base logging time until check is done againExample of implementation in scaling indication

[0071] The scaling factor applied in logged data, could be indicated in logged data explicitly or implicitly.

[0072] In case of indicating explicitly, the value of scaling can be stamped in the logged data, as shown below:• Flag: Indicate start of a frame• Frame No.: frame number of collected data• Scale: time difference between log instances• Collected data:• Fixed data length in every subframe, disregarding the scale applied• Collected data could be data sequence or data structure The ASN.1 of logged data could beLoggedData::= SEQUENCE {startFlag OxEEEEEEE, / / any special valueframeNumber INTEGER,scalingFactor INTEGER / DOUBLE,loggedData OCTET STRING (SIZE( 1.. MAX))

[0073] In another case, if the scaling factor is indicated in an implicit way, the index of scaling factor or more detail about scaling, such as fast, medium and slow etc., can be addressed in one of the row of the table that has been stored on the network node side.The ASN.1 of logged data could beLoggedData::= SEQUENCE {startFlag OxEEEEEEE, / / any special valueframeNumber INTEGER,scalingindex INTEGER, / / Address to one of the row in stored tableloggedData OCTET STRING (SIZE(1.. MAX))Example of implementation in Measurement logging

[0074] Following is an example implementation into 38.331 TS by 3GPP. The example shows where a UE is configured with a set of classification mappings as described earlier. Part of the specification is shown below. The new added portion is shown in Bold.5.5a.3.2InitiationWhile T330 is running and SDT procedure is not ongoing, the UE shall:1> if measurement logging is suspended:2>if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging;1> if not suspended, perform the logging in accordance with the following:2> if the reportType is set to periodical in the VarLogMeasConfig'.3> if the UE is in any cell selection state (as specified in TS 38.304

[0020] ):4> perform the logging at regular time intervals, as defined by the logginginterval in the VarLogMeas Config-,3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport', or3> if the UE is in camped normally state on an NR cell and if the registered SNPN identity is included in snpn-ConfigID-List stored in VarLogMeasReport'.4> if areaConfiguration is not included in VarLogMeasConfig', or4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig', or4> if the serving cell is part of the area indicated by cag-ConfigList in areaConfiguration in VarLogMeasConfig', or4> if the serving cell is part of the area indicated by snpn-ConfigList in areaConfiguration in VarLogMeas Confit g:5> perform the logging at regular time intervals, as defined by the logginginterval in the VarLogMeasConfig',3> If VarLogMeasCongfig includes variable LoggingPeriodicity.4> Perform a check if resultingLoggingTime derived from classificationSet in variableLoggingPeriodicity is longer than time from last logging instance at regular time intervals as defined in the VarLogMeasConfi.5> If check is positive do logging at checked time.— ASN1START— TAG-VARLOGMEASCONFIG-STARTVarLogMeasConf ig-rl 6:: = SEQUENCE {areaConf igurat ion- rl 6 AreaConf iguration-rl 6 OPTIONAL,bt-NameList-rl 6 BT-NameLi st-rl 6 OPTIONAL,wlan-NameLi st-rl 6 WLAN-NameLi st-r 16 OPTIONAL,sense r-NameLi st-rl 6 Sensor-NameList-rl 6 OPTIONAL, loggingDuration-rl 6 LoggingDuration-rl 6,reportType CHOICE {periodical Logged? eriodicalReport Conf ig-rl 6, eventTriggered LoggedEvent TriggerConf ig-rl 6bearlyMeas Indi cat ion-rl 7 ENUMERATED { true } OPTIONAL,areaConf igurat ion-r 17 AreaConf igurat ion-r 17 OPTIONAL,areaConf igurat ion- vl 800 AreaConf igurati on- vl800 OPTIONAL, variableLoggingPeriodicity VariableLoggingPeriodicity OPTIONAL,}— TAG-VARLOGMEASCONFIG-STOP— ASN1STOPVariableLoggingPeriodicity::= SEQUENCE!classificationSet SET{ low: resultingLoggingPeriodicityl, medium: resultingLoggingPeriodicity2, high: resultingLoggingPeriodicity3}

[0075] Figure 2 shows a flow diagram 200, which is an extension of the flow diagram of Figure 1, but now with the inclusion of an AI / ML function which receives the logged data obtained by the network node as shown by operation 201. The collected data from the UE is routed to the AI / ML function to be used as training data to train the AI / ML function. The AI / ML function, once trained, can be used to perform machine analysis on data under normal operation of the network node.

[0076] Figure 3 shows a flow diagram for performing a method 300 at a network node. The method is performed by a network node of a communication network for obtaining data collection from a UE. At operation 301, the network node determines configuration information for logging the data collection at the UE, the configuration information includes a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity. The operation 301 can be practiced by the earlier described procedure for determining the configuration information for the UE to perform data logging using the variable logging interval. The configuration information indicates the logging interval and an associated scaling factor that can be used by the UE to determine how often to measure the measurement quantities. The measurement quantity to be logged could be RSRP, RSRQ, SINR, and / or signal pathloss for the UE, for example but notlimited to these. The scaling factor associated with the logging interval could be based on the mobility class of the UE or some other feature of the UE.

[0077] At operation 302, the network node sends the configuration information to the UE.Figure 1 shows the operation 102, in which the network node sends configuration information to the UE to configure the UE with logging and scaling information after determining the desired information to be retrieved from the UE.

[0078] At operation 303 the network node receives a logging report from the UE, based on the data collection by the UE pursuant to the configuration information. Figure 1 shows the operation 106 in which the UE sends the logged data to the network node.

[0079] In practicing the method 300, the configuration information can also include a scaling quantity for the measurement quantity, where the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

[0080] In practicing the method 300, the configuration information can also include an evaluation time to designate a time period that the scaling quantity is to be evaluated.

[0081] In practicing the method 300, the at least one scaling factor can utilize different scaling factors based on a frequency channel used by the UE.

[0082] In practicing the method 300, the at least one scaling factor can utilize different scaling factors based on a mobility of the UE.

[0083] In practicing the method 300, the configuration information can include different classes of objects to measure the measurement quantity and where different scaling factors can be used for the different classes.

[0084] In practicing the method 300, the configuration information can include more than one logging object.

[0085] In practicing the method 300, the measurement quantity can be RSRP, RSRQ, SINR, and / or signal pathloss for the UE.

[0086] In practicing the method 300, the received logging report can be sent to an AI / ML function as training data for the AI / ML function.

[0087] Figure 4 shows a network node 400 of a communication network for obtaining data collection from a UE. The network node 400 includes a processing circuitry 401 and memory 402. The processing circuitry 401 provides the processing capability. A processor of the processing circuitry 401 may be a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, any other type of electronic circuitry, or any combination of one or more of the preceding. The processor may include one or more processor cores.

[0088] The memory 402 can store instructions which, when executed by the processing circuitry 401, are capable of configuring the network node 400 to perform the methods described in the present disclosure, including the method shown in flow diagram 300. The memory can be a computer readable storage medium 403, such as, but not limited to, any type of disk, including magnetic disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions. Furthermore, a carrier containing the computer program instructions can also be one of an electronic signal, optical signal, radio signal or computer storage medium.

[0089] Figure 5 shows a flow diagram for performing a method 500 at a user equipment. The method is performed by a UE of a communication network for obtaining data collection. At operation 501, the UE receives configuration information, from a network node, for logging the data collection at the UE, the configuration information includes a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity. The configuration information indicates the logging interval and an associated scaling factor that can be used by the UE to determine how often to measure the measurement quantities. The measurement quantity to be logged could be RSRP, RSRQ, SINR, and / or signal pathloss for the UE, for example but not limited to these. The scaling factor associated with the logging interval could be based on the mobility class of the UE or some other feature of the UE.

[0090] At operation 502 the UE performs the logging of the data collection pursuant to the configuration information. At operation 503, the UE sends a logging report to the network node based on the data collection by the UE pursuant to the configuration information.

[0091] In practicing the method 500, the configuration information can also include a scaling quantity for the measurement quantity, where the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

[0092] In practicing the method 500, the configuration information can also include an evaluation time to designate a time period that the scaling quantity is to be evaluated.

[0093] In practicing the method 500, the at least one scaling factor can utilize different scaling factors based on a frequency channel used by the UE.

[0094] In practicing the method 500, the at least one scaling factor can utilize different scaling factors based on a mobility of the UE.

[0095] In practicing the method 500, the configuration information can include different classes of objects to measure the measurement quantity and where different scaling factors can be used for the different classes.

[0096] In practicing the method 500, the configuration information can include more than one logging object.

[0097] In practicing the method 500, the measurement quantity can be RSRP, RSRQ, SINR, and / or signal pathloss for the UE.

[0098] In practicing the method 500, the logging report can be sent to an AI / ML function as training data for the AI / ML function.

[0099] Figure 6 shows a UE 600 of a communication network for obtaining data collection. The UE 600 includes a processing circuitry 601 and memory 602. The processing circuitry 601 provides the processing capability. A processor of the processing circuitry 601 may be a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, any other type of electronic circuitry, or any combination of one or more of the preceding. The processor may include one or more processor cores.

[0100] The memory 602 can store instructions which, when executed by the processing circuitry 601, are capable of configuring the UE 600 to perform the methods described in the present disclosure, including the method shown in flow diagram 500. The memory can be a computer readable storage medium 503, such as, but not limited to, any type of disk, including magnetic disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions. Furthermore, a carrier containing the computer program instructions can also be one of an electronic signal, optical signal, radio signal or computer storage medium.

[0101] Figure 7 shows an example of a communication system 700 in accordance with some embodiments. In some embodiments UE 712A-D can perform the function of the UE described above in reference to Figures 1- Figure 6. In some embodiments, network nodes 708 and / or 710A-B can perform the function of the network node described above in reference to Figures 1-Figure 6 that determines the configuration information.

[0102] In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or anyother similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipment(s) (UEs), such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

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

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

[0105] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover,in different embodiments, the communication system 700 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 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

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

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

[0108] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunications network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 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.

[0109] As a whole, the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 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); Fong Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.

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

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

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

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

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

[0115] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedulebetween the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 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 710B. In other embodiments, the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0116] Figure 8 is another example of a communication system 800 according to some embodiments. In some embodiments STA 812A-E can perform the function of the UE described above in reference to Figures 1- Figure 6. In some embodiments, AP 810A-D can perform the function of the network node described above in reference to Figures 1- Figure 6 that determines the configuration information.

[0117] As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812 (referred to individually as STA 812A, STA 812B, STA 812C, STA 812D, and STA 812E). STA 812A is served by AP 810A in a first basic service set (BSS) 820A. STA 810B and STA 810C are served by AP 810B in a second BSS, BSS 820B. STA 812D is served by AP 810C in a third BSS, BSS 820C. STA 812E is served by AP 810D in a fourth BSS, BSS 820D. Stations 812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

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

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

[0120] Figure 9 shows a wireless device 900, which may be configured to operate in communication system 700 of Figure 7 or in communication system 800 of Figure 8. In some embodiments wireless device 900 can perform the function of the UE described above in reference to Figures 1- Figure 6. Furthermore, processing circuitry 902 can perform the function of the processing circuitry 601 and memory 910 can perform the function of memory 602 of Figure 6.

[0121] The wireless device 900 may be alternatively referred to as a UE 900, like a UE 712 within the context of communication system 700, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA 812 within the context of the communication system 800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0123] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0124] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine -readable computer programs in the memory 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).

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

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

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

[0128] The memory 910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow wireless device 900 to access instructions, programs and the like, stored on transitory ornon-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 910, which may be or comprise a device-readable storage medium.

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

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

[0131] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0132] As another example, wireless device 900 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 900 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.

[0133] Wireless device 900, 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, 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, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 900 represents an loT device that 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 example embodiment of wireless device 900 shown in Figure 9.

[0134] As yet another specific example, in an loT scenario, wireless device 900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 900 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 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.

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

[0136] Figure 10 shows a network node 1000 in accordance with some embodiments. In some embodiments, network node 1000 can perform the function of the network node described above in reference to Figures 1- Figure 6 that determines the configuration information. Furthermore, processing circuitry 1002 can perform the function of the processing circuitry 401 and memory 1004 can perform the function of memory 402 of Figure 4.

[0137] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 700 of Figure 7, like network nodes 708 or 710, or in communication system 800 of Figure 8, like an AP 810 or a station 812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0138] Network nodes 1000 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 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).

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

[0140] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.

[0141] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1000.

[0142] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1004, to provide network node 1000 functionality.

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

[0144] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

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

[0146] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of thecommunication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

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

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

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

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

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

[0152] Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1100 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

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

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

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

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

[0157] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitionedbetween 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.

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

Claims

CLAIMSWhat is claimed is:

1. A method (300) performed by a network node of a communication network for obtaining data collection from a user equipment, UE, the method comprising:determining (301) configuration information for logging the data collection at the UE, the configuration information comprising a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity;sending (302) the configuration information to the UE; andreceiving (303) a logging report from the UE, based on the data collection by the UE pursuant to the configuration information.

2. The method according to claim 1, wherein the configuration information also includes a scaling quantity for the measurement quantity, wherein the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

3. The method according to claim 2, wherein the configuration information also includes an evaluation time to designate a time period that the scaling quantity is to be evaluated.

4. The method according to any one of claims 1-3, wherein the at least one scaling factor utilizes different scaling factors based on a frequency channel used by the UE.

5. The method according to any one of claims 1-3, wherein the at least one scaling factor utilizes different scaling factors based on a mobility of the UE.

6. The method according to any one of claims 1-5, wherein the configuration information comprises different classes of objects to measure the measurement quantity and wherein different scaling factors are used for the different classes.

7. The method according to any one of claims 1-5, wherein the configuration information comprises more than one logging object.

8. The method according to any one of claims 1-7, wherein the measurement quantity is one or more of:Reference Signal Received Power, RSRP;Reference Signal Received Quality, RSRQ;Signal to Interference and Noise Ratio, SINR; andsignal pathloss for the UE.

9. The method according to any one of claims 1-8, further comprising sending the received logging report to an Artificial Intelligence / Machine Learning, AI / ML, function as training data for the AI / ML function.

10. A computing device (401) of a network node (400) to perform the method according to any one of claims 1-9.

11. A computer program (402, 403) comprising instructions which, when executed by at least one processor (401), cause a network node (400) to perform the method according to any one of claims 1-9.

12. A method (500) performed by a user equipment, UE, of a communication network for obtaining data collection, the method comprising:receiving (501) configuration information, from a network node, for logging the data collection at the UE, the configuration information comprising a measurement quantity to be logged by the UE, a logging interval for performing a measurement of the measurement quantity, and at least one scaling factor associated with the logging interval to vary a duration of the logging interval between measurements of the measurement quantity;performing (502) the logging of the data collection pursuant to the configuration information; andsending (503) a logging report to the network node based on the data collection by the UE pursuant to the configuration information.

13. The method according to claim 12, wherein the configuration information also includes a scaling quantity for the measurement quantity, wherein the scaling quantity varies the duration of the logging interval based on measurements performed by the UE.

14. The method according to claim 13, wherein the configuration information also includes an evaluation time to designate a time period that the scaling quantity is to be evaluated.

15. The method according to any one of claims 12-14, wherein the at least one scaling factor utilizes different scaling factors based on a frequency channel used by the UE.

16. The method according to any one of claims 12-14, wherein the at least one scaling factor utilizes different scaling factors based on a mobility of the UE.

17. The method according to any one of claims 12-16, wherein the configuration information comprises different classes of objects to measure the measurement quantity and wherein different scaling factors are used for the different classes.

18. The method according to any one of claims 12-17, wherein the configuration information comprises more than one logging objects.

19. The method according to any one of claims 12-18, wherein the measurement quantity is one or more of:Reference Signal Received Power, RSRP;Reference Signal Received Quality, RSRQ;Signal to Interference and Noise Ratio, SINR; andsignal pathloss for the UE.

20. The method according to any one of claims 12-19, wherein the logging report is sent to an Artificial Intelligence / Machine Learning, AI / ML, function as training data for the AI / ML function.

21. A User Equipment, UE (600), to perform the method (500) according to any one of claims 12-20.

22. A computer program (602, 603) comprising instructions which, when executed by at least one processor (601), cause a user equipment, UE (600), to perform the method according to any one of claims 12-20.