Training data retransmission

Abstract

Example embodiments of the present disclosure relate to a terminal device, a network entity, a method, an apparatus, a computer readable storage medium, and a computer program product for training data retransmission. In this solution, the terminal device can receive a data collection configuration from the network entity, and then store the reported data based on the configuration. Furthermore, data retransmission can be performed according to the stored data, and thus the data lost at the network side can be recovered. For example, a relaxed timer is configured, and thus the reported data can be stored for a relatively long time. For example, statistical information can be stored and provided, and thus the network side is able to evaluate the availability of the received data.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of communications, and more particularly to terminal devices, network entities, methods, apparatuses, computer-readable storage media, and computer program products for training data retransmission. Background Technology

[0002] Data collected at terminal devices (such as user equipment (UE)) can be used to train models, such as network-side models, UE-side models, or dual-side models. The UE can collect Layer 1 (L1) measurement data and / or Layer 3 (L3) measurement data and provide the collected data to the network. However, data transmission may fail, and in some cases, data retransmission may be required. In such cases, mechanisms for retransmitting the collected data should be investigated. Summary of the Invention

[0003] Overall, the exemplary embodiments of this disclosure provide a solution for training data retransmission.

[0004] In a first aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the instructions cause the terminal device to at least: receive a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; transmit the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission; receive a retransmission request from the network entity for at least a portion of the acquired data; and retransmit the at least a portion of the acquired data to the network entity based on the retransmission request.

[0005] In a second aspect, a network entity is provided. The network entity includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the instructions cause the network entity to at least: send a data acquisition configuration to a terminal device, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations; receive a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission; send a retransmission request to the terminal device for at least a portion of the acquired data based on a determination that retransmission is required; and receive the at least a portion of the acquired data from the terminal device based on the retransmission request.

[0006] In a third aspect, a method is provided. The method includes: receiving, at a terminal device, a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations; transmitting the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission; receiving from the network entity a retransmission request for at least a portion of the acquired data; and retransmitting the at least a portion of the acquired data to the network entity based on the retransmission request.

[0007] In a fourth aspect, a method is provided. The method includes: sending a data acquisition configuration at a network entity to a terminal device, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations; receiving a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission; sending a retransmission request to the terminal device for at least a portion of the acquired data based on a determination that retransmission is necessary; and receiving the at least a portion of the acquired data from the terminal device based on the retransmission request.

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes: components for receiving a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; components for transmitting the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission; components for receiving a retransmission request from the network entity for at least a portion of the acquired data; and components for retransmitting the at least a portion of the acquired data to the network entity based on the retransmission request.

[0009] In a sixth aspect, an apparatus is provided. The apparatus includes: components for transmitting a data acquisition configuration at a network entity to a terminal device, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations; components for receiving a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission; components for sending a retransmission request to the terminal device for at least a portion of the acquired data based on a determination that retransmission is required; and components for receiving the at least a portion of the acquired data from the terminal device based on the retransmission request.

[0010] In a seventh aspect, an apparatus is provided. The apparatus includes: a receiving circuitry configured to receive a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; a transmitting circuitry configured to transmit the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission; a receiving circuitry configured to receive a retransmission request from the network entity for at least a portion of the acquired data; and a retransmission circuitry configured to retransmit the at least a portion of the acquired data to the network entity based on the retransmission request.

[0011] In an eighth aspect, an apparatus is provided. The apparatus includes: a transmitting circuit system configured to transmit a data acquisition configuration to a terminal device, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; a receiving circuit system configured to receive a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission; a transmitting circuit system configured to transmit a retransmission request to the terminal device for at least a portion of the acquired data based on determining that retransmission is necessary; and a receiving circuit system configured to receive the at least a portion of the acquired data from the terminal device based on the retransmission request.

[0012] In a ninth aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the terminal device causes the terminal device to at least: receive a data acquisition configuration including measurement and reporting configuration from a network entity; transmit acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission; receive a release command from the network entity for discarding the stored data; and discard the stored acquired data based on the release command.

[0013] In a tenth aspect, a network entity is provided. The network entity includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the network entity causes the network entity to at least: send a data acquisition configuration including measurement and reporting configuration to a terminal device; receive a portion of acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device for retransmission; and send a release command to the terminal device for discarding the stored data.

[0014] In an eleventh aspect, a method is provided. The method includes: receiving from a network entity a data acquisition configuration including measurement and reporting configuration; transmitting acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission; receiving from the network entity a release command for discarding the stored data; and discarding the stored acquired data based on the release command.

[0015] In a twelfth aspect, a method is provided. The method includes: sending a data acquisition configuration, including measurement and reporting configuration, to a terminal device; receiving, based on the data acquisition configuration, a portion of acquired data from the terminal device, wherein the acquired data is stored at the terminal device for retransmission; and sending a release command to the terminal device for discarding the stored data.

[0016] In a thirteenth aspect, an apparatus is provided. The apparatus includes: components for receiving a data acquisition configuration including measurement and reporting configuration from a network entity; components for transmitting acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission; components for receiving a release command from the network entity for discarding the stored data; and components for discarding the stored acquired data based on the release command.

[0017] In a fourteenth aspect, an apparatus is provided. The apparatus includes: components for transmitting a data acquisition configuration including measurement and reporting configuration to a terminal device; components for receiving data acquired from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device for retransmission; and components for transmitting a release command to the terminal device for discarding the stored data.

[0018] In a fifteenth aspect, an apparatus is provided. The apparatus includes: a receiving circuit system configured to receive from a network entity a data acquisition configuration including measurement and reporting configurations; a transmitting circuit system configured to transmit acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission; a receiving circuit system configured to receive from the network entity a release command for discarding the stored data; and a discarding circuit system configured to discard the stored acquired data based on the release command.

[0019] In a sixteenth aspect, an apparatus is provided. The apparatus includes: a transmitting circuit system configured to transmit a data acquisition configuration including measurement and reporting configuration to a terminal device; a receiving circuit system configured to receive data acquired from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device for retransmission; and a transmitting circuit system configured to transmit a release command to the terminal device for discarding the stored data.

[0020] In a seventeenth aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the terminal device causes at least: receiving from a network entity a data acquisition configuration including measurement and reporting configuration; transmitting acquired data to the network entity based on the data acquisition configuration, wherein statistical information of the acquired data is stored for retransmission; receiving from the network entity a request for statistical information on at least a portion of the acquired data; and transmitting the statistical information of the at least a portion of the acquired data to the network entity based on the request.

[0021] In an eighteenth aspect, a network entity is provided. The network entity includes: at least one processor; and at least one memory storing instructions, wherein when executed by the at least one processor, the network entity causes at least: to send a data acquisition configuration including measurement and reporting configuration to a terminal device; to receive, based on the data acquisition configuration, a portion of the acquired data from the terminal device, wherein statistical information of the acquired data is stored at the terminal device for retransmission; to send a request to the terminal device for statistical information regarding at least a portion of the acquired data; and, based on the request, to receive the statistical information of the at least a portion of the acquired data from the terminal device.

[0022] In a nineteenth aspect, a method is provided. The method includes: receiving, at a terminal device, a data acquisition configuration including measurement and reporting configuration from a network entity; transmitting acquired data to the network entity based on the data acquisition configuration, wherein statistical information of the acquired data is stored for retransmission; receiving from the network entity a request for statistical information on at least a portion of the acquired data; and transmitting the statistical information on the at least a portion of the acquired data to the network entity based on the request.

[0023] In a twentieth aspect, a method is provided. The method includes: sending a data acquisition configuration, including measurement and reporting configuration, to a terminal device at a network entity; receiving, based on the data acquisition configuration, a portion of acquired data from the terminal device, wherein statistical information of the acquired data is stored at the terminal device for retransmission; sending a request to the terminal device for statistical information regarding at least a portion of the acquired data; and receiving, based on the request, the statistical information of the at least a portion of the acquired data from the terminal device.

[0024] In a twenty-first aspect, an apparatus is provided. The apparatus includes: components for receiving a data acquisition configuration including measurement and reporting configuration from a network entity; components for transmitting acquired data to the network entity based on the data acquisition configuration, wherein statistical information of the acquired data is stored for retransmission; components for receiving a request from the network entity for statistical information regarding at least a portion of the acquired data; and components for transmitting the statistical information of the at least a portion of the acquired data to the network entity based on the request.

[0025] In a twenty-second aspect, an apparatus is provided. The apparatus includes: components for transmitting a data acquisition configuration including measurement and reporting configuration to a terminal device; components for receiving a portion of acquired data from the terminal device based on the data acquisition configuration, wherein statistical information of the acquired data is stored at the terminal device for retransmission; components for transmitting a request to the terminal device for statistical information regarding at least a portion of the acquired data; and components for receiving the statistical information of the at least a portion of the acquired data from the terminal device based on the request.

[0026] In a twenty-third aspect, an apparatus is provided. The apparatus includes: a receiving circuit system configured to receive from a network entity a data acquisition configuration including measurement and reporting configuration; a transmitting circuit system configured to transmit acquired data to the network entity based on the data acquisition configuration, wherein statistical information of the acquired data is stored for retransmission; a receiving circuit system configured to receive from the network entity a request for statistical information regarding at least a portion of the acquired data; and a transmitting circuit system configured to transmit the statistical information of the at least a portion of the acquired data to the network entity based on the request.

[0027] In a twenty-fourth aspect, an apparatus is provided. The apparatus includes: a transmitting circuit system configured to transmit a data acquisition configuration including measurement and reporting configuration to a terminal device; a receiving circuit system configured to receive, based on the data acquisition configuration, a portion of the acquired data from the terminal device, wherein statistical information of the acquired data is stored at the terminal device for retransmission; a transmitting circuit system configured to transmit a request to the terminal device for statistical information regarding at least a portion of the acquired data; and a receiving circuit system configured to receive, based on the request, the statistical information of the at least a portion of the acquired data from the terminal device.

[0028] In the twenty-fifth aspect, a non-transient computer-readable medium including program instructions is provided for causing a device to perform the methods of any one of the third, fourth, eleventh, twelfth, nineteenth, or twentieth aspects.

[0029] In the twenty-sixth aspect, a computer program including instructions is provided that, when executed by a device, causes the device to perform the method of any one of the third, fourth, eleventh, twelfth, nineteenth, or twentieth aspects.

[0030] It should be understood that the summary portion is not intended to represent key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

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

[0032] Figure 1 The illustration shows an example of a network environment in which some exemplary embodiments of the present disclosure may be implemented;

[0033] Figure 2 Examples of process flows according to some exemplary embodiments of this disclosure are illustrated;

[0034] Figure 3 The illustration shows an example procedure for measuring L1 channel state information (CSI) according to some example embodiments of the present disclosure;

[0035] Figure 4 The illustration shows an example process of location data according to some example embodiments of the present disclosure;

[0036] Figure 5 The illustration shows an example process for statistical information according to some example embodiments of this disclosure;

[0037] Figure 6 The illustration shows a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0038] Figure 7 The illustration shows a flowchart of a method implemented at a network entity according to some example embodiments of the present disclosure;

[0039] Figure 8 The illustration shows a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0040] Figure 9 The illustration shows a flowchart of a method implemented at a network entity according to some example embodiments of the present disclosure;

[0041] Figure 10 The illustration shows a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0042] Figure 11The illustration shows a flowchart of a method implemented at a network entity according to some example embodiments of the present disclosure;

[0043] Figure 12 The illustration shows a simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure; and

[0044] Figure 13 A block diagram illustrating an example of a computer-readable medium according to some exemplary embodiments of the present disclosure is shown.

[0045] Unless otherwise stated, the same or similar reference numerals in all figures denote the same or similar elements. Detailed Implementation

[0046] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

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

[0048] References to "an embodiment," "an embodiment," "an example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, it is believed that its influence in conjunction with other embodiments on such feature, structure, or characteristic is within the knowledge of those skilled in the art.

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

[0050] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” also include the plural forms. It should also be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “including” as used herein specify the presence of stated features, elements, and / or components, but do not exclude 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 is connected by “and” or “or”) means at least any one element, or at least any two or more elements, or at least all elements.

[0051] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of the (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) Multiple hardware circuits and / or multiple processors, such as multiple microprocessors or a portion thereof, that require software (e.g., firmware) to operate, but which may be absent when no software is required to operate.

[0052] This definition of circuit system applies to all uses of the term in this application (including in any claim). As a further example, as used herein, the term circuit system also covers only hardware circuitry or a processor (or processors) or a portion thereof and its accompanying software and / or firmware implementation. For example, where suitable for a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0053] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Non-Terrestrial Network (NTN), NTN-based Internet of Things, Wi-Fi, and so on. Furthermore, communication within a communication network can be performed according to any suitable communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols, the IEEE 802.11 protocol, and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0054] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. A network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a New Radio (NR) NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Headend (RH), a Remote Radio Headend (RRH), an Integrated Access and Backhaul (IAB) node, a relay, or a low-power node (such as a femtosecond, picosecond, etc.), depending on the terminology and technology used.

[0055] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), access terminal (AT), or Internet of Things (IoT) device. Terminal devices may include, but are not limited to: mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, machine-type communication (MTC) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0056] In this disclosure, "network entity" refers to entities, nodes, functions, etc., on the network side. For example, a network entity can be one of the following: network equipment (such as access network nodes), core network (CN) entities, operation, administration and maintenance (OAM), UE servers, over-the-top services (OTT), etc. For example, a CN entity can be a CN function associated with a specific use case, such as a location management function (LMF) used to locate the use case.

[0057] Any data transmitted over the air in mobile networks is susceptible to packet loss. Given the challenging nature of wireless communication environments, receivers may fail to correctly decode transmitted signals. In 5G NR, the Hybrid Automatic Repeat Request (HARQ) process is used at the Media Access Control (MAC) layer to improve the spectral efficiency and reliability of communication by enabling Forward Error Correction (FEC) and data retransmission. In HARQ, the receiver checks for errors in the received data. If an error is detected, the receiver with HARQ enabled buffers the (erroneous) data and requests a retransmission from the transmitter. This receiver then combines the buffered data with the newly transmitted data before performing channel decoding and error detection, thereby improving receiver performance. Another retransmission protocol is Automatic Repeat Request (ARQ), which is used in Radio Link Control (RLC) layer in ACK mode. In ARQ, if the receiver detects an error, it discards the data and requests a retransmission, where RLC has three modes: transparent mode (only for the control plane), unacknowledged mode (only for user plane data), and acknowledged mode (for both the user plane and control plane).

[0058] In any data acquisition (DC) scheme in a mobile network, data collected from the UE can be used to train artificial intelligence (AI) or machine learning (ML) models. For example, the UE can collect L1 data with PHY layer configuration. For instance, in beam management use cases, CSI-MeasConfig is used to configure the UE. Traditionally, data such as L1 CSI measurements are reported to the network using the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). While the HARQ retransmission protocol is applied to the PUSCH, the retransmission protocol is not used on the PUCCH. Model inference and monitoring operations will use this mechanism to reliably send measured and predicted CSI reports; while in training data acquisition, the UE can send at least some CSI measurements in L3 (e.g., via RRC messages), and L1 may also be used to collect some training data.

[0059] Data is prone to gaps, for example, when data is sent from the UE to other entities (such as gNB / CN entities). This can lead to AI / ML models being trained using incomplete or insufficient data, resulting in biased, underfitting, or unrepresentative models that do not fully represent the current scenario. In some cases, this can even lead to training failure and require the entire data acquisition process to be repeated.

[0060] One straightforward solution is to reuse or extend retransmission protocols to ensure data is correctly delivered to the NW. However, retransmission protocols are not suitable for the PUCCH channel, one of the channels carrying L1 measurements such as CSI measurements. Another drawback of using such retransmission protocols is that they do not account for the necessary communication between the UE and the CN entity (e.g., for positioning). More importantly, when acquiring measurements for training the UE and / or network-side models, HARQ / ARQ retransmission mechanisms are insufficient because data will be sent via (multiple) RRC messages.

[0061] Another aspect to consider is the complexity of the retransmission protocol. For example, if PUSCH is used to send training data, blindly applying HARQ to the training data might waste training data acquisition, as ML model training can handle some missing values ​​in the dataset. In other words, by applying HARQ, all measured data can be correctly delivered to the UE, but in some cases, losing some insignificant measurements or samples is acceptable. This will help keep signaling overhead to a minimum.

[0062] Therefore, when collecting training data from UEs, it is necessary to address how to effectively recover lost data.

[0063] Embodiments of this disclosure provide a solution for retransmitting data related to AI / ML models. In this solution, the terminal device can receive a data acquisition configuration from a network entity and then store the reported data based on that configuration. Furthermore, data retransmission can be performed based on the stored data, and thus data lost on the network side can be recovered. For example, a relaxed timer can be configured, allowing the reported data to be stored for a relatively long period. For example, statistical information can be stored and provided, enabling the network side to assess the availability of the received data. The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings.

[0064] Figure 1 The illustration shows an example of a network environment 100 in which some exemplary embodiments of the present disclosure may be implemented. Network environment 100 may be part of a communication network, including terminal device 110, network device 120, OAM 130, OTT 140, and CN entity 150. Network environment 100 may also be referred to as a network system, communication environment, communication network, communication system, etc., and the present disclosure is not limited in this respect. In some examples, terminal device 110 may be connected to CN entity 150 via network device 120. In some examples, terminal device 110 may be directly connected to CN entity 150.

[0065] CN entity 150 may include one or more CN functions, such as location management function (LMF), user plane function (UPF), network data analysis function (NWDAF), etc.

[0066] The communication environment 100 may include any suitable number of devices and cells. In the communication environment 100, network device 120 may provide services to terminal device 110, and network device 120 and terminal device 110 may exchange data and control information. In some embodiments, network device 120 and terminal device 110 may communicate via a direct link / channel.

[0067] In system 100, the link from network device 120 to terminal device 110 is referred to as a downlink (DL), and the link from terminal device 110 to network device 120 is referred to as an uplink (UL). In the downlink, network device 120 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In the uplink, terminal device 110 is a transmitting (TX) device (or transmitter), and network device 120 is an RX device (or receiver). It should be understood that network device 120 can provide one or more serving cells. In some embodiments, network device 120 can provide multiple cells.

[0068] Communication in network environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocol currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0069] In a split-type Radio Access Network (RAN), network devices can refer to a centralized unit (CU) and / or a distributed unit (DU) of a base station. The interface between the CU and DU may be referred to as the F1 interface in NR. In a split-type RAN architecture, node operations can be performed at least partially in a central / centralized unit (CU, such as a server, host, or node) operatively coupled to a DU (e.g., a radio headend / node). A CU can control one or more DUs, at least acting as a transmit / receive (Tx / Rx) node. In some embodiments, a DU may include, for example, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer, while a CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, the Radio Resource Control (RRC) layer, and the Internet Protocol (IP) layer. Other functional splitting is also possible. In practice, any processing task can be performed in a CU or a DU, and the boundary of the transfer of responsibilities between the CU and DU may depend on the applied implementation.

[0070] It should be understood that Figure 1 The number, connection relationships, and types of devices shown (i.e., terminal device 110 and network device 120) are for illustrative purposes only and do not imply any limitations. For example, environment 100 may include any number of devices suitable for implementing embodiments of this disclosure. For example, although Figure 1 Terminal device 110 is described as a mobile phone, but terminal device 110 can be any type of user equipment.

[0071] This disclosure introduces a novel retransmission protocol for data acquired in relation to AI / ML models, where the data may include training data for model training, inference data for model inference, monitoring data for model monitoring, and so on. For example, if training data is transmitted via a channel (such as PUCCH) or via RRC, or from terminal device 110 to CN entity 150, the new retransmission protocol for training data should be enabled. For example, this new retransmission protocol can be considered a model data retransmission protocol. For example, this new retransmission protocol at least enables retransmission of lost data and error detection. For example, the new retransmission protocol enables forward error correction (FEC).

[0072] In this disclosure, the term "data" can refer to data related to an AI / ML model. For example, data can include data used for training, inference, or monitoring of the AI / ML model. For instance, data can include training data, inference data, or monitoring data used to generate the AI / ML model. In some examples, data can be determined or generated by terminal device 110, and may include, but is not limited to, the following: L1 measurement data, L3 measurement data, CSI measurement data, beam measurement data, reference signal received power (RSRP) for beams and cells, location-related measurement data, etc. In some examples, data can be transmitted / sent from terminal device 110 to network entities via the user plane or control plane.

[0073] Figure 2 An example of a process flow 200 according to some exemplary embodiments of the present disclosure is illustrated. Process flow 200 relates to terminal device 110 and network entity 210. For example, network entity 210 may be… Figure 1 The network device 120 (such as a gNB), OAM 130, OTT 140, or CN entity 150 illustrated herein, or network entity 210, may be a server, such as a UE vendor, used to train AI / ML models deployed on the UE side. In some examples, signaling between terminal device 110 and network entity 210 may be performed via another entity; for example, OAM 130, OTT 140, or CN entity 150 may communicate with terminal device 110 via network device 120.

[0074] In process flow 200, at point 202, terminal device 110 may send capability information to network entity 210. In some implementations, this capability information may indicate whether terminal device 110 supports storing data for retransmission. In some implementations, this capability information may indicate whether terminal device 110 supports determining and storing statistical information. In some examples, terminal device 110 has the capability to store data for retransmission and also has the capability to determine and store statistical information for the data.

[0075] In some example embodiments, terminal device 110 supports storing data for retransmission. In some examples, terminal device 110 has logging capabilities for enabling new retransmission protocols. In some examples, terminal device 110 has logging capabilities for retransmission. For example, terminal device 110 can store (log) sent data (or reported data) in a cache for retransmission.

[0076] In some example embodiments, terminal device 110 may have functions related to statistical information. In some examples, terminal device 110 supports calculating (or determining) statistical information, storing statistical information, and reporting statistical information. Details regarding statistical information can be found below.

[0077] In some example embodiments, the capability information may also indicate whether the terminal device 110 supports storing data that has not been transmitted. In some examples, the terminal device 110 may support storing data for transmission or have the capability for training data acquisition. For example, the terminal device 110 may store data (or log) in a cache for transmission. For example, the terminal device 110 may store untransmitted data (or log) in a cache for scheduling.

[0078] It should be noted that the logging capability for retransmission differs from the logging capability for transmission. For example, the logging capability for transmission indicates the ability to store data that has not yet been sent. For example, the logging capability for retransmission indicates the ability to store data that has already been sent. In this disclosure, terminal device 110 has a logging capability for retransmission, but may or may not have a logging capability for transmission.

[0079] In process flow 200, at point 204, network entity 210 sends a configuration, and terminal device 110 receives the configuration. In some embodiments, this configuration may be a data acquisition configuration, which may include a measurement configuration and a reporting configuration (or a measurement and reporting configuration). For example, the measurement configuration may indicate the measurement object, measurement period, measurement metric, etc. For example, the reporting configuration may indicate the reporting object, reporting period, report message size, etc.

[0080] In some example embodiments, this configuration indicates a timer for storing the collected data for retransmission. In some examples, the timer is associated with log data for retransmission. In some examples, the timer may be a loose timer, an extended timer, a retransmission log timer, a retransmission timer, a retransmission protocol timer, a timer for a new retransmission protocol, a timer for retransmitted log data, a timer for a retransmission protocol for training data collection, etc., and this disclosure does not limit it in this respect.

[0081] In some examples, timers are introduced to accommodate a more relaxed latency for training data acquisition. For instance, the timer's duration can be longer than that of the timer used for the HARQ process. For example, a timer used for the HARQ process is nearly real-time and has a maximum latency of only a few retransmissions, while the timer used for training data acquisition in this disclosure may require a more relaxed latency. For example, the timer's duration indicated in the configuration at 204 can be in one of the following units: week, day, hour, minute, or second. For example, the timer's duration indicated in the configuration at 204 can be in units of the number of transmissions performed.

[0082] In some examples, the configuration can indicate the duration of the configuration used to determine the statistics. For example, the duration of the configuration could be the period from the time the data was collected (or stored, or sent) to the current time.

[0083] In process flow 200, terminal device 110 can execute steps 212, 214, and 216 based on configuration. In some examples, these steps may be repeated because available transport resources may be limited.

[0084] At 212, terminal device 110 can perform measurements based on its configuration to acquire the collected data. In some examples, terminal device 110 can perform L1 or L3 measurements; therefore, the data can be either L1 or L3 measurement data.

[0085] At point 216, terminal device 110 can transmit the collected data to network entity 210. It should be noted that embodiments of this disclosure are not limited to the signaling or messages used for transmitting data. In some examples, any of the following can be used to carry data from terminal device 110 to network entity 210: Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Radio Resource Control (RRC) signaling, application layer signaling, or Long Term Evolution (LTE) Positioning Protocol (LPP) messages via the Non-Access Stratum (NAS). For example, data can be carried in user plane (UP) packets. It should be noted that this disclosure does not limit the channels used for data transmission.

[0086] Furthermore, at 214, data is stored for retransmission, for example, based on configuration. For example, a timer associated with the stored data for retransmission can be started. This timer can be started at the point in time when the collected data is stored (or transmitted). For example, if the introduced retransmission protocol only supports error detection, terminal device 110 may need to log and save the data based on a configured or predefined timer, where the timer can be started based on rules defined in the specification or on configured rules. For example, terminal device 110 may start the timer based on a set of predefined rules or a configured timer, depending on the UE implementation / capabilities.

[0087] Alternatively, terminal device 110 stores statistics on the collected data. In some example embodiments, terminal device 110 may determine and store statistics on data over a duration. For example, the duration may be a time window when training data collection is activated or configured. In some examples, statistics may be stored for data within a configured duration (which may be represented by T). For example, the configured duration refers to the duration from the point in time when the collected data begins to be stored / reported to the current time. For example, the configured duration refers to the duration from the point in time when training data collection begins to the current time when terminal device 110 has sent the latest report. In some examples, statistics may be stored for data within a specific duration. For example, the specific duration may be the duration during the generation / collection / storage / reporting of data. In some examples, the statistics may be updated as additional data is collected and stored.

[0088] In some examples, statistical information about the data may include measures of the data, such as one or more of the following: maximum, minimum, mean, variance, median, mode, weighted mean, truncated mean, standard deviation, range (the difference between the maximum and minimum values), absolute deviation of the mean, skewness, kurtosis, quantiles, moments, covariance, correlation coefficient, cross-correlation matrix, confidence interval, autocorrelation, etc. In some examples, statistical information about the data may include the number of samples or the number of measurements.

[0089] In process flow 200, at 220, network entity 210 performs error detection. Optionally, network entity 210 may perform error correction on the received data. In some example embodiments, network entity 210 may determine a decoding failure rate based on the received data. For example, network entity 210 may determine the number of received data packets (or data samples or data bits), e.g., N1. For example, network entity 210 may determine the number of data packets (or data samples or data bits) that have been successfully / correctly decoded, e.g., N2. For example, network entity 210 may determine a decoding failure rate (p%) based on N1 and N2. In some examples, network entity 210 may determine statistics about the data received by network entity 210.

[0090] In some implementations, at 222, network entity 210 can send, and terminal device 110 can receive, a request for statistical information. In some example embodiments, if the determined decoding failure rate is higher than a threshold, network entity 210 can determine that an error has been detected. In some examples, if the determined decoding failure rate is higher than a threshold, network entity 210 can send a request for statistical information. For example, the threshold could be 20%, 25%, or other values.

[0091] At point 224, based on a request for statistical information, terminal device 110 can send and network entity 210 can receive statistical information. In some example embodiments, the reported statistical information may include a measure of the collected data (or a portion of the collected data), wherein the measure may be the measure described above. For example, statistical information on data collected / sent / stored over a specific period of time may be provided from terminal device 110 to network entity 210.

[0092] In some examples, a request for statistics is sent before the timer expires. For example, network entity 210 may start a timer when it begins receiving data from terminal device 110. At 222, for example, based on the determination that the timer has not expired, network entity 210 may send a request for statistics.

[0093] In some examples, statistics are sent before the timer expires. At 224, for example, terminal device 110 may send statistics based on the determination that the timer has not expired. On the other hand, if the timer expires, terminal device 110 may discard (or release, or delete) the stored statistics.

[0094] In this way, network entity 210 can obtain statistical information. Furthermore, network entity 210 can determine whether the received data is sufficient, or whether it is unnecessary to retransmit lost data.

[0095] For example, network entity 210 can estimate / assess the severity of lost data, such as using a decoding failure rate of p%. For example, if the mean (1-p%) of the data correctly decoded at network entity 210 is close to the mean indicated by statistics reported from terminal device 110, the severity of the lost data can be assumed to be low. For example, the mean indicated by the reported statistics could be the mean over all measurements, which was performed during the period when training data acquisition was activated or configured, and therefore includes 100% of the transmitted data. For example, the difference or ratio between the mean (1-p%) of the data correctly decoded at network entity 210 and the reported mean is less than a predefined threshold.

[0096] In some cases, the severity of the lost data can be considered high if the mean (1-p%) of the correctly decoded data at network entity 210 is not close to the mean indicated by statistics reported from terminal device 110. For example, the difference or ratio between the mean (1-p%) of the correctly decoded data at network entity 210 and the reported mean is greater than a predefined threshold. For example, network entity 210 may determine that the lost data is important to the model and that the lost data needs to be retransmitted.

[0097] In some implementations, at 232, network entity 210 can send a retransmission request, and terminal device 110 can receive the retransmission request. In some example embodiments, if network entity 210 determines that data decoding has failed, it can send a retransmission request. In some example embodiments, if network entity 210 determines (e.g., after 224) that the severity of the lost data is high, it can send a retransmission request. In some examples, the retransmission request can be implemented as a negative acknowledgment (NACK).

[0098] It should be noted that retransmission requests can be made at [time range]. Figure 2 The 224 in the sequence is sent after the 224, or it can be sent without steps 222 and 224.

[0099] In some examples, a retransmission request may indicate lost data, such as which portion of the data should be retransmitted. In some examples, a retransmission request may indicate a statistical measure of the data received at network entity 210. In some examples, a retransmission request may indicate a decoding failure rate determined by network entity 210.

[0100] In some examples, a retransmission request may include statistics on the data received by network entity 210. In some examples, terminal device 110 may estimate the severity of data loss at network entity 210 based on statistics on the data received by network entity 210 and statistics on the data stored at terminal device 110.

[0101] For example, if the statistical measure of the data received by network entity 210 is close to the statistical measure of the data collected at terminal device 110 (the difference between them is less than a threshold), then terminal device 110 can determine that the severity of the data loss at network entity 210 is low. Therefore, terminal device 110 can determine not to retransmit at least part of the collected data.

[0102] For example, if the statistical measure of the data received by network entity 210 differs significantly from the statistical measure of the data collected at terminal device 110 (the difference is greater than a threshold), terminal device 110 can determine that the severity of data loss at network entity 210 is high. Therefore, terminal device 110 can determine to retransmit at least a portion of the collected data based on a retransmission request.

[0103] At step 234, terminal device 110 may also send a data retransmission, and network entity 210 may perform the data retransmission. In some examples, terminal device 110 may retransmit some data based on a retransmission request. In some examples, if terminal device 110 determines that retransmission is necessary (e.g., the severity of data loss at network entity 210 is high), terminal device 110 may retransmit some data based on a retransmission request. For example, terminal device 110 may retransmit some of the stored data (e.g., some or all of the lost data indicated by the retransmission request) based on statistical measures of the data received at network entity 210. In some examples, the retransmitted data is retained (or stored or logged) after step 234 as long as the timer has not expired.

[0104] In some examples, a retransmission request is sent before the timer expires. At 232, for example, network entity 210 may send a retransmission request based on the determination that the timer has not expired. For example, if the timer expires, no retransmission request will be sent.

[0105] In some examples, data retransmission is performed before the timer expires. At 234, for example, based on the determination that the timer has not expired, terminal device 110 can perform data retransmission. On the other hand, if the timer expires, terminal device 110 can discard (or release, or delete) the stored data intended for retransmission.

[0106] Alternatively, network entity 210 may perform error detection after receiving retransmitted data. In some examples, if the decoding failure rate is still higher than a threshold, steps 232-234 may be performed again. In other examples, if the decoding failure rate is lower than a threshold, network entity 210 may determine that the received data is sufficient for model training.

[0107] In some implementations, at point 242, network entity 210 can send a release command, and terminal device 110 can receive the release command. In some example embodiments, the release command is used to discard stored data (or data and statistics) logged at terminal device 110. In some example embodiments, the release command is sent while the timer is still running (i.e., the timer has not expired).

[0108] In some examples, the release command may instruct terminal device 110 to discard the stored collected data. In some examples, the release command may instruct terminal device 110 to discard the stored statistics of the data. In some examples, the release command may instruct terminal device 110 to discard both the stored collected data and the stored statistics of the data.

[0109] In some examples, the release command can indicate a time period, for example, during which data and / or statistics stored (or collected) should be discarded.

[0110] Furthermore, at 244, terminal device 110 can discard stored collected data (and optional statistics) based on a release command (e.g., the release command is received before the timer expires).

[0111] It is important to note that steps 242-244 do not depend on steps 222-224 or 232-234. For example, at 220, if network entity 210 determines that the encoding failure rate is below a threshold and no data retransmission is required, then step 242 can be executed after 220 without steps 222-234. Similarly, if network entity 210 determines that the lost data is not important to the training data after 224, then step 242 can be executed after 224 without steps 232-234.

[0112] In some examples, the release command can be implemented as an acknowledgment (ACK) of the data. For example, network entity 210 can send an ACK of the data, which can implicitly indicate that the stored data can be discarded, wherein the ACK is sent before the timer expires.

[0113] In some implementations, at point 252, terminal device 110 discards the stored collected data (and optional statistics, if any) when the timer expires. For example, if no release command is received before the timer expires, the stored data can be discarded based on the timer's expiration.

[0114] Alternatively, network entity 210 may perform additional operations based on the received and collected data. In some examples, network entity 210 may perform model training, model inference, model monitoring, and so on. For example, network entity 210 may generate more data based on the received data, for example, using interpolation or interpolation methods. In some examples, network entity 210 may determine to initiate another data collection process to obtain more data.

[0115] Thus, based on receiving a release command before the timer expires or based on the timer's expiration, stored data can be discarded, and the cache can be cleared for further use, thereby improving the utilization of storage resources.

[0116] It should be noted that this disclosure does not impose any restrictions. Figure 2 The type of network entity 210 in the text, for example, network entity 210 may be a training server located on the network side, or it may be a tracking acquisition entity (TCE) that initiates training data acquisition.

[0117] In some examples, the training server may receive statistics from the terminal device 110 (e.g., via a gNB or other entity) and may also (i) generate new synthetic samples based on the statistics, and / or (ii) use interpolation methods to solve problems and train an unbiased model. For example, the training server may use interpolation methods to determine missing data with values.

[0118] In some examples, a split architecture can be applied, meaning that network device 120 may include a DU and a CU. In this case, the retransmission protocol applies to communication between the UE and the DU, as well as between the DU and the CU.

[0119] Figure 3 An example procedure 300 for L1 CSI measurement according to some example embodiments of the present disclosure is illustrated. Procedure 300 relates to, for example... Figure 1 The diagram illustrates a terminal device 110 (such as a UE) and a network device 120 (such as a gNB). For example, process 300 could be a case of data acquisition using a data acquisition unit gNB for beam measurement, and is related to signaling enhancement between the UE and the gNB.

[0120] At step 1, terminal device 110 may perform UE capability exchange with network device 120. For example, assume that the UE is enabled to calculate and store statistics (one or more metrics) for lost data recovery. For example, the UE may not have the ability to log training data acquisition, but it may have the ability to log data used for retransmission.

[0121] In step 2, network device 120 configures terminal device 110 to measure and report data. For example, when the UE is in the RRC_CONNECTED state, configuration can be provided to the UE via an RRC message. For example, a new retransmission protocol can be enforced and indicated to the UE. For example, the configuration can include configurations for L1 measurement and L1 reporting. For example, the configuration can indicate when data is collected from the UE to be used as training data, performance data, or monitoring data.

[0122] In some examples, the configuration may include instructions for a new retransmission protocol. For instance, a new retransmission protocol could be applied to data acquisition where the data is used not only for training but also for fine-tuning ML models and / or performance monitoring. For ease of description, the new retransmission protocol may be referred to as a data acquisition (DC) retransmission protocol.

[0123] In some cases, if a new retransmission protocol should be applied, it may not be necessary to instruct on a new retransmission protocol.

[0124] In some examples, the configuration may instruct the UE to calculate and store one or more metrics (e.g., mean, variance, third-order statistic kurtosis, etc.) as statistics.

[0125] In some examples, the configuration may indicate a timer, which can be a loose timer or an extended timer discussed above. In some examples, there is a timer pre-configured for the new retransmission protocol, and the terminal device 110 can determine the timer associated with the new retransmission protocol.

[0126] In step 3, terminal device 110 measures L1 layer resources (e.g., reference signals, such as CSI-RS) based on the configuration provided by network device 120.

[0127] At step 4, terminal device 110 stores and updates the statistics of L1 measurements. In some examples, the UE can calculate the metric of L1 measurements taken during a duration based on a new retransmission protocol. For example, the new retransmission protocol is active during that duration. For example, the configuration has indicated that duration.

[0128] For example, a metric can be determined for all data samples or a subset of data samples within a configured duration. It should be noted that the duration can also be referred to as the length of time, a time period, a time window, etc., and this disclosure does not limit this terminology. For example, statistics (metrics) should be calculated and updated for data within that duration.

[0129] At step 5, terminal device 110 stores L1 measurements (e.g., original measurements) based on a timer configured for the new retransmission protocol.

[0130] At step 6, terminal device 110 sends an L1 report to network device 120. The L1 report may include the L1 measurement data collected at step 3. In some examples, additional data (e.g., data for performance monitoring) may be sent along with the L1 report.

[0131] At step 7, network device 120 performs error detection on the received data and optionally performs error correction. In some examples, the gNB can calculate the decoding failure rate because it knows the number of packets / bits received and how many packets / bits have been correctly decoded.

[0132] At step 8, network device 120 may request statistical information from terminal device 110, for example, if a high decoding failure rate is detected when decoding data at step 7.

[0133] At step 9, terminal device 110 sends the updated statistics (metrics) stored at step 4. For example, network device 120 can use this statistics to determine whether including erroneous data as missing values ​​is detrimental to the current task (e.g., training). Details can be found in the reference. Figure 2 Those that were discussed.

[0134] In step 10, network device 120 may request a retransmission before the timer expires. In step 11, terminal device 110 may retransmit the requested data, and if the retransmission protocol timer is valid, retain the data.

[0135] At step 12, network device 120 may send a release command to discard the logged data and clear the cache at terminal device 110. For example, the release command may be sent if network device 120 receives retransmitted data and has an acceptable decoding failure rate or zero errors.

[0136] At step 13, if terminal device 110 receives an explicit release command from network device 120, or implicitly if a timer expires, terminal device 110 may discard the logged data.

[0137] For example, even without using the release command, logged data (and statistics) can be discarded. From the perspective of releasing UE logs more quickly, the release command can improve the efficiency of the solution, thus allowing this capability to be reused for other purposes.

[0138] According to the reference Figure 3 In some embodiments, L1 reports can be used for data transmission and enable retransmission protocols for data retransmission, for use cases such as beam management data acquisition.

[0139] Figure 4 An example of a process 400 for location data according to some exemplary embodiments of the present disclosure is illustrated. As shown, process 400 relates to terminal device 110 and LMF 152, wherein LMF 152 may be... Figure 1 CN entity 150 in the context. For example, process 400 could be a case where data acquisition is located using data acquisition device LMF 152. It should be understood that HARQ / ARQ procedures are not applied to data transmission from terminal device 110 to LMF 152.

[0140] Steps 1 and 2 with Figure 3 The steps are similar, so their details will not be repeated.

[0141] In step 3, LMF 152 via LPP requestLocationInformation The terminal device 110 requests this data. In step 4, the terminal device 110 stores and updates statistics and raw data for potential retransmission requests. In step 5, the terminal device 110 via... LPP ProvideLocationInformation Send the data to LMF 152.

[0142] At step 6, the LMF 152 detects errors during decoding. For example, the LMF 152 can perform error detection and optional error correction for retransmission protocols.

[0143] At step 7, LMF 152 passes through LPP Error Request statistical information from terminal device 110. For example, if LMF152 determines a high decoding failure rate, it can send... LPP Error Message. For example, LPP Error The message can indicate the reason for the error for the request. For example, LPP Error The message can be an enhanced error message.

[0144] At step 8, for example by LPP ProvideAssistanceData The terminal device 110 provides statistical information.

[0145] At step 9, terminal device 110 performs a retransmission. In some examples, an ACK may be required, and if terminal device 110 does not receive an ACK, it may retransmit, for example, statistics before a timeout period (e.g., up to 3 times). For example, the timeout period may be determined based on the UE implementation, such as a minimum of not less than 250 milliseconds.

[0146] At step 10, LMF 152 sends an acknowledgment for retransmission. For example, terminal device 110 may discard stored data and statistics based on the received acknowledgment.

[0147] In some examples, if LMF 152 does not send any acknowledgment after the timer expires, terminal device 110 may suspend all LPP activities for the associated session.

[0148] It should be noted that process 400 is discussed for illustrative purposes only and is not limited in any way; for example, some of the steps described above may also be applied. For instance, LMF 152 may send a release command to discard logged data at terminal device 110, thereby complying with the data acquisition and retransmission protocol requirements.

[0149] Figure 5 An example process 500 for providing statistical information according to some exemplary embodiments of the present disclosure is illustrated. As shown in the figure, process 500 relates to terminal device 110, network device 120, and network entity 510. For example, network entity 510 may be OAM 130, CN entity 150, or OTT 140. For example, network entity 510 may include a training server located at CN entity 150. For example, process 500 may be used to detail how statistical information is provided from terminal device 110 to network entity 510 via network device 120.

[0150] In process 500, at 502, network entity 510 sends a data acquisition configuration to network device 120, and furthermore, at 504, network device 120 may forward the data acquisition configuration to terminal device 110.

[0151] In some examples, the data acquisition configuration can be configured with information related to statistics, such as duration and metrics to be calculated.

[0152] Alternatively, data collection configuration can be enhanced using requests for collected statistics. Alternatively, separate requests for statistics can be provided.

[0153] In process 500, at 506, terminal device 110 sends statistical information to network device 120, and furthermore, at 508, network device 120 may forward it to network entity 510.

[0154] In some examples, network entity 510 may decide to train an AI / ML model based on received statistical information; for example, the model may be a UE-side model, an NW-side model, or a dual-side model. In some examples, network entity 510 may decide to perform interpolation or other evaluations based on received statistical information.

[0155] According to embodiments of this disclosure, a retransmission protocol can be defined to effectively enable lost data recovery when data is collected from the UE. By using the solution in this disclosure, the retransmission protocol can be applied to any communication channel between the UE and any network entity. Furthermore, signaling overhead can be kept to a minimum possible level.

[0156] Figure 6 The illustration shows a flowchart of a method 600 implemented at a terminal device according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 1 The angle description method of terminal device 110 in the middle is 600.

[0157] At block 610, terminal device 110 receives a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations. At block 620, terminal device 110 sends the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission. At block 630, terminal device 110 receives a retransmission request from the network entity for at least a portion of the acquired data. At block 640, terminal device 110 retransmits the at least a portion of the acquired data to the network entity based on the retransmission request.

[0158] In some example embodiments, the terminal device starts a timer when storing or sending the collected data; and based on determining that the timer has expired, the terminal device discards the stored collected data.

[0159] In some example embodiments, the terminal device receives a request from a network entity for statistical information on the collected data; and the terminal device sends the statistical information on the collected data to the network entity based on the request.

[0160] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0161] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0162] In some example embodiments, the terminal device sends capability information to the network entity, which indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0163] In some example embodiments, the collected data includes one of the following: channel state information (CSI) measurement data, beam measurement data, or location-related measurement data.

[0164] In some example embodiments, the collected data is sent to the network entity via one of the following: Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Radio Resource Control (RRC) signaling, application layer signaling, or Long Term Evolution (LTE) Positioning Protocol (LPP) messages via the Non-Access Stratum (NAS).

[0165] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0166] In some example embodiments, the network entity includes one of the following: a wireless access network node, a core network entity, an OAM, a server, or an OTT.

[0167] Figure 7 The illustration shows a flowchart of a method 700 implemented at a network entity according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 2 The perspective description method 700 for network entity 210 in the text can be... Figure 1 Any of the network devices 120 (such as gNB), OAM 130, OTT 140, or CN entity 150 illustrated herein.

[0168] At block 710, at the network entity, network entity 210 sends a data acquisition configuration to the terminal device, which indicates a timer for storing the acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations. At block 720, based on the data acquisition configuration, network entity 210 receives a portion of the acquired data from the terminal device, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission. At block 730, based on determining that retransmission is necessary, network entity 210 sends a retransmission request to the terminal device for at least a portion of the acquired data. At block 740, based on the retransmission request, network entity 210 receives the at least a portion of the acquired data from the terminal device.

[0169] In some example implementations, the network entity starts a timer when it receives the data collected in this part; and based on determining that the timer has expired, the network entity stops sending the retransmission request.

[0170] In some example embodiments, the network entity determines a decoding failure rate based on the received data; and based on the determination that the decoding failure rate is greater than a threshold, sends a request to the terminal device for statistical information on the collected data; receives the statistical information on the collected data from the terminal device; and determines whether retransmission is required based on the statistical information on the collected data and the statistical information on the received data.

[0171] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0172] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0173] In some example embodiments, the network entity receives capability information from the terminal device that indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0174] In some example embodiments, the collected data includes one of the following: CSI measurement data, beam measurement data, or location-related measurement data.

[0175] In some example embodiments, the collected data is sent to the network entity via one of the following: PUCCH, PUSCH, RRC signaling, application layer signals, or LPP messages via NAS.

[0176] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0177] In some example embodiments, the network entity includes one of the following: a radio access network node, a core network entity, an OAM, a server, or an OTT.

[0178] Figure 8 The illustration shows a flowchart of a method 800 implemented at a terminal device according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 1 The angle description method of the terminal device 110 in the middle is 800.

[0179] At box 810, terminal device 110 receives a data acquisition configuration, including measurement and reporting configurations, from a network entity. At box 820, terminal device 110 sends the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission. At box 830, terminal device 110 receives a release command from the network entity for discarding the stored data. At box 840, the terminal device discards the stored acquired data based on the release command.

[0180] In some example embodiments, the data acquisition configuration indicates a timer for storing the acquired data for retransmission, and the terminal device discards the stored acquired data based on a release command received before the timer expires; or discards the stored acquired data based on the timer's expiration.

[0181] In some example embodiments, the terminal device stores statistical information of the collected data.

[0182] In some example embodiments, the release command instructs the terminal device to discard the collected data and / or the statistics of the collected data. In some example embodiments, the terminal device discards the statistics of the collected data based on the release command.

[0183] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0184] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0185] In some example embodiments, the terminal device sends capability information to the network entity, which indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0186] In some example embodiments, the collected data includes one of the following: CSI measurement data, beam measurement data, or location-related measurement data.

[0187] In some example embodiments, the collected data is sent to the network entity via one of the following: PUCCH, PUSCH, RRC signaling, application layer signals, or LPP messages via NAS.

[0188] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0189] In some example embodiments, the network entity includes one of the following: a radio access network node, a core network entity, an OAM, a server, or an OTT.

[0190] Figure 9 The illustration shows a flowchart of a method 900 implemented at a network entity according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 2 The perspective description method 900 for network entity 210 in the text can be... Figure 1 Any of the network devices 120 (such as gNB), OAM 130, OTT 140, or CN entity 150 illustrated herein.

[0191] At box 910, network entity 210 sends a data acquisition configuration, including measurement and reporting configurations, to the terminal device. At box 920, based on this data acquisition configuration, network entity 210 receives a portion of the acquired data from the terminal device, wherein the acquired data is stored at the terminal device for retransmission. At box 930, network entity 210 sends a release command to the terminal device for discarding the stored data.

[0192] In some example embodiments, the data acquisition configuration indicates a timer for storing the acquired data for retransmission, and the network entity starts the timer when it receives the portion of the acquired data; and sends a release command based on the determination that the acquired data does not need to be retransmitted and the timer has not expired.

[0193] In some example embodiments, the release command instructs the terminal device to discard the collected data and / or the statistics of the collected data.

[0194] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0195] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0196] In some example embodiments, the network entity receives capability information from the terminal device that indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0197] In some example embodiments, the collected data includes one of the following: CSI measurement data, beam measurement data, or location-related measurement data.

[0198] In some example embodiments, the collected data is sent to the network entity via one of the following: PUCCH, PUSCH, RRC signaling, application layer signals, or LPP messages via NAS.

[0199] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0200] In some example embodiments, the network entity includes one of the following: a radio access network node, a core network entity, an OAM, a server, or an OTT.

[0201] Figure 10 The illustration shows a flowchart of a method 1000 implemented at a terminal device according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 1Angle description method 1000 for terminal device 110 in the middle.

[0202] At block 1010, terminal device 110 receives a data acquisition configuration, including measurement and reporting configuration, from a network entity. At block 1020, terminal device 110 sends the acquired data to the network entity based on the data acquisition configuration, wherein statistics of the acquired data are stored for retransmission. At block 1030, terminal device 110 receives a request from the network entity for statistics on at least a portion of the acquired data. At block 1040, terminal device sends the statistics of the at least a portion of the acquired data to the network entity based on the request.

[0203] In some example embodiments, the terminal device receives a retransmission request from a network entity for the at least portion of the collected data; and the terminal device sends the at least portion of the collected data to the network entity based on the retransmission request.

[0204] In some example embodiments, the retransmission request includes an indication of retransmission conditions, wherein the retransmission conditions indicate that the statistical measure of the data received by the network entity does not match the statistical information of the at least partially collected data.

[0205] In some example embodiments, statistics are determined based on data over a duration that is configured by the network entity or based on the time used to collect or store the collected data.

[0206] In some example embodiments, the data acquisition configuration indicates a timer for storing the acquired data for retransmission, and the terminal device stores the acquired data and statistical information of the acquired data based on the timer.

[0207] In some example embodiments, based on the determination that a timer has expired, the terminal device discards the stored collected data and the stored statistical information of the collected data.

[0208] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0209] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0210] In some example embodiments, the terminal device sends capability information to the network entity, which indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0211] In some example embodiments, the collected data includes one of the following: CSI measurement data, beam measurement data, or location-related measurement data.

[0212] In some example embodiments, the collected data is sent to the network entity via one of the following: PUCCH, PUSCH, RRC signaling, application layer signals, or LPP messages via NAS.

[0213] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0214] In some example embodiments, the network entity includes one of the following: a radio access network node, a core network entity, an OAM, a server, or an OTT.

[0215] Figure 11 The illustration shows a flowchart of a method 1100 implemented at a network entity according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 2 The perspective description method 1100 of network entity 210 in the text can be... Figure 1 Any of the network devices 120 (such as gNB), OAM 130, OTT 140, or CN entity 150 illustrated herein.

[0216] At box 1110, network entity 210 sends a data acquisition configuration, including measurement and reporting configurations, to the terminal device. At box 1120, based on this data acquisition configuration, network entity 210 receives a portion of the acquired data from the terminal device, wherein statistical information of the acquired data is stored at the terminal device for retransmission. At box 1130, the network entity sends a request to the terminal device for statistical information on at least a portion of the acquired data. At box 1140, based on this request, the network entity receives the statistical information of the at least a portion of the acquired data from the terminal device.

[0217] In some example embodiments, based on the determination that the difference between the statistics of the collected data and the statistics of the received data is greater than a threshold, the network entity sends a retransmission request to the terminal device for at least a portion of the collected data; and the network entity receives the at least a portion of the collected data from the terminal device based on the retransmission request.

[0218] In some example embodiments, statistics are determined based on data over a duration configured by the network entity or based on the time used to collect or store the collected data.

[0219] In some example embodiments, the data acquisition configuration indicates a timer for storing the acquired data for retransmission, and the network entity starts the timer when it receives the portion of the acquired data; and sends a request for statistics before the timer expires.

[0220] In some example embodiments, the statistical information includes one of the following of the collected data: maximum value, minimum value, mean, median, standard deviation, skewness, kurtosis, or variance.

[0221] In some example embodiments, the duration of the timer has an upper limit of one of the following units: week, day, hour, minute, or second.

[0222] In some example embodiments, the network entity receives capability information from the terminal device that indicates that the terminal device supports at least one of the following: storing data related to the AI ​​model for retransmission, or determining statistics on the stored data.

[0223] In some example embodiments, the collected data includes one of the following: CSI measurement data, beam measurement data, or location-related measurement data.

[0224] In some example embodiments, the collected data is sent to the network entity via one of the following: PUCCH, PUSCH, RRC signaling, application layer signals, or LPP messages via NAS.

[0225] In some example embodiments, the collected data is used to generate at least one of the following: training data, inference data, or monitoring data.

[0226] In some example embodiments, the network entity includes one of the following: a radio access network node, a core network entity, an OAM, a server, or an OTT.

[0227] In some example embodiments, the apparatus capable of performing method 600 (e.g., terminal device 110) may include components for performing the corresponding steps of method 600. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0228] In some example embodiments, the apparatus includes: components for receiving a data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; components for transmitting the acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored based on the indicated timer for retransmission; components for receiving a retransmission request from the network entity for at least a portion of the acquired data; and components for retransmitting the at least a portion of the acquired data to the network entity based on the retransmission request.

[0229] In some example embodiments, the apparatus capable of performing method 700 (e.g., network entity 210) may include components for performing the corresponding steps of method 700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0230] In some example embodiments, the apparatus includes: components for sending a data acquisition configuration to a terminal device, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes a measurement and reporting configuration; components for receiving a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission; components for sending a retransmission request to the terminal device for at least a portion of the acquired data based on determining that retransmission is required; and components for receiving the at least a portion of the acquired data from the terminal device based on the retransmission request.

[0231] In some example embodiments, the apparatus capable of performing method 800 (e.g., terminal device 110) may include components for performing the corresponding steps of method 800. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0232] In some example embodiments, the apparatus includes: components for receiving a data acquisition configuration including measurement and reporting configuration from a network entity; components for transmitting acquired data to the network entity based on the data acquisition configuration, wherein the acquired data is stored for retransmission; components for receiving a release command from the network entity for discarding the stored data; and components for discarding the stored acquired data based on the release command.

[0233] In some example embodiments, the apparatus capable of performing method 900 (e.g., network entity 210) may include components for performing the corresponding steps of method 900. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0234] In some example embodiments, the apparatus includes: components for sending a data acquisition configuration including measurement and reporting configuration to a terminal device; components for receiving data acquired from the terminal device based on the data acquisition configuration, wherein the acquired data is stored at the terminal device for retransmission; and components for sending a release command to the terminal device for discarding the stored data.

[0235] In some example embodiments, the apparatus capable of performing method 1000 (e.g., terminal device 110) may include components for performing the corresponding steps of method 1000. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0236] In some example embodiments, the apparatus includes: components for receiving a data acquisition configuration including measurement and reporting configuration from a network entity; components for transmitting acquired data to the network entity based on the data acquisition configuration, wherein statistics of the acquired data are stored for retransmission; components for receiving a request from the network entity for statistics of at least a portion of the acquired data; and components for transmitting the statistics of the at least a portion of the acquired data to the network entity based on the request.

[0237] In some example embodiments, the apparatus capable of performing method 1100 (e.g., network entity 210) may include components for performing the corresponding steps of method 1100. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0238] In some example embodiments, the apparatus includes: components for sending a data acquisition configuration including measurement and reporting configuration to a terminal device; components for receiving a portion of the acquired data from the terminal device based on the data acquisition configuration, wherein statistical information of the acquired data is stored at the terminal device for retransmission; components for sending a request to the terminal device for statistical information of at least a portion of the acquired data; and components for receiving the statistical information of the at least a portion of the acquired data from the terminal device based on the request.

[0239] The term "component" as used in the specification and claims can refer to one or more independent elements configured to perform one or more corresponding functions as described, or it can refer to several elements performing such one or more functions. Furthermore, the functions described in the claims can be performed by the same independent component or a combination of the same components. For example, performing such one or more functions can be done in the device by a processor executing instructions stored in the device's memory.

[0240] Figure 12A simplified block diagram of a device 1200 suitable for implementing some example embodiments of the present disclosure is illustrated. The device 1200 may be provided to implement the terminal devices discussed above, such as terminal device 110 or network entity 210. As shown, the device 1200 includes one or more processors 1210, one or more memories 1220 coupled to the processors 1210, and one or more communication modules 1240 coupled to the processors 1210.

[0241] The communication module 1240 is used for bidirectional communication. The communication module 1240 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0242] Processor 1210 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1200 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock that synchronizes with the main processor.

[0243] Memory 1220 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1224, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1222 and other volatile memories that do not persist during power-off periods.

[0244] Computer program 1230 includes computer-executable instructions that are executed by the associated processor 1210. Program 1230 may be stored in ROM 1224. Processor 1210 may perform any suitable actions and processes by loading program 1230 into RAM 1222.

[0245] Embodiments of this disclosure can be implemented using program 1230, enabling device 1200 to execute as described in the reference. Figures 2-11 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0246] In some example embodiments, program 1230 may be tangibly contained in a computer-readable medium, which may be included in device 1200 (such as in memory 1220) or in other storage devices accessible by device 1200. Device 1200 may load program 1230 from the computer-readable medium into RAM 1222 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0247] Figure 13 A block diagram of an example of a computer-readable medium 1300 according to some exemplary embodiments of the present disclosure is illustrated. The computer-readable medium 1300 has a program 1230 stored thereon. It should be noted that, although in Figure 13 The computer-readable medium 1300 is depicted in the form of a CD or DVD, but the computer-readable medium 1300 may be any other form suitable for carrying or storing the program 1230.

[0248] Various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0249] This disclosure also provides at least one computer program product tangibly stored on a non-transient computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, which are executed in a device on a target real or virtual processor to perform the functions described above in reference 2- Figure 11 The method described in any diagram. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as desired. The machine-executable instructions for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0250] The program code used in the methods of this disclosure can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code can be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0251] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0252] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. As used herein, the term "non-transient" is a limitation on the medium itself (i.e., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0253] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all illustrated operations be performed to achieve the desired result. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable sub-combination.

[0254] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the terminal device to at least: Receive data acquisition configuration from a network entity, the data acquisition configuration indicating a timer for storing acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configuration; Based on the data acquisition configuration, the acquired data is sent to the network entity, wherein the acquired data is stored based on the indicated timer for retransmission; Receive a retransmission request from the network entity for at least a portion of the collected data; as well as Based on the retransmission request, the at least part of the collected data is retransmitted to the network entity.

2. The terminal device according to claim 1, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the terminal device to: The timer is started when the collected data is stored or transmitted; and Based on the timer expiring, the stored collected data is discarded.

3. The terminal device according to claim 1, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the terminal device to: A request to receive statistical information about the collected data from the network entity; and Based on the request, the statistical information of the collected data is sent to the network entity.

4. The terminal device according to claim 3, wherein the statistical information includes one of the following of the collected data: maximum value, minimum value, average value, median, standard deviation, skewness, kurtosis, or variance.

5. The terminal device according to claim 1, wherein the timer has an upper limit of one of the following units: week, day, hour, minute or second.

6. The terminal device according to claim 1, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the terminal device to: Send capability information to the network entity, the capability information indicating that the terminal device supports at least one of the following: Store data related to the AI ​​model for retransmission, or Determine the statistical information of the stored data.

7. The terminal device according to claim 1, wherein the collected data includes one of the following: Channel State Information (CSI) measurement data Beam measurement data, or Location-related measurement data.

8. The terminal device of claim 1, wherein the collected data is transmitted to the network entity via one of the following: Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Radio Resource Control (RRC) signaling, application layer signals, or Long Term Evolution (LTE) Positioning Protocol (LPP) messages via Non-Access Stratum (NAS).

9. The terminal device of claim 1, wherein the collected data is used to generate an artificial intelligence (AI) model using at least one of the following: training data, inference data, or monitoring data.

10. The terminal device according to claim 1, wherein the network entity includes one of the following: Wireless access network node; Core network entity; Operations Management and Maintenance (OAM); server; or Overhead OTT services.

11. A network entity, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the network entity to at least: Send a data acquisition configuration to the terminal device, the data acquisition configuration indicating a timer for storing the acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configuration; Based on the data acquisition configuration, the data acquired by the receiving portion is received from the terminal device, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission. Based on the determination that retransmission is required, a retransmission request for at least a portion of the collected data is sent to the terminal device. as well as Based on the retransmission request, the terminal device receives at least a portion of the collected data.

12. The network entity of claim 11, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the network entity to: The timer is started when the data collected in the aforementioned portion is received; and Based on the determination that the timer has expired, the retransmission request is stopped.

13. The network entity of claim 11, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the network entity to: The decoding failure rate is determined based on the received data; as well as Based on the determination that the decoding failure rate is greater than a threshold, a request for statistical information on the collected data is sent to the terminal device; Receive statistical information from the collected data from the terminal device; as well as Based on the statistical information of the collected data and the statistical information of the received data, it is determined that retransmission is required.

14. The network entity of claim 13, wherein the statistical information includes one of the following of the collected data: maximum value, minimum value, average value, median, standard deviation, skewness, kurtosis, or variance.

15. The network entity of claim 11, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the network entity to: The terminal device receives capability information, which indicates that the terminal device supports at least one of the following: Store data related to the AI ​​model for retransmission, or Determine the statistical information of the stored data.

16. The network entity of claim 11, wherein the collected data is transmitted to the network entity via one of the following: Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Radio Resource Control (RRC) signaling, application layer signaling, or Long Term Evolution (LTE) Location Protocol (LPP) messages via Non-Access Stratum (NAS).

17. The network entity of claim 11, wherein the collected data is used to generate an artificial intelligence (AI) model from at least one of the following: training data, inference data, or monitoring data.

18. The network entity of claim 11, wherein the network entity comprises one of the following: Wireless access network node; Core network entity; Operations Management and Maintenance (OAM); server; or Overhead OTT services.

19. A method for communication, comprising: At the terminal device, a data acquisition configuration is received from a network entity. The data acquisition configuration indicates a timer for storing the acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations. Based on the data acquisition configuration, the acquired data is sent to the network entity, wherein the acquired data is stored based on the indicated timer for retransmission. Receive a retransmission request from the network entity for at least a portion of the collected data; as well as Based on the retransmission request, the at least part of the collected data is retransmitted to the network entity.

20. A method for communication, comprising: A network entity sends a data acquisition configuration to a terminal device, the data acquisition configuration indicating a timer for storing the acquired data for retransmission, wherein the data acquisition configuration includes measurement and reporting configurations; Based on the data acquisition configuration, the data acquired by the receiving portion is received from the terminal device, wherein the acquired data is stored at the terminal device based on the indicated timer for retransmission. Based on the determination that retransmission is required, a retransmission request for at least a portion of the collected data is sent to the terminal device. as well as Based on the retransmission request, the terminal device receives at least a portion of the collected data.

Images