Data collection method and apparatus, and communication device

Abstract

The present application belongs to the technical field of communications. Disclosed are a data collection method and apparatus, and a communication device. The method comprises: a first device sending a first message to a second device, wherein the first message includes at least one of the following: a first indication, which is used for indicating that a data collection mode of a data collection request is a target mode; first information, which is used for indicating data needing to be acquired by the first device; second information, which is used for indicating data that the first device can provide; and third information, which is used for indicating a reward that the first device can provide; and the target mode comprises any one of the following: a first mode, in which the first device acquires data from the second device; a second mode, in which the first device acquires data from the second device, and provides data or a reward to the second device; a third mode, in which the first device acquires data from the second device, and provides collected data to the second device; a fourth mode, in which the first device acquires data from the second device, and provides existing data to the second device; and a fifth mode, in which the first device acquires data from the second device, and provides a reward to the second device.

Description

Data collection method, device and communication equipment

[0001] Cross-references

[0002] This disclosure claims priority to Chinese patent application number 202410379253.8 filed on March 29, 2024, entitled “Data Collection Method, Device and Communication Equipment,” and the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data collection method, device and communication equipment. Background Art

[0004] Mobile communication network data is the foundation for network-side devices and user equipment (UE) to understand real-time status and formulate appropriate policies and controls. In related technologies, data demanders typically obtain data from data providers in a one-way manner. For example, network-side devices obtain data from UEs in a one-way manner. This data collection method is relatively simple. In practical applications, this inflexible data collection method results in limited data available to data demanders, resulting in poor data collection results. Summary of the Invention

[0005] The embodiments of the present application provide a data collection method, apparatus, and communication device, which can solve the problem that the data collection method in the related art is relatively single and the data collection effect is poor.

[0006] In a first aspect, a data collection method is provided, which is performed by a first device, and the method includes:

[0007] The first device sends a first message to the second device, where the first message includes at least one data collection request;

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

[0009] an identifier of the data collection request;

[0010] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0011] First information, used to indicate data that the first device needs to obtain;

[0012] second information, used to indicate data that the first device can provide;

[0013] third information, used to indicate a reward that can be provided by the first device;

[0014] The target mode includes any of the following:

[0015] a first mode, in which the first device obtains data from the second device;

[0016] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0017] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0018] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0019] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0020] In a second aspect, a data collection method is provided, which is performed by a second device, and the method includes:

[0021] The second device receives a first message from the first device, the first message including at least one data collection request;

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

[0023] an identifier of the data collection request;

[0024] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0025] First information, used to indicate data that the first device needs to obtain;

[0026] second information, used to indicate data that the first device can provide;

[0027] third information, used to indicate a reward that can be provided by the first device;

[0028] The target mode includes any of the following:

[0029] a first mode, in which the first device obtains data from the second device;

[0030] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0031] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0032] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0033] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0034] In a third aspect, a data collection device is provided, the device comprising:

[0035] a first sending unit, configured to send a first message to a second device, wherein the first message includes at least one data collection request;

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

[0037] an identifier of the data collection request;

[0038] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0039] First information, used to indicate data that the first device needs to obtain;

[0040] second information, used to indicate data that the first device can provide;

[0041] third information, used to indicate a reward that can be provided by the first device;

[0042] The target mode includes any of the following:

[0043] a first mode, in which the first device obtains data from the second device;

[0044] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0045] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0046] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0047] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0048] In a fourth aspect, a data collection device is provided, the device comprising:

[0049] a first receiving unit, configured to receive a first message from a first device, wherein the first message includes at least one data collection request;

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

[0051] an identifier of the data collection request;

[0052] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0053] First information, used to indicate data that the first device needs to obtain;

[0054] second information, used to indicate data that the first device can provide;

[0055] third information, used to indicate a reward that can be provided by the first device;

[0056] The target mode includes any of the following:

[0057] a first mode, in which the first device obtains data from the second device;

[0058] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0059] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0060] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0061] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0062] In a fifth aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0063] According to a sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to: send a first message to a second device, the first message comprising at least one data collection request;

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

[0065] an identifier of the data collection request;

[0066] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0067] First information, used to indicate data that the first device needs to obtain;

[0068] second information, used to indicate data that the first device can provide;

[0069] third information, used to indicate a reward that can be provided by the first device;

[0070] The target mode includes any of the following:

[0071] a first mode, in which the first device obtains data from the second device;

[0072] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0073] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0074] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0075] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0076] According to a seventh aspect, a second device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to: receive a first message from a first device, the first message comprising at least one data collection request;

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

[0078] an identifier of the data collection request;

[0079] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0080] First information, used to indicate data that the first device needs to obtain;

[0081] second information, used to indicate data that the first device can provide;

[0082] third information, used to indicate a reward that can be provided by the first device;

[0083] The target mode includes any of the following:

[0084] a first mode, in which the first device obtains data from the second device;

[0085] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0086] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0087] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0088] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0089] In an eighth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0090] In a ninth aspect, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device can be used to execute the steps of the method described in the first aspect, and the second device can be used to execute the steps of the method described in the second aspect.

[0091] In the tenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0092] In the eleventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data collection method described in the first aspect, or to implement the steps of the data collection method described in the second aspect.

[0093] In an embodiment of the present application, a first device sends a first message to a second device, and the first message includes at least one data collection request; wherein the data collection request includes at least one of the following: an identifier of the data collection request; a first indication for indicating that the data collection mode of the data collection request is a target mode; first information for indicating the data that the first device needs to obtain; second information for indicating the data that the first device can provide; third information for indicating the reward that the first device can provide; wherein the target mode includes any one of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device, and the first device provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device, and the first device provides the second device with existing data; a fifth mode, in which the first device obtains data from the second device, and the first device provides the second device with a reward. In this way, the first device can use any of the first to fifth modes to collect data, not just the data requester obtaining data from the data provider in a unilateral manner, making data collection more flexible and diverse. In practical applications, the first device can select the appropriate data collection mode to collect data based on demand, which helps improve data collection effectiveness. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application;

[0095] FIG2 is a schematic diagram of a data collection architecture using data collection coordination;

[0096] FIG3 is a schematic diagram of an open architecture for network data analysis using data collection coordination;

[0097] FIG4 is a flow chart of a data collection method provided in an embodiment of the present application;

[0098] FIG5 is a flow chart of another data collection method provided in an embodiment of the present application;

[0099] FIG6 is a structural diagram of a data collection device provided in an embodiment of the present application;

[0100] FIG7 is a structural diagram of another data collection device provided in an embodiment of the present application;

[0101] FIG8 is a structural diagram of a communication device provided in an embodiment of the present application;

[0102] FIG9 is a structural diagram of a terminal provided in an embodiment of the present application;

[0103] FIG10 is a structural diagram of a network-side device provided in an embodiment of the present application;

[0104] FIG11 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0105] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0106] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0107] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication 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 operation to be performed or the requested result, etc. based on the judgment result.

[0108] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0109] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0110] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home subscriber server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0111] Before describing the embodiments of the present application, the following briefly introduces the relevant technologies for data collection:

[0112] 1. 5G network data analysis services

[0113] The Network Data Analytics Function (NWDAF) is a 5G Core Control Plane (5GC) network function that interacts with different entities for different purposes:

[0114] Collect data based on event subscriptions provided by AMF, SMF, PCF, UDM, AF (directly or through NEF), or Operations, Administration and Maintenance (OAM);

[0115] Use the Data Collection Coordination Function (DCCF) for analysis and data collection (optional)

[0116] Retrieve information from a data repository (e.g., a UDR that retrieves user-related information via a UDM);

[0117] Store and retrieve information from the Analytics Data Repository Function (ADRF);

[0118] Profiling and data collection from the Messaging Framework Adaptor Function (MFAF); (optional)

[0119] Retrieve information about NFs (e.g., retrieve information related to NFs from NRF);

[0120] Provide analysis to consumers based on their needs;

[0121] Provide consumers with large amounts of data.

[0122] FIG2 illustrates a Data Collection architecture using Data Collection Coordination.

[0123] FIG3 illustrates a Network Data Analytics Exposure architecture using Data Collection Coordination.

[0124] 2. Network configuration triggers terminal data reporting events

[0125] In the current protocol, as shown in Table 1, the following network configurations are supported to trigger terminal data reporting events:

[0126] Table 1

[0127] Among them, Ms is the measurement result of the serving cell without considering any offset;

[0128] Mn is the measurement result of the neighboring cell without considering any offset;

[0129] Mp is the measurement result of the special cell (SpCell) without considering any offset;

[0130] Mi is the result of interference measurement without considering any offset;

[0131] Ofn is the neighbor cell measurement event offset, and Ocn is the neighbor cell specific offset. Both are configured by Radio Resource Control (RRC). If not configured by RRC, set to 0.

[0132] Ofp is the primary cell measurement event offset, and Ocp is the primary cell-specific offset. Both are configured by RRC. If not configured by RRC, set to 0.

[0133] Hys is the hysteresis parameter of this event, which is configured by RRC and has a value range of [0, 30]. The actual value is the configured value * 0.5dB;

[0134] Off is the offset parameter of this event (i.e., a3-Offset defined in reportConfigNR of this event);

[0135] Thresh is the threshold parameter of this event (i.e., the Threshold defined in reportConfigNR of this event);

[0136] In the case of Reference Signal Received Power (RSRP), Mn and Mp are expressed in dBm, or in the case of Reference Signal Received Quality (RSRQ) and Reference Signal (RS) signal-to-noise and interference ratio (SINR), they are expressed in dB. Ofn, Ocn, Ofp, Ocp, Hys, and Off are expressed in dB, and Thresh is expressed in the same units as Mn.

[0137] When one or more cells meet the entry conditions of the configured event within the trigger time (timeToTrigger), the upper layer arranges the measurement results corresponding to the measurement resources that meet the trigger conditions in the measurement configuration and sends them to the network side device.

[0138] 3. Artificial Intelligence (AI) in Wireless Networks

[0139] The standardization work of applying AI to mobile communications has been carried out in the 3rd Generation Partnership Project (3GPP). Among them, RAN3 conducted research and standardization work on three use cases (Mobility Robustness Optimization (MRO), Network Energy Conservation (NES), and Mobility Load Balancing (MLB)) in R17 / R18: mobility optimization, load balancing, and network energy saving. From the data of the three use cases in the existing standards, it can be seen that the network side data mainly includes the current service status and future service status prediction of the serving cell and the neighboring cell. The AI ​​function deployment options of the three use cases are the same, including the following two methods:

[0140] Method 1: AI training functions are deployed in the OAM, and AI inference functions are deployed in the base station.

[0141] Method 2: Both AI training and inference functions are deployed at the base station.

[0142] Data from mobile communication networks is the basis for network-side devices and UEs to understand real-time status and formulate correct strategies or controls. In related technologies, network-side devices can use UEs to obtain network quality data, user experience data, and other data through methods such as Self-Organizing Network (SON), Minimization of Drive-Test (MDT), or Quality of Experience (QoE). However, this data collection method is relatively simple and the UE does not benefit significantly from it. Therefore, in actual applications, the UE data obtained by network-side devices is limited, resulting in poor data collection results.

[0143] In view of this, the embodiments of the present application provide a data collection method, a data collection device, and a communication device to solve the problem that the data collection method in the related art is relatively single and the data collection effect is poor.

[0144] The data collection method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0145] FIG4 shows a flow chart of a data collection method provided by an embodiment of the present application. As shown in FIG4 , the data collection method includes the following steps:

[0146] Step 401: A first device sends a first message to a second device, where the first message includes at least one data collection request;

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

[0148] The identifier of the data collection request is used to uniquely identify a data collection request, which can be referred to as a request identifier or request ID;

[0149] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0150] First information, used to indicate data that the first device needs to obtain;

[0151] second information, used to indicate data that the first device can provide;

[0152] third information, used to indicate a reward that can be provided by the first device;

[0153] The target mode includes any of the following:

[0154] a first mode, in which the first device obtains data from the second device;

[0155] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0156] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0157] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0158] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0159] In the embodiments of the present application, the first device can be understood as a data demander (or data requester), and the second device can be understood as a data provider. The first device can include a network-side device or a terminal, and the second device can also include a network-side device or a terminal. For example, the first device is a network-side device and the second device is a terminal; or, the first device is a terminal and the second device is a network-side device; or, both the first device and the second device are network-side devices; or, both the first device and the second device are terminals.

[0160] Optionally, in the second mode, the first device providing data to the second device includes providing the second device with data collected during a data collection process or existing data.

[0161] The first mode may be referred to as a single-ended mode (or one-way mode), which means that the first device obtains required data from the second device, and the first device does not provide any data or reward to the second device.

[0162] The second mode, also known as dual-end mode (or bidirectional mode), involves the first device obtaining the required data from the second device, and the second device also receiving data or rewards from the first device. The rewards are in exchange for providing data to the second device, increasing the likelihood that the second device will accept the data collection request. These rewards can include QoS guarantees, priority increases, traffic, voice calls, phone charges, or points.

[0163] The third mode, also known as the sharing mode, involves a data collection process in which the first device requests data from the second device, and the second device requests data from the first device. Ultimately, the first device sends the data it collected to the second device, and the second device sends the data it collected to the first device.

[0164] The fourth mode may be referred to as an exchange mode, which means that during a data collection process, the first device requests the required data from the second device in exchange for its existing data.

[0165] The fifth mode, called the reward mode, involves the first device requesting the required data from the second device in exchange for a valuable reward during a data collection process. The reward can include QoS guarantees, priority upgrades, data usage, voice calls, phone charges, or points.

[0166] The fourth mode differs from the third mode in that the data provided by the first device in the fourth mode is existing (i.e., already collected) data, whereas the data provided by the first device in the third mode is data collected during a subsequent data collection process. For example, in the third mode, both parties agree to collect data and then report the data to each other at the agreed time. The data provided by the first device matches the data provided by the second device in terms of collection time. In the fourth mode, the data provided by the first device is already collected, and its collection time is earlier than the time when the second device collected the data.

[0167] Compared with the third and fourth modes, the fifth mode still needs to maintain relevant reward information after the data is collected to ensure that the data provider can obtain the reward, that is, realize the value of the reward.

[0168] In the second to fifth modes described above, not only can the first device obtain data from the second device, but the second device can also obtain data or rewards from the first device. Since the second device can also benefit from it, the second device is more willing to provide data to the first device. In addition, when the second device performs autonomous performance optimization or user experience optimization, it can obtain the data of the first device as a reference, thereby improving the performance optimization effect. It can be seen that the embodiments of the present application can promote collaboration between the first device and the second device, promote data sharing, data exchange or data rewards, and make it easier for the first device and the second device to obtain the data or rewards they need, thereby improving the data collection effect.

[0169] Unlike the first mode, in any of the second through fifth modes, the first and second devices can both obtain the data or rewards they desire. Therefore, the second through fifth modes can be understood as four different types of dual-ended modes. Alternatively, the third, fourth, and fifth modes can be understood as sub-modes of the second mode. For example, the third mode can be the first sub-mode of the second mode, the fourth mode can be the second sub-mode of the second mode, and the fifth mode can be the third sub-mode of the second mode.

[0170] It should be noted that the data collection mode can be explicitly indicated by the first indication, or implicitly indicated by the first information, second information or third information mentioned above.

[0171] In one embodiment, the first message includes the second information but does not include the first indication, which is equivalent to implicitly indicating the second mode, the third mode, or the fourth mode.

[0172] In one implementation, the first message includes the third information but does not include the first indication, which is equivalent to implicitly indicating the second mode or the fifth mode.

[0173] It should be noted that the first message may be sent to a designated second device, or may be sent to multiple second devices via a broadcast message, etc., so as to solicit second devices (such as UEs) that are willing to provide data.

[0174] In an embodiment of the present application, a first device sends a first message to a second device, the first message including at least one data collection request; wherein the data collection request includes at least one of the following: an identifier of the data collection request; a first indication indicating that the data collection mode of the data collection request is a target mode; and first information indicating the data that the first device needs to obtain. wherein the target mode includes any of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device and provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device and provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device and provides the second device with existing data; and a fifth mode, in which the first device obtains data from the second device and provides the second device with a reward. In this way, the first device can use any of the first to fifth modes to collect data, making the data collection method more flexible and diverse. In actual applications, the first device can select an appropriate data collection mode to collect data according to needs, which is conducive to improving data collection effects.

[0175] In some embodiments, the data that can be provided by the first device indicated by the second information includes at least one of the following:

[0176] data that the first device can provide during the data collection process;

[0177] The first device may provide existing data.

[0178] As previously described, if the first message does not include the first indication, the second mode, the third mode, or the fourth mode may be implicitly indicated by the second information. If the third mode and the fourth mode exist and the first message does not include the first indication, the second information may specifically indicate the data that the first device can provide during the data collection process, or specifically indicate the existing data that the first device can provide. If the second information is used to indicate the data that the first device can provide during the data collection process, then the second information implicitly indicates the third mode; if the second information is used to indicate the existing data that the first device can provide, then the second information implicitly indicates the fourth mode.

[0179] Optionally, the first information includes at least one of the following:

[0180] the type of data that the first device needs to obtain;

[0181] a collection target of the data to be acquired by the first device;

[0182] a method for collecting data required by the first device;

[0183] The acquisition time of the data required to be acquired by the first device;

[0184] The number of sampling points of the data required to be acquired by the first device.

[0185] The type of data can be understood as the parameters that need to be collected, and the first device can determine the type of data based on specific data requirements. Taking the need for the first device to collect downlink measurement data (or downlink measurement data) as an example, the type of data may include RSRP, RSRPB, RSRQ, RSSI or SINR, etc. Taking the paging failure optimization scenario as an example, the type of data may include the terminal's mobile path, the cell information where the terminal resides, downlink RSRP / RSRQ / SINR or paging reception mechanism, etc. The type of data may also be different for different first devices.

[0186] The data collection target can be understood as the data collection area, such as the serving cell and the neighboring cell.

[0187] The data collection method, such as periodic triggering, event triggering, or request triggering.

[0188] The data collection time includes, for example, at least one of the collection start time, end time, time length, and collection time interval.

[0189] Including the above content in the first information helps the first device to obtain the data it needs.

[0190] Optionally, the second information includes at least one of the following:

[0191] the type of data that the first device can provide;

[0192] a collection target of data that can be provided by the first device;

[0193] a method for collecting data that can be provided by the first device;

[0194] the collection time of the data that can be provided by the first device;

[0195] The first device may provide the number of sampling points of data.

[0196] The data type can be understood as the data collection parameters.

[0197] The data collection target can be understood as the data collection area, such as the serving cell and the neighboring cell.

[0198] The data collection method, such as periodic triggering, event triggering, or request triggering.

[0199] The data collection time includes, for example, at least one of the collection start time, end time, time length, and collection time interval.

[0200] By including the above content in the second information, the second device is helped to know the situation in which data can be obtained, thereby promoting the cooperation between the second device and the first device and improving the data collection effect.

[0201] In some embodiments, the third information includes at least one of the following:

[0202] the type of reward that the first device can provide;

[0203] The number of rewards that the first device can provide.

[0204] Optionally, the types of rewards include at least one of the following: quality of service (QoS) guarantee, priority enhancement, network data acquisition, free traffic, free voice, free call charges, and free points.

[0205] Optionally, the amount of the reward includes at least one of the following: number of QoS guarantees, number of priority upgrades, number of network data acquisitions, amount of network data acquired, amount of free traffic, duration of free voice calls, amount of free call charges, and number of free points.

[0206] By including the above content in the third information, the second device is helped to know the situation in which the reward can be obtained, thereby promoting the collaboration between the second device and the first device and improving the data collection effect.

[0207] In some embodiments, the first device includes a network-side device, and the second device includes a terminal;

[0208] The type of data required to be acquired by the first device includes at least one of downlink measurement data and QoE information:

[0209] The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of active UEs in RRC_CONNECTED, and QoE abnormality reasons.

[0210] Among them, the downlink measurement data is provided by the UE, and the downlink measurement data may include at least one of the following: RSRP, Reference Signal Received Power per Branch (RSPRB), RSRQ, Received Signal Strength Indicator (RSSI), SINR, and downlink packet delay. The downlink packet delay includes at least one of the air interface packet delay (Average over-the-air interface packet delay), Radio Link Control (RLC) packet delay, and Packet Data Convergence Protocol (PDCP) packet delay. An example of air interface packet delay is the average air interface packet delay of each downlink radio bearer (such as a data radio bearer (DRB)) of the UE (i.e., the second device). An example of RLC packet delay is the average RLC packet delay of each downlink radio bearer of the UE. An example of PDCP packet delay is the average PDCP packet delay of each downlink radio bearer of the UE.

[0211] The uplink measurement data is provided by the network side device, and the uplink measurement data may include at least one of the following: RSRP, RSPRB, RSRQ, RSSI, SINR, and uplink packet delay. The uplink packet delay includes at least one of air interface packet delay, RLC packet delay, and PDCP packet delay. An example of air interface packet delay is the average air interface packet delay of each uplink radio bearer of the UE (i.e., the second device), or the average air interface packet delay of each uplink radio bearer of UEs located near the UE, or the uplink average air interface packet delay of all UEs in the cell served by the UE within nearly T time. An example of RLC packet delay is the average RLC packet delay of each uplink radio bearer of the UE, or the average RLC packet delay of each uplink radio bearer of UEs located near the UE, or the uplink average RLC packet delay of all UEs in the cell served by the UE within nearly T time. An example of PDCP packet delay is the average PDCP packet delay of each radio bearer in the uplink of the UE, or the average PDCP packet delay of each DRB in the uplink of UEs located near the UE, or the average uplink PDCP packet delay of all UEs in the UE serving cell within the last T time.

[0212] The downlink buffer size is provided by the network-side device and may include at least one of the following: Layer 2 (L2) buffer size, PDCP buffer size, and RLC buffer size. Taking the PDCP buffer size as an example, the PDCP buffer size may include: the average PDCP buffer size for all downlink bearers of the UE, the PDCP buffer size of a specific radio bearer (RB), or a list of PDCP buffer sizes for each radio bearer. For example, the PDCP buffer size list includes the following information: RB ID and PDCP buffer size.

[0213] The number of activated UEs in the RRC connected state is provided by the network side device, and the number of activated UEs in the RRC connected state includes at least one of the following: the average number of activated UEs in the RRC connected state in the uplink of a cell, the maximum number of activated UEs in the RRC connected state in the uplink of a cell, the average number of activated UEs in the RRC connected state in the downlink of a cell, the maximum number of activated UEs in the RRC connected state in the downlink of a cell, the average number of activated UEs in the RRC connected state in a cell, and the maximum number of activated UEs in the RRC connected state in a cell.

[0214] The reasons for QoE abnormalities are provided by network-side devices. These reasons include service (such as video, game, etc.) lags. Specifically, they include at least one of the following:

[0215] Application server overload;

[0216] The network has no downlink resource scheduling;

[0217] The network has no uplink resource scheduling;

[0218] Terminal demodulation or interference causes packet parsing failure;

[0219] The network side has a heavy business load.

[0220] In some embodiments, the first device includes a terminal, and the second device includes a network-side device;

[0221] The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason;

[0222] The data type provided by the first device during the data collection process includes at least one of downlink measurement data and QoE information.

[0223] The types of the above data can be found in the above description. To avoid repetition, they will not be described in detail.

[0224] In some embodiments, the above method further includes any of the following:

[0225] The first device receives a second message from the second device, where the second message is used to indicate rejection of the data collection request;

[0226] The first device receives a third message from the second device, where the third message is used to indicate acceptance of the data collection request.

[0227] After receiving the first message, the second device can determine whether to accept the data collection request from the first device. If the second device does not accept the request, one implementation is for the second device to not send a response, while another implementation is for the second device to send a rejection response, i.e., a second message. Accordingly, the first device receives the second message.

[0228] If the second device accepts or considers accepting the data collection request of the first device, the second device may send a third message. Accordingly, the first device receives the third message.

[0229] In some embodiments, the second message includes at least one of the following:

[0230] an identifier of the data collection request;

[0231] a second instruction, used to indicate rejection of the data collection request;

[0232] The fourth information is used to indicate the reason for rejecting the data collection request.

[0233] Exemplarily, the rejection reason indicated by the fourth information may include high network traffic load, UE privacy issues, and the like.

[0234] In some embodiments, the third message includes at least one of the following:

[0235] an identifier of the data collection request;

[0236] A third instruction, used to indicate acceptance of the data collection request;

[0237] Fifth information, used to indicate data that the second device needs to obtain;

[0238] The sixth information is used to indicate the reward that the second device expects to obtain.

[0239] That is, the second device may inform the first device of its data demand or reward demand, so that the second device can obtain the data or reward it needs.

[0240] Optionally, the fifth information includes at least one of the following:

[0241] the type of data that the second device needs to obtain;

[0242] a collection target of the data to be acquired by the second device;

[0243] a method for collecting data required by the second device;

[0244] the collection time of the data required to be acquired by the second device;

[0245] The number of sampling points of the data required to be acquired by the second device.

[0246] The above content included in the fifth information can be found in the aforementioned related instructions. To avoid repetition, it will not be elaborated on.

[0247] Including the above content in the fifth information helps the second device to obtain the data it needs.

[0248] Optionally, the sixth information includes at least one of the following:

[0249] the type of reward that the second device desires to obtain;

[0250] The amount of the reward that the second device expects to obtain.

[0251] The above content included in the sixth information can be found in the aforementioned related instructions. To avoid repetition, it will not be elaborated on.

[0252] By including the above content in the sixth information, it is helpful for the second device to obtain the reward it needs.

[0253] In some embodiments, the second device includes a network-side device, and the first device includes a terminal;

[0254] The type of data that the second device needs to obtain includes at least one of downlink measurement data and QoE information.

[0255] In some embodiments, the second device includes a terminal, and the first device includes a network-side device;

[0256] The type of data that the second device needs to obtain includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in RRC connected state, and QoE abnormality reasons.

[0257] For downlink measurement data, uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and the causes of QoE abnormalities, please refer to the aforementioned relevant descriptions. To avoid repetition, these will not be described in detail.

[0258] In some embodiments, after the first device receives the third message, the method further includes any one of the following:

[0259] The first device sends a fourth message to the second device, where the fourth message is used to indicate that a request from the second device is rejected;

[0260] The first device sends a fifth message to the second device, where the fifth message is used to indicate acceptance of the request of the second device.

[0261] After receiving the third message, the first device can determine whether to accept the request from the second device. If the first device does not accept, one implementation is for the first device to not send a response, and another implementation is for the first device to send a rejection response, i.e., the fourth message. Accordingly, the second device receives the fourth message.

[0262] If the first device accepts or considers accepting the request of the second device, the first device may send a fifth message. Accordingly, the second device receives the fifth message.

[0263] In some embodiments, the fourth message includes at least one of the following:

[0264] an identifier of the data collection request;

[0265] a fourth indication, used to indicate rejection of the request of the second device;

[0266] The seventh information is used to indicate the reason for rejecting the request of the second device.

[0267] Exemplarily, the rejection reason indicated by the seventh information may include high network service load, UE privacy issues, and the like.

[0268] In some embodiments, the fifth message includes at least one of the following:

[0269] an identifier of the data collection request;

[0270] a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection;

[0271] Eighth information, used to instruct the second device to perform data reporting configuration information;

[0272] Ninth information, used to indicate configuration information for receiving data by the second device;

[0273] The first data is existing data provided by the first device to the second device.

[0274] The eighth information may be understood as data reporting configuration information, and the second device may report the data required by the first device to the first device according to the eighth information.

[0275] The ninth information may be understood as data receiving configuration information, and the second device may receive the data required by the second device according to the ninth information.

[0276] In a case where the target mode includes the fourth mode, the first device may further carry the first data in the fifth message, that is, the first device provides the existing data to the second device through the fifth message.

[0277] For the fourth mode, a typical scenario is the paging failure optimization scenario. Paging failure optimization means that when data arrives, the network side device will initiate paging, but due to network side reasons or terminal side reasons (such as network deployment, paging configuration, signal quality, UE side processing capabilities, etc.), there is a paging failure (or paging loss). In this case, in order to confirm the specific cause of the paging failure, the network side device needs to obtain the relevant parameters required for paging performance optimization. For further explanation, the following takes paging failure optimization as an example to explain the first data and the data that the first device needs to obtain, wherein the first device is a network side device and the second device is a terminal.

[0278] In some embodiments, when paging of the second device fails, the first data includes at least one of the following:

[0279] paging identification;

[0280] An identifier of the first device, such as a gNB ID;

[0281] The identifier of the second device, for example, UE ID;

[0282] Identification of the paging area, such as the RAN-based notification area (RNA) ID, routing area (RA) ID, tracking area (TA) ID, and cell ID involved in the paging initiation;

[0283] Time information for sending paging messages, such as the time when the paging message is sent (such as the paging frame (PF), paging occasion (PO), physical downlink control channel (PDCCH) occasion, etc.), and the time period for sending the paging message;

[0284] a discontinuous reception (DRX) configuration or an extended DRX (eDRX) configuration of the second device;

[0285] Indication information of whether a paging optimization mechanism is applied, used to indicate whether a paging optimization mechanism is applied when sending a paging message. The paging optimization mechanism includes, for example, sending a Paging Early Indication (PEI) or a Low-Power Wake-up Signal (LP-WUS);

[0286] paging message sending mechanism indication information, used to indicate the paging message sending mechanism, the paging message sending mechanism includes, for example, RAN paging or core network paging;

[0287] When sending the paging message, the first device expects the RRC state of the second device, for example, an idle state or an inactive state.

[0288] Furthermore, the type of data required to be acquired by the first device includes at least one of the following:

[0289] The movement path of the second device, for example, the latitude, longitude, and altitude of multiple points on the path;

[0290] The paging reception mechanism of the second device, for example: whether to monitor PEI or LP-WUS, PEI grouping information, LP-WUS grouping information;

[0291] at least one of a time and a duration for the second device to receive the paging;

[0292] at least one of a time and a duration during which the second device does not receive a paging call;

[0293] The RRC state of the second device, for example, IDLE or inactive;

[0294] Downlink measurement data of the second device, such as RSRP / RSRQ / SINR;

[0295] An identifier of the cell where the second device resides, for example, a cell ID;

[0296] at least one of a time and a duration during which the second device resides in the cell;

[0297] Whether the second device is out of service coverage;

[0298] at least one of a time and a duration during which the second device is not covered by a service area;

[0299] an identifier of the last cell where the second device resided before it left the service area;

[0300] The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

[0301] In this implementation, in the event of a paging failure, the exchange of the above data enables the first device to obtain relevant parameters required for paging performance optimization, thereby facilitating the first device to identify the specific cause of the paging failure.

[0302] In some embodiments, after the first device receives the third message, the method further includes:

[0303] The first device sends tenth information to the third device, where the tenth information is used to indicate a reward event.

[0304] Optionally, the tenth information includes at least one of the following:

[0305] an identifier of the second device;

[0306] Type of reward;

[0307] The number of rewards.

[0308] Optionally, when the type of the reward includes free traffic, free voice, free call charges or free points, the third device includes a billing function.

[0309] Optionally, when the type of the reward includes QoS guarantee, priority enhancement or network data acquisition, the third device includes at least one of a wireless access network device and a policy control function.

[0310] That is, the first device sends reward event indication information to the billing function, the wireless access network, or the policy control function. The reward indication information includes the UE identifier, reward content, and reward amount. For example, if the reward content is traffic, voice, call charges, or points, the first device sends the reward event indication information to the billing function. If the reward content is data acquisition, priority increase, or QoS guarantee, the first device sends the reward event indication information to the wireless access network or the policy control function.

[0311] Through the above implementation, it is possible to ensure that the second device obtains the corresponding reward.

[0312] In some embodiments, before the first device sends the first message to the second device, the method further includes:

[0313] The first device receives eleventh information from the second device, where the eleventh information is used to indicate a data collection mode supported by the second device.

[0314] That is, the second device reports capability information to the first device, indicating that the second device supports the first mode, the second mode, the third mode, the fourth mode, or the fifth mode. In this way, when the first device needs to obtain data from the second device, it can select an appropriate data collection mode based on the modes supported by the second device.

[0315] The above is a method embodiment on the first device side. The following describes a method embodiment on the second device side.

[0316] FIG5 is a flow chart of a data collection method provided by an embodiment of the present application. As shown in FIG5 , the data collection method includes the following steps:

[0317] Step 501: A second device receives a first message from a first device, where the first message includes at least one data collection request;

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

[0319] an identifier of the data collection request;

[0320] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0321] First information, used to indicate data that the first device needs to obtain;

[0322] second information, used to indicate data that the first device can provide;

[0323] third information, used to indicate a reward that can be provided by the first device;

[0324] The target mode includes any of the following:

[0325] a first mode, in which the first device obtains data from the second device;

[0326] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0327] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0328] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0329] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0330] Optionally, the data that can be provided by the first device indicated by the second information includes at least one of the following:

[0331] data that the first device can provide during the data collection process;

[0332] The first device may provide existing data.

[0333] Optionally, the first information includes at least one of the following:

[0334] the type of data that the first device needs to obtain;

[0335] a collection target of the data to be acquired by the first device;

[0336] a method for collecting data required by the first device;

[0337] The acquisition time of the data required to be acquired by the first device;

[0338] The number of sampling points of the data required to be acquired by the first device.

[0339] Optionally, the type of data that the first device can provide;

[0340] a collection target of data that can be provided by the first device;

[0341] a method for collecting data that can be provided by the first device;

[0342] the collection time of the data that can be provided by the first device;

[0343] The first device may provide the number of sampling points of data.

[0344] Optionally, the third information includes at least one of the following:

[0345] the type of reward that the first device can provide;

[0346] The number of rewards that the first device can provide.

[0347] Optionally, the method further includes any of the following:

[0348] The second device sends a second message to the first device, where the second message is used to indicate that the data collection request is rejected;

[0349] The second device sends a third message to the first device, where the third message is used to indicate acceptance of the data collection request.

[0350] Optionally, the second message includes at least one of the following:

[0351] an identifier of the data collection request;

[0352] a second instruction, used to indicate rejection of the data collection request;

[0353] The fourth information is used to indicate the reason for rejecting the data collection request.

[0354] Optionally, the third message includes at least one of the following:

[0355] an identifier of the data collection request;

[0356] A third instruction, used to indicate acceptance of the data collection request;

[0357] Fifth information, used to indicate data that the second device needs to obtain;

[0358] The sixth information is used to indicate the reward that the second device expects to obtain.

[0359] Optionally, the fifth information includes at least one of the following:

[0360] the type of data that the second device needs to obtain;

[0361] a collection target of the data to be acquired by the second device;

[0362] a method for collecting data required by the second device;

[0363] the collection time of the data required to be acquired by the second device;

[0364] The number of sampling points of the data required to be acquired by the second device.

[0365] Optionally, the sixth information includes at least one of the following:

[0366] the type of reward that the second device desires to obtain;

[0367] The amount of the reward that the second device expects to obtain.

[0368] Optionally, after the second device sends the third message to the first device, the method further includes any one of the following:

[0369] The second device receives a fourth message from the first device, where the fourth message is used to indicate that a request from the second device is rejected;

[0370] The second device receives a fifth message from the first device, where the fifth message is used to indicate acceptance of the request of the second device.

[0371] Optionally, the fourth message includes at least one of the following:

[0372] an identifier of the data collection request;

[0373] a fourth indication, used to indicate rejection of the request of the second device;

[0374] The seventh information is used to indicate the reason for rejecting the request of the second device.

[0375] Optionally, the fifth message includes at least one of the following:

[0376] an identifier of the data collection request;

[0377] a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection;

[0378] Eighth information, used to instruct the second device to perform data reporting configuration information;

[0379] Ninth information, used to indicate configuration information for receiving data by the second device;

[0380] The first data is existing data provided by the first device to the second device.

[0381] Optionally, the types of rewards include at least one of the following: quality of service (QoS) guarantee, priority enhancement, network data acquisition, free traffic, free voice, free call charges, and free points.

[0382] Optionally, the amount of the reward includes at least one of the following: number of QoS guarantees, number of priority upgrades, number of network data acquisitions, amount of network data acquired, amount of free traffic, duration of free voice calls, amount of free call charges, and number of free points.

[0383] Optionally, in the case where paging of the second device fails, the first data includes at least one of the following:

[0384] paging identification;

[0385] an identifier of the first device;

[0386] an identifier of the second device;

[0387] Identification of the paging area;

[0388] Time information for sending paging messages;

[0389] a discontinuous reception (DRX) configuration or an extended DRX configuration of the second device;

[0390] Indication of whether to apply the paging optimization mechanism;

[0391] Instructions for the paging message sending mechanism;

[0392] When sending a paging message, the first device expects the second device to have a radio resource control (RRC) state; or

[0393] The type of data that the first device needs to obtain includes at least one of the following:

[0394] a movement path of the second device;

[0395] a paging receiving mechanism of the second device;

[0396] at least one of a time and a duration for the second device to receive the paging;

[0397] at least one of a time and a duration during which the second device does not receive a paging call;

[0398] an RRC state of the second device;

[0399] downlink measurement data of the second device;

[0400] an identifier of a cell in which the second device resides;

[0401] at least one of a time and a duration during which the second device resides in the cell;

[0402] Whether the second device is out of service coverage;

[0403] at least one of a time and a duration during which the second device is not covered by a service area;

[0404] an identifier of the last cell where the second device resided before it left the service area;

[0405] The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

[0406] Optionally, the first device includes a network-side device, and the second device includes a terminal;

[0407] The type of data that the first device needs to obtain includes at least one of downlink measurement data and quality of service (QoE) information:

[0408] The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in RRC connected state, and QoE abnormality reasons.

[0409] Optionally, the first device includes a terminal, and the second device includes a network-side device;

[0410] The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason;

[0411] The data type provided by the first device during the data collection process includes at least one of downlink measurement data and quality of service (QoE) information.

[0412] Optionally, the method further includes:

[0413] The second device sends eleventh information to the first device, where the eleventh information is used to indicate a data collection mode supported by the second device.

[0414] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 4, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0415] In order to better understand the embodiments of the present application, specific embodiments are provided below for illustrative purposes.

[0416] Example 1: Data collection based on the second mode or the third mode

[0417] This embodiment takes the second mode or the third mode as an example, assuming that the first device is a network-side device (such as a radio access network or core network function) and the second device is a UE. The relevant steps are briefly described as follows:

[0418] Step 1: A first device sends a first message, where the first message is used for data request and includes at least one of the following:

[0419] The first indication is used to indicate a data collection mode, which is the second mode or the third mode in this embodiment.

[0420] Request ID, used to uniquely identify a data collection request.

[0421] The first information includes at least one collection parameter / content, which is used to indicate the parameters that the first device needs to collect.

[0422] The second information includes at least one collection parameter / content, which is used to indicate the parameters that the first device can share with the second device during this data collection process.

[0423] For example, the network requests the UE to collect downlink measurement data, and the network shares uplink measurement data for the UE (eg, uplink measurement data collected by the network during the time interval of UE data collection).

[0424] In the first information, the acquisition parameters may include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, and SINR.

[0425] The first information may further include a collection target, which is used to instruct the UE which cells to collect data from, including at least one of the following:

[0426] A sixth indication is used to indicate whether to collect only the serving cell data, or only the neighboring cell data, or both the serving cell and the neighboring cell data. For example, for the neighboring cell data, the network selects which neighboring cell data to send to the terminal based on the implementation;

[0427] Cell Global Identifier (CGI) (including Public Land Mobile Network (PLMN) ID and Cell ID);

[0428] Physical cell identifier (PCI);

[0429] Carrier frequency information;

[0430] Tracking Area Code (TAC);

[0431] Tracking area identify (TAI) (including PLMN ID and TAC).

[0432] The first information may also include a collection method, which may include at least one of network request triggering, periodic triggering, and event triggering. For periodic triggering, the first information may also include a time interval, which may be expressed in units of hours, minutes, seconds, milliseconds, microseconds, frames, subframes, symbols, or time slots. For event triggering, the first information may also include at least one of a triggering event and a triggering time associated with the triggering event.

[0433] The first information may further include the number of sampling points.

[0434] In the second information, the acquisition parameters may include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, SINR, Radio Resource Status (used to indicate the PRB usage in each cell, each SSB area and each switching of MIMO in the downlink and uplink, and indicates the usage of PDCCH CCE for downlink and uplink scheduling (indicates the usage of the PRBs per cell for MIMO, per SSB area, and per slice for all traffic in Downlink and Uplink and the usage of PDCCH CCEs for Downlink and Uplink scheduling)), Physical Resource Block (PRB) usage, PDCCH Control Channel Element (CCE) usage for uplink scheduling, PDCCH CCE usage for downlink scheduling, the number of users in RRC connected state / inactive state, the ratio of the number of users in RRC connected state / inactive state to the maximum number of users accommodated, and uplink / downlink throughput.

[0435] The second information may further include a collection target, which is used to instruct the network to collect data of which cells, such as CGI (including PLMN ID and Cell ID), PCI, etc.

[0436] The second information may further include a collection time, including at least one of a start time, an end time, a time length, and a collection time interval of the collection.

[0437] The second information may further include the number of sampling points.

[0438] Note: The first message can be sent to a designated UE or to multiple UEs via a broadcast message, etc., thereby soliciting UEs willing to provide data.

[0439] Step 2: The second device receives the first message and determines whether to accept the data collection request. If not, one method is to not send a response, or another method is to send a rejection response, optionally including a rejection reason. If the second device accepts or considers accepting the data collection request, the second device sends a third message. The third message includes at least one of the following:

[0440] A third indication is used to indicate acceptance of the data collection request. If there are multiple data collection requests, the acceptance indication may include a request ID, indicating acceptance of the data collection request with the request ID;

[0441] The fifth information includes at least one collection parameter / content, which is used to indicate the parameters that the second device needs to collect in this data collection.

[0442] When the first message contains the second information, one way is that the fifth information indication is the same as the second information, indicating that the second device needs the data indicated by the second information; another way is that the fifth information indicates a subset of the second information, indicating that the second device only needs the subset data indicated by the fifth information.

[0443] When the first message does not include the second information, the fifth information may indicate the required data through collection parameters, collection targets or collection time.

[0444] Step 3: The first device receives the third message. The first device determines whether to accept the data requested in the third message. Optionally, the first device sends a fourth message or a fifth message.

[0445] The fourth message includes:

[0446] A fourth indication, used to indicate rejection of the data request from the second device. If there are multiple data collection requests, the fourth indication may include a request ID, used to indicate rejection of the data collection request with the request ID;

[0447] Reason for rejection.

[0448] The fifth message includes:

[0449] The fifth indication is used to indicate acceptance of the data request of the second device. If there are multiple data collection requests, the fifth indication may include a request ID, which is used to indicate acceptance of the data collection request with the request ID.

[0450] Step 4: If the first device accepts the data requested by the second device, the first device sends a request to trigger data collection, or sends a data reporting configuration to the UE, or sends a data receiving configuration to the UE. The data reporting configuration is used by the UE to report data required by the network. The data receiving configuration is used by the UE to receive network data required by the UE.

[0451] Example 2: Data collection based on the second mode or the fourth mode

[0452] This embodiment uses the second mode or the fourth mode as an example, assuming that the first device is the network and the second device is the UE. For further explanation, this embodiment uses paging failure optimization as an example. The relevant steps are briefly described as follows:

[0453] Step 1: A first device sends a first message, where the first message is used for data request and includes at least one of the following:

[0454] The first indication is used to indicate a data collection mode, which is the second mode or the fourth mode in this embodiment.

[0455] Request ID, used to uniquely identify a data collection request.

[0456] The first information includes at least one collection parameter / content, which is used to indicate the parameters that the first device needs to collect.

[0457] The second information includes at least one collection parameter / content, which is used to indicate the parameter / content provided by the first device as an exchange in this data collection.

[0458] Take paging failure optimization as an example.

[0459] The first information may include acquisition parameters and time information, where the time information indicates the acquisition time required for the acquisition parameters. The acquisition parameters include at least one of the following:

[0460] The terminal's movement path, such as the latitude, longitude, and altitude of multiple points along the path;

[0461] Information about the cell you stay in, such as the cell ID, the duration and time period of your stay in each cell;

[0462] Downlink RSRP / RSRQ / SINR;

[0463] Paging reception mechanism, whether to monitor PEI or LP-WUS, PEI group information, LP-WUS group information;

[0464] The RRC state of the terminal, such as IDLE or inactive;

[0465] The timestamp, time period, or paging time corresponding to the above information;

[0466] Whether it is out of service area / out of coverage;

[0467] Time and time period when not in service area / coverage range;

[0468] The time period when no paigng is received;

[0469] The last resident cell before the out-of-service area / coverage area;

[0470] The first cell to camp on when returning to the service area / coverage area.

[0471] The second information may include at least one of the following: acquisition parameters, acquisition time, number of sampling points, etc. The acquisition parameters may include at least one of the following:

[0472] RNA ID, RA ID, TA ID, gNB ID, cell ID, and UE ID involved in paging initiation;

[0473] The time (such as PF, PO, PDCCH occasion, etc.) and time period for sending paging messages;

[0474] paging identification;

[0475] UE DRX / eDRX configuration;

[0476] Whether paging optimization mechanisms, such as PEI and LP-WUS, are applied when sending paging messages;

[0477] The network's expected UE RRC state (e.g., IDLE or inactive) when sending a paging message;

[0478] The corresponding sending mechanism of the paging message (such as RAN paging or core network paging).

[0479] Note: The first message can be sent to a designated UE or to multiple UEs via a broadcast message, etc., thereby soliciting UEs willing to provide data.

[0480] Step 2: The second device receives the first message and determines whether to accept the data collection request. If not, one method is to not send a response, or another method is to send a rejection response, optionally including a rejection reason. If the second device accepts or considers accepting the data collection request, the second device sends a third message. The third message includes at least one of the following:

[0481] The third instruction is used to indicate acceptance of the data collection request. If there are multiple data collection requests, the acceptance instruction may include a request ID, which is used to indicate acceptance of the data collection request with the request ID.

[0482] Step 3: The first device receives the third message. The first device sends the data indicated by the second message to the second device, or sends a request to trigger data collection, or sends a data reporting configuration to the UE, or sends a data receiving configuration to the UE. The data reporting configuration is used by the UE to report data required by the network. The data receiving configuration is used by the UE to receive network data required by the UE.

[0483] Example 3: Data collection based on the second mode or the fifth mode

[0484] This embodiment takes the second mode or the fifth mode as an example, assuming that the first device is a network-side device and the second device is a UE. The relevant steps are briefly described as follows:

[0485] Step 1: A first device sends a first message, where the first message is used for data request and includes at least one of the following:

[0486] The first indication is used to indicate a data collection mode, which is the second mode or the fifth mode in this embodiment.

[0487] Request ID, used to uniquely identify a data collection request.

[0488] The first information includes at least one collection parameter / content, which is used to indicate the parameters that the first device needs to collect.

[0489] The third information includes at least one parameter / content, and is used to indicate the reward information provided by the first device in this data collection.

[0490] Take the example where the network requests the UE to collect downlink measurement data and the network provides a reward to the UE.

[0491] In the first information, the acquisition parameters may include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, and SINR.

[0492] The first information may further include a collection target, which is used to instruct the UE which cells to collect data from, including at least one of the following:

[0493] A sixth indication is used to indicate whether to collect only the serving cell data, or only the neighboring cell data, or both the serving cell and the neighboring cell data. For example, for the neighboring cell data, the network selects which neighboring cell data to send to the terminal based on the implementation;

[0494] CGI (including PLMN ID and Cell ID);

[0495] PCI;

[0496] Carrier frequency information;

[0497] TAC;

[0498] TAI (including PLMN ID and TAC).

[0499] The first information may also include a collection method, which may include at least one of network request triggering, periodic triggering, and event triggering. For periodic triggering, the first information may also include a time interval, which may be expressed in units of hours, minutes, seconds, milliseconds, microseconds, frames, subframes, symbols, or time slots. For event triggering, the first information may also include at least one of a triggering event and a triggering time associated with the triggering event.

[0500] The first information may further include the number of sampling points.

[0501] The fourth information may include at least one of the following: reward content and reward amount. The reward content includes at least one of the following: QoS guarantee, network data acquisition, priority increase, traffic, voice, points, etc. The reward amount includes the number of QoS guarantee times, network data acquisition times, priority increase times, call duration, traffic amount (such as 100MB of traffic), or point amount (such as 100 points).

[0502] Note: The first message can be sent to a designated UE or to multiple UEs via a broadcast message, etc., thereby soliciting UEs willing to provide data.

[0503] Step 2: The second device receives the first message and determines whether to accept the data collection request. If not, one method is to not send a response, or another method is to send a rejection response, optionally including a rejection reason. If the second device accepts or considers accepting the data collection request, the second device sends a third message. The third message includes at least one of the following:

[0504] A third indication is used to indicate acceptance of the data collection request. If there are multiple data collection requests, the acceptance indication may include a request ID, indicating acceptance of the data collection request with the request ID;

[0505] The sixth information includes at least one collection parameter / content, which is used to indicate the reward information that the second device expects to obtain in this data collection.

[0506] When the first message contains the third information, one way is that the sixth information indication is the same as the third information, indicating that the second device agrees with the reward content and quantity indicated by the third information; another way is that the sixth information indicates the reward content and quantity required by the second device. When using this method, the sixth information is different from the third information, and the reward content and / or reward quantity may be different.

[0507] When the first message does not include the third information, the sixth information may indicate the required reward through reward content or reward amount.

[0508] Step 3: The first device receives the third message. The first device determines whether to accept the reward requested in the third message. Optionally, the first device sends a fourth message or a fifth message.

[0509] The fourth message includes:

[0510] a fourth instruction, configured to indicate rejection of the reward request of the second device. If there are multiple data collection requests, the fourth instruction may include a request ID, configured to indicate rejection of the data collection request of the request ID;

[0511] Reason for rejection.

[0512] The fifth message includes:

[0513] The fifth instruction is used to indicate that the reward request of the second device is accepted. If there are multiple data collection requests, the fifth instruction may include a request ID, which is used to indicate that the data collection request of the request ID is accepted.

[0514] Step 4: If the first device accepts the reward requested by the second device, the first device sends a request to trigger data collection, or sends a data reporting configuration to the UE. The data reporting configuration is used by the UE to report data required by the network.

[0515] Step 5: The first device sends a reward event to the billing function or network function node. The reward event includes the UE identifier, reward content, or reward amount. If the reward content is traffic, voice, call charges, or points, the first device sends the reward event to the billing function. If the reward content is data acquisition, priority increase, or QoS guarantee, the first device sends the reward event to the radio access network or policy control function.

[0516] Embodiment 4: UE data collection based on the second mode, the third mode, or the fourth mode

[0517] This embodiment takes the second mode, the third mode, or the fourth mode as an example, assuming that the first device is a UE and the second device is a network-side device. The relevant steps are briefly described as follows:

[0518] Step 1: A first device sends a first message, where the first message is used for data request and includes at least one of the following:

[0519] The first indication is used to indicate a data collection mode, which in this embodiment is the second mode, the third mode, or the fourth mode.

[0520] Request ID, used to uniquely identify a data collection request.

[0521] The first information includes at least one collection parameter / content, which is used to indicate the parameters that the first device needs to collect.

[0522] The first message may also include second information. Specifically, if the second or third mode is selected, the second information includes at least one collection parameter / content, indicating the parameters that the first device can share with the second device during this data collection process. If the second or fourth mode is selected, the second information includes at least one collection parameter / content, indicating the parameters / content that the first device provides in exchange during this data collection process.

[0523] For example, the UE requests the network to collect uplink measurement data, and the UE shares downlink measurement data with the network (eg, downlink measurement data collected by the UE during a time interval for network data collection).

[0524] In the first information, the acquisition parameters may include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, and SINR.

[0525] The first information may also include a collection target, which is used to instruct the network which cells to collect data, including at least one of the following: CGI (including PLMN ID and Cell ID), PCI, carrier frequency information, TAC, TAI (including PLMN ID and TAC).

[0526] The first information may also include a collection method, which may include at least one of UE request triggering, periodic triggering, and event triggering. For periodic triggering, the first information may also include a time interval, which may be expressed in hours, minutes, seconds, milliseconds, microseconds, frames, subframes, symbols, or time slots. For event-triggered collection, the first information may also include at least one of a triggering event and a triggering time associated with the triggering event (e.g., UE downlink traffic is less than threshold 1, downlink RSRP is greater than threshold 2, and duration is greater than threshold 3).

[0527] The first information may further include the number of sampling points.

[0528] In the second information, the acquisition parameters may include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, SINR, and Radio Resource Status.

[0529] The second information may further include a collection target, which is used to instruct the network to collect data of which cells, such as CGI (including PLMN ID and Cell ID), PCI, etc.

[0530] The second information may further include a collection time, including at least one of a start time, an end time, a time length, and a collection time interval of the collection.

[0531] The second information may further include the number of sampling points.

[0532] Take paging failure optimization as an example.

[0533] The first information may include at least one of the following: acquisition parameters, acquisition time, number of sampling points, etc. The acquisition parameters may include at least one of the following:

[0534] RNA ID, RA ID, TA ID, gNB ID, cell ID, and UE ID involved in paging initiation;

[0535] The time (such as PF, PO, PDCCH occasion, etc.) and time period for sending paging messages;

[0536] paging identification;

[0537] UE DRX / eDRX configuration;

[0538] Whether paging optimization mechanisms, such as PEI and LP-WUS, are applied when sending paging messages;

[0539] The network's expected UE RRC state (e.g., IDLE or inactive) when sending a paging message;

[0540] The corresponding sending mechanism of the paging message (such as RAN paging or core network paging).

[0541] The second information may include acquisition parameters and time information, where the time information is used to indicate the acquisition time required for the acquisition parameters.

[0542] The acquisition parameters include at least one of the following:

[0543] The terminal's movement path, such as the latitude, longitude, and altitude of multiple points along the path;

[0544] Information about the cell you stay in, such as the cell ID, the duration and time period of your stay in each cell;

[0545] Downlink RSRP / RSRQ / SINR;

[0546] Paging reception mechanism, whether to monitor PEI or LP-WUS, PEI group information, LP-WUS group information;

[0547] The RRC state of the terminal, such as IDLE or inactive;

[0548] The timestamp, time period, or paging time corresponding to the above information;

[0549] Whether it is out of service area / out of coverage;

[0550] Time and time period when not in service area / coverage range;

[0551] The time period when no paigng is received;

[0552] The last resident cell before the out-of-service area / coverage area;

[0553] The first cell to camp on when returning to the service area / coverage area.

[0554] Step 2: The second device receives the first message and determines whether to accept the data collection request. If not, one method is to not send a response, or another method is to send a rejection response, optionally including a rejection reason. If the second device accepts or considers accepting the data collection request, the second device sends a third message. The third message includes at least one of the following:

[0555] The third instruction is used to indicate acceptance of the data collection request. If there are multiple data collection requests, the acceptance instruction may include a request ID, which is used to indicate acceptance of the data collection request with the request ID.

[0556] When the mode in the first message is the second mode or the third mode, the third message may further include fifth information, where the fifth information includes at least one collection parameter / content, which is used to indicate the parameters that the second device needs to collect in this data collection.

[0557] Step 3: The first device receives the third message. The first device determines whether to accept the data requested in the third message. Optionally, the first device sends a fourth message or a fifth message.

[0558] The fourth message includes:

[0559] A fourth indication, used to indicate rejection of the data request from the second device. If there are multiple data collection requests, the fourth indication may include a request ID, used to indicate rejection of the data collection request with the request ID;

[0560] Reason for rejection.

[0561] The fifth message includes:

[0562] The fifth indication is used to indicate acceptance of the data request of the second device. If there are multiple data collection requests, the fifth indication may include a request ID, which is used to indicate acceptance of the data collection request with the request ID.

[0563] Step 4: If the first device accepts the data requested by the second device, it sends a request to trigger data collection. In this case, the first device is the UE, and the second device is the network. The first device also needs to report the data provided by the UE according to the data reporting configuration sent by the second device, and the first device also needs to receive the data requested by the UE according to the data reception configuration sent by the second device.

[0564] In summary, in the embodiments of the present application, the network-side device or the UE can obtain the data they need in a single data collection, or the UE can obtain the reward corresponding to the data. The embodiments of the present application can not only facilitate the UE to obtain network data, but also facilitate the network-side device to obtain UE data. In this way, through the diversified data collection modes of data sharing, data exchange, or data rewards, the network-side device and the UE can achieve collaboration and win-win in data collection.

[0565] The data collection method provided in the embodiment of the present application can be executed by a data collection device. In the embodiment of the present application, the data collection device provided in the embodiment of the present application is described by taking the data collection method executed by the data collection device as an example.

[0566] 6 , the present invention also provides a data collection device. As shown in FIG6 , the data collection device 600 includes:

[0567] A first sending unit 601 is configured to send a first message to a second device, where the first message includes at least one data collection request;

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

[0569] an identifier of the data collection request;

[0570] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0571] First information, used to indicate data that the first device needs to obtain;

[0572] second information, used to indicate data that the first device can provide;

[0573] third information, used to indicate a reward that can be provided by the first device;

[0574] The target mode includes any of the following:

[0575] a first mode, in which the first device obtains data from the second device;

[0576] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0577] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0578] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0579] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0580] Optionally, the data that can be provided by the first device indicated by the second information includes at least one of the following:

[0581] data that the first device can provide during the data collection process;

[0582] The first device may provide existing data.

[0583] Optionally, the first information includes at least one of the following:

[0584] the type of data that the first device needs to obtain;

[0585] a collection target of the data to be acquired by the first device;

[0586] a method for collecting data required by the first device;

[0587] The acquisition time of the data required to be acquired by the first device;

[0588] The number of sampling points of the data required to be acquired by the first device.

[0589] Optionally, the second information includes at least one of the following:

[0590] the type of data that the first device can provide;

[0591] a collection target of data that can be provided by the first device;

[0592] a method for collecting data that can be provided by the first device;

[0593] the collection time of the data that can be provided by the first device;

[0594] The first device may provide the number of sampling points of data.

[0595] Optionally, the third information includes at least one of the following:

[0596] the type of reward that the first device can provide;

[0597] The amount of the reward that the first device can provide.

[0598] Optionally, the device further includes a first receiving unit, configured to:

[0599] receiving a second message from the second device, wherein the second message is used to indicate rejection of the data collection request;

[0600] A third message is received from the second device, where the third message is used to indicate acceptance of the data collection request.

[0601] Optionally, the second message includes at least one of the following:

[0602] an identifier of the data collection request;

[0603] a second instruction, used to indicate rejection of the data collection request;

[0604] The fourth information is used to indicate the reason for rejecting the data collection request.

[0605] Optionally, the third message includes at least one of the following:

[0606] an identifier of the data collection request;

[0607] A third instruction, used to indicate acceptance of the data collection request;

[0608] Fifth information, used to indicate data that the second device needs to obtain;

[0609] The sixth information is used to indicate the reward that the second device expects to obtain.

[0610] Optionally, the fifth information includes at least one of the following:

[0611] the type of data that the second device needs to obtain;

[0612] a collection target of the data to be acquired by the second device;

[0613] a method for collecting data required by the second device;

[0614] the collection time of the data required to be acquired by the second device;

[0615] The number of sampling points of the data required to be acquired by the second device.

[0616] Optionally, the sixth information includes at least one of the following:

[0617] the type of reward that the second device desires to obtain;

[0618] The amount of the reward that the second device expects to obtain.

[0619] Optionally, the apparatus further includes a second sending unit, configured to:

[0620] sending a fourth message to the second device, where the fourth message is used to indicate that the request of the second device is rejected;

[0621] A fifth message is sent to the second device, where the fifth message is used to indicate acceptance of the request of the second device.

[0622] Optionally, the fourth message includes at least one of the following:

[0623] an identifier of the data collection request;

[0624] a fourth indication, used to indicate rejection of the request of the second device;

[0625] The seventh information is used to indicate the reason for rejecting the request of the second device.

[0626] Optionally, the fifth message includes at least one of the following:

[0627] an identifier of the data collection request;

[0628] a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection;

[0629] Eighth information, used to instruct the second device to perform data reporting configuration information;

[0630] Ninth information, used to indicate configuration information for receiving data by the second device;

[0631] The first data is existing data provided by the first device to the second device.

[0632] Optionally, the device further comprises:

[0633] The third sending unit is used to send tenth information to the third device, where the tenth information is used to indicate a reward event.

[0634] Optionally, the tenth information includes at least one of the following:

[0635] an identifier of the second device;

[0636] Type of reward;

[0637] The number of rewards.

[0638] Optionally, the types of rewards include at least one of the following: quality of service (QoS) guarantee, priority enhancement, network data acquisition, free traffic, free voice, free call charges, and free points.

[0639] Optionally, the amount of the reward includes at least one of the following: number of QoS guarantees, number of priority upgrades, number of network data acquisitions, amount of network data acquired, amount of free traffic, duration of free voice calls, amount of free call charges, and number of free points.

[0640] Optionally, when the type of the reward includes free traffic, free voice, free call charges or free points, the third device includes a billing function.

[0641] Optionally, when the type of the reward includes QoS guarantee, priority enhancement or network data acquisition, the third device includes at least one of a wireless access network device and a policy control function.

[0642] Optionally, in the case where paging of the second device fails, the first data includes at least one of the following:

[0643] paging identification;

[0644] an identifier of the first device;

[0645] an identifier of the second device;

[0646] Identification of the paging area;

[0647] Time information for sending paging messages;

[0648] a discontinuous reception (DRX) configuration or an extended DRX configuration of the second device;

[0649] Indication of whether to apply the paging optimization mechanism;

[0650] Instructions for the paging message sending mechanism;

[0651] When sending a paging message, the first device expects the second device to have a radio resource control (RRC) state; or

[0652] The type of data that the first device needs to obtain includes at least one of the following:

[0653] a movement path of the second device;

[0654] a paging receiving mechanism of the second device;

[0655] at least one of a time and a duration for the second device to receive the paging;

[0656] at least one of a time and a duration during which the second device does not receive a paging call;

[0657] an RRC state of the second device;

[0658] downlink measurement data of the second device;

[0659] an identifier of a cell in which the second device resides;

[0660] at least one of a time and a duration during which the second device resides in the cell;

[0661] Whether the second device is out of service coverage;

[0662] at least one of a time and a duration during which the second device is not covered by a service area;

[0663] an identifier of the last cell where the second device resided before it left the service area;

[0664] The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

[0665] Optionally, the first device includes a network-side device, and the second device includes a terminal;

[0666] The type of data required to be acquired by the first device includes at least one of downlink measurement data and quality of service (QoE) information;

[0667] The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in RRC connected state, and QoE abnormality reasons.

[0668] Optionally, the first device includes a terminal, and the second device includes a network-side device;

[0669] The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason;

[0670] The data type provided by the first device during the data collection process includes at least one of downlink measurement data and quality of service (QoE) information.

[0671] Optionally, the device further comprises:

[0672] The second receiving unit is configured to receive eleventh information from the second device, where the eleventh information is used to indicate a data collection mode supported by the second device.

[0673] The data collection device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0674] The data collection device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0675] 7 , an embodiment of the present application further provides a data collection device. As shown in FIG7 , the data collection device 700 includes:

[0676] A first receiving unit 701 is configured to receive a first message from a first device, where the first message includes at least one data collection request;

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

[0678] an identifier of the data collection request;

[0679] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0680] First information, used to indicate data that the first device needs to obtain;

[0681] second information, used to indicate data that the first device can provide;

[0682] third information, used to indicate a reward that can be provided by the first device;

[0683] The target mode includes any of the following:

[0684] a first mode, in which the first device obtains data from the second device;

[0685] a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device;

[0686] a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process;

[0687] a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device;

[0688] A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

[0689] Optionally, the data that can be provided by the first device indicated by the second information includes at least one of the following:

[0690] data that the first device can provide during the data collection process;

[0691] The first device may provide existing data.

[0692] Optionally, the first information includes at least one of the following:

[0693] the type of data that the first device needs to obtain;

[0694] a collection target of the data to be acquired by the first device;

[0695] a method for collecting data required by the first device;

[0696] The acquisition time of the data required to be acquired by the first device;

[0697] The number of sampling points of the data required to be acquired by the first device.

[0698] Optionally, the type of data that the first device can provide;

[0699] a collection target of data that can be provided by the first device;

[0700] a method for collecting data that can be provided by the first device;

[0701] the collection time of the data that can be provided by the first device;

[0702] The first device may provide the number of sampling points of data.

[0703] Optionally, the third information includes at least one of the following:

[0704] the type of reward that the first device can provide;

[0705] The amount of the reward that the first device can provide.

[0706] Optionally, the apparatus further includes a first sending unit, configured to:

[0707] sending a second message to the first device, where the second message is used to indicate rejection of the data collection request;

[0708] A third message is sent to the first device, where the third message is used to indicate acceptance of the data collection request.

[0709] Optionally, the second message includes at least one of the following:

[0710] an identifier of the data collection request;

[0711] a second instruction, used to indicate rejection of the data collection request;

[0712] The fourth information is used to indicate the reason for rejecting the data collection request.

[0713] Optionally, the third message includes at least one of the following:

[0714] an identifier of the data collection request;

[0715] A third instruction, used to indicate acceptance of the data collection request;

[0716] Fifth information, used to indicate data that the second device needs to obtain;

[0717] The sixth information is used to indicate the reward that the second device expects to obtain.

[0718] Optionally, the fifth information includes at least one of the following:

[0719] the type of data that the second device needs to obtain;

[0720] a collection target of the data to be acquired by the second device;

[0721] a method for collecting data required by the second device;

[0722] the collection time of the data required to be acquired by the second device;

[0723] The number of sampling points of the data required to be acquired by the second device.

[0724] Optionally, the sixth information includes at least one of the following:

[0725] the type of reward that the second device desires to obtain;

[0726] The amount of the reward that the second device expects to obtain.

[0727] Optionally, the device further includes a second receiving unit, configured to:

[0728] receiving a fourth message from the first device, where the fourth message is used to indicate a rejection of a request from the second device;

[0729] A fifth message is received from the first device, where the fifth message is used to indicate acceptance of the request of the second device.

[0730] Optionally, the fourth message includes at least one of the following:

[0731] an identifier of the data collection request;

[0732] a fourth indication, used to indicate rejection of the request of the second device;

[0733] The seventh information is used to indicate the reason for rejecting the request of the second device.

[0734] Optionally, the fifth message includes at least one of the following:

[0735] an identifier of the data collection request;

[0736] a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection;

[0737] Eighth information, used to instruct the second device to perform data reporting configuration information;

[0738] Ninth information, used to indicate configuration information for receiving data by the second device;

[0739] The first data is existing data provided by the first device to the second device.

[0740] Optionally, the types of rewards include at least one of the following: quality of service (QoS) guarantee, priority enhancement, network data acquisition, free traffic, free voice, free call charges, and free points.

[0741] Optionally, the amount of the reward includes at least one of the following: number of QoS guarantees, number of priority upgrades, number of network data acquisitions, amount of network data acquired, amount of free traffic, duration of free voice calls, amount of free call charges, and number of free points.

[0742] Optionally, in the case where paging of the second device fails, the first data includes at least one of the following:

[0743] paging identification;

[0744] an identifier of the first device;

[0745] an identifier of the second device;

[0746] Identification of the paging area;

[0747] Time information for sending paging messages;

[0748] Indication of whether to apply the paging optimization mechanism;

[0749] a discontinuous reception (DRX) configuration or an extended DRX configuration of the second device;

[0750] Instructions for the paging message sending mechanism;

[0751] When sending a paging message, the first device expects the second device to have a radio resource control (RRC) state; or

[0752] The type of data that the first device needs to obtain includes at least one of the following:

[0753] a movement path of the second device;

[0754] a paging receiving mechanism of the second device;

[0755] at least one of a time and a duration for the second device to receive the paging;

[0756] at least one of a time and a duration during which the second device does not receive a paging call;

[0757] an RRC state of the second device;

[0758] downlink measurement data of the second device;

[0759] an identifier of a cell in which the second device resides;

[0760] at least one of a time and a duration during which the second device resides in the cell;

[0761] Whether the second device is out of service coverage;

[0762] at least one of a time and a duration during which the second device is not covered by a service area;

[0763] an identifier of the last cell where the second device resided before it left the service area;

[0764] The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

[0765] Optionally, the first device includes a network-side device, and the second device includes a terminal;

[0766] The type of data that the first device needs to obtain includes at least one of downlink measurement data and quality of service (QoE) information:

[0767] The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in RRC connected state, and QoE abnormality reasons.

[0768] Optionally, the first device includes a terminal, and the second device includes a network-side device;

[0769] The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason;

[0770] The data type provided by the first device during the data collection process includes at least one of downlink measurement data and quality of service (QoE) information.

[0771] Optionally, the device further comprises:

[0772] The second sending unit is configured to send eleventh information to the first device, where the eleventh information is used to indicate a data collection mode supported by the second device.

[0773] The data collection device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0774] The data collection device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0775] As shown in Figure 8, an embodiment of the present application further provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instruction that can be run on the processor 801. For example, when the communication device 800 is a first device, the program or instruction, when executed by the processor 801, implements the various steps of the first device-side method embodiment described above, and can achieve the same technical effect. When the communication device 800 is a second device, the program or instruction, when executed by the processor 801, implements the various steps of the second device-side method embodiment described above, and can achieve the same technical effect. To avoid repetition, they are not described here.

[0776] The present 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 configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG4 or FIG5 . This terminal embodiment corresponds to the first device-side method embodiment or the second device-side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, FIG9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0777] The terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909 and at least some of the components of the processor 910.

[0778] Those skilled in the art will appreciate that the terminal 900 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0779] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0780] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 901 may transmit the data to the processor 910 for processing. Furthermore, the RF unit 901 may send uplink data to the network-side device. Typically, the RF unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0781] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 909 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a 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 RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0782] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0783] The radio frequency unit 901 is used for:

[0784] receiving a first message from a first device, the first message including at least one data collection request;

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

[0786] an identifier of the data collection request;

[0787] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0788] First information, used to indicate data that the first device needs to obtain;

[0789] second information, used to indicate data that the first device can provide;

[0790] third information, used to indicate a reward that can be provided by the first device;

[0791] The target mode includes any of the following:

[0792] a first mode, in which the first device obtains data from the terminal;

[0793] a second mode, in which the first device acquires data from the terminal and provides at least one of data and a reward to the terminal;

[0794] a third mode, in which the first device acquires data from the terminal and provides the terminal with data collected during the data collection process;

[0795] a fourth mode, in which the first device obtains data from the terminal and provides existing data to the terminal;

[0796] A fifth mode, in which the first device obtains data from the terminal and provides a reward to the terminal.

[0797] or,

[0798] The radio frequency unit 901 is used for:

[0799] sending a first message to a second device, wherein the first message includes at least one data collection request;

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

[0801] an identifier of the data collection request;

[0802] A first indication, used to indicate that the data collection mode of the data collection request is a target mode;

[0803] First information, used to indicate data that the terminal needs to obtain;

[0804] Second information, used to indicate data that the terminal can provide;

[0805] third information, used to indicate a reward that can be provided by the terminal;

[0806] The target mode includes any of the following:

[0807] a first mode, in which the terminal obtains data from the second device;

[0808] a second mode, in which the terminal obtains data from the second device and provides at least one of data and a reward to the second device;

[0809] a third mode, in which the terminal obtains data from the second device and provides the second device with data collected during the data collection process;

[0810] a fourth mode, in which the terminal obtains data from the second device and provides existing data to the second device;

[0811] A fifth mode: in the fifth mode, the terminal obtains data from the second device and provides a reward to the second device.

[0812] In summary, the embodiments of the present application can facilitate both UEs obtaining network data and network-side devices obtaining UE data. Thus, through diverse data collection modes such as data sharing, data exchange, or data rewards, collaboration and win-win results are achieved between network-side devices and UEs in data collection.

[0813] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the data collection method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0814] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 4 or Figure 5. This network-side device embodiment corresponds to the first device-side method embodiment or the second device-side method embodiment described above, and each implementation process and implementation method of the above method embodiments are applicable to this network-side device embodiment and can achieve the same technical effects.

[0815] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 10, network-side device 1000 includes an antenna 101, a radio frequency device 102, a baseband device 103, a processor 104, and a memory 105. Antenna 101 is connected to radio frequency device 102. In the uplink direction, radio frequency device 102 receives information via antenna 101 and sends the received information to baseband device 103 for processing. In the downlink direction, baseband device 103 processes the information to be transmitted and sends it to radio frequency device 102. Radio frequency device 102 processes the received information and then sends it through antenna 101.

[0816] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 103 , which includes a baseband processor.

[0817] The baseband device 103 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 105 through a bus interface to call the program in the memory 105 and execute the network device operations shown in the above method embodiment.

[0818] The network side device may further include a network interface 106, which is, for example, a Common Public Radio Interface (CPRI).

[0819] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 105 and can be run on the processor 104. The processor 104 calls the instructions or programs in the memory 105 to execute the methods executed by each module shown in Figure 6 or Figure 7, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0820] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG11 , the network-side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0821] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1103 and executable on the processor 1101. The processor 1101 calls the instructions or programs in the memory 1103 to execute the methods executed by the modules shown in FIG6 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0822] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data collection method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0823] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0824] An embodiment of the present application further provides a chip, which includes 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 various processes of the above-mentioned data collection method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0825] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0826] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data collection method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0827] An embodiment of the present application also provides a communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the data collection method on the first device side as described above, and the second device can be used to execute the steps of the data collection method on the second device side as described above.

[0828] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0829] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0830] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data collection method comprising: The first device sends a first message to the second device, where the first message includes at least one data collection request; The data collection request includes at least one of the following: an identifier of the data collection request; A first indication, used to indicate that the data collection mode of the data collection request is a target mode; First information, used to indicate data that the first device needs to obtain; second information, used to indicate data that the first device can provide; third information, used to indicate a reward that can be provided by the first device; The target mode includes any of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device; A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

2. The method according to claim 1, wherein The data that can be provided by the first device indicated by the second information includes at least one of the following: data that the first device can provide during the data collection process; The first device may provide existing data.

3. The method according to claim 1 or 2, wherein: The first information includes at least one of the following: the type of data that the first device needs to obtain; a collection target of the data to be acquired by the first device; a method for collecting data required by the first device; The acquisition time of the data required to be acquired by the first device; the number of sampling points of data required to be acquired by the first device; or, The second information includes at least one of the following: the type of data that the first device can provide; a collection target of data that can be provided by the first device; a method for collecting data that can be provided by the first device; the collection time of the data that can be provided by the first device; the number of sampling points of data that the first device can provide; or, The third information includes at least one of the following: the type of reward that the first device can provide; The amount of the reward that the first device can provide.

4. The method according to any one of claims 1 to 3, wherein Also includes any of the following: The first device receives a second message from the second device, where the second message is used to indicate rejection of the data collection request; The first device receives a third message from the second device, where the third message is used to indicate acceptance of the data collection request.

5. The method according to claim 4, wherein The second message includes at least one of the following: an identifier of the data collection request; a second instruction, used to indicate rejection of the data collection request; Fourth information, used to indicate the reason for rejecting the data collection request; or, The third message includes at least one of the following: an identifier of the data collection request; A third instruction, used to indicate acceptance of the data collection request; Fifth information, used to indicate data that the second device needs to obtain; The sixth information is used to indicate the reward that the second device expects to obtain.

6. The method according to claim 5, wherein: The fifth information includes at least one of the following: the type of data that the second device needs to obtain; a collection target of the data to be acquired by the second device; a method for collecting data required by the second device; the collection time of the data required to be acquired by the second device; the number of sampling points of data required to be acquired by the second device; or, The sixth information includes at least one of the following: the type of reward that the second device desires to obtain; The amount of the reward that the second device expects to obtain.

7. The method according to any one of claims 4 to 6, wherein After the first device receives the third message, the method further includes any one of the following: The first device sends a fourth message to the second device, where the fourth message is used to indicate that a request from the second device is rejected; The first device sends a fifth message to the second device, where the fifth message is used to indicate acceptance of the request of the second device.

8. The method according to claim 7, wherein: The fourth message includes at least one of the following: an identifier of the data collection request; a fourth indication, used to indicate rejection of the request of the second device; seventh information, used to indicate the reason for rejecting the request of the second device; or, The fifth message includes at least one of the following: an identifier of the data collection request; a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection; Eighth information, used to instruct the second device to perform data reporting configuration information; Ninth information, used to indicate configuration information for receiving data by the second device; The first data is existing data provided by the first device to the second device.

9. The method according to any one of claims 4 to 6, wherein: After the first device receives the third message, the method further includes: The first device sends tenth information to the third device, where the tenth information is used to indicate a reward event.

10. The method according to claim 9, wherein: The tenth information includes at least one of the following: an identifier of the second device; Type of reward; The number of rewards.

11. The method according to claim 3, 6 or 10, wherein: The types of rewards include at least one of the following: quality of service (QoS) guarantee, priority improvement, network data acquisition, free traffic, free voice, free call charges, and free points; or, The amount of the reward includes at least one of the following: number of QoS guarantees, number of priority upgrades, number of network data acquisitions, amount of network data acquired, amount of free traffic, free voice call duration, free call fee amount, and number of free points.

12. The method according to claim 11, wherein In the case where the type of the reward includes free data, free voice, free call charges or free points, the third device includes a billing function; or, In a case where the type of the reward includes QoS guarantee, priority improvement, or network data acquisition, the third device includes at least one of a wireless access network device and a policy control function.

13. The method according to claim 8, wherein In the case where paging of the second device fails, the first data includes at least one of the following: paging identification; an identifier of the first device; an identifier of the second device; Identification of the paging area; Time information for sending paging messages; a discontinuous reception (DRX) configuration or an extended DRX configuration of the second device; Indication of whether to apply the paging optimization mechanism; Instructions for the paging message sending mechanism; When sending a paging message, the first device expects the second device to have a radio resource control (RRC) state; or The type of data that the first device needs to obtain includes at least one of the following: a movement path of the second device; a paging receiving mechanism of the second device; at least one of a time and a duration for the second device to receive the paging; at least one of a time and a duration during which the second device does not receive a paging call; an RRC state of the second device; downlink measurement data of the second device; an identifier of a cell in which the second device resides; at least one of a time and a duration during which the second device resides in the cell; Whether the second device is out of service coverage; at least one of a time and a duration during which the second device is not covered by a service area; an identifier of the last cell where the second device resided before it left the service area; The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

14. The method according to any one of claims 1 to 12, wherein The first device includes a network-side device, and the second device includes a terminal; The type of data required to be acquired by the first device includes at least one of downlink measurement data and quality of service (QoE) information; The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in a radio resource control RRC connected state, and a QoE abnormality reason; or, The first device includes a terminal, and the second device includes a network-side device; The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason; The data type provided by the first device during the data collection process includes at least one of downlink measurement data and quality of service (QoE) information.

15. The method according to any one of claims 1 to 14, wherein Before the first device sends the first message to the second device, the method further includes: The first device receives eleventh information from the second device, where the eleventh information is used to indicate a data collection mode supported by the second device.

16. A data collection method comprising: The second device receives a first message from the first device, the first message including at least one data collection request; The data collection request includes at least one of the following: an identifier of the data collection request; A first indication, used to indicate that the data collection mode of the data collection request is a target mode; First information, used to indicate data that the first device needs to obtain; second information, used to indicate data that the first device can provide; third information, used to indicate a reward that can be provided by the first device; The target mode includes any of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device; A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

17. The method according to claim 16, wherein The data that can be provided by the first device indicated by the second information includes at least one of the following: data that the first device can provide during the data collection process; The first device may provide existing data.

18. The method according to claim 16 or 17, wherein Also includes any of the following: The second device sends a second message to the first device, where the second message is used to indicate that the data collection request is rejected; The second device sends a third message to the first device, where the third message is used to indicate acceptance of the data collection request.

19. The method according to claim 18, wherein After the second device sends the third message to the first device, the method further includes any one of the following: The second device receives a fourth message from the first device, where the fourth message is used to indicate that a request from the second device is rejected; The second device receives a fifth message from the first device, where the fifth message is used to indicate acceptance of the request of the second device.

20. The method according to claim 19, wherein The fourth message includes at least one of the following: an identifier of the data collection request; a fourth indication, used to indicate rejection of the request of the second device; seventh information, used to indicate the reason for rejecting the request of the second device; or, The fifth message includes at least one of the following: an identifier of the data collection request; a fifth indication, used to indicate acceptance of the request of the second device, or to indicate triggering of data collection, or to request triggering of data collection; Eighth information, used to instruct the second device to perform data reporting configuration information; Ninth information, used to indicate configuration information for receiving data by the second device; The first data is existing data provided by the first device to the second device.

21. The method according to claim 20, wherein In the case where paging of the second device fails, the first data includes at least one of the following: paging identification; an identifier of the first device; an identifier of the second device; Identification of the paging area; Time information for sending paging messages; a discontinuous reception (DRX) configuration or an extended DRX configuration of the second device; Indication of whether to apply the paging optimization mechanism; Instructions for the paging message sending mechanism; When sending a paging message, the first device expects the second device to have a radio resource control (RRC) state; or The type of data that the first device needs to obtain includes at least one of the following: a movement path of the second device; a paging receiving mechanism of the second device; at least one of a time and a duration for the second device to receive the paging; at least one of a time and a duration during which the second device does not receive a paging call; an RRC state of the second device; downlink measurement data of the second device; an identifier of a cell in which the second device resides; at least one of a time and a duration during which the second device resides in the cell; Whether the second device is out of service coverage; at least one of a time and a duration during which the second device is not covered by a service area; an identifier of the last cell where the second device resided before it left the service area; The identifier of the first cell where the second device resides when it returns to the coverage area of ​​the service area.

22. The method according to any one of claims 16 to 20, wherein The first device includes a network-side device, and the second device includes a terminal; The type of data that the first device needs to obtain includes at least one of downlink measurement data and quality of service (QoE) information: The data type provided by the first device during the data collection process includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason; or, The first device includes a terminal, and the second device includes a network-side device; The type of data required to be obtained by the first device includes at least one of uplink measurement data, downlink buffer size, the number of activated UEs in the RRC connected state, and a QoE abnormality reason; The data type provided by the first device during the data collection process includes at least one of downlink measurement data and quality of service (QoE) information.

23. The method according to any one of claims 16 to 22, wherein The method further comprises: The second device sends eleventh information to the first device, where the eleventh information is used to indicate a data collection mode supported by the second device.

24. A data collection device comprising: a first sending unit, configured to send a first message to a second device, wherein the first message includes at least one data collection request; The data collection request includes at least one of the following: an identifier of the data collection request; A first indication, used to indicate that the data collection mode of the data collection request is a target mode; The first information is used to indicate data that the first device needs to obtain; second information, used to indicate data that the first device can provide; third information, used to indicate a reward that can be provided by the first device; The target mode includes any of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device; A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

25. The apparatus according to claim 24, wherein It also includes a first receiving unit, configured to: receiving a second message from the second device, wherein the second message is used to indicate rejection of the data collection request; A third message is received from the second device, where the third message is used to indicate acceptance of the data collection request.

26. The device according to claim 25, wherein The device further includes a second sending unit, configured to: sending a fourth message to the second device, where the fourth message is used to indicate that the request of the second device is rejected; A fifth message is sent to the second device, where the fifth message is used to indicate acceptance of the request of the second device.

27. The device according to claim 26, wherein Also includes: The third sending unit is used to send tenth information to the third device, where the tenth information is used to indicate a reward event.

28. The device according to any one of claims 24 to 27, wherein Also includes: The second receiving unit is configured to receive eleventh information from the second device, where the eleventh information is used to indicate a data collection mode supported by the second device.

29. A data collection device comprising: a first receiving unit, configured to receive a first message from a first device, wherein the first message includes at least one data collection request; The data collection request includes at least one of the following: an identifier of the data collection request; A first indication, used to indicate that the data collection mode of the data collection request is a target mode; First information, used to indicate data that the first device needs to obtain; second information, used to indicate data that the first device can provide; third information, used to indicate a reward that can be provided by the first device; The target mode includes any of the following: a first mode, in which the first device obtains data from the second device; a second mode, in which the first device obtains data from the second device and the first device provides at least one of data and a reward to the second device; a third mode, in which the first device obtains data from the second device, and the first device provides the second device with data collected during the data collection process; a fourth mode, in which the first device obtains data from the second device and provides existing data to the second device; A fifth mode, in which the first device obtains data from the second device, and the first device provides a reward to the second device.

30. The apparatus according to claim 29, wherein The first sending unit is further included, configured to: sending a second message to the first device, where the second message is used to indicate rejection of the data collection request; A third message is sent to the first device, where the third message is used to indicate acceptance of the data collection request.

31. The device according to claim 30, wherein Also includes a second receiving unit, configured to: receiving a fourth message from the first device, where the fourth message is used to indicate a rejection of a request from the second device; A fifth message is received from the first device, where the fifth message is used to indicate acceptance of the request of the second device.

32. The device according to any one of claims 29 to 31, wherein Also includes: The second sending unit is configured to send eleventh information to the first device, where the eleventh information is used to indicate a data collection mode supported by the second device.

33. A communication device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the data collection method as described in any one of claims 1 to 15 are implemented, or the steps of the data collection method as described in any one of claims 16 to 23 are implemented.

34. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the data collection method according to any one of claims 1 to 15, or implements the steps of the data collection method according to any one of claims 16 to 23.

35. A computer program product comprising computer instructions, which, when executed by a processor, implement the steps of the data collection method according to any one of claims 1 to 15, or the steps of the data collection method according to any one of claims 16 to 23.

Images