Transmitting device, receiving device, user equipment, radio network node, and methods performed therein

Abstract

A method performed by a transmitting device (120) for handling data collection in a wireless communication network, the method comprising transmitting (512) a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions, receiving (513) a command or a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

Description

[0001] TRANSMITTING DEVICE, RECEIVING DEVICE, USER EQUIPMENT, RADIO

[0002] NETWORK NODE, AND METHODS PERFORMED THEREIN

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a transmitting device, a receiving device, a user equipment (UE), a radio network node, and methods performed therein regarding communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as collecting data for machine learning (ML) model training or modelling, in a wireless communication network. The project leading to this application has received funding from the European Union’s Horizon Europe research and innovation programme under grant agreement No 101095759.

[0005] BACKGROUND

[0006] In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, servers, computers, communicate via an Access Network (AN), such as a radio access network (RAN) or a wired access network, with one or more core networks (CNs). The AN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the access node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the access node.

[0007] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate, e.g., enhanced data rate and radio capacity. In some RANs, e.g., as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises, and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0008] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and present and coming 3GPP releases, such as New Radio (NR) and extensions, are being worked on. The EPS comprises of the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

[0009] With the emerging 5G technologies such as new radio (NR), the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.

[0010] Power amplifiers (PA) are essential for wireless communication to work. Herein there is a focus on power amplifiers in a transmitting node which has the purpose to as linearly as possible increase the signal power with a certain targeted gain factor. PAs are however not ideal and non-linear distortions will impact the signal when passing through the PA.

[0011] PA back-off is a mechanism to adjust the operating point of a PA, such that the distortion of the signal due to the PA non-linearity can be within a certain target, e.g., constraints on error vector magnitude (EVM) for in-band distortion, and constraints on adjacent carrier leakage ratio (ACLR) for out of band (OOB) emissions, for given transmit signal parameters, e.g., a selected modulation scheme.

[0012] There are other means to linearize the PA, such as using a pre-distortion in digital domain, also referred to as digital pre-distortion (DPD). The purpose of such pre-distorter is for the combined signal after going through the DPD (digital) and PA (analogue) to be amplified with the targeted gain factor mentioned above. Hence, such a scheme will typically make the PA operation more linear, but still not remove non-linear effects when transmitting with a low enough back-off, and hence, there will still be limitations on how well one can linearize the signal. To design the DPD, a feedback-loop is typically required, in which case the DPD can be designed based on the signal coming into the PA and / or DPD and the signal that is fed back after PA.

[0013] The overall impairments imposed on a signal at the transmitter, or receiver, are typically measured using distortion measures such as the error-vector-magnitude (EVM), see 3GPP TS 38.104 v18.2.0, “Base Station (BS) radio transmission and reception; NR”for the EVM definition in NR. Such impairments can, e.g., come from the abovementioned power-amplified non-linearities but also from other effects, such as phase noise, in-phase(l) / quadrature (Q) gain and phase imbalance, unwanted direct current (DC) levels and digital to analogue converter (DAC) noise.

[0014] Depending on the operating level of the receiver thermal noise, and level of interference, different levels of EVM will impact overall throughput of the wireless link. In simple terms, if the distortion caused by transmission (Tx) EVM is greater than the thermal noise I interference I reception (Rx) EVM, the overall performance will be limited by distortions added already at the transmitter.

[0015] In the 3GPP specifications there are requirements for the largest values of EVM that can be tolerated, see for instance 3GPP TS 38.104 v18.2.0, “Base Station (BS) radio transmission and reception; NR” for the required EVM values for different modulation schemes as shown below. As can be seen, lower constellation orders can tolerate higher impairment levels, and they operate also on lower signal to noise ratios (SNR). The required EVM values are specified in section 6.5.2.2 of 3GPP TS 38.104 v18.2.0, “Base Station (BS) radio transmission and reception; NR” and are listed in Table 1 below.

[0016] Table 1: EVM requirements for BS from 3GPP TS 38.104 v18.2.0, “Base Station (BS) radio transmission and reception; NR”

[0017] Power class.

[0018] A UE and a base station is typically associated with a declared output power class. Such power class determines the maximum output power level allowed, within a specified tolerance ± X dB.

[0019] Maximum power reduction.

[0020] The UE is allowed to reduce the maximum output power due to higher order modulations and transmit bandwidth configurations. This is called maximum power reduction (MPR) and hence defines an allowed maximum power reduction depending on certain conditions.

[0021] Additional MPR (A-MPR) is also defined that can be signalled by the network and is associated with different frequency bands.

[0022] For more details, see Subclause 6.2 in 3GPP TS 38.101 v18.0.0, ’’User Equipment (UE) radio transmission and reception; NR”.

[0023] AI / ML at the physical layer.

[0024] Artificial Intelligence (Al), Machine Learning (ML) have been investigated as promising tools to optimize the design of air-interface in wireless communication networks in both academia and industry. Example use cases include using autoencoders for channel state information (CSI) compression to reduce the feedback overhead and improve channel prediction accuracy and using deep neural networks for classifying line of sight (LOS) and non line of sight (NLOS) conditions to enhance the positioning accuracy see RP-213599, “Study on Artificial Intelligence (Al) / Machine Learning (ML) for NR Air Interface”, 3GPP, Dec. 2021. AI / ML-assisted mobility, traffic, and radio channel prediction are outlined as example enablers for next generation mobile networks see “Next generation mobile networks' enablers: Machine learning-assisted mobility, traffic, and radio channel prediction”, IEEE Communications Magazine, 2023. Standardizing an Al-based air interface.

[0025] In 3GPP NR standardization work, a new release 18 study item (SI) on AI / ML for NR air interface has started since May 2022 see RP-213599, “Study on Artificial Intelligence (Al) / Machine Learning (ML) for NR Air Interface”, 3GPP, Dec. 2021. The study item is exploring the benefits of augmenting the air-interface with features enabling improved support of AI / ML based algorithms for enhanced performance and / or reduced complexity / overhead. Through studying a few selected use cases, such as CSI feedback, beam management and positioning, this SI aims at laying the foundation for future airinterface use cases leveraging AI / ML techniques.

[0026] AI / ML-based PA post-distortion.

[0027] One application of interest for AI / ML at the physical layer, not yet considered in the current standardization initiative, is the use of PA post-distortion, i.e. , the receiver compensating for non-linear distortion added at the transmitter. One example of such application is shown in Fig. 1 where a system is compared using a linear PA (‘Baseline, linear PA’), a compressed non-linear PA transmission with no attempt to compensate it at the receiver (‘Baseline, nonlinear PA’) and a compressed PA transmission with AI / ML- based receiver compensation (‘NN, nonlinear PA’). Fig. 1 shows Link throughput performance with an AI / ML-based PA post-distortion

[0028] As can be seen, the performance can be significantly improved through the use of AI / ML in this use case. We refer the interested reader to “A deep learning receiver for non-linear transmitter", IEEE Access, 2023 for additional results.

[0029] AI / ML model life cycle management (LCM).

[0030] To support AI / ML models in the network life-cycle management functionality needs to be defined. A possible high-level description of model LCM for Al on physical layer (PHY) can include the stages and data / signal flows depicted in Fig. 2 A detailed description of different LCM stages can be found in R1-2208908, Discussion on general aspects of Al ML framework, Ericsson. Fig.2 shows functional framework of model LCM for Al on PHY.

[0031] Data Collection is a stage that collects and provides input data, such as raw data or pre-processed data, for Model Training, Model inference, and Model Monitoring. AI / ML algorithm specific data preparation, e.g., data ingestion and data refinement, is not carried out in the Data Collection stage. Model Training is a process that uses featured data in terms of training datasets and validation datasets to train an AI / ML model.

[0032] Model deployment is a process of converting an AI / ML model into an executable form and delivering the AI / ML model to a target UE or base station (BS) for inference where model inference is to be performed.

[0033] Model inference is a process of using a deployed AI / ML model to produce a set of outputs based on a set of featured inputs.

[0034] Model monitoring is a process that monitors drifts in data and model or monitors performance metrics after the AI / ML model has been deployed. Based on the monitored performance, decisions like model activation, deactivation, switching, fallback, and / or selection can be taken.

[0035] Data collection.

[0036] Traditionally, physical layer algorithms have been designed to a large extent in simulated baseband implementations of the physical layer and radio channel models. This has shown to be a powerful approach later also in deployments of algorithms in the field with realistic hardware due to the generalizability of human-designed algorithms based on radio theory. However, this mindset needs to shift with the increased use of AI / ML in the networks. That is, when moving to more data-driven algorithms, it is important that the data that the algorithm is trained on reflects the data distribution seen later in deployment. Hence, supporting data collection for different AI / ML use cases is essential to fully exploit AI / ML as a tool for physical layer algorithm development.

[0037] One such support is added in WO2024 / 149803, where an Al-empowered receiver is assumed to use the received signal as input to an AI / ML model and define a computational graph all the way to the bit / symbol estimation at the receiver, e.g. the soft demapper. Hence, in this case we need to know the bits / symbols transmitted and use them as labels in the AI / ML model training. This is what WO2024 / 149803achieves by defining a common understanding between the transmitting node and the receiving node on what bits / symbols were transmitted, without explicitly transmitting such labels over-the- air.

[0038] SUMMARY

[0039] As part of developing embodiments herein one or more problems have first been identified. For AI / ML receiver use cases, e.g., the PA post-distortion use case above, where the AI / ML model output depends on different operating points of the transmitter hardware they need to be trained on the operating conditions expected in deployment. Currently, there is no way to generate such data and hence such AI / ML models are currently limited in implementation to simulated setups, where such operating conditions can be controlled / modelled. This poses a severe risk to the performance of the AI / ML models when deployed the field.

[0040] Prior art WO2024 / 149803 only enables data collection in the general case of an Al-empowered receiver and does not detail how different Tx hardware operating conditions would be considered in data collection.

[0041] An object herein is to provide a mechanism to handle communication efficiently in the wireless communication network.

[0042] According to an aspect the object is achieved, according to embodiments herein, by providing a method performed by a transmitting device for handling data collection in a wireless communication network. The transmitting device transmits, to a receiving device, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The transmitting device receives, from the receiving device, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions. This, thus, allows the receiving device to steer the Tx data generated based on different Tx hardware operating conditions such as operating points of the transmitting device.

[0043] According to another aspect the object is achieved, according to embodiments herein, by providing a method performed by a receiving device for handling data collection in a wireless communication network. The receiving device receives, from a transmitting device, a capability indication indicating capability to generate data according to one or more Tx hardware conditions. The receiving device transmits, to the transmitting device, a request for data collection according to a Tx hardware operating condition. This enables the receiving device to steer the Tx data generated based on different Tx hardware operating conditions such as operating points of the transmitting device.

[0044] According to an aspect the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling data collection in a wireless communication network. The UE transmits to a radio network node, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions; and receives, from the radio network node, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

[0045] According to an aspect the object is achieved, according to embodiments herein, by providing a method performed by a radio network node for handling data collection in a wireless communication network. The radio network node receives, from a UE, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The radio network node transmits to the UE, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

[0046] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the receiving device, the transmitting device, the UE, and the radio network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the receiving device, the transmitting device, the UE and the radio network node , respectively.

[0047] According to yet another aspect the object is achieved, according to embodiments herein, by providing a receiving device, a transmitting device, a UE, and a radio network node configured to perform the methods herein, respectively.

[0048] Thus, it is herein provided a transmitting device for handling data collection in a wireless communication network. The transmitting device is configured to transmit, to a receiving device, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The transmitting device is further confiogured to receive, from the receiving device, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

[0049] It is further provided a receiving device for handling data collection in a wireless communication network. The receiving device is configured to receive, from a transmitting device, a capability indication indicating capability to generate data according to one or more Tx hardware conditions. The receiving device is configured to transmit, to the transmitting device, a request for data collection according to a Tx hardware operating condition. According to an aspect the object is achieved, according to embodiments herein, by providing a UE for handling data collection in a wireless communication network. The UE is configured to transmit to a radio network node, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The UE is configured to receive, from the radio network node, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

[0050] According to another aspect the object is achieved, according to embodiments herein, by providing a method performed by a radio network node for handling data collection in a wireless communication network. The radio network node receives, from a UE, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The radio network node transmits to the UE, a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

[0051] It is further herein disclosed two embodiments, for DL and UL training data generation respectively, that are outlined for the support of data collection for AI / ML receiver use cases, where a receiver ML model, also referred to as AI / ML model, is impacted by different Tx hardware operating conditions or operating points of the transmitter hardware. Means for the receiving device to control the transmitting device are introduced to ensure that a diverse enough data set can be collected. Such Tx hardware operating conditions could for example be to operate under a specific EVM level, introducing a level of distortion to the transmitter signal.

[0052] Thus, embodiments herein handle data collection to train ML models efficiently in the wireless communication network.

[0053] BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0055] Fig. 1 shows a Link throughput performance with a AI / ML-based PA postdistortion;

[0056] Fig. 2 shows a flowchart of a Model LCM according to prior art;

[0057] Fig. 3 shows a wireless communication network according to embodiments herein;

[0058] Fig. 4 shows a setup according to some embodiments herein;

[0059] Fig. 5a shows a combined signalling scheme and flowchart according to some embodiments herein; Fig. 5b shows a flowchart according to some embodiments herein;

[0060] Fig. 5c shows a flowchart according to some embodiments herein;

[0061] Fig. 5d shows a flowchart according to some embodiments herein;

[0062] Fig. 5e shows a flowchart according to some embodiments herein;

[0063] Fig. 6 shows a combined signalling scheme and flowchart according to some embodiments herein;

[0064] Fig. 7 shows a combined signalling scheme and flowchart according to some embodiments herein;

[0065] Fig. 8 shows a schematic overview depicting a transmitting device according to embodiments herein:

[0066] Fig. 9 shows a schematic overview depicting a receiving device according to embodiments herein:

[0067] Fig. 10 shows an example of a communication system QQ100 in accordance with some embodiments;

[0068] Fig. 11 shows a UE QQ200 in accordance with some embodiments;

[0069] Fig. 12 shows a network node QQ300 in accordance with some embodiments;

[0070] Fig. 13 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 10, in accordance with various aspects described herein;

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

[0072] Fig. 15 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0073] DETAILED DESCRIPTION

[0074] Embodiments herein relate to wireless communication networks in general. Fig. 3 is a schematic overview depicting a wireless communication network 1 . The wireless communication network 1 comprises one or more ANs, such as RANs or wired ANs, and one or more CNs. The communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent wired and wireless networks such as Wi-Fi, new radio (NR), 6G, other existing wired or wireless networks, and further developments of existing wireless communications systems such as e.g., LTE or WCDMA. In the wireless communication network 1, a UE 10, for example, a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and / or a wireless terminal, is comprised communicating via the one or more AN to other UEs or one or more CNs. It should be understood by the skilled in the art that “UE” is a nonlimiting term which means any terminal, wireless communications terminal, internet of things (loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

[0075] The wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11 or first cell, of a first RAT, such as WiFi, NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the radio network node depending e.g. on the first radio access technology and terminology used. The radio network node 12 may be an access node such as a WiFi-modern or a radio network node and may be referred to as a serving radio network node, master node, or serving secondary network node, wherein the service area may be referred to as a source cell. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0076] Embodiments herein relate to a receiving device 110, which may be the UE 10 but may also be another UE or the radio network node 12 depending on communication direction. Embodiments herein further relate to a transmitting device 120, which may be the radio network node 12 but may also be the UE 10 or another UE depending on communication direction.

[0077] Fig. 4 shows a General setup between Tx and Rx node for the described embodiments herein. According to embodiments herein the transmitting device 120, such as the UE 10, transmits to the receiving device 110, such as the radio network node 12, a capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. The receiving device 110 may trigger a data collection, and transmits to the transmitting device 120, a request for data collection according to a Tx hardware operating condition to allow the receiving device 110 to steer the Tx data generated based on different operating points of the transmitting device 120. The transmitting device 120 may further transmit data to the receiving device 110 according to the commanded Tx hardware operating condition which may be used to train and build an ML model, also referred to herein as an AI / ML model.

[0078] Fig. 5a is a combined signalling scheme and flowchart according to some embodiments herein.

[0079] Action 501. The receiving device 110 may request a capability indication from the transmitting device 120.

[0080] Action 502. The transmitting device 120 transmits the capability indication indicating capability to generate data according to one or more Tx hardware operating conditions.

[0081] Action 503. The receiving device 110 triggers a data collection.

[0082] Action 504. The receiving device 110 transmits a request for data collection according to a Tx hardware operating condition to allow the receiving device 110 to steer the Tx data generated based on different operating points of the transmitter.

[0083] Action 505. The transmitting device 120 may further transmit data to the receiving device 110 according to the commanded Tx hardware operating condition. Thus, the transmitting device 120 may provide data for an ML model over, for, or during one or more Tx hardware operating conditions.

[0084] The method actions performed by the transmitting device 120, such as the UE 10 or the radio network node 12, for handling data collection in the wireless communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 5b. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0085] Action 511. The transmitting device 120 may receive from the receiving device 110, a request for the capability indication.

[0086] Action 512. The transmitting device 120 transmits to the receiving device 110, the capability indication indicating capability to generate data according to one or more Tx hardware operating conditions. Action 513. The transmitting device 120 receives from the receiving device 110, the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. Thus, the receiving device 110 may request for data for training a ML model during one or more Tx hardware operating conditions. The request may further indicate which data to be collected and / or how to transmit the data to the receiving device 110. This will provide an efficent solution for collecting data to train the ML model.

[0087] Action 514. The transmitting device 120 may transmit data to the receiving device 110 according to the Tx hardware operating condition. That is, the transmitting device 120 may transmit (or collect) data for or during the Tx hardware operating condition. This may be data based the indicated data to be collected and / or how to transmit the data to the receiving device 110. The transmitting device 120 may further transmit the data and further indicate when and / or for which Tx hardware operating condition the data was generated. Thus, the transmitting device 120 may collect and / or transmit data using / during the one or more Tx hardware operating conditions and transmit the data to the receiving device 110. This will provide an efficent solution for the receiving device to know which data to use to train the ML model.

[0088] It should be noted that the one or more Tx hardware operating conditions may comprise one or more of the following:

[0089] • one or more EVM levels;

[0090] • one or more power levels;

[0091] • one or more distortion levels;

[0092] • one or more tolerance levels associated with different EVM and / or power levels;

[0093] • one or more operating modes of a digital predistortion algorithm;

[0094] • number of power amplifiers used for transmission;

[0095] • one or more back-off levels; and / or

[0096] • activation or deactivation of an envelope tracking process.

[0097] Hence, the one or more Tx hardware operating conditions may comprise one or more of the following:

[0098] • The range of EVM levels supported for one or more of o different constellation / modulation orders, e.g., different Quadrature Amplitude Modulation (QAM) such as 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM), discrete Fourier transform-spread- orthogonal frequency division multiplexing (DFT-s-OFDM), or a single carrier modulation.

[0099] • The output power levels supported. Such power levels could be associated with one or more of: o different constellation / modulation orders, e.g. 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0100] • An implicit / abstract range of operating conditions, e.g., normal, low distortion, high distortion. Since it is only of interest for the receiver to be able to generate training data corresponding to the data used during deployment, there is little reason for it to know the exact operating condition, and instead know the expected range of conditions and the ability to generate training data accordingly.

[0101] • Tolerance levels associated with different EVM I power levels. o For example, if the UE indicates supporting an EVM range of 2% to 12% for 64QAM, it could be associated with a tolerance of ±0.5%.

[0102] • A range of operating modes of a digital predistortion (DPD) algorithm, for example, 5 different modes of operation ranging from worst performing to best performing. In a related embodiment, the Tx indicates two basic modes of DPD operation - DPD on and DPD off.

[0103] • Maximum number of PAs used for transmission, or a set of possible numbers of PAs that can be used in a transmission, for example 1, 2, 4 or 8 PAs. In a related embodiment, a set of indices used to label the PAs is indicated.

[0104] • The back-off level or the relative adjustment in the back-off level associated with one or more of o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0105] • The command to activate or deactivate “envelope tracking” capability of the PA associated with one or more of o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0106] The method actions performed by the receiving device 120, such as the UE 10 or the radio network noed 12, for handling data collection in the wireless communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 5c. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0107] Action 521. The receiving device 110 may transmit to the transmitting device 120, the request for the capability indication.

[0108] Action 522. The receiving device 110 receives from the transmitting device 120, the capability indication indicating capability to generate data according to the one or more Tx hardware operating conditions.

[0109] Action 523. The receiving device 110 may trigger a data collection for training a machine learning model. The need for such data collection may be triggered by a network node from training the ML model and the data may be collected via an intermediate network node or UE.

[0110] Action 524. The receiving device 110 transmits to the transmitting device 120, the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. The receiving device 110 may request data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions. The receiving device 110 may transmit the request in DCI to generate data, while the configuration of what data to generate may be configured through RRC and a specification may outline how the training data should be mapped onto radio resources based on such request. Thus, the receiving device 110 may indicate data collection from the transmitting device 120 during one or more Tx hardware operating conditions such as one or more out of: EVM levels; one or more power levels; one or more distortion levels; one or more tolerance levels associated with different EVM and / or power levels; one or more operating modes of a digital predistortion algorithm; number of power amplifiers used for transmission; one or more back-off levels; and / or activation or deactivation of an envelope tracking process. Thus, the receiving device 110 may select and collect data for different Tx hardware operating conditions to train the ML model. Action 525. The receiving device 110 may receive the data from the transmitting device 120 according to the Tx hardware operating condition. The receiving device 110 may further receive information when and / or for which Tx hardware operating condition the data was generated. This will provide an efficent solution for the receiving device to know which data to use to train the ML model.

[0111] The method actions performed by the UE 10 for handling data collection in the wireless communication network 1 according to some embodiments herein will now be described with reference to a flowchart depicted in Fig. 5b. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0112] Action 531. The UE 10 may receive from the radio network node 12, a request for the capability indication.

[0113] Action 532. The UE 10 transmits to the radio network node 12, the capability indication indicating capability to generate data according to one or more Tx hardware operating conditions.

[0114] Action 533. The UE 10 receives from the radio network node 12, the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. Thus, the radio network node 12 may request for data for training a ML model during one or more Tx hardware operating conditions. The request may further indicate which data to be collected and / or how to transmit the data to the radio network node 12.

[0115] Action 534. The UE 10 may transmit data to the receiving device 110 according to the Tx hardware operating condition. That is, the UE 10 may transmit and / or collect data for or during the Tx hardware operating condition. The UE 10 may further transmit the data and further indicate when and / or for which Tx hardware operating condition the data was generated. Thus, the UE 10 may transmit data using the one or more Tx hardware operating conditions to the radio network node 12.

[0116] It should be noted that the one or more Tx hardware operating conditions may comprise one or more of the following:

[0117] • one or more EVM levels;

[0118] • one or more power levels;

[0119] • one or more distortion levels;

[0120] • one or more tolerance levels associated with different EVM and / or power levels;

[0121] • one or more operating modes of a digital predistortion algorithm; • number of power amplifiers used for transmission;

[0122] • one or more back-off levels; and / or

[0123] • activation or deactivation of an envelope tracking process.

[0124] Hence, the one or more Tx hardware operating conditions may comprise one or more of the following:

[0125] • The range of EVM levels supported for one or more of o different constellation / modulation orders (e.g., 64QAM, 256QAM, or for a numerically defined constellation), frequency bands, transmissions bandwidths, modulation scheme (e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation).

[0126] • The output power levels supported. Such power levels could be associated with one or more of: o different constellation / modulation orders (e.g. 64QAM, 256QAM, or for a numerically defined constellation), frequency bands, transmissions bandwidths, modulation scheme (e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation) and absolute resource allocation of the transmission bandwidth within the frequency band.

[0127] • An implicit / abstract range of operating conditions, e.g., normal, low distortion, high distortion. Since it is only of interest for the receiver to be able to generate training data corresponding to the data used during deployment, there is little reason for it to know the exact operating condition, and instead know the expected range of conditions and the ability to generate training data accordingly.

[0128] • Tolerance levels associated with different EVM I power levels. o For example, if the UE indicates supporting an EVM range of 2% to 12% for 64QAM, it could be associated with a tolerance of ±0.5%.

[0129] • A range of operating modes of a digital predistortion (DPD) algorithm, for example, 5 different modes of operation ranging from worst performing to best performing. In a related embodiment, the Tx indicates two basic modes of DPD operation - DPD on and DPD off.

[0130] • Maximum number of PAs used for transmission, or a set of possible numbers of PAs that can be used in a transmission (for example 1, 2, 4 or 8 PAs). In a related embodiment, a set of indices used to label the PAs is indicated.

[0131] • The back-off level or the relative adjustment in the back-off level associated with one or more of o different constellation / modulation orders (e.g. 64QAM, 256QAM, or for a numerically defined constellation), frequency bands, transmissions bandwidths, modulation scheme (e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation) and absolute resource allocation of the transmission bandwidth within the frequency band.

[0132] • The command to activate or deactivate “envelope tracking” capability of the PA associated with one or more of o different constellation / modulation orders (e.g. 64QAM, 256QAM, or for a numerically defined constellation), frequency bands, transmissions bandwidths, modulation scheme (e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation) and absolute resource allocation of the transmission bandwidth within the frequency band.

[0133] The method actions performed by the radio network node 12 for handling data collection in the wireless communication network 1 according to some embodiments herein will now be described with reference to a flowchart depicted in Fig. 5e. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0134] Action 541. The radio network node 12 may transmit to the UE 10, the request for the capability indication.

[0135] Action 542. The radio network node 12 receives from the UE 10, the capability indication indicating capability to generate data according to the one or more Tx hardware operating conditions.

[0136] Action 543. The radio network node 12 may trigger a data collection for training a machine learning model. The need for such data collection may be triggered by a network node from training the ML model and the data may be collected via an intermediate network node or UE.

[0137] Action 544. The radio network node 12 transmits to the UE 10, the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. The radio network node 12 may request data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions. The radio network node 12 may transmit the request in DCI to generate data, while the configuration of what data to generate may be configured through RRC and a specification may outline how the training data should be mapped onto radio resources based on such request. Thus, the radio network node 12 may indicate data collection from the UE 10 during one or more Tx hardware operating conditions such as one or more out of: EVM levels; one or more power levels; one or more distortion levels; one or more tolerance levels associated with different EVM and / or power levels; one or more operating modes of a digital predistortion algorithm; number of power amplifiers used for transmission; one or more back-off levels; and / or activation or deactivation of an envelope tracking process.

[0138] Action 545. The radio network node 12 may receive the data from the UE 10 according to the Tx hardware operating condition. The UE 10 may further receive information when and / or for which Tx hardware operating condition the data was generated.

[0139] Embodiments herein show a novel signalling between transmitting device 120 such as a network node, the UE 10 or the radio network node 12 and receiving device 110 such as the radio network node 12, a network node, or the UE 10 to acquire data in real deployments at least for the training of AI / ML-empowered receivers.

[0140] The proposed solution enables the acquisition of real deployment data at least for training of AI / ML-empowered receiving devices under, for example, different operating points of the transmitter hardware.

[0141] Embodiments herein may have an impact to existing or new standard text.

[0142] Embodiment 1 : The receiving device 110 being exemplified as a base station that controls data collection during UE hardware operating conditions for the purpose of data collection in the UL.

[0143] An overview of Embodiment 1 for UL data collection is illustrated in Fig. 6.

[0144] Fig. 6 shows an illustration of embodiment 1 with training data collection in UL, wherein the transmitting device 120 is the UE 10 and the receiving device 110 is the radio network node 12.

[0145] Action 61 : The UE 10 indicates its capability to generate data according to specific Tx hardware operating conditions. This may be done through UE capability signalling. The capability indication may indicate that the transmitting device is capable of generating data during or in one or more Tx hardware operating conditions related to EVM level and / or power levels. The capability indication may imply:

[0146] • The range of EVM levels, see more info in Action 63, supported for one or more of o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation.

[0147] • The output power levels supported. Such power levels could be associated with one or more of: o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0148] • An implicit / abstract range of operating conditions, e.g., normal, low distortion, high distortion. Since it is only of interest for the receiver to be able to generate training data corresponding to the data used during deployment, there is little reason for it to know the exact operating condition, and instead know the expected range of conditions and the ability to generate training data accordingly.

[0149] • Tolerance levels associated with different EVM I power levels. o For example, if the UE indicates supporting an EVM range of 2% to 12% for 64QAM, it could be associated with a tolerance of ±0.5%.

[0150] • A range of operating modes of a digital predistortion (DPD) algorithm, for example, 5 different modes of operation ranging from worst performing to best performing. In a related embodiment, the Tx indicates two basic modes of DPD operation - DPD on and DPD off.

[0151] • Maximum number of PAs used for transmission, or a set of possible numbers of PAs that can be used in a transmission, for example 1, 2, 4 or 8 PAs. In a related embodiment, a set of indices used to label the PAs is indicated.

[0152] • The back-off level or the relative adjustment in the back-off level associated with one or more of o different constellation / modulation orders, e.g. 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0153] • The command to activate or deactivate “envelope tracking” capability of the PA associated with one or more of o different constellation / modulation orders, e.g. 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0154] Since not only in-band requirements, e.g., EVM, exist in the standard, but also requirements related to co-existence between systems, e.g., spectrum mask and ACLR, a combination of the capabilities above could also be defined as a capability. For example, indicating the range of EVM and power level a UE supports and still comply with existing co-existence requirements, could be different among UEs and, hence, a capability that can be signalled.

[0155] It should further be noted that as an alternative to UEs indicating their capability, the same capability could be assumed across all UEs and, hence, rather what is listed above could be a mandated support level for UEs in the specification with limited or no possibility of UE differentiation based on capability. A combination of mandated specification functionality and explicit capability indication could also be foreseen. In the simplest case, a UE could indicate a capability to support data collection for different transmitter hardware operating conditions and based on that capability conform to a set of requirements in the specification, e.g., the abovementioned range of EVM levels.

[0156] Action 62: Embodiments herein are related to data collection, the need for such data collection will be triggered by a node from which the relevant AI / ML algorithm requires data, e.g., an algorithm implemented in the same network node, or an algorithm implemented at a third node that combines the data from several network nodes. Such trigger could be related to training an AI / ML model from scratch, i.e. , collecting a first data set for training, or collecting data to refine an already existing (trained) model. The AI / ML receiver algorithm may be dependent on I impacted by the operating conditions relating to the Tx hardware and, hence, if the model is not trained for all expected operating conditions, it is likely to underperform or not provide acceptable performance.

[0157] Action 63: After the need to trigger data collection is identified by the receiving device 110 such as the radio network node 12, the request is sent using a training data request, e.g., like the training data request described in WO2024 / 149803. Both the request and the information on the data to generate, e.g. modulation to be used or other Tx hardware operating conditions, see below, which physical channel to send the data on, how to map the data to radio resources could be transmitted in L1 control signalling, in DL, e.g. DCI, through medum access control (MAC) control element (CE), through RRC messages, could be defined by specification text or a combination thereof. For example, one could indicate dynamically in DCI the request to generate data, while the configuration of what data to generate is configured through RRC and the specification outlines how the training data should be mapped onto radio resources based on such request. In embodiments herein, both the actual request to the transmitting device 120 and the information about what type of data to transmit is referred to as a “request”. To allow the receiving device 110 to steer the Tx data generated based on different operating points of the transmitter hardware, the radio network node 12 indicates in the request in different embodiments:

[0158] • The level of EVM to target by the transmission. In contrast to existing requirements on EVM that puts an upper limit on the allowed error on the signal typically for different modulation orders, determined by specification text and tested through a set of performance requirements, this would rather imply a, dynamic, indication of a target EVM, where the target is not to not exceed a certain level but rather to be within a certain range of the target, see also Action 61.

[0159] • An implicit / abstract range of operating conditions, e.g. normal, low distortion, high distortion. What the different levels within such range in detail imply could be left for implementation, and for example tested through observing a lower distorting of the signal if commanding the Tx to transmit with a lower distortion level.

[0160] • The output power level to be used by the transmitting device 120. Similar to EVM, maximum output power level is today associated with a certain declared output power class. In the case of collecting data for a certain power level, the training data request would include a commanded power level to be used. This could be expressed in absolute terms, e.g., a dBm level, or in relative terms from the declared output power class of the transmitting device 120, e.g., a reduction of X dB from the declared maximum, e.g. in alignment with the UE capability mentioned in Action 61.

[0161] • Operating mode of the DPD, for example, DPD is off. If there are several possible modes of DPD operation, the mode is indicated by its index, for example, DPD operation mode 3.

[0162] • The number of PAs used in the transmission, for example, 4 PAs. If there is possibility of individual indexing of PAs, they are indicated by their indices, for example, PAs 1 , 2, 4 and 6.

[0163] • The back-off level or the relative adjustment in the back-off level.

[0164] • The command to activate or deactivate “envelope tracking” capability of the PA in the UE 10.

[0165] Action 64: The UE 10 transmits data according to the request. Embodiment 2: wherein the receiving device 110 is exemplified as the UE 10 that controls data collection during the base station hardware operating conditions for the purpose of data collection in DL.

[0166] An overview of Embodiment 2 for DL data collection is illustrated in Fig. 7

[0167] Fig. 7 shows an illustration of embodiment 2 with training data collection in DL, wherein the transmitting device 120 is the radio network node 12 and the receiving device 110 is the UE 10.

[0168] Action 71 & Action 72: In order for the UE 10 to request training data to be transmitted for specific Tx hardware operating conditions, the UE 10 needs to know that the radio network node 12 is able to generate such data. Such capability from the radio network node 12 could be sent for example broadcast in system information, or through RRC signalling. It could also be preceded by a request from the UE 10 to understand such capability of the radio network node 12, sent for example over RRC or through NAS signalling. Informing the radio network node 12 of the interest of data collection in the UE 10 could also be indicated implicitly through a UE capability, replacing a request with a signalled UE capability in Action 71. In this case, the radio network node 12 may safely send its capability to the UE 10, see Action 72, knowing the functionality is supported. For indications of the capability of the radio network node 12 see Action 61 in Embodiment 1.

[0169] Action 73: See action 62 in Embodiment 1

[0170] Action 74: See action 63 in Embodiment 1.

[0171] Action 75: With a request for training data from the UE 10, the radio network node 12 may need to indicate when and for which Tx hardware operating condition it is transmitting the training data. The information needed, and how such information is defined, may be similar as in the UL scenario where the radio network node 12 requests such data from the UE 10. Details can be found in Action 63 in Embodiment 1. It could be noted that the radio network node 12 has an interest to follow the request in Action 74 but would not be mandated to do so. For example, if the radio network node 12 is simultaneously transmitting to multiple UEs over multiple carriers, frequency bands, or even different standards, such as a multi-standard base station - using a multi standard radio (MSR), fulfilling the request of the UE 10 could be problematic, in which case explicit information on the data generated and the Tx hardware operating conditions may need to be included with the data transmission. Fig. 8 depicts embodiment of the transmitting device 120, such as the UE 10 or the radio network node 12, for handling communication or data collection of the transmitting device 120 in the wireless communication network 1 according to embodiments herein.

[0172] The transmitting device 120 may comprise processing circuitry 801 , e.g. one or more processors, configured to perform the methods herein.

[0173] The transmitting device 120 and / or the processing circuitry 801 may be configured to receive from the receiving device 110, the request for the capability indication.

[0174] The transmitting device 120 and / or the processing circuitry 801 is configured to transmit the capability indication, to the receiving device 110, indicating capability to generate data according to one or more Tx hardware operating conditions.

[0175] The transmitting device 120 and / or the processing circuitry 801 is configured to receive, from the receiving device 110, the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. This is to allow the receiving device 110 to steer the Tx data generated based on different operating points of the transmitter. The request may further indicate which data to be collected and / or how to transmit the data to the receiving device 110.

[0176] The transmitting device 120 and / or the processing circuitry 801 may be configured to transmit the data to the receiving device 110 according to the commanded Tx hardware operating condition. That is, the transmitting device 120 and / or the processing circuitry 801 may be configured to read or collect data for or during the Tx hardware operating condition. The transmitting device 120 and / or the processing circuitry 801 may be configured to transmit the data and further indicate when and / or for which Tx hardware operating condition the data was generated. Thus, the transmitting device 120 and / or the processing circuitry 801 may be configured to collect data using / during the one or more Tx hardware operating conditions and transmit the data to the receiving device 110.

[0177] It should be noted that the one or more Tx hardware operating conditions may comprise one or more of the following:

[0178] • one or more EVM levels;

[0179] • one or more power levels;

[0180] • one or more distortion levels;

[0181] • one or more tolerance levels associated with different EVM and / or power levels;

[0182] • one or more operating modes of a digital predistortion algorithm;

[0183] • number of power amplifiers used for transmission;

[0184] • one or more back-off levels; and / or • activation or deactivation of an envelope tracking process.

[0185] Hence, the one or more Tx hardware operating conditions may comprise one or more of the following:

[0186] • The range of EVM levels supported for one or more of o different constellation / modulation orders, e.g., different Quadrature Amplitude Modulation (QAM) such as 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM), discrete Fourier transform-spread- orthogonal frequency division multiplexing (DFT-s-OFDM), or a single carrier modulation.

[0187] • The output power levels supported. Such power levels could be associated with one or more of: o different constellation / modulation orders, e.g. 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g. CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0188] • An implicit / abstract range of operating conditions, e.g., normal, low distortion, high distortion. Since it is only of interest for the receiver to be able to generate training data corresponding to the data used during deployment, there is little reason for it to know the exact operating condition, and instead know the expected range of conditions and the ability to generate training data accordingly.

[0189] • Tolerance levels associated with different EVM I power levels. o For example, if the UE indicates supporting an EVM range of 2% to 12% for 64QAM, it could be associated with a tolerance of ±0.5%.

[0190] • A range of operating modes of a digital predistortion (DPD) algorithm, for example, 5 different modes of operation ranging from worst performing to best performing. In a related embodiment, the Tx indicates two basic modes of DPD operation - DPD on and DPD off.

[0191] • Maximum number of PAs used for transmission, or a set of possible numbers of PAs that can be used in a transmission, for example 1, 2, 4 or 8 PAs. In a related embodiment, a set of indices used to label the PAs is indicated.

[0192] • The back-off level or the relative adjustment in the back-off level associated with one or more of o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0193] • The command to activate or deactivate “envelope tracking” capability of the PA associated with one or more of o different constellation / modulation orders, e.g., 64QAM, 256QAM, or for a numerically defined constellation, frequency bands, transmissions bandwidths, modulation scheme, e.g., CP-OFDM, DFT-s-OFDM, or a single carrier modulation, and absolute resource allocation of the transmission bandwidth within the frequency band.

[0194] The transmitting device 120 further comprises a memory 805. The memory 805 comprises one or more units to be used to store data on, such as indications, conditions, data, Al related information, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the transmitting device 120 may comprise a communication interface 806 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0195] The methods according to the embodiments described herein for the transmitting device 120 are respectively implemented using e.g., a computer program product 807 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the transmitting device 120. The computer program product 807 may be stored on a computer-readable storage medium 808, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 808, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the transmitting device 120. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a transmitting device 120 for handling communication in a wireless communication network, wherein the transmitting device 120 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the transmitting device 120 is operative to perform any of the methods herein. Fig. 9 depicts embodiment of the receiving device 110, such as the radio network node 12 or the UE 10, for handling data collection in the wireless communication network 1 according to embodiments herein.

[0196] The receiving device 110 may comprise processing circuitry 901 , e.g. one or more processors, configured to perform the methods herein.

[0197] The receiving device 110 and / or the processing circuitry 901 may be configured to transmit to the transmitting device 120 the request for the capability indication from the transmitting device 120.

[0198] The receiving device 110 and / or the processing circuitry 901 is configured to receive from the transmitting device 120, the capability indication indicating capability to generate data according to the one or more Tx hardware operating conditions.

[0199] The receiving device 110 and / or the processing circuitry 901 may be configured to trigger a data collection for training the machine learning model.

[0200] The receiving device 110 and / or the processing circuitry 901 is configured to transmit to the transmitting device 120 the request for data collection according to the Tx hardware operating condition out of the one or more Tx hardware operating conditions. This is to allow the receiving device 110 to steer the Tx data generated based on different operating points of the transmitting device 120. The receiving device 110 and / or the processing circuitry 901 may be configured to request data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions. The receiving device 110 and / or the processing circuitry 901 may be configured to transmit the request in DCI to generate data, while the configuration of what data to generate may be configured through RRC and a specification may outline how the training data should be mapped onto radio resources based on such request. The receiving device 110 and / or the processing circuitry 901 may be configured to indicate data collection from the transmitting device 120 during one or more Tx hardware operating conditions such as one or more out of: EVM levels; one or more power levels; one or more distortion levels; one or more tolerance levels associated with different EVM and / or power levels; one or more operating modes of a digital predistortion algorithm; number of power amplifiers used for transmission; one or more back-off levels; and / or activation or deactivation of an envelope tracking process.

[0201] The receiving device 110 and / or the processing circuitry 901 may be configured to receive the data from the transmitting device 120 according to the Tx hardware operating condition. The receiving device 110 and / or the processing circuitry 901 may be configured to receive information when and / or for which Tx hardware operating condition the data was generated.

[0202] The receiving device 110 further comprises a memory 905. The memory 905 comprises one or more units to be used to store data on, such as indications, triggers, collected data, ML model, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the receiving device 110 may comprise a communication interface 906 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0203] The methods according to the embodiments described herein for the receiving device 110 are respectively implemented using e.g., a computer program product 907 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the receiving device 110. The computer program product 907 may be stored on a computer-readable storage medium 908, e g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the receiving device 110. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a receiving device 110 for handling communication in a wireless communication network, wherein the receiving device 110 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the receiving device 110 is operative to perform any of the methods herein.

[0204] In some embodiments a more general term “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device, wired device and / or with another network node. Examples of network nodes are, router, modem, server, UE, NodeB, master (M)eNB, secondary (S)eNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc. In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), internet of things (loT) capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0205] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

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

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

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

[0209] Fig. 10 shows an example of a communication system QQ100 in accordance with some embodiments.

[0210] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 or network node 12), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node, being examples of the entities herein, is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

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

[0212] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0213] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102. In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), 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).

[0214] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded 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.

[0215] As a whole, the communication system QQ100 of Fig. 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other 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 (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0216] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0217] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or 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).

[0218] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0219] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0220] Fig. 11 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage 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, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0222] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

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

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

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

[0229] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0230] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0231] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 11.

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

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

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

[0235] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0237] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple 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 QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, 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 QQ300.

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

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

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

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

[0242] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

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

[0244] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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.

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

[0246] Fig. 13 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 10, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0247] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Fig. 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400. The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0248] Fig. 14 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0249] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0250] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0251] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0252] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0253] Fig. 15 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 10 and / or UE QQ200 of Figure 11), network node (such as network node QQ110a of Figure 10 and / or network node QQ300 of Figure 12), and host (such as host QQ116 of Figure 10 and / or host QQ400 of Figure 13) discussed in the preceding paragraphs will now be described with reference to Figure 15.

[0254] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0255] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 10) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0256] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0257] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0258] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602. In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0259] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may ML modelling or data collection and thereby provide benefits such as reduced user waiting time, better energy savings, better responsiveness or similar.

[0260] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0261] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

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

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

[0264] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

[0265]

[0266] c»i cn ~^

[0267] References:

[0268] 1. 3GPP TS 38.104 v18.2.0, “Base Station (BS) radio transmission and reception; NR”. 2. 3GPP TS38.101 v18.0.0, ’’User Equipment (UE) radio transmission and reception; NR”

[0269] 3. RP-213599, “Study on Artificial Intelligence (Al) / Machine Learning (ML) for NR Air Interface”, 3GPP, Dec. 2021.

[0270] 4. “Next generation mobile networks' enablers: Machine learning-assisted mobility, traffic, and radio channel prediction”, IEEE Communications Magazine, 2023.

[0271] “A deep learning receiver for non-linear transmitter", IEEE Access, 2023. R1 -2208908, Discussion on general aspects of Al ML framework, Ericsson P106717, “A Method for Training Data Acquisition”

Claims

CLAIMS1. A method performed by a transmitting device (120) for handling data collection in a wireless communication network, the method comprising transmitting (512) to a receiving device (110), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and receiving (513), from the receiving device (110), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

2. The method according to claim 1, further comprising receiving (511) from the receiving device (110), a request for the capability indication.

3. The method according to any of the claims 1-2, further comprising transmitting (514) data to the receiving device (110) according to the Tx hardware operating condition.

4. The method according to claim 3, wherein transmitting the data further comprises indicating when and / or for which Tx hardware operating condition the data was generated.

5. The method according to any of the claims 1-4, wherein the one or more Tx hardware operating conditions comprise one or more of the following:• one or more error vector magnitude, EVM, levels;• one or more power levels;• one or more distortion levels;• one or more tolerance levels associated with different EVM and / or power levels;• one or more operating modes of a digital predistortion algorithm;• number of power amplifiers used for transmission;• one or more back-off levels; and / or• activation or deactivation of an envelope tracking process.

6. The method according to any of the claims 1-5, wherein the request further indicates which data to be collected and / or how to transmit the data to the receiving device (110).

7. A method performed by a receiving device (110) for handling data collection in a wireless communication network, the method comprising: receiving (522), from a transmitting device (120), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and transmitting (524) to the transmitting device (120), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

8. The method according to claim 7, further comprising triggering (523) a data collection for training a machine learning model.

9. The method according to any of the claims 7-8, further comprising transmitting (521) to the transmitting device (120), a request for the capability indication.

10. The method according to any of the claims 7-9, further comprising receiving (525) data from the transmitting device (120) according to the Tx hardware operating condition.

11. The method according to claim 10, wherein receiving the data further comprises receiving information when and / or for which Tx hardware operating condition the data was generated.

12. The method according to any of the claims 7-11 , wherein the receiving device (110) requests data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions.

13. A transmitting device (120) for handling data collection in a wireless communication network, wherein the transmitting device is configured to:transmit to a receiving device (110), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and receive, from the receiving device (110), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

14. The transmitting device (120) according to claim 13, wherein the transmitting device (120) is configured to receive from the receiving device (110), a request for the capability indication.

15. The transmitting device (120) according to any of the claims 13-14, wherein the transmitting device (120) is configured to transmit data to the receiving device (110) according to the Tx hardware operating condition.

16. The transmitting device (120) according to claim 15, wherein the transmitting device (120) is configured to further transmit information indicating when and / or for which Tx hardware operating condition the data was generated.

17. The transmitting device (120) according to any of the claims 13-16, wherein the one or more Tx hardware operating conditions comprise one or more of the following:• one or more error vector magnitude, EVM, levels;• one or more power levels;• one or more distortion levels;• one or more tolerance levels associated with different EVM and / or power levels;• one or more operating modes of a digital predistortion algorithm;• number of power amplifiers used for transmission;• one or more back-off levels; and / or• activation or deactivation of an envelope tracking process.

18. The transmitting device (120) according to any of the claims 13-17, wherein the request further indicates which data to be collected and / or how to transmit the data to the receiving device (110).

19. A receiving device (110) for handling data collection in a wireless communication network, wherein the receiving device (110) is configured to: receive from a transmitting device (120), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and transmit to the transmitting device (120), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

20. The receiving device (110) according to claim 19, wherein the receiving device (110) is configured to: trigger a data collection for training a machine learning model.

21. The receiving device (110) according to any of the claims 19-20, wherein the receiving device (110) is configured to: transmit to the transmitting device (120), a request for the capability indication.

22. The receiving device (110) according to any of the claims 19-21, wherein the receiving device (110) is configured to receive data from the transmitting device (120) according to the Tx hardware operating condition.

23. The receiving device (110) according to claim 22, wherein the receiving device (110) is configured to receive information when and / or for which Tx hardware operating condition the data was generated.

24. The receiving device (110) according to any of the claims 19-23, wherein the receiving device is configured to request data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions.

25. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-12, as performed by the receiving device and the transmitting device, respectively.

26. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-12, as performed by the receiving device and the transmitting device, respectively.

27. A method performed by a user equipment, UE, (10) for handling data collection in a wireless communication network, the method comprising- transmitting (532) to a radio network node (12), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and receiving (533), from the radio network node (12), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

28. The method according to claim 27, further comprising- transmitting (534) data to the receiving device (110) according to the Tx hardware operating condition.

29. The method according to claim 28, wherein transmitting the data further comprises indicating when and / or for which Tx hardware operating condition the data was generated.

30. The method according to any of the claims 27-29, wherein the request further indicates which data to be collected and / or how to transmit the data to the radio network node (12).

31. A method performed by a radio network node (12) for handling data collection in a wireless communication network, the method comprising:receiving (542), from a user equipment, UE, (10), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and- transmitting (544) to the UE (10), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

32. The method according to claim 31, further comprising- triggering (543) a data collection for training a machine learning model.

33. The method according to any of the claims 31-32, further comprising receiving (545) data from the UE (10) according to the Tx hardware operating condition.

34. The method according to claim 33, wherein receiving the data further comprises receiving information when and / or for which Tx hardware operating condition the data was generated.

35. The method according to any of the claims 31-34, wherein the radio network node (12) requests data for a number of Tx hardware operating conditions to enable training of a machine learning model for the number of Tx hardware operating conditions.

36. A user equipment, UE, (10) for handling data collection in a wireless communication network, wherein the UE (10) is configured to: transmit to a radio network node (12), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and receive, from the radio network node (12), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

37. A radio network node (12) for handling data collection in a wireless communication network, wherein the radio network node (12) is configured to:receive from a user equipment, UE, (10), a capability indication indicating capability to generate data according to one or more transmission, Tx, hardware operating conditions; and transmit to the transmitting device (120), a request for data collection according to a Tx hardware operating condition out of the one or more Tx hardware operating conditions.

Images