Event based data logging

Abstract

Embodiments of the present disclosure relate event based data logging. In an aspect, a terminal device receives, from a network device, a request message for data collected at the terminal device. Further, the terminal device determines there is no collected data to report. Moreover, the terminal device transmits, to the network device, a response message with an empty container.

Description

EVENT BASED DATA LOGGINGFIELD

[0001] Various example embodiments relate to the field of communications and in particular, to devices, methods, apparatuses, and computer readable storage media for event based data logging.BACKGROUND

[0002] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network.

[0003] Such communication networks operate in accordance with standards, such as those promulgated by third generation partnership project (3GPP) or European telecommunications standards institute (ETSI). Examples of such standards include the so-called 5th generation (5G) standard or other standards promulgated by 3GPP.SUMMARY

[0004] In general, example embodiments of the present disclosure provide a solution related to event based data logging.

[0005] In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: obtain a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; measure a reference signal transmitted from a network device to obtain the measured metric; and log the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0006] In a second aspect, there is provided a network device. The network devicecomprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: transmit, to a terminal device, at least part of a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; and transmit a reference signal to the terminal device.

[0007] In a third aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a network device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; measure a reference signal transmitted from the network device to obtain the measured metric; and log data associated with the measured metric in a buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0008] In a fourth aspect, there is provided a network device. The network device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: transmit, to a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; and transmit a reference signal to the terminal device.

[0009] In a fifth aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: obtain a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; measure a reference signal transmitted from a network device to obtain the measured metric; and log the data associated with the measured metric in the buffer of the terminal device based on determining that thecondition is fulfilled.

[0010] In a sixth aspect, there is provided a network device. The network device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: transmit, to a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; and transmit a reference signal to the terminal device.

[0011] In a seventh aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a network device, a request message for data collected at the terminal device; determine there is no collected data to report; and transmit, to the network device, a response message with an empty container.

[0012] In an eighth aspect, there is provided a network device. The network device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: transmit, to a terminal device, a request message for data collected at the terminal device; and receive, from the terminal device, a response message with an empty container.

[0013] In a ninth aspect, there is provided a method. The method comprises obtaining, at a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; measuring, at the terminal device, a reference signal transmitted from a network device to obtain the measured metric; and logging, at the terminal device, the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0014] In a tenth aspect, there is provided a method. The method comprises transmitting, at a network device, to a terminal device, at least part of a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; andtransmitting, at the network device, a reference signal to the terminal device.

[0015] In an eleventh aspect, there is provided a method. The method comprises receiving, at a terminal device, from a network device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; measuring, at the terminal device, a reference signal transmitted from the network device to obtain the measured metric; and logging, at the terminal device, data associated with the measured metric in a buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0016] In a twelfth aspect, there is provided a method. The method comprises transmitting, at a network device, to a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; and transmitting, at the network device, a reference signal to the terminal device.

[0017] In a thirteenth aspect, there is provided a method. The method comprises cause the terminal device at least to: obtaining, at a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; measuring, at the terminal device, a reference signal transmitted from a network device to obtain the measured metric; and logging the data associated with the measured metric in the buffer of the terminal device based on determining that the condition is fulfilled.

[0018] In a fourteenth aspect, there is provided a method. The method comprises transmitting, at a network device, to a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; and transmitting, at the network device, a reference signal to the terminal device.

[0019] In a fifteenth aspect, there is provided a method. The method comprises receiving, at a terminal device, from a network device, a request message for data collected at theterminal device; determining, at the terminal device, there is no collected data to report; and transmitting, at the terminal device, to the network device, a response message with an empty container.

[0020] In a sixteenth aspect, there is provided a method. The method comprises transmiting, at a network device, to a terminal device, a request message for data collected at the terminal device; and receiving, at the network device, from the terminal device, a response message with an empty container.

[0021] In a seventeenth aspect, there is provided an apparatus. The apparatus comprises means for obtaining, at a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; means for measuring, at the terminal device, a reference signal transmitted from a network device to obtain the measured metric; and means for logging, at the terminal device, the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0022] In an eighteenth aspect, there is provided an apparatus. The apparatus comprises means for transmitting, at a network device, to a terminal device, at least part of a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; means for and transmitting, at the network device, a reference signal to the terminal device.

[0023] In a nineteenth aspect, there is provided an apparatus. The apparatus comprises means for receiving, at a terminal device, from a network device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; means for measuring, at the terminal device, a reference signal transmitted from the network device to obtain the measured metric; and means for logging, at the terminal device, data associated with the measured metric in a buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0024] In a twentieth aspect, there is provided an apparatus. The apparatus comprises means for transmitting, at a network device, to a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; and means for transmitting, at the network device, a reference signal to the terminal device.

[0025] In a twenty-first aspect, there is provided an apparatus. The apparatus comprises means for obtaining, at a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; means for measuring, at the terminal device, a reference signal transmitted from a network device to obtain the measured metric; and means for logging the data associated with the measured metric in the buffer of the terminal device based on determining that the condition is fulfilled.

[0026] In a twenty-second aspect, there is provided an apparatus. The apparatus comprises means for transmitting, at a network device, to a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; and means for transmitting, at the network device, a reference signal to the terminal device.

[0027] In a twenty-third aspect, there is provided an apparatus. The apparatus comprises means for receiving, at a terminal device, from a network device, a request message for data collected at the terminal device; means for determining, at the terminal device, there is no collected data to report; and means for transmitting, at the terminal device, to the network device, a response message with an empty container.

[0028] In a twenty-fourth aspect, there is provided an apparatus. The apparatus comprises means for transmiting, at a network device, to a terminal device, a request message for data collected at the terminal device; and means for receiving, at the network device, from the terminal device, a response message with an empty container.

[0029] In a twenty-fifth aspect, there is provided a non-transitory computer readable medium that, when executed by an apparatus, cause the apparatus to perform at least themethod according to any one of the above ninth to sixteenth aspects.

[0030] In a twenty-sixth aspect, there is provided a computer program product comprising program instructions for performing at least the method according to any one of the above ninth to sixteenth aspects.

[0031] In a twenty-seventh aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to perform at least the method according to any one of the above ninth to sixteenth aspects.

[0032] In a twenty-eighth aspect, there is provided a terminal device. The terminal device comprises obtaining circuitry configured to obtain a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; measuring circuitry configured to measure a reference signal transmitted from a network device to obtain the measured metric; and logging circuitry configured to log the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0033] In a twenty-ninth aspect, there is provided a network device. The network device comprises transmitting circuitry configured to transmit, to a terminal device, at least part of a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; and transmitting circuitry configured to transmit a reference signal to the terminal device .

[0034] In a thirtieth aspect, there is provided a terminal device. The terminal device comprises receiving circuitry configured to receive, from a network device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; measuring circuitry configured to measure a reference signal transmitted from the network device to obtain the measured metric; and logging circuitry configured to log data associated with the measured metric in a buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0035] In a thirty-first aspect, there is provided a network device. The network device comprises transmitting circuitry configured to transmit, to a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; and transmitting circuitry configured to transmit a reference signal to the terminal device.

[0036] In a thirty-second aspect, there is provided a terminal device. The terminal device comprises obtaining circuitry configured to obtain a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; measuring circuitry configured to measure a reference signal transmitted from a network device to obtain the measured metric; and logging circuitry configured to log the data associated with the measured metric in the buffer of the terminal device based on determining that the condition is fulfilled.

[0037] In a thirty-third aspect, there is provided a network device. The network device comprises transmitting circuitry configured to transmit, to a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; and transmitting circuitry configured to transmit a reference signal to the terminal device.

[0038] In a thirty-fourth aspect, there is provided a terminal device. The terminal device comprises receiving circuitry configured to receive, from a network device, a request message for data collected at the terminal device; determining circuitry configured to determine there is no collected data to report; and transmitting circuitry configured to transmit, to the network device, a response message with an empty container.

[0039] In a thirty-fifth aspect, there is provided a network device. The network device comprises transmitting circuitry configured to transmit, to a terminal device, a request message for data collected at the terminal device; and receiving circuitry configured to receive, from the terminal device, a response message with an empty container.

[0040] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used tolimit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0042] FIG. 1 A illustrates an example environment in which example embodiments of the present disclosure can be implemented;

[0043] FIGS. IB and 1C illustrate example data collection principles for the beam management (BM) associated with some example embodiments of the present disclosure;

[0044] FIG. 2 illustrates a signaling flow between a terminal device and a network device according to some example embodiments of the present disclosure;

[0045] FIGS. 3 to 8 illustrate example communication processes according to some example embodiments of the present disclosure;

[0046] FIG. 9 illustrates a signaling flow between a terminal device and a network device according to some example embodiments of the present disclosure;

[0047] FIG. 10 illustrates an example communication process according to some example embodiments of the present disclosure;

[0048] FIG. 11 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure;

[0049] FIG. 12 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

[0050] FIG. 13 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure;

[0051] FIG. 14 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

[0052] FIG. 15 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure;

[0053] FIG. 16 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

[0054] FIG. 17 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure;

[0055] FIG. 18 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

[0056] FIG. 19 illustrates a simplified block diagram of a device that is suitable for implementing some example embodiments of the present disclosure; and

[0057] FIG. 20 illustrates a block diagram of an example of a computer readable medium in accordance with some example embodiments of the present disclosure.

[0058] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION

[0059] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

[0060] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0061] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0062] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms.These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0063] The terminology used herein is for the purpose of describing particular embodiments and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0064] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

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

[0066] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as new radio (NR), long term evolution (LTE), LTE-advanced (LTE-A), wideband code division multiple access (WCDMA), high-speed packet access (HSPA), narrow band internet of things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the third generation (3G), the 4G, 4.5G, 5G, or 6G communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0067] As used herein, the term “network device” refers to a node in a communication network via which a terminal device can access the communication network and receive services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP), a reception point (RP), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the applied terminology and technology.

[0068] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voiceover IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0069] Principles and implementations of embodiments of the present disclosure will be described in detail below with reference to the figures. Reference is first made to FIG. 1A, which illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.

[0070] The environment 100, which may be a part of a communication network, comprises a terminal device 110 and a network device 120 communicating with each other. The communication between the terminal device 110 and the network device 120 may be direct or indirect. As an example, the terminal device 110 and the network device 120 may communicate with one or more further devices not shown in FIG. 1A.

[0071] To receive or / and transmit data and / or control information, the terminal device 110 may perform communications with the network device 120. A link from the network device 120 to the terminal device 110 is referred to as a downlink (DL), while a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL).

[0072] Although the terminal device 110 and the network device 120 are described in the communication environment 100 of FIG. 1A, embodiments of the present disclosure may apply to any other suitable communication devices in communication with one another. That is, embodiments of the present disclosure are not limited to the exemplary scenarios of FIG. 1A. In this regard, it is noted that although the terminal device is schematically depicted as a mobile phone and the network device 120 is schematically depicted as a basestation in FIG. 1A. It is understood that these depictions are exemplary in nature without suggesting any limitation. In other embodiments, the first device 110 and the network device 120 may be any other communication devices, for example, any other wireless communication devices.

[0073] It is to be understood that the particular number of various communication devices and the particular number of various communication links as shown in FIG. 1A is for illustration purpose only without suggesting any limitations. The communication environment 100 may include any suitable number of communication devices and any suitable number of communication links for implementing embodiments of the present disclosure. In addition, it should be appreciated that there may be various wireless as well as wireline communications (if needed) among all of the communication devices.

[0074] The communications in the environment 100 may follow any suitable communication standards or protocols, which are already in existence or to be developed in the future, such as Universal Mobile Telecommunications System (UMTS), long term evolution (LTE), LTE-Advanced (LTE-A), the fifth generation (5G) New Radio (NR), 6G, Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, and machine type communication (MTC), enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultrareliable low latency communication (URLLC), carrier aggregation (CA), dual connectivity (DC), and new radio unlicensed (NR-U) technologies.

[0075] Network (NW)-side model data collection in release 19 (Rel-19) beam management (BM)-Casel and BM-Case2 has mainly been investigated for offline training model. FIG. IB illustrates an example data collection principle for NW-side training of a beam prediction model. As shown in FIG. IB, different gNBs may collect data based on layer 1 (LI) reference signal received power (RSRP) measurement reports corresponding to different beams from different UEs. It may be assumed that the gNBs from the same vendor may be able to transmit reported measurements of all the cells to a server, for instance, a data server operated by NW vendors so that this server may aggregate received data from multiple gNBs to form a training dataset. With a larger dataset, the gNB may be able to train a more general model to cover a large geographical area or multiple site locations. The data may be pre-processed using normalization, scaling, encoding, etc., before model training or further retraining.

[0076] With respect to data collection for UE-side model, FIG. 1C illustrates an example data collection principle for UE-side training of a beam prediction model. As shown in FIG. 1C, multiple UEs may collect data based on the Ll-RSRP measurements corresponding to different beams. The UE may not be capable of training a beam prediction model from scratch on its own due to i) limited data available at the single UE device and ii) hardware limitations such as computational resources and UE power limitation problems. Therefore, the UE may send the beam measurements to an external UE server, for instance, located in a data centre operated by a UE vendor. The external UE server may be referred as a server for UE side model training or an over the top (OTT) server. Alternatively, the NW may collect the measurements from UE(s) and forward to the external UE server. The UE server may receive data from multiple UEs from the same cell (e.g., served by the gNB 1) or from different cells (e.g., served by the gNBl and the gNB 2). The UE server may aggregate the data received from multiple UEs to form a training dataset, and send to UEs for training the UE-side model. With a larger dataset, the UE may be able to train a generalized model that can be applied to multiple site locations. The data may be pre-processed using normalization, scaling, encoding, etc., before model training or further retraining. Lastly, the beam prediction model may be assumed to be downloaded to all the UEs.

[0077] It can be seen that for the data collection for NW-side model, the UE needs to support logging, and configurations related to logging and reporting of these logged data to the NW may be configured by the NW. It is also expected that for the data collection for UE-side model, the NW may have a similar approach. Therefore, further improvements related to both aspects may need to be considered.

[0078] In a data collection configuration in Rel-19, a gNB may employ an immediate minimization drive test (MDT) and configure a channel state information (CSI) reporting framework in a radio resource control connected (RRC_CONNECTED) state via an RRC message to the UE after a data collection configuration activation from the operation, administration, and maintenance (OAM) / core network (CN). The configurations dedicatedto data collection reference signal (RS) resources may contain configurations for LI measurements, LI data logging, and reporting of the LI logged data if logging is supported by the UE. If measurement collection trigger conditions are met, UE may measure channel state information reference signal (CSI-RS) resources and LI data may be logged. During logging, if reporting conditions are met, the UE may send logged LI measurements via an RRC message. The gNB may then be responsible for forwarding the data to another network entity if required.

[0079] To support the data logging, the UE may contain an access stratum (AS) buffer to log, for example, Ll-RSRP and / or beam index upon receiving configurations from the NW to measure RS resources. The initiation of data logging may be upon receiving the configurations or an event may trigger the process to log the data.

[0080] Currently, how to support event-based data logging and / or the subsequent data reporting in an efficient approach, for example, how to define events that may allow starting and stopping of data logging or what types of conditions or events to consider, is still an open issue to be solved.

[0081] According to some embodiments of the present disclosure, a terminal device obtains a configuration for data collection. The configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of at least one measurement threshold, a target uplink waveform, beam failure detection, congestion detection, downlink interference detection, or radio link failure prediction. In addition, the terminal device measures a reference signal transmitted from a network device to obtain the measured metric. Moreover, the terminal device logs the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.

[0082] According to some embodiments of the present disclosure, when a terminal device receives, from a network device, a request message for data collected at the terminal device, and if the terminal device determines there is no collected data to report, the terminal device transmits, to the network device, a response message with an empty container.

[0083] In this way, it is possible to assist the terminal device to perform data logging considering different conditions and / or help the network device to request the data collected by the terminal device in an efficient way. Therefore, it is allowed to enhancecommunication performance and improve communication efficiency.

[0084] In the present disclosure, the terms “event”, and “condition” may be used interchangeably in some cases.

[0085] FIG. 2 illustrates a signaling flow 200 between a terminal device and a network device according to some example embodiments of the present disclosure. For the purpose of discussion, the signaling flow 200 will be described with reference to FIG. 1A.

[0086] As shown in FIG. 2, the terminal device 110 obtains (205) a configuration for data collection at the terminal device 110. The configuration for data collection may be obtained in a variety of approaches.

[0087] In some implementations, the network device 120 may transmit (210), to the terminal device 110, at least part of the configuration for data collection. For example, the network device 120 may receive, from a management system that is in an operator domain, one or more parameters for configuring the terminal device 110 for data collection. For example, for the management-based MDT, the data collection trigger may be transmitted from the management system to the network device 120, and such a trigger may contain parameters to configure the terminal device 110 for data collection. Alternatively or additionally, the terminal device 110 may initiate a data collection trigger to request the configuration for data collection from the network device 120. For example, the data collection trigger may be initiated based on a capability of the terminal device 110. Then, on this basis, the network device 120 may transmit at least part of the configuration for data collection to the terminal device.

[0088] Alternatively or additionally, at least part of the configuration for data collection may be predefined in a standard specification, and in this case, the terminal device 110 may obtain at least part of the configuration based on the standard specification. For example, the terminal device 110 may obtain the other part of the configuration from the network device 120.

[0089] In some embodiments, the configuration for data collection may comprise at least one condition (i.e., event) for logging data associated with a measured metric in a buffer (for example, an AS buffer) of the terminal device 110, which will be discussed in detail hereinafter. The measured metric may also be referred to as a measured property or a measured quantity. The measured metric may refer to anything that may be measured, determined, or obtained. The measured metric may comprise an individual quantity or astatistical quantity (for example, an averaged quantity).

[0090] For example, the measured metric may comprise RSRP, rank indicator (RI), layer indicator (LI), or a pre-coding matrix indicator (PMI). For example, the measured metric may comprise one or more of: LI -RSRP, CSI-RS resource index (CRI)-RSRP, synchronization signal block (SSB)-index-RSRP, CRI-RI-PMI-channel quality indicator (CQI), CRI-RI-il, CRI-RI-il-CQI, CRI-RI-CQI, CRI-signal-to-interference-plus-noise ratio (SINR), SSB-index-SINR, CRI-RI-LI-PMI-CQI, CRI-RSRP-index, SSB-Index-RSRP-index, CRI-SINR-index, SSB-index-SINR-index, or time-domain channel property (TDCP). The type of measured metric may be indicated in the configuration.

[0091] As shown in FIG. 2, the network device 120 transmits (215) a reference signal to the terminal device 110. Accordingly, the terminal device 110 measures (220) the reference signal transmitted from the network device 120 to obtain the measured metric. As an example, the reference signal may be a CSI-RS. In this case, the network device 120 may transmit CSI-RSs for SET A / SET B beams. As another example, the reference signal may be a synchronization signal block (SSB).

[0092] Based on the reference signal from the network device 120, the terminal device 110 may perform measurements and determine the data associated with the measured metric (for example, also referred to as report metric or report quantity). In some example embodiments, the report metric may be the same as the measured metric. In some other example embodiments, the report metric may be different from the measured metric. In some example embodiments, the type of the report metric may be indicated in the configuration for data collection. The terminal device 110 logs (225) the data associated with the measured metric in the buffer of the terminal device 110, if a condition of the at least one condition indicated in the configuration is fulfilled. Alternatively or additionally, the terminal device 110 may discard a measurement if a condition of the at least one condition is not fulfilled. For example, if the terminal device 110 determines that the at least one condition is not fulfilled, it may stop the measurement and the collection of the data.

[0093] In some example embodiments, the at least one condition may be associated with at least one measurement threshold. For example, a condition of the at least one condition may comprise a value of the measured metric being above (or above or equal) or below (or below or equal to) a measurement threshold of the at least one measurement threshold. In this case, collection of data associated with the measured metric may be performed when thevalue of the measured metric is above or below the measurement threshold of the at least one measurement threshold. Alternatively or additionally, for some measured metric (such as a PMI), it may not be possible to use a single measurement threshold, and in this case, a statistical metric based on this measured metric may be used for the comparison.

[0094] In some implementations, the terminal device 110 may log the data associated with the measured metric in its buffer if the value of the measured metric is above (or above or equal to) a measurement threshold of the at least one measurement threshold. The terminal device 110 may discard a measurement if the value of the measured metric is below or equal to (or below) this measurement threshold. This can ensure that the terminal device 110 can collect data samples with the best beam measurement conditions. The data samples may comprise at least one measurement or a set of measurements. As an example implementation, the measured results may be logged in the AS buffer of the terminal device 110 if the value for the given measured metric (for example, CRI-RSRP) is above the configured measurement threshold (for example, CRI-RSRP > CRI-RSRP-Threshold).

[0095] Alternatively, the terminal device 110 may log the data associated with the measured metric in its buffer if the value of the measured metric is below (or below or equal to) a measurement threshold of the at least one measurement threshold. The terminal device 110 may discard a measurement if the value of the measured metric is above or equal to (or above) this measurement threshold.

[0096] In some implementations, the configured at least one measurement threshold may be a single value for a given measured metric, or different measurement thresholds may be configured for different resource sets (for example, SET A and SET B). The at least one measurement threshold may comprise a first measurement threshold associated with a first resource set (for example, SET A) and a second measurement threshold associated with a second resource set (for example, SET B). For example, at least one LI RSRP threshold may be configured for SET A / B, and collection of data associated with the measured metric may be performed when the value of the measured metric is above or below the configured LI RSRP threshold for SET A / SET B.

[0097] In the example implementations where a reporting condition is fulfilled, the terminal device 110 may perform data reporting. For example, if the buffer of the terminal device 110 is full, the terminal device 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready forreporting due to the buffer being full. For example, the terminal device 110 may transmit a data available indication with a cause as Buffer_full. The data availability / ready indication may help the network device 120 to know that the buffer in the terminal device 110 is full. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.

[0098] In certain example embodiments, if the terminal device 110 is unable to comply with the configuration for data collection received from the network device 120, the terminal device 110 may send a message to the network device 120 to indicate this failure. The message may comprise an RRC reconfiguration failure message or a new failure indication message dedicated to data collection.

[0099] FIG. 3 illustrates an example communication process 300 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 300 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 301 may be an example of the terminal device 110, and the gNB 302 may be an example of the network device 120.[000100] As shown in FIG. 3, at 303, a data collection trigger is received at the gNB 302. For management-based MDT, for instance, such a trigger may be received from the management system, which is in an operator domain, and the trigger may contain parameters to configure the UE 301 for data collection. As another example implementation, the UE 301 may initiate a data collection trigger to request data collection configuration from the gNB 302, for example, based on UE capabilities.[000101] At 305, a capability exchange may be performed, and the attach procedure is done. At 307, the gNB 302 configures the UE 301 with a data collection configuration. In this case, the UE 301 is configured with at least one LI RSRP threshold for SET A / B (for example, received from the data collection specific CSI-RS configurations). At 309, the UE 301 acknowledges the configuration of threshold-based events in an RRC configuration complete message. Otherwise, if the UE 301 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000102] At 311, the gNB 302 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 313, the UE 301 starts measuring the CSI-RSs and generates the measured metric indicated in the data collection configuration, such as CRI-RSRR[000103] At 315, the data, i.e., report quantity, associated with the measured LI quantity is logged in the AS buffer of the UE 301 if the value of the measured LI quantity is above the threshold configured by the gNB 302. This can ensure that the UE 301 collects data samples with the best beam measurement conditions. Otherwise, the UE 301 discards the measurement. Alternatively, if there is a request to collect data samples with the measured LI quantity value below the threshold, the required data samples may also be logged. As an example implementation, the measured results may be logged in the AS buffer if the value for the measured metric is above the configured threshold (for example, CRI-RSRP > CRI-RSRP-Threshold). As another example implementation, for some measured metric (such as PMI), it may not be possible to use a single threshold, and in this case, a statistical metric based on the PMI may be used for comparison. The configured at least one threshold may be a single value, or different thresholds may be configured for different resource sets (i.e., SET A and SET B).[000104] At 317, the UE 301 determines reporting conditions, for example, whether the buffer is full. At 319, the UE 301 sends a data available / ready indication with a cause as Buffer_full. The data availability / ready indication helps the gNB 302 to know that the AS buffer in the UE 301 is full (or other conditions). This helps the gNB 302 to plan uplink resources to fetch the collected data from the UE 301.[000105] At 321, the gNB 302 requests data using, for example, a UEInformationRequest message. At 323, the UE 301 sends logged data using, for example, a UEInformationResponse message. At 325, the gNB 302 maps the collected data to relevant trace collection sessions. At 327, the collected data is sent to a trace collection entity.[000106] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 300 and have similar effects. For the purpose of simplification, the details will be omitted.[000107] In some example embodiments, the at least one condition may be associated with a target uplink waveform. For example, a condition of the at least one condition may comprise an uplink waveform for the terminal device being the target uplink waveform. As an example, the target uplink waveform may comprise discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM). In this case, the terminal device 110 may log the data associated with the measured metric in its buffer if the uplink waveform for the terminal device 110 is DFT-S-OFDM. Otherwise, the terminal device 110may discard a measurement. This may apply to data collection in poor radio conditions for cell edge terminal device, as when the terminal device 110 is at the cell edge, it may use the DFT-S-OFDM to sustain poor radio conditions due to a poor UL SINR. Thus, this can help to train models specifically for cell edge scenarios.[000108] In the example implementations when a reporting condition is fulfilled, the terminal device 110 may perform data reporting accordingly. For example, the terminal device 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready for reporting due to a full buffer or / and a poor radio condition. For example, the terminal device 110 may transmit a data available indication with cause as Buffer_full_poor_radio. The data availability / ready indication may help the network device 120 to know that the data has been collected in the buffer in the terminal device 110 and is ready to be reported. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.[000109] FIG. 4 illustrates an example communication process 400 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 400 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 401 may be an example of the terminal device 110, and the gNB 402 may be an example of the network device 120.[000110] As shown in FIG. 4, at 403, a data collection trigger is received at the gNB 402. More implementations related to the operation 403 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 403 are omitted for brevity.[000111] At 405, a capability exchange may be performed, and the attach procedure is done. At 407, the gNB 402 configures the UE 401 with a data collection configuration. In this case, the UL waveform is configured as CP-OFDM, and the condition of logging is configured as UL waveform being a specific waveform such as for example, DFT-S-OFDM. Alternatively or additionally, the UE 401 may be configured with LI RSRP threshold(s) associated with data collection for specific SET A / B. At 409, the UE 401 acknowledges the configuration of data collection in an RRC configuration complete message. Otherwise, if the UE 401 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000112] At 411, the gNB 402 starts transmitting CSI-RSs in the DL for SET A / SET Bbeams. At 413, the UE 401 starts measuring the CSI-RSs and generates the specified quantity, i.e., report quantity indicated in the data collection configuration, such as CRI-RSRP.[000113] At 415, the UE 401 checks and finds that the UL waveform is CP-OFDM and discards the measurement. At 417, the UE 401 moves to a cell edge and notices poor radio conditions. At 419, the gNB 402 detects, e.g., based on an UL SINR measurement, that UE is in poor radio conditions and decides to switch the UL waveform of the UE 401 to DFT-S-OFDM.[000114] At 421, the gNB 402 reconfigures the UE 401 to use DFT-S-OFDM. At 423, the UE 401 acknowledges the reconfiguration in an RRC reconfiguration complete message. At 425, the gNB 402 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 427, the UE 401 starts measuring the CSI-RSs and generates the specified quantity, i.e., report quantity indicated in the data collection configuration, such as CRI-RSRP.[000115] At 429, the UE 401 notices the UL waveform is DFT-S-OFDM, and it stores the data in the AS buffer. At 431, the UE 401 determines reporting condition, e.g., a full buffer or / and a poor radio condition. At 433, the UE 401 sends a data available indication with cause as Buffer_full_poor_radio. At 435, the gNB 402 requests data using, e.g., a UEInformationRequest message. At 437, the UE sends logged data using, e.g., a UEInformationResponse message. At 439, the gNB 402 maps the collected data to relevant trace collection sessions. At 441, the collected data is sent to a trace collection entity.[000116] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 400 and have similar effects. For the purpose of simplification, the details will be omitted.[000117] In some example embodiments, the at least one condition may be associated with beam failure detection. For example, a condition of the at least one condition may comprise a beam failure indication count being below a count threshold for the beam failure detection. In this case, data collection may be performed when the beam failure indication count is below the count threshold. In other words, data collection may be performed if beam failure detection is not triggered. The received configuration for data collection may comprise the count threshold. To have early detection of beam failure, the count threshold value may be less than a regular count threshold (i.e., BFI_COUNT) for beam failure. For example, the count threshold may be referred to as a data collection (DC) specific beam failure indication count threshold (denoted as DC_BFI_COUNT) which is less than regularBFI_COUNT. In this way, it is allowed to ensure that the terminal device 110 collects data samples before the beam failure occurs, and also help the network device 120 to retrieve data from the terminal-side buffer before the actual beam failure occurs. Alternatively or additionally, in this case, the received configuration for data collection may further comprise a reference signal resource for the beam failure detection. The reference signal resource may comprise beam failure detection specific CSI-RS resources (qO), and the CSI resources for qO may be based on SET A beams or SET B beams, or a combination of SET A and SET B beams.[000118] In the example implementations, when the beam failure indication count is equal to or above the count threshold, the terminal device 110 may perform data reporting. For example, the terminal device 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready for reporting due to the beam failure detection to realize an early notification of the actual beam failure. For example, the terminal device 110 may transmit a data available indication with a cause as beam failure detection. The data availability / ready indication may help the network device 120 to know that the data has been collected in the buffer in the terminal device 110 and is ready to be reported. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.[000119] FIG. 5 illustrates an example communication process 500 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 500 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 501 may be an example of the terminal device 110, and the gNB 502 may be an example of the network device 120.[000120] As shown in FIG. 5, at 503, a data collection trigger is received at the gNB 502. More implementations related to the operation 503 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 503 are omitted for brevity.[000121] At 505, a capability exchange may be performed, and the attach procedure is done. At 507, the gNB 502 configures the UE 501 with a data collection configuration. In this case, the UE 501 is configured with a logging condition as Beam failure detection (BFD) and data collection specific beam failure indication count (DC_BFI_COUNT), and optionally beam failure detection specific CSI-RS resources(qO). The CSI resources for qO may bebased on SET A or SET B or a combination of SET A / SET B beams. To have early detection of beam failure, the DC_BFI_COUNT value may be less than the regular BFI_COUNT. Alternatively or additionally, the UE 501 may be configured with LI RSRP thresholds associated with data collection for specific SET A / B.[000122] At 509, the UE 501 accepts the RRC configuration, and sends an RRCReconfigurationComplete message to the gNB 502. Otherwise, if the UE 501 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000123] At 511, the gNB 502 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 513, the UE 501 starts measuring the CSI-RSs and estimates the LI RSRR The UE 501 also starts detecting the beam failure based on the received configuration. At 515, the measured LI RSRP is logged in the AS buffer of the UE 501 if the beam failure notification counter BFI is less than DC_BFI_COUNT. This can ensure that the UE 501 collects data samples before beam failure occurs. Also, this can help the gNB 502 to retrieve data from UE 501’s AS buffer before the actual beam failure occurs.[000124] At 517, the UE 501 determines trigger conditions, for example, the BFI is equal to DC_BFI_COUNT. At 519, the UE 501 sends a data available indication with cause as beam failure detection (i.e., an early notification). At 521, the gNB 502 requests data using, e.g., a UEInformationRequest message. At 523, the UE 501 sends logged data using, e.g., a UEInformationResponse message. At 525, the gNB 502 maps the collected data to relevant trace collection sessions. At 527, the collected data is sent to a trace collection entity.[000125] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 500 and have similar effects. For the purpose of simplification, the details will be omitted.[000126] In some example embodiments, the at least one condition may be associated with congestion detection. For example, a condition of the at least one condition may comprise a congestion level being above (or above or equal to) or below (or below or equal to) a congestion threshold for the congestion. When the congestion level is above or below the congestion threshold, the terminal device 110 may start / stop logging data. For example, the terminal device 110 may log the data associated with the measured metric in its buffer if the congestion level is above (or above or equal to) or below (or below or equal to) thecongestion threshold for the congestion detection. Otherwise, the terminal device 110 may discard a measurement. It may be up to the network device 120 to set a criterion for logging the measurements depending upon the type of data required for the model training. For example, the network congestion in the uplink may be detected by the terminal device 110 based on how many resources it requests and / or how many resources it is granted or through the accumulation of data in its transmit buffer. The terminal device 110 may determine the congestion level in any other available way and the scope of the present disclosure is not limited in this regard. In example embodiments, the congestion threshold may be comprised in the received configuration for data collection. As an example implementation, the congestion threshold may be based on uplink transmission buffer occupancy at the terminal device 110.[000127] In some implementations, the terminal device 110 may log the data associated with the measured metric in its buffer if the congestion level is above (or above or equal to) the congestion threshold. The terminal device 110 may discard a measurement if the congestion level is below or equal to (or below) this congestion threshold. In this implementation, when the congestion level is equal to or below the congestion threshold, the terminal device 110 may perform data reporting accordingly.[000128] Alternatively, the terminal device 110 may log the data associated with the measured metric in its buffer if the congestion level is below (or below or equal to) the congestion threshold. The terminal device 110 may discard a measurement if the congestion level is above or equal to (or above) this congestion threshold. This can ensure that the terminal device 110 can collect data samples with a good communication environment. In this implementation, when the congestion level is equal to or above the congestion threshold, the terminal device 110 may perform data reporting accordingly.[000129] In example embodiments, the terminal device 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready for reporting due to the congestion detection. For example, the terminal device 110 may transmit a data available indication with cause as congestion detection / level. The data availability / ready indication may help the network device 120 to know that the data has been collected in the buffer in the terminal device 110 and is ready to be reported. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.[000130] FIG. 6 illustrates an example communication process 600 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 600 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 601 may be an example of the terminal device 110, and the gNB 602 may be an example of the network device 120.[000131] As shown in FIG. 6, at 603, a data collection trigger (i.e., an MDT based DC activation trigger for beam management) is received at the gNB 602. More implementations related to the operation 603 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 603 are omitted for brevity.[000132] At 605, a capability exchange may be performed, and attach procedure is done. At 607, the gNB 602 configures the UE 601 with a data collection configuration. In this case, the UE 601 is configured with a congestion detection based condition, and a DC congestion threshold (DC_CONG_THR). For example, the congestion threshold may be based on UL transmission buffer occupancy at the UE side.[000133] At 609, once the UE 601 has been configured by the configuration received in operation 607, it sends an RRC Reconfiguration Complete message to the gNB 602. Otherwise, if the UE 601 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000134] At 611, the gNB 602 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 613, the UE 601 starts measuring LI RSRP based on the CSI-RSs. At the same time, the UE 601 also keeps detecting / measuring congestion in the NW. At 615, the measured LI RSRP is logged in the AS buffer of the UE 601 if the value of detected / measured congestion level is below / above the threshold, DC_CONG_THR. It is up to the NW to set a criterion for logging the measurements depending upon the type of data required for the model training.[000135] At 617, the UE 601 monitors the criteria set for reporting the logged data to the NW, e.g., whether the congestion level is equal to or above the configured threshold DC_CONG_THR. At 619, the UE 601 sends a data available indication with a cause as congestion detection or congestion level. At 621, the gNB 602 sends, e.g., a UEInformationRequest message to the UE 601 to request collected data. At 623, the UE 601 sends collected data to the gNB 602 via, e.g., a UEInformationResponse message. At 625, the gNB 602 collates multiple reports of the collected data received from the UE 601,and maps the collected data to relevant trace collection sessions. At 6 1 , gNB 602 forwards the collected data to the training data entity.[000136] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 600 and have similar effects. For the purpose of simplification, the details will be omitted.[000137] In some example embodiments, the at least one condition may be associated with downlink interference detection. For example, the condition may comprise a downlink interference level being above (or above or equal to) or below (or below or equal to) an interference threshold for the downlink interference. The terminal device 110 may log the data associated with the measured metric in its buffer if the downlink interference level is above (or above or equal to) or below (or below or equal to) the interference threshold. Otherwise, the terminal device 110 may discard a measurement. It may be up to the network device 120 to set a criterion for logging the measurements depending upon the type of data required for the model training. In some example embodiments, the terminal device 110 may measure the level of the downlink interference using the CSI-interference management (IM) resources configured by the network device 120. The terminal device 110 may determine the interference level in any available way and the scope of the present disclosure is not limited in this regard. In example embodiments, the interference threshold may be comprised in the received configuration for data collection.[000138] In some implementations, the terminal device 110 may log the data associated with the measured metric in its buffer if the interference level is above (or above or equal to) the interference threshold. The terminal device 110 may discard a measurement if the interference level is below or equal to (or below) this interference threshold. In this implementation, when the interference level is equal to or below the interference threshold, the terminal device 110 may perform data reporting accordingly[000139] Alternatively, the terminal device 110 may log the data associated with the measured metric in its buffer if the interference level is below (or below or equal to) the interference threshold. The terminal device 110 may discard a measurement if the interference level is above or equal to (or above) this interference threshold. This can ensure that the terminal device 110 can collect data samples with a good communication environment. In this implementation, when the congestion level is equal to or above the congestion threshold, the terminal device 110 may perform data reporting accordingly[000140] In example embodiments, the terminal device 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready for reporting due to the downlink interference detection. For example, the terminal device 110 may transmit a data available indication with cause as interference detection / level. The data availability / ready indication may help the network device 120 to know that the data has been collected in the buffer in the terminal device 110 and is ready to be reported. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.[000141] In example embodiments, if the terminal device 110 is unable to comply with the configuration for data collection received from the network device 120, the terminal device 110 may send a message to the network device 120 to indicate this failure. The message may comprise an RRC reconfiguration failure message or a new failure indication message dedicated to data collection.[000142] FIG. 7 illustrates an example communication process 700 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 700 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 701 may be an example of the terminal device 110, and the gNB 702 may be an example of the network device 120.[000143] As shown in FIG. 7, at 703, a data collection trigger (i.e., an MDT based DC activation trigger for beam management) is received at the gNB 702. More implementations related to the operation 703 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 703 are omitted for brevity.[000144] At 705, a capability exchange may be performed, and attach procedure is done. At 707, the gNB 702 configures the UE 701 with a data collection configuration. In this case, the UE 701 is configured with a interference detection based condition, and a DC interference threshold (DC_INTF_THR).[000145] At 709, once the UE 701 has been configured by the configuration received in operation 707, it sends an RRC Reconfiguration Complete message to the gNB 702. Otherwise, if the UE 701 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000146] At 711, the gNB 702 starts transmitting CSI-RSs in the DL. At 713, the UE 701 starts measuring LI RSRP based on the CSI-RSs. At the same time, the UE 701 alsokeeps detecting / measuring interference in the NW. At 715, the measured LI RSRP is logged in the AS buffer of the UE 701 if the value of the detected / measured interference level is below / above the threshold, DC_INTF_THR. It is up to the NW to set a criterion for logging the measurements depending upon the type of data required for the model training.[000147] At 717, the UE 701 monitors the criteria set for reporting the logged data to the NW, for example, whether the detected / measured interference level is equal to or above the threshold. At 719, the UE 701 sends a data available indication with a cause as interference detection or interference level. At 721, the gNB 702 sends, e.g., a UEInformationRequest message to the UE 701 to request collected data. At 723, the UE 701 sends collected data to the gNB 702 via e.g., a UEInformationResponse message. At 725, the gNB 702 collates multiple reports of the collected data received from the UE 701, and maps the collected data to relevant trace collection sessions. At 727, gNB 702 forwards the collected data to the training data entity.[000148] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 700 and have similar effects. For the purpose of simplification, the details will be omitted.[000149] In some example embodiments, the condition may be associated with radio link failure (RLF) prediction. For example, the condition may comprise the terminal device 110 predicting no radio link failure. In this case, the terminal device 110 may log the data associated with the measured metric in its buffer if the terminal device 110 predicts no radio link failure. In this case, data collection may be performed if the radio link failure is not triggered, or in other words, the data associated with the measured metric may be logged if the terminal-based radio link failure prediction is false. Otherwise, if the radio link failure is predicted, the terminal device 110 may discard a measurement. For example, if the terminal device 110 predicts the radio link failure, it may stop the measurement and the collection of the data. The terminal device 110 may predict the radio link failure in any other available way and the scope of the present disclosure is not limited in this regard. This can ensure that the terminal device 110 collects data samples with the best radio conditions. It is allowed to assist the early detection of the possible radio link failure and recovery of the collected data by the network device 120.[000150] In the example implementations when there is predicted radio link failure, the terminal device 110 may perform data reporting accordingly. For example, the terminaldevice 110 may transmit, to the network device 120, an indication (also referred to as a data availability / ready indication) indicating that the data is ready for reporting due to a predicted radio link failure. For example, the terminal device 110 may transmit a data available indication with cause as predicted_RLF. The data availability / ready indication may help the network device 120 to know that the data has been collected in the buffer in the terminal device 110 and is ready to be reported. This may help the network device 120 to plan uplink resources to fetch the logged data from the terminal device 110.[000151] In example embodiments, if the terminal device 110 is unable to comply with the configuration for data collection received from the network device 120, the terminal device 110 may send a message to the network device 120 to indicate this failure. The message may comprise an RRC reconfiguration failure message or a new failure indication message dedicated to data collection.[000152] FIG. 8 illustrates an example communication process 800 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 800 may be considered as a more specific example of the signaling flow 200 as shown in FIG. 2. The UE 801 may be an example of the terminal device 110, and the gNB 802 may be an example of the network device 120.[000153] As shown in FIG. 8, at 803, a data collection trigger (i.e., an MDT based DC activation trigger for beam management) is received at the gNB 802. More implementations related to the operation 803 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 803 are omitted for brevity.[000154] At 805, a capability exchange may be performed, and the attach procedure is done. At 807, the gNB 802 configures the UE 801 with a data collection configuration. In this case, the UE 801 is configured with a radio link failure prediction based condition. For example, the UE may also be configured with LI RSRP thresholds associated with data collection specific SET A / B. At 809, the UE 801 accepts the RRC configuration related to radio link failure prediction based data collection. Otherwise, if the UE 801 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000155] At 811, the gNB 802 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 813, the UE 801 starts measuring the CSI-RSs and estimates the LI RSRR [000156] At 815, the estimated LI RSRP is logged in the AS buffer of the UE 801 if theUE based RLF prediction is false. This can ensure that the UE 801 collects data samples with the best radio conditions. During this process, if the UE 801 predicts the RLF, it stops the measurement and the collection of data. The RLF prediction is up to UE 801’s implementation, and this will help the early detection of the possible RLF and recovery of the collected data by the gNB 802.[000157] At 817, the UE 801 determines reporting conditions. At 819, the UE 801 sends a data available / ready indication with a cause as predicted_RLF. The data availability / ready indication helps the gNB 802 to know that the AS buffer in UE is full (or other conditions). This helps the gNB 802 to plan uplink resources to fetch the collected data from the UE 801.[000158] At 821, the gNB 802 requests data using, e.g., a UEInformationRequest message. At 823, the UE 801 sends logged data using, e.g., a UEInformationResponse message. At 825, the gNB 802 maps the collected data to relevant trace collection sessions. At 827, the collected data is sent to a trace collection entity.[000159] Operations and features as described above with reference to FIG. 2 are likewise applicable to the process 800 and have similar effects. For the purpose of simplification, the details will be omitted.[000160] It is to be understood that the above conditions may be combined when determining whether to log data at the terminal device 110. For example, the above condition associated with the at least one measurement threshold and the above condition associated with the target uplink waveform, the beam failure detection, congestion detection, downlink interference detection, and / or the radio link failure prediction may be combined when performing data logging.[000161] In some implementations, after the terminal device 110 informs the network device 120 about its data availability indication, it may happen that it is too late for the network device 120 to retrieve the data, and the terminal device 110 may have already discarded the data for an internal reason. Then, in this case, there may be no collected data to report when the network device 120 requests the data.[000162] FIG. 9 illustrates a signaling flow 900 between a terminal device and a network device according to some example embodiments of the present disclosure. For the purpose of discussion, the signaling flow 900 will be described with reference to FIG. 1A.[000163] As shown in FIG. 9, the network device 120 transmits (905), to the terminal device 110, a request message for data collected at the terminal device 110. For example, the request message may comprise a UEInformationRequest message. As shown in FIG. 9, upon the reception of the request message for the collected data, the terminal device 110 determines (910) that there is no collected data to report.[000164] As shown in FIG. 9, the terminal device 110 transmits (915), to the network device 120, a response message with an empty container. For example, the response message may comprise a flag indicating that the response message has no payload for collected data. Alternatively or additionally, the response message may comprise a discard flag / reason indication to indicate the reason for discarding the measurement, for example, if the data have already been discarded for an internal reason. As an example, the response message may comprise a UEInformationResponse message. Accordingly, the network device 120 may determine that no data is collected at the terminal device based on the response message.[000165] In some embodiments, an example abstract syntax notation one (ASN).l structure for the empty container may be as follows:UEInformationResponse-AIML-BM-rl9-IEs ::= SEQUENCE {measResult!dleEUTRA-rl9 MeasResultIdleEUTRA-rl9 OPTIONAL, measResult!dleNR-rl9 MeasResultIdleNR-rl9 OPTIONAL, logMeasReport-AIML-BM-r!9 LogMeasReport-AVML-BM-rl9 OPTIONAL, connEstFailReport-r!9 ConnEstFailReport-rl9 OPTIONAL, ra-ReportList-r!9 RA-ReportList-rl9 OPTIONAL, rlf-Report-r!9 RLF-Report-rl9 OPTIONAL, mobility HistoryReport-r 19 Mobility HistoryReport-rl9 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEInformationResponse-v 1700-IEs OPTIONAL }LogMeasReport-AIML-BM-rl9 : := SEQUENCE {logMeasInfoList-AVML-BM-rl9 LogMeasInfoList-AVML-BM-rl9,logMeas Available-r 19 ENUMERATED {true} OPTIONAL, logMeas AvailableBT-r 19 ENUMERATED {true} OPTIONAL, logMeas AvailableWL AN -r 19 ENUMERATED {true} OPTIONAL,LogMeasInfoList-AVML-BM-rl9 ::= SEQUENCE (SIZE (LmaxLogMeasReport-AIML-BM-rl9)) OF LogMeasInfo- AIML-BM-rl9LogMeasInfo-AIML-BM-rl9 ::= SEQUENCE {locationlnfo-rl9 Locationlnfo-rl9 OPTIONAL, relativeTimeStamp-r!9 INTEGER (0.7200),servCellIdentity-rl9 CGI- Info-Logging -r 19 OPTIONAL, eventType ENUMERATED {BufferFull, Beamfailure, RLF, UL Congestion, DL interference, PoorRadio}; OPTIONAL,isMsgWithoutPayload BOOLEAN;# True: without payload False: With payload measResultServingCell-AIML-BM-rl9 MeasResultServingCell- AIML-BM-rl9 OPTIONAL,measResultNeighCells-rl9 SEQUENCE {measResultNeighCellListNR MeasResultListLogging2NR-rl9 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-rl9OPTIONAL},anyCellSelectionDetected-r!9 ENUMERATED {true} OPTIONAL,[[inDeviceCoexDetected-rl9 ENUMERATED {true} OPTIONAL ]]}}[000166] FIG. 10 illustrates an example communication process 1000 according to some example embodiments of the present disclosure. It would be appreciated that the process flow 1000 may be considered as a more specific example of the signaling flow 900 as shown in FIG. 9. The UE 1001 may be an example of the terminal device 110, and the gNB 1002 may be an example of the network device 120.[000167] As shown in FIG. 10, at 1003, a data collection trigger is received at the gNB 1002. More implementations related to the operation 1003 may be similar to the operation 303 discussed above with reference to FIG. 3, and thus details of the operation 1003 are omitted for brevity.[000168] At 1005, a capability exchange may be performed, and the attach procedure is done. At 1007, the gNB 1002 configures the UE 1001 with a data collection configuration. In this case, the UE 1001 is configured with at least one LI RSRP threshold for SET A / B (for example, received from the data collection specific CSI-RS configurations). At 1009, the UE 1001 acknowledges the configuration of threshold-based events in an RRC configurationcomplete message. Otherwise, if the UE 1001 is unable to comply with the configuration, it may send either an RRC reconfiguration failure or a new failure indication message dedicated to data collection.[000169] At 1011, the gNB 1002 starts transmitting CSI-RSs in the DL for SET A / SET B beams. At 1013, the UE 1001 starts measuring the CSI-RSs and generates the specified quantity, i.e., report quantity indicated in the data collection configuration, such as CRI-RSRR [000170] At 1015, the measured LI quantity is logged in the AS buffer of the UE 301 if the value of the measured LI quantity is above a threshold configured by the gNB 302. Otherwise, the UE 1001 discards the measurement.[000171] At 1017, the gNB 1002 decides, based on internal conditions, to retrieve collected data from the UE 1001 without getting a data_ready indication from the UE 1001. At 1019, the gNB 1002 requests data using, e.g., a UEInformationRequest message. At 1021, the UE 1001 finds that the AS buffer is empty, for example, as none of the CRI-RSRP values were above the RSRP threshold. At 1023, the UE 1001 sends, e.g., a UEInformationResponse message with an empty container with a flag indicating the message has no payload.[000172] It should be understood that, although embodiments of the present disclosure are discussed with regard to data collection related to CSI, embodiments of the present disclosure may also apply to the data collection of any other types of information.[000173] It should be understood that the above embodiments of the present disclosure can apply to both network side data collection and terminal side data collection.[000174] According to some embodiments with reference to FIGS. 2 to 10, there is proposed a framework to collect the training data based on those events. The events and the data collection framework can be utilized by the network device to augment an existing training data set, which may lack enough data to train the models for the situations on which these events are based. An exhaustive list of events that need to be considered for data collection start and stop reporting has been provided. Further, it is allowed to enable the terminal device to effectively collect the data and report at a feasible interval. It is also proposed for the terminal device to indicate to the network device about data readiness with a suitable cause or data unavailable with a suitable cause. In this way, it is allowed to enhance communication performance and improve communication efficiency.[000175] FIG. 11 illustrates a flowchart 1100 of a method implemented at a terminaldevice according to some embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.[000176] At block 1110, the terminal device 110 obtains a configuration for data collection. The configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform.[000177] At block 1120, the terminal device 110 measures a reference signal transmitted from a network device 120 to obtain the measured metric.[000178] At block 1130, the terminal device 110 logs the data associated with the measured metric in the buffer of the terminal device 110 based on determining that a condition of the at least one condition is fulfilled.[000179] In some example embodiments, a condition of the at least one condition may comprise at least one of the following: a value of the measured metric being above or below a measurement threshold of the at least one measurement threshold; or an uplink waveform for the terminal device 110 being the target uplink waveform.[000180] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000181] In some example embodiments, the at least one measurement threshold may comprise a first measurement threshold associated with a first resource set and a second measurement threshold associated with a second resource set.[000182] In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to the buffer being full.[000183] In some example embodiments, the target uplink waveform may comprise discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM).[000184] In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to a poor radio condition.[000185] In some example embodiments, the terminal device 110 may further discard a measurement, based on determining that a condition of the at least one condition is not fulfilled.[000186] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000187] In some example embodiments, the obtaining the configuration may comprise at least one of receiving at least part of the configuration from the network device 120, or obtaining at least part of the configuration predefined in a standard specification.[000188] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 to 4 are likewise applicable to the method 1100 and have similar effects.[000189] FIG. 12 illustrates a flowchart 1200 of a method implemented at a network device 120 according to some embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the network device 120 with reference to FIG. 1A.[000190] At block 1210, the network device 120 transmits, to a terminal device 110, at least part of a configuration for data collection. The configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device 110, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform.[000191] At block 1220, the network device 120 transmits a reference signal to the terminal device 110.[000192] In some example embodiments, a condition of the at least one condition may comprise at least one of the following: a value of the measured metric being above or below a measurement threshold of the at least one measurement threshold; or an uplink waveform for the terminal device 110 being the target uplink waveform.[000193] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000194] In some example embodiments, the at least one measurement threshold may comprise a first measurement threshold associated with a first resource set and a secondmeasurement threshold associated with a second resource set.[000195] In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to the buffer being full.[000196] In some example embodiments, the target uplink waveform may comprise discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM).[000197] In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to a poor radio condition.[000198] In some example embodiments, the network device 120 may further receive, from a management system, one or more parameters for configuring the terminal device 110 for data collection.[000199] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000200] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 to 4 are likewise applicable to the method 1200 and have similar effects.[000201] FIG. 13 illustrates a flowchart 1300 of a method implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.[000202] At block 1310, the terminal device 110 receives, from a network device 120, a configuration for data collection. The configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device 110, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection.[000203] At block 1320, the terminal device 110 measures a reference signal transmitted from the network device 120 to obtain the measured metric.[000204] At block 1330, the terminal device 110 logs data associated with the measured metric in a buffer of the terminal device 110 based on determining that a condition of the atleast one condition is fulfilled.[000205] In some example embodiments, a condition of the at least one condition may comprise a beam failure indication count being below a count threshold for the beam failure detection, wherein the count threshold is comprised in the configuration. In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to the beam failure detection. In some example embodiments, the configuration may further comprise a reference signal resource for the beam failure detection.[000206] In some example embodiments, a condition of the at least one condition may comprise a congestion level being above or below a congestion threshold for the congestion detection, wherein the congestion threshold is comprised in the configuration. In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to the congestion detection. In some example embodiments, the congestion threshold may be based on uplink transmission buffer occupancy at the terminal device 110.[000207] In some example embodiments, a condition of the at least one condition may comprise a downlink interference level being above or below an interference threshold for the downlink interference detection, wherein the interference threshold is comprised in the configuration. In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to the downlink interference detection.[000208] In some example embodiments, the terminal device 110 may further discard a measurement, based on determining that a condition of the at least one condition is not fulfilled.[000209] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000210] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000211] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least onemeasurement threshold.[000212] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 and 5 to 7 are likewise applicable to the method 1300 and have similar effects.[000213] FIG. 14 illustrates a flowchart 1400 of a method implemented at a network device according to some embodiments of the present disclosure. For the purpose of discussion, the method 1400 will be described from the perspective of the network device 120 with reference to FIG. 1A.[000214] At block 1410, the network device 120 transmits, to a terminal device 110, a configuration for data collection. The configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device 110, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection.[000215] At block 1420, the network device 120 transmits a reference signal to the terminal device 110.[000216] In some example embodiments, a condition of the at least one condition may comprise a beam failure indication count being below a count threshold for the beam failure detection, wherein the count threshold is comprised in the configuration. In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to the beam failure detection. In some example embodiments, the configuration may further comprise a reference signal resource for the beam failure detection.[000217] In some example embodiments, a condition of the at least one condition may comprise a congestion level being above or below a congestion threshold for the congestion detection, wherein the congestion threshold is comprised in the configuration. In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to the congestion detection. In some example embodiments, the congestion threshold may be based on uplink transmission buffer occupancy at the terminal device 110.[000218] In some example embodiments, a condition of the at least one condition may comprise a downlink interference level being above or below an interference threshold for the downlink interference detection, wherein the interference threshold is comprised in theconfiguration. In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to the downlink interference detection.[000219] In some example embodiments, the network device 120 may further receive, from a management system, one or more parameters for configuring the terminal device 110 for data collection.[000220] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000221] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000222] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000223] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 and 5 to 7 are likewise applicable to the method 1400 and have similar effects.[000224] FIG. 15 illustrates a flowchart 1500 of a method implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, the method 1500 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.[000225] At block 1510, the terminal device 110 obtains a configuration for data collection. The configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device 110, and the condition is associated with radio link failure prediction.[000226] At block 1520, the terminal device 110 measures a reference signal transmitted from a network device 120 to obtain the measured metric.[000227] At block 1530, the terminal device 110 logs the data associated with the measured metric in the buffer of the terminal device 110 based on determining that the condition is fulfilled.[000228] In some example embodiments, the condition comprises the terminal device 110 predicting no radio link failure. In some example embodiments, the terminal device 110 may further transmit, to the network device 120, an indication indicating that the data is ready for reporting due to a predicted radio link failure.[000229] In some example embodiments, the terminal device 110 may further discard a measurement, based on determining that the condition is not fulfilled.[000230] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000231] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000232] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000233] In some example embodiments, the obtaining the configuration may comprise at least one of receiving at least part of the configuration from the network device 120, or obtaining at least part of the configuration predefined in a standard specification.[000234] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 and 8 are likewise applicable to the method 1500 and have similar effects.[000235] FIG. 16 illustrates a flowchart 1600 of a method implemented at a network device according to some embodiments of the present disclosure. For the purpose of discussion, the method 1600 will be described from the perspective of the network device 120 with reference to FIG. 1A.[000236] At block 1610, the network device 120 transmits, to a terminal device 110, a configuration for data collection. The configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device 110, and the condition is associated with radio link failure prediction.[000237] At block 1620, the network device 120 transmits a reference signal to the terminal device 110.[000238] In some example embodiments, the condition may comprise the terminal device 110 predicting no radio link failure. In some example embodiments, the network device 120 may further receive, from the terminal device 110, an indication indicating that the data is ready for reporting due to the predicted radio link failure.[000239] In some example embodiments, the measured metric may comprise at least one of the following reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000240] In some example embodiments, the network device 120 may further receive, from a management system, one or more parameters for configuring the terminal device 110 for data collection.[000241] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000242] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000243] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 2 and 8 are likewise applicable to the method 1600 and have similar effects.[000244] FIG. 17 illustrates a flowchart 1700 of a method implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, the method 1700 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.[000245] At block 1710, the terminal device 110 receives, from a network device 120, a request message for data collected at the terminal device 110.[000246] At block 1720, the terminal device 110 determines there is no collected data to report .[000247] At block 1730, the terminal device 110 transmits, to the network device 120, a response message with an empty container.[000248] In some example embodiments, the response message may comprise a flag indicating that the response message has no payload for collected data.[000249] In some example embodiments, the request message may comprise a UEInformationRequest message.[000250] In some example embodiments, the response message may comprise a UEInformationResponse message.[000251] In some example embodiments, the data may be associated with a measured metric that comprises at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI). In some example embodiments, the measured metric may be measured based on a channel state information reference signal (CSI-RS) or a synchronization signal (SSB).[000252] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 9 and 10 are likewise applicable to the method 1700 and have similar effects.[000253] FIG. 18 illustrates a flowchart 1800 of a method implemented at a network device 120 according to some embodiments of the present disclosure. For the purpose of discussion, the method 1800 will be described from the perspective of the network device 120 with reference to FIG. 1A.[000254] At block 1810, the network device 120 transmits, to a terminal device 110, a request message for data collected at the terminal device 110.[000255] At block 1820, the network device 120 receives, from the terminal device 110, a response message with an empty container.[000256] In some example embodiments, the response message may comprise a flag indicating that the response message has no payload for collected data.[000257] In some example embodiments, the network device 120 may further determine that no data is collected at the terminal device 110 based on the response message.[000258] In some example embodiments, the request message may comprise a UEInformationRequest message.[000259] In some example embodiments, the response message may comprise a UEInformationResponse message.[000260] In some example embodiments, the data may be associated with a measured metric that comprises at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000261] In some example embodiments, the measured metric may be measured based on a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000262] Those skilled in the art can understand that all operations and features as described above with reference to FIGS. 9 and 10 are likewise applicable to the method 1800 and have similar effects.[000263] In some example embodiments, an apparatus capable of performing the method 1100 (for example, the terminal device 110) may comprise means for performing the respective steps of the method 1100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000264] In some example embodiments, the apparatus comprises means for obtaining a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; means for measuring a reference signal transmitted from a network device to obtain the measured metric; and means for logging the data associated with the measured metric in the buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.[000265] In some example embodiments, a condition of the at least one condition may comprise at least one of the following: a value of the measured metric being above or below a measurement threshold of the at least one measurement threshold; or an uplink waveform for the terminal device being the target uplink waveform.[000266] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000267] In some example embodiments, the at least one measurement threshold may comprise a first measurement threshold associated with a first resource set and a second measurement threshold associated with a second resource set.[000268] In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to the buffer being full.[000269] In some example embodiments, the target uplink waveform may comprise discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM).[000270] In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to a poor radio condition.[000271] In some example embodiments, the apparatus may further comprise means for discarding a measurement, based on determining that a condition of the at least one condition is not fulfilled.[000272] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000273] In some example embodiments, the means for obtaining the configuration may comprise at least one of means for receiving at least part of the configuration from the network device, or means for obtaining at least part of the configuration predefined in a standard specification.[000274] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1100. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000275] In some example embodiments, an apparatus capable of performing the method 1200 (for example, the network device 120) may comprise means for performing the respective steps of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000276] In some example embodiments, the apparatus comprises means for transmitting, to a terminal device, at least part of a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with at least one measurement threshold, or a target uplink waveform; and means for transmitting a reference signal to the terminal device.[000277] In some example embodiments, a condition of the at least one condition maycomprise at least one of the following: a value of the measured metric being above or below a measurement threshold of the at least one measurement threshold; or an uplink waveform for the terminal device being the target uplink waveform.[000278] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000279] In some example embodiments, the at least one measurement threshold may comprise a first measurement threshold associated with a first resource set and a second measurement threshold associated with a second resource set.[000280] In some example embodiments, the apparatus may further comprise means for receiving, from the terminal device, an indication indicating that the data is ready for reporting due to the buffer being full.[000281] In some example embodiments, the target uplink waveform may comprise discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM).[000282] In some example embodiments, the apparatus may further comprise means for receiving, from the terminal device, an indication indicating that the data is ready for reporting due to a poor radio condition.[000283] In some example embodiments, the apparatus may further comprise means for receiving, from a management system, one or more parameters for configuring the terminal device for data collection.[000284] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000285] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1200. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000286] In some example embodiments, an apparatus capable of performing the method 1300 (for example, the terminal device 110) may comprise means for performing the respective steps of the method 1300. The means may be implemented in any suitable form.For example, the means may be implemented in a circuitry or software module.[000287] In some example embodiments, the apparatus comprises means for receiving, from a network device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; means for measuring a reference signal transmitted from the network device to obtain the measured metric; and means for logging data associated with the measured metric in a buffer of the terminal device based on determining that a condition of the at least one condition is fulfilled.[000288] In some example embodiments, a condition of the at least one condition may comprise a beam failure indication count being below a count threshold for the beam failure detection, wherein the count threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to the beam failure detection. In some example embodiments, the configuration may further comprise a reference signal resource for the beam failure detection.[000289] In some example embodiments, a condition of the at least one condition may comprise a congestion level being above or below a congestion threshold for the congestion detection, wherein the congestion threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to the congestion detection. In some example embodiments, the congestion threshold may be based on uplink transmission buffer occupancy at the terminal device.[000290] In some example embodiments, a condition of the at least one condition may comprise a downlink interference level being above or below an interference threshold for the downlink interference detection, wherein the interference threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to the downlink interference detection.[000291] In some example embodiments, the apparatus may further comprise menas for discarding a measurement, based on determining that a condition of the at least one condition is not fulfilled.[000292] In some example embodiments, the measured metric may comprise at least one of the following reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000293] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000294] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000295] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1300. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000296] In some example embodiments, an apparatus capable of performing the method 1400 (for example, the network device 120) may comprise means for performing the respective steps of the method 1400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000297] In some example embodiments, the apparatus comprises means for transmitting, to a terminal device, a configuration for data collection, wherein the configuration comprises at least one condition for logging data associated with a measured metric in a buffer of the terminal device, and the at least one condition is associated with one or more of beam failure detection; congestion detection; or downlink interference detection; and means for transmitting a reference signal to the terminal device.[000298] In some example embodiments, a condition of the at least one condition may comprise a beam failure indication count being below a count threshold for the beam failure detection, wherein the count threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for receiving, from the terminal device, an indication indicating that the data is ready for reporting due to the beam failure detection. In some example embodiments, the configuration may further comprise a reference signal resource for the beam failure detection.[000299] In some example embodiments, a condition of the at least one condition maycomprise a congestion level being above or below a congestion threshold for the congestion detection, wherein the congestion threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for receiving, from the terminal device, an indication indicating that the data is ready for reporting due to the congestion detection. In some example embodiments, the congestion threshold may be based on uplink transmission buffer occupancy at the terminal device.[000300] In some example embodiments, a condition of the at least one condition may comprise a downlink interference level being above or below an interference threshold for the downlink interference detection, wherein the interference threshold is comprised in the configuration. In some example embodiments, the apparatus may further comprise means for receiving, from the terminal device, an indication indicating that the data is ready for reporting due to the downlink interference detection.[000301] In some example embodiments, the apparatus may further comprise means for receiving, from a management system, one or more parameters for configuring the terminal device for data collection.[000302] In some example embodiments, the measured metric may comprise at least one of the following reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000303] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000304] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000305] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1400. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000306] In some example embodiments, an apparatus capable of performing the method 1500 (for example, the terminal device 110) may comprise means for performing the respective steps of the method 1500. The means may be implemented in any suitable form.For example, the means may be implemented in a circuitry or software module.[000307] In some example embodiments, the apparatus comprises means for obtaining a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; means for measuring a reference signal transmitted from a network device to obtain the measured metric; and means for logging the data associated with the measured metric in the buffer of the terminal device based on determining that the condition is fulfilled.[000308] In some example embodiments, the condition comprises the terminal device predicting no radio link failure.[000309] In some example embodiments, the apparatus may further comprise means for transmitting, to the network device, an indication indicating that the data is ready for reporting due to a predicted radio link failure.[000310] In some example embodiments, the apparatus may further comprise means for discarding a measurement, based on determining that the condition is not fulfilled.[000311] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000312] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000313] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data may be based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000314] In some example embodiments, the means for obtaining the configuration may comprise at least one of means for receiving at least part of the configuration from the network device, or means for obtaining at least part of the configuration predefined in a standard specification.[000315] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1500. In some embodiments, the means comprises at least one processor and at least one memory including computer program code,the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000316] In some example embodiments, an apparatus capable of performing the method 1600 (for example, the network device 120) may comprise means for performing the respective steps of the method 1600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000317] In some example embodiments, the apparatus comprises means for transmitting, to a terminal device, a configuration for data collection, wherein the configuration comprises a condition for logging data associated with a measured metric in a buffer of the terminal device, and wherein the condition is associated with radio link failure prediction; and means for transmitting a reference signal to the terminal device.[000318] In some example embodiments, the condition comprises the terminal device predicting no radio link failure. In some example embodiments, the apparatus may further comprise means for receive, from the terminal device, an indication indicating that the data is ready for reporting due to the predicted radio link failure.[000319] In some example embodiments, the measured metric may comprise at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI).[000320] In some example embodiments, the apparatus may further comprise means for receiving, from a management system, one or more parameters for configuring the terminal device for data collection.[000321] In some example embodiments, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000322] In some example embodiments, the configuration may comprise at least one measurement threshold and the logging of data is based on determining that a value of the measured metric is above or below a measurement threshold of the at least one measurement threshold.[000323] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1600. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least oneprocessor, cause the performance of the apparatus.[000324] In some example embodiments, an apparatus capable of performing the method 1700 (for example, the terminal device 110) may comprise means for performing the respective steps of the method 1700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000325] In some example embodiments, the apparatus comprises means for receiving, from a network device, a request message for data collected at the terminal device; means for determining there is no collected data to report; and means for transmitting, to the network device, a response message with an empty container.[000326] In some example embodiments, the response message may comprise a flag indicating that the response message has no payload for collected data.[000327] In some example embodiments, the request message may comprise a UEInformationRequest message.[000328] In some example embodiments, the response message may comprise a UEInformationResponse message.[000329] In some example embodiments, the data may be associated with a measured metric that comprises at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI). In some example embodiments, the measured metric may be measured based on a channel state information reference signal (CSI-RS) or a synchronization signal (SSB).[000330] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1700. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000331] In some example embodiments, an apparatus capable of performing the method 1800 (for example, the network device 120) may comprise means for performing the respective steps of the method 1800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.[000332] In some example embodiments, the apparatus comprises means for transmitting, to a terminal device, a request message for data collected at the terminal device; and meansfor receiving, from the terminal device, a response message with an empty container.[000333] In some example embodiments, the response message may comprise a flag indicating that the response message has no payload for collected data.[000334] In some example embodiments, the apparatus may further comprises means for determining that no data is collected at the terminal device based on the response message.[000335] In some example embodiments, the request message may comprise a UEInformationRequest message.[000336] In some example embodiments, the response message may comprise a UEInformationResponse message.[000337] In some example embodiments, the data may be associated with a measured metric that comprises at least one of the following: reference signal received power (RSRP); or a pre-coding matrix indicator (PMI). In some example embodiments, the measured metric may be measured based on a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).[000338] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1800. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.[000339] FIG. 19 illustrates a simplified block diagram of a device 1900 that is suitable for implementing some example embodiments of the present disclosure. The device 1900 may be provided to implement the communication device, for example, the terminal device 110 or the network device 120 as shown in FIG. 1A. As shown, the device 1900 includes one or more processors 1910, one or more memories 1920 coupled to the processor 1910, and one or more communication modules 1940 coupled to the processor 1910.[000340] The communication module 1940 is for bidirectional communications. The communication module 1940 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.[000341] The processor 1910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purposecomputers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.[000342] The memory 1920 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1924, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1922 and other volatile memories that will not last in the power-down duration.[000343] A computer program 1930 includes computer executable instructions that are executed by the associated processor 1910. The program 1930 may be stored in the ROM 1924. The processor 1910 may perform any suitable actions and processing by loading the program 1930 into the RAM 1922.[000344] The embodiments of the present disclosure may be implemented by means of the program 1930 so that the device 1900 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 10. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.[000345] In some example embodiments, the program 1930 may be tangibly contained in a computer readable medium which may be included in the device 1900 (such as in the memory 1920) or other storage devices that are accessible by the device 1900. The device 1900 may load the program 1930 from the computer readable medium to the RAM 1922 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.[000346] FIG. 20 illustrates a block diagram of an example of a computer readable medium 2000 in accordance with some example embodiments of the present disclosure. The computer readable medium 2000 has the program 1930 stored thereon. It is noted that although the computer readable medium 2000 is depicted in form of CD or DVD in FIG. 20, the computer readable medium 2000 may be in any other form suitable for carrying or holding the program 1930.[000347] Generally, various embodiments of the present disclosure may be implementedin hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.[000348] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method as described above with reference to any of FIGS. 11 to 18. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.[000349] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.[000350] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.[000351] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).[000352] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Eike wise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.[000353] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A terminal device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to:receive, from a network device, a request message for data collected at the terminal device;determine there is no collected data to report; andtransmit, to the network device, a response message with an empty container.

2. The terminal device of claim 1, wherein the response message comprises a flag indicating that the response message has no payload for collected data.

3. The terminal device of claim 1 or 2, wherein the request message comprises a UEInformationRequest message.

4. The terminal device of any of claims 1-3, wherein the response message comprises a UEInformationResponse message.

5. The terminal device of any of claims 1-4, wherein the data is associated with a measured metric that comprises at least one of the following:reference signal received power (RSRP); ora pre-coding matrix indicator (PMI).

6. The terminal device of claim 5, wherein the measured metric is measured based on a channel state information reference signal (CSI-RS) or a synchronization signal (SSB).

7. A network device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to:transmit, to a terminal device, a request message for data collected at theterminal device; andreceive, from the terminal device, a response message with an empty container.

8. The network device of claim 7, wherein the response message comprises a flag indicating that the response message has no payload for collected data.

9. The network device of claim 7 or 8, wherein the network device is further caused to:determine that no data is collected at the terminal device based on the response message.

10. The network device of any of claims 7-9, wherein the request message comprises a UEInformationRequest message.

11. The network device of any of claims 7-10, wherein the response message comprises a UEInformationResponse message.

12. The network device of any of claims 7-11, wherein the data is associated with a measured metric that comprises at least one of the following:reference signal received power (RSRP); ora pre-coding matrix indicator (PMI).

13. The network device of claim 12, wherein the measured metric is measured based on a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB).

14. A method comprising:receiving, at a terminal device, from a network device, a request message for data collected at the terminal device;determining, at the terminal device, there is no collected data to report; and transmitting, at the terminal device, to the network device, a response message with an empty container.

15. A method comprising:transmitting, at a network device, to a terminal device, a request message for data collected at the terminal device; andreceiving, at the network device, from the terminal device, a response message with an empty container.

16. An apparatus comprising:means for receiving, at a terminal device, from a network device, a request message for data collected at the terminal device;means for determining, at the terminal device, there is no collected data to report; and means for transmitting, at the terminal device, to the network device, a response message with an empty container.

17. An apparatus comprising:means for transmitting, at a network device, to a terminal device, a request message for data collected at the terminal device; andmeans for receiving, at the network device, from the terminal device, a response message with an empty container.

18. A non-transitory computer readable medium comprising program instructions, that, when executed by an apparatus, cause the apparatus to perform at least the method of claim 14 or 15.

Images