Data collection method and apparatus, and node

By receiving and collecting data based on identification information, the problem of redundant data collection in data services is solved, thereby improving data collection efficiency.

WO2026233279A1PCT designated stage Publication Date: 2026-11-12VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

In existing technologies, the separate data collection by different data services increases the probability of data duplication, resulting in low data collection efficiency.

Method used

The first node receives identification information sent by the second or third node, collects data based on the identification information, and sends a data report to the second node. The data report includes at least one identification and the data corresponding to each identification.

Benefits of technology

By identifying data types through identification information, the data collected by the first node can be used by multiple different nodes, reducing the probability of data duplication and improving data collection efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026094759_12112026_PF_FP_ABST
    Figure CN2026094759_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and discloses a data collection method and apparatus, and a node. The data collection method in the embodiments of the present application comprises: a first node receives identification information sent by a second node or a third node, the identification information comprising at least one identifier; the first node performs data collection on the basis of the identification information; and the first node sends a data report to the second node, the data report comprising the at least one identifier and data corresponding to each identifier among the at least one identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Data collection method, apparatus and node

[0001] Cross-reference to Related Applications

[0002] This application claims priority to Chinese Patent Application No. 202510591457.2 filed on May 08, 2025 in China, the contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and specifically relates to a data collection method, apparatus and node. BACKGROUND

[0004] Communication awareness fusion, artificial intelligence (AI) and communication application scenarios promote network systems to have data service capabilities such as awareness services, AI services and computing services. Data services involve data collection, privacy security management, storage, opening and other processes. The data required by different data services may be the same or overlap. In the related art, different data services collect data respectively, which leads to a high probability of repeated data collection and low data collection efficiency. SUMMARY

[0005] Embodiments of the present application provide a data collection method, apparatus and node, which can solve the problem of low data collection efficiency.

[0006] In a first aspect, a data collection method is provided, which includes:

[0007] The first node receives identification information sent by the second node or the third node, and the identification information includes at least one identifier.

[0008] The first node collects data based on the identification information.

[0009] The first node sends a data report to the second node, and the data report includes the at least one identifier and data corresponding to each identifier in the at least one identifier.

[0010] In a second aspect, a data collection method is provided, which includes:

[0011] The second node receives a data report sent by the first node, and the data report includes at least one identifier and data corresponding to each identifier in the at least one identifier.

[0012] The second node sends corresponding data to a fourth node associated with the at least one identifier.

[0013] In a third aspect, a data collection method is provided, which includes:

[0014] The third node receives a data collection request sent by at least one fourth node;

[0015] The third node sends identification information to the first node, and the identification information includes at least one identifier.

[0016] Fourthly, a data collection device is provided, comprising:

[0017] A receiving module is used to receive identification information sent by a second node or a third node, wherein the identification information includes at least one identifier;

[0018] The processing module is used to collect data based on the identification information;

[0019] The sending module is used to send a data report to the second node. The data report includes the at least one identifier and the data corresponding to each of the at least one identifier.

[0020] Fifthly, a data collection device is provided, comprising:

[0021] The receiving module is configured to receive a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0022] The sending module is used to send corresponding data to the at least one fourth node associated with the identifier.

[0023] Sixthly, a data collection device is provided, comprising:

[0024] The receiving module is used to receive data collection requests sent by at least one fourth node;

[0025] The sending module is used to send identification information to the first node, the identification information including at least one identifier.

[0026] In a seventh aspect, a data collection apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0027] Eighthly, a node is provided, the node including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first, second, or third aspect.

[0028] Ninthly, a first node is provided, including a processor and a communication interface, wherein,

[0029] A communication interface is used to receive identification information sent by a second node or a third node, wherein the identification information includes at least one identifier;

[0030] A processor for collecting data based on the identification information;

[0031] The communication interface is also used to send a data report to the second node, the data report including the at least one identifier and data corresponding to each of the at least one identifier.

[0032] In a tenth aspect, a second node is provided, including a processor and a communication interface, wherein,

[0033] A communication interface is used to receive a data report sent by a first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0034] The communication interface is also used to send corresponding data to the at least one fourth node associated with the identifier.

[0035] Eleventhly, a third node is provided, including a processor and a communication interface, wherein,

[0036] A communication interface for receiving data collection requests from at least one fourth node;

[0037] The communication interface is also used to send identification information to the first node, the identification information including at least one identifier.

[0038] In a twelfth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0039] In a thirteenth aspect, a wireless communication system is provided, comprising a first node and a second node; or comprising a first node, a second node, and a third node. The first node may be used to perform the steps of the method described in the first aspect, the second node may be used to perform the steps of the method described in the second aspect, and the third node may be used to perform the steps of the method described in the third aspect.

[0040] In a fourteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0041] In a fifteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0042] In this embodiment, a first node receives identification information sent by a second or third node, the identification information including at least one identifier; the first node collects data based on the identification information; the first node sends a data report to the second node, the data report including the at least one identifier and data corresponding to each of the at least one identifier. In this way, the type of data can be identified through the identification information, enabling the data collected by the first node to be used by multiple different nodes, reducing the probability of duplicate data collection, and thus improving data collection efficiency. Attached Figure Description

[0043] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0044] Figure 2 is a schematic diagram of the UE-RAN data plane protocol stack in related technologies;

[0045] Figure 3 is a flowchart of one of the data collection methods provided in the embodiments of this application;

[0046] Figure 4 is a second flowchart of a data collection method provided in an embodiment of this application;

[0047] Figure 5 is a flowchart of a data collection method provided in an embodiment of this application;

[0048] Figure 6 is a flowchart of a data collection method provided in an embodiment of this application;

[0049] Figure 7 is a flowchart of a data collection method provided in an embodiment of this application;

[0050] Figure 8 is a flowchart of a data collection method provided in an embodiment of this application;

[0051] Figure 9 is a schematic diagram of one of the data collection devices provided in an embodiment of this application;

[0052] Figure 10 is a second schematic diagram of the structure of a data collection device provided in an embodiment of this application;

[0053] Figure 11 is a third schematic diagram of a data collection device provided in an embodiment of this application;

[0054] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0055] Figure 13 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0056] Figure 14 is one of the structural schematic diagrams of a network-side device provided in an embodiment of this application;

[0057] Figure 15 is a second schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0058] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0059] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0060] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0061] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0062] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 101 and a network-side device 102. The terminal 101 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 101 is not limited in this application embodiment. Network-side equipment 102 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmission and Reception Point (TRP), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical term. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0063] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0064] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0065] For ease of understanding, the following explains some aspects of the embodiments of this application:

[0066] 1. Data Services

[0067] The convergence of communication and sensing, along with 6G applications such as Artificial Intelligence (AI) and communication, enables 6G networks to possess capabilities such as sensing services, AI services, and computing services. These services can be further categorized into external services and service networks based on their target audience. Taking sensing as an example, sensing services provided by 6G to external network functions such as application functions are called external sensing services; sensing services provided by 6G to core network functions, radio access network nodes, or UEs are called service networks.

[0068] The aforementioned services will generate a large amount of internal network data. This internal network data is typically transmitted to internal network functions, such as core network functions, radio access network nodes, or UEs for use. Therefore, this type is called service network data service, also known as internal data service. Regarding network exposure, data generated by 6G networks may also be sent to external network functions such as application functions; this is called external data service. Data services involve processes such as data collection, privacy and security management, storage, and sharing.

[0069] 2. Data plane

[0070] Because sensing / AI data is characterized by large volume, flexible endpoints, and flexible priorities, and because multi-UE data and UE-base station data can have their volume reduced or quality improved through preprocessing at the base station, a data plane can be introduced in 6G networks to collect, transmit, and process the aforementioned internal network data. The data plane is a protocol stack used for data collection and transmission within the mobile network. This data plane protocol stack supports the session / radio bearers required for any data service, potentially including data service protocol stacks between UE and RAN, between UE and Core Network (CN), between RAN and CN, within CN, and within RAN. If we follow the existing definition of peers, a protocol stack needs to be defined between each of these pairs of peers. For example, in positioning, when the UE or base station acts as a positioning measurement node, the positioning protocol stack between the UE and LMF is used, as well as the positioning protocol stack between the base station and LMF. Different sending and receiving nodes have different underlying transport protocols depending on whether they involve air interface transmission. For example, the data service protocol stack between the UE and the network (radio access network or core network) involves air interface transmission, so its underlying transport protocols in 5G are Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), Physical Layer (PHY) or Service Data Adaptation Protocol (SDAP), PDCP, RLC, MAC, and PHY. On the other hand, the data service protocol stack between the RAN and CN does not involve air interface transmission, so its underlying transport protocols in 5G are Stream Control Transmission Protocol (SCTP) / Internet Protocol (IP) or General Packet Radio Service (GPRS) Tunnel Protocol-User Plane (GTP-U), User Datagram Protocol (UDP), and IP.

[0071] Figure 2 shows an example of a data plane protocol stack between a UE and a RAN. The data plane consists of core network data plane functions, radio access network data plane functions, and UE data plane functions, providing end-to-end connectivity. The data plane is responsible for data control, including data collection coordination, data collection configuration, and data transmission configuration. The data plane is also responsible for functions such as data acquisition, data transmission, data preprocessing, data privacy and security, data analysis, data storage, and data services.

[0072] 3. Definitions

[0073] Explanation 1: Perception Function Node

[0074] The sensing node includes at least one of the following functions:

[0075] (1) Receive a sensing service request and determine the required sensing measurement quantity based on the sensing service request.

[0076] (2) Receive the sensing measurement results (also known as sensing measurement data, i.e. the value of the sensing measurement quantity) and generate the sensing results (third-level measurement quantity).

[0077] (3) Send the perception results and respond to the perception service request.

[0078] (4) Control of perceived service quality (QoS), that is, to control the perception-related nodes in order to meet the perceived service QoS requirements.

[0079] (5) Identify sensing signal transmitting or receiving nodes or sensing auxiliary nodes. Sensing signal transmitting or receiving nodes in a mobile communication system include network equipment (such as base stations) and user equipment (UE) (such as mobile phones). Among them, sensing auxiliary nodes refer to information used to provide sensing assistance, such as sensing information from other sensors, geographical location information, etc., to improve the performance of wireless sensing.

[0080] (6) Determine the sensing link or sensing method, wherein the sensing link may include Uu link (base station transmit / UE receive or base station receive / UE transmit), side link (UE transmit and receive), echo link (base station transmits and receives, UE transmits and receives), and base station transmit and receive link (base station transmits and receives); the sensing method may include base station transmits and UE receives, UE transmits and base station receives, base station transmits and receives, UE transmits and receives, base station transmits and receives, and UE transmits and receives.

[0081] (7) Determine the sensing signal. Potential sensing signals include reference signals and data signals, where the reference signal can be a communication reference signal or a sensing-specific reference signal.

[0082] (8) Determine the time-frequency resources used for sensing. Potential sensing resources include unused time-frequency resources in communication (such as guard bands), shared time-frequency resources already used in communication (such as reference signals or data signals), and time-frequency resources dedicated to sensing. Further, the configuration of the sensing signal needs to be determined. Potential configurations include time-domain, frequency-domain, and spatial-domain resource information of the sensing signal. If it is determined that the node for sensing time-frequency resources is not the transmitting node for the sensing signal, then the sensing signal configuration is sent to the transmitting node for the sensing signal.

[0083] (9) Determine the configuration of the sensing measurement quantity. Potential configurations include the indication of the sensing signals to be measured, the number or time of the sensing signals to be measured, and the indication of reporting the measurement results (i.e., sensing measurement data). If the node for configuring the sensing measurement quantity is not the receiving and measuring node of the sensing signals, then send the sensing measurement quantity configuration to the sensing signal receiving node.

[0084] (10) Determine and configure the transmission channels for reporting sensing measurement results, including establishing, modifying or releasing transmission channels.

[0085] (11) Determining the AMF: After the network side determines the sensing function node based on the geographical range of the requested sensing service and the geographical range of the sensing service provided by the sensing function node, the sensing function node needs to determine the AMF in at least one of the following situations: 1) When the UE is a sensing signal transmitting node, sensing signal receiving node, or sensing auxiliary node, and the sensing target is a certain UE, the sensing function node selects the AMF based on the geographical area to be sensed, and according to the Tracking Area Identity (TAI) of the AMF requested from the NRF, and / or AMF ID / location, etc.; 2) When the sensing data needs to be transmitted through the AMF (e.g., defined as a Non-Access Stratum (NAS) message or the NAS layer as the transmission bearer protocol layer for sensing data), the sensing function node selects the AMF based on the geographical location information of the sensing node to be transmitted (e.g., Tracking Area (TA) etc.), and according to the TAI of the AMF requested from the NRF, and / or AMF ID / location, etc.; 3) When the sensing target is a 3GPP UE, the sensing function node selects the AMF based on the UE identifier (e.g., AMF UE NGAP). AMF is determined by factors such as ID.

[0086] Explanation 2: Sensing and Measurement Related Configuration Information

[0087] The sensing and measurement related configuration information includes at least one of the following: sensing and measurement object configuration information / sensing signal configuration information, sensing and measurement quantity configuration, sensing and measurement report configuration, and sensing data transmission configuration.

[0088] Wireless sensing involves measuring received signals and then processing the measurement results to obtain the desired sensing outcome. Therefore, the configuration of the sensing signals can also be referred to as the configuration of the sensing measurement object, including at least one of the following:

[0089] Waveforms, such as OFDM, Single-carrier Frequency-Division Multiple Access (SC-FDMA), OTFS, Frequency Modulated Continuous Wave (FMCW), pulse signals, etc.

[0090] Subcarrier spacing: For example, the subcarrier spacing of an OFDM system is 30 kHz;

[0091] Guard interval: The time interval between the end of signal transmission and the latest echo signal of that signal being received; this parameter is proportional to the maximum sensing distance; for example, it can be expressed as 2d. max / c is calculated to obtain d max This refers to the maximum sensing distance (related to sensing requirements), for example, for spontaneously generated and received sensing signals, d max It represents the maximum distance from the sensing signal transceiver point to the signal transmitter point; in some cases, the OFDM signal cyclic prefix CP can serve as the minimum guard interval.

[0092] Bandwidth: This parameter is inversely proportional to the distance resolution and can be obtained by c / (2Δd), where Δd is the distance resolution (related to perception requirements); and c is the speed of light.

[0093] Burst duration: This parameter is inversely proportional to the rate resolution (related to sensing requirements). It represents the time span of the sensed signal and is primarily used to calculate the Doppler frequency offset. This parameter can be obtained by c / (2f c Δv) is calculated; where Δv is the velocity resolution; f c It is the carrier frequency of the sensed signal;

[0094] Time domain interval: This parameter can be obtained by c / (2f) c v range ) is calculated; where, v range It is the maximum speed minus the minimum speed (related to sensing requirements); this parameter is the time interval between two adjacent sensing signals;

[0095] The transmission power of the sensing signal is measured, for example, by taking a value every 2dBm from -20dBm to 23dBm;

[0096] Information about the transmitting ports of the sensing signals, including the quantity and port number;

[0097] Signal format, such as Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), or other predefined signals, as well as related sequence format information;

[0098] Signal direction; for example, sensing the direction of signals (such as base station transmitting and UE receiving, base station receiving and UE transmitting, base station transmitting and receiving independently, base station transmitting and receiving between base stations, UE transmitting and receiving independently, and UE transmitting and receiving between UEs).

[0099] Beam information of the sensed signal;

[0100] Time resources, such as the time slot index or symbol index of the time slot where the sensing signal is located; among them, time resources are divided into two types: one is one-time time resources, such as one symbol sending an omnidirectional first signal; the other is non-one-time time resources, such as multiple sets of periodic time resources or discontinuous time resources (which may include start and end times), each set of periodic time resources sends a sensing signal in the same direction, and the beam direction on different sets of periodic time resources is different.

[0101] Frequency resources include the center frequency, bandwidth, resource block (RB), or subcarrier of the sensing signal. When node A transmits information from node B, the center frequency is the center frequency of node B. If node B supports multiple cells, then the list of center frequencies includes the center frequencies corresponding to multiple cells. For methods similar to Sidelink communication in NR, the sensing measurement object is a pool of transmission resources used for Sidelink communication in NR on a single carrier frequency.

[0102] Quasi-co-location (QCL) relationships, for example, a sensing signal includes multiple resources, each resource is associated with a Synchronization Signal Block (SSB) QCL, and the QCL includes Type A, B, C or D;

[0103] The sensing measurement parameters are configured to instruct the sensing measurement node to measure at least one of the following sensing measurement parameters:

[0104] The first level of measurement (the received signal or raw channel information) includes: the complex result of the received signal / channel response, amplitude / phase, I-channel / Q-channel and its operation results (operations include addition, subtraction, multiplication, division, matrix addition, subtraction, multiplication, matrix transpose, trigonometric operations, square root operations, and power operations, as well as threshold detection results and maximum / minimum value extraction results of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), 2D-FFT, 3D-FFT, matched filtering, autocorrelation operation, wavelet transform and digital filtering, as well as threshold detection results and maximum / minimum value extraction results of the above operation results).

[0105] Second-level measurements (basic measurements) include: time delay, Doppler, angle, signal strength, multi-dimensional spectral information (such as time-delayed Doppler two-dimensional spectrum, etc.), point cloud, etc.

[0106] The third level of measurement (also known as perception results) includes: target presence, distance, speed, angle / orientation, RCS, acceleration, position, trajectory, movement, facial expression, breathing rate, heart rate, imaging results, weather, air quality, material and composition, etc.

[0107] The perception measurement report configuration includes at least one of the following:

[0108] (1) The access type indication used for report transmission can be either 3rd Generation Partnership Project (3GPP) access or non-3GPP access. Further, 3GPP access can be indicated as 4th Generation (4G) (LTE), 5th Generation (5G) (NR), 6G, etc., while non-3GPP can be indicated as WLAN, Bluetooth, and wired networks, etc. If multiple types are used, a list can be used to indicate the priority order. For example, if the access type indication for report transmission is 5G or 4G, it means that 5G will be used preferentially for transmitting the report.

[0109] (2) Reporting Standards: The standards that trigger the sensing and measurement nodes to send measurement reports can be periodic, event-triggered, or indicated. Events include, but are not limited to, the following:

[0110] The quality of the sensed signal detected by the receiver must meet at least one of the following threshold requirements: signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indication (RSSI), and signal-to-clutter ratio threshold. If the threshold is met, then the sensed measurement quantity and report in the sensed measurement item configuration will be measured.

[0111] The sensing measurement results obtained by the receiving end do not meet the sensing requirements, that is, the sensing performance index corresponding to the calculated sensing measurement results meets the requirement of not being lower than the preset threshold, such as the sensing SNR (a potential definition is the ratio between the effective signal power of the signal propagation path corresponding to the sensing target and the noise power, or it can be defined as the ratio between the effective signal power of the signal propagation path corresponding to the sensing target and the sum of the noise power and the signal power of the signal propagation path corresponding to the non-sensing target).

[0112] If the receiving end correctly demodulates the data (e.g., the cyclic redundancy check (CRC) passes), and sensing is performed based on the communication data, the sensing parameters are estimated by first demodulating the data. If the communication demodulation is incorrect, the sensing measurement results will be affected and become unreliable.

[0113] If the mandatory sensing measurement items meet the requirements, such as the time delay, Doppler effect, and GPS location information at the time of measurement for the sensing signal, the RSRP and Reference Signal Received Quality (RSRQ) are optional. Therefore, a report is only submitted when all the mandatory sensing measurement items are available.

[0114] (3) Report format: The report includes the maximum number of cells under the RAT supported by node B, the maximum number of measurements per cell, etc.

[0115] The data collection method, apparatus, and related equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0116] Referring to Figure 3, which is a flowchart of a data collection method provided in an embodiment of this application, the data collection method includes the following steps:

[0117] Step 11: The first node receives identification information sent by the second or third node, the identification information including at least one identifier;

[0118] Step 12: The first node collects data based on the identification information;

[0119] Step 13: The first node sends a data report to the second node. The data report includes the at least one identifier and the data corresponding to each of the at least one identifier.

[0120] The first node can be a data providing node, such as a UE or a core network function node; the second node can be a data forwarding node, such as a radio access network node (e.g., a base station); and the third node can be a control node, such as a core network function node.

[0121] It is understandable that when both the first node and the third node are core network functional nodes, the first node and the third node are different core network functional nodes.

[0122] In one embodiment, the at least one identifier includes: at least one first identifier.

[0123] In this context, each of the at least one first identifier has a different identifier value, and the forwarding processing of the second node is performed based on the different values ​​of the first identifier.

[0124] One possible implementation is that the first identifier is used to identify the data packet. For example, based on the received data collection request and / or the data collection needs within the second node, the first node is configured to identify data packets consisting of the same data type requested by different nodes using a value of a first identifier (i.e., the first identifier value), such as the first identifier value X; and to identify data requested by different nodes other than the same data type using another value of the first identifier, such as the first identifier value Y.

[0125] It is understandable that in the above optional implementation methods, the first identifier value X indicates that the forwarding destination node of the corresponding data is greater than 1, and the first identifier value Y indicates that the forwarding destination node of the corresponding data is equal to 1.

[0126] It should be noted that the data collected by the first node can be used to serve the fourth node, and the second node can forward the data collected by the first node to the fourth node. Taking the fourth node as including an AI model training node and a perception function node as an example, data of the same data type requested by the AI ​​model training node and the perception function node are identified by a first identifier value X. Data in the data requested by the AI ​​model training node other than the data corresponding to the first identifier value X is identified by a first identifier value Y1. Data in the data requested by the perception function node other than the data corresponding to the first identifier value X is identified by a first identifier value Y2. In addition, data packets carrying the first identifier can be mapped to one or more radio bearers (RBs) or logical channels (LCs) for transmission. The fourth node is a data request node.

[0127] It should be noted that the aforementioned first identifier values ​​X and Y, or first identifier values ​​X, Y1 and Y2, are merely examples; another optional implementation is to use the first identifier to represent data packets with more than one receiving node (i.e., forwarding destination node), and to use the absence of a first identifier to represent data packets with only one receiving node.

[0128] It should be noted that the identification information may include configuration information of a first identifier, and the configuration information of the first identifier may include at least one first identifier. When multiple first nodes use the same configuration information of the first identifier during data collection, a second or third node can configure the configuration information of the first identifier to multiple first nodes via broadcast or multicast messages. This reduces configuration overhead.

[0129] Wherein, the first node collects data based on the identification information, which may mean that the first node triggers data collection based on the received identification information; or, the first node may collect data according to the data type corresponding to the identification information. Taking the at least one identification including at least one first identification as an example, the correspondence between the first identification and the data type may be configured by the second node or the third node, or may be pre-agreed upon, and this embodiment does not limit this.

[0130] Furthermore, the data report includes at least one identifier and data corresponding to each of the at least one identifier, enabling the second node to perform data processing or data forwarding based on the at least one identifier. Each of the at least one identifier can be associated with at least one node information, allowing the second node to perform data processing or data forwarding based on the node information associated with the at least one identifier. The correspondence between the at least one identifier and the node information can be configured by the second node or the third node, or pre-agreed upon; this embodiment does not impose any limitations on this.

[0131] Taking the at least one identifier including at least one first identifier as an example, the data report includes a first identifier value X and the data corresponding to the first identifier value X, as well as a first identifier value Y and the data corresponding to the first identifier value Y; both the first identifier value X and the first identifier value Y are configured with forwarding target nodes, and the second node can forward the data corresponding to the first identifier value X according to the forwarding target node associated with the first identifier value X, and forward the data corresponding to the first identifier value Y according to the forwarding target node associated with the first identifier value Y.

[0132] In one embodiment, the second node receives a data collection request sent by at least one fourth node; the second node sends identification information to the first node; and the first node receives the identification information sent by the second node.

[0133] In this embodiment of the application, the fourth node can be a data request node, such as an AI model training node or a perception function node.

[0134] In one implementation, a third node receives a data collection request from at least one fourth node; the third node sends identification information to a first node; and the first node receives the identification information sent by the third node.

[0135] In one implementation, the data collection request includes at least one of the following:

[0136] Data types, also known as measurement types, include, for example, Reference signal received power (RSRP), Reference signal received quality (RSRQ), Signal-to-noise and interference ratio (SINR), Channel estimation (H), Delay, Doppler, etc.

[0137] Data report configuration, including the number of training samples or datasets included in each data report, and the data composition of each training sample or dataset;

[0138] The total number of training samples or datasets;

[0139] Number of data-providing nodes.

[0140] In one implementation, the second node can be a radio access network (RAN) node. If the second node is an integrated node, it can be a gNB, a 6G nodeB, or another node with RAN node functionality evolved subsequently. If the second node is a separate node, it can be a Centralized Unit (CU), a CU-Control Plane (CP), or a CU-Data Plane (DP) (such as a node with xNB first sublayer functionality). When the second node receives more than one data collection request, and different data collection requests are for the same type of data, or when the data collection needs within the second node are for the same type of data as the aforementioned received data collection requests, the second node sends data collection configuration information to the first node (i.e., the data provider node), wherein the data collection configuration information includes at least a first identifier. The first identifier is used to identify the data packet of the data report sent by the first node, and the second node can forward the corresponding data packet according to the first identifier.

[0141] It should be noted that different data collection requests are used to request the same type of data in the following scenarios:

[0142] For AI-related use cases, the same use case typically has both a network-sided model and a UE-sided model, such as Channel State Information (CSI) prediction and location. Therefore, the network-sided model or the UE-sided model for the same use case may be trained on different AI model training nodes (such as base stations, core network positioning management functions, OTT servers, etc.). Consequently, data collection requests sent by different AI model training nodes may be for the same type of data.

[0143] Different AI use cases may share similar parameters in their inputs or outputs due to the relevance of the problems they solve. For example, if the AI ​​models for AI CSI prediction and AI CSI compression have the same input and output parameters, then the data collection requests sent by the AI ​​model training nodes will be for the same type of data.

[0144] Since different data consuming nodes all require channel information for channel transmission, the data collected by these different data consuming nodes may contain the same data, even if their data providing nodes are the same. For example, a sensing function node and an AI model training node for CSI prediction may both collect the frequency domain channel estimation result H of the first node (such as the UE). Similarly, a positioning management function node and a base station may both collect the UE's SS-RSRP / RSRQ.

[0145] In this embodiment, a first node receives identification information sent by a second or third node, the identification information including at least one identifier; the first node collects data based on the identification information; the first node sends a data report to the second node, the data report including the at least one identifier and data corresponding to each of the at least one identifier. In this way, the type of data can be identified through the identification information, enabling the data collected by the first node to be used by multiple different nodes, reducing the probability of duplicate data collection, and thus improving data collection efficiency.

[0146] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0147] or,

[0148] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0149] In one embodiment, different values ​​of the first identifier can be used to indicate whether the forwarding destination node of the corresponding data is greater than 1. For example, the first identifier value X indicates that the forwarding destination node of the corresponding data is greater than 1, and values ​​other than the first identifier value X indicate that the forwarding destination node of the corresponding data is equal to 1; or, if the data carries the first identifier, it indicates that the forwarding destination node of the data is greater than 1, and if the data does not carry the first identifier, it indicates that the forwarding destination node of the data is equal to 1; etc. This embodiment does not limit this.

[0150] In one implementation, the second identifier can be used to identify the data processing method of the data packet in the data report sent by the first node (such as the data providing node). The second node needs to perform corresponding processing according to the second identifier before forwarding the data packet. For example, when the forwarding destination node of the data packet is greater than 1, the second identifier can also be a value of the first identifier. In this case, this value of the first identifier indicates that the data packet is forwarded to multiple receiving nodes and needs to be processed before being forwarded to multiple nodes.

[0151] In this embodiment, the at least one identifier includes: at least one first identifier, which is used to indicate whether the forwarding node of the corresponding data is greater than 1. The first identifier can support the reuse of the same data providing node, reduce the air interface resource overhead of data collection, reduce the data collection amount of the data providing node, and avoid duplicate data collection.

[0152] In this embodiment, the at least one identifier includes at least one second identifier, which is used to indicate the data processing method of the data corresponding to the second identifier. The second identifier enables the data service that has the same type or overlap after data processing to reuse the same data providing node, which can further reduce the air interface resource overhead of data collection.

[0153] Optionally, the at least one first identifier may include a partial first identifier, and the first identifier in the partial first identifier may be associated with a data processing method.

[0154] In this embodiment, the at least one first identifier includes a partial first identifier, and the first identifier in the partial first identifier is associated with a data processing method. Through the partial first identifier, it is possible to support the reuse of the same data providing node for data services that have the same or overlapping data types after data processing, which can further reduce the air interface resource overhead of data collection.

[0155] Optionally, the at least one first identifier includes: a first identifier corresponding to the first data;

[0156] Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

[0157] In this embodiment, the at least one first identifier includes: a first identifier corresponding to the first data, wherein the first data is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node. Thus, the data collected by the first node can be simultaneously provided to multiple different nodes, reducing the probability of duplicate data collection and thereby improving data collection efficiency.

[0158] Optionally, each of the at least one identifier is associated with at least one node information, which is used to characterize the fourth node or the second node.

[0159] Wherein, each of the at least one identifier is associated with at least one node information, meaning that each of the at least one identifier is associated with at least one forwarding destination node. For example, the forwarding destination nodes corresponding to the data packet with the first identifier value X are an AI model training node and a perception function node. The node information of the forwarding destination node can be a forwarding destination node identifier or an IP address, etc.; as another example, the forwarding destination node corresponding to the data packet with the first identifier value Y1 is an AI model training node; and the forwarding destination node corresponding to the data packet with the first identifier value Y2 is a perception function node.

[0160] In this embodiment, each of the at least one identifier is associated with at least one node information, so that the second node can forward data based on the at least one identifier, and the second node does not need to parse the content of the data packet when forwarding data, and can directly forward data based on the at least one identifier.

[0161] Optionally, the data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier;

[0162] The target object includes any one of the following:

[0163] Radio bearer (RB); logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

[0164] The target identifier may include a first identifier or a second identifier.

[0165] In one implementation, the first identifier can be configured to identify the data carried by a specific RB or LC. For example, based on a received data collection request and / or its internal data collection needs, the second node configures the first node to carry the same first identifier value X in data packets composed of data of the same data type requested by different nodes, and transmit them in the configured RB or LC. The second node can also configure the first node to carry the first identifier value Y in data packets composed of data of a different data type, and transmit them in the configured RB or LC. If data reports with first identifier values ​​X and Y are transmitted simultaneously, then data packets with first identifier values ​​X and Y can correspond to different RBs or LCs; if data reports with first identifier values ​​X and Y are not transmitted simultaneously, then data packets with first identifier values ​​X and Y can correspond to the same RB or LC. For example, if a first node sends a data report through the RB or LC within a certain time interval, the first node can carry the aforementioned first identifier with a value of X or Y in the first data packet of the data report (e.g., a control protocol data unit (PDU) or a data PDU). Then, for subsequent data packets with the same first identifier carried by the RB or LC, it is not necessary to carry the first identifier, thus saving the overhead of the first identifier. When the first node completes the corresponding data report transmission, one approach is for the first node to send a data packet containing the first identifier and an end identifier; another approach is for the first node to send a data packet containing a first identifier with a different value (e.g., the first identifier of the first data packet of the data report sent by the first node on the RB or LC is X, and after the data packets with the first identifier of X are sent, the first node sends a data packet with the first identifier of Y), thus identifying subsequent data packets as data packets with a first identifier of other values ​​(e.g., Y); or yet another approach is for the first node to stop sending data on the RB or LC before receiving the RB or LC configuration (e.g., modification), to avoid the second node mistakenly identifying the data as a data packet forwarded with the same first identifier.

[0166] In one implementation, the second identifier can be configured as an identifier for data carried by a certain RB or LC; or the second identifier can be indirectly indicated by the RB or LC through a mapping relationship between the second identifier and the RB or LC. For example, based on a received data collection request and / or the data collection needs within the second node, the second node configures the first node to send data packets that need to undergo first processing and then forward them by carrying the aforementioned second identifier in the configured RB or LC. It is understood that the first processing is a data processing method. The second node can also configure the first node to send data packets that are directly forwarded by carrying the aforementioned second identifier in the configured RB or LC. If data from multiple data reports that undergo different first processing and then forward, are sent simultaneously (processed forwarding, direct forwarding, or forwarding after different first processing), then the data packets corresponding to different types of data reports correspond to different RBs or LCs. If data from multiple data reports that undergo different first processing and then forward, are not sent simultaneously (processed forwarding, direct forwarding, or forwarding after different first processing), then the data packets corresponding to different types of data reports can correspond to the same RB or LC. For example, if a first node sends a data report through the RB or LC within a certain time interval, the first node can carry the aforementioned second identifier in the first data packet of the data report; then, for subsequent data packets with the same second identifier carried by the RB or LC, it is not necessary to carry the second identifier, thus saving the overhead of the second identifier. When the first node completes the corresponding data report transmission, one method is for the first node to send a data packet containing the second identifier and an end identifier; another method is for the first node to send a data packet containing a second identifier with a different value, thus identifying subsequent data packets as data packets corresponding to the second identifier with other values; or yet another method is for the first node to stop sending data on the RB or LC before receiving the RB or LC configuration (such as a modification), to avoid the second node mistakenly identifying the data as a forwarded data packet with the aforementioned second identifier.

[0167] It should be noted that different first processes can be indicated by different values ​​of the second identifier. For example, the first process of converting the channel estimation result H into a point cloud can be indicated by the second identifier value A1, and the first process of cleaning the AI ​​training data samples can be indicated by the second identifier value A2. The second identifier value refers to the value of the second identifier.

[0168] In one implementation, data packets carrying a first identifier and / or a second identifier can be mapped to one or more QoS flows or PDU sessions. An alternative implementation is that the first identifier and / or the second identifier identifies the data carried by the QoS flow or PDU session. For example, a third node configures a second node or a first node to send data packets consisting of data of the same data type carrying the aforementioned first identifier value X in the configured QoS flow or PDU session. Alternatively, the third node can configure the first node to send data packets consisting of data of different data types carrying the aforementioned first identifier value Y in the configured QoS flow or PDU session.

[0169] If two data reports with first identifier values ​​of X and Y are sent simultaneously, then the data packets with first identifier values ​​X and Y correspond to different QoS flows or PDU sessions, respectively. If the two data reports with first identifier values ​​X and Y are not sent simultaneously, then the data packets with first identifier values ​​X and Y can correspond to the same QoS flow or PDU session. Data packets carrying a second identifier can also be determined based on whether simultaneous transmission is required, using the same QoS flow or PDU session or different QoS flows or PDU sessions. When a first node sends a data report through this QoS flow and / or PDU session within a certain time interval, the first node can carry the aforementioned first identifier with a value of X or Y in the first data packet of that data report. Then, for subsequent data packets with the same first identifier carried by this QoS flow or PDU session, it is not necessary to carry the first identifier, thus saving the overhead of the first identifier. When the first node completes the corresponding data report transmission, one method is for the first node to send a data packet containing a first identifier and an end identifier; another method is for the first node to send a data packet containing a first identifier with different values, which then identifies subsequent data packets as data packets corresponding to the first identifier with other values; or another method is for the first node to stop sending data on the QoS flow or PDU session before receiving the PDU session configuration (such as modification), so as to avoid the second node mistakenly identifying the data as a data packet forwarded with the same first identifier as mentioned above.

[0170] Optionally, the first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and the data packets in the data corresponding to the target identifier transmitted on the target object other than the first data packet do not carry the target identifier.

[0171] In this embodiment, the first data packet transmitted on the target object in the data corresponding to the target identifier carries the target identifier, and the data packets transmitted on the target object in the data corresponding to the target identifier, except for the first data packet, do not carry the target identifier. This reduces transmission overhead.

[0172] Optionally, the first data packet is a Control Protocol Data Unit (PDU) or a Data PDU. One example: The Control Protocol Data Unit can be a Packet Data Convergence Protocol (PDCP) control PDU, which is the first data packet. The control PDU on the RB carries the first identifier and / or, a second identifier; subsequent Data PDUs that do not carry the first or second identifier reuse the first or second identifier of the aforementioned first data packet. Another example: The Control Protocol Data Unit can be a MAC PDU containing a Medium Access Control (MAC) Control Element (CE), which is the first data packet. The MAC CE on the LC carries the first identifier and / or, a second identifier. One example: The Data Protocol Data Unit can be a PDCP Data PDU, where a data PDU is the first data packet. The data PDU on the RB carries the first identifier and / or, a second identifier in its header; subsequent Data PDUs that do not carry the first or second identifier reuse the first or second identifier of the aforementioned first data packet. Another example: The data protocol data unit can be a MAC PDU containing a MAC subheader, wherein a certain MAC PDU is the first data packet, and carries the first identifier and / or, the second identifier through the MAC subheader on the LC.

[0173] Optionally, the identification information is carried in the data collection configuration information, and the identification information includes a radio bearer identifier.

[0174] One possible implementation is to indirectly indicate the first identifier through the radio bearer by means of the mapping relationship between the first identifier and the radio bearer. For example, data plane RB1 is used to carry forward data packets with a destination node greater than 1, and data plane RB2 is used to carry forward data packets with a destination node of 1. In this case, the identifier of the radio bearer can be regarded as the first identifier.

[0175] One possible implementation is to indirectly indicate the second identifier through the radio bearer by means of the mapping relationship between the second identifier and the radio bearer. For example, data plane RB1 is used to carry data packets that are forwarded directly, and data plane RB2 is used to carry data packets that need to be forwarded after the first processing. In this case, the identifier of the radio bearer can be regarded as the second identifier.

[0176] Optionally, the identification information is carried in the data collection configuration information;

[0177] The data collection configuration information also includes at least one of the following:

[0178] The data report contains wireless bearer configuration information;

[0179] The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

[0180] One alternative implementation is that the radio bearer configuration information is used to indicate the type or ID of the radio bearer (RB) used for data reporting, such as data plane RB 1, or data radio bearer (DRB) 1, etc.

[0181] In this embodiment, through the wireless bearer configuration information of the data report, the first node can learn the wireless bearer transmission method of the data corresponding to the at least one identifier, and then use the wireless bearer transmission method to transmit the data report.

[0182] In this embodiment, the first node can learn how at least one of the first identifier and the second identifier in the identification information is carried in the data report through the first indication information, and then use the carrying method when transmitting the data report.

[0183] It should be noted that different data services may require the same data, or the data required by different data services may overlap. Traditional data transmission and forwarding technologies based purely on IP may lead to duplicate data collection or transmission. The measurement configuration of relevant 5G protocols mainly considers the configuration and reporting of data collection required by the base station, as well as transparent forwarding of Quality of Experience (QoE) or Minimization of Drive Tests (MDT) reports required by the trace collection entity (TCE), which is difficult to support complex data collection, forwarding, or processing.

[0184] To improve the efficiency of data collection, forwarding, or processing when different data collection requests contain the same or partially overlapping data, it is necessary to classify the data according to the data in different data collection requests and configure the data providing node to send data according to the data type configuration. Simultaneously, the data forwarding node or receiving node forwards or processes data according to the data type. This application embodiment reuses the data providing node, as well as the air interface resources and data reports used by the node during the data collection process, to avoid duplicate data collection or transmission and improve forwarding or processing efficiency.

[0185] This application provides a method for reusing the same data providing node and its data report, addressing situations where more than one data collection request contains the same data (or contains the same data after a first processing step). A first node receives configuration information for a first identifier and / or configuration information for a second identifier, and sends a data report based on the configuration information. The data report includes the first identifier or the second identifier and the corresponding data. The first identifier indicates that the data packet for the data report sent by the data providing node (such as the first node) has more than one forwarding node. The second identifier indicates that the data packet for the data report sent by the data providing node (such as the first node) needs to undergo a first processing step before being forwarded to at least one node. The base station forwards and / or processes the data packet based on the first identifier and / or the second identifier.

[0186] The following examples will provide further explanation:

[0187] Example 1:

[0188] In this example, the first node (i.e., the data provider node) is the UE, the second node is the base station, and the base station forwards data based on the first identifier.

[0189] In this example, when more than one data collection request seeks to collect the same data, the second node selects a suitable UE to satisfy the data requirements of the multiple requests. The second node sends data collection configuration to the UE to configure a first identifier. The UE uses an appropriate first identifier value to identify data packets based on the configuration information, and the second node forwards the data packets based on the first identifier. This reduces the air interface overhead of data collection and avoids duplicate data collection and reporting by the selected UE.

[0190] As shown in Figure 4, this example includes the following process:

[0191] Step (1): Optionally, one or more fourth nodes send a data collection request to the second node.

[0192] The data collection request includes at least one of the following:

[0193] Data types, also known as measurement types, include RSRP, RSRQ, SINR, channel estimation H, time delay, Doppler, etc.

[0194] Data report configuration, including the number of training samples or datasets included in each data report, and the data composition of each training sample or dataset;

[0195] The total number of training samples or datasets;

[0196] Number of data-providing nodes.

[0197] In one alternative implementation, when the fourth node is an AI model training node (such as NWDAF), if the fourth node sends a data collection request to collect the training dataset based on DMRS channel estimation, an example of a data collection request would be as follows:

[0198] The data type is frequency domain channel estimation H, where the channel estimation H for each resource element is a complex value consisting of a real part and an imaginary part;

[0199] The AI ​​model training node receives a data report consisting of one or more integer training samples, where each training data sample contains channel estimates H for 48 REs (i.e., 4 resource blocks (RBs)) within a certain time slot, for a total of 672 REs channel estimates H.

[0200] Total number of training samples, indicating the total number of training samples required for this data collection request, for example, 50,000;

[0201] The number of UEs can be a specified number, such as 500; or it can be a lower or upper limit for the number of UEs, such as not less than 300.

[0202] In one alternative implementation, when the fourth node is a sensing function node (see Explanation 1), if the fourth node sends a data collection request to identify and track data of the sensing target, an example of a data collection request is shown below:

[0203] The data types are frequency domain channel estimation H, location, and antenna panel orientation;

[0204] The data report received by the sensing function node is a set of sensing measurement data for one time slot or an integer number of time slots greater than 1. Each set of sensing measurement data contains the channel estimate H of M REs with N symbols in a certain time slot; for example, 3726 REs (i.e. 273 RBs) with 2 OFDM symbols in this time slot are used for sensing measurement.

[0205] The total number of sensing measurement data sets is a requirement. If the sensing measurement data sets are used for training AI-based sensing models, the sensing function nodes can also provide a requirement for the number of sensing measurement data sets. Alternatively, there is no specific requirement for the number of sensing measurement data sets. The sensing measurement data is determined by the configuration of the sensing signals being measured. That is, the sensing measurement data sets are generated by measuring according to the configuration of the sensing signals. For time-frequency domain signals without sensing signals, there is no need to perform sensing measurements or generate sensing measurement data sets.

[0206] The number of UEs can be a specified number, such as when the sensing function node has selected a suitable UE, or it can be a lower or upper limit for the number of UEs, such as not less than 2.

[0207] Step (2): The second node receives the data collection request.

[0208] The second node is a radio access network node. In the case of an integrated node, the second node can be a gNB or a 6G nodeB. In the case of a separate node, the second node can be a CU, CU-CP, or CU-DP (such as a node with xNB first sublayer functionality). When the second node receives more than one data collection request, and the different data collection requests contain the same data type (i.e., the data requested by different data collection requests contains the same type of data), or when the data collection requirement within the second node contains the same data type as the aforementioned received data collection requests (i.e., the data required by the data collection requirement and the data requested by the data collection request contain the same type of data), the second node sends data collection configuration information to the data provider node. This data collection configuration information includes at least a first identifier. The first identifier is used to identify the data packet of the data report sent by the data provider node, and the second node needs to forward the corresponding data packet according to the first identifier.

[0209] In one optional implementation, when the second node receives the data collection requests from the AI ​​model training node and the perception function node in step (1), the second node also selects the UE A selected by the perception function node as the node providing AI model training data. This allows for the reuse of air interface resources. The network, by sending a reference signal to the UE, satisfies both the AI ​​model training data required for channel estimation and the perception measurement data required for the perception function, reducing the air interface overhead of reporting the reference signal and corresponding policy data. Simultaneously, UE A only needs to measure the aforementioned reference signal and report the corresponding measurement data, reducing the measurement and reporting overhead of UE A. In summary, selecting the same UE A and configuring the corresponding data collection can reduce air interface overhead, avoid more UEs performing measurements and data reporting, and prevent UE A from repeatedly collecting and sending data reports.

[0210] Regarding the first identifier, different values ​​of the first identifier represent the forwarding processing of the second node. One possible implementation is that the first identifier identifies the data packet. For example, based on received data collection requests and / or internal data collection needs, the second node configures the UE to identify data packets composed of data of the same data type using the first identifier value X, and data packets composed of data of different data types using the first identifier value Y. For example, data of the same data type requested by the AI ​​model training node and the perception function node are identified using the first identifier value X; data in the data requested by the AI ​​model training node other than the data corresponding to the first identifier value X is identified using the first identifier value Y1; and data in the data requested by the perception function node other than the data corresponding to the first identifier value X is identified using the first identifier value Y2. The data packet carrying the first identifier with the value X or Y can be mapped to one or more radio bearers (RBs) or logical channels (LCs). Specifically, for example, the data collection configuration information sent by the second node to the UE may indicate the following information by configuring the first identifier:

[0211] The first identifier value corresponding to H required for the aforementioned AI model training nodes and perception function nodes on the same symbol is X;

[0212] The first identifier value corresponding to H required by the AI ​​model training node on other symbols is Y1;

[0213] The first identifier value corresponding to the location required by the sensing function node and the orientation of the antenna panel is Y2.

[0214] It should be noted that the configuration information of the first identifier can be configured based on the situation of each UE acting as a data providing node. If more than one UE uses the same first identifier information during the data collection process, then the second node can also configure the first identifier information to more than one UE via broadcast or multicast messages. For example, if the data required by the AI ​​model training node and the data required by the perception function node are both designed for UE A, UE B, and UE C, and the first identifier configuration information of UE A and UE B is the same, then the second node can send it via encrypted broadcast messages using the keys of UE A, UE B, and UE C, so that UE A, UE B, and UE C can receive the information.

[0215] Regarding the first identifier, another optional implementation is that the first identifier is an identifier for the data carried by the RB or LC. For example, the second node, based on the received data collection request and / or its internal data collection needs, configures the UE to send data packets composed of data of the same data type by carrying the aforementioned first identifier value X in the configured RB or LC. The second node can also configure the UE to send data packets composed of data of different data types by carrying the aforementioned first identifier value Y in the configured RB or LC. If data reports with first identifier values ​​X and Y are sent simultaneously, then the data packets with first identifier values ​​X and Y correspond to different RBs or LCs, respectively. If the two data reports with first identifier values ​​X and Y are not sent simultaneously, then the data packets with first identifier values ​​X and Y can correspond to the same RB or LC. Specifically, if the UE sends a data report through this RB or LC within a certain time interval, the UE can carry the aforementioned first identifier value X or Y in the first data packet of the data report. Then, for subsequent data packets with the same first identifier carried by this RB or LC, it is not necessary to carry the first identifier, thereby saving the overhead of the first identifier. When the UE completes the corresponding data report transmission, one method is for the UE to send a data packet containing a first identifier and an end identifier; another method is for the UE to send a data packet containing a first identifier with different values, which then identifies subsequent data packets as data packets corresponding to the first identifier with other values; or another method is for the UE to stop sending data on the RB or LC before receiving the RB or LC configuration (if modified), so as to avoid the data being mistakenly identified by the second node as a data packet forwarded with the same first identifier as mentioned above.

[0216] It should also be noted that the first identifier in the data collection configuration information can be configured through RRC, MAC, or the first sub-layer of the data plane.

[0217] Additionally, it should be noted that the second node instructs the UE on how to carry the first identifier in the data packet of the data report during data collection configuration. Therefore, the second node can forward data based on the first identifier.

[0218] Furthermore, it should be noted that the aforementioned first identifier values ​​X, Y1, and Y2 are merely examples; another optional implementation is to use the first identifier to represent data packets with more than one receiving node, and to use the absence of a first identifier to represent data packets with only one receiving node.

[0219] Optionally, the data collection configuration information may also include perception measurement-related configuration information (see Explanation 2), or the signal configuration corresponding to the training samples required by the aforementioned AI model training nodes.

[0220] Optionally, the data collection configuration information may also include radio bearer configuration information for data reporting. One optional implementation is that the radio bearer configuration information indicates the RB type or RB ID used for data reporting, such as data plane RB 1, or DRB 1, etc.; another optional implementation is that the first identifier can be indirectly indicated through the radio bearer by means of a mapping relationship between the first identifier and the radio bearer, for example, data plane RB1 is used to carry and forward data packets with a destination node greater than 1, and data plane RB2 is used to carry and forward data packets with a destination node of 1.

[0221] Optionally, if the aforementioned first identifier is configured via CU-CP, and the UE transmits data reports via user plane or data plane (DP), then CU-CP also needs to send the configuration information of the first identifier to CU-UP or CU-DP. The configuration information of the first identifier includes at least one of the following:

[0222] The first identifier value and the corresponding forwarding destination node information, for example, the forwarding destination nodes corresponding to the data packet with the first identifier value X are the AI ​​model training node and the perception function node. The forwarding destination node information can be the destination node identifier or IP address, etc.; for another example, the forwarding destination node corresponding to the data packet with the first identifier value Y1 is the AI ​​model training node; the forwarding destination nodes corresponding to the data packet with the first identifier value Y2 are the AI ​​model training node and the perception function node.

[0223] Step (3): The first node (UE) receives the data collection configuration information from the second node.

[0224] The UE collects data and sends a data report to the second node according to the data collection configuration. The data report includes a first identifier and the corresponding data.

[0225] One possible implementation is that, based on the data collection configuration information, the UE carries a first identifier with a value of X for the data packet corresponding to the H required by the AI ​​model training node and the perception function node on the same symbol; carries a first identifier with a value of Y1 for the data packet corresponding to the H required by the AI ​​model training node on other symbols; and carries a first identifier with a value of Y2 for the data packet corresponding to the required position and antenna panel orientation of the perception function node.

[0226] Step (4): The second node receives the data report and forwards it according to the first identifier.

[0227] Optionally, if the second node receives a data collection request from an external source, it forwards the data packet to the corresponding fourth node based on the first identifier value. For example, a data packet with a first identifier value of X is forwarded to the AI ​​model training node and the perception function node.

[0228] Example 2:

[0229] In this example, the first node (i.e., the data provider node) is the UE, and the second node is the base station. The base station processes and forwards data based on the second identifier.

[0230] Example 1 involves selecting a suitable UE as a data provider node to satisfy more than one data collection request and performing forwarding processing based on a first identifier. In this example, during the process of selecting a suitable UE as a data provider node to satisfy more than one data collection request, at least one fourth node requires data that needs to be processed by a second node before forwarding. One possible implementation is to introduce a second identifier, which indicates whether the data packet requires first processing; another possible implementation is to use the first identifier value to indicate that the data packet has more than one receiving node and requires first processing. This example can be further expanded based on Example 1 to include data collection requests that can be multiplexed, because this example is applicable not only to different data collection requests containing the same data, but also to cases where data in different data collection requests can be transformed through first processing.

[0231] As shown in Figure 5, this example includes the following process:

[0232] Step (1): Optionally, one or more fourth nodes send a data collection request to the second node.

[0233] The data collection request includes at least one of the following:

[0234] Data types, also known as measurement types, include RSRP, RSRQ, SINR, channel estimation H, time delay, Doppler, etc.

[0235] Data report configuration, including the number of training samples or datasets included in each data report, and the data composition of each training sample or dataset;

[0236] The total number of training samples or datasets;

[0237] Number of data-providing nodes.

[0238] In one alternative implementation, when the fourth node is an AI model training node (such as NWDAF), if the fourth node sends a data collection request to collect the training dataset based on DMRS channel estimation, an example of a data collection request would be as follows:

[0239] The data type is frequency domain channel estimation H, where the channel estimation H for each resource element is a complex value consisting of a real part and an imaginary part;

[0240] The AI ​​model training node receives a data report consisting of one or more integer training samples, where each training data sample contains channel estimates H for 48 REs (i.e., 4 resource blocks (RBs)) within a certain time slot, for a total of 672 REs channel estimates H.

[0241] Total number of training samples, indicating the total number of training samples required for this data collection request, for example, 50,000;

[0242] The number of UEs can be a specified number, such as 500; or it can be a lower or upper limit for the number of UEs, such as not less than 300.

[0243] In one alternative implementation, when the fourth node is a sensing function node 1 (see Explanation 1), if the fourth node sends a data collection request to identify and track data of the sensing target, an example of a data collection request is shown below:

[0244] The data types are channel estimation H, location, and antenna panel orientation;

[0245] The data report received by the sensing function node is a set of sensing measurement data for one time slot or an integer number of time slots greater than 1. Each set of sensing measurement data contains the channel estimate H of M REs with N symbols in a certain time slot; for example, 3726 REs (i.e. 273 RBs) with 2 OFDM symbols in this time slot are used for sensing measurement.

[0246] The total number of sensing measurement data sets is a requirement. If the sensing measurement data sets are used for training AI-based sensing models, the sensing function nodes can also provide a requirement for the number of sensing measurement data sets. Alternatively, there is no specific requirement for the number of sensing measurement data sets. The sensing measurement data is determined by the configuration of the sensing signals being measured. That is, the sensing measurement data sets are generated by measuring according to the configuration of the sensing signals. For time-frequency domain signals without sensing signals, there is no need to perform sensing measurements or generate sensing measurement data sets.

[0247] The number of UEs can be a specified number, such as when the sensing function node has selected a suitable UE, or it can be a lower or upper limit for the number of UEs, such as not less than 2.

[0248] An alternative implementation, where a fourth node needs data collection for sensing-assisted communication or another sensing node (such as sensing node 2) needs point cloud data of the same UE, would present an example of a data collection request as follows:

[0249] The data types are point cloud, location, and antenna panel orientation, where the point cloud is obtained by first processing based on frequency domain channel estimation H;

[0250] The data report received by the sensing function node is a set of sensing measurement data for one time slot or an integer number of time slots greater than 1. Each set of sensing measurement data contains the channel estimate H of M REs with N symbols in a certain time slot; for example, 3726 REs (i.e. 273 RBs) with 2 OFDM symbols in this time slot are used for sensing measurement.

[0251] The total number of sensing measurement data sets is a requirement. If the sensing measurement data sets are used for training AI-based sensing models, the sensing function nodes can also provide a requirement for the number of sensing measurement data sets. Alternatively, there is no specific requirement for the number of sensing measurement data sets. The sensing measurement data is determined by the configuration of the sensing signals being measured. That is, the sensing measurement data sets are generated by measuring according to the configuration of the sensing signals. For time-frequency domain signals without sensing signals, there is no need to perform sensing measurements or generate sensing measurement data sets.

[0252] The number of UEs can be a specified number, such as when the sensing function node has selected a suitable UE, or it can be a lower or upper limit for the number of UEs, such as not less than 2.

[0253] Step (2): The second node receives the data collection request.

[0254] The second node is a radio access network node. In the case of an integrated node, the second node can be a gNB or a 6G nodeB. In the case of a separate node, the second node can be a CU, CU-CP, or CU-DP (such as a node with xNB first-layer functionality). When the second node receives more than one data collection request, and these requests contain the same data type, or when the data collection needs within the second node contain the same data type as the previously received requests, the second node sends data collection configuration information to the data provider node. This configuration information includes at least a second identifier. The second identifier identifies the data packet sent by the data provider node as a data report. The second node must process the data packet according to the second identifier before forwarding it. When there are more than one receiving node for the data packet, the second identifier can also be a value of the first identifier. In this case, this value of the first identifier indicates that the data packet is forwarded to multiple receiving nodes and must be processed before being forwarded to multiple nodes.

[0255] It should also be noted that the second identifier in the data collection configuration information can be configured through RRC, MAC or the first sub-layer of the data plane.

[0256] Optionally, the data collection configuration information may also include radio bearer configuration information for the data report. One optional implementation is that the radio bearer configuration information indicates the RB type or RB ID used by the data report, such as data plane RB 1, or DRB 1. Another optional implementation is that the second identifier can be indirectly indicated via the RB or LC through a mapping relationship between the second identifier and the RB or LC. For example, based on a received data collection request and / or the data collection needs within the second node, the second node configures the UE to carry the aforementioned second identifier and send the data packets that need to undergo first processing before forwarding in the configured RB or LC. The second node can also configure the UE to carry the aforementioned second identifier and send the directly forwarded data packets in the configured RB or LC. If multiple data reports undergoing different first processing before forwarding, direct forwarding, or forwarding simultaneously, the data packets corresponding to different types of data reports correspond to different RBs or LCs. If multiple data reports undergoing different first processing before forwarding, direct forwarding, or forwarding simultaneously are not sent, the data packets corresponding to different types of data reports can correspond to the same RB or LC. Specifically, if the UE sends a data report through the RB or LC within a certain time interval, the UE can carry the aforementioned second identifier in the first data packet of the data report; then, for subsequent data packets with the same second identifier carried by the RB or LC, it is not necessary to carry the second identifier, thus saving the overhead of the second identifier. When the UE completes the corresponding data report transmission, one method is that the UE sends a data packet containing the second identifier and an end identifier; another method is that the UE sends a data packet containing a second identifier with different values, thus identifying subsequent data packets as data packets corresponding to the second identifier with other values; or yet another method is that the UE does not send data on the RB or LC before receiving the RB or LC configuration (such as modification), to avoid the data being mistakenly identified by the second node as a data packet forwarded with the same second identifier.

[0257] In one optional implementation, when the second node receives the data collection requests from the AI ​​model training node and the perception function node in step (1), the fourth node also selects the UE A selected by the perception function node as the node providing AI model training data. This allows for the reuse of air interface resources; the network, by sending a reference signal to the UE, satisfies both the AI ​​model training data required for channel estimation and the perception measurement data required for the perception function, reducing the air interface overhead of reporting the reference signal and corresponding policy data. Simultaneously, UE A only needs to measure the aforementioned reference signal and report the corresponding measurement data, reducing the measurement and reporting overhead of UE A. In summary, selecting the same UE A and configuring the corresponding data collection can reduce air interface overhead, avoid more UEs performing measurements and data reporting, and prevent UE A from repeatedly collecting and sending data reports.

[0258] Regarding the second identifier, it indicates that the data packet requires a first processing step. This first processing step involves converting the channel estimate H into a point cloud before forwarding it to the sensing function node 2. The second identifier allows the selected UE's channel estimate H data to be reused to meet the requirements of either the second node or the sensing function node 2 that needs a point cloud. The UE can also save the processing overhead of converting H into a point cloud. If more than one first processing step is performed on the data packet, it can be indicated by different values ​​of the second identifier. For example, one first processing step is converting the channel estimate H into a point cloud for the sensing function node 2, while another first processing step is combining the data required by the AI ​​model training node according to the sample requirements of the AI ​​training data.

[0259] Regarding the first identifier, different values ​​of the first identifier can represent the forwarding processing of the second node. One optional implementation is to identify the same data type using the first identifier value X, and different data types using the first identifier value Y, based on the received data collection request and / or the data collection needs within the second node. Specifically, for example, the data collection configuration information sent by the second node to the UE may be configured with the first identifier to indicate the following information:

[0260] The first identifier value corresponding to H required by the aforementioned AI model training node, perception function node 1, and perception function node 2 on the same symbol is X1;

[0261] The required positions and antenna panel orientations of sensing functional node 1 and sensing functional node 2 are corresponding to the first identifier value X2;

[0262] The first identifier value corresponding to H required by the AI ​​model training node on other symbols is Y1.

[0263] It should be noted that the configuration information of the first identifier can be configured based on the situation of each UE acting as a data providing node. If more than one UE uses the same first identifier information during the data collection process, then the second node can also configure the first identifier information to more than one UE via broadcast or multicast messages. For example, if the data required by the AI ​​model training node and the data required by the perception function node are both designed for UE A, UE B, and UE C, and the first identifier configuration information of UE A and UE B is the same, then the second node can send it via encrypted broadcast messages using the keys of UE A, UE B, and UE C, so that UE A, UE B, and UE C can receive the information.

[0264] It should also be noted that the first identifier in the data collection configuration information can be configured through RRC, MAC or the first sub-layer of the data plane.

[0265] Furthermore, it should be noted that the aforementioned first identifier values ​​X1, X2, and Y1 are merely examples. Another alternative implementation is to use the first identifier to represent data packets with more than one receiving node, and to use the absence of a first identifier to represent data packets with only one receiving node.

[0266] Optionally, the data collection configuration information may also include perception measurement-related configuration information (see Explanation 2), or the signal configuration corresponding to the training samples required by the aforementioned AI model training nodes.

[0267] Optionally, if the aforementioned second identifier is configured via CU-CP, and the UE transmits data reports via user plane or data plane (DP), then CU-CP also needs to send the configuration information of the second identifier to CU-UP or CU-DP. The configuration information of the second identifier includes at least one of the following:

[0268] The second identifier value and the corresponding first processing, for example, when the second identifier value is P1, H is processed into a point cloud, and when the second identifier value is P2, samples that do not meet the integrity requirements are removed based on the integrity of the AI ​​training samples, etc.; if CU-UP or CU-DP only supports one type of first processing, then it is also possible to perform the first processing on the data packet containing the second identifier when the second identifier exists, otherwise the data is not processed.

[0269] The second identifier value and the corresponding destination node after the first processing, for example, when the second identifier value is P1, H is processed into a point cloud and forwarded to the perception function node 2;

[0270] If the first process requires data reports from more than one UE, or if the first process requires data reports from both the UE and the base station, one possible implementation is to use data reports with the same second identifier value as input to the first process. For example, to improve perception accuracy, multiple UEs near the perceived target may perform perception measurements and send data reports, or perception measurement data may be obtained by the UE and the base station performing perception measurements. The first process can then process the perception measurement data from multiple UEs, or the aforementioned UEs and the base station, to generate point cloud data.

[0271] Optionally, if the aforementioned first identifier is configured via CU-CP, and the UE transmits data reports via user plane or data plane (DP), then CU-CP also needs to send the configuration information of the first identifier to CU-UP or CU-DP. The configuration information of the first identifier includes at least one of the following:

[0272] The first identifier value and the corresponding forwarding destination node information, or the first identifier value and the corresponding forwarding processing and forwarding destination node information. For example, a data packet with the first identifier value Q undergoes first processing before being forwarded by the second node to the forwarding destination node D.

[0273] Step (3): The first node (UE) receives the data collection configuration information from the second node.

[0274] The UE collects data and sends a data report to the second node according to the data collection configuration. The data report includes a second identifier (or a first identifier indicating processing and forwarding) and the corresponding data.

[0275] One optional implementation is that, based on data collection configuration information, the UE carries a first identifier and a second identifier with a value of X1 for the data packet corresponding to the required H on the same symbol by the AI ​​model training node and perception function nodes 1 and 2. The data packet carrying a first identifier with a value of Y1 for the required H on other symbols by the AI ​​model training node. The data packet carrying a first identifier with a value of X2 for the required position and antenna panel orientation of perception function nodes 1 and 2.

[0276] Step (4): The second node receives the data report, processes it according to the second identifier, and forwards it according to the first identifier.

[0277] Optionally, if the second node receives a data collection request from an external source, it forwards the data packet to the corresponding second node according to the first identifier value. For example, the data packet with the first identifier value of X is forwarded to the AI ​​model training node and the perception function node 1. For example, the data packet containing the second identifier is processed to obtain a point cloud and then forwarded to the perception function node 2; or the data packet with the same second identifier value is processed to obtain a point cloud and then sent to the perception function node 2; or the first processing is performed according to the second identifier with different values, such as in the example of step (2) above, one first processing is to convert H into a point cloud, and another first processing is to combine the data in the data report into the format required by the fourth node. Taking the sample requirements of the AI ​​training data in the example above as an example, the requirement is the channel estimation H of 48 REs (i.e., 4 resource blocks (RBs)) in 14 symbols in a certain time slot, that is, the channel estimation H of a total of 672 REs; however, the perception measurement data set of perception function node 1 and perception function node 2 is 3726 REs (i.e. 273 RBs) in 2 OFDM symbols. Therefore, the other first processing described here is to combine the data in the received data report according to the training data sample requirements of the AI ​​model training node and the requirements of perception function nodes 1 and 2 for H and point cloud into the corresponding data format based on the second identifier instruction, and then forward it to the fourth node.

[0278] It should be noted that in Example 1, the second node forwards the UE's data report to one or more corresponding fourth nodes, while the other first processing described here, which involves combining the data into the required format, is done by the fourth node.

[0279] Example 3:

[0280] In this example, the first node (i.e., the data provider node) is the UE, the second node is the base station, and the third node is the core network function node. The core network function node sends configuration information to the base station and the UE.

[0281] In Examples 1 and 2, the data collection configuration information is sent by the second node (base station). However, in this example, the data collection configuration information is sent by the core network functional node, and the base station and UE perform data collection and send data reports based on the data collection configuration information. This example is particularly applicable to situations where, due to privacy and security reasons, the data type and other information in the data collection request are controlled by the core network functional node.

[0282] As shown in Figure 6, this example includes the following process:

[0283] Step (1): Optionally, one or more fourth nodes (e.g., UE or AI model training nodes or perception function nodes) send a data collection request to a third node (e.g., core network data plane function node or data collection coordination function node).

[0284] The data collection request includes at least one of the following:

[0285] Data types, also known as measurement types, include RSRP, RSRQ, SINR, channel estimation H, time delay, Doppler, etc.

[0286] Data report configuration, including the number of training samples or datasets included in each data report, and the data composition of each training sample or dataset;

[0287] The total number of training samples or datasets;

[0288] Number of data-providing nodes.

[0289] An alternative implementation, where the fourth node is a UE, involves sending a data collection request to collect a training dataset based on DMRS channel estimation for fine-tuning the AI ​​model. An example of such a data collection request would be as follows:

[0290] The data type is frequency domain channel estimation H, where the channel estimation H for each resource element is a complex value consisting of a real part and an imaginary part;

[0291] The AI ​​model training node receives a data report consisting of one or more integer training samples, where each training data sample contains channel estimates H for 48 REs (i.e., 4 resource blocks (RBs)) within a certain time slot, for a total of 672 REs channel estimates H.

[0292] Total number of training samples, indicating the total number of training samples required for this data collection request, for example, 20,000;

[0293] The number of UEs can be a specified number, such as 500; or it can be a lower or upper limit for the number of UEs, such as not less than 300.

[0294] In one alternative implementation, when the fourth node is an AI model training node (such as NWDAF), if the fourth node sends a data collection request to collect the training dataset based on DMRS channel estimation, an example of a data collection request would be as follows:

[0295] The data type is frequency domain channel estimation H, where the channel estimation H for each resource element is a complex value consisting of a real part and an imaginary part;

[0296] The AI ​​model training node receives a data report consisting of one or more integer training samples, where each training data sample contains channel estimates H for 48 REs (i.e., 4 resource blocks (RBs)) within a certain time slot, for a total of 672 REs channel estimates H.

[0297] Total number of training samples, indicating the total number of training samples required for this data collection request, for example, 50,000;

[0298] The number of UEs can be a specified number, such as 500; or it can be a lower or upper limit for the number of UEs, such as not less than 300.

[0299] In one alternative implementation, when the fourth node is a sensing function node (see Explanation 1), if the third node sends a data collection request to identify and track data of the sensing target, an example of a data collection request would be as follows:

[0300] The data types are frequency domain channel estimation H, location, and antenna panel orientation;

[0301] The data report received by the sensing function node is a set of sensing measurement data for one time slot or an integer number of time slots greater than 1. Each set of sensing measurement data contains the channel estimate H of M REs with N symbols in a certain time slot; for example, 3726 REs (i.e. 273 RBs) with 2 OFDM symbols in this time slot are used for sensing measurement.

[0302] The total number of sensing measurement data sets is a requirement. If the sensing measurement data sets are used for training AI-based sensing models, the sensing function nodes can also provide a requirement for the number of sensing measurement data sets. Alternatively, there is no specific requirement for the number of sensing measurement data sets. The sensing measurement data is determined by the configuration of the sensing signals being measured. That is, the sensing measurement data sets are generated by measuring according to the configuration of the sensing signals. For time-frequency domain signals without sensing signals, there is no need to perform sensing measurements or generate sensing measurement data sets.

[0303] The number of UEs can be a specified number, such as when the sensing function node has selected a suitable UE; or it can be a lower or upper limit for the number of UEs, such as not less than 2.

[0304] Step (2): Optionally, the third node sends a data collection response message, indicating whether to accept or reject the data collection request.

[0305] The third node determines whether to accept the corresponding data collection request based on factors such as whether there are suitable data providing nodes.

[0306] Step (3): includes steps (3a) and (3b).

[0307] When a third node receives more than one data collection request, and the different data collection requests contain the same data type, or when the data collection needs within the third node contain the same data type as the aforementioned received data collection requests, and the data reports of these identical data (or the same data after the first processing) need to be directly forwarded to the corresponding fourth node via the second node:

[0308] Step (3a): The third node sends a first message (i.e., first information) to the second node, the first message including at least one of the following:

[0309] The first identifier value and the corresponding forwarding destination node information, for example, the forwarding destination nodes corresponding to the data packet with the first identifier value X are the AI ​​model training node, the perception function node and the UE, where the forwarding destination node information can be the destination node identifier or IP address, etc.; another example is that the forwarding destination node corresponding to the data packet with the first identifier value Y1 is the AI ​​model training node; the forwarding destination nodes corresponding to the data packet with the first identifier value Y2 are the AI ​​model training node and the perception function node.

[0310] The first identifier value and the corresponding forwarding processing and forwarding destination node information, for example, a data packet with the first identifier value Q, is processed by the second node before being forwarded to the forwarding destination node D;

[0311] The second identifier value and the corresponding first processing, for example, when the second identifier value is P1, H is processed into a point cloud, and when the second identifier value is P2, samples that do not meet the integrity requirements are removed based on the integrity of the AI ​​training samples, etc.

[0312] If CU-UP or CU-DP only supports one type of first processing, then the first processing can be performed on the data packet containing the second identifier when the second identifier exists, otherwise the first processing is not performed on the data.

[0313] The second identifier value and the corresponding destination node after the first processing, for example, when the second identifier value is P1, H is processed into a point cloud and forwarded to the perception function node 2;

[0314] If the first process requires data reports from more than one UE, or if the first process requires data reports from both the UE and the base station, one possible implementation is to use data reports with the same second identifier value as input to the first process. For example, to improve perception accuracy, multiple UEs near the perceived target may perform perception measurements and send data reports, or perception measurement data may be obtained by the UE and the base station performing perception measurements. The first process can then process the perception measurement data from multiple UEs, or the aforementioned UEs and the base station, to generate point cloud data.

[0315] Step (3b): The third node sends data collection configuration information to the data providing node (e.g., UE, core network functional node, etc.), wherein the data collection configuration information includes at least a first identifier and / or a second identifier. The first identifier is used to identify the data packet of the data report sent by the data providing node, and the second node needs to forward the corresponding data packet according to the first identifier. The second identifier is used to identify the processing method of the data packet of the data report sent by the data providing node, and the second node needs to process it according to the second identifier information before forwarding the data packet. When the number of receiving nodes for the data packet is greater than 1, the second identifier can also be a value of the first identifier. In this case, this value of the first identifier indicates that the data packet is forwarded to multiple receiving nodes and needs to be processed before being forwarded to multiple nodes. Examples of the first identifier or the second identifier are described in Example 1 or Example 2, and will not be repeated here.

[0316] Optionally, the data collection configuration information may also include perception measurement-related configuration information (see Explanation 2), or the signal configuration corresponding to the training samples required by the aforementioned AI model training nodes.

[0317] It should be noted that the aforementioned data packets carrying the first identifier and / or the second identifier can be mapped to one or more QoS flows or PDU sessions. Alternatively, the first identifier and / or the second identifier can be used to identify the data carried in the QoS flow or PDU session. For example, based on a received data collection request and / or internal data collection needs, the third node configures the second node or UE to send data packets composed of the same data type, carrying the aforementioned first identifier value X, within the configured QoS flow or PDU session.

[0318] Specifically, the third node can also be configured for the UE to send data packets composed of different data types by carrying the aforementioned first identifier value Y within the configured QoS stream or PDU session. If two data reports with first identifier values ​​X and Y are sent simultaneously, then the data packets with first identifier values ​​X and Y correspond to different QoS streams or PDU sessions, respectively. If the two data reports with first identifier values ​​X and Y are not sent simultaneously, then the data packets with first identifier values ​​X and Y can correspond to the same QoS stream or PDU session. The data packets carrying the second identifier can also be determined based on whether simultaneous transmission is required, using the same QoS stream or PDU session or different QoS streams or PDU sessions. When the UE sends a data report through this QoS stream / or PDU session within a certain time interval, the UE can carry the aforementioned first identifier value of X or Y in the first data packet of the data report. Then, for subsequent data packets with the same first identifier carried in this QoS stream or PDU session, it is not necessary to carry the first identifier, thereby saving the overhead of the first identifier. When the UE completes the corresponding data report transmission, one method is for the UE to send a data packet containing a first identifier and an end identifier; another method is for the UE to send a data packet containing a first identifier with different values, then the subsequent data packets are identified as data packets corresponding to the first identifier with other values; or another method is for the UE not to send data on the QoS flow or PDU session before receiving the PDU session configuration (such as modification), so as to avoid the data being mistaken by the second node as a data packet forwarded with the same first identifier as mentioned above.

[0319] Step (4): The first node (UE) receives the data collection configuration information from the third node.

[0320] The UE collects data and, according to the data collection configuration, sends a data report to the fourth node via the second node. The data report includes a first identifier and / or a second identifier, and the corresponding data.

[0321] One possible implementation is that, based on the data collection configuration information, the UE carries a first identifier with a value of X for the data packet corresponding to the H required by the AI ​​model training node and the perception function node on the same symbol; carries a first identifier with a value of Y1 for the data packet corresponding to the H required by the AI ​​model training node on other symbols; and carries a first identifier with a value of Y2 for the data packet corresponding to the position and antenna panel orientation required by the perception function node.

[0322] One possible implementation is that the UE collects configuration information based on the receipt and carries a second identifier in the data packet corresponding to the data report that needs to be processed.

[0323] Step (5): The second node receives the data report and forwards and / or processes it according to the first identifier and / or the second identifier.

[0324] It should be noted that this example applies to cases where the fourth node or data provider node is the UE, because data reports need to be forwarded and / or processed by the second node.

[0325] It should be noted that Examples 1 and 2 above can be combined.

[0326] This application provides a base station forwarding and / or processing method based on a first identifier and / or a second identifier for data collection. When forwarding, the second node does not need to parse the content of the data packet; it can forward it based on the first identifier and / or the second identifier. This application supports data packet-level data report forwarding or processing, thereby reusing the same data providing node when more than one data collection request contains the same data (or contains the same data after first processing). This reduces the air interface resource overhead of data collection, reduces the data of the data providing node, and avoids duplicate data collection. If the number of data packets corresponding to data collection is large, the overhead of the first identifier and / or the second identifier of data packets with the same first identifier and / or second identifier as the previous data packet can be saved by associating the first identifier and / or the second identifier with RB, LC, QoS, or PDU sessions.

[0327] Referring to Figure 7, which is a flowchart of a data collection method provided in an embodiment of this application, the data collection method includes the following steps:

[0328] Step 21: The second node receives a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0329] Step 22: The second node sends the corresponding data to the at least one fourth node associated with the identifier.

[0330] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0331] or,

[0332] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0333] Optionally, the at least one first identifier may include a partial first identifier, and the first identifier in the partial first identifier may be associated with a data processing method.

[0334] Optionally, the at least one first identifier includes: a first identifier corresponding to the first data;

[0335] Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

[0336] Optionally, the method further includes:

[0337] The second node receives a data collection request from at least one fourth node;

[0338] The second node sends identification information to the first node, the identification information including the at least one identifier.

[0339] Optionally, the second node sends identification information to the first node, including:

[0340] If the data collection request received by the second node meets the first condition, the second node sends the identification information to the first node;

[0341] The first condition includes at least one of the following:

[0342] There are at least two fourth-node data collection requests that request data of the same data type.

[0343] There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request;

[0344] There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node;

[0345] There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

[0346] In this embodiment, when the data collection request received by the second node meets the first condition, the second node sends the identification information to the first node. This enables the reuse of the same data provider node when more than one data collection request contains the same type of data or contains the same type of data after data processing. This reduces the air interface resource overhead of data collection, reduces the amount of data collected by the data provider node, and avoids duplicate data collection.

[0347] Optionally, the method further includes:

[0348] If the data collection request received by the second node meets the first condition, the second node selects the first node.

[0349] In one implementation, if the data collection request received by the second node satisfies the first condition, the second node selects the first node to obtain data of the same data type.

[0350] In this embodiment, when the data collection request received by the second node meets the first condition, the second node selects the first node to obtain data of the same data type. Thus, when more than one data collection request contains the same type of data or the data contains the same type of data after processing, the second node selects a suitable data providing node to meet the data requirements of more than one data collection request.

[0351] Optionally, the identification information is carried in the data collection configuration information;

[0352] The data collection configuration information also includes at least one of the following:

[0353] The data report contains wireless bearer configuration information;

[0354] The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

[0355] Optionally, the method further includes:

[0356] The second node receives the first information sent by the third node;

[0357] The first information includes at least one of the following:

[0358] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0359] The correspondence between the at least one identifier and the data processing method;

[0360] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0361] In one embodiment, when the at least one identifier includes a first identifier, the first information includes configuration information of the first identifier.

[0362] The configuration information for the first identifier includes:

[0363] The first identifier value and the corresponding node information of the forwarding destination node, or the first identifier value and the corresponding node information of the forwarding processing and forwarding destination node.

[0364] The configuration information of the input data of the data processing method can also be described as the input configuration information of the data processing method, or the configuration information of the input source of the data processing method.

[0365] In one embodiment, when the at least one identifier includes a second identifier, the first information includes configuration information of the second identifier.

[0366] The configuration information for the second identifier includes at least one of the following:

[0367] The second identifier value (i.e. the value of the second identifier) ​​and the corresponding first processing, for example, when the second identifier value is P1, H is processed into a point cloud, and when the second identifier value is P2, samples that do not meet the integrity requirements are removed according to the integrity of the AI ​​training samples, etc.; if CU-UP or CU-DP only supports one type of first processing, then it is also possible to perform the first processing on the data packet containing the second identifier when the second identifier exists, otherwise the data is not processed.

[0368] The second identifier value and the corresponding forwarding destination node after the first processing, for example, when the second identifier value is P1, H is processed into a point cloud and forwarded to the perception function node 2;

[0369] The configuration information for the input data of the data processing method corresponding to the second identifier value includes, for example, the configuration information for the input data of the data processing method of the first processing method. For instance, if the first processing requires data reports from multiple first nodes, or data reports from both the first nodes and the base station, one possible implementation is to use data reports with the same second identifier value as input to the first processing method. For example, to improve sensing accuracy, multiple first nodes near the sensing target may perform sensing measurements and send data reports, or the first nodes and the base station may perform sensing measurements to obtain sensing measurement data. The first processing method can then process the sensing measurement data from multiple first nodes, or the aforementioned first nodes and the base station, to generate point cloud data.

[0370] In this embodiment, the second node receives the first information sent by the third node, thereby enabling the second node to perform data processing based on the first information and the second identifier, and / or to forward data based on the first information and the first identifier.

[0371] Optionally, if the identification information includes at least one second identifier, the second node sends corresponding data to the fourth node associated with the at least one identifier, including:

[0372] The second node performs data processing corresponding to each of the data corresponding to the second identifier.

[0373] The second node sends the corresponding processed data to the fourth node associated with the at least one second identifier.

[0374] In this embodiment, the second node performs data processing corresponding to each of the data corresponding to the second identifier; the second node then sends the processed data to the fourth node associated with the at least one second identifier. This expands the reuse of the same data provider node by using the second identifier. For data services where the required data is of the same type or overlaps after data processing, the same data provider node can also be reused, further reducing the overhead of air interface resources for data collection, decreasing the amount of data collected by the data provider node, and avoiding duplicate data collection.

[0375] Optionally, if the partial first identifier exists among the at least one first identifier, the second node sends corresponding data to the fourth node associated with the at least one identifier, including:

[0376] The second node performs data processing corresponding to each first identifier in the first identifier portion;

[0377] The second node sends the corresponding processed data to the fourth node associated with the first identifier.

[0378] In this embodiment, the second node performs data processing corresponding to each first identifier in the partial first identifier; the second node then sends the processed data to the fourth node associated with the partial first identifier. In this way, the partial first identifier expands the reuse of the same data providing node. For data services where the required data is of the same type or overlaps after data processing, the same data providing node can also be reused, further reducing the air interface resource overhead of data collection, reducing the data collection volume of data providing nodes, and avoiding duplicate data collection.

[0379] Optionally, the data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier;

[0380] The target object includes any one of the following:

[0381] Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

[0382] Optionally, the first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and the data packets in the data corresponding to the target identifier transmitted on the target object other than the first data packet do not carry the target identifier.

[0383] Optionally, the first data packet is a Control Protocol Data Unit (PDU) or a Data PDU.

[0384] Optionally, the method further includes:

[0385] The user plane function or data plane function of the second node receives the second information sent by the control plane function of the second node;

[0386] The second information includes at least one of the following:

[0387] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0388] The correspondence between the at least one identifier and the data processing method;

[0389] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0390] In one embodiment, when the at least one identifier includes a first identifier, the second information includes configuration information of the first identifier. The configuration information of the first identifier is described above in the description of the configuration information of the first identifier, and will not be repeated here.

[0391] In one embodiment, when the at least one identifier includes a second identifier, the second information includes configuration information of the second identifier. The configuration information of the second identifier is described above in the description of the configuration information of the second identifier, and will not be repeated here.

[0392] It should be noted that this embodiment is an implementation of the second node corresponding to the embodiment shown in Figure 3. For the specific implementation, please refer to the relevant description of the embodiment shown in Figure 3. To avoid repetition, this embodiment will not be described again.

[0393] Referring to Figure 8, which is a flowchart of a data collection method provided in an embodiment of this application, the data collection method includes the following steps:

[0394] Step 31: The third node receives a data collection request from at least one fourth node;

[0395] Step 32: The third node sends identification information to the first node, the identification information including at least one identifier.

[0396] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0397] or,

[0398] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0399] Optionally, the method further includes:

[0400] The third node sends the first information to the second node;

[0401] The first information includes at least one of the following:

[0402] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0403] The correspondence between the at least one identifier and the data processing method;

[0404] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0405] Optionally, the third node sends identification information to the first node, including:

[0406] If the data collection request received by the third node meets the first condition, the third node sends the identification information to the first node;

[0407] The first condition includes at least one of the following:

[0408] There are at least two fourth-node data collection requests that request data of the same data type.

[0409] There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request;

[0410] There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node;

[0411] There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

[0412] It should be noted that this embodiment is an implementation of the third node corresponding to the embodiment shown in Figure 3 or Figure 7. For the specific implementation, please refer to the relevant description of the embodiment shown in Figure 3 or Figure 7. To avoid repetition, this embodiment will not be described again.

[0413] The data collection method provided in this application can be executed by a data collection device. This application uses an example of a data collection device executing the data collection method to illustrate the data collection device provided in this application.

[0414] This application provides a data collection device. As an example, the data collection device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 101 listed above, and the network-side device may include, but is not limited to, the type of network-side device 102 listed above. This application does not impose specific limitations.

[0415] The data collection device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0416] Specifically, referring to Figure 9, when the data collection device is a first node or a component within the first node, the data collection device 200 includes:

[0417] The receiving module 201 is used to receive identification information sent by a second node or a third node, wherein the identification information includes at least one identifier;

[0418] Processing module 202 is used to collect data based on the identification information;

[0419] The sending module 203 is used to send a data report to the second node. The data report includes the at least one identifier and the data corresponding to each of the at least one identifier.

[0420] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0421] or,

[0422] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0423] Optionally, the at least one first identifier may include a partial first identifier, and the first identifier in the partial first identifier may be associated with a data processing method.

[0424] Optionally, the at least one first identifier includes: a first identifier corresponding to the first data;

[0425] Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

[0426] Optionally, each of the at least one identifier is associated with at least one node information, which is used to characterize the fourth node or the second node.

[0427] Optionally, the data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier;

[0428] The target object includes any one of the following:

[0429] Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

[0430] Optionally, the first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and the data packets in the data corresponding to the target identifier transmitted on the target object other than the first data packet do not carry the target identifier.

[0431] Optionally, the first data packet is a Control Protocol Data Unit (PDU) or a Data PDU.

[0432] Optionally, the identification information is carried in the data collection configuration information;

[0433] The data collection configuration information also includes at least one of the following:

[0434] The data report contains wireless bearer configuration information;

[0435] The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

[0436] Referring to Figure 10, when the data collection device is a second node or a component within a second node, the data collection device 300 includes:

[0437] The receiving module 301 is configured to receive a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0438] The sending module 302 is used to send corresponding data to the at least one fourth node associated with the identifier.

[0439] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0440] or,

[0441] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0442] Optionally, the at least one first identifier may include a partial first identifier, and the first identifier in the partial first identifier may be associated with a data processing method.

[0443] Optionally, the at least one first identifier includes: a first identifier corresponding to the first data;

[0444] Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

[0445] Optionally, the receiving module is further configured to: receive a data collection request sent by at least one fourth node;

[0446] The sending module is further configured to: send identification information to the first node, the identification information including the at least one identifier.

[0447] Optionally, the sending module is specifically used for:

[0448] If the data collection request received by the second node meets the first condition, the identification information is sent to the first node;

[0449] The first condition includes at least one of the following:

[0450] There are at least two fourth-node data collection requests that request data of the same data type.

[0451] There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request;

[0452] There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node;

[0453] There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

[0454] Optionally, the device further includes:

[0455] The processing module is used to select the first node when the data collection request received by the second node meets the first condition.

[0456] Optionally, the identification information is carried in the data collection configuration information;

[0457] The data collection configuration information also includes at least one of the following:

[0458] The data report contains wireless bearer configuration information;

[0459] The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

[0460] Optionally, the receiving module is further configured to: receive first information sent by the third node;

[0461] The first information includes at least one of the following:

[0462] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0463] The correspondence between the at least one identifier and the data processing method;

[0464] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0465] Optionally, when the identification information includes at least one second identifier, the processing module of the device is configured to: perform data processing corresponding to the second identifier on the data corresponding to each second identifier;

[0466] The sending module is also used to send the corresponding processed data to the fourth node associated with the at least one second identifier.

[0467] Optionally, if the partial first identifier exists in the at least one first identifier, the processing module of the device is configured to: perform data processing corresponding to the first identifier on the data corresponding to each of the partial first identifiers;

[0468] The sending module is also used to send the corresponding processed data to the fourth node associated with the first identifier.

[0469] Optionally, the data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier;

[0470] The target object includes any one of the following:

[0471] Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

[0472] Optionally, the first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and the data packets in the data corresponding to the target identifier transmitted on the target object other than the first data packet do not carry the target identifier.

[0473] Optionally, the first data packet is a Control Protocol Data Unit (PDU) or a Data PDU.

[0474] Optionally, the sending module is further configured to:

[0475] Receive the second information sent by the control plane function of the second node through the user plane function or the data plane function;

[0476] The second information includes at least one of the following:

[0477] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0478] The correspondence between the at least one identifier and the data processing method;

[0479] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0480] Referring to Figure 11, when the data collection device is a third node or a component within a third node, the data collection device 400 includes:

[0481] Receiver module 401 is used to receive data collection requests sent by at least one fourth node;

[0482] The sending module 402 is used to send identification information to the first node, the identification information including at least one identifier.

[0483] Optionally, the at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1;

[0484] or,

[0485] The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

[0486] Optionally, the sending module is further configured to: send first information to the second node;

[0487] The first information includes at least one of the following:

[0488] The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node;

[0489] The correspondence between the at least one identifier and the data processing method;

[0490] The configuration information of the input data for the data processing method corresponding to the at least one identifier.

[0491] Optionally, the sending module is further configured to: send the identification information to the first node if the data collection request received by the third node satisfies the first condition;

[0492] The first condition includes at least one of the following:

[0493] There are at least two fourth-node data collection requests that request data of the same data type.

[0494] There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request;

[0495] There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node;

[0496] There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

[0497] The data collection device provided in this application embodiment can implement the various processes implemented in the method embodiments of FIG3, FIG7 or FIG8 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0498] As shown in Figure 12, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. For example, when the communication device 500 is a first node, when the program or instructions are executed by the processor 501, they implement the various steps of the data collection method embodiment on the first node side described above, and achieve the same technical effect. When the communication device 500 is a second node, when the program or instructions are executed by the processor 501, they implement the various steps of the data collection method embodiment on the second node side described above, and achieve the same technical effect. To avoid repetition, this will not be repeated here. When the communication device 500 is a third node, when the program or instructions are executed by the processor 501, they implement the various steps of the data collection method embodiment on the third node side described above, and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0499] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the data collection device shown in FIG9. Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0500] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0501] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 13 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0502] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0503] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0504] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0505] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0506] When the terminal is the first node, the radio frequency unit 601 is used to: receive identification information sent by the second node or the third node, wherein the identification information includes at least one identifier;

[0507] Processor 610: Used for data collection based on the identification information;

[0508] The radio frequency unit 601 is also configured to: send a data report to the second node, the data report including the at least one identifier and data corresponding to each of the at least one identifier.

[0509] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in Figure 3 of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0510] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG7 or FIG8. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0511] Specifically, this application embodiment also provides a network-side device, which can be the data collection device shown in FIG10. As shown in FIG14, the network-side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information through the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be transmitted and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and transmits it through the antenna 701.

[0512] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 703, which includes a baseband processor.

[0513] The baseband device 703 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG14. One of the chips is, for example, a baseband processor, which is connected to the memory 705 via a bus interface to call the program or instructions in the memory 705 to execute the network-side device operation shown in the above method embodiment.

[0514] The network-side device may also include a network interface 706, such as a Common Public Radio Interface (CPRI).

[0515] When the network-side device is the second node, the radio frequency device 702 is used for:

[0516] Receive a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0517] Send the corresponding data to the at least one fourth node associated with the identifier.

[0518] In addition, the network-side device 700 of this application embodiment also includes: a program or instructions stored in a memory 705 and executable on a processor 704. The processor 704 calls the program or instructions in the memory 705 to execute the methods executed by each module shown in FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0519] Specifically, this application also provides a network-side device. As shown in FIG15, the network-side device 800 includes a processor 801, a network interface 802, and a memory 803. The network-side device may be the data collection device shown in FIG9, FIG10, or FIG11. The network interface 802 is, for example, a Common Public Radio Interface (CPRI).

[0520] When the network-side device is the first node:

[0521] Network interface 802 is used to: receive identification information sent by a second node or a third node, the identification information including at least one identifier;

[0522] Processor 801 is used to: collect data based on the identification information;

[0523] Network interface 802 is also used to: send a data report to the second node, the data report including the at least one identifier and data corresponding to each of the at least one identifier.

[0524] When the network-side device is the second node, network interface 802 is used for:

[0525] Receive a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier;

[0526] Send the corresponding data to the at least one fourth node associated with the identifier.

[0527] When the network-side device is a third node, network interface 802 is used for:

[0528] Receive data collection requests from at least one fourth node;

[0529] Send identification information to the first node, the identification information including at least one identifier.

[0530] In addition, the network-side device 800 of this application embodiment also includes: a program or instructions stored in a memory 803 and executable on a processor 801. The processor 801 calls the program or instructions in the memory 803 to execute the methods executed by the modules shown in FIG9, FIG10 or FIG11 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0531] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data collection method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0532] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0533] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data collection method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0534] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0535] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data collection method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0536] This application also provides a wireless communication system, including a first node and a second node; or including a first node, a second node, and a third node. The first node can be used to perform the steps of the data collection method applied to the first node as described above, the second node can be used to perform the steps of the data collection method applied to the second node as described above, and the third node can be used to perform the steps of the data collection method applied to the third node as described above.

[0537] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0538] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0539] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A data collection method, comprising: The first node receives identification information sent by the second or third node, the identification information including at least one identifier; The first node collects data based on the identification information; The first node sends a data report to the second node, the data report including the at least one identifier and the data corresponding to each of the at least one identifier.

2. The method according to claim 1, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

3. The method according to claim 2, wherein, The at least one first identifier contains a portion of the first identifiers, and the first identifiers in the portion of the first identifiers are associated with a data processing method.

4. The method according to claim 2 or 3, wherein, The at least one first identifier includes: a first identifier corresponding to the first data; Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

5. The method according to any one of claims 1-4, wherein, Each of the at least one identifier is associated with at least one node information, which is used to characterize the fourth node or the second node.

6. The method according to any one of claims 1-5, wherein, The data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier; The target object includes any one of the following: Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

7. The method according to claim 6, wherein, The first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and none of the data packets in the data corresponding to the target identifier transmitted on the target object, except for the first data packet, carry the target identifier.

8. The method according to claim 7, wherein, The first data packet is a Control Protocol Data Unit (PDU) or a Data PDU.

9. The method according to any one of claims 1-8, wherein, The identification information is carried in the data collection configuration information; The data collection configuration information also includes at least one of the following: The data report contains wireless bearer configuration information; The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

10. A data collection method, comprising: The second node receives a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier; The second node sends the corresponding data to the at least one fourth node associated with the identifier.

11. The method according to claim 10, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

12. The method according to claim 11, wherein, The at least one first identifier contains a portion of the first identifiers, and the first identifiers in the portion of the first identifiers are associated with a data processing method.

13. The method according to claim 11 or 12, wherein, The at least one first identifier includes: a first identifier corresponding to the first data; Wherein, the data collected by the first node includes the first data, which is used to provide to at least two fourth nodes; or, the first data is used to provide to the second node and at least one fourth node.

14. The method according to any one of claims 10-13, wherein, The method further includes: The second node receives a data collection request from at least one fourth node; The second node sends identification information to the first node, the identification information including the at least one identifier.

15. The method according to claim 14, wherein, The second node sends identification information to the first node, including: If the data collection request received by the second node meets the first condition, the second node sends the identification information to the first node; The first condition includes at least one of the following: There are at least two fourth-node data collection requests that request data of the same data type. There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request; There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node; There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

16. The method according to claim 15, wherein, The method further includes: If the data collection request received by the second node meets the first condition, the second node selects the first node.

17. The method according to any one of claims 14-16, wherein, The identification information is carried in the data collection configuration information; The data collection configuration information also includes at least one of the following: The data report contains wireless bearer configuration information; The first indication information is used to indicate the carrying method of at least one of the first identifier and the second identifier in the identification information in the data report.

18. The method according to any one of claims 10-13, wherein, The method further includes: The second node receives the first information sent by the third node; The first information includes at least one of the following: The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node; The correspondence between the at least one identifier and the data processing method; The configuration information of the input data for the data processing method corresponding to the at least one identifier.

19. The method according to any one of claims 11-13, wherein, When the identification information includes at least one second identifier, the second node sends corresponding data to the fourth node associated with the at least one identifier, including: The second node performs data processing corresponding to each of the data corresponding to the second identifier. The second node sends the corresponding processed data to the fourth node associated with the at least one second identifier.

20. The method according to claim 12, wherein, If a portion of the first identifier exists among the at least one first identifier, the second node sends corresponding data to the fourth node associated with the at least one identifier, including: The second node performs data processing corresponding to each first identifier in the first identifier portion; The second node sends the corresponding processed data to the fourth node associated with the first identifier.

21. The method according to any one of claims 10-20, wherein, The data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier; The target object includes any one of the following: Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

22. The method according to claim 21, wherein, The first data packet in the data corresponding to the target identifier transmitted on the target object carries the target identifier, and none of the data packets in the data corresponding to the target identifier transmitted on the target object, except for the first data packet, carry the target identifier.

23. The method according to claim 22, wherein, The first data packet is a Control Protocol Data Unit (PDU) or a Data PDU.

24. The method according to any one of claims 10-23, wherein, The method further includes: The user plane function or data plane function of the second node receives the second information sent by the control plane function of the second node; The second information includes at least one of the following: The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node; The correspondence between the at least one identifier and the data processing method; The configuration information of the input data for the data processing method corresponding to the at least one identifier.

25. A data collection method, comprising: The third node receives a data collection request sent by at least one fourth node; The third node sends identification information to the first node, and the identification information includes at least one identifier.

26. The method according to claim 25, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

27. The method according to claim 25 or 26, wherein, The method further includes: The third node sends the first information to the second node; The first information includes at least one of the following: The correspondence between the at least one identifier and the node information, wherein the node information is used to characterize the fourth node or the second node; The correspondence between the at least one identifier and the data processing method; The configuration information of the input data for the data processing method corresponding to the at least one identifier.

28. The method according to any one of claims 25-27, wherein, The third node sends identification information to the first node, including: If the data collection request received by the third node meets the first condition, the third node sends the identification information to the first node; The first condition includes at least one of the following: There are at least two fourth-node data collection requests that request data of the same data type. There exists at least one fourth node whose data collection request requires the same type of data as the data collection request of the second node. There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node; There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

29. A data collection device, comprising: A receiving module is used to receive identification information sent by a second node or a third node, wherein the identification information includes at least one identifier; The processing module is used to collect data based on the identification information; The sending module is used to send a data report to the second node. The data report includes the at least one identifier and the data corresponding to each of the at least one identifier.

30. The apparatus according to claim 29, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

31. The apparatus according to claim 29 or 30, wherein, The data corresponding to the target identifier in the at least one identifier is transmitted through the target object associated with the target identifier; The target object includes any one of the following: Radio bearer (RB); Logical channel (LC); Quality of Service (QoS) stream; Protocol Data Unit (PDU) session.

32. A data collection device, comprising: The receiving module is configured to receive a data report sent by the first node, the data report including at least one identifier and data corresponding to each of the at least one identifier; The sending module is used to send corresponding data to the at least one fourth node associated with the identifier.

33. The apparatus according to claim 32, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

34. The apparatus according to claim 32 or 33, wherein, The receiving module is also configured to: receive a data collection request sent by at least one fourth node; The sending module is further configured to: send identification information to the first node, the identification information including the at least one identifier.

35. The apparatus according to claim 34, wherein, The sending module is specifically used for: If the data collection request received by the second node meets the first condition, the identification information is sent to the first node. The first condition includes at least one of the following: There are at least two fourth-node data collection requests that request data of the same data type. There exists at least one fourth node whose data collection request requests data of the same type as the data required by the second node's data collection request; There exists a data collection request from at least one fourth node whose requested data, after being processed by a data processing method, is of the same type as the data requested by a data collection request from another fourth node; There exists a data collection request from at least one fourth node. The data requested is processed by a data processing method and is of the same type as the data required by the data collection request of the second node.

36. A data collection device, comprising: The receiving module is used to receive data collection requests sent by at least one fourth node; The sending module is used to send identification information to the first node, the identification information including at least one identifier.

37. The apparatus according to claim 36, wherein, The at least one identifier includes: at least one first identifier, wherein the first identifier is used to indicate whether the forwarding destination node of the corresponding data is greater than 1; or, The at least one identifier includes: at least one second identifier, the second identifier being used to indicate the data processing method for the data corresponding to the second identifier.

38. A node comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the data collection method as claimed in any one of claims 1 to 9, or the steps of the data collection method as claimed in any one of claims 10 to 24, or the steps of the data collection method as claimed in any one of claims 25 to 28.

39. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the data collection method as claimed in any one of claims 1 to 9, or the steps of the data collection method as claimed in any one of claims 10 to 24, or the steps of the data collection method as claimed in any one of claims 25 to 28.