Method and apparatus for collecting data, and device

Abstract

The present application belongs to the technical field of communications, and discloses a method and apparatus for collecting data, and a device. The method for collecting data in the embodiments of the present application comprises: a first device receives a first message sent by a second device, the first message being used for requesting data of a target device; and the first device determines whether to allow the second device to collect the data of the target device.

Description

Data collection methods, devices and equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410379298.5 filed in China on March 29, 2024, 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 equipment. Background Art

[0004] To improve the user experience of devices, networks can collect device data and analyze the collected data to improve services. In related technologies, when collecting device data, networks can send requests to devices and obtain device data directly from them, which has poor data security. Summary of the Invention

[0005] The embodiments of the present application provide a data collection method, apparatus, and device that can solve the problem of poor data security.

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

[0007] The first device receives a first message sent by the second device, where the first message is used to request data from a target device;

[0008] The first device determines whether to allow the second device to collect data of the target device.

[0009] In a second aspect, a data collection method is provided, comprising:

[0010] The second device sends a first message to the first device, where the first message is used to request data from the target device;

[0011] The second device receives a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

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

[0013] a receiving module, configured to receive a first message sent by a second device, wherein the first message is used to request data from a target device;

[0014] A determination module is configured to determine whether the second device is allowed to collect data of the target device.

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

[0016] A sending module, configured to send a first message to a first device, wherein the first message is used to request data of a target device;

[0017] The receiving module is configured to receive a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

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

[0019] In a sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein the processor is configured to:

[0020] receiving a first message sent by a second device, where the first message is used to request data from a target device;

[0021] Determine whether to allow the second device to collect data of the target device.

[0022] In a seventh aspect, a second device is provided, comprising a processor and a communication interface, wherein the processor is configured to:

[0023] Sending a first message to a first device, where the first message is used to request data from a target device;

[0024] A second message sent by the first device is received, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

[0025] 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 or the steps of the method described in the second aspect are implemented.

[0026] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0027] In the tenth 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 method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0028] In the eleventh aspect, a data collection 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.

[0029] In an embodiment of the present application, a first device receives a first message sent by a second device, the first message being used to request data from a target device. The first device then determines whether to allow the second device to collect the target device's data. This allows the first device to determine whether to allow the second device to collect the target device's data, and the first device to authorize the second device to collect the target device's data, thereby improving data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0031] FIG2 is a schematic diagram of a data collection architecture using data collection coordination in the related art;

[0032] FIG3 is a schematic diagram of an open architecture for network data analysis using data collection coordination in the related art;

[0033] FIG4 is a schematic diagram of a data plane in the related art;

[0034] FIG5 is a schematic diagram of a data plane protocol architecture terminated in a wireless access network in the related art;

[0035] FIG6 is a schematic diagram of a data plane protocol architecture in the related art;

[0036] FIG7 is a second schematic diagram of a data plane protocol architecture in the related art;

[0037] FIG8 is a schematic diagram of a data collection method according to an embodiment of the present application;

[0038] FIG9 is a second schematic diagram of a data collection method provided in an embodiment of the present application;

[0039] FIG10 is a structural diagram of a data collection device according to an embodiment of the present application;

[0040] FIG11 is a second structural diagram of a data collection device provided in an embodiment of the present application;

[0041] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0042] FIG13 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0043] FIG14 is a schematic diagram of a structure of a network side device according to an embodiment of the present application;

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

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

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

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

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

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

[0050] 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 user 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.

[0051] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0052] 1. 5th Generation Mobile Communication Technology (5G) network data analysis services

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

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

[0055] [Optional] Use the Data Collection Coordination Function (DCCF) for analysis and data collection;

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

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

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

[0059] Retrieve information about Network File System (NFs) (e.g., retrieve information related to NFs from NRF);

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

[0061] Provide consumers with large amounts of data.

[0062] The Data Collection architecture using Data Collection Coordination is shown in Figure 2.

[0063] The Network Data Analytics Exposure architecture using Data Collection Coordination is shown in Figure 3.

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

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

[0066] Table 1

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

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

[0069] Mp is the measurement result of SpCell without considering any offset;

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

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

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

[0073] 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;

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

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

[0076] In the case of RSRP, Mn and Mp are expressed in dBm, or in the case of RSRQ and RS-SINR, they are expressed in dB. Ofn, Ocn, Ofp, Ocp, Hys, and Off are expressed in dB, and Thresh is expressed in the same unit as Mn.

[0077] When one or more cells meet the entry conditions of the configuration 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.

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

[0079] 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:

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

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

[0082] 4. Data Plane and Potential Data Plane Protocol Solutions

[0083] The data plane is currently being discussed in 6G network architecture discussions. The data plane comprises core network data plane functions, radio access network data plane functions, and user equipment (UE) data plane functions, providing end-to-end connectivity. The data plane is responsible for data control, including data collection coordination, data collection configuration, and data transmission configuration. It also handles data acquisition, data transmission, data preprocessing, data privacy and security, data analysis, data storage, and data services. A schematic diagram of the data plane is shown in Figure 4. The data plane protocol architecture terminating in the radio access network is shown in Figure 5. The data plane protocol architecture for the UE, radio access network, and core network is shown in Figure 6.

[0084] With the introduction of the data plane, a schematic diagram of data-plane-based self-organized network (SON) / minimization of drive tests (MDT), positioning, perception, and AI is shown in Figure 7. For data plane data transmission, a new protocol layer is introduced, which for ease of description is called the Data Plane Adaptation Protocol (DPAP). This protocol layer is used to transmit data plane data and can also be used to generate data plane data, such as data plane signaling data.

[0085] The data collection method, apparatus, and device provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0086] 8 , which is a flow chart of a data collection method provided in an embodiment of the present application. As shown in FIG8 , the data collection method includes the following steps:

[0087] Step 101: A first device receives a first message sent by a second device, where the first message is used to request data from a target device.

[0088] Step 102: The first device determines whether to allow the second device to collect data of the target device.

[0089] The target device may be the first device, or a device other than the first device. The first device may be a network-side device. The second device may be a terminal or a network-side device.

[0090] It should be understood that the first device can be used to authorize data collection, thereby authorizing the second device to collect data from the target device. If the first device authorizes the second device, the second device can collect data from the target device; if the first device does not authorize the second device, the second device cannot collect data from the target device.

[0091] For example, the first device may be a network function node, such as a data plane function node, a radio access network node, a core network function node such as an AMF or NEF.

[0092] For example, the first device may be a terminal.

[0093] For example, the second device may be a terminal, and the target device may be a network-side device, such as a network function node or an application function. Thus, the first device can authorize the terminal to collect network data. The first device and the target device may be the same device or different devices.

[0094] For example, the second device may be a network-side device, such as a network function node or an application function, and the target device may be a terminal. Thus, the first device can authorize the network to collect terminal data.

[0095] It should be noted that compared to 5G, where data collection is primarily used for communication optimization, 6G systems collect more data types, potentially enabling multiple services (or use cases). The collected data can be used for at least one of the following service types:

[0096] Perception services are services that provide information about an object's location, characteristics, or environment. These services typically include those provided to external network functions (e.g., application functions), such as drone intrusion detection, indoor positioning for robot navigation, and obstacle perception assistance for autonomous vehicles. They also include those provided to internal network functions (e.g., radio access network nodes or core network function nodes). For example, these services can assist in determining whether a propagation path is line-of-sight (LOS) or non-line-of-sight (NLOS) by detecting the presence of obstacles in a particular beam direction.

[0097] AI services refer to services that provide AI training data, AI inference data, AI models, etc. AI services generally include providing AI services to external network functions (such as application function provision), such as providing AI model inference services for application functions deployed on terminals. AI services also include providing AI services to internal network functions (such as wireless access network nodes or core network function nodes), such as for network data analytics function nodes (NWDAF) to perform network intelligent analysis.

[0098] Network capability exposure services refer to services exposed through network functions, such as the Network Exposure Function (NEF) or Common API Framework (CAPIF) in 5G.

[0099] User experience optimization service refers to identifying user experience issues, analyzing causes or optimizing configurations based on data analysis.

[0100] Network optimization service refers to identifying network problems, analyzing causes, or optimizing configurations based on data analysis.

[0101] In one embodiment, the first device determining whether to allow the second device to collect data of the target device may include the first device determining whether to allow the second device to collect data of the target device for a target service type.

[0102] In one embodiment, the first device determining whether to allow the second device to collect data from the target device may include the first device determining whether to allow the second device to collect data from the target device for data processing, data storage, or data services. Data processing includes data compression, data cleaning, data integration, data format conversion, data analysis, etc. Data storage refers to storing the collected data from the target device. Data services refer to providing the target device data to a data requesting node.

[0103] For example, the second device can be a network-side device, such as a network function node or application function, and the target device can be a terminal. This allows the first device to authorize the types of services for which the network collects terminal data; or authorize the processing, data storage, or data services of the network-collected terminal data; or authorize nodes that can perform data processing, data storage, or data services, thereby ensuring that data is processed, stored, or served on nodes authorized by the terminal.

[0104] In one embodiment, after a first device receives a first message sent by a second device, the first device may send a second message to the second device, where the second message is used to indicate whether the second device is allowed to collect data of the target device; or, the first device may send the second message to the second device only if the second device is allowed to collect data of the target device; or, the first device may send the second message to the second device only if the second device is not allowed to collect data of the target device; and so on. This embodiment does not limit this.

[0105] In one embodiment, the first device can determine whether to allow the second device to collect data of the target device using the target data collection mode, so that the first device can not only authorize the second device to collect data of the target device, but also authorize the target data collection mode for the second device to collect data of the target device.

[0106] It should be noted that the first message may be a data request message, a data request authorization request message, a data collection message, a data collection authorization request message, etc. This embodiment does not limit the specific name of the first message.

[0107] In one embodiment, the first message may carry at least one of first indication information, first information, second information, third information, fourth information, and fifth information. The first indication information is indication information for indicating the target data collection mode; the first information is information related to the requested data; the second information is information related to data that can be shared with the target device; the third information is information related to data that can be exchanged with the target device; the fourth information is information about rewards that can be provided by the second device; and the fifth information is information about rewards that the second device expects to obtain.

[0108] In addition, the first message may further include a request identifier, which may be used to uniquely identify a data collection request.

[0109] It should be noted that in the embodiment of the present application, "collect" can be replaced by "acquisition." The first device determines whether to allow the second device to collect the data of the target device, which can also be described as the first device determining whether to allow the second device to collect the data of the target device. The first device determines whether to allow the second device to collect the data of the target device, which can also be described as the first device determining whether to allow the second device to collect the data of the target device for data processing; or the first device determines whether to allow the second device to collect the data of the target device for data storage; or the first device determines whether to allow the second device to collect the data of the target device and provide it to the data requester.

[0110] Among them, the data of the target device may include data collected by the target device, data locally stored by the target device, data obtained by the target device, or data associated with the target device, etc. This embodiment does not limit the data of the target device, and all data that can be obtained from the target device can be considered as the data of the target device.

[0111] In an embodiment of the present application, a first device receives a first message sent by a second device, the first message being used to request data from a target device. The first device then determines whether to allow the second device to collect the target device's data. This allows the first device to determine whether to allow the second device to collect the target device's data, and the first device to authorize the second device to collect the target device's data, thereby improving data security.

[0112] Optionally, the first device determines whether to allow the second device to collect data of the target device, including at least one of the following:

[0113] determining, by the first device, whether to allow the second device to collect data of the target device in a target data collection mode;

[0114] determining, by the first device, whether to allow the second device to collect data of the target device for a target service type;

[0115] The first device determines whether to allow the second device to collect data of the target device for data processing, data storage, or data service.

[0116] In the target data collection mode, the second device may be used to perform a data collection operation; the data collection operation includes:

[0117] During a data collection process, the second device collects data from the target device, and the second device does not provide data to the target device; or

[0118] During a data collection process, the second device collects data from the target device and provides data to the target device; or

[0119] The second device collects the data of the target device in a data sharing manner; or

[0120] The second device collects data of the target device in a data exchange manner; or

[0121] The second device collects data of the target device based on the reward information; or

[0122] The second device collects data of the target device based on the permission information.

[0123] In one embodiment, the target data collection mode may be a first mode, where the second device collects data from the target device during a data collection process and does not provide data to the target device. The first mode may be considered a single-ended mode, where either the network or the terminal obtains the required data.

[0124] In one embodiment, the target data collection mode may be a second mode. The second mode may mean that during a data collection process, the second device collects data from the target device and provides data to the target device. The second mode can be considered a dual-end mode. The dual-end mode means that both the network and the terminal obtain the required content. The required content may include data, Quality of Service (QoS) guaranteed times, priority increase times, traffic quota, voice quota or points, etc.

[0125] In one embodiment, the target data collection mode may be a third mode, where the second device collects data from the target device in a data sharing manner. The third mode can be considered a sharing mode, where the network requests the terminal for data collected by the terminal, and the terminal also requests the network for data collected by the network. Ultimately, during the data collection process, the network sends the collected data to the terminal, and the terminal sends the collected data to the network. The data sharing method may refer to either the third mode or the sharing mode.

[0126] In one embodiment, the target data collection mode may be a fourth mode, where the second device collects data from the target device in a data exchange manner. The fourth mode can be considered an exchange mode, where a network or terminal requests required data in exchange for existing data during a data collection process. The data exchange method may be the fourth mode or the exchange mode.

[0127] In one embodiment, the target data collection mode may be a fifth mode, which may refer to the second device collecting data of the target device based on reward information. The fifth mode can be considered a reward mode, which refers to the network or terminal requesting the required data with a valuable reward during a data collection process. The reward information may include the number of QoS guarantees, the number of priority upgrades, traffic, voice, call charges or points, etc. The characteristic of the fifth mode is that the relevant reward information needs to be maintained after the data is collected to ensure that the recipient can use the reward, that is, to realize the value of the reward.

[0128] In one embodiment, the target data collection mode may be the sixth mode, which may refer to the second device collecting data from the target device based on permission information. The sixth mode can be considered a permission mode, which refers to the network or terminal requesting the required data during a data collection process using its permission to collect data. The permission information may include the number of network data acquisitions or the amount of network data acquired. The permission in the embodiments of the present application can be understood or replaced by rights.

[0129] In addition, after the first device receives the first message sent by the second device, the first device may send a second message to the second device, where the second message may be used to indicate whether the second device is allowed to collect data of the target device in the target data collection mode.

[0130] In this implementation, the first device authorizes whether to allow the second device to collect data of the target device using the target data collection mode, and supports the first device to authorize whether to allow the second device to collect data of the target device according to different data collection modes. While improving data security, it can also improve the flexibility of data collection authorization.

[0131] Optionally, the first message carries first indication information, first information, second information, third information, fourth information or fifth information; the target data collection mode is determined based on the first indication information, the first information, the second information, the third information, the fourth information or the fifth information; wherein,

[0132] The first indication information is indication information for indicating the target data collection mode;

[0133] The first information is related information of the requested data;

[0134] The second information is related information of data that can be shared with the target device;

[0135] The third information is information related to data that can be exchanged with the target device;

[0136] The fourth information is reward information that can be provided by the second device;

[0137] The fifth information is reward information that the second device expects to obtain.

[0138] The first information is information related to the requested data and may include at least one of a collection parameter, a collection target, and a collection method.

[0139] For the acquisition parameters in the first information, taking the first information used to request terminal downlink measurement data as an example, the acquisition parameters may include at least one of the following: reference signal received power (RSRP), reference signal received power per branch (RSRPB), reference signal received quality (RSRQ), received signal strength indicator (RSSI), and signal-to-noise and interference ratio (SINR).

[0140] The collection target in the first information refers to the cells whose data the terminal collects. The collection target can be represented by at least one of the following items in the first information:

[0141] Indication information, used to indicate that only serving cell data is to be collected, or that only neighboring cell data is to be collected, or that both serving cell and neighboring cell data need to be collected. For example, for neighboring cell data, the network selects which neighboring cell data to send to the terminal based on implementation;

[0142] Cell Global Identifier (CGI), including Public Land Mobile Network (PLMN) identifier (ID) and cell ID;

[0143] Physical cell identity (PCI);

[0144] Carrier frequency information;

[0145] Tracking Area Code (TAC);

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

[0147] The collection mode in the first information includes at least one of network request triggering, periodic triggering, and event triggering. The collection mode can be characterized by parameters of the network request triggering, periodic triggering, or event triggering in the first information. The periodic triggering parameter can include a time interval, where the unit of the time interval can be any one of hours, minutes, seconds, milliseconds, microseconds, frames, subframes, symbols, and time slots; the event triggering parameter can include at least one of a triggering event and a triggering time associated with the triggering time.

[0148] The second information is information related to data that can be shared with the target device. The second information may include at least one of a collection parameter, a collection target, and a collection time.

[0149] For the acquisition parameters in the second information, taking the first information as uplink measurement data collected by the network as an example, the acquisition parameters include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, SINR, radio resource status (for example, the radio resource status in the current protocol, indicating the usage of the physical resource blocks (PRBs) for multiple input multiple output (MIMO) in each cell, each synchronization signal block (SSB) area, and each slice for all services in the downlink and uplink, and the usage of the physical downlink control channel (PDCCH) control channel element (CCE) for downlink and uplink scheduling (Radio Resource Status, 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), PRB usage, PDCCH for uplink scheduling. CCE utilization, PDCCH CCE utilization for downlink scheduling, number of users in Radio Resource Control (RRC) connected / inactive state, ratio of the number of users in RRC connected / inactive state to the maximum number of users, uplink / downlink throughput.

[0150] The collection target in the second information is used to instruct the network which cells' data to collect, such as the global cell identity CGI (such as PLMN ID and Cell ID), physical cell identity (PCI), etc.

[0151] Regarding the collection time in the second information, the collection time includes at least one of the collection start time, end time, time length, collection time interval, and number of sampling points.

[0152] The third information is related information of data that can be exchanged with the target device, and may include at least one of the following: parameters, time, number of sampling points, etc. Taking paging failure optimization as an example, the parameters in the third information include at least one of the following:

[0153] The RAN-based Notification Area (RNA) ID, Random Access (RA) ID, Tracking Area (TA) ID, gNB ID, cell ID, and terminal ID involved in the paging initiation;

[0154] The time when the paging message is sent (such as the paging frame (PF), paging occasion (PO), PDCCH occasion, etc.), time period, paging identifier, and terminal discontinuous reception (DRX) / extended DRX cycle (eDRX) configuration;

[0155] Whether paging optimization mechanisms, such as Permanent Equipment Identifier (PEI) and Low Power Wake Up Receiver (LP-WUR), are applied when sending paging messages;

[0156] When sending a paging message, the network expects the RRC state of the terminal (such as idle state (IDLE) or inactive state (inactive)), or the corresponding sending mechanism of the paging message (such as RAN paging or core network paging).

[0157] The fourth information is the reward information that the second device can provide, and the reward information may include at least one of the following: reward content, quantity, etc.

[0158] The reward content in the reward information may include at least one of the following: QoS guarantee, number of network data acquisition times, priority improvement, traffic, voice, points, etc.

[0159] The amount in the reward information may include at least one of the following:

[0160] Times, such as QoS guarantee times, network data acquisition times, or priority enhancement times;

[0161] duration, such as the duration of a call;

[0162] Traffic or points, such as 100M traffic or 100 points.

[0163] The fifth information is the reward information that the second device expects to obtain, and the fifth information may include at least one of the following: reward content and amount, etc. The reward information in the fifth information can refer to the description of the reward information in the fourth information, and will not be repeated here.

[0164] In one embodiment, when the target data collection mode is the second mode or the third mode, the first message may further include at least one of the following: first information, second information; or, when the target data collection mode is the second mode or the fourth mode, the first message may further include at least one of the following: first information, third information; or, when the target data collection mode is the second mode or the fifth mode, the first message may further include at least one of the following: first information, fourth information; or, when the target data collection mode is the first mode or the sixth mode, the first message may further include at least one of the following: third information, fifth information.

[0165] It should be noted that the first message may contain the second information but not the first indication information, thereby implicitly indicating that the data collection mode is the sharing mode (i.e., the third mode) through the second information; or, the first message may contain the third information but not the first indication information, thereby implicitly indicating that the data collection mode is the exchange mode (i.e., the fourth mode) through the third information; or, the first message may contain the fourth information but not the first indication information, thereby implicitly indicating that the data collection mode is the reward mode (i.e., the fifth mode) through the fourth information; or, the first message may contain the fifth information but not the first indication information, thereby implicitly indicating that the data collection mode is the permission mode (i.e., the sixth mode) through the fifth information.

[0166] In one embodiment, the second device (network side device or terminal) sends a first message, which is used for data request and includes at least one of a mode indication, a request identifier, first information, second information, third information, fourth information, and fifth information.

[0167] The mode indication is used to indicate a data collection mode, including at least one of a first mode, a second mode, a third mode, a fourth mode, a fifth mode, and a sixth mode.

[0168] The first mode refers to one of the network-side device or terminal obtaining the required data;

[0169] The second mode means that both the network-side device and the terminal obtain the required content, which may be data, QoS guarantee times, priority upgrade times, traffic quota, voice quota or points, etc.

[0170] The third mode refers to a data collection process in which the network device requests the terminal to collect data, and the terminal also requests the network device to collect data. Finally, during the data collection process, the network device sends the collected data to the terminal, and the terminal sends the collected data to the network device.

[0171] The fourth mode refers to a data collection process in which a network-side device or terminal requests the required data in exchange for its existing data;

[0172] The fifth mode is that during a data collection process, the network-side device or terminal requests the required data with valuable rewards, such as QoS guarantee times, priority upgrade times, traffic, voice, call charges or points;

[0173] The sixth mode refers to a network side device or terminal requesting required data with its data collection permission during a data collection process, wherein the data collection permission includes the number of network data acquisitions, the amount of network data acquired, etc.

[0174] In one embodiment, the first device receives the first message and performs data request authorization. The first device (such as a data plane node, AMF or wireless access network node, etc.) obtains the privacy profile or user consent information corresponding to the terminal to perform authorization.

[0175] Authorizing a data request by the first device may mean that the first device determines whether to accept the data request. If not, the first device may not send a response or may send a rejection response to the second device. Optionally, the rejection response may include a rejection reason. If the first device accepts or considers accepting the data request, the first device may send a second message to the second device, which may include an acceptance indication or fifth information.

[0176] In this embodiment, the first device determines the target data collection mode through one or more of the first indication information, the first information, the second information, the third information, the fourth information and the fifth information, and then determines whether to allow the second device to use the target data collection mode to collect data of the target device. The determination of the target data collection mode can be achieved through the first message interacted between the first device and the second device.

[0177] Optionally, when the target device is a terminal, the first device determining whether to allow the second device to collect data of the target device includes:

[0178] The first device obtains first configuration information corresponding to the terminal;

[0179] The first device determines whether to allow the second device to collect data of the terminal based on the first configuration information.

[0180] The first configuration information may be stored on the first device or a third device. The third device may be a network-side device, such as a UDM. The third device and the first device are different devices. The first device obtaining the first configuration information corresponding to the terminal may include: the first device obtaining the first configuration information corresponding to the terminal from a local storage; or the first device obtaining the first configuration information corresponding to the terminal from a third device. For example, the first device may send a request message to the third device, the request message being used to request the first configuration information corresponding to the terminal, and the third device sending the first configuration information corresponding to the terminal to the first device.

[0181] Optionally, the first configuration information corresponding to the terminal may be a privacy profile of the terminal.

[0182] Optionally, the first configuration information may be used to indicate whether terminal data collection is allowed, whether a certain data collection mode is allowed, effective time, effective area, notification method, verification method, etc., or a combination of multiple thereof.

[0183] In this implementation, when the target device is a terminal, the first device obtains the first configuration information corresponding to the terminal, and the first device determines whether to allow the second device to collect the data of the terminal based on the first configuration information, so that the first device can authorize whether to allow the second device to collect the terminal data based on the first configuration information corresponding to the terminal, thereby improving the security of the terminal data.

[0184] Optionally, the first configuration information is used to indicate at least one of the following:

[0185] Whether to allow collection of data from the terminal;

[0186] The validity period for allowing the collection of data from the terminal;

[0187] The validity period during which the collection of data from the terminal is not permitted;

[0188] The area where data collection of the terminal is allowed;

[0189] Areas where data collection of the terminal is not permitted;

[0190] Permissible modes of data collection;

[0191] Impermissible patterns of data collection;

[0192] allowing collection of data of the terminal upon notifying the terminal;

[0193] the data collection modes permitted with notification to said terminal;

[0194] In the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, allowing the collection of data from the terminal; or, in the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, not allowing the collection of data from the terminal;

[0195] In the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, allowing the collection of data from the terminal using the first data collection mode; or, in the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, not allowing the collection of data from the terminal using the second data collection mode;

[0196] Types of services allowed;

[0197] Types of services not permitted;

[0198] Allowing the collection of data from the terminal for data processing, data storage or data services;

[0199] It is not allowed to collect data from the terminal for data processing, data storage or data services;

[0200] A node that allows data processing, data storage, or data service.

[0201] In one embodiment, the first configuration information can be used to indicate whether the collection of data of the terminal is allowed. The first device determines whether the second device is allowed to collect data of the terminal based on the first configuration information, which may include: when the first configuration information indicates that the collection of data of the terminal is allowed, the first device determines that the second device is allowed to collect data of the terminal; or when the first configuration information indicates that the collection of data of the terminal is not allowed, the first device determines that the second device is not allowed to collect data of the terminal.

[0202] The validity period for allowing or not allowing the terminal data to be collected may be a valid time interval represented by a start time and an end time, during which data collection is allowed or not allowed.

[0203] In one embodiment, the first configuration information can be used to indicate the validity period for allowing the collection of data of the terminal. The first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: within the validity period for allowing the collection of data of the terminal indicated by the first configuration information, the first device allows the second device to collect data of the terminal.

[0204] In one embodiment, the first configuration information can be used to indicate a validity period during which the collection of data of the terminal is not allowed. The first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: within the validity period during which the collection of data of the terminal is not allowed as indicated by the first configuration information, the first device does not allow the second device to collect data of the terminal.

[0205] Among them, the area where the data of the terminal is allowed to be collected or the area where the data of the terminal is not allowed to be collected can be represented by a general geographical area, or an area associated with the terminal or base station or AMF (such as RNA or TA, etc.).

[0206] In one embodiment, the first configuration information can be used to indicate an area where data collection of the terminal is allowed, and the first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: the first device allows the second device to collect data of the terminal within the area where data collection of the terminal is allowed as indicated by the first configuration information.

[0207] In one embodiment, the first configuration information can be used to indicate an area where data collection of the terminal is not allowed. The first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: the first device does not allow the second device to collect data of the terminal in the area indicated by the first configuration information where data collection of the terminal is not allowed.

[0208] In one embodiment, the first configuration information can be used to indicate a disallowed data collection mode, and the first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: the first device does not allow the second device to collect data of the terminal using the disallowed data collection mode indicated by the first configuration information.

[0209] In one embodiment, the first configuration information can be used to indicate an allowed data collection mode, and the first device determines whether to allow the second device to collect data of the terminal based on the first configuration information, which may include: the first device allows the second device to collect data of the terminal using the allowed data collection mode indicated by the first configuration information.

[0210] Among them, the service types may include perception services, AI services, network capability exposure services, user experience optimization services, etc. The service types can refer to the explanation of the aforementioned service types and will not be repeated here.

[0211] In one embodiment, the first data collection mode may include at least one of the aforementioned first to sixth modes. The second data collection mode may include at least one of the aforementioned first to sixth modes. When the first configuration information indicates that if no response from the terminal is received after notifying the terminal and performing terminal privacy verification, the first data collection mode is allowed to be used to collect data from the terminal; and the first configuration information further indicates that if no response from the terminal is received after notifying the terminal and performing terminal privacy verification, the second data collection mode is not allowed to be used to collect data from the terminal, the first data collection mode is different from the second data collection mode.

[0212] In one embodiment, the allowing of the collection of the terminal's data for data processing, data storage, or data service can also be described as allowing data processing, data storage, or data service. The not allowing of the collection of the terminal's data for data processing, data storage, or data service can also be described as not allowing data processing, data storage, or data service. When the first configuration information indicates that data processing, data storage, or data service is not allowed, or when the first configuration information indicates that the node that allows data processing, data storage, or data service is not the second device, then the first device does not allow the second device to perform data processing, data storage, or data service on the collected data of the target device.

[0213] In this embodiment, the first device can authorize the second device to collect terminal data based on whether the first configuration information indicates whether terminal data collection is allowed, whether a certain data collection mode is allowed, the effective time, the effective area, the notification method or the verification method, thereby improving the security of the terminal data.

[0214] Optionally, when the target device is a network-side device and the second device is a terminal, the first device determining whether to allow the second device to collect data of the target device includes:

[0215] The first device obtains second configuration information corresponding to the terminal;

[0216] The first device determines whether to allow the terminal to collect data of the network-side device based on the second configuration information.

[0217] The second configuration information may be stored on the first device or the third device. The third device may be a network-side device, such as a UDM, and the third device is a different device from the first device. The first device obtaining the second configuration information corresponding to the terminal may include: the first device obtaining the second configuration information corresponding to the terminal from the local storage; or the first device obtaining the second configuration information corresponding to the terminal from the third device. For example, the first device may send a request message to the third device, the request message being used to request the second configuration information corresponding to the terminal, and the third device sending the second configuration information corresponding to the terminal to the first device.

[0218] In this embodiment, the first device obtains the second configuration information corresponding to the terminal, and the first device determines whether to allow the terminal to collect data of the network side device based on the second configuration information, so that the first device can authorize whether to allow the terminal to collect data of the network side device based on the second configuration information corresponding to the terminal, thereby improving the security of the data of the network side device.

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

[0220] second indication information, where the second indication information is used to indicate whether the terminal has permission to obtain data from the network-side device;

[0221] third indication information, where the third indication information is used to indicate the number of times the terminal is allowed to obtain data from the network-side device;

[0222] Fourth indication information, the fourth indication information is used to indicate the permitted data volume of the terminal, and the permitted data volume represents the amount of data that can be obtained from the network-side device.

[0223] The fifth indication information is used to indicate that the terminal has a permission event for obtaining data of the network-side device, and the permission event represents an event in which the network-side device can be obtained.

[0224] In one embodiment, the second configuration information may include second indication information, so that the first device can determine whether the terminal has consent or permission to obtain data from the network-side device based on the second indication information. If the second indication information indicates that the terminal does not have consent or permission to obtain data from the network-side device, the first device determines not to allow the terminal to collect data from the network-side device; if the second indication information indicates that the terminal has consent or permission to obtain data from the network-side device, the first device determines to allow the terminal to collect data from the network-side device.

[0225] The number of times the terminal is permitted indicated by the third indication information may refer to the total number of times permitted, the number of times permitted that has been used, or the number of times permitted that remains, which is not limited in this embodiment.

[0226] In one embodiment, the second configuration information may include third indication information, and the first device may determine whether to allow the terminal to collect data from the network-side device based on the total number of permitted times the terminal has indicated by the third indication information, and the number of times the terminal has used to obtain data from the network-side device. For example, if the number of times the terminal has used to obtain data from the network-side device is less than the total number of permitted times the terminal has indicated by the third indication information, the first device determines to allow the terminal to collect data from the network-side device; if the number of times the terminal has used to obtain data from the network-side device is greater than or equal to the total number of permitted times the terminal has indicated by the third indication information, the first device determines not to allow the terminal to collect data from the network-side device.

[0227] In one embodiment, the first device may determine whether to allow the terminal to collect data from the network-side device based on the remaining number of permitted times for the terminal indicated by the third indication information. If the number of permitted times for the terminal indicated by the third indication information is greater than 0, the first device determines to allow the terminal to collect data from the network-side device; otherwise, the first device determines not to allow the terminal to collect data from the network-side device.

[0228] The permitted data volume of the terminal indicated by the fourth indication information may refer to the total permitted data volume, the used permitted data volume, or the remaining permitted data volume, which is not limited in this embodiment.

[0229] In one embodiment, the second configuration information may include fourth indication information, and the first device may determine whether to allow the terminal to collect data from the network-side device based on the total permitted data volume of the terminal indicated by the fourth indication information and the amount of data already used by the terminal to obtain data from the network-side device. For example, if the amount of data already used by the terminal to obtain data from the network-side device is less than the total permitted data volume of the terminal indicated by the fourth indication information, the first device determines to allow the terminal to collect data from the network-side device; if the amount of data already used by the terminal to obtain data from the network-side device is greater than or equal to the total permitted data volume of the terminal indicated by the fourth indication information, the first device determines not to allow the terminal to collect data from the network-side device.

[0230] In one embodiment, the first device may determine whether to allow the terminal to collect data from the network-side device based on the remaining permitted data amount of the terminal indicated by the fourth indication information. If the remaining permitted data amount of the terminal indicated by the fourth indication information is greater than 0, the first device determines to allow the terminal to collect data from the network-side device; otherwise, the first device determines not to allow the terminal to collect data from the network-side device.

[0231] Among them, the fifth indication information is used to indicate that the terminal has permission to obtain data from the network side device, which may be a paging failure event, a flow interruption event (for example, the downlink rate is less than the first threshold, and the downlink received signal quality is greater than the second threshold), a switching failure event, or a quality of experience (QoE) abnormal event (for example, video freeze), etc. This embodiment does not limit this.

[0232] In this embodiment, the first device can authorize whether to allow the terminal to collect network data through whether the second configuration information indicates whether the terminal has permission to obtain data from the network side device, the number of times the terminal has permission, the amount of permission the terminal has, or the permission events the terminal has, thereby improving the security of network data.

[0233] Optionally, the method further includes:

[0234] The first device sends a second message to the second device, where the second message is used to indicate whether the second device is allowed to collect data of the target device.

[0235] In this implementation, the first device sends a second message to the second device in response to the first message, so that the second device can learn from the second message the authorization result of the first device on whether to allow the second device to collect data of the target device.

[0236] Optionally, the method further includes:

[0237] In a case where the first device determines to allow the second device to collect data of the target device, the first device sends a third message to the target device, where the third message is used to instruct the target device to provide data.

[0238] The third message may be used to instruct the target device to provide data directly to the second device; or the third message may be used to instruct the target device to provide data to the first device, and the first device forwards the data provided by the target device.

[0239] It should be noted that, when the second message is used to indicate that the second device is allowed to collect data of the target device, the third message and the second message can be the same message, that is, the third message is a multicast message, and the second device and the target device can both receive the third message to know that the first device allows the second device to collect data of the target device.

[0240] In this embodiment, when the first device determines to allow the second device to collect data of the target device, the first device sends a third message to the target device, so that the target device can determine whether to provide data to the second device according to the third message.

[0241] 9 , which is a flow chart of a data collection method provided in an embodiment of the present application. As shown in FIG9 , the data collection method includes the following steps:

[0242] Step 201: The second device sends a first message to the first device, where the first message is used to request data from the target device.

[0243] Step 202: The second device receives a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

[0244] Optionally, the first message carries first indication information, and the first indication information is indication information used to indicate a target data collection mode.

[0245] Optionally, the first message carries at least one of first information, second information, third information, fourth information and fifth information; wherein,

[0246] The first information is related information of the requested data;

[0247] The second information is related information of data that can be shared with the target device;

[0248] The third information is information related to data that can be exchanged with the target device;

[0249] The fourth information is reward information that can be provided by the second device;

[0250] The fifth information is reward information that the second device expects to obtain.

[0251] Optionally, the method further includes:

[0252] In the target data collection mode, the second device performs a data collection operation;

[0253] The data collection operation includes:

[0254] During a data collection process, the second device collects data from the target device, and the second device does not provide data to the target device; or

[0255] During a data collection process, the second device collects data from the target device and provides data to the target device; or

[0256] The second device collects the data of the target device in a data sharing manner; or

[0257] The second device collects data of the target device in a data exchange manner; or

[0258] The second device collects data of the target device based on the reward information; or

[0259] The second device collects data of the target device based on the permission information.

[0260] In which, during a data collection process, the second device collects data from the target device and does not provide data to the target device, which may refer to collecting data in a first mode. During a data collection process, the second device collects data from the target device and provides data to the target device, which may refer to collecting data in a second mode. The second device collects data from the target device in a data sharing manner, which may refer to collecting data in a third mode. The second device collects data from the target device in a data exchange manner, which may refer to collecting data in a fourth mode. The second device collects data from the target device based on reward information, which may refer to collecting data in a fifth mode. The second device collects data from the target device based on permission information, which may refer to collecting data in a sixth mode.

[0261] It should be noted that this embodiment is an implementation of the second device corresponding to the embodiment shown in Figure 8. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 8. To avoid repeated description, this embodiment will not be repeated.

[0262] In related technologies, network-side devices collect terminal data in two scenarios: one in which no authorization is required, such as when the RAN performs L1 or L3 measurements on the terminal; and the other in which authorization is performed based on user permission. In the embodiments of this application, user permission is provided and authorization based on the data collection mode is supported. As the scope of data collection becomes wider and more extensive, when requesting terminal data collection, the user can authorize based on different data collection modes. When a terminal requests data from a network-side device, the network-side device can support authorization based on user permission.

[0263] The data collection method of the embodiment of the present application is described below through several examples.

[0264] Example 1:

[0265] An embodiment of the present application provides a data collection method that supports data sharing, data exchange, or data rewards.

[0266] In one embodiment, a second device (such as a terminal or a network-side device) sends a first message to a network (such as a first device), where the first message is used for a data request and includes at least one of the following:

[0267] Mode indication; request identification.

[0268] The mode indication is used to indicate a data collection mode, and the data collection mode includes at least one of a first mode, a second mode, a third mode, a fourth mode, and a fifth mode.

[0269] One name for the first mode is single-ended mode, which means that either the network or the terminal obtains the required data.

[0270] One name for the second mode is dual-end mode, which means that both the network and the terminal obtain the required content, which may be data, QoS guarantee times, priority enhancement times, traffic quota, voice quota or points, etc.

[0271] The third mode is also known as the shared mode. During a data collection process, the network requests the terminal's collected data, and the terminal also requests the network's collected data. Ultimately, during the data collection process, the network sends the collected data to the terminal, and the terminal sends the collected data to the network.

[0272] One name of the fourth mode is exchange mode, which means that during a data collection process, a network or terminal requests required data in exchange for its existing data.

[0273] The fifth mode, also known as the reward mode, involves the network or terminal offering a valuable reward during a data collection process to request the required data. This reward can include QoS guarantees, priority upgrades, traffic, voice, phone charges, or points. A characteristic of the fifth mode is that after data collection, the relevant reward information must be maintained to ensure that the recipient can use the reward, effectively realizing its value.

[0274] The sixth mode is also known as the permission mode, which means that during a data collection process, the network or terminal requests the required data with its permission to collect data, including the number of network data acquisitions and the amount of network data acquired.

[0275] It should be understood that the above modes can be combined into multiple modes, which are not listed here one by one. For example, the third mode and the fourth mode can be combined into the seventh mode. The characteristic of the seventh mode is that the network and the terminal complete the collaboration during the data collection process, and no subsequent related information maintenance is required.

[0276] It should be noted that the above modes are merely examples of data collection modes. Data collection modes can also be defined in other ways, and the embodiments of this application do not limit the definition of data collection modes. For example, the third, fourth, and fifth modes can be used as sub-modes of the second mode; or the sixth mode can be used as a sub-mode of the first mode.

[0277] The request identifier is used to uniquely identify a data collection request.

[0278] In one embodiment, when the data collection mode is the second mode or the third mode, the first message may further include at least one of the following: first information; second information.

[0279] The first information may include at least one of a collection parameter, a collection target, and a collection method. The first information may be used to indicate the parameters that the second device needs to collect.

[0280] For the acquisition parameters in the first information, taking the first information used to request terminal downlink measurement data as an example, the acquisition parameters include at least one of the following: reference signal received power (RSRP), reference signal received power per branch (RSRPB), reference signal received quality (RSRQ), received signal strength indicator (RSSI), and signal-to-noise and interference ratio (SINR).

[0281] The collection target in the first information is used to indicate which cells the terminal collects data from, and includes at least one of the following:

[0282] Indication information, used to indicate that only serving cell data is to be collected, or that only neighboring cell data is to be collected, or that both serving cell and neighboring cell data need to be collected. For example, for neighboring cell data, the network selects which neighboring cell data to send to the terminal based on implementation;

[0283] Cell Global Identifier (CGI), including PLMN ID and Cell ID;

[0284] Physical cell identity (PCI);

[0285] Carrier frequency information;

[0286] Tracking Area Code TAC;

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

[0288] The collection mode in the first information includes at least one of network request triggering, periodic triggering, and event triggering. The periodic trigger parameter may further include a time interval, where the unit of the time interval may be any one of hours, minutes, seconds, milliseconds, microseconds, frames, subframes, symbols, and time slots. The event trigger parameter includes at least one of a triggering event and a triggering time associated with the triggering time.

[0289] It should be noted that the first message may include the second information without including a mode indication. This situation is equivalent to implicitly indicating that the data collection mode is a data sharing mode.

[0290] In the data sharing mode, both parties collect data after agreeing, and then report the data to each other at the agreed time. The data provided by the second device is data that matches the data collection time provided by the third node.

[0291] The second information includes at least one of a collection parameter, a collection target, and a collection time, and is used to indicate parameters that the second device can share with the third node in this data collection, such as network synchronous collection and shared network data.

[0292] For the collection parameters in the second information, taking the first information as uplink measurement data collected by the network as an example, the collection parameters include at least one of the following: RSRP, RSRPB, RSRQ, RSSI, SINR, radio resource status (for example, Radio Resource Status in the current protocol, 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), PRB usage, PDCCH CCE usage for uplink scheduling, PDCCH CCE usage for downlink scheduling, number of users in RRC connected / inactive state, ratio of the number of users in RRC connected / inactive state to the maximum number of users accommodated, uplink / downlink throughput;

[0293] The collection target in the second information is used to instruct the network which cells' data to collect, such as the global cell identity CGI (such as PLMN ID and Cell ID), physical cell identity (PCI), etc.

[0294] Regarding the collection time in the second information, the collection time includes at least one of the collection start time, end time, time length, collection time interval, and number of sampling points.

[0295] In one embodiment, when the data collection mode is the second mode or the fourth mode, the first message may further include at least one of the following: first information; third information.

[0296] The first information includes at least one collection parameter or content, which is used to indicate the parameters that the second device needs to collect. The first information here can refer to the description of the first information above, and will not be repeated here.

[0297] The third information includes at least one collection parameter or content, which is used to indicate the parameter or content provided by the second device in this data collection, and may include at least one of the following: parameter, time, number of sampling points, etc. Taking paging failure optimization as an example, the parameters in the third information include at least one of the following:

[0298] RNA ID, RA ID, TA ID, gNB ID, cell ID, and terminal ID involved in paging initiation;

[0299] The time of sending the paging message (such as PF, PO, PDCCH occasion, etc.), time period, paging identifier, and DRX / eDRX configuration of the terminal;

[0300] Whether paging optimization mechanisms, such as PEI and Low-Power Wake Up Signals (LP-WUS), are applied when sending paging messages;

[0301] When sending a paging message, the network expects the terminal's RRC state (such as IDLE or inactive), or the corresponding sending mechanism of the paging message (such as RAN paging or core network paging).

[0302] It should be noted that the first message may include the third information but not the mode indication. This situation is equivalent to implicitly indicating that the data collection mode is the data exchange mode.

[0303] In the data exchange mode, the data provided by the second device is already collected data, and the collection time of the data is earlier than the time when the target device collects the data.

[0304] In one embodiment, when the data collection mode is the second mode or the fifth mode, the first message may further include at least one of the following: first information or fourth information.

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

[0306] The fourth information includes at least one parameter or content, which is used to indicate the reward information provided by the second device in this data collection. The reward information may include at least one of the following: reward content, amount, etc.

[0307] The reward content in the reward information includes at least one of the following: QoS guarantee, number of network data acquisition times, priority improvement, traffic, voice, points, etc.

[0308] The amount in the reward information includes at least one of the following:

[0309] Times, such as QoS guarantee times, network data acquisition times, or priority enhancement times;

[0310] duration, such as the duration of a call;

[0311] Traffic or points, such as 100M traffic or 100 points.

[0312] It should be noted that the first message may include the fourth information but not the mode indication. This is equivalent to implicitly indicating that the data collection mode is a data reward mode.

[0313] In one embodiment, when the data collection mode is the first mode or the sixth mode, the first message may further include third information or fifth information, wherein:

[0314] The third information can refer to the description of the third information mentioned above and will not be repeated here.

[0315] The fifth information includes at least one parameter or content, which is used to indicate the reward information that the second device expects to obtain from data sharing, and may include at least one of the following: reward content and amount, etc. The reward information in the fifth information can be referred to the description of the reward information above, and will not be repeated here.

[0316] In one embodiment, a network (e.g., a first device) receives a first message and performs data request authorization. The first device (e.g., a data plane node, an AMF, a wireless access network node, etc.) obtains a privacy profile corresponding to the terminal. For example, the first device requests a privacy profile from a third device (e.g., a UDM). The privacy profile is used for at least one of the following:

[0317] Indicate whether data collection is permitted;

[0318] Indicates whether the first mode allows data collection;

[0319] Indicates whether the second mode allows data collection;

[0320] Indicates whether the third mode allows data collection;

[0321] Indicates whether the fourth mode allows data collection;

[0322] Indicates whether the fifth mode allows data collection;

[0323] Indicates whether the sixth mode allows data collection;

[0324] Indicates the validity period, such as using the start time and end time to indicate the validity period, and whether data collection is allowed or not during the validity period;

[0325] Indicates a valid area. For example, the valid area can be represented by a general geographical area, or an area associated with a terminal, a base station, or an AMF (such as an RNA or a TA). Data collection is allowed or not allowed within the valid area;

[0326] Instruction notification to allow data collection;

[0327] The instruction verification allows data collection, including allowing data collection only after receiving a permission response from the terminal, or allowing data collection whether or not a permission response from the terminal is received.

[0328] It should be noted that the privacy profile corresponding to the above-mentioned terminal can allow or not allow in a certain period of time, or allow or not allow in a certain area, or allow or not allow for a certain data collection mode, or allow after notifying the terminal, or allow after terminal verification.

[0329] In one embodiment, the first device can subscribe to changes in the terminal's privacy profile. If the terminal's privacy profile changes, the first device can obtain the updated terminal's privacy profile. The first device performs authorization based on the terminal's implicit profile; if data collection is not permitted, the authorization is rejected. The network (the first device or another network-side device) sends a response to the second device, rejecting the data request; if data collection is permitted, the authorization is granted, and subsequent steps can be performed.

[0330] If authorization is granted and the first message requests network data, the network sends a second message to the second device. If authorization is granted and the first message requests terminal data, the network sends a second message to the terminal. The second message includes at least one of a mode indicator, a request identifier, first information, second information, third information, fourth information, or fifth information. Upon receiving the second message, the terminal determines whether to accept the data request. If so, it sends a third message to provide the requested data.

[0331] Embodiment 2:

[0332] In this embodiment, the first message is used to request data request authorization for terminal (User Equipment, UE) data.

[0333] In this embodiment, the second device is described as a network-side device, such as a network function node, an application function, etc. The first device can be a network function node, such as a data plane function node, a radio access network node, an AMF or NEF core network function node. The data collection method includes the following steps:

[0334] (1) The second device sends a first message to the network (such as the first device), where the first message is used for data request and includes at least one of the following: a mode indication; a request identifier; first information; second information; third information; fourth information; and fifth information.

[0335] Among them, the mode indication is used to indicate a data collection mode, and the data collection mode includes at least one of a first mode, a second mode, a third mode, a fourth mode, a fifth mode, and a sixth mode.

[0336] One name for the first mode is single-ended mode, which means that either the network or the UE obtains the required data.

[0337] The second mode is also known as dual-ended mode. This means both the network and the UE obtain the required content. The required content may include data, QoS guarantees, priority boosts, traffic quotas, voice quotas, or credits.

[0338] The third mode is also known as the shared mode. In this shared mode, during a data collection process, the network requests the UE for the data it has collected, and the UE also requests the network for the data it has collected. Ultimately, during the data collection process, the network sends the collected data to the UE, and the UE sends the collected data to the network.

[0339] One name of the fourth mode is exchange mode, which means that during a data collection process, the network or UE requests required data in exchange for its existing data.

[0340] The fifth mode, also known as the reward mode, involves the network or UE requesting the required data in exchange for a valuable reward during a data collection process. This reward can include QoS guarantees, priority upgrades, data traffic, voice calls, phone charges, or points. A characteristic of the fifth mode is that after data collection, the relevant reward information must be maintained to ensure that the recipient can use the reward, effectively realizing its value.

[0341] The sixth mode is also known as the permission mode, which means that during a data collection process, the network or UE requests the required data with permission to collect data, including the number of network data acquisitions and the amount of network data acquired.

[0342] The request identifier is used to uniquely identify a data collection request.

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

[0344] The second information includes at least one collection parameter or content, which is used to indicate a parameter that the second device can share with the target device in this data collection.

[0345] The third information includes at least one acquisition parameter or content, which is used to indicate the parameter or content provided by the second device in this data collection, and may include at least one of the following: parameter, time, number of sampling points, etc.

[0346] The fourth information includes at least one parameter or content, which is used to indicate the reward information provided by the second device in this data collection, and may include at least one of the following: reward content and quantity, etc.

[0347] The fifth information includes at least one parameter or content, which is used to indicate the reward information that the second device expects to obtain in data sharing, and may include at least one of the following: reward content and amount, etc.

[0348] Step (2): The first device receives the first message and performs data request authorization.

[0349] One authorization method is that a first device (such as a data plane node, AMF, radio access network node, etc.) obtains a privacy profile corresponding to the UE, for example, the first device requests a privacy profile from a third device (such as a UDM). The privacy profile is used for at least one of the following:

[0350] Indicate whether data collection is permitted;

[0351] Indicates whether the first mode allows data collection;

[0352] Indicates whether the second mode allows data collection;

[0353] Indicates whether the third mode allows data collection;

[0354] Indicates whether the fourth mode allows data collection;

[0355] Indicates whether the fifth mode allows data collection;

[0356] Indicates whether the sixth mode allows data collection;

[0357] Indicates the validity period, such as using the start time and end time to indicate the validity period, and whether data collection is allowed or not during the validity period;

[0358] Valid area, for example, the valid area can be represented by a general geographical area, or an area associated with the UE, base station or AMF (such as RNA, TA, etc.), and data collection is allowed or not allowed within the valid area;

[0359] Notify the UE being collected and allow data collection;

[0360] Data collection requires notification to the end user and verification, and data collection is only permitted if the end user agrees or if no response is received;

[0361] Data collection needs to be notified to the end user and verified, and data collection is only allowed with the end user's authorization.

[0362] It should be noted that, when the first message does not include a mode indication, the first device may map the first message to a corresponding data collection mode according to whether the first message includes the second information, the third information, the fourth information, and the fifth information.

[0363] The first device performs authorization based on the UE's implicit profile. If data collection is not permitted, the authorization is rejected. The network (the first device or other node) sends a response, rejecting the data request. If data collection is permitted, the authorization is accepted, and the subsequent steps are continued.

[0364] Step (3): If the authorization is passed, the first device sends a second message to the UE, where the second message includes at least one of a mode indication, a request identifier, the first information, the second information, the third information, the fourth information, or the fifth information.

[0365] Step (4): The UE determines whether to accept the data request. If the data request is accepted, the UE sends a third message to provide the requested data.

[0366] Example 3:

[0367] In this embodiment, the first message is used by the UE to request data request authorization for network data.

[0368] In this embodiment, the second device is a UE as an example for illustration, and the first device may be a network function node, such as a data plane function node, a radio access network node, an AMF or NEF or other core network function node. Before step (1), the UE may obtain permission for network data acquisition by providing data, or the UE may obtain permission for network data acquisition by purchasing a package or other means. The data collection method includes the following steps:

[0369] (1) The UE (second device) sends a first message to the network (such as the first device), where the first message is used for data request and includes at least one of the following: a mode indication; a request identifier; and first information.

[0370] The mode indication is used to indicate a data collection mode, and the data collection mode includes at least one of a first mode, a second mode, a third mode, a fourth mode, a fifth mode, and a sixth mode. In this embodiment, the data collection mode indicated by the first message is the sixth mode.

[0371] The request identifier is used to uniquely identify a data collection request.

[0372] The first information includes at least one collection parameter or content, which is used to indicate the parameters that the second device needs to collect. Taking paging failure optimization as an example, the parameters include at least one of the following:

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

[0374] The time of sending the paging message (such as PF, PO, PDCCH occasion, etc.), time period, paging identifier, and UE DRX or eDRX configuration;

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

[0376] When sending a paging message, the network expects the UE RRC state (such as IDLE or inactive), or the corresponding sending mechanism of the paging message (such as RAN paging or core network paging).

[0377] (2) The first device receives the first message and performs data request authorization.

[0378] One authorization method is that a first device (such as a data plane node, AMF, radio access network node, etc.) obtains a configuration file corresponding to the UE, for example, the first device requests the configuration file from a third device (such as a UDM). The configuration file is used for at least one of the following:

[0379] Indicates whether the UE has network data acquisition permission;

[0380] Indicates the number of network data acquisitions that the UE has;

[0381] Indicates the amount of network data acquisition that the UE has;

[0382] Indicates the event of network data acquisition by the UE.

[0383] When the first message does not include a mode indication, the first device may map the first message to the corresponding data collection mode based on whether the first message includes the fifth information. The first device performs authorization based on the UE's profile. If data collection is not permitted, the authorization is rejected. The network (first device or other node) sends a response, rejecting the data request. If data collection is permitted, the authorization is granted, and subsequent steps are performed.

[0384] (3) The first device sends a second message to the second device, where the second message is used to provide the data requested by the UE. The first device sends a permission event to the billing function or network function node, where the permission event includes the UE identifier, permission content or quantity, etc. For example, if the permission content is the number of network data acquisitions or the amount of network data acquired, the second device sends a reward event to the billing function node.

[0385] This embodiment of the present application proposes a mode-based data collection authorization method. When requesting to collect UE data, this embodiment supports user authorization and authentication based on different collection modes. When the UE requests network data, the network also supports authorization based on user permission. This provides a more flexible data collection authorization method, which not only facilitates the network's acquisition of UE data, but also helps UEs obtain network data.

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

[0387] Please refer to FIG10 , which is a structural diagram of a data collection device provided in an embodiment of the present application. The first device includes the data collection device. As shown in FIG10 , the data collection device 300 includes:

[0388] A receiving module 301 is configured to receive a first message sent by a second device, where the first message is used to request data from a target device;

[0389] The determination module 302 is configured to determine whether the second device is allowed to collect data of the target device.

[0390] Optionally, the determining module is specifically configured to perform at least one of the following:

[0391] determining whether to allow the second device to collect data of the target device in a target data collection mode;

[0392] determining whether to allow the second device to collect data of the target device for a target service type;

[0393] Determine whether to allow the second device to collect data of the target device for data processing, data storage, or data service.

[0394] Optionally, the first message carries first indication information, first information, second information, third information, fourth information or fifth information; the target data collection mode is determined based on the first indication information, the first information, the second information, the third information, the fourth information or the fifth information; wherein,

[0395] The first indication information is indication information for indicating the target data collection mode;

[0396] The first information is related information of the requested data;

[0397] The second information is related information of data that can be shared with the target device;

[0398] The third information is information related to data that can be exchanged with the target device;

[0399] The fourth information is reward information that can be provided by the second device;

[0400] The fifth information is reward information that the second device expects to obtain.

[0401] Optionally, when the target device is a terminal, the determining module is specifically configured to:

[0402] Obtaining first configuration information corresponding to the terminal;

[0403] Determine whether to allow the second device to collect data of the terminal based on the first configuration information.

[0404] Optionally, the first configuration information is used to indicate at least one of the following:

[0405] Whether to allow collection of data from the terminal;

[0406] The validity period for allowing the collection of data from the terminal;

[0407] The validity period during which the collection of data from the terminal is not permitted;

[0408] The area where data collection of the terminal is allowed;

[0409] Areas where data collection of the terminal is not permitted;

[0410] Permissible modes of data collection;

[0411] Impermissible patterns of data collection;

[0412] allowing collection of data of the terminal upon notifying the terminal;

[0413] the data collection modes permitted with notification to said terminal;

[0414] In the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, allowing the collection of data from the terminal; or, in the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, not allowing the collection of data from the terminal;

[0415] In the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, allowing the collection of data from the terminal using the first data collection mode; or, in the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, not allowing the collection of data from the terminal using the second data collection mode;

[0416] Types of services allowed;

[0417] Types of services not permitted;

[0418] Allowing the collection of data from the terminal for data processing, data storage or data services;

[0419] It is not allowed to collect data from the terminal for data processing, data storage or data services;

[0420] A node that allows data processing, data storage, or data service.

[0421] Optionally, when the target device is a network-side device and the second device is a terminal, the determining module is specifically configured to:

[0422] Obtaining second configuration information corresponding to the terminal;

[0423] Determine whether to allow the terminal to collect data of the network-side device based on the second configuration information.

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

[0425] second indication information, where the second indication information is used to indicate whether the terminal has permission to obtain data from the network-side device;

[0426] third indication information, where the third indication information is used to indicate that the terminal has a permitted number of times of obtaining data from the network-side device, where the permitted number of times represents a number of times the terminal can obtain data from the network-side device;

[0427] fourth indication information, where the fourth indication information is used to indicate that the terminal has a permitted data volume for acquiring data from the network-side device, where the permitted data volume represents a volume of data that can be acquired from the network-side device;

[0428] The fifth indication information is used to indicate that the terminal has a permission event for obtaining data of the network-side device, and the permission event represents an event in which the network-side device can be obtained.

[0429] Optionally, the device further comprises:

[0430] The first sending module is configured to send a second message to the second device, where the second message is used to indicate whether the second device is allowed to collect data of the target device.

[0431] Optionally, the device further comprises:

[0432] The second sending module is configured to send a third message to the target device if the first device determines to allow the second device to collect data of the target device, wherein the third message is used to instruct the target device to provide data.

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

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

[0435] Please refer to FIG11 , which is a structural diagram of a data collection device provided in an embodiment of the present application. The second device includes the data collection device. As shown in FIG11 , the data collection device 400 includes:

[0436] A sending module 401 is configured to send a first message to a first device, where the first message is used to request data from a target device;

[0437] The receiving module 402 is configured to receive a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

[0438] Optionally, the first message carries first indication information, and the first indication information is indication information used to indicate a target data collection mode.

[0439] Optionally, the first message carries at least one of first information, second information, third information, fourth information and fifth information; wherein,

[0440] The first information is related information of the requested data;

[0441] The second information is related information of data that can be shared with the target device;

[0442] The third information is information related to data that can be exchanged with the target device;

[0443] The fourth information is reward information that can be provided by the second device;

[0444] The fifth information is reward information that the second device expects to obtain.

[0445] Optionally, the device further comprises:

[0446] An execution module, configured to execute a data collection operation in the target data collection mode;

[0447] The data collection operation includes:

[0448] During a data collection process, the second device collects data from the target device, and the second device does not provide data to the target device; or

[0449] During a data collection process, the second device collects data from the target device and provides data to the target device; or

[0450] The second device collects the data of the target device in a data sharing manner; or

[0451] The second device collects data of the target device in a data exchange manner; or

[0452] The second device collects data of the target device based on the reward information; or

[0453] The second device collects data of the target device based on the permission information.

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

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

[0456] Optionally, as shown in FIG12 , an embodiment of the present application further provides a communication device 500, comprising a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be run on the processor 501. For example, when the communication device 500 is a first device, the program or instruction, when executed by the processor 501, implements the various steps of the data collection method embodiment applied to the first device, and can achieve the same technical effect. To avoid repetition, it is not described here. When the communication device 500 is a second device, the program or instruction, when executed by the processor 501, implements the various steps of the data collection method embodiment applied to the second device, and can achieve the same technical effect. To avoid repetition, it is not described here.

[0457] 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 in the method embodiment shown in Figure 8 or Figure 9. This terminal embodiment corresponds to the first device or 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 effects.

[0458] Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

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

[0460] Those skilled in the art will appreciate that the terminal 600 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 610 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG13 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.

[0461] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042, and the GPU 6041 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 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and at least one of other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

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

[0463] The memory 609 can be used to store software programs or instructions and various data. The memory 609 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 609 may include a volatile memory or a non-volatile memory, or the memory 609 may include both volatile and non-volatile memories. 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. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0464] Processor 610 may include one or more processing units. Optionally, processor 610 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 610.

[0465] In the case where the terminal is a first device, the processor 610 is configured to:

[0466] a receiving module, configured to receive a first message sent by a second device, wherein the first message is used to request data from a target device;

[0467] A determination module is configured to determine whether the second device is allowed to collect data of the target device.

[0468] Optionally, the processor 610 is specifically configured to perform at least one of the following:

[0469] determining whether to allow the second device to collect data of the target device in a target data collection mode;

[0470] determining whether to allow the second device to collect data of the target device for a target service type;

[0471] Determine whether to allow the second device to collect data of the target device for data processing, data storage, or data service.

[0472] Optionally, the first message carries first indication information, first information, second information, third information, fourth information or fifth information; the target data collection mode is determined based on the first indication information, the first information, the second information, the third information, the fourth information or the fifth information; wherein,

[0473] The first indication information is indication information for indicating the target data collection mode;

[0474] The first information is related information of the requested data;

[0475] The second information is related information of data that can be shared with the target device;

[0476] The third information is information related to data that can be exchanged with the target device;

[0477] The fourth information is reward information that can be provided by the second device;

[0478] The fifth information is reward information that the second device expects to obtain.

[0479] Optionally, when the target device is a terminal, the processor 610 is specifically configured to:

[0480] Obtaining first configuration information corresponding to the terminal;

[0481] Determine whether to allow the second device to collect data of the terminal based on the first configuration information.

[0482] Optionally, the first configuration information is used to indicate at least one of the following:

[0483] Whether to allow collection of data from the terminal;

[0484] The validity period for allowing the collection of data from the terminal;

[0485] The validity period during which the collection of data from the terminal is not permitted;

[0486] The area where data collection of the terminal is allowed;

[0487] Areas where data collection of the terminal is not permitted;

[0488] Permissible modes of data collection;

[0489] Impermissible patterns of data collection;

[0490] allowing collection of data of the terminal upon notifying the terminal;

[0491] the data collection modes permitted with notification to said terminal;

[0492] In the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, allowing the collection of data from the terminal; or, in the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, not allowing the collection of data from the terminal;

[0493] In the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, allowing the collection of data from the terminal using the first data collection mode; or, in the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, not allowing the collection of data from the terminal using the second data collection mode;

[0494] Types of services allowed;

[0495] Types of services not permitted;

[0496] Allowing the collection of data from the terminal for data processing, data storage or data services;

[0497] It is not allowed to collect data from the terminal for data processing, data storage or data services;

[0498] A node that allows data processing, data storage, or data service.

[0499] Optionally, when the target device is a network-side device and the second device is a terminal, the processor 610 is specifically configured to:

[0500] Obtaining second configuration information corresponding to the terminal;

[0501] Determine whether to allow the terminal to collect data of the network-side device based on the second configuration information.

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

[0503] second indication information, where the second indication information is used to indicate whether the terminal has permission to obtain data from the network-side device;

[0504] third indication information, where the third indication information is used to indicate that the terminal has a permitted number of times of obtaining data from the network-side device, where the permitted number of times represents a number of times the terminal can obtain data from the network-side device;

[0505] fourth indication information, where the fourth indication information is used to indicate that the terminal has a permitted data volume for acquiring data from the network-side device, where the permitted data volume represents a volume of data that can be acquired from the network-side device;

[0506] The fifth indication information is used to indicate that the terminal has a permission event for obtaining data of the network-side device, and the permission event represents an event in which the network-side device can be obtained.

[0507] Optionally, the radio frequency unit 601 is configured to send a second message to the second device, where the second message is used to indicate whether the second device is allowed to collect data of the target device.

[0508] Optionally, the radio frequency unit 601 is configured to: when the first device determines to allow the second device to collect data of the target device, send a third message to the target device, where the third message is used to instruct the target device to provide data.

[0509] Wherein, when the terminal is a second device, the radio frequency unit 601 is configured to:

[0510] Sending a first message to a first device, where the first message is used to request data from a target device;

[0511] A second message sent by the first device is received, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

[0512] Optionally, the first message carries first indication information, and the first indication information is indication information used to indicate a target data collection mode.

[0513] Optionally, the first message carries at least one of first information, second information, third information, fourth information and fifth information; wherein,

[0514] The first information is related information of the requested data;

[0515] The second information is related information of data that can be shared with the target device;

[0516] The third information is information related to data that can be exchanged with the target device;

[0517] The fourth information is reward information that can be provided by the second device;

[0518] The fifth information is reward information that the second device expects to obtain.

[0519] Optionally, the processor 610 is configured to: perform a data collection operation in the target data collection mode;

[0520] The data collection operation includes:

[0521] During a data collection process, the second device collects data from the target device, and the second device does not provide data to the target device; or

[0522] During a data collection process, the second device collects data from the target device and provides data to the target device; or

[0523] The second device collects the data of the target device in a data sharing manner; or

[0524] The second device collects data of the target device in a data exchange manner; or

[0525] The second device collects data of the target device based on the reward information; or

[0526] The second device collects data of the target device based on the permission information.

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

[0528] Specifically, the terminal of the embodiment of the present application also includes: instructions or programs stored in the memory 609 and executable on the processor 610. The processor 610 calls the instructions or programs in the memory 609 to execute the methods of the modules shown in FIG10 or FIG11 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0529] 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 8 or Figure 9. This network-side device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0530] Specifically, an embodiment of the present application further provides a network-side device. The network-side device can be a first device or a second device. As shown in Figure 14, the network-side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information via the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be transmitted and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and sends it through the antenna 701.

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

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

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

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

[0535] Specifically, an embodiment of the present application further provides a network-side device. The network-side device can be a first device or a second device. As shown in FIG15 , the network-side device 800 includes: a processor 801, a network interface 802, and a memory 803. The network interface 802 is, for example, a common public radio interface (CPRI).

[0536] Specifically, the network side device 800 of the embodiment of the present application also includes: instructions or programs stored in the memory 803 and executable on the processor 801. The processor 801 calls the instructions or programs in the memory 803 to execute the methods executed by the modules shown in FIG10 or FIG11 and achieve the same technical effect. To avoid repetition, they will not be described here.

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

[0538] The processor is the processor in the terminal or network-side device described in the above embodiments. 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.

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

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

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

[0542] An embodiment of the present application also provides a data collection 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 applied to the first device as described above, and the second device can be used to execute the steps of the data collection method applied to the second device as described above.

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

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

[0545] 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 receives a first message sent by the second device, where the first message is used to request data from a target device; The first device determines whether to allow the second device to collect data of the target device.

2. The method according to claim 1, wherein The first device determines whether to allow the second device to collect data of the target device, including at least one of the following: determining, by the first device, whether to allow the second device to collect data of the target device in a target data collection mode; determining, by the first device, whether to allow the second device to collect data of the target device for a target service type; The first device determines whether to allow the second device to collect data of the target device for data processing, data storage, or data service.

3. The method according to claim 2, wherein: The first message carries first indication information, first information, second information, third information, fourth information or fifth information; The target data collection mode is determined based on the first indication information, the first information, the second information, the third information, the fourth information or the fifth information; wherein, The first indication information is indication information for indicating the target data collection mode; The first information is related information of the requested data; The second information is related information of data that can be shared with the target device; The third information is information related to data that can be exchanged with the target device; The fourth information is reward information that can be provided by the second device; The fifth information is reward information that the second device expects to obtain.

4. The method according to any one of claims 1 to 3, wherein In a case where the target device is a terminal, the first device determining whether to allow the second device to collect data of the target device includes: The first device obtains first configuration information corresponding to the terminal; The first device determines whether to allow the second device to collect data of the terminal based on the first configuration information.

5. The method according to claim 4, wherein The first configuration information is used to indicate at least one of the following: Whether to allow collection of data from the terminal; The validity period for allowing the collection of data from the terminal; The validity period during which the collection of data from the terminal is not permitted; The area where data collection of the terminal is allowed; Areas where data collection of the terminal is not permitted; Permissible modes of data collection; Impermissible patterns of data collection; allowing collection of data of the terminal upon notifying the terminal; the data collection modes permitted with notification to said terminal; In the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, allowing the collection of data from the terminal; Alternatively, in the case of notifying the terminal and performing terminal privacy verification, if no response from the terminal is received, then collection of data from the terminal is not permitted; In the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, allowing the collection of data from the terminal using the first data collection mode; or, in the case of notifying the terminal and performing terminal privacy verification, if no response is received from the terminal, not allowing the collection of data from the terminal using the second data collection mode; Types of services allowed; Types of services not permitted; Allowing the collection of data from the terminal for data processing, data storage or data services; It is not allowed to collect data from the terminal for data processing, data storage or data services; A node that allows data processing, data storage, or data service.

6. The method according to any one of claims 1 to 4, wherein In a case where the target device is a network-side device and the second device is a terminal, the first device determining whether to allow the second device to collect data of the target device includes: The first device obtains second configuration information corresponding to the terminal; The first device determines whether to allow the terminal to collect data of the network-side device based on the second configuration information.

7. The method according to claim 6, wherein: The second configuration information includes at least one of the following: second indication information, where the second indication information is used to indicate whether the terminal has permission to obtain data from the network-side device; third indication information, where the third indication information is used to indicate that the terminal has a permitted number of times of obtaining data from the network-side device, where the permitted number of times represents a number of times the terminal can obtain data from the network-side device; fourth indication information, where the fourth indication information is used to indicate that the terminal has a permitted data volume for acquiring data from the network-side device, where the permitted data volume represents a volume of data that can be acquired from the network-side device; The fifth indication information is used to indicate that the terminal has a permission event for obtaining data of the network-side device, and the permission event represents an event in which the network-side device can be obtained.

8. The method according to any one of claims 1 to 7, further comprising: The first device sends a second message to the second device, where the second message is used to indicate whether the second device is allowed to collect data of the target device.

9. The method according to any one of claims 1 to 8, further comprising: In a case where the first device determines to allow the second device to collect data of the target device, the first device sends a third message to the target device, where the third message is used to instruct the target device to provide data.

10. A data collection method comprising: The second device sends a first message to the first device, where the first message is used to request data from the target device; The second device receives a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

11. The method according to claim 10, wherein: The first message carries first indication information, where the first indication information is indication information used to indicate a target data collection mode.

12. The method according to claim 10 or 11, wherein: The first message carries at least one of the first information, the second information, the third information, the fourth information and the fifth information; wherein, The first information is related information of the requested data; The second information is related information of data that can be shared with the target device; The third information is information related to data that can be exchanged with the target device; The fourth information is reward information that can be provided by the second device; The fifth information is reward information that the second device expects to obtain.

13. The method according to any one of claims 10 to 12, further comprising: In the target data collection mode, the second device performs a data collection operation; The data collection operation includes: During a data collection process, the second device collects data from the target device, and the second device does not provide data to the target device; or During a data collection process, the second device collects data from the target device and provides data to the target device; or The second device collects the data of the target device in a data sharing manner; or The second device collects data of the target device in a data exchange manner; or The second device collects data of the target device based on the reward information; or The second device collects data of the target device based on the permission information.

14. A data collection device comprising: a receiving module, configured to receive a first message sent by a second device, wherein the first message is used to request data from a target device; A determination module is configured to determine whether the second device is allowed to collect data of the target device.

15. The device according to claim 14, wherein The determining module is specifically configured to: determining whether to allow the second device to collect data of the target device in a target data collection mode; determining whether to allow the second device to collect data of the target device for a target service type; Determine whether to allow the second device to collect data of the target device for data processing, data storage, or data service.

16. The device according to claim 14 or 15, wherein The first message carries first indication information, first information, second information, third information, fourth information or fifth information; The target data collection mode is determined based on the first indication information, the first information, the second information, the third information, the fourth information or the fifth information; wherein, The first indication information is indication information for indicating a target data collection mode; The first information is related information of the requested data; The second information is related information of data that can be shared with the target device; The third information is information related to data that can be exchanged with the target device; The fourth information is reward information that can be provided by the second device; The fifth information is reward information that the second device expects to obtain.

17. The device according to any one of claims 14 to 16, wherein: In the case where the target device is a terminal, the determining module is specifically configured to: Obtaining first configuration information corresponding to the terminal; Determine whether to allow the second device to collect data of the terminal based on the first configuration information.

18. A data collection device comprising: A sending module, configured to send a first message to a first device, wherein the first message is used to request data of a target device; The receiving module is configured to receive a second message sent by the first device, where the second message is used to indicate whether the first device allows the second device to collect data of the target device.

19. The device according to claim 18, wherein The first message carries first indication information, where the first indication information is indication information used to indicate a target data collection mode.

20. The device according to claim 18 or 19, wherein The first message carries at least one of the first information, the second information, the third information, the fourth information and the fifth information; wherein, The first information is related information of the requested data; The second information is related information of data that can be shared with the target device; The third information is information related to data that can be exchanged with the target device; The fourth information is reward information that can be provided by the second device; The fifth information is reward information that the second device expects to obtain.

21. 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 according to any one of claims 1 to 9 are implemented, or the steps of the data collection method according to any one of claims 10 to 13 are implemented.

22. A chip comprising 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 data collection method according to any one of claims 1 to 9, or to implement the steps of the data collection method according to any one of claims 10 to 13.

23. 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 9, or implements the steps of the data collection method according to any one of claims 10 to 13.

24. A computer program / program product, which, when executed by at least one processor, implements the steps of the data collection method according to any one of claims 1 to 9, or implements the steps of the data collection method according to any one of claims 10 to 13.

Images