Enabling data collection during inactivity periods

By configuring UEs to collect data during inactive periods using DRX or measurement gaps, the challenge of data collection during active periods is addressed, enhancing AI/ML model training and inference in communication networks.

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

Patent Information

Application Number
PCT/SE2026/050324
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

In existing communication networks, user equipment (UE) faces challenges in collecting data for machine learning model training or inference during active transmission or reception periods, as the network may not be aware of the UE's data collection needs, and there are no means for the UE to notify the network.

Method used

The UE is configured to collect data during inactive periods, such as discontinuous reception (DRX) or measurement gaps, by requesting and receiving a data collection configuration from the network, allowing data collection during DRX inactivity periods or measurement gaps.

Benefits of technology

Enables the UE to collect data efficiently for model training or inference without interfering with active transmissions, improving the accuracy and efficiency of AI/ML predictions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2026050324_12112026_PF_FP_ABST
    Figure SE2026050324_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Methods and apparatus for ML model data collection. A method performed by a wireless device comprises receiving, from a network node, a data collection configuration. The method further comprises performing data collection, based on the data collection configuration, during inactive periods.
Need to check novelty before this filing date? Find Prior Art

Description

ENABLING DATA COLLECTION DURING INACTIVITY PERIODSTechnical FieldEmbodiments of the present disclosure relate to methods and apparatus in communication networks, in particular methods and apparatus for Machine Learning (ML) model data collection.BackgroundAI / ML for Mobility

[0001] 3rdGeneration Partnership Project (3 GPP) Release 19 (rel-19) included a focus on Artificial Intelligence / Machine Learning (AI / ML) for mobility. An aim is mobility enhancement in Radio Resource Control Connected (RRC CONNECTED) mode over air interface based on the existing mobility framework, wherein handover decisions are made at the network side. Mobility use cases focus on standalone New Radio (NR) Primary Cell (PCell) change. User Equipment side (UE-side) and network-side AI / ML models may be considered.

[0002] Studies of the potential benefits and gains of AI / ML aided mobility for network triggered L3-based handover, may include consideration of the following aspects:AI / ML based Radio Resource Management (RRM) measurement and event prediction,a. Cell-level measurement prediction including intra and inter-frequency (UE sided and NW sided model)b. Inter-cell Beam -level measurement prediction for L3 Mobility (UE sided and NW sided model)c. Handover (HO) failure / Radio Link Failure (RLF) prediction (UE sided model)d. Measurement events prediction (UE sided model)Studies of the need / benefits of any other UE assistance information for the network side modelThe evaluation of the AI / ML aided mobility benefits should consider HO performance Key Performance Indicators (KPIs) (e.g., Ping-pong Handover (HO), HOF / RLF, Time of stay, Handover interruption, prediction accuracy, and measurement reduction) etc.) and complexity tradeoffs

[0003] Simulation assumption and methodology are considered in 3 GPP TR documents TR 38.901 vl8.0.0 (available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx7specificatio nld=3173 as of 8 May 2025), TR 38.843 vl8.0.0 (available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx7specificatio nld=3983 as of 8 May 2025) and TR 36.839 vl 1.1.0 (available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx7specificatio nId=2540 as of 8 May 2025)Potential Al mobility specific enhancement may be based on the Rell9 AI / ML-air interface framework, once finalized.Potential specification impacts of AI / ML aided mobility.Evaluate testability, interoperability, and impacts on RRM requirements and performance.Model training and inference

[0004] When a UE is configured with an AI / ML model to perform predictions, the phase when it actually performs the predictions is called inference. Before the inference phase, the UE needs to train the AI / ML model so that it can perform well during the inference. This phase is called model training.DRX for RRC CONNECTED

[0005] When a UE is in RRC CONNECTED, it is required to monitor Physical Downlink Control Channels (PDCCH). This consumes battery in the UE and some UE power saving functions have been defined, e.g. Discontinuous Reception DRX, where the UE is not required to monitor PDCCH the whole time. When DRX is configured, the UE does not have to continuously monitor PDCCH. The UE is configured with periods of on-duration when it is required to monitor PDCCH and periods of inactivity when it is not required to monitor PDCCH. A DRX cycle timing diagram is shown in Figure 1.Figure 1: DRX cycle timing diagram

[0006] DRX is further described in TS 38.300 vl8.5.0, chapter 11 (available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx7specificatio nld=3191 as of 8 May 2025).Measurement gaps

[0007] When a UE performs measurements on a different frequency than the serving frequency, it, in many cases, cannot transmit and receive on the serving frequency at the same time as it needs to retune the transmitter and receiver to the other frequency. Whether it can transmit and receive on the serving frequency at the same time depends on the UE capabilities. If the UE is not capable of monitoring the serving frequency when measuring on a different frequency, it needs to be configured with measurement gaps. Measurement gaps are defined periods when the UE does not have to monitor the serving frequency and during these periods the UE has the opportunity to measure on a different frequency. The measurement gaps need to be aligned between the network and the UE, so that the network will not schedule the UE during the measurement gaps. Hence, the network provides the UE with a configuration for the measurement gaps where it is defined when the UE monitors the serving frequency and when the UE is allowed to measure on the other frequency. 3GPP TS 38.331 vl8.5.1, available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx7specificatio nld=3197 as of 8 May 2025 specifies the Radio Resource Control (RRC) protocol for the radio interface between UE and NG-RAN.

[0008] There currently exist certain challenge(s). A UE that performs predictions may desire to collect data for model training or inference. The data collection may not be possible to perform during ongoing transmissions or receptions. If the prediction model is located in the UE, the network may not be aware of when the UE needs to collect data. So, the problem is that the UE needs to collect the data, but the UE may not have the possibility to collect data using an existing configuration. Also, the UE may not have any means of notifying the network of this problem, and the network may not be aware of the need.Summary

[0009] In accordance with embodiments, a method performed by a wireless device for ML model data collection is provided. The method comprises receiving, from a network node, adata collection configuration. The method further comprises performing data collection, based on the data collection configuration, during inactive periods.

[0010] In accordance with embodiments, a method performed by a network node for ML model data collection is provided. The method comprises transmitting, to a wireless device, a data collection configuration, for configuring wireless device data collection during inactive periods.

[0011] Further embodiments provide wireless devices and network nodes configured to perform the methods discussed herein.

[0012] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Initially, a UE may be configured to perform predictions in RRC CONNECTED. In order to perform the predictions, the UE needs to collect data for model training or for inference (as input to the models). In some embodiments, the data needs to be collected while the UE is in RRC CONNECTED. Embodiments provide methods performed by the UE wherein the UE receives the data collection configuration for the model training and / or inference wherein the UE based on the received data collection configuration performs the data collection and logging the measurements only when it is in inactive periods in RRC CONNECTED state, wherein the inactive period in RRC CONNECTED state refers to periods when there are no UL and DL data transmissions scheduled for the UE.

[0013] In some embodiments, the configuration comprises an indication to collect the data during the inactive periods of DRX for RRC CONNECTED, i.e. the periods normally used for power saving.

[0014] In some embodiments, the configuration comprises the configuration of a new type of inactivity periods specifically for data collection. The inactive periods may be defined by a length and periodicity of the inactivity periods, and where no UL or DL data transmissions is scheduled during the inactivity periods.

[0015] In some embodiments, the configuration comprises the configuration of measurement gaps, and where the UE can collect measurements on different frequencies during the measurement gaps, or use the measurement gaps to collect any type of data.

[0016] According to embodiments, the UE is configured with periods of inactivity in order to perform data collection for prediction model training or in order to perform inference of an inference configuration. The network may configure the UE with the inactive periods without UE input or the UE may request to be configured with the inactive periods. The inactive periods may include discontinuous transmissions / receptions, i.e. periods of inactivity in thetransmission and receptions, in order to perform data collection for prediction model training or in order to perform inference of an inference configuration. The inactive periods may comprise:connected mode DRX, where the UE is intended to perform data collection during the inactive periods of the DRX.a new type of inactive period, where the UE is intended to perform data collection during the inactive period.measurement gaps, where the UE is intended to perform measurements on a different frequency for data collection during the measurement gaps.

[0017] Certain embodiments may provide one or more of the following technical advantage(s). A UE may be provided with the capability to indicate to the network that it needs a configuration that allows data collection, addressing prior situations in which it may be difficult or impossible for the UE to collect the necessary data, which may mean that the UE is not able to perform predictions.Brief Description of the Drawings

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

[0019] Fig l is a DRX cycle timing diagram

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

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

[0022] Fig. 4 is a signaling diagram showing a UE requesting discontinuous reception, in accordance with some embodiments;

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

[0024] Fig. 6 shows an example of another communication system in accordance with some embodiments;

[0025] Fig. 7 shows a wireless device in accordance with some embodiments;

[0026] Fig. 8 shows a network node in accordance with some embodiments; and

[0027] Fig. 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.Detailed DescriptionSome of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0028] Figure 2 depicts a method for ML model data collection in accordance with particular embodiments. The method 2 may be performed by a wireless device (e.g. UE 512, station 612 or wireless device 700 as described later with reference to Figures 5, 6 and 7 respectively).

[0029] The method begins at step 202, in which the wireless device receives, from a network node (which may be network node 510, access point 610 or network node 800 as described later with reference to Figures 5, 6 and 8 respectively; the network node may execute method 3 as discussed below), a data collection configuration. The method continues at step 204 with the wireless device performing data collection, based on the data collection configuration, during inactive periods.

[0030] Figure 3 depicts a method for ML model data collection in accordance with particular embodiments. The method 3 may be performed by a network node (e.g. network node 510, access point 610 or network node 800 as described later with reference to Figures 5, 6 and 8 respectively).

[0031] The method begins at step 302, in which the network node transmits, to a wireless device (which may be UE 512, station 612 or wireless device 700 as described later with reference to Figures 5, 6 and 7 respectively; the wireless device may execute method 2 as discussed above), a data collection configuration, for configuring wireless device data collection during inactive periods.

[0032] In the following discussion, references to predictions refer to any Artificial intelligence (AI) / Machine Learning (ML) based predictions, namely the results of the inference of an AI / ML engine, that is performed based on measurements and / or some additional information or any non-AL / ML based predictions, and reported to the network. The predictions may also be performed using a non-AI / ML model based on measurements and / or additional information.

[0033] In embodiments a UE may be configured to perform predictions. To be able to perform the predictions, the UE may need to perform data collection when the UE is in RRC CONNECTED. The data collection may be needed for model training or for performing the actual inference. In figure 4 a signaling flow for the UE requesting discontinuous reception is shown.

[0034] Embodiments provide methods for UEs. In some embodiments, the UE may transmit UE capabilities related to predictions, data collection, DRX, measurements, supported frequencies and frequency bands, and so on.

[0035] Initially, the UE may be configured to perform predictions in RRC CONNECTED. In order to perform the predictions, the UE may need to collect data for model training or for inference (as input to the models). In some embodiments the data may need to be collected while the UE is in RRC CONNECTED. Embodiments include a method performed by the UE wherein the UE receives the data collection configuration for the model training and / or inference wherein the UE based on the received data collection configuration performs the data collection and logging the measurements only when it is in inactive periods in RRC CONNECTED state, wherein the inactive period in RRC CONNECTED state refers to periods when there is no UL and DL data transmissions scheduled for the UE.In some embodiments, the configuration comprises an indication to collect the data during the inactive periods of DRX for RRC CONNECTED, i.e. the periods normally used for power saving, and / orIn some embodiments, the configuration comprises the configuration of a new type of inactivity periods specifically for data collection. The inactive periods may be defined by a length and periodicity of the inactivity periods, and where no UL or DL data transmissions is scheduled during the inactivity periods, and / orIn some embodiments, the configuration comprises the configuration of measurement gaps, and where the UE can collect measurements on different frequencies during the measurement gaps, or use the measurement gaps to collect any type of data.

[0036] In order to collect the data, the UE may send a configuration request to the network. The request may be a request to be configured with discontinuous reception for RRC CONNECTED state. The request may be sent in an RRC message, e.g.UE Assistanceinformation, RRCReconfigurationComplete, RRCResumeComplete or MeasurementReport and may be defined as a new indication or a new Information Element (IE), e.g. NeedForDRX. Alternatively, a new RRC message e.g. Inactivityinterestindication, may be defined comprising an indication or a new IE and possibly additional information, e.g. the reason for the request. The request could be of different types and may comprise additional information; by way of example:a. The request may be a request to be configured with DRX for RRC CONNECTED. This means that the UE requests to be configured with DRX for RRC CONNECTED, but not for the purpose of power saving, but in order to perform data collection. Hence, the DRX for RRC CONNECTED is used with the new purpose of data collection. The purpose of the request may be indicated, or the request may just say that the UE would like to be configured with DRX.b. The request may be a request to be configured with a new type of inactivity periods. The purpose of these inactive periods may be specifically for data collection for model training and / or inference or the inactive periods may also be used for other purposes. The inactive periods may comprise periods of inactivity related to reception / transmission and which the UE can utilize to perform data collection. The inactive periods may be defined by a length and periodicity of the inactivity periods. Alternatively, the periods when the UE needs to monitor PDCCH and be able to receive and transmit data may be defined.c. The request may comprise an indication of the reason for the request, e.g. data collection for predictions, data collection for model training, data collection for inference. Alternatively, the request itself may indicate that the UE needs the discontinuous reception for data collection purposes.d. Where the predictions comprise inter-frequency predictions for one or more frequencies, the request may comprise a request to be configured with measurement gaps. The UE may use the measurement gaps to perform measurements on different frequencies in order to collect data for the model training and / or inference.e. The UE may indicate to the network that it needs to measure on different frequency(ies) and which frequency(ies) it needs to measure in order to collect data for model training and / or inference. The network may, based on UE capabilities for the indicated frequency(ies), determine whether the UE needs to be configured with measurement gaps in order to perform the measurements.

[0037] Where the UE sends a configuration request to the network node, the request may be accepted or rejected. If the request is rejected, the UE may receive an indication of rejection, possibly with an associated cause value / reason for the reject. The reject may be sent in a DL RRC message, e.g. in a new RRC message or in RRCReconfiguration. Alternatively, a lack of reply may be used to indicate that the network has rejected the request. Upon receiving a reject response from the network, the UE may need to run a timer (e.g., a prohibition timer) wherein the UE is not allowed to send a second request for a predetermined period of time (that is, if the prohibition timer is running). In some embodiments the UE may run the timer right after sending the request. In some embodiments the prohibition timer may be configured by the network as part of RRC reconfiguration message e.g., within otherConfig.

[0038] If the request is accepted, or if the configuration is triggered by the network without prior request from the UE, the UE may receives a message, e.g. an RRCReconfiguration, containing an updated UE configuration. The reconfiguration message may comprise a configuration of discontinuous reception for RRC CONNECTED, for example:a. The configuration may comprise the configuration of the DRX for RRC CONNECTED, in other cases used for power saving purposes. b. The configuration may comprise the configuration of a new type inactivity periods for data collection for model training and / or inference. The configuration of the inactive periods may comprise the length and periodicity of the inactivity periods. The configuration may also define the occasions where the UE needs to monitor PDCCH.c. The configuration may comprise the configuration of measurement gaps. The UE may use the gaps to perform measurements on different frequencies and the measurement results may be used as input to the model training and / or inference.

[0039] The data collection configuration may further include a data collection supervision timer information and value. The UE upon receiving the supervision timer may start the datacollection supervision timer when it starts the data collection in inactive period in RRC CONNECTED state and stop the data collection supervision timer when it stops the data collection supervision timer upon stopping / suspending the data collection e.g., due to the end of the inactive period in RRC_ CONNECTED state due to receiving DL data or transmitting UL data.

[0040] Upon receiving such configuration when logging the data the UE may include the time information in the collected measurements. For example, the UE may store with the sample of data a relative time indicating the time elapsed since logging the sample of data and receiving the data collection configuration. In another example the UE for each sample of data the UE logs the time elapsed since logging the previous sample of data. In a variant the UE logs the time information only for the samples for which there was a data transmission in between logging such samples and hence there logging interval is longer than the normal logging interval for the data collection.

[0041] Logging time information as part of data collection in inactive period in RRC CONNECTED state enables the model training entity to be aware of the discontinuity of the data collection hence the time series analysis of the collected measurements would not be misled by the sequence of the data which may be collected in different time.

[0042] Upon receiving such configuration when logging the data the UE may include a flag in the report and associate it to the data samples collected at the time instances at which there was an interruption in data collection due to UL / DL data transmission / reception.

[0043] The UE, upon receiving a data collection configuration, may request that a different DRX cycle period be configured for the data collection purpose. Some embodiments related to such a request are as follows. Similar to the time information logging such flag indicating the discontinuity of the logging the samples as part of data collection in inactive period in RRC CONNECTED state enables the model training entity to be aware of the discontinuity of the data collection hence the time series analysis of the collected measurements would not be misled by the sequence of the data which may be collected in different time.

[0044] In some embodiments a UE may request from a network node one of two categories of DRX cycle:Short DRX (e.g., 20-40 ms) if the UE needed data collection for inference purpose (e.g., HO prediction A3 within PW)- Long DRX (e.g., > 640 ms) if the UE needed data collection for the purpose of accumulating training data (e.g., offline model training and improving generalization)

[0045] In some embodiments, where NR Dual Connectivity is considered, and a UE is connected to a Master Cell Group (MCG) and a Secondary Cell Group (SCG), the UE may request two independent DRX configurations, one for the MCG and another for the SCG.

[0046] Data collection on MCG-DRX may be useful for:a. Long-term mobility trends model training.b. Predicting coverage loss (e.g., macro anchor) model training

[0047] Data collection on SCG-DRX may be useful for:a. Model training on Fast switching spatial beam predictionb. Model training on Dense beam pattern

[0048] In some embodiments, a UE may explicitly indicate its desired DRX category (or config in term of cycle length) associated with the UE mobility state class.

[0049] Embodiments provide methods for network nodes.

[0050] In some embodiments, the network node may receive from a UE a request to be configured with discontinuous reception for RRC CONNECTED. The request may be sent in an RRC message, e.g. UEAssistancelnformation, RRCReconfigurationComplete, RRCResumeComplete or MeasurementReport and may be defined as a new indication or a new Information Element (IE), e.g. NeedForDRX. Alternatively, a new RRC message e.g. Inactivity Interestindication, may be defined comprising an indication or a new IE and possibly additional information, e.g. the reason for the request. The request mat be of different types and comprise additional information, by way of example:a. The request may be a request to be configured with DRX for RRC CONNECTED. This means that the UE requests to be configured with DRX for RRC CONNECTED, but not for the purpose of power saving, but in order to perform data collection. Hence, the DRX for RRC CONNECTED is used with the new purpose of data collection. The purpose of the request may be indicated, or the request may just say that the UE would like to be configured with DRX.b. The request may be a request to be configured with a new type of inactivity periods. The purpose of these inactive periods may bespecifically for data collection for model training and / or inference or the inactive periods may also be used for other purposes. The inactive periods may comprise periods of inactivity related to reception / transmission and which the UE can utilize to perform data collection. The inactive periods may be defined by a length and periodicity of the inactivity periods. Alternatively, the periods when the UE needs to monitor PDCCH and be able to receive and transmit data may be defined.c. The request may comprise an indication of the reason for the request, e.g. data collection for predictions, data collection for model training, data collection for inference. Alternatively, the request itself may indicate that the UE needs the discontinuous reception for data collection purposes.d. Where the predictions comprise inter-frequency predictions for one or more frequencies, the request may comprise a request to be configured with measurement gaps. The UE may use the measurement gaps to perform measurements on different frequencies in order to collect data for the model training and / or inference.e. The UE may indicate to the network that it needs to measure on different frequency(ies) and which frequency(ies) it needs to measure in order to collect data for model training and / or inference. The network may, based on UE capabilities for the indicated frequency(ies), determine whether the UE needs to be configured with measurement gaps in order to perform the measurements.

[0051] Where the network node has received a configuration request, the network node may evaluate whether the UEs request can be fulfilled or not. If the request cannot be fulfilled, the network may send an indication of reject in response to the request, possibly with an associated cause value / reason for the reject. The reject may be sent in a DL RRC message, e.g. in a new RRC message or in RRCReconfiguration. Alternatively, the network may ignore the request from the UE.

[0052] Where the network node has received a configuration request and evaluates that the request can be fulfilled, the network node may respond to the UE with a message, e.g. an RRCReconfiguration, containing an updated UE configuration. Also, if the network decides toconfigure the UE with discontinuous reception in order to utilize data collection in the UE without a prior request from the UE, the network may send a message to the UE, e.g. an RRCReconfiguration message. The reconfiguration message may comprise a configuration of discontinuous reception for RRC CONNECTED, for example:a. The configuration may comprise the configuration of the DRX for RRC CONNECTED, in other cases used for power saving purposes. b. The configuration may comprise the configuration of a new type inactivity periods for data collection for model training and / or inference. The configuration of the inactive periods may comprise the length and periodicity of the inactivity periods. The configuration may also define the occasions where the UE needs to monitor PDCCH.c. The configuration may comprise the configuration of measurement gaps. The UE may use the gaps to perform measurements on different frequencies and the measurement results may be used as input to the model training and / or inference.

[0053] In some embodiments, the network node may transmit to the UE a use indication that the UE should use inactive periods for data collection; alternatively this may be implicit. Where present, the use indication may be transmitted with the data collection configuration, or may be transmitted separately to the data collection configuration.

[0054] In embodiments where NR Dual Connectivity is considered, and the UE is connected to a MCG and a SCG, the network may configure the UE with two independent DRX configuration, one for the MCG and other one for the SCG.

[0055] Data collection on MCG-DRX may be useful for:a. Long-term mobility trends model training.b. Predicting coverage loss (e.g., macro anchor) model training

[0056] Data collection on SCG-DRX may be useful for:a. Model training on Fast switching spatial beam predictionb. Model training on Dense beam pattern

[0057] In some embodiments, a network nodes may align DRX (off-durations) with measurement gaps offsets, and send this alignment to a UE, to prevent conflict between data collection and active UL / DL. Typically, there is no field or IE that directly connects drx-Config with measGapConfig, hence such alignment is missing. Accordingly, network has two options:

[0058] Option 1 : Reuse Existing Fields with Shared offset Alignmenta. If drx-Config.longDRX-CycleStartOffset and measGapConfig. gapOffset are set to the same value, they may implicitly align the drx inactivity with the measurement gap start.b. Option 1 may require, manual coordination by the NW, and No indication to the UE that this alignment is intentional or for model training and / or inference use.

[0059] Option 2: Introduce a New Field or IEa. This field / IE, e.g., DRX-MeasGap-Alignment, may be added in UE Assistanceinformation, or in drx-Config, and could extend measGapConfig.b. Option 2 may help the UE schedule its Al inference / data-collection engine only when Gaps occur and not schedule due to DRX inactivity, which is useful from many angles:i. Power efficiency, as it avoids waking up during separate Al data collection and measurement periodsii. Inference accuracy, as it ensures stable RF conditions and no PDCCH reception during data loggingiii. Standards clarity, as it makes Al-data collection intents explicit (as contrasted with implicit timing reuse).

[0060] Figure 5 shows an example of a communication system 500 in accordance with some embodiments.

[0061] In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, access network nodes 510A and 510B are depicted (which may be collectively referred to as network nodes 510), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which maybe generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0062] 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 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 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 502, including one or more access network nodes 510 and / or core network nodes 508.

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

[0064] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 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 500 may includeany 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 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0065] The UEs 512 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 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 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 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 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 508, 510 may send messages, data, and other signals to UEs 5122, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 108 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.

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

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

[0068] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 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 500 supporting different standards, protocols, or rule sets.

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

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

[0071] In some examples, one or more of the UEs 512 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 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. 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).

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

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

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

[0075] Figure 6 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (STAs) 612 (referred to individually as ST A 612A, ST A 612B, ST A 612C, ST A 612D, and STA 612E). STA 612A is served by AP 610A in a first basic service set (BSS) 620A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612E is served by AP 610D in a fourth BSS, BSS 620D. Stations 612 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 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

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

[0077] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may also provide data connectivity between STAs 612 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 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, Figure 6 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.

[0078] Figure 7 shows a wireless device 700, which may be configured to operate in communication system 500 of Figure 5 or in communication system 600 of Figure 6. The wireless device 700 may be alternatively referred to as a UE 700, like a UE 512 within the context of communication system 500, or as a station (STA) 700 or as a non-access-point station (non-AP STA) 700, like a STA 612 within the context of the communication system 600, 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 limitedto, 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.

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

[0080] In particular embodiments, wireless device 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain embodiments of wireless device 700 may include all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one embodiment of wireless device 700 to another. In general, in a particular embodiment of wireless device 700, processing circuitry 702, input / output interface 706, power source 708, memory 710, and communication interface 712 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 700. Further, certain embodiments of wireless devices 700 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0081] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructionsstored as machine-readable computer programs in the memory 710. The processing circuitry 702 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 702 may include multiple central processing units (CPUs). The processing circuitry 702 may be configured to cause the wireless device 700 to perform the methods as described with reference to Figure 2.

[0082] In the example, the input / output interface 706 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 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

[0085] The memory 710 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 710 may allow wireless device 700 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0086] The processing circuitry 702 may be configured to communicate with an access network or other network via or using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 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 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 andreceiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0087] In the illustrated embodiment, communication functions of the communication interface 712 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.

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

[0089] As another example, wireless device 700 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 700 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.

[0090] Wireless device 700, 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-limitingexamples 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 700 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 700 shown in Figure 7.

[0091] As yet another specific example, in an loT scenario, wireless device 700 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 700 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 700 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 700 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.

[0092] In practice, any number of wireless devices 700 may be used together with respect to a single use case. For example, a first wireless device 700 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 700 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 700 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 700 can also include more than one of the functionalities described above. For example, wireless device 700 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0093] Figure 8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 800 may be configured to operate in communication system 500 of Figure 5, like network nodes 508 or 510, or in communication system 600 of Figure 6, like an AP 610 or a station 612. 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).

[0094] Network nodes 800 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 800 may be a relay node or a relay donor node controlling a relay. Network nodes 800 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).

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

[0096] In particular embodiments, network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. In general, in a particular embodiment of network node 800, processing circuitry 802, memory 804, communication interface 806, and power source 808 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 800.

[0097] The network node 800 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 800 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 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 804 or portions of memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 800.

[0098] The processing circuitry 802 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 804, to provide network node 800 functionality. For example, the processing circuitry 802 may be configured to cause the network node 800 to perform the methods as described with reference to Figure 3.

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

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

[0101] The communication interface 806 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 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 700 may be capable of wireless communication and communication interface 806 may also include radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, an antenna 810. Particular embodiments of radio front-end circuitry 818 include filter(s) 820 and amplifier(s) 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio frontend circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 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 818 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal(s) may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0102] In certain alternative embodiments, network node 800 may be capable of wireless communication but does not include separate radio front-end circuitry 818, instead, theprocessing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

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

[0104] The antenna 810, communication interface 806, and / or the processing circuitry 802 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 800. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 800. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

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

[0107] Figure 9 is a block diagram illustrating a virtualization environment 900 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 900 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 900 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.

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

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

[0110] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.[OHl] In the context of NFV, each of the VMs 908 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 908, and that part of hardware 904 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 908 on top of the hardware 904 and corresponds to an application 902.

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

[0113] 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 understoodthat these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0114] 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.Additional information on the disclosure is provided by 3GPP TSG-RAN WG2 #130 R2- 2504132, the text of which can be found below.3GPP TSG-RAN WG2 #130 R2-2504132 St. Julian’s, Malta, May 19th - 23rd, 2025Agenda Item: 8.3.4 Data collectionSource: EricssonTitle: Data collection for network sided and UE sided models Document for: Discussion1 IntroductionThe study item on Artificial Intelligence (AI)ZMachine Learning (ML) for mobility in NR was approved in RAN plenary #102 [1], One of the objectives included in the SID is the Life Cycle Management (LCM) of the AI / ML model:• Potential Al mobility specific enhancement should be based on the Rel19 AI / ML-air interface WID general framework (e.g. LCM, performance monitoring etc) [RAN2]This contribution discusses the aspects related to the data collection for both NW sided and UE sided AI / ML model, as part of the LCM framework.2 Discussion2.1 IntroductionIn RAN2#129bis meeting, the following agreements have been taken:As a baseline, use the Al ML PHY NW-side data collection procedures, configuration and reporting framework.Study UE side data collection configuration, taking Al ML PHY relevant procedure as baseline. Postpone UE side data collection transfer discussion until further progress is made in Al ML PHYin R20.Based on these agreements, this contribution divides the data collection subject into three parts where the first is related to overall principles for data collection, the second part is related to data collection for network side models and the final part is related to data collection for UE side models. Data collection needs to be performed to provide input to AI / ML models for model training or inference. The data collection could consist of performing measurements which are used as input to the model.Data collection may interfere with other actions or events in the network, and it should therefore be transparent what data collection procedures the UE is doing since it can influence the rest of the network. The network should therefore also be able to terminate and initiate data collection procedures to limit the effect of data collection on other parts of the network.The network configures the UE to initiate / terminate data collection procedures.On the same topic, if data collection measurement collides with other RRM measurements and both cannot be carried out, RRM measurement should have higher priority than data collection measurements. User plane data should also have higher priority than data collection.Priority between data collection and RRM measurements or user plane data needs to be considered.2.2 Data collection for network sided model2.2.1 Data collection for inferenceData collection for inference purpose requires the UE to send data when in RRC_CONNECTED state to the network. The network therefore needs to configure the data collection and the relevant reporting of the UE, in a similar way as done for the legacy RRM measurements. For this reason, the simplest way to implement that, in terms of standardization effort, is to reuse the RRM measurement framework.RRM measurement framework is used for configuration of data collection and reporting of the collected data from UE to the NW, for inference purpose.Depending on the scenarios, the network may need to receive data from the UE periodically (e.g. to provide it as input to the AI / ML model for continuous inference) or it may need to receive the collected data only when a certain event is fulfilled (e.g. in case of handover, to predict the quality of neighbor cells). For this reason, both periodical and event triggered reporting can be supported for the data collection from the UE.Event triggered report and periodical report are used for data collection for inference purposes.2.2.2 Data collection fortrainingTo ensure that the training of network-side machine learning models benefit from comprehensive and representative data, it is important to collect data from the UE regardless of its state. Additionally, we need flexibility in the data collection process by allowing the UE to perform data logging and collection in both RRC_CONNECTED and RRCJDLE / INACTIVE states, maximizing the coverage while minimizing the signaling impact.Data collection fortraining purpose of network side model should be supported to be done by the UE in RRCJDLE / INACTIVE state or RRC_CONNECTED state.In scenarios where the UE is in RRCJDLE or RRCJNACTIVE state, minimizing network signaling while still enabling useful data collection would be useful. Hence, reusing the established procedures of logged Minimization of Drive Tests (MDT), which allow the UEs to collect and store measurement data for later retrieval by the network, offers a low-overhead mechanism for data collection for training.For data collection when the UE is in RRCJDLE / INACTIVE state, a solution based on logged MDT principles can be reused.For UEs in RRC_CONNECTED state, it is important to collect data without disrupting ongoing sessions. It is also important to think about reducing unnecessary uplink traffic and enable the network to retrieve the data at an optimal time, maintaining efficiency and session continuity.Therefore, the UE should be able to locally log relevant measurement data and simply notify the network about the availability of such logs.For data collection when the UE is in CONNECTED state, the UE logs the data and reports the availability of data to the network.The simplest solution for retrieval of the data and which require the least specification impacts is to reuse the UE Information Request / Response procedure.The UE information request / response procedure is used to retrieve the logged data from the UE.It should be investigated if assistance information should be provided by the UE to facilitate and improve the quality of the inference and training of the network sided model. Since the study item is almost completed, this can be done in the work item phase.Possible assistance information from the UE to the network can be considered in the work item.2.3 Data collection for the UE sided modelData collection for UE-side models is similar to network sided models in the way that it can be divided into data collection fortraining and data collection for inference.2.3.1 Data collection for inferenceData collection for inference of UE side models are discussed in another Ericsson contribution submitted to this meeting and is therefore left out here and readers are referred to 0.2.3.2 Data collection fortrainingCollection of data fortraining should preferably be done in all RRC state to maximize the opportunities for data collection. The collection can be divided into two parts where one part is collection of data in RRCJDLE / INACTIVE state and the other one is collection of data in RRC_CONNECTED state.Data collection for training purposes of UE-side models can be done in either RRCJDLE / INACTIVE or RRC_CONNECTED state.2.3.2.1 Data collection in IDLE / INACTIVE stateDeta collection for UEs in RRCJDLE / INACTIVE states can be done without any specific configuration required from the network, since the UE actions in RRCJDLE / INACTIVE are to a large extent up to UE implementation. The data collection in RRCJDLE / INACTIVE states can most likely be up to UE implementation too. Possibly, the requirements on the measurements may need to be looked into.Data collection for UE sided models in RRCJDLE / INACTIVE state is mainly up to UE implementation.The measurement requirements for RRCJDLE / INACTIVE can be checked for data collection purposes.2.3.2.2 Data collection in RRC_CONNECTED stateWhen a UE is in RRC_CONNECTED state and collects measurements from its serving frequency, the data collection for model training may often not impact ongoing procedures or measurements.However, if a lot of data needs to be collected, it could be cumbersome for the UE to perform the data collection during ongoing transmissions / receptions and other measurements. A possibility for the UE could be to perform the data collection during inactive periods in RRC_CONNECTED when there are no ongoing data transmissions / receptions.The UE preferably performs data collection in RRC_CONNECTED when there are no ongoing data transmissions / receptions.When a UE is in RRC_CONNECTED state and collects measurements from its serving frequency, no additional configuration is needed from the network as no measurement gaps are required.UEs can perform intra-frequency measurement collection for UE side models without any configuration update from the network.However, measurements on other frequencies may require periods, such as measurement gaps, when the UE is not required to monitor PDCCH or perform data transmissions / reception on the serving frequency. It is proposed that RAN2 discusses whether measurement gaps can be configured for the UE to perform data collection for model training and / or inference.Discuss whether measurement gaps can be configured for the purpose of data collection and / or model training.ConclusionBased on the discussion in the previous sections we propose the following:Observation 1 UEs can perform intra-frequency measurement collection for UE side models without any configuration update from the network.Based on the discussion in the previous sections we propose the following:Proposal 1 The network configures the UE to initiate / terminate data collection procedures. Proposal 2 Priority between data collection and RRM measurements or user plane data needs to be considered.Proposal 3 RRM measurement framework is used for configuration of data collection and reporting of the collected data from UE to the NW, for inference purpose.Proposal 4 Event triggered report and periodical report are used for data collection for inference purposes.Proposal 5 Data collection for training purpose of network side model should be supported to be done by the UE in RRCJDLE / INACTIVE state or RRC_CONNECTED state.Proposal 6 For data collection when the UE is in RRCJDLE / INACTIVE state, a solution based on logged MDT principles can be reused.Proposal 7 For data collection when the UE is in CONNECTED state, the UE logs the data and reports the availability of data to the network.Proposal 8 The UE information request / response procedure is used to retrieve the logged data from the UE.Proposal 9 Possible assistance information from the UE to the network can be considered in the work item.Proposal 10 Data collection fortraining purposes of UE-side models can be done in either RRCJDLE / INACTIVE or RRC_CONNECTED state.Proposal 11 Data collection for UE sided models in RRCJDLE / INACTIVE state is mainly up to UE implementation.Proposal 12 The measurement requirements for RRCJDLE / INACTIVE can be checked for data collection purposes.Proposal 13 The UE preferably performs data collection in RRC_CONNECTED when there are no ongoing data transmissions / receptions.Proposal 14 Discuss whether measurement gaps can be configured for the purpose of data collection and / or model training.ReferencesRP-234055, SID: Study on Artificial Intelligence (Al) / Machine Learning (ML) for mobility in NR R2-2504131 - Inference and report configuration of UE sided modelThe following numbered statements provide additional information on the present disclosure:Group A Statements1. A method performed by a wireless device for Machine Learning, ML model data collection, the method comprising:receiving, from a network node, a data collection configuration; and performing data collection, based on the data collection configuration, during inactive periods.2. The method of statement 1, wherein the inactive periods are scheduled while the wireless device is in a Radio Resource Control, RRC CONNECTED state.3. The method of any preceding statement further comprising, prior to receiving the data collection configuration:transmitting, to the network node, wireless device capability information.4. The method of any preceding statement further comprising, by the wireless device prior to receiving the data collection configuration:transmitting, to the network node, a configuration request to be configured with inactive periods.5. The method of statement 4, wherein the configuration request comprises one or more of:a request to be configured with discontinuous reception, DRX;a request to be configured with a new type of inactivity period;a request to be configured with measurement gaps;an indication of the reason for the configuration request; andan indication of one or more desired measurement frequencies.6. The method of any of statements 4 and 5, wherein the configuration request is sent in a RRC message.7. The method of statement 6, wherein the RRC message comprises a new indication and / or a new Information Element, IE.8. The method of any of statements 4 to 7 further comprising receiving, from the networknode, an indication of rejection of the configuration request.9. The method of statement 8, wherein the indication of rejection includes a reason for the rejection.10. The method of any of statements 4 to 9 wherein, if the configuration request is not accepted, the wireless device waits a predetermined period of time before transmitting a further configuration request.11. The method of any preceding statement, wherein the data collection configuration comprises one or more of:a discontinuous reception, DRX, configuration;a new type of inactivity period configuration;a measurement gap configuration; anda data collection supervision timer configuration.12. The method of any preceding statement, wherein the inactive periods during which data is collected comprise one or more of:discontinuous reception, DRX, periods;a new type of inactivity periods; andmeasurement gap periods.13. The method of any preceding statement wherein performing data collection comprises logging the collected data.14. The method of statement 13, wherein the logged data comprises collection time information.15. The method of any preceding statement, wherein the wireless device is a dual connectivity wireless device, and wherein the wireless device receives two independent data collection configurations.16. The method of any preceding statement, wherein data collected during the data collection is for use in ML model training and / or ML model inference.17. The method of any of the previous statements, further comprising:providing user data; andforwarding the user data to a host via the transmission to the network node.Group B Statements18. A method performed by a network node for Machine Learning, ML model data collection, the method comprising:transmitting, to a wireless device, a data collection configuration, for configuring wireless device data collection during inactive periods.19. The method of statement 18, wherein the inactive periods are scheduled while the wireless device is in a Radio Resource Control, RRC CONNECTED state.20. The method of any of statements 18 and 19, wherein the data collection configuration comprises one or more of:a DRX configuration;a new type of inactivity period configuration;a measurement gap configuration; anda data collection supervision timer configuration.21. The method of any of statements 18 to 20, wherein the inactive periods during which data is collected comprise one or more of:discontinuous reception, DRX, periods;a new type of inactivity periods; andmeasurement gap periods.22. The method of any of statements 18 to 21, wherein the wireless device is a dual connectivity wireless device and wherein the network node transmits two independent data collection configurations to the wireless device.23. The method of any of statements 18 to 22, further comprising, prior to transmitting the data collection configuration:receiving, from the wireless device, wireless device capability information.24. The method of any of statements 18 to 23, further comprising, prior to transmitting the data collection configuration:receiving, from the wireless device, a configuration request to be configured with inactive periods.25. The method of statement 24 wherein the configuration request comprises one or more of:a request to be configured with discontinuous reception, DRX;a request to be configured with a new type of inactivity period;a request to be configured with measurement gaps;an indication of the reason for the configuration request; andan indication of one or more desired measurement frequencies.26. The method of any of statements 24 and 25, wherein the configuration request is sent in a RRC message.27. The method of statement 26, wherein the RRC message comprises a new indication and / or a new Information Element, IE.28. The method of any of statements 24 to 27 further comprising evaluating the configuration request and accepting or rejecting the configuration request.29. The method of statement 28 wherein, if the configuration request is rejected, the network node transmits an indication of rejection to the wireless device, or ignores the configuration request.30. The method of statement 29 wherein, when an indication of rejection is sent, the indication includes one or more of:a reason for the rejection; anda predetermined time period the wireless device should wait before transmitting a further configuration request.31. The method of any of statements 18 to 30, wherein data collected during the data collection is for use in ML model training and / or ML model inference.32. The method of any of statements 18 to 31 further comprising transmitting, to the wireless device, a use indication that the wireless device should use inactive periods for data collection.33. The method of statement 32, wherein the use indication is transmitted with the data collection configuration, or wherein the use indication is transmitted separately to the data collection configuration.34. The method of any of statements 18 to 33, further comprising:obtaining user data; andforwarding the user data to a host or a user equipment.C Statements35. A wireless device (512, 612, 700) for Machine Learning, ML model data collection, comprising:processing circuitry (702) configured to cause the wireless device to perform any of the operations of any of the Group A statements; anda power source (708) configured to supply power to the processing circuitry (702).36. A network node (510, 610, 800) for Machine Learning, ML model data collection, the network node comprising:processing circuitry (802) configured to cause the network node to perform any of the operations of any of the Group B statements;a power source (808) configured to supply power to the processing circuitry (802).37. A wireless device for Machine Learning, ML model data collection, the wireless device comprising:one or more antennas;communication interface connected to the one or more antennas and to processing circuitry;the processing circuitry being configured to cause the wireless device to perform any of the operations of any of the Group A statements;an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply powerto the wireless device.38. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of the Group A statements and the Group B statements.39. A wireless device (512, 612, 700) configured to perform the method of any of the Group A statements.40. A wireless device (512, 612, 700) comprising processing circuitry (702) and a memory (710), said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of any of the Group A statements.41. A network node (510, 610, 800), configured to perform the method of any of the Group B statements.42. A network node (510, 610, 800) comprising processing circuitry (802) and a memory (804), said memory containing instructions executable by said processing circuitry whereby said network node is operative to perform the method of any of the Group B statements.

Claims

Claims1. A method performed by a wireless device (700) for Machine Learning, ML, model data collection, the method comprising:receiving, from a network node (800), a data collection configuration; and performing data collection, based on the data collection configuration, during inactive periods.

2. The method of claim 1, wherein the inactive periods are scheduled while the wireless device (700) is in a Radio Resource Control, RRC CONNECTED state.

3. The method of any of claims 1 and 2 further comprising, prior to receiving the data collection configuration:transmitting, to the network node (800), wireless device capability information.

4. The method of any of claims 1 to 3 further comprising, by the wireless device (700) prior to receiving the data collection configuration:transmitting, to the network node (800), a configuration request to be configured with inactive periods.

5. The method of claim 4, wherein the configuration request comprises one or more of:a request to be configured with discontinuous reception, DRX;a request to be configured with a new type of inactivity period;a request to be configured with measurement gaps;an indication of the reason for the configuration request; andan indication of one or more desired measurement frequencies.

6. The method of any of claims 4 and 5, wherein the configuration request is sent in a RRC message, optionally wherein the RRC message comprises a new indication and / or a new Information Element, IE.

7. The method of any of claims 4 to 6 further comprising receiving, from the network node (800), an indication of rejection of the configuration request, optionally wherein the indication of rejection includes a reason for the rejection.

8. The method of any of claims 4 to 7 wherein, if the configuration request is not accepted, the wireless device (700) waits a predetermined period of time before transmitting a further configuration request.

9. The method of any of claims 1 to 8, wherein the data collection configuration comprises one or more of:a discontinuous reception, DRX, configuration;a new type of inactivity period configuration;a measurement gap configuration; anda data collection supervision timer configuration.

10. The method of any of claims 1 to 9, wherein the inactive periods during which data is collected comprise one or more of:discontinuous reception, DRX, periods;a new type of inactivity periods; andmeasurement gap periods.

11. The method of any of claims 1 to 10 wherein performing data collection comprises logging the collected data, optionally wherein the logged data comprises collection time information.

12. The method of any of claims 1 to 11, wherein the wireless device (700) is a dual connectivity wireless device, and wherein the wireless device (700) receives two independent data collection configurations.

13. The method of any of claims 1 to 12, wherein data collected during the data collection is for use in ML model training and / or ML model inference.

14. A method performed by a network node (800) for Machine Learning, ML model data collection, the method comprising:transmitting, to a wireless device (700), a data collection configuration, for configuring wireless device data collection during inactive periods.

15. The method of claim 14, wherein the inactive periods are scheduled while the wireless device (700) is in a Radio Resource Control, RRC CONNECTED state.

16. The method of any of claims 14 and 15, wherein the data collection configuration comprises one or more of:a DRX configuration;a new type of inactivity period configuration;a measurement gap configuration; anda data collection supervision timer configuration.

17. The method of any of claims 14 to 16, wherein the inactive periods during which data is collected comprise one or more of:discontinuous reception, DRX, periods;a new type of inactivity periods; andmeasurement gap periods.

18. The method of any of claims 14 to 17, wherein the wireless device (700) is a dual connectivity wireless device and wherein the network node (800) transmits two independent data collection configurations to the wireless device (700).

19. The method of any of claims 14 to 18, further comprising, prior to transmitting the data collection configuration:receiving, from the wireless device (700), wireless device capability information.

20. The method of any of claims 14 to 19, further comprising, prior to transmitting the data collection configuration:receiving, from the wireless device (700), a configuration request to be configured with inactive periods.

21. The method of claim 20 wherein the configuration request comprises one or more of:a request to be configured with discontinuous reception, DRX;a request to be configured with a new type of inactivity period;a request to be configured with measurement gaps;an indication of the reason for the configuration request; andan indication of one or more desired measurement frequencies.

22. The method of any of claims 20 and 21, wherein the configuration request is sent in a RRC message, optionally wherein the RRC message comprises a new indication and / or a newInformation Element, IE.

23. The method of any of claims 20 to 22 further comprising evaluating the configuration request and accepting or rejecting the configuration request.

24. The method of claim 23 wherein, if the configuration request is rejected, the network node (800) transmits an indication of rejection to the wireless device (700), or ignores the configuration request, optionally wherein when an indication of rejection is sent, the indication includes one or more of:a reason for the rejection; anda predetermined time period the wireless device (700) should wait before transmitting a further configuration request.

25. The method of any of claims 14 to 24, wherein data collected during the data collection is for use in ML model training and / or ML model inference.

26. The method of any of claims 14 to 25 further comprising transmitting, to the wireless device (700), a use indication that the wireless device (700) should use inactive periods for data collection.

27. The method of claim 26, wherein the use indication is transmitted with the data collection configuration, or wherein the use indication is transmitted separately to the data collection configuration.

28. A wireless device (512, 612, 700) for Machine Learning, ML model data collection, comprising:processing circuitry (702) configured to cause the wireless device to: receive, from a network node, a data collection configuration; and perform data collection, based on the data collection configuration, during inactive periods; anda power source (708) configured to supply power to the processing circuitry (702).

29. A network node (510, 610, 800) for Machine Learning, ML model data collection, the network node comprising:processing circuitry (802) configured to cause the network node to transmit, to a wireless device, a data collection configuration, for configuring wireless device data collectionduring inactive periods; anda power source (808) configured to supply power to the processing circuitry (802).

30. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of claims 1 to 27.