Data acquisition method, network element and terminal

Abstract

The application discloses a data collection method, a network element and a terminal, and belongs to the communication field. The data collection method comprises the following steps: a first network element acquires first information, wherein the first information is information related to data collection provided by a first terminal; and the first network element performs at least one of the following: sending the first information to the first terminal; determining to perform data collection on the first terminal based on the first information; determining second information; and sending the second information to the first terminal.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a data acquisition method, network element, and terminal. Background Technology

[0002] In communication systems, network-side devices can collect data from terminals and use it for training artificial intelligence (AI) models. Specifically, for terminals for which users have authorized data collection, network-side devices can initiate data collection processes at any time as needed.

[0003] However, since users only authorize data collection, and the process of collecting data from the terminal is initiated by the network-side device, when too much data needs to be collected, the terminal will need to continuously collect data, increasing the terminal's power consumption. Summary of the Invention

[0004] This application provides a data acquisition method, network element, and terminal that can reduce the power consumption of the terminal.

[0005] Firstly, a data acquisition method is provided, executed by a first network element, the method comprising:

[0006] The first network element acquires first information, which is information related to data collection provided by the first terminal.

[0007] The first network element performs at least one of the following:

[0008] Send the first information to the first terminal;

[0009] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0010] Determine the second piece of information;

[0011] Send the second information to the first terminal.

[0012] Secondly, a data acquisition method is provided, executed by a first terminal, the method comprising:

[0013] The first terminal performs at least one of the following:

[0014] Obtain first information;

[0015] Send the first information to the first network element, the second network element, or the third network element;

[0016] Decide whether to accept or refuse data collection;

[0017] The second information is determined based on the first information or the second information is received from the first network element;

[0018] The first information refers to the information related to data collection provided by the first terminal.

[0019] Thirdly, a data acquisition method is provided, executed by a second network element, the method comprising:

[0020] The second network element acquires the first information, which is information related to data collection provided by the first terminal.

[0021] The second network element sends the first information to the first network element.

[0022] Fourthly, a data acquisition method is provided, executed by a third network element, which includes:

[0023] The third network element performs at least one of the following:

[0024] Obtain first information;

[0025] Send the identification information of the terminals in the third area to the first network element;

[0026] Send information related to data collection provided by terminals in the third area to the first network element;

[0027] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0028] Fifthly, a data acquisition device is provided, comprising:

[0029] Processing module and sending module;

[0030] The processing module is used to acquire first information, which is information related to data collection provided by the first terminal.

[0031] The processing module is also configured to perform at least one of the following:

[0032] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0033] Determine the second piece of information;

[0034] Or the sending module may be used to perform at least one of the following:

[0035] Send the first information to the first terminal;

[0036] Send the second information to the first terminal.

[0037] Sixthly, a data acquisition device is provided, comprising:

[0038] Processing module, sending module, and receiving module;

[0039] The processing module is configured to perform at least one of the following:

[0040] Obtain first information;

[0041] Decide whether to accept or refuse data collection;

[0042] The second information is determined based on the first information;

[0043] Alternatively, the sending module may be used to send first information to a first network element, a second network element, or a third network element;

[0044] Alternatively, the receiving module may be used to receive second information from the first network element;

[0045] The first information is information related to data collection provided by the first terminal.

[0046] Seventhly, a data acquisition device is provided, comprising:

[0047] The processing module is used to acquire first information, which is information related to data collection provided by the first terminal;

[0048] The sending module is used to send the first information to the first network element.

[0049] Eighthly, a data acquisition device is provided, comprising:

[0050] Processing unit and sending module;

[0051] The processing module is used to acquire the first information;

[0052] Or the sending module may be used to perform at least one of the following:

[0053] Send the identification information of the terminals in the third area to the first network element;

[0054] Send information related to data collection provided by terminals in the third area to the first network element;

[0055] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0056] Ninth aspect, a data acquisition apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect, or implement the steps of the method described in the fourth aspect.

[0057] In a tenth aspect, a network element is provided, including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect, or implementing the steps of the method described in the third aspect, or implementing the steps of the method described in the fourth aspect.

[0058] Eleventhly, a first network element is provided, including a processor and a communication interface;

[0059] The processor is used to acquire first information, which is information related to data collection provided by the first terminal.

[0060] The processor is also configured to perform at least one of the following:

[0061] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0062] Determine the second piece of information;

[0063] Or the communication interface may be used to perform at least one of the following:

[0064] Send the first information to the first terminal;

[0065] Send the second information to the first terminal.

[0066] In a twelfth aspect, a second network element is provided, including a processor and a communication interface, wherein the processor is used to acquire first information, the first information being data collection-related information provided by a first terminal; and the communication interface is used to send the first information to the first network element.

[0067] In the thirteenth aspect, a third network element is provided, including a processor and a communication interface;

[0068] The processor is used to acquire first information;

[0069] Or the communication interface may be used to perform at least one of the following:

[0070] Send the identification information of the terminals in the third area to the first network element;

[0071] Send information related to data collection provided by terminals in the third area to the first network element;

[0072] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0073] In a fourteenth aspect, a first terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0074] In the fifteenth aspect, a first terminal is provided, including a processor and a communication interface;

[0075] The processor is configured to perform at least one of the following:

[0076] Obtain first information;

[0077] Decide whether to accept or refuse data collection;

[0078] The second information is determined based on the first information;

[0079] Alternatively, the communication interface may be used to send first information to a first network element, a second network element, or a third network element;

[0080] Alternatively, the communication interface may be used to receive second information from the first network element;

[0081] The first information is information related to data collection provided by the first terminal.

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

[0083] In a seventeenth aspect, a wireless communication system is provided, comprising: a first terminal and at least one of the following: a first network element, a second network element, and a third network element, wherein the first network element is available to perform the steps of the method described in the first aspect, the first terminal is available to perform the steps of the method described in the second aspect, the second network element is available to perform the steps of the method described in the third aspect, and the third network element is available to perform the steps of the method described in the fourth aspect.

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

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

[0086] In this embodiment, when the first network element sends the first information to the first terminal, since the first information is data collection-related information provided by the first terminal, the data collection performed by the first terminal can be restricted through the first information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. When the first network element determines to perform data collection on the first terminal based on the first information, unnecessary collection triggered by the first network element can be reduced, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. When the first network element sends second information or determines second information to the first terminal, the first terminal can perform data collection based on the second information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. Attached Figure Description

[0087] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application.

[0088] Figure 2 This is a schematic diagram of a data collection process initiated by a network-side device according to an embodiment of this application.

[0089] Figure 3 This is a schematic flowchart illustrating a data acquisition method performed by a first network element according to an embodiment of this application.

[0090] Figure 4 This is a schematic flowchart of a data acquisition method executed by a first terminal according to an embodiment of this application.

[0091] Figure 5 This is a schematic flowchart illustrating a data acquisition method performed by a second network element according to an embodiment of this application.

[0092] Figure 6This is a schematic flowchart illustrating a data acquisition method performed by a third network element according to an embodiment of this application.

[0093] Figure 7 This is a schematic flowchart illustrating a data acquisition method provided in this application embodiment, in which a first terminal performs data acquisition based on first information stored locally on the first terminal.

[0094] Figure 8 This is a schematic flowchart illustrating a data acquisition method provided in this application embodiment, in which a first network element obtains first information from other network elements and determines to perform data acquisition on a first terminal based on the first information.

[0095] Figure 9 This is a schematic flowchart illustrating a data acquisition method provided in this application embodiment, in which a first terminal obtains first information from a first network element and performs data acquisition based on the first information.

[0096] Figure 10 This is a schematic flowchart illustrating a data acquisition method provided in this application embodiment, in which a first network element determines to perform data acquisition on a first terminal based on first information stored locally by the first network element.

[0097] Figure 11 This is an illustrative flowchart of another data acquisition method provided in this application embodiment, in which a first network element obtains first information from other network elements and determines to perform data acquisition on a first terminal based on the first information.

[0098] Figure 12 This is a schematic block diagram of a data acquisition device provided in an embodiment of this application.

[0099] Figure 13 This is a schematic block diagram of another data acquisition device provided in the embodiments of this application.

[0100] Figure 14 This is a schematic block diagram of another data acquisition device provided in the embodiments of this application.

[0101] Figure 15 This is a schematic block diagram of another data acquisition device provided in the embodiments of this application.

[0102] Figure 16 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0103] Figure 17 This is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application.

[0104] Figure 18 This is a schematic block diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

[0112] To facilitate a better understanding of the embodiments of this application, the related technologies are described.

[0113] In the 5G network framework, terminals can utilize artificial intelligence (AI) models to better perform operations such as beam measurement or positioning. These models can be trained by the user equipment (UE), the network, or a third party. To support network-side equipment in training these models, the network-side equipment needs to collect training data from the terminals for model training.

[0114] In the AI ​​positioning technology of R19, the Local Location Function (LMF) first determines the Area of ​​Interest (AOI) for data collection. It then uses the Network Rendering Service (NRF) to locate the AMF covering that AOI. Next, the LMF queries the AMF for information about the UEs within that AOI (e.g., UE identifier, UE positioning capabilities, etc.). Following this, it checks the user consent of all UEs within the AOI. The user consent information indicates whether data collection of the UE is authorized. For UEs authorized for data collection, the LMF can initiate a data collection process to obtain positioning-related data. Specifically, for example... Figure 2 As shown, the data collection process 200 includes:

[0115] S201, LMF sends a discovery request to NRF.

[0116] For example, the discovery request could be Nnrf_NFDiscovery_Request.

[0117] S202, NRF sends a response to the discovery request to LMF.

[0118] For example, the response to this discovery request could be an Nnrf_NFDiscovery_Request Response.

[0119] S203, LMF sends a query request to AMF.

[0120] For example, the query request could be Namf_EventExposure_Subscribe, which can be used to request the identification information of any UE in the AOI (Presence in AOI).

[0121] S204, AMF sends a response to the query request to LMF.

[0122] For example, the response to this query request could be Namf_EventExposure_Subscribe, which could include identification information for any UE in the AOI.

[0123] S205, LMF examines user intent for data collection for each SUPI from UDM.

[0124] For example, LMF sends a request for user consent information for each SUPI to UDM, and obtains the user consent information for each SUPI from UDM.

[0125] S206, LMF obtains input data from UE.

[0126] This input information can be used for model training.

[0127] As can be seen from the above, when network-side devices collect data from terminals, they only consider whether the user is willing to have their data collected. For example, if the user is willing, it usually applies to all times and all scenarios / locations, without finely reflecting the user's needs, such as when and where they are willing to have their data collected, and when and where they are unwilling to have their data collected. For example, when the terminal's battery is low, although the user may indicate that they want to authorize, the terminal may only authorize data collection for specific times, specific areas, or specific data types.

[0128] This application provides a data collection method that reduces the amount of data to be collected by restricting data collection performed by the terminal in one or more dimensions, thereby reducing the terminal's power consumption. Furthermore, since users can restrict data collection performed by the terminal in multiple dimensions, user control over data collection is enhanced, thus improving the user experience. In addition, by allowing users to flexibly control the collection initiated by network-side devices, data collection that conflicts with terminal performance can be reduced, unnecessary data reporting or leakage can be avoided, thereby ensuring the terminal's communication performance and security.

[0129] The data acquisition method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0130] It should be noted that in this application, the data requesting device (such as network-side equipment, Network Data Analytics Function (NWDAF), Data Collection Coordination Function (DCCF), Messaging Framework Adaptor Function (MFAF), Data Collection Application Function (DCAF), Location Management Function (LMF), Sensing Function (SF), Energy Information Function (EIF), Session Management Function (SMF), User Plane Function (UPF), Access and Mobility Management Function (AMF), or network function equipment dedicated to data collection) requests the requested device (such as UE, Positioning Reference Unit (PRU), or RAN) to collect data from the requested device and report the data to the data requesting device. In other words, the data requesting device sends a data collection request to the requested device, the requested device collects the data according to the request, and reports the collected data to the data requesting device. The requested device may be the first terminal mentioned in this application.

[0131] The term "perform data collection" in this application can be understood as: performing data collection and / or reporting the collected data.

[0132] The permission to collect data mentioned in this application can be understood as at least one of the following: allowing the data collecting device to request the requested device to perform data collection, allowing the performance of data collection and / or reporting of the collected data. Furthermore, the permission mentioned in this application can be understood as support, non-prohibition, etc.

[0133] The prohibition of data collection mentioned in this application can be understood as at least one of the following: prohibition of the data collecting device from requesting the requested device to perform data collection, prohibition of data collection, and prohibition of reporting the collected data. Furthermore, the prohibition mentioned in this application can be understood as not supporting, prohibiting, etc.

[0134] It should be noted that the area mentioned in this application may include at least one of the following: Tracking Area (TA), cell, or physical area. The identifier of the TA may be called the Tracking Area Identity (TAI), and the physical area may be a polygonal area represented by multiple coordinate points. An area may include one or more TAs, cells, or physical areas.

[0135] It should be noted that the information of the time period mentioned in this application includes at least one of the following: the start time of the time period, the end time of the time period, the frequency of the time period (daily, weekly, monthly, annual, etc.), the period of the time period, the start time of the first period, and the end time of the first period.

[0136] It should be noted that the data types mentioned in this application include at least one of the following: location estimate, timestamp information, movement rate, movement orientation, measurement data, intermediate feature data of the measurement data, configuration information used for measurement, information related to the reference cell, information related to neighboring cells, information related to channel response, power delay profile (PDP), information related to the channel matrix, angle information of multipath propagation, and antenna-related information. Here, PDP is statistical data of CIR, describing the signal strength at different delays, while CIR refers to the set of attenuation, delay, and phase response of the signal along its transmission path from the transmitter to the receiver.

[0137] Optionally, the measurement data may include measurement data of the serving cell or measurement data of neighboring cells.

[0138] Optionally, the measurement data includes at least one of the following: Signal-to-Noise Ratio (SINR), Signal-to-Noise Ratio (SNR), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indication (RSSI), and Reference Signal Received Power Path (RSRPP). RSSI represents the strength of the received signal and is an indicator used by wireless communication devices to measure the power of the wireless signal. SNR represents the signal-to-noise ratio and is commonly used to measure the quality of the received signal; a higher SNR means the signal is stronger relative to background noise, generally indicating better communication quality. SINR is the ratio of signal strength to interference plus noise. RSRP refers to the power level of the received reference signal. RSRQ refers to the quality of the received reference signal; RSRQ considers not only the signal power but also the level of interference. A higher RSRQ value indicates better signal quality and less interference. RSRPP stands for RSRP on a specific path in a multipath network. RSTD is an abbreviation for Reference Signal Time Difference, also known as Timing Advance (TA). RSTD is another important radio parameter in LTE networks, used to measure the delay difference between different base stations.

[0139] Optional configuration information for measurement includes information such as the RSTD search time window.

[0140] Optionally, the intermediate feature data includes at least one of the following: Time of Arrival (TOA), Path Phase, etc. TOA is used to measure the propagation time of a signal from the transmitter to the receiver, thereby calculating the distance between the transmitter and the receiver.

[0141] Optionally, the channel response-related information includes at least one of the following: Channel Frequency Response (CFR) and Channel Impulse Response (CIR). CFR describes the channel's response at various frequency points and is a description of the channel's characteristics in the frequency domain in response to an input signal. CFR can be used to characterize the channel's gain and phase shift characteristics. CIR represents the channel's response to an input pulse signal and is typically used to represent the channel's response at a specific frequency.

[0142] Optionally, the antenna-related information includes the number of antennas, antenna distribution patterns, and other information.

[0143] It should be noted that the scenarios mentioned in this application include at least one of the following: Channel State Information (CSI) measurement, positioning, sensing, and energy saving. For example, the scenarios mentioned in this application include at least one of the following: AI CSI, AI positioning, AI sensing, and AI energy saving.

[0144] It should be noted that the model mentioned in this application may also be referred to as an AI unit, AI model, machine learning (ML) model, ML unit, AI structure, AI function, AI characteristic, machine learning model, neural network, neural network function, neural network functionality, etc. Alternatively, the AI ​​unit / AI model may refer to a processing unit capable of implementing specific algorithms, formulas, processing flows, capabilities, etc., related to AI. Or, the AI ​​unit / AI model may be a processing method, algorithm, function, module, or unit for a specific dataset. Alternatively, the AI ​​unit / AI model may be a processing method, algorithm, function, module, or unit running on AI / ML related hardware such as a Graphics Processing Unit (GPU), Neural Processing Unit (NPU), Tensor Processing Unit (TPU), or Application Specific Integrated Circuit (ASIC). This application does not specifically limit this. Optionally, the specific dataset may include the input and / or output of the AI ​​unit / AI model.

[0145] It should be noted that the identifier of the AI ​​unit / AI model mentioned in this application may be an AI model identifier, an AI structure identifier, an AI algorithm identifier, or an identifier of a specific dataset associated with the AI ​​unit / AI model, or an identifier of a specific scenario, environment, channel characteristics, or device related to the AI / ML, or an identifier of a function, characteristic, capability, or module related to the AI / ML. This application does not make any specific limitations on this.

[0146] Figure 3 This is a schematic flowchart of the data acquisition method 310 according to an embodiment of this application. It should be understood that... Figure 3 The steps or operations of data acquisition method 310 are illustrated, but these steps or operations are merely examples, and other operations may be performed in this application. Figure 3 Variations of various operations within it.

[0147] like Figure 3 As shown, the data acquisition method 310 may include:

[0148] S311, the first network element obtains first information, which is information related to data collection provided by the first terminal.

[0149] S312, the first network element performs at least one of the following:

[0150] Send the first information to the first terminal;

[0151] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0152] Determine the second piece of information;

[0153] Send the second information to the first terminal.

[0154] For example, the second information is used to assist the first terminal in performing data collection.

[0155] For example, after obtaining the first information, the first network element sends the first information to the first terminal. After receiving the first information, the first terminal determines whether to accept or refuse to perform data collection based on the first information, or determines the second information based on the first information. In some embodiments, if the first network element cannot determine whether to initiate data collection to the first terminal based on the first information and / or other information (such as the third information mentioned in this application), the first network element may send the first information and other information to the first terminal, and the first terminal may decide whether to accept or refuse to perform data collection.

[0156] For example, the first network element may be NWDAF, DCCF, MFAF, DCAF, LMF, SF, EIF, SMF, UPF, AMF, or a network function device dedicated to data collection.

[0157] For example, after obtaining the first information, the first network element can determine whether to perform data collection on the first terminal based on the first information. If it determines to perform data collection on the first terminal based on the first information, it can directly request the first terminal to perform data collection, or it can determine the second information and send the second information to the first terminal. After receiving the second information, the first terminal can perform data collection based on the second information. In one implementation, the second information can be determined by the first terminal, that is, the first network element does not need to determine the second information for the first terminal based on the first information, and correspondingly, the first network element does not need to send the second information to the first terminal. If it determines not to perform data collection on the first terminal based on the first information, it does not need to request the first terminal to perform data collection.

[0158] In this embodiment, when the first network element sends the first information to the first terminal, since the first information is data collection-related information provided by the first terminal, the data collection performed by the first terminal can be restricted through the first information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. When the first network element determines to perform data collection on the first terminal based on the first information, unnecessary collection triggered by the first network element can be reduced, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. When the first network element sends second information or determines second information to the first terminal, the first terminal can perform data collection based on the second information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal.

[0159] In some embodiments, the first network element acquires the first information, including at least one of the following:

[0160] The first network element obtains the first information stored locally;

[0161] The first network element obtains the first information from the second or third network element;

[0162] The first network element obtains the first information from the first terminal.

[0163] For example, the first network element obtains the first information stored locally on the first network element; or the first network element obtains the first information stored on the second network element from the second network element; or the first network element obtains the first information stored on the third network element from the third network element; or the first network element obtains the first information stored locally on the first terminal from the first terminal. For example, the second network element may be a UDM or NRF. For example, the third network element may be an AMF.

[0164] It should be noted that when the first information is stored locally on the first terminal, it can be stored in non-volatile memory or in a Universal Subscriber Identity Module (USIM) card. Optionally, the first information can be dynamically configured by the user through the mobile phone interface. When the first information changes, the first terminal can update the changed first information to the first network element, the second network element, and the third network element via NAS signaling.

[0165] In one implementation, the first information further includes terminal capability information, which is used to indicate whether the terminal supports or does not support data collection.

[0166] In this embodiment, the first network element can obtain the first information from its local device, the second network element, the third network element, or the first terminal. By enriching the methods for obtaining the first information, the success rate of the first network element obtaining the first information can be improved.

[0167] In some embodiments, before the first network element obtains the first information stored locally, method 310 further includes:

[0168] The first network element obtains the first information from the first terminal and stores the first information locally.

[0169] For example, the first network element can obtain the first information from the first terminal through control plane messages or user plane messages, and store the first information locally.

[0170] In this embodiment, the first network element obtains the first information from the first terminal and stores the first information locally, so that the first network element can directly obtain the first information stored locally, thereby reducing the acquisition latency of the first information.

[0171] In some embodiments, the first information includes at least one of the following:

[0172] 1. Information about one or more areas where data collection is permitted or prohibited.

[0173] It should be noted that the information of the one or more areas can be represented using a TA list or a cell list, or using the coordinates of the physical area. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data from terminals within one or more areas. When the requesting device requests the requested device to collect data from terminals within the one or more areas, if the requested device is located within that area, the requested device reports information / data. Conversely, if the requested device refuses to report information / data... When the first terminal is located within one or more areas where data collection is permitted, data collection from the first terminal is allowed; or when the first terminal is not located within one or more areas where data collection is permitted, data collection from the first terminal is not allowed; or when the first terminal is located within one or more areas where data collection is not permitted, data collection from the first terminal is not allowed; or when the first terminal is not located within one or more areas where data collection is not permitted, data collection from the first terminal is allowed.

[0174] In one implementation, the first information may include information about one or more areas where data collection is permitted or prohibited. For example, the protocol stipulates that the first information includes information about one or more areas where data collection is permitted, or the protocol stipulates that the first information includes information about one or more areas where data collection is prohibited. For instance, when the protocol stipulates that the first information includes information about one or more areas where data collection is permitted, if the first information includes {areas: cell A, cell B}, it specifically indicates that terminals in cell A and cell B are permitted to perform data collection.

[0175] In another implementation, the first information may include information about one or more regions. The type of information about the one or more regions may implicitly indicate whether data collection is permitted or not when the terminal is within the one or more regions. For example, if the type of information about the one or more regions is a first region information type, it implicitly indicates that data collection is permitted when the terminal is within the one or more regions; if the type of information about the one or more regions is a second region information type, it implicitly indicates that data collection is not permitted when the terminal is within the one or more regions. The first region information type and the second region information type may be region information types agreed upon in the protocol. The first region information type is different from the second region information type. The first region information type and the second region information type can refer to the region information types that the first information may include; to avoid repetition, they will not be elaborated here. For example, if the protocol stipulates that the first region information type includes cells and the second region information type includes TAI, if the first information includes {region: cell A, cell B}, it means that data collection is permitted when the terminal is in cell A and cell B; if the first information includes {TAI c}, it means that data collection is not permitted when the terminal is in TAI c. For example, implicit indication can be implemented through information encapsulation identifiers (such as information element identifiers, IEIs). For instance, when the IEI of an information element carrying information about one or more areas where data collection is permitted or prohibited is A, it implicitly indicates that data collection is permitted in one or more areas. That is, when the first terminal is in that area, data collection is permitted; when the first terminal is not in that area, data collection is prohibited. As another example, when the IEI of an information element carrying information about one or more areas where data collection is permitted or prohibited is B, it implicitly indicates that data collection is prohibited in one or more areas. That is, when the first terminal is in that area, data collection is prohibited; when the first terminal is not in that area, data collection is either permitted or prohibited.

[0176] In another implementation, the first information may include an indication for explicitly indicating that data collection is permitted and / or not permitted by terminals in one or more areas. For example, when the first information includes {indication: permitted; area: cell A, cell B}, it indicates that terminals in cell A and cell B are permitted to perform data collection. For example, when the first information includes {indication: not permitted; area: TAI c, coordinates of a specific polygonal area}, it indicates that terminals in TAI c and terminals within the specific polygonal area are not permitted to perform data collection.

[0177] In another implementation, the first information may include both an instruction allowing terminals in one or more areas to perform data collection and information about the one or more areas where data collection is permitted, and an instruction disallowing terminals in one or more areas from performing data collection and information about the one or more areas where data collection is disallowed. For example, when the first information includes {instruction: permitted; area: cell A, cell B} and {instruction: disallowed; area: TAI c, coordinates of a specific polygonal area}, it indicates that terminals in cell A and cell B are permitted to perform data collection, and that terminals in TAI c and terminals within the specific polygonal area are not permitted to perform data collection.

[0178] In another implementation, the first information includes both information about one or more areas where data collection is permitted and information about one or more areas where data collection is permitted. For example, the first information includes information about two sets of areas, where the protocol specifies or implicitly indicates that areas in the first set are areas where data collection is permitted, and areas in the second set are areas where data collection is not permitted; or, the protocol specifies or implicitly indicates that areas in the first set are areas where data collection is not permitted, and areas in the second set are areas where data collection is permitted. For example, if the protocol specifies that areas in the first set are areas where data collection is permitted, and areas in the second set are areas where data collection is not permitted, then if the first information includes {area: cell A, cell B; area: TAI c, coordinates of a specific polygonal area}, it indicates that terminals in cell A and cell B are permitted to perform data collection, and that terminals in TAI c and terminals within the specific polygonal area are not permitted to perform data collection. For example, implicit indication can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more areas where data collection is permitted or prohibited is A, it implicitly indicates that data collection is permitted in one or more areas. That is, when the first terminal is in that area, data collection is permitted, and when the first terminal is not in that area, data collection is prohibited. As another example, when the IEI of an information element carrying information about one or more areas where data collection is permitted or prohibited is B, it implicitly indicates that data collection is prohibited in one or more areas. That is, when the first terminal is in that area, data collection is prohibited, and when the first terminal is not in that area, data collection is either permitted or prohibited.

[0179] It should also be noted that the one or more areas mentioned in this application may be referred to as restricted areas for data collection or other descriptions, and this application does not specifically limit them. For example, the one or more areas where data collection is permitted, as mentioned in this application, may be called data collection allowed areas or data collection validity spatial, etc. Similarly, the one or more areas where data collection is not permitted, as mentioned in this application, may be called data collection dis-allowed areas, etc.

[0180] 2. Information on one or more time periods during which data collection is permitted or prohibited.

[0181] It should be noted that the information for each of the one or more time periods may include at least one of the following: the start time of the time period, the end time of the time period, the frequency of the time period (daily, weekly, monthly, yearly, etc.), the period of the time period, the start time of the first period, and the end time of the first period. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data within one or more time periods. When the requesting device requests the requested device to collect data within the one or more time periods, if the requested device allows data collection within the one or more time periods, the requested device reports information / data. Conversely, if the requested device refuses to report information / data... Data collection from the first terminal is permitted when the time during which the first terminal performs data collection falls within one or more permitted time periods; or data collection from the first terminal is not permitted when the time during which the first terminal performs data collection falls outside one or more permitted time periods; or data collection from the first terminal is permitted when the time during which the first terminal performs data collection falls outside one or more permitted time periods.

[0182] In one implementation, the first information may include information about one or more time periods during which data collection is permitted or prohibited. For example, the protocol stipulates that the first information includes information about one or more time periods during which data collection is permitted, or the protocol stipulates that the first information includes information about one or more time periods during which data collection is prohibited. For instance, if the protocol stipulates that the first information includes information about one or more time periods during which data collection is permitted, and the first information includes {time period: start time 1, end time 1}, it indicates that data collection is permitted during the time period between start time 1 and end time 1.

[0183] In another implementation, the first information may include information from one or more time periods, which may implicitly indicate whether data collection is permitted and / or not permitted. For example, the type of information from the one or more time periods may implicitly indicate whether data collection is permitted or not during those time periods. For instance, if the type of information from the one or more time periods is a first time information type, it implicitly indicates that data collection is permitted during those time periods; if the type of information from the one or more time periods is a second time information type, it implicitly indicates that data collection is not permitted during those time periods. The first time information type and the second time information type may be time information types agreed upon in a protocol. The first time information type is different from the second time information type. The first time information type and the second time information type can refer to the information types of the time periods that the first information may include; to avoid repetition, they will not be elaborated further here. For example, if the protocol stipulates that the first time information type includes start time and end time, and the second time information type includes start time and period, if the first information includes {time period: start time 1, end time 1}, it means that data collection is allowed during the time period between start time 1 and end time 1; if the first information includes {time period: start time 1, period 1}, it means that data collection is not allowed during the time period where the starting position is start time 1 and the period is period 1. For example, implicit indications can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more time periods that allow or disallow data collection is A, it implicitly indicates that one or more time periods that allow data collection are permitted. That is, when the time is within that time period, data collection is permitted, and when the time is outside that time period, data collection is disallowed. As another example, when the IEI of an information element carrying information about one or more time periods that allow or disallow data collection is B, it implicitly indicates that one or more time periods that disallow data collection are disallowed. That is, when the time is within that time period, data collection is disallowed, and when the time is outside that time period, data collection is either permitted or disallowed.

[0184] In another implementation, the first information may include instructions for explicitly indicating that data collection is permitted and / or not permitted during one or more time periods. For example, if the first information includes {instruction: permitted; time period: start time 2, end time 2}, it indicates that data collection is permitted during the time period from start time 2 to end time 2. For example, if the first information includes {instruction: not permitted; time period: start time 3, end time 3}, it indicates that data collection is not permitted during the time period from start time 3 to end time 3.

[0185] In another implementation, the first information may include both an instruction allowing data collection to be performed within one or more time periods and information about the one or more time periods during which data collection is permitted, and an instruction disallowing data collection within one or more time periods and information about the one or more time periods during which data collection is disallowed. For example, when the first information includes {instruction: permitted; time periods: start time 1, end time 1} and {instruction: disallowed; time periods: start time 2, end time 2}, it indicates that data collection is permitted during the time period from start time 1 to end time 1, and that data collection is disallowed during the time period from start time 2 to end time 2.

[0186] In another implementation, the first information includes both information on one or more time periods during which data collection is permitted and information on one or more time periods during which data collection is not permitted.

[0187] For example, the first information includes information on two sets of time periods. The protocol stipulates or implicitly indicates that the time periods in the first set are one or more time periods where data collection is permitted, and the time periods in the second set are one or more time periods where data collection is not permitted; or, the protocol stipulates or implicitly indicates that the time periods in the first set are one or more time periods where data collection is not permitted, and the time periods in the second set are one or more time periods where data collection is permitted. For example, if the protocol stipulates that the time periods in the first set are one or more time periods where data collection is permitted, and the time periods in the second set are one or more time periods where data collection is not permitted, then if the first information includes {time period: start time 1, end time 1; time period: start time 2, end time 2}, it indicates that data collection is permitted during the time period between start time 1 and end time 1, and that data collection is not permitted during the time period between start time 2 and end time 2. For example, implicit indications can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more time periods that allow or disallow data collection is A, it implicitly indicates that one or more time periods that allow data collection are permitted. That is, when the time is within that time period, data collection is permitted, and when the time is outside that time period, data collection is disallowed. As another example, when the IEI of an information element carrying information about one or more time periods that allow or disallow data collection is B, it implicitly indicates that one or more time periods that disallow data collection are disallowed. That is, when the time is within that time period, data collection is disallowed, and when the time is outside that time period, data collection is either permitted or disallowed.

[0188] It should also be noted that the information regarding the one or more time periods mentioned in this application may be referred to as time limits for data collection or other descriptions, and this application does not specifically limit it in this way. For example, the one or more time periods during which data collection is permitted mentioned in this application may be referred to as the data collection allowed period or the data collection validity period, etc. As another example, the one or more time periods during which data collection is not permitted mentioned in this application may be referred to as the data collection dis-allowed period, etc.

[0189] 3. Information on one or more data types that may or may not be allowed to be collected.

[0190] It should be noted that the information for each of the one or more data types may include at least one of the following: measurement data, intermediate feature data of the measurement data, configuration information for measurement, reference cell-related information, neighbor cell-related information, channel response-related information, PDP, channel matrix-related information, multipath angle information, and antenna-related information. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data of one or more data types. When the requesting device requests the requested device to collect data of the one or more data types, if the requested device allows the collection of data of the one or more data types, the requested device reports the information / data. Conversely, if the requested device refuses to report the information / data... Data collection from the first terminal is permitted when the data type collected by the first terminal falls within one or more permitted data types; or data collection from the first terminal is not permitted when the data type collected by the first terminal falls within one or more permitted data types; or data collection from the first terminal is permitted when the data type collected by the first terminal falls within one or more permitted data types.

[0191] In one implementation, the first information may include information about one or more data types that allow or disallow data collection. For example, the protocol stipulates that the first information includes information about one or more data types that allow data collection, or the protocol stipulates that the first information includes information about one or more data types that disallow data collection. For instance, if the protocol stipulates that the first information includes information about one or more data types that allow data collection, and the first information includes {data type: location result}, it indicates that data collection of the location result is allowed.

[0192] In another implementation, the first information may include information of one or more data types, which may implicitly indicate whether data collection is permitted and / or not permitted. For example, the type of the information of the one or more data types may implicitly indicate whether data collection of the data of the one or more data types is permitted or not. For instance, when the type of the information of the one or more data types is a first type, it implicitly indicates that data collection of the data of the one or more data types is permitted; when the type of the information of the one or more data types is a second type, it implicitly indicates that data collection of the data of the one or more data types is not permitted. The first type and the second type may be types agreed upon by the protocol. The first type is different from the second type. The first type and the second type can refer to the types of data types that the first information may include, and to avoid repetition, they will not be elaborated here. For example, if the protocol stipulates that the first type includes positioning results and the second type includes movement rate, if the first information includes {data type: positioning results}, it indicates that data collection of positioning results is permitted; if the first information includes {data type: movement rate}, it indicates that data collection of movement rate is not permitted. For example, implicit indications can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more data types that allow or disallow data collection is A, it implicitly indicates that one or more data types that allow data collection are allowed. That is, if the data type to be collected is in the information of that data type, data collection is allowed; if the data type to be collected is not in the information of that data type, data collection is disallowed. As another example, when the IEI of an information element carrying information about one or more data types that allow or disallow data collection is B, it implicitly indicates that one or more data types that disallow data collection are disallowed. That is, if the data type to be collected is in the information of that data type, data collection is disallowed; if the data type to be collected is not in the information of that data type, data collection is either disallowed or allowed.

[0193] In another implementation, the first information may include an indication for explicitly indicating that data collection of one or more data types is permitted and / or not permitted. For example, when the first information includes {indication: permitted; data type: location result}, it indicates that data collection of the location result is permitted; for example, when the first information includes {indication: not permitted; data type: movement rate}, it indicates that data collection of the movement rate is not permitted.

[0194] In another implementation, the first information may include both an instruction allowing data collection of one or more data types and information about the one or more data types allowed to be collected, and an instruction disallowing data collection of one or more data types and information about the one or more data types disallowing data collection. For example, when the first information includes {instruction: allowed; data type: location result} and {instruction: disallowed; data type: movement rate}, it indicates that data collection of the location result is allowed, and that data collection of the movement rate is disallowed.

[0195] In another implementation, the first information includes both information on one or more data types that are permitted for data collection and information on one or more data types that are not permitted for data collection. For example, the first information may include information on two sets of data types, with the protocol specifying or implicitly indicating that the data types in the first set are one or more data types that are permitted for data collection, and the data types in the second set are one or more data types that are not permitted for data collection; or, the protocol specifying or implicitly indicating that the data types in the first set are one or more data types that are not permitted for data collection, and the data types in the second set are one or more data types that are permitted for data collection. For example, if the protocol specifies that the data types in the first set are one or more data types that are permitted for data collection, and the data types in the second set are one or more data types that are not permitted for data collection, then if the first information includes {data type: positioning result; data type: movement rate}, it indicates that data collection of the positioning result is permitted, and that data collection of the movement rate is not permitted. For example, implicit indications can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more data types that allow or disallow data collection is A, it implicitly indicates that one or more data types that allow data collection are allowed. That is, if the data type to be collected is in the information of that data type, data collection is allowed; if the data type to be collected is not in the information of that data type, data collection is disallowed. As another example, when the IEI of an information element carrying information about one or more data types that allow or disallow data collection is B, it implicitly indicates that one or more data types that disallow data collection are disallowed. That is, if the data type to be collected is in the information of that data type, data collection is disallowed; if the data type to be collected is not in the information of that data type, data collection is either disallowed or allowed.

[0196] It should also be noted that the information regarding the one or more data types mentioned in this application may be referred to as data type restriction or other descriptions, and this application does not specifically limit it in this regard. For example, the one or more data types that are allowed to be collected mentioned in this application may also be referred to as allowed data types or data collection validity data types, etc. As another example, the one or more data types that are not allowed to be collected mentioned in this application may be referred to as dis-allowed data types, etc.

[0197] 4. Information on one or more scenarios in which data collection is permitted or prohibited.

[0198] It should be noted that the information for each of the one or more scenarios may include at least one of the following: CSI measurement, positioning, sensing, and energy saving. Specifically, the first terminal can act as the requested device. The requesting device and the requested device agree that data needs to be reported / collected for one or more scenarios. When the requesting device requests the requested device to collect data for the one or more scenarios, if the requested device allows the collection of data for that scenario, then the requested device reports the information / data for that scenario. Conversely, if the requested device does not allow the collection of data for that scenario, then the requested device refuses to provide all relevant information / data for that scenario. When the data collected by the first terminal is data from one or more scenarios where data collection is permitted, then data collection from the first terminal is permitted; or when the data collected by the first terminal is not data from one or more scenarios where data collection is permitted, then data collection from the first terminal is not permitted; or when the data collected by the first terminal is not data from one or more scenarios where data collection is not permitted, then data collection from the first terminal is permitted.

[0199] In one implementation, the first information may include information about one or more scenarios where data collection is permitted or prohibited. For example, the protocol stipulates that the first information includes information about one or more scenarios where data collection is permitted, or the protocol stipulates that the first information includes information about one or more scenarios where data collection is prohibited. For instance, if the protocol stipulates that the first information includes information about one or more scenarios where data collection is permitted, and the first information includes {scenario: location}, it indicates that data collection is permitted for data in the location scenario.

[0200] In another implementation, the first information may include information about one or more scenarios, which may implicitly indicate whether data collection is permitted and / or prohibited. For example, the type of information for the one or more scenarios may implicitly indicate whether data collection is permitted or prohibited in the one or more scenarios. For instance, if the type of information for the one or more scenarios is a first scenario information type, it implicitly indicates that data collection is permitted in the one or more scenarios; if the type of information for the one or more scenarios is a second scenario information type, it implicitly indicates that data collection is prohibited in the one or more scenarios. The first scenario information type and the second scenario information type may be scenario information types agreed upon in the protocol. The first scenario information type is different from the second scenario information type. The first scenario information type and the second scenario information type can refer to the scenario information types that the first information may include; to avoid repetition, they will not be elaborated here. For example, if the protocol stipulates that the first scenario information type includes location and the second scenario information type includes perception, if the first information includes {scenario: location}, it indicates that data collection is permitted in the location scenario; if the first information includes {scenario: perception}, it indicates that data collection is prohibited in the perception scenario. For example, implicit indications can be implemented through information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more scenarios where data collection is permitted or prohibited is A, it implicitly indicates that one or more scenarios where data collection is permitted. That is, when the scenario requiring data collection is one of the scenarios in the scenario information, data collection is permitted; when the scenario requiring data collection is not any of the scenarios in the scenario information, data collection is prohibited. As another example, when the IEI of an information element carrying information about one or more scenarios where data collection is permitted or prohibited is B, it implicitly indicates that one or more scenarios where data collection is prohibited. That is, when the scenario requiring data collection is one of the scenarios in the scenario information, data collection is prohibited; when the scenario requiring data collection is not any of the scenarios in the scenario information, data collection is either prohibited or permitted.

[0201] In another implementation, the first information may include an indication for explicitly indicating that data collection is permitted and / or not permitted in one or more scenarios. For example, when the first information includes {indication: permitted; scenario: location}, it indicates that data collection is permitted in the location scenario; or when the first information includes {indication: not permitted; scenario: perception}, it indicates that data collection is not permitted in the perception scenario.

[0202] In another implementation, the first information may include both instructions allowing data collection in one or more scenarios and information about the one or more scenarios where data collection is permitted, and instructions disallowing data collection in one or more scenarios and information about the one or more scenarios where data collection is disallowed. For example, when the first information includes {instruction: permitted; scenario: location} and {instruction: disallowed; scenario: perception}, it indicates that data collection is permitted in the location scenario and that data collection is disallowed in the perception scenario.

[0203] In another implementation, the first information includes both information about one or more scenarios where data collection is permitted and information about one or more scenarios where data collection is not permitted. For example, the first information includes information about two sets of scenarios, where the protocol stipulates or implicitly indicates that scenarios in the first set of scenarios are one or more scenarios where data collection is permitted, and scenarios in the second set of scenarios are one or more scenarios where data collection is not permitted; or, the protocol stipulates or implicitly indicates that scenarios in the first set of scenarios are one or more scenarios where data collection is not permitted, and scenarios in the second set of scenarios are one or more scenarios where data collection is permitted. For example, when the protocol stipulates that scenarios in the first set of scenarios are one or more scenarios where data collection is permitted, and scenarios in the second set of scenarios are one or more scenarios where data collection is not permitted, if the first information includes {Scenario: Location; Scenario: Perception}, it indicates that data collection is permitted in the location scenario and that data collection is not permitted in the perception scenario. For example, implicit indications can be implemented using information encapsulation identifiers (such as IEIs). For instance, when the IEI of an information element carrying information about one or more scenarios where data collection is permitted or prohibited is A, it implicitly indicates that one or more scenarios are permitted for data collection. That is, if the scenario requiring data collection is one of the scenarios in this scenario information, data collection is permitted; if the scenario requiring data collection is not any of the scenarios in this scenario information, data collection is prohibited. Similarly, when the IEI of an information element carrying information about one or more scenarios where data collection is permitted or prohibited is B, it implicitly indicates that one or more scenarios are prohibited for data collection. That is, if the scenario requiring data collection is one of the scenarios in this scenario information, data collection is prohibited; if the scenario requiring data collection is not any of the scenarios in this scenario information, data collection is either prohibited or permitted.

[0204] It should also be noted that the information regarding the one or more scenarios mentioned in this application may be referred to as case restrictions on data collection or other descriptions, and this application does not specifically limit them. For example, the one or more scenarios in which data collection is permitted mentioned in this application may also be referred to as allowed cases or data collection validity cases, etc. As another example, the one or more scenarios in which data collection is not permitted mentioned in this application may be referred to as dis-allowed cases, etc.

[0205] 5. Information for the first area.

[0206] The first area may include one or more areas. Optionally, the first area may include areas where data collection is permitted, or the first area may include areas where data collection is not permitted.

[0207] 6. Instructions to allow or disallow terminals in the first area to perform data collection.

[0208] When the first region includes multiple regions, the instruction to allow or disallow terminals within the first region to perform data collection may include: an instruction to allow or disallow terminals within each of the multiple regions to perform data collection. Alternatively, when the first region includes multiple regions, the instruction to allow or disallow terminals within the first region to perform data collection may include: an instruction to allow or disallow terminals within one or more of the first regions to perform data collection.

[0209] It should be noted that the information of the first area can be represented using a TA list or a cell list, or using the coordinates of the physical area. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data from terminals in the first area. When the requesting device requests the requested device to collect data from terminals in the first area, if the requested device is located within the first area, the requested device reports information / data. Conversely, if the requested device refuses to report information / data... When the first terminal is located within the first area where data collection is permitted, data collection from that first terminal is allowed; or when the first terminal is not located within the first area where data collection is permitted, data collection from that first terminal is not allowed; or when the first terminal is located within the first area where data collection is not permitted, data collection from that first terminal is not allowed; or when the first terminal is not located within the first area where data collection is not permitted, data collection from that first terminal is allowed.

[0210] In one implementation, the first area may be an implicit indication of whether data collection is permitted or not. For example, if the first information includes {area: TAI a, TAI b}, it indicates that terminals in TAI a and TAI b are permitted to perform data collection. In another implementation, the first information may include an indication for explicitly indicating whether terminals in the first area are permitted or not. For example, if the first information includes {indication: permitted; area: cell A, cell B}, it indicates that terminals in cell A and cell B are permitted to perform data collection; or if the first information includes {indication: not permitted; area: TAI c, coordinates of a specific polygonal region}, it indicates that terminals in TAI c and terminals within the specific polygonal region are not permitted to perform data collection. In one implementation, the first information may include both a permitted indication and associated permitted area information, and a disallowed indication and associated disallowed area information.

[0211] It should also be noted that the first area mentioned in this application may be referred to as a restricted area for data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first area mentioned in this application may be referred to as a data collection allowed area, a data collection validity space, or a data collection dis-allowed area, etc.

[0212] 7. Information of the first data type.

[0213] The first data type may include one or more data types. Optionally, the first data type may include data types that allow data collection, or the first data type may include data types that do not allow data collection.

[0214] 8. Instructions to allow or disallow data collection of the first data type.

[0215] When the first data type includes multiple data types, the instruction to allow or disallow data collection of data of the first data type may include: an instruction to allow or disallow data collection of data of each of the multiple data types. Alternatively, when the first data type includes multiple data types, the instruction to allow or disallow data collection by terminals within the first area may include: an instruction to allow or disallow data collection of data of one or more of the first data types.

[0216] It should be noted that the information of the first data type may include at least one of the following: measurement data, intermediate feature data of the measurement data, configuration information for measurement, information related to the reference cell, information related to neighboring cells, information related to channel response, PDP, information related to the channel matrix, multipath angle information, and antenna-related information. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data of the first data type. When the requesting device requests the requested device to collect data of the first data type, if the requested device allows the collection, the requested device reports the information / data. Conversely, if the requested device refuses to report the information / data... If the data type collected by the first terminal is within the first data type that is allowed to be collected, then data collection of the first terminal is permitted; or if the data type collected by the first terminal is not within the first data type that is allowed to be collected, then data collection of the first terminal is not permitted; or if the data type collected by the first terminal is not within the first data type that is not allowed to be collected, then data collection of the first terminal is permitted.

[0217] In one implementation, the first data type can be an implicit indication of whether data collection is permitted and / or prohibited. For example, if the first information includes {data type: channel matrix related information}, it indicates that data collection of channel matrix related information is permitted. In another implementation, the first information can include an indication for explicitly indicating whether data collection of the first data type is permitted and / or prohibited. For example, if the first information includes {indication: permitted; data type: reference cell related information}, it indicates that data collection of reference cell related information is permitted; or if the first information includes {indication: prohibited; data type: channel response related information}, it indicates that data collection of channel response related information is prohibited. In one implementation, the first information can include both a permitted indication and associated permitted data type information, and a prohibited indication and associated prohibited data type information.

[0218] It should also be noted that the information regarding the first data type mentioned in this application may be referred to as a data type restriction or other description, and this application does not specifically limit it in this regard. For example, the first data type mentioned in this application may also be referred to as an allowed data type, a data collection validity data type, or a dis-allowed data type, etc.

[0219] 9. Information from the first time period.

[0220] The first time period may include one or more time periods. Optionally, the first time period may include time periods during which data collection is permitted, or the first time period may include time periods during which data collection is not permitted.

[0221] 10. Instructions to allow or disallow data collection during the first time period.

[0222] When the first time period includes multiple time periods, the instruction to allow or disallow data collection within the first time period may include: an instruction to allow or disallow data collection within each time period of the first time period. Alternatively, when the first time period includes multiple time periods, the instruction to allow or disallow data collection within the first time period may include: an instruction to allow or disallow data collection within one or more time periods of the first time period.

[0223] It should be noted that the information for the first time period may include at least one of the following: the start time of the time period, the end time of the time period, the frequency of the time period (daily, weekly, monthly, yearly, etc.), the period of the time period, the start time of the first period, and the end time of the first period. When data collection occurs within the first time period, data collection of the UE may or may not be permitted. The first terminal can act as the requested device. The requesting device and the requested device agree to collect data within the first time period. When the requesting device requests the requested device to collect data within the first time period, if the requested device permits data collection within the first time period, the requested device reports information / data. Conversely, if the requested device refuses to report information / data... Data collection is permitted when the first terminal performs data collection within a first permitted time period; or when the first terminal performs data collection outside the first permitted time period; or when the first terminal performs data collection within the first prohibited time period; or when the first terminal performs data collection outside the first prohibited time period.

[0224] In one implementation, the first time period can be an implicit indication of when data collection is permitted and / or not permitted. For example, if the first information includes {time period: start time 1, end time 1}, it indicates that data collection is permitted during the time period from start time 1 to end time 1. In another implementation, the first information may include an explicit indication of when data collection is permitted and / or not permitted during the first time period. For example, if the first information includes {indication: permitted; time period: start time 2, end time 2}, it indicates that data collection is permitted during the time period from start time 2 to end time 2; or if the first information includes {indication: not permitted; time period: start time 3, end time 3}, it indicates that data collection is not permitted during the time period from start time 3 to end time 3. In one implementation, the first information may include both a permitted indication and associated permitted time period information, and a disallowed indication and associated disallowed time period information.

[0225] It should also be noted that the information regarding the first time period mentioned in this application may be referred to as a time limit for data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first time period mentioned in this application may be referred to as a data collection allowed period, a data collection validity period, or a data collection dis-allowed period, etc.

[0226] 11. Information from the first scene.

[0227] The first scenario may include one or more scenarios. Optionally, the first scenario may include scenarios that allow data collection, or the first area may include scenarios that do not allow data collection.

[0228] 12. Instructions on whether or not to collect data in the first scenario.

[0229] When the first scenario includes multiple scenarios, the indication to allow or disallow the collection of data in the first scenario may include: an indication for each of the multiple scenarios.

[0230] It should be noted that the information in the first scenario may include at least one of the following: CSI measurement, positioning, sensing, and energy saving. Specifically, the first terminal can act as the requested device. The data requesting device and the requested device agree that data in the first scenario needs to be reported / collected. When the data requesting device requests the requested device to collect data in the first scenario, if the requested device allows the collection of data in the first scenario, then the requested device reports the information / data in the first scenario. Conversely, if the requested device does not allow the collection of data in the first scenario, then the requested device refuses to provide all relevant information / data in the first scenario. When the data collected by the first terminal is data in the first scenario where data collection is allowed, then data collection of the first terminal is permitted; or when the data collected by the first terminal is not data in the first scenario where data collection is not allowed, then data collection of the first terminal is not permitted; or when the data collected by the first terminal is not data in the first scenario where data collection is not allowed, then data collection of the first terminal is permitted.

[0231] In one implementation, the first scenario can be an implicit indication of whether data collection is permitted and / or not permitted. For example, if the first information includes {Scenario: Location}, it indicates that data collection is permitted in the location scenario. In another implementation, the first information can include an indication of explicit permission to collect data in the first scenario. For example, if the first information includes {Instruction: Permitted; Scenario: Location}, it indicates that data collection is permitted in the location scenario; or if the first information includes {Instruction: Disallowed; Scenario: Perception}, it indicates that data collection is not permitted in the perception scenario. In one implementation, the first information can include both a permitted instruction and associated permitted scenario information, and a disallowed instruction and associated disallowed scenario information.

[0232] It should also be noted that the first scenario mentioned in this application may be referred to as a case restriction on data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first scenario mentioned in this application may be referred to as an allowed case, a data collection validity case, or a dis-allowed case, etc.

[0233] In this embodiment, when the first information includes information about one or more areas where data collection is permitted or prohibited, information about a first area, or an instruction to permit or prohibit a terminal within the first area from performing data collection, the first information can be used to restrict the data collection terminal at the area level, reducing unnecessary data collection by the first terminal and thus lowering its power consumption. When the first information includes information about one or more time periods where data collection is permitted or prohibited, information about a first time period, or an instruction to permit or prohibit data collection within the first time period, the first information can be used to restrict the data collection performed by the first terminal at the collection time level, reducing the amount of data to be collected and thus lowering its power consumption. When the first information includes information about one or more data types where data collection is permitted or prohibited, information about a first data type, or an instruction to permit or prohibit data collection of the first data type, the first information can be used to restrict the data type collected by the first terminal, reducing the amount of data to be collected and thus lowering its power consumption. When the first information includes information about one or more scenarios that allow or disallow data collection, information about the first scenario, or an indication that data collection in the first scenario is allowed or disallowed, the scenarios for collecting data can be restricted by the first information, thereby reducing the amount of data that needs to be collected and thus reducing the power consumption of the first terminal.

[0234] In some embodiments, the second information includes at least one of the following:

[0235] The second area is used to instruct the first terminal to perform data collection when it is located within the second area.

[0236] The second time period is used to instruct the first terminal to perform data collection during the second time period.

[0237] The second data type is used to instruct the first terminal to collect data of the second data type.

[0238] The second scenario is used to instruct the first terminal to collect data under the second scenario.

[0239] For example, the first network element sends the second information to the first terminal. After receiving the second information, the first terminal can directly perform data collection based on the second information. For instance, if the second information includes the second area, the first terminal can perform data collection when it is located within the second area. Alternatively, if the second information includes the second time period, the first terminal can perform data collection within the second time period. Furthermore, if the second information includes the second data type, the first terminal can collect data based on the second data type. Finally, if the second information includes the second scenario, the first terminal can perform data collection based on the second scenario.

[0240] In one embodiment, the second information including a second region can be understood as the second information including information indicating the second region; the second information including a second time period can be understood as the second information including information indicating the second time period; the second information including a second data type can be understood as the second information including information indicating the second data type; and the second information including a second scenario can be understood as the second information including information indicating the second scenario.

[0241] In one embodiment, the second region may include one or more regions, the second time period may include one or more time periods, the second data type may include one or more data types, and the second scenario may include one or more scenarios.

[0242] In this embodiment, when the second information includes the second region, the data acquisition terminal can be restricted in terms of region using the second information, reducing unnecessary data collection by the first terminal and thus reducing its power consumption. When the second information includes the second time period, the data acquisition performed by the first terminal can be restricted in terms of collection time using the second information, reducing the amount of data to be collected and thus reducing its power consumption. When the second information includes the second data type, the data type of the data collected by the first terminal can be restricted using the second information, reducing the amount of data to be collected and thus reducing its power consumption. When the second information includes the second scenario, the scenario of the collected data can be restricted using the second information, reducing the amount of data to be collected and thus reducing its power consumption.

[0243] In some embodiments, determining the second information includes:

[0244] The second information is determined based on at least one of the first information and the third information;

[0245] The third piece of information refers to information related to data collection provided by the data requesting device.

[0246] For example, the first network element may determine the first information as the second information, or the first network element may determine the third information as the second information, or the first network element may determine the second information based on the first information and the third information.

[0247] For example, if the first information includes information about a first region, the second information includes information about a second region, and the third information includes information about a third region, the third region is used to request the terminal to perform data collection within the third region; the first network element can determine the overlapping area of ​​the first region and the second region as the second region. Alternatively, if the first information includes information about a first time period, the second information includes information about a second time period, and the third information includes a third time period, the third time period is used to request the terminal to perform data collection within the third time period; the first network element can determine the overlapping time period of the first time period and the third time period as the second time period. Alternatively, if the first information includes information about a first data type, the second information includes information about a second data type, and the third information includes a third data type, the third data type is used to request the terminal to collect data of the third data type; the first network element can determine the intersection of the first data type and the third data type as the second data type. Alternatively, if the first information includes information about a first scenario, the second information includes information about a second scenario, and the third information includes a third scenario, the third scenario is used to request the terminal to collect data under the third scenario; the first network element can determine the intersection of the first scenario and the third scenario as the second scenario.

[0248] In this embodiment, since the second information is used by the first terminal to perform data collection, when determining the second information based on the first information, the data collection performed by the first terminal can be restricted using the first information, thereby reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. Similarly, when determining the second information based on the third information, the data collection performed by the first terminal can be restricted using the third information, thereby reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. Finally, when determining the second information based on both the first and third information, the data collection performed by the first terminal can be restricted using both the first and third information, thereby reducing the amount of data to be collected and thus reducing the power consumption of the first terminal.

[0249] In some embodiments, method 310 further includes:

[0250] The first network element receives the first request from the data requesting device;

[0251] The first network element sends a second request to the first terminal;

[0252] The first request includes at least one of the following:

[0253] The third information is information related to data collection provided by the data collection device;

[0254] Address information of the data requester's device;

[0255] The second request includes at least one of the following:

[0256] The first information or the second information;

[0257] The third information;

[0258] The address information of the first network element.

[0259] For example, the address information of the data requesting device includes, but is not limited to, information such as IP address, FQDN, or port number.

[0260] For example, the address information of the first network element includes, but is not limited to, information such as IP address, FQDN, or port number.

[0261] For example, the first request may further include at least one of the following: an instruction to perform data collection on data from any terminal within the third area; and an identifier of the terminal for which data collection needs to be performed. If the first request includes an instruction to perform data collection on data from any terminal within the third area, the first network element can obtain the identifier information of the terminal within the third area from the third network element, and request the terminal within the third area to perform data collection based on the identifier information of the terminal within the third area. If the first request includes the identifier of the terminal for which data collection needs to be performed, the first network can directly request the terminal for which data collection needs to be performed to perform data collection based on the identifier of the terminal for which data collection needs to be performed.

[0262] In this embodiment, when the second request includes the first information or the second information, or when the second request includes the third information, the first terminal can limit the data collection performed by the first terminal based on the first information, the second information, or the third information, thereby reducing the amount of data that needs to be collected and thus reducing the power consumption of the first terminal.

[0263] In some embodiments, the second request is transmitted via control plane messages or user plane messages.

[0264] In this embodiment, the first network element can flexibly choose control plane messages or user plane messages to send the second request, thereby improving the flexibility of the first network element in sending the second request.

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

[0266] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0267] The third time period is used to request the terminal to perform data collection during the third time period;

[0268] A third data type, wherein the third data type is used to request the terminal to collect data of the third data type;

[0269] The third scenario is used to request the terminal to collect data under the third scenario;

[0270] Instructions for collecting user-plane data;

[0271] The purpose of data collection.

[0272] For example, the purpose of the data collection may include at least one of the following: model training, model inference, performance monitoring, etc.

[0273] In one embodiment, the third information including a third region can be understood as the third information including information indicating the third region; the third information including a third time period can be understood as the third information including information indicating the third time period; the third information including a third data type can be understood as the third information including information indicating the third data type; and the third information including a third scenario can be understood as the third information including information indicating the third scenario.

[0274] In one embodiment, the third region may include one or more regions, the third time period may include one or more time periods, the third data type may include one or more data types, and the third scenario may include one or more scenarios.

[0275] In this embodiment, when the third information includes the third region, the data acquisition terminal can be restricted in terms of region, reducing unnecessary data collection by the first terminal and thus reducing its power consumption. When the third information includes the second time period, the data acquisition performed by the first terminal can be restricted in terms of collection time, reducing the amount of data to be collected and thus reducing its power consumption. When the third information includes the second data type, the data type of the data collected by the first terminal can be restricted, reducing the amount of data to be collected and thus reducing its power consumption. When the third information includes the third scenario, the scenario of the collected data can be restricted, reducing the amount of data to be collected and thus reducing its power consumption. When the third information includes an instruction for data collection via user plane, the first terminal reports the collected data via user plane messages, reducing control plane signaling overhead. When the third information includes the purpose of data collection, the purpose of the collected data can be restricted, reducing the amount of data to be collected and thus reducing its power consumption.

[0276] In some embodiments, method 310 further includes:

[0277] The first network element receives a response message for the second request from the first terminal, the response message including at least one of the following:

[0278] 1. Instructions for accepting or rejecting the second request.

[0279] 2. Reason information indicating the reason for rejection, said reason information including at least one of the following:

[0280] The indication that the first terminal is not located in the third area;

[0281] The indication that the first terminal is not located in a portion of the third region;

[0282] The first terminal does not support instructions to perform data collection during the third time period;

[0283] The first terminal does not support instructions to perform data collection during a portion of the third time period;

[0284] The first terminal does not support instructions to collect data of the third data type;

[0285] The first terminal does not support instructions to collect data of some data types in the third data type;

[0286] The first terminal does not support instructions to collect data in the third scenario;

[0287] The first terminal does not support instructions to collect data in some scenarios of the third scenario.

[0288] 3. Indicate the reason for acceptance, such as including at least one of the following:

[0289] The indication of the first terminal within the third area;

[0290] The indication of the first terminal within a portion of the third region;

[0291] The first terminal supports instructions to perform data collection during the third time period;

[0292] The first terminal supports instructions to perform data collection during a portion of the third time period;

[0293] The first terminal supports instructions to collect data of the third data type;

[0294] The first terminal supports instructions to collect data of some data types in the third data type;

[0295] The first terminal supports instructions to collect data in the third scenario;

[0296] The first terminal supports instructions to collect data from certain scenarios within the third scenario.

[0297] For example, if the second request includes the second information, the response message may also include cause information. For example, it may include an indication that the first terminal is not in the third area. For instance, if the first terminal is not in the third area due to terminal movement, the cause information may include an indication that the first terminal is not in the third area.

[0298] It should be noted that if the second request includes the second information, the first terminal can determine whether to accept or reject the second request based on its own situation (e.g., communication status, battery status). That is, the response message of the second request may include at least one of the following:

[0299] 1. Instructions for accepting or rejecting the second request.

[0300] 2. Reason information indicating the reason for rejection, said reason information including at least one of the following:

[0301] An indication that the first terminal is not in the second area;

[0302] The first terminal is not located in a portion of the second region;

[0303] The first terminal does not support instructions to perform data collection during the second time period;

[0304] The first terminal does not support instructions to perform data collection during a portion of the second time period;

[0305] The first terminal does not support instructions to collect data of the second data type;

[0306] The first terminal does not support instructions to collect data of some data types in the second data type;

[0307] The first terminal does not support instructions to collect data in the second scenario;

[0308] The first terminal does not support instructions to collect data from certain scenarios in the second scenario.

[0309] 3. Indicate the reason for acceptance, such as including at least one of the following:

[0310] The indication of the first terminal within the second area;

[0311] The indication of the first terminal within a portion of the second region;

[0312] The first terminal supports instructions to perform data collection during the second time period;

[0313] The first terminal supports instructions to collect data during a portion of the second time period;

[0314] The first terminal supports instructions to collect data of the second data type;

[0315] The first terminal supports instructions to collect data of some data types in the second data type;

[0316] The first terminal supports instructions to collect data in the second scenario;

[0317] The first terminal supports instructions to collect data from certain scenarios in the second scenario.

[0318] In this embodiment, the response message includes an indication of accepting or rejecting the second request, enabling a response to the second request. When the response message includes reason information indicating a reason for rejection or reason information indicating a reason for acceptance, the response message can assist the data requesting device in adjusting the data collection-related information provided by the data requester, thereby improving the data collection effect.

[0319] In some embodiments, method 310 further includes:

[0320] The first network element sends fourth information to the third network element, the fourth information including at least one of the following:

[0321] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0322] Instructions to request information related to data collection provided by terminals within the third area;

[0323] Instructions to request the identification information of terminals within the third area.

[0324] For example, the fourth information includes the third region and at least one of the following:

[0325] Instructions to request information related to data collection provided by terminals within the third area;

[0326] Instructions to request the identification information of terminals within the third area.

[0327] If the fourth information includes the third region, the third network element, upon receiving the fourth information, determines the identification information of the terminal located within the third region.

[0328] If the fourth information includes an instruction to request the identification information of terminals in the third area, the third network element, upon receiving the fourth information, sends the identification information of terminals in the third area to the first network element.

[0329] If the fourth information includes an instruction to request data collection-related information provided by a terminal in the third area, the third network element, upon receiving the fourth information, sends the identification information of the terminal in the third area and the instruction to the terminal in the third area to the first network element.

[0330] In this embodiment, the fourth information includes the third region, which can restrict the terminals that need to perform data collection, reducing unnecessary data collection by the first terminal and thus reducing the power consumption of the first terminal. When the fourth information includes an instruction to request data collection-related information provided by terminals within the third region, or when the fourth information includes an instruction to request identification information of terminals within the third region, the third network element can know whether to feed back data collection-related information provided by terminals within the third region to the first network element, or to feed back the identification information of terminals within the third region to the first network element, thereby enabling data collection from terminals within the third region.

[0331] Figure 4 This is a schematic flowchart of the data acquisition method 320 according to an embodiment of this application.

[0332] like Figure 4 As shown, the data acquisition method 320 may include:

[0333] S321, the first terminal performs at least one of the following:

[0334] Obtain first information;

[0335] Send the first information to the first network element, the second network element, or the third network element;

[0336] Decide whether to accept or refuse data collection;

[0337] The second information is determined based on the first information or the second information is received from the first network element;

[0338] The first information refers to the information related to data collection provided by the first terminal.

[0339] For example, the second information is used to assist the first terminal in performing data collection.

[0340] For example, the first terminal acquires the first information and sends the first information to the first network element, the second network element, or the third network element. Upon receiving the first information, the first network element can determine to perform data collection on the first terminal based on the first information, or it can determine second information based on the first information. Upon receiving the first information, the second network element can store the first information locally so that the first network element can subsequently retrieve the first information from the second network element. Similarly, upon receiving the first information, the third network element can store the first information locally so that the first network element can subsequently retrieve the first information from the third network element.

[0341] For example, after the first terminal obtains the first information, it can determine whether to accept or refuse to perform data collection based on the first information.

[0342] For example, the first terminal can obtain the first information, determine the second information based on the first information, and perform data collection based on the second information.

[0343] For example, after receiving the second information from the first network element, the first terminal can perform data collection based on the second information.

[0344] In this embodiment, when the first terminal obtains the first information, since the first information is data collection-related information provided by the first terminal, the data collection performed by the first terminal can be restricted through the first information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal. When the first terminal sends the first information to the first network element, the second network element, or the third network element, the first network element can determine whether the first terminal should perform data collection, reducing unnecessary collection triggered by the first network element, reducing the amount of data to be collected, and thus reducing the power consumption of the first terminal. When the first terminal determines to accept or refuse to perform data collection, unnecessary collection triggered by the first network element can be reduced, reducing the amount of data to be collected, and thus reducing the power consumption of the first terminal. When the first terminal determines the second information or receives the second information from the first network element, data collection can be performed based on the second information, reducing the amount of data to be collected and thus reducing the power consumption of the first terminal.

[0345] In some embodiments, obtaining the first information includes at least one of the following:

[0346] Obtain the first information stored locally by the first terminal;

[0347] The first information is obtained from the first network element.

[0348] In some embodiments, before obtaining the first information stored locally by the first terminal, method 320 further includes:

[0349] The first terminal stores the first information locally.

[0350] In some embodiments, the first information includes at least one of the following:

[0351] Information about one or more areas where data collection is permitted or not permitted;

[0352] Information on one or more time periods during which data collection is permitted or not permitted;

[0353] Information on one or more data types that allow or disallow data collection;

[0354] Information on one or more scenarios in which data collection is permitted or prohibited;

[0355] Information for the first area;

[0356] Instructions to allow or disallow terminals in the first area to perform data collection;

[0357] Information of the first data type;

[0358] Instructions to allow or disallow data collection of the first data type;

[0359] Information from the first time period;

[0360] Instructions to allow or disallow data collection during the first time period;

[0361] Information from the first scene;

[0362] Instructions for allowing or disallowing the collection of data in the first scenario.

[0363] In some embodiments, the second information includes at least one of the following:

[0364] A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area;

[0365] The second time period is used to instruct the first terminal to perform data collection within the second time period;

[0366] The second data type is used to instruct the first terminal to collect data of the second data type;

[0367] The second scenario is used to instruct the first terminal to collect data under the second scenario.

[0368] In some embodiments, determining whether to accept or reject data collection includes:

[0369] Based on at least one of the first and third information, determine whether to accept or refuse to perform data collection;

[0370] The third piece of information refers to information related to data collection provided by the data requesting device.

[0371] For example, if the first information includes information about a first region and the third information includes information about a third region, the third region is used to request the terminal to perform data collection when the third region is within that region; if the first region and the third region do not overlap, the first terminal can determine to refuse to perform data collection; if the first region and the third region overlap, the first terminal can determine to accept and perform data collection. Alternatively, if the first information includes information about a first time period and the third information includes information about a third time period, the third time period is used to request the terminal to perform data collection within that third time period; if the first time period and the third time period do not overlap, the first terminal can determine to refuse to perform data collection; if the first time period and the third time period overlap, the first terminal can determine to accept and perform data collection. Alternatively, if the first information includes information about a first data type and the third information includes information about a third data type, the third data type is used to request the terminal to collect data of that third data type; if the first data type and the third data type do not intersect, the first terminal can determine to refuse to perform data collection; if the first data type and the third data type intersect, the first terminal can determine to accept and perform data collection. Alternatively, if the first information includes information about a first scenario and the third information includes information about a third scenario, the third scenario is used to request the terminal to collect data under the third scenario; if the first scenario and the third scenario do not intersect, the first terminal can determine to refuse to perform data collection; if the first scenario and the third scenario intersect, the first terminal can determine to accept and perform data collection. This judgment logic also applies to the first network element determining whether to perform data collection.

[0372] In this embodiment, data collection can be refused by using at least one of the first information and the third information, which can reduce unnecessary data collection and thus reduce the power consumption of the first terminal.

[0373] In some embodiments, the method 320 further includes:

[0374] The first terminal receives the second request from the first network element;

[0375] The second request includes at least one of the following:

[0376] The first information or the second information;

[0377] The third information is information related to data collection provided by the data collection device;

[0378] The address information of the first network element.

[0379] In some embodiments, the second request is transmitted via control plane messages or user plane messages.

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

[0381] A third region, wherein the third region is used to request a terminal within the third region to perform data collection;

[0382] The third time period is used to request the terminal to perform data collection during the third time period;

[0383] A third data type, wherein the third data type is used to request the terminal to collect data of the third data type;

[0384] The third scenario is used to request the terminal to collect data under the third scenario;

[0385] Instructions for collecting user-plane data;

[0386] The purpose of data collection.

[0387] In some embodiments, the method 320 further includes:

[0388] The first terminal sends a response message to the first network element regarding the second request, the response message including at least one of the following:

[0389] Instructions for accepting or rejecting the second request;

[0390] The reason information indicating the reason for rejection includes at least one of the following:

[0391] The indication that the first terminal is not located in the third area;

[0392] The indication that the first terminal is not located in a portion of the third region;

[0393] The first terminal does not support instructions to perform data collection during the third time period;

[0394] The first terminal does not support instructions to perform data collection during a portion of the third time period;

[0395] The first terminal does not support instructions to collect data of the third data type;

[0396] The first terminal does not support instructions to collect data of some data types in the third data type;

[0397] The first terminal does not support instructions to collect data in the third scenario;

[0398] The first terminal does not support instructions to collect data in some scenarios of the third scenario.

[0399] It should be understood that the data acquisition method 320 includes the relevant processes executed by the first terminal, and its interaction with the first network element and the terms and methods involved are similar to those in method 310. Therefore, the specific content can be referred to the relevant description in method 310. To avoid repetition, it will not be repeated here.

[0400] Figure 5 This is a schematic flowchart of the data acquisition method 330 according to an embodiment of this application.

[0401] like Figure 5 As shown, the data acquisition method 330 may include:

[0402] S331, the second network element obtains the first information, which is information related to data collection provided by the first terminal.

[0403] S332, the second network element sends the first information to the first network element.

[0404] For example, the second network element can be a UDM or an NRF.

[0405] For example, the second network element may send the first information to the first network element based on the request of the first network element.

[0406] In this embodiment, the second network element sends the first information to the first network element, enabling the first network element to determine whether the first terminal is to perform data collection. This reduces unnecessary data collection triggered by the first network element, reduces the amount of data to be collected, and thus reduces the power consumption of the first terminal.

[0407] In some embodiments, S331 includes at least one of the following:

[0408] The second network element acquires the first information stored locally;

[0409] The second network element obtains the first information from the first terminal.

[0410] In some embodiments, before the second network element obtains the first information stored locally, the method 330 further includes:

[0411] The second network element obtains the first information from the first terminal and stores the first information locally.

[0412] In some embodiments, the first information includes at least one of the following:

[0413] Information about one or more areas where data collection is permitted or not permitted;

[0414] Information on one or more time periods during which data collection is permitted or not permitted;

[0415] Information on one or more data types that allow or disallow data collection;

[0416] Information on one or more scenarios in which data collection is permitted or prohibited;

[0417] Information for the first area;

[0418] Instructions to allow or disallow terminals in the first area to perform data collection;

[0419] Information of the first data type;

[0420] Instructions to allow or disallow data collection of the first data type;

[0421] Information from the first time period;

[0422] Instructions to allow or disallow data collection during the first time period;

[0423] Information from the first scene;

[0424] Instructions for allowing or disallowing the collection of data in the first scenario.

[0425] It should be understood that the data acquisition method 330 includes the relevant processes executed by the second network element. Its interaction with the first network element and the terms and methods involved are similar to those in method 310. Therefore, its specific content can be referred to the relevant description in method 310. To avoid repetition, it will not be repeated here.

[0426] Figure 6 This is a schematic flowchart of a data acquisition method 340 according to an embodiment of this application.

[0427] like Figure 6 As shown, the data acquisition method 340 may include:

[0428] S341, the third network element performs at least one of the following:

[0429] Obtain first information;

[0430] Send the identification information of the terminals in the third area to the first network element;

[0431] Send information related to data collection provided by terminals in the third area to the first network element;

[0432] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0433] For example, the third network element can be an AMF.

[0434] For example, the third network element sends data collection-related information provided by a terminal in the third area to the first network element. The data collection-related information provided by the terminal in the third area includes the first information, which is the data collection-related information provided by the first terminal.

[0435] In this embodiment, the third network element sends the identification information of the terminal in the third area to the first network element, or the third network element sends the data collection-related information provided by the terminal in the third area to the first network element, so that the first network element can collect data from the terminal in the third area.

[0436] In some embodiments, obtaining the first information includes at least one of the following:

[0437] Obtain the first information stored locally by the third network element;

[0438] Obtain the first information from the first terminal.

[0439] In some embodiments, before obtaining the first information stored locally by the third network element, method 340 further includes:

[0440] The first information is obtained from the first terminal and stored locally.

[0441] In some embodiments, the first information includes at least one of the following:

[0442] Information about one or more areas where data collection is permitted or not permitted;

[0443] Information on one or more time periods during which data collection is permitted or not permitted;

[0444] Information on one or more data types that allow or disallow data collection;

[0445] Information on one or more scenarios in which data collection is permitted or prohibited;

[0446] Information for the first area;

[0447] Instructions to allow or disallow terminals in the first area to perform data collection;

[0448] Information of the first data type;

[0449] Instructions to allow or disallow data collection of the first data type;

[0450] Information from the first time period;

[0451] Instructions to allow or disallow data collection during the first time period;

[0452] Information from the first scene;

[0453] Instructions for allowing or disallowing the collection of data in the first scenario.

[0454] In some embodiments, the method 340 further includes:

[0455] The third network element receives fourth information, which includes at least one of the following:

[0456] The third region;

[0457] Instructions to request information related to data collection provided by terminals within the third area;

[0458] Instructions to request the identification information of terminals within the third area.

[0459] It should be understood that the data acquisition method 340 includes the relevant processes executed by the third network element. Its interaction with the first network element and the terms and methods involved are similar to those in method 310. Therefore, its specific content can be referred to the relevant description in method 310. To avoid repetition, it will not be repeated here.

[0460] The data acquisition method provided in this application will be described below with reference to specific embodiments.

[0461] Example 1:

[0462] The first terminal stores the first information locally. When the second request sent by the first network element reaches the first terminal, the first terminal checks the first information locally and determines whether to accept or refuse to perform data collection based on the first information, or determines the second information based on the first information.

[0463] In this embodiment, since the first information is obtained taking into account the user's settings, the first terminal can selectively reject some second requests that do not conform to the first information when performing data collection by saving the first information, thereby avoiding subsequent signaling interaction and data collection, and thus saving terminal power.

[0464] Figure 7 This is a schematic flowchart of the data collection method 410 provided in the embodiments of this application.

[0465] It should be noted that, Figure 7 The first network element can be an LMF (UP on itself), a DCCF (UP on itself or an MFAF), a DCAF (UP on itself), an SMF (UP on a specific (configured) UPF), an AMF (UP on a specific (configured) UPF), an NWDAF, a UPF, or a newly established network function entity. If the first network element is an AMF, then... Figure 7 All messages exchanged between the AMF and the first network element are internal logic.

[0466] like Figure 7 The data collection method 410 may include:

[0467] S410-1, the first terminal locally configures and saves the first information.

[0468] The first information is information related to data collection provided by the first terminal.

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

[0470] Information for the first area;

[0471] Instructions to allow or disallow terminals in the first area to perform data collection;

[0472] Information of the first data type;

[0473] Instructions to allow or disallow data collection of the first data type;

[0474] Information from the first time period;

[0475] Instructions to allow or disallow data collection during the first time period;

[0476] Information from the first scene;

[0477] Instructions for allowing or disallowing the collection of data in the first scenario.

[0478] It should be noted that the information of the first area can be represented using a TA list or a cell list, or it can be represented using the coordinates of a physical area. When a UE is located within the first area, data collection for that UE is either permitted or prohibited. In one implementation, the first area can be an implicit indication of permitted and / or prohibited data collection areas. For example, if the first information includes {area: TAI a, TAI b}, it indicates that terminals in TAI a and TAI b are permitted to perform data collection. In another implementation, the first information can include an indication for explicitly indicating that terminals in the first area are permitted and / or prohibited from performing data collection. For example, if the first information includes {indication: permitted; area: cell A, cell B}, it indicates that terminals in cell A and cell B are permitted to perform data collection; for example, if the first information includes {indication: prohibited; area: TAI c, coordinates of a specific polygonal area}, it indicates that terminals in TAI c and terminals within the specific polygonal area are prohibited from performing data collection. In one implementation, the first information can include both permitted indications and associated permitted area information, and prohibited indications and associated prohibited area information.

[0479] It should also be noted that the first area mentioned in this application may be referred to as a restricted area for data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first area mentioned in this application may be referred to as a data collection allowed area, a data collection validity space, or a data collection dis-allowed area, etc.

[0480] It should be noted that the information of the first data type may include at least one of the following: measurement data, intermediate feature data of measurement data, configuration information for measurement, reference cell-related information, neighbor cell-related information, channel response-related information, PDP, channel matrix-related information, multipath angle information, and antenna-related information. In one implementation, the first data type may be an implicit indication of whether data collection is permitted or not. For example, if the first information includes {data type: channel matrix-related information}, it indicates that data collection of channel matrix-related information is permitted. In another implementation, the first information may include an indication for explicitly indicating whether data collection of the first data type is permitted or not. For example, if the first information includes {indication: permitted; data type: reference cell-related information}, it indicates that data collection of reference cell-related information is permitted; or if the first information includes {indication: not permitted; data type: channel response-related information}, it indicates that data collection of channel response-related information is not permitted. In one implementation, the first information may include both a permitted indication and associated permitted data type information, and a disallowed indication and associated disallowed data type information.

[0481] It should also be noted that the information regarding the first data type mentioned in this application may be referred to as a data type restriction or other description, and this application does not specifically limit it in this regard. For example, the first data type mentioned in this application may also be referred to as an allowed data type, a data collection validity data type, or a dis-allowed data type, etc.

[0482] It should be noted that the information of the first time period may include at least one of the following: the start time of the time period, the end time of the time period, the frequency of the time period (daily, weekly, monthly, yearly, etc.), the period of the time period, the start time of the first period, and the end time of the first period. When the data collection time is within the first time period, data collection of the UE is allowed or not allowed. In one implementation, the first time period can be a time period that implicitly indicates whether data collection is allowed or not. For example, when the first information includes {time period: start time 1, end time 1}, it indicates that data collection is allowed during the time period between start time 1 and end time 1. In another implementation, the first information may include an indication for explicitly indicating whether data collection is allowed or not during the first time period. For example, when the first information includes {indication: allowed; time period: start time 2, end time 2}, it indicates that data collection is allowed during the time period between start time 2 and end time 2; for example, when the first information includes {indication: not allowed; time period: start time 3, end time 3}, it indicates that data collection is not allowed during the time period between start time 3 and end time 3. In one implementation, the first information may include both permitted indications and associated permitted time period information, and disallowed indications and associated disallowed time period information.

[0483] It should also be noted that the information regarding the first time period mentioned in this application may be referred to as a time limit for data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first time period mentioned in this application may be referred to as a data collection allowed period, a data collection validity period, or a data collection dis-allowed period, etc.

[0484] It should be noted that the information in the first scenario may include at least one of the following: CSI measurement, positioning, sensing, and energy saving. Specifically, the data requesting device and the requested device agree that data in the first scenario needs to be reported / collected. When the data requesting device requests the requested device to collect data in the first scenario, if the requested device allows the collection of data in the first scenario, then the requested device reports the information / data in the first scenario. Conversely, if the requested device does not allow the collection of data in the first scenario, then the requested device refuses to provide all relevant information / data in the first scenario. In one implementation, the first scenario may be an implicitly indicated scenario that allows and / or disallows data collection. For example, when the first information includes {Scenario: Positioning}, it indicates that data collection in the positioning scenario is allowed. In another implementation, the first information may include an indication for explicitly indicating whether data collection in the first scenario is permitted and / or not permitted. For example, if the first information includes {indication: permitted; scenario: location}, it indicates that data collection in the location scenario is permitted; if the first information includes {indication: not permitted; scenario: perception}, it indicates that data collection in the perception scenario is not permitted. In one implementation, the first information may include both a permitted indication and associated permitted scenario information, and a disallowed indication and associated disallowed scenario information.

[0485] It should also be noted that the first scenario mentioned in this application may be referred to as a case restriction on data collection or other descriptions, and this application does not specifically limit it in this regard. For example, the first scenario mentioned in this application may be referred to as an allowed case, a data collection validity case, or a dis-allowed case, etc.

[0486] It should be noted that when the first information is stored locally on the first terminal, it can be stored in non-volatile memory or in a Universal Subscriber Identity Module (USIM) card. Optionally, the first information can be dynamically configured by the user through the phone's interface.

[0487] S411, the first network element receives a first request from the data requesting device, including at least one of the following: third information, address information of the data requesting device.

[0488] The third piece of information refers to information related to data collection provided by the data requesting device.

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

[0490] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0491] The third time period is used to request the terminal to perform data collection during the third time period;

[0492] A third data type, wherein the third data type is used to request the terminal to collect data of the third data type;

[0493] The third scenario is used to request the terminal to collect data under the third scenario;

[0494] Instructions for collecting user-plane data;

[0495] The purpose of data collection.

[0496] Optionally, the purpose of the data collection may include at least one of the following: model training, model inference, performance monitoring, etc.

[0497] Optionally, the first request may further include at least one of the following: an instruction to perform data collection on data from any terminal within the third area; and an identifier of the terminal requiring data collection. If the first request includes an instruction to perform data collection on data from any terminal within the third area, the first network element can obtain the identifier information of the terminal within the third area from the third network element, and request the terminal within the third area to perform data collection based on the identifier information of the terminal within the third area. If the first request includes the identifier of the terminal requiring data collection, the first network can directly request the terminal requiring data collection to perform data collection based on the identifier of the terminal requiring data collection.

[0498] S412, the first network element sends a query request to the AMF.

[0499] Optionally, the first network element sends a Namf_EventExposure_subscriber message to the AMF to request the identification information of the terminals in the third area.

[0500] S413, the first network element receives the response to the query request from the AMF.

[0501] Optionally, the AMF responds to the query request to the first network element, which may include the identification information of the terminals in the third area. If the first request includes an instruction to perform data collection on any terminal in the third area, steps S412-S413 are executed; if the first request includes the identification information of the terminal that needs to perform data collection, steps S412-S413 are skipped. The AMF sends the identification information of the terminals in the third area to the LMF, including the identification information of the first terminal. In one implementation, after receiving the identification information of the terminals in the third area, the first network element decides to perform data collection on all or some of the terminals in the third area, i.e., sends a data collection request, triggering the terminals to perform data collection and reporting. In this case, these terminals can be understood as the first terminal in this application.

[0502] S414, the first network element sends a request to the UDM to obtain the user's intention.

[0503] For each terminal identified by the identification information of the terminal in the third area, or for each terminal among the terminals that need to perform data collection received in the first request, the first network element may optionally request the user consent of each terminal from the UDM.

[0504] S415, the first network element receives the user's intention from the UDM.

[0505] The first network element receives the user's intentions from each terminal from the UDM.

[0506] It should be noted that the first network element can determine the terminal to perform data collection based on the user's intention for each terminal. When the user's intention for a terminal indicates that the terminal has authorized data collection for a specific purpose, such as for model training, the first network element will proceed with subsequent steps and may be identified as the terminal to perform data collection. If the user's intention for a terminal indicates that the terminal has not authorized data collection for a specific purpose, such as the aforementioned purpose for model inference, the first network element will skip subsequent steps and will not collect data from that terminal.

[0507] It should be noted that if the first request does not contain information about the third time period, the first network element can determine the third time period.

[0508] S416, the first network element sends a second request to the AMF, including third information.

[0509] Optionally, when the first network element sends the second request to the first terminal via CP signaling, the first network element sends the second request to the AMF.

[0510] Optionally, the first network element sends a first message to the AMF, the first message including the identification information of the first terminal and the second request. The second request carries the third information. The second request can be a container (e.g., a container in a downlink NAS TRANSPORT message or a container in a configuration update command).

[0511] S417, AMF sends a second request to the first terminal.

[0512] After receiving the second request, the AMF forwards it to the first terminal.

[0513] S418, the first terminal determines whether to accept or refuse to perform data collection, or determines second information based on the first information.

[0514] Optionally, when the first network element sends the second request to the first terminal via CP signaling, the first network element sends the second request to the AMF.

[0515] Optionally, after receiving the second request, the first terminal may determine whether to accept or refuse to perform data collection based on the third information in the second request and the first information stored locally on the first terminal, or determine the second information based on the third information and the first information stored locally on the first terminal.

[0516] For example, if the first information includes information about a first region and the third information includes information about a third region, and if the first region and the third region do not overlap, the first terminal can determine to refuse data collection; if the first region and the third region overlap, the first terminal can determine to accept and execute data collection. Alternatively, if the first information includes information about a first time period and the third information includes information about a third time period; and if the first time period and the third time period do not overlap, the first terminal can determine to refuse data collection; and if the first time period and the third time period overlap, the first terminal can determine to accept and execute data collection. Alternatively, if the first information includes information about a first data type and the third information includes information about a third data type; and if the first data type and the third data type do not intersect, the first terminal can determine to refuse data collection; and if the first data type and the third data type intersect, the first terminal can determine to accept and execute data collection. Alternatively, if the first information includes information about a first scenario and the third information includes information about a third scenario; and if the first scenario and the third scenario do not intersect, the first terminal can determine to refuse data collection; and if the first scenario and the third scenario intersect, the first terminal can determine to accept and execute data collection.

[0517] For example, if the first information includes information about a first region, the second information includes information about a second region, and the third information includes information about a third region, the first terminal can determine the overlapping area of ​​the first region and the second region as the second region. Alternatively, if the first information includes information about a first time period, the second information includes information about a second time period, and the third information includes a third time period, the first terminal can determine the overlapping time period of the first time period and the third time period as the second time period. Alternatively, if the first information includes information about a first data type, the second information includes information about a second data type, and the third information includes a third data type, the first terminal can determine the intersection of the first data type and the third data type as the second data type. Alternatively, if the first information includes information about a first scene, the second information includes information about a second scene, and the third information includes a third scene, the first terminal can determine the intersection of the first scene and the third scene as the second scene.

[0518] S419, the first terminal sends a response message for the second request to the first network element through the AMF, including at least one of the following: an indication to accept or reject the second request, and reason information.

[0519] Optionally, the first terminal may determine whether to accept or reject the second request based on first information stored locally on the first terminal, that is, the response message of the second request may include at least one of the following:

[0520] The cause information includes at least one of the following:

[0521] 1. Instructions for accepting or rejecting the second request.

[0522] 2. Reason information indicating the reason for rejection, said reason information including at least one of the following:

[0523] The indication that the first terminal is not located in the third area;

[0524] The indication that the first terminal is not located in a portion of the third region;

[0525] The first terminal does not support instructions to perform data collection during the third time period;

[0526] The first terminal does not support instructions to perform data collection during a portion of the third time period;

[0527] The first terminal does not support instructions to collect data of the third data type;

[0528] The first terminal does not support instructions to collect data of some data types in the third data type;

[0529] The first terminal does not support instructions to collect data in the third scenario;

[0530] The first terminal does not support instructions to collect data in some scenarios of the third scenario.

[0531] 3. Indicate the reason for acceptance, such as including at least one of the following:

[0532] The indication of the first terminal within the third area;

[0533] The indication of the first terminal within a portion of the third region;

[0534] The first terminal supports instructions to perform data collection during the third time period;

[0535] The first terminal supports instructions to perform data collection during a portion of the third time period;

[0536] The first terminal supports instructions to collect data of the third data type;

[0537] The first terminal supports instructions to collect data of some data types in the third data type;

[0538] The first terminal supports instructions to collect data in the third scenario;

[0539] The first terminal supports instructions to collect data from certain scenarios within the third scenario.

[0540] S4110, the first terminal establishes a UP connection with the first network element.

[0541] Optionally, if the second request includes the address information of the first network element, the first terminal can establish a UP connection with the first network element based on the address information of the first network element, so that the first terminal can send data packets to the first network element through RAN-UPF.

[0542] S4111a, the first terminal receives a second request from the first network element, including third information.

[0543] Optionally, when the first network element sends the second request to the first terminal via UP signaling, the first network element sends the second request to the first terminal.

[0544] It should be noted that the second request can be sent to the first terminal via CP signaling (i.e., via AMF, i.e., S416~S417); or via UP signaling (i.e., via UPF, i.e., S4111a). In practical applications, one of the two schemes is selected.

[0545] It should be noted that when the first network element sends the second request to the first terminal via CP signaling, the first network element can also resend the second request to the first terminal via UP message. For example, the second request sent via CP signaling may include some information in the third information, and the second request sent via UP may include information in the third information other than the information sent via CP.

[0546] S4111b, the first terminal determines whether to accept or refuse to perform data collection, or determines second information based on the first information.

[0547] It should be understood that S4111b is the same as S418, and its specific solution can be found in the relevant description of S418. To avoid repetition, it will not be repeated here.

[0548] S4111c, the first terminal sends a response message to the first network element for the second request, including at least one of the following: an indication to accept or reject the second request, or reason information.

[0549] It should be understood that S4111c is the same as S419, and its specific scheme can be found in the relevant description of S419. To avoid repetition, it will not be repeated here.

[0550] S4112, the first terminal reports data via UP connection.

[0551] The first terminal sends the collected data to the first network element through the user plane connection established by S4110.

[0552] S4113, the first network element sends a data notification to the data requesting device.

[0553] Upon receiving data from the first terminal, the first network element verifies whether the data sent by the first terminal is the data that needs to be collected. If the verification is successful, the first network element saves this data, for example, in the ADRF. If the verification fails, the first network element can repeat steps S416 to S4112 until the required data is collected, or the first network element can abandon collecting data from the first terminal. After collecting the data, the first network element sends the collected data to the data requesting device according to the address information of the data requesting device in the first request received in step S421.

[0554] Example 2:

[0555] The first information is stored in the UDM. When the data requesting device requests data collection from the first terminal, the first network element can check the first information in the UDM and consider whether to collect the data from the first terminal based on the first information.

[0556] In this embodiment, from the start of data collection, data requests sent from the first network element to the first terminal can be avoided, thereby avoiding unnecessary signaling interactions and saving terminal power. Furthermore, the first terminal can dynamically update the first information stored in the UDM.

[0557] Figure 8 This is a schematic flowchart of the data collection method 420 provided in the embodiments of this application.

[0558] It should be noted that, Figure 8 The first network element can be an LMF (UP on itself), a DCCF (UP on itself or an MFAF), a DCAF (UP on itself), an SMF (UP on a specific (configured) UPF), an AMF (UP on a specific (configured) UPF), an NWDAF, a UPF, or a newly established network function entity. If the first network element is an AMF, then... Figure 8 All messages exchanged between the AMF and the first network element are internal logic.

[0559] like Figure 8The data collection method 420 may include:

[0560] S420-1, the first terminal sends a privacy setting message to the AMF, including first information.

[0561] The first information is information related to data collection provided by the first terminal.

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

[0563] Information for the first area;

[0564] Instructions to allow or disallow terminals in the first area to perform data collection;

[0565] Information of the first data type;

[0566] Instructions to allow or disallow data collection of the first data type;

[0567] Information from the first time period;

[0568] Instructions to allow or disallow data collection during the first time period;

[0569] Information from the first scene;

[0570] Instructions for allowing or disallowing the collection of data in the first scenario.

[0571] It should be understood that the description of the first information can be referred to the description of Embodiment 1, and will not be repeated here to avoid repetition.

[0572] S420-2, First Information Update Process.

[0573] S420-3, the first terminal receives a privacy response message from the AMF.

[0574] When the first terminal sends the first information to the UDM via the AMF, the first terminal can send it to the UDM in the form of a ULNAS TRANSPORT message, a registration request message, or a configuration update complete message.

[0575] S420-4, UDM saves or updates first information.

[0576] When the first information is saved in the UDM, the first information can be part of the user's intention of the first terminal, or it can be a separate piece of information.

[0577] S421~S423.

[0578] It should be understood that the descriptions of S421 to S423 can be found in the relevant content of S411 to S413 of Embodiment 1, and will not be repeated here to avoid repetition.

[0579] S424, the first network element sends a request to the UDM to obtain the user's intention.

[0580] S425, the first network element receives the user's intention from the UDM, including the first information.

[0581] In S424-S425, the first network element obtains the first information of the first terminal from the UDM. Specifically, the first network element sends a retrieval message to the UDM, such as a Nudm_SDM_Get message, which carries the data type "user intention" or "data collection configuration". After receiving the retrieval message, the UDM replies with the first information to the first network element. In one implementation, the first information includes the user intention.

[0582] S426, the first network element determines, based on the first information, to perform data collection on the first terminal, or determines the second information.

[0583] Optionally, the first network element may determine whether to accept or refuse to perform data collection based on the third information in the first request and the first information stored locally by the first network element, or determine the second information based on the third information in the first request and the first information stored locally by the first network element.

[0584] For example, if the first information includes information about a first region and the third information includes information about a third region, and if the first terminal is not located in either the first region or the third region, the first network element can determine not to collect data from the first terminal. If the first terminal is located in an overlapping area of ​​the first region and the third region, the first network element can determine to collect data from the first terminal. Alternatively, if the first information includes information about a first time period and the third information includes information about a third time period; if the first time period and the third time period do not overlap, the first network element can determine not to collect data from the first terminal. If the first time period and the third time period overlap, the first network element can determine to collect data from the first terminal. Alternatively, if the first information includes information about a first data type and the third information includes information about a third data type; if the first data type and the third data type do not intersect, the first network element can determine not to collect data from the first terminal. If the first data type and the third data type intersect, the first network element can determine to collect data from the first terminal. Alternatively, if the first information includes information about the first scenario and the third information includes information about the third scenario; if the first scenario and the third scenario do not intersect, the first network element can determine not to perform data collection on the first terminal; if the first scenario and the third scenario intersect, the first network element can determine to perform data collection on the first terminal.

[0585] For example, if the first information includes information about a first region, the second information includes information about a second region, and the third information includes information about a third region, the first network element can determine the overlapping area of ​​the first region and the second region as the second region. Alternatively, if the first information includes information about a first time period, the second information includes information about a second time period, and the third information includes information about a third time period, the first network element can determine the overlapping time period of the first time period and the third time period as the second time period. Alternatively, if the first information includes information about a first data type, the second information includes information about a second data type, and the third information includes information about a third data type, the first network element can determine the intersection of the first data type and the third data type as the second data type. Alternatively, if the first information includes information about a first scene, the second information includes information about a second scene, and the third information includes information about a third scene, the first network element can determine the intersection of the first scene and the third scene as the second scene.

[0586] It should be noted that the first network element can check the user's intentions at the first terminal in this step to determine whether to collect data from the first terminal.

[0587] It should be noted that if the first request does not contain information about the third time period, the first network element can determine the third time period.

[0588] S427, the first network element sends a second request to the AMF, including second information.

[0589] Optionally, when the first network element sends the second request to the first terminal via CP signaling, the first network element sends the second request to the AMF.

[0590] Optionally, the first network element sends a first message to the AMF, the first message including the identification information of the first terminal and the second request. The second request carries the second information. The second request can be a container (such as a container in a downlink NAS TRANSPORT message or a container in a configuration update command).

[0591] S428, AMF sends a second request to the first terminal.

[0592] After receiving the second request, the AMF forwards it to the first terminal.

[0593] S429, the first terminal sends a response message for the second request to the first network element through the AMF, including at least one of the following: an indication to accept or reject the second request, and reason information.

[0594] Optionally, the first terminal may determine whether to accept or reject the second request based on its own situation (e.g., communication status, battery status), that is, the response message of the second request may include at least one of the following:

[0595] 1. Instructions for accepting or rejecting the second request.

[0596] 2. Reason information indicating the reason for rejection, said reason information including at least one of the following:

[0597] An indication that the first terminal is not in the second area;

[0598] The first terminal is not located in a portion of the second region;

[0599] The first terminal does not support instructions to perform data collection during the second time period;

[0600] The first terminal does not support instructions to perform data collection during a portion of the second time period;

[0601] The first terminal does not support instructions to collect data of the second data type;

[0602] The first terminal does not support instructions to collect data of some data types in the second data type;

[0603] The first terminal does not support instructions to collect data in the second scenario;

[0604] The first terminal does not support instructions to collect data from certain scenarios in the second scenario.

[0605] 3. Indicate the reason for acceptance, such as including at least one of the following:

[0606] The indication of the first terminal within the second area;

[0607] The indication of the first terminal within a portion of the second region;

[0608] The first terminal supports instructions to perform data collection during the second time period;

[0609] The first terminal supports instructions to collect data during a portion of the second time period;

[0610] The first terminal supports instructions to collect data of the second data type;

[0611] The first terminal supports instructions to collect data of some data types in the second data type;

[0612] The first terminal supports instructions to collect data in the second scenario;

[0613] The first terminal supports instructions to collect data from certain scenarios in the second scenario.

[0614] S4210, the first terminal establishes a UP connection with the first network element.

[0615] Optionally, if the second request includes the address information of the first network element, the first terminal can establish a UP connection with the first network element based on the address information of the first network element, so that the first terminal can send data packets to the first network element through RAN-UPF.

[0616] S4211a, the first terminal receives a second request from the first network element, including second information.

[0617] Optionally, when the first network element sends the second request to the first terminal via UP signaling, the first network element sends the second request to the first terminal.

[0618] It should be noted that the second request can be sent to the first terminal via CP signaling (i.e., via AMF, i.e., S426~S427); or via UP signaling (i.e., via UPF, i.e., S4211a). In practical applications, one of the two schemes is selected.

[0619] It should be noted that when the first network element sends the second request to the first terminal via CP signaling, the first network element can also resend the second request to the first terminal via UP message. For example, the second request sent via CP signaling may include some information from the second information, and the second request sent via UP may include information from the second information other than the information sent via CP.

[0620] S4211b, the first terminal sends a response message to the first network element for the second request, including at least one of the following: an indication to accept or reject the second request, or reason information.

[0621] It should be understood that S4211b is the same as S429, and its specific scheme can be found in the relevant description of S429. To avoid repetition, it will not be repeated here.

[0622] S4212, the first terminal reports data via UP connection.

[0623] The first terminal sends the collected data to the first network element through the user plane connection established by S4210.

[0624] S4213, the first network element sends a data notification to the data requesting device.

[0625] Upon receiving data from the first terminal, the first network element verifies whether the data sent by the first terminal is the data that needs to be collected. If the verification is successful, the first network element saves this data, for example, in the ADRF. If the verification fails, the first network element can repeat steps S426 to S4212 until the required data is collected, or the first network element can abandon collecting data from the first terminal. After collecting the data, the first network element sends the collected data to the data requesting device according to the address information of the data requesting device in the first request received in step S421.

[0626] Example 3:

[0627] Similar to Embodiment 2, the first information is stored in the UDM. The first request is received from the data requesting device, the first information is obtained from the UDM, and the first information and the third information carried in the first request are sent to the first terminal through the second request. The first terminal then determines whether to accept the second request.

[0628] In this embodiment, when the first terminal performs data collection, it can selectively reject some second requests that do not conform to the first and third information, thereby avoiding subsequent signaling interactions and data collection, and thus saving terminal power.

[0629] Figure 9 This is a schematic flowchart of the data collection method 430 provided in the embodiments of this application.

[0630] It should be noted that, Figure 9 The first network element can be an LMF (UP on itself), a DCCF (UP on itself or an MFAF), a DCAF (UP on itself), an SMF (UP on a specific (configured) UPF), an AMF (UP on a specific (configured) UPF), an NWDAF, a UPF, or a newly established network function entity. If the first network element is an AMF, then... Figure 9 All messages exchanged between the AMF and the first network element are internal logic.

[0631] like Figure 9 The data collection method 430 may include:

[0632] S430-1~S430-3.

[0633] It should be understood that S430-1 to S430-3 are the same as S420-1 to S420-3. For specific solutions, please refer to the relevant descriptions of S420-1 to S420-3. To avoid repetition, they will not be repeated here.

[0634] S431~S435.

[0635] It should be understood that S431 to S435 are the same as S421 to S425. For specific solutions, please refer to the relevant descriptions of S421 to S425. To avoid repetition, they will not be repeated here.

[0636] S436, the first network element sends a second request to the AMF, including first information and third information.

[0637] The difference from Example 2 is as follows:

[0638] The first network element does not make a judgment, that is, it does not execute S426 of Embodiment 2, but directly sends the third information and the first information in the first request received in S431 to the first terminal, and the first terminal makes a judgment.

[0639] S437, AMF sends a second request to the first terminal.

[0640] After receiving the second request, the AMF forwards it to the first terminal.

[0641] S438, the first terminal determines whether to accept or refuse to perform data collection, or determines second information based on the first information.

[0642] In one implementation, when the first network element determines that the third region in the first request and the first region in the first information partially overlap or partially do not overlap, for example, the third region includes {cell A, cell B, cell C} and the first information includes {instruction: allow; region: cell A, cell D}, the first network element sends the third information in the first request, optionally including the first information, to the first terminal, and the first terminal decides whether to accept or refuse to perform data collection.

[0643] It should be understood that S438 is the same as S418, and the specific solution can be found in the relevant description of S418. To avoid repetition, it will not be repeated here.

[0644] S439~S4310.

[0645] It should be understood that S439~S4310 are the same as S419~S4110. For specific solutions, please refer to the relevant descriptions of S419~S4110. To avoid repetition, they will not be repeated here.

[0646] S4311a, the first terminal receives a second request from the first network element, including second information.

[0647] Optionally, when the first network element sends the second request to the first terminal via UP signaling, the first network element sends the second request to the first terminal.

[0648] It should be noted that the second request can be sent to the first terminal via CP signaling (i.e., via AMF, i.e., S426~S427); or via UP signaling (i.e., via UPF, i.e., S4211a). In practical applications, one of the two schemes is selected.

[0649] It should be noted that when the first network element sends the second request to the first terminal via CP signaling, the first network element can also resend the second request to the first terminal via UP message. For example, the second request sent via CP signaling may include some information from the second information, and the second request sent via UP may include information from the second information other than the information sent via CP.

[0650] S4311b, the first terminal sends a response message to the first network element for the second request, including at least one of the following: an indication to accept or reject the second request, or reason information.

[0651] It should be understood that S4311b is the same as S439, and its specific scheme can be found in the relevant description of S439. To avoid repetition, it will not be repeated here.

[0652] S4312, the first terminal reports data via UP connection.

[0653] The first terminal sends the collected data to the first network element through the user plane connection established by S4310.

[0654] S4313, the first network element sends a data notification to the data requesting device.

[0655] Upon receiving data from the first terminal, the first network element verifies whether the data sent by the first terminal is the data that needs to be collected. If the verification is successful, the first network element saves this data, for example, in the ADRF. If the verification fails, the first network element can repeat steps S436 to S4312 until the required data is collected, or the first network element can abandon collecting data from the first terminal. After collecting the data, the first network element sends the collected data to the data requesting device according to the address information of the data requesting device in the first request received in step S431.

[0656] Example 4:

[0657] The first information is directly stored in the first network element. When the first network element receives the first request for the first terminal, it can directly decide whether to collect data from the first terminal based on the first information.

[0658] In this embodiment, from the start of data collection, data requests sent from the first network element to the first terminal can be avoided, thereby preventing unnecessary signaling interactions and saving terminal power. Furthermore, the first terminal can dynamically update the first information stored in the first network element.

[0659] Figure 10 This is a schematic flowchart of the data collection method 440 provided in the embodiments of this application.

[0660] It should be noted that, Figure 10 The first network element can be an LMF (UP on itself), a DCCF (UP on itself or an MFAF), a DCAF (UP on itself), an SMF (UP on a specific (configured) UPF), an AMF (UP on a specific (configured) UPF), an NWDAF, a UPF, or a newly established network function entity. If the first network element is an AMF, then... Figure 10All messages exchanged between the AMF and the first network element are internal logic.

[0661] like Figure 10 The data collection method 440 may include:

[0662] S440-1, the first terminal sends a parameter update request to the first network element.

[0663] The parameter update request includes first information, which is information related to data collection provided by the first terminal.

[0664] Optionally, the first terminal may send the first information to the first network element via CP signaling (such as UL NAS TRANSPORT message, registration request message, PDU session establishment request message, LPP message, or LCS-SS message) or UP message (UP message between the first terminal and the first network element, such as LCS-UPP uplink message).

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

[0666] Information for the first area;

[0667] Instructions to allow or disallow terminals in the first area to perform data collection;

[0668] Information of the first data type;

[0669] Instructions to allow or disallow data collection of the first data type;

[0670] Information from the first time period;

[0671] Instructions to allow or disallow data collection during the first time period;

[0672] Information from the first scene;

[0673] Instructions for allowing or disallowing the collection of data in the first scenario.

[0674] It should be understood that the description of the first information can be referred to the description of Embodiment 1, and will not be repeated here to avoid repetition.

[0675] S440-2, the first terminal receives a parameter update reply message from the first network element.

[0676] S440-3, the first network element saves or updates the first information.

[0677] S441~S445.

[0678] It should be understood that the descriptions of S441 to S445 can be found in the relevant content of S411 to S415 of Example 1, and will not be repeated here to avoid repetition.

[0679] S446~S4413.

[0680] It should be understood that the descriptions of S446 to S4413 can be found in the relevant content of S426 to S4213 of Example 2, and will not be repeated here to avoid repetition.

[0681] Example 5:

[0682] The first information is stored directly in the AMF. When the first network element receives the first request for the first terminal, it can obtain the first information from the AMF and decide whether to collect data from the first terminal based on the obtained first information.

[0683] In this embodiment, from the start of data collection, data requests sent from the first network element to the first terminal can be avoided, thereby avoiding unnecessary signaling interactions and saving terminal power. Furthermore, the first terminal can dynamically update the first information stored in the AMF.

[0684] Figure 11 This is a schematic flowchart of the data collection method 450 provided in the embodiments of this application.

[0685] It should be noted that, Figure 11 The first network element can be an LMF (UP on itself), a DCCF (UP on itself or an MFAF), a DCAF (UP on itself), an SMF (UP on a specific (configured) UPF), an AMF (UP on a specific (configured) UPF), an NWDAF, a UPF, or a newly established network function entity. If the first network element is an AMF, then... Figure 11 All messages exchanged between the AMF and the first network element are internal logic.

[0686] like Figure 11 The data collection method 450 may include:

[0687] S450-1, the first terminal sends a parameter update request to the AMF.

[0688] The parameter update request includes first information, which is information related to data collection provided by the first terminal.

[0689] Optionally, the first terminal may send the first information to the AMF via a UL NAS TRANSPORT message or a registration request message.

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

[0691] Information for the first area;

[0692] Instructions to allow or disallow terminals in the first area to perform data collection;

[0693] Information of the first data type;

[0694] Instructions to allow or disallow data collection of the first data type;

[0695] Information from the first time period;

[0696] Instructions to allow or disallow data collection during the first time period;

[0697] Information from the first scene;

[0698] Instructions for allowing or disallowing the collection of data in the first scenario.

[0699] It should be understood that the description of the first information can be referred to the description of Embodiment 1, and will not be repeated here to avoid repetition.

[0700] S450-2, the first terminal receives a parameter update reply message from the AMF.

[0701] S450-3, AMF saves or updates first information.

[0702] AMF locally stores the first information, such as the context information of the first terminal.

[0703] S451.

[0704] It should be understood that the description of S451 can be found in the relevant content of S411 in Embodiment 1, and will not be repeated here to avoid repetition.

[0705] S452, the first network element sends a query request to the AMF, including the fourth information.

[0706] Optionally, the first network element sends a Namf_EventExposure_subscriber message to the AMF, which may include fourth information, the fourth information including at least one of the following:

[0707] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0708] Instructions to request information related to data collection provided by terminals within the third area;

[0709] Instructions to request the identification information of terminals within the third area.

[0710] S453, AMF determines the identification information of the target terminal in the third area, and the information related to data collection provided by the target terminal in the third area.

[0711] Optionally, the fourth information includes the third region and at least one of the following:

[0712] Instructions to request information related to data collection provided by terminals within the third area;

[0713] Instructions to request the identification information of terminals within the third area.

[0714] After receiving the fourth information, if the fourth information includes the third area, the third network element determines the identification information of the terminal located in the third area.

[0715] For any terminal within the third area, such as the first terminal within the third area, the AMF checks both the first and third areas to determine whether the first terminal allows or supports data collection within the third area. If allowed, at least one of the identification information and first information of the first terminal is sent to the first network element in S454; if not allowed, at least one of the identification information and first information of the first terminal is not sent to the first network element. The data collection-related information provided by the terminals within the third area can be understood as acquiring data collection-related information from all terminals within the third area, including the first terminal. This data collection-related information includes the terminal's data collection capability (e.g., whether the terminal supports performing data collection) and the terminal's first information.

[0716] S454, the response of the AMF to the query request sent to the first network element includes at least one of the following: identification information of the target terminal in the third area, and information related to data collection provided by the target terminal in the third area.

[0717] If the fourth information includes an instruction to request the identification information of terminals within the third area, the response to the query request includes the identification information of terminals within the third area. If the fourth information includes an instruction to request the acquisition of data collection-related information provided by terminals within the third area, the response to the query request includes the identification information of terminals within the third area, and the data collection-related information provided by terminals within the third area is sent. The AMF sends the identification information and / or data collection-related information of terminals within the third area to the LMF, including the first terminal. In one implementation, after receiving the identification information and / or data collection-related information of terminals within the third area, the first network element decides to collect data from all or some terminals within the third area, i.e., sends a data collection request, triggering the terminals to perform data collection and reporting. In this case, these terminals can be understood as the first terminal in this application.

[0718] S455a~S455b.

[0719] It should be understood that the descriptions of S455a to S455b can be found in the relevant content of S414 to S415 of Example 1, and will not be repeated here to avoid repetition.

[0720] S456~S4513.

[0721] It should be understood that the descriptions of S456 to S4513 can be found in the relevant content of S426 to S4213 of Example 2, and will not be repeated here to avoid repetition.

[0722] The data acquisition method provided in this application can be executed by a data acquisition device. This application uses a data acquisition device to perform the data acquisition method as an example to illustrate the data acquisition device provided in this application.

[0723] This application provides a data acquisition device. As an example, the data acquisition device may be a communication device or a component within a communication device, such as a chip. The communication device may be a first terminal, a first network element, a second network element, or a third network element, etc. Exemplarily, the first terminal may include, but is not limited to, the type of terminal 11 listed above, and the first network element, second network element, or third network element may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

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

[0725] For details, see Figure 12 When the data acquisition device is a first network element or a component of the first network element, the data acquisition device 510 includes a processing module 511 and a sending module 512; the processing module 511 is used to acquire first information, which is information related to data collection provided by the first terminal.

[0726] The processing module 511 is further configured to perform at least one of the following:

[0727] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0728] Determine the second piece of information;

[0729] Alternatively, the sending module 512 may be used to perform at least one of the following:

[0730] Send the first information to the first terminal;

[0731] Send the second information to the first terminal.

[0732] In some embodiments, the processing module 511 is specifically configured to perform at least one of the following:

[0733] Retrieve the first information stored locally;

[0734] The first information is obtained from the second or third network element;

[0735] Obtain the first information from the first terminal.

[0736] In some embodiments, before obtaining the first information stored locally, the processing module 511 is further configured to:

[0737] The first information is obtained from the first terminal and stored locally.

[0738] In some embodiments, the first information includes at least one of the following:

[0739] Information about one or more areas where data collection is permitted or not permitted;

[0740] Information on one or more time periods during which data collection is permitted or not permitted;

[0741] Information on one or more data types that allow or disallow data collection;

[0742] Information on one or more scenarios in which data collection is permitted or prohibited;

[0743] Information for the first area;

[0744] Instructions to allow or disallow terminals in the first area to perform data collection;

[0745] Information of the first data type;

[0746] Instructions to allow or disallow data collection of the first data type;

[0747] Information from the first time period;

[0748] Instructions to allow or disallow data collection during the first time period;

[0749] Information from the first scene;

[0750] Instructions for allowing or disallowing the collection of data in the first scenario.

[0751] In some embodiments, the second information includes at least one of the following:

[0752] A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area;

[0753] The second time period is used to instruct the first terminal to perform data collection within the second time period;

[0754] The second data type is used to instruct the first terminal to collect data of the second data type;

[0755] The second scenario is used to instruct the first terminal to collect data under the second scenario.

[0756] In some embodiments, the processing module 511 is specifically used for:

[0757] The second information is determined based on at least one of the first information and the third information;

[0758] The third piece of information refers to information related to data collection provided by the data requesting device.

[0759] In some embodiments, the device 510 further includes a first receiving module, configured to:

[0760] Receive the first request from the data requesting device;

[0761] The sending module 512 is also used to send a second request to the first terminal;

[0762] The first request includes at least one of the following:

[0763] The third information is information related to data collection provided by the data collection device;

[0764] Address information of the data requester's device;

[0765] The second request includes at least one of the following:

[0766] The first information or the second information;

[0767] The third information;

[0768] The address information of the first network element.

[0769] In some embodiments, the second request is transmitted via control plane messages or user plane messages.

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

[0771] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0772] The third time period is used to request the terminal to perform data collection during the third time period;

[0773] A third data type, wherein the third data type is used to request the terminal to collect data of the third data type;

[0774] The third scenario is used to request the terminal to collect data under the third scenario;

[0775] Instructions for collecting user-plane data;

[0776] The purpose of data collection.

[0777] In some embodiments, the device 510 further includes a second receiving module, configured to:

[0778] The response message for the second request is received from the first terminal, and the response message includes at least one of the following:

[0779] Instructions for accepting or rejecting the second request;

[0780] The reason information indicating the reason for rejection includes at least one of the following:

[0781] The indication that the first terminal is not located in the third area;

[0782] The indication that the first terminal is not located in a portion of the third region;

[0783] The first terminal does not support instructions to perform data collection during the third time period;

[0784] The first terminal does not support instructions to perform data collection during a portion of the third time period;

[0785] The first terminal does not support instructions to collect data of the third data type;

[0786] The first terminal does not support instructions to collect data of some data types in the third data type;

[0787] The first terminal does not support instructions to collect data in the third scenario;

[0788] The first terminal does not support instructions to collect data in some scenarios of the third scenario.

[0789] In some embodiments, the sending module 512 is further configured to:

[0790] Send a fourth message to the third network element, the fourth message including at least one of the following:

[0791] A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located;

[0792] Instructions to request information related to data collection provided by terminals within the third area;

[0793] Instructions to request the identification information of terminals within the third area.

[0794] See Figure 13 When the data acquisition device is a first terminal or a component of the first terminal, the data acquisition device 520 includes a processing module 521, a sending module 522 and a receiving module 523.

[0795] The processing module 521 is configured to perform at least one of the following:

[0796] Obtain first information;

[0797] Decide whether to accept or refuse data collection;

[0798] The second information is determined based on the first information;

[0799] Alternatively, the sending module 522 may be used to send first information to the first network element, the second network element, or the third network element;

[0800] Alternatively, the receiving module 523 may be used to receive second information from the first network element;

[0801] The first information is information related to data collection provided by the first terminal.

[0802] In some embodiments, the processing module 521 is specifically configured to perform at least one of the following:

[0803] Obtain the first information stored locally by the first terminal;

[0804] The first information is obtained from the first network element.

[0805] In some embodiments, before the processing module 521 obtains the first information stored locally by the first terminal, it is further configured to:

[0806] Store the first information locally.

[0807] In some embodiments, the first information includes at least one of the following:

[0808] Information about one or more areas where data collection is permitted or not permitted;

[0809] Information on one or more time periods during which data collection is permitted or not permitted;

[0810] Information on one or more data types that allow or disallow data collection;

[0811] Information on one or more scenarios in which data collection is permitted or prohibited;

[0812] Information for the first area;

[0813] Instructions to allow or disallow terminals in the first area to perform data collection;

[0814] Information of the first data type;

[0815] Instructions to allow or disallow data collection of the first data type;

[0816] Information from the first time period;

[0817] Instructions to allow or disallow data collection during the first time period;

[0818] Information from the first scene;

[0819] Instructions for allowing or disallowing the collection of data in the first scenario.

[0820] In some embodiments, the second information includes at least one of the following:

[0821] A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area;

[0822] The second time period is used to instruct the first terminal to perform data collection within the second time period;

[0823] The second data type is used to instruct the first terminal to collect data of the second data type;

[0824] The second scenario is used to instruct the first terminal to collect data under the second scenario.

[0825] In some embodiments, the processing module 521 is specifically used for:

[0826] Based on at least one of the first and third information, determine whether to accept or refuse to perform data collection;

[0827] The third piece of information refers to information related to data collection provided by the data requesting device.

[0828] In some embodiments, the receiving module 523 is further configured to:

[0829] Receive the second request from the first network element;

[0830] The second request includes at least one of the following:

[0831] The first information or the second information;

[0832] The third information is information related to data collection provided by the data collection device;

[0833] The address information of the first network element.

[0834] In some embodiments, the second request is transmitted via control plane messages or user plane messages.

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

[0836] A third region, wherein the third region is used to request a terminal within the third region to perform data collection;

[0837] The third time period is used to request the terminal to perform data collection during the third time period;

[0838] A third data type, wherein the third data type is used to request the terminal to collect data of the third data type;

[0839] The third scenario is used to request the terminal to collect data under the third scenario;

[0840] Instructions for collecting user-plane data;

[0841] The purpose of data collection.

[0842] In some embodiments, the sending module 522 is further configured to:

[0843] Send a response message for the second request to the first network element, the response message including at least one of the following:

[0844] Instructions for accepting or rejecting the second request;

[0845] The reason information indicating the reason for rejection includes at least one of the following:

[0846] The indication that the first terminal is not located in the third area;

[0847] The indication that the first terminal is not located in a portion of the third region;

[0848] The first terminal does not support instructions to perform data collection during the third time period;

[0849] The first terminal does not support instructions to perform data collection during a portion of the third time period;

[0850] The first terminal does not support instructions to collect data of the third data type;

[0851] The first terminal does not support instructions to collect data of some data types in the third data type;

[0852] The first terminal does not support instructions to collect data in the third scenario;

[0853] The first terminal does not support instructions to collect data in some scenarios of the third scenario.

[0854] See Figure 14 When the data acquisition device is a second network element or a component within a second network element, the data acquisition device 530 includes:

[0855] Processing module 531 is used to acquire first information, wherein the first information is information related to data collection provided by the first terminal;

[0856] The sending module 532 is used to send the first information to the first network element.

[0857] In some embodiments, the processing module 531 is specifically configured to perform at least one of the following:

[0858] Retrieve the first information stored locally;

[0859] Obtain the first information from the first terminal.

[0860] In some embodiments, before the processing module 531 obtains the first information stored locally, it is further configured to:

[0861] The first information is obtained from the first terminal and stored locally.

[0862] In some embodiments, the first information includes at least one of the following:

[0863] Information about one or more areas where data collection is permitted or not permitted;

[0864] Information on one or more time periods during which data collection is permitted or not permitted;

[0865] Information on one or more data types that allow or disallow data collection;

[0866] Information on one or more scenarios in which data collection is permitted or prohibited;

[0867] Information for the first area;

[0868] Instructions to allow or disallow terminals in the first area to perform data collection;

[0869] Information of the first data type;

[0870] Instructions to allow or disallow data collection of the first data type;

[0871] Information from the first time period;

[0872] Instructions to allow or disallow data collection during the first time period;

[0873] Information from the first scene;

[0874] Instructions for allowing or disallowing the collection of data in the first scenario.

[0875] See Figure 15 When the data acquisition device is a third network element or a component in a third network element, the data acquisition device 540 includes a processing module 541 and a transmitting module 542.

[0876] The processing module 541 is used to acquire the first information;

[0877] Alternatively, the sending module 542 may be used to perform at least one of the following:

[0878] Send the identification information of the terminals in the third area to the first network element;

[0879] Send information related to data collection provided by terminals in the third area to the first network element;

[0880] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0881] In some embodiments, the processing module 541 is specifically configured to perform at least one of the following:

[0882] Obtain the first information stored locally by the third network element;

[0883] Obtain the first information from the first terminal.

[0884] In some embodiments, before the processing module 541 obtains the first information stored locally by the third network element, it is further configured to:

[0885] The first information is obtained from the first terminal and stored locally.

[0886] In some embodiments, the first information includes at least one of the following:

[0887] Information about one or more areas where data collection is permitted or not permitted;

[0888] Information on one or more time periods during which data collection is permitted or not permitted;

[0889] Information on one or more data types that allow or disallow data collection;

[0890] Information on one or more scenarios in which data collection is permitted or prohibited;

[0891] Information for the first area;

[0892] Instructions to allow or disallow terminals in the first area to perform data collection;

[0893] Information of the first data type;

[0894] Instructions to allow or disallow data collection of the first data type;

[0895] Information from the first time period;

[0896] Instructions to allow or disallow data collection during the first time period;

[0897] Information from the first scene;

[0898] Instructions for allowing or disallowing the collection of data in the first scenario.

[0899] In some embodiments, the device 54 further includes a receiving module for:

[0900] Receive a fourth message, which includes at least one of the following:

[0901] The third region;

[0902] Instructions to request information related to data collection provided by terminals within the third area;

[0903] Instructions to request the identification information of terminals within the third area.

[0904] The apparatus provided in this application embodiment can achieve... Figures 3 to 11 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0905] like Figure 16As shown in the illustration, this application also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores programs or instructions that can run on the processor 601. For example, when the communication device 600 is a first terminal, the program or instructions executed by the processor 601 implement the various steps of the above-described data acquisition method embodiments and achieve the same technical effect. When the communication device 600 is a first network element, a second network element, or a third network element, the program or instructions executed by the processor 601 implement the various steps of the above-described data acquisition method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0906] This application embodiment also provides a first terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, etc. Figure 3 , Figures 7 to 11 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the first terminal-side method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this first terminal embodiment and achieve the same technical effect. The first terminal can be... Figure 13 The data acquisition device shown. Specifically, Figure 17 A schematic diagram of the hardware structure of a terminal 700 according to an embodiment of this application.

[0907] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

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

[0909] It should be understood that, in this embodiment, the input unit 704 may include a graphics processor 7041 and a microphone 7042. The graphics processor 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

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

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

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

[0913] Among them, the radio frequency unit 701 is used for

[0914] Processor 710 is used to perform at least one of the following:

[0915] Obtain first information;

[0916] Decide whether to accept or refuse data collection;

[0917] The second information is determined based on the first information;

[0918] Alternatively, the radio frequency unit 701 may be used to perform at least one of the following:

[0919] Send the first information to the first network element, the second network element, or the third network element;

[0920] Receive the second information from the first network element;

[0921] The first information is information related to data collection provided by the terminal 700.

[0922] In this embodiment, when the terminal 700 obtains the first information, since the first information is information related to data collection provided by the terminal 700, the data collection performed by the terminal 700 can be restricted through the first information, reducing the amount of data to be collected and thus reducing the power consumption of the terminal 700. When the terminal 700 sends the first information to the first network element, the second network element, or the third network element, the first network element can determine whether the terminal 700 performs data collection, reducing unnecessary collection triggered by the first network element, reducing the amount of data to be collected, and thus reducing the power consumption of the terminal 700. When the terminal 700 determines to accept or refuse to perform data collection, unnecessary collection triggered by the first network element can be reduced, reducing the amount of data to be collected, and thus reducing the power consumption of the terminal 700. When the terminal 700 determines the second information or receives the second information from the first network element, data collection can be performed based on the second information, reducing the amount of data to be collected and thus reducing the power consumption of the terminal 700.

[0923] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant descriptions of method embodiments 320, 410 to 450, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0924] This application embodiment 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 used to run programs or instructions to implement, for example... Figure 3 , Figures 5 to 11 The steps of any one of the method embodiments shown in the figures. This network-side device embodiment corresponds to the method embodiments of the first network element, second network element, or third network element described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0925] Specifically, embodiments of this application also provide a network-side device. For example... Figure 18As shown, the network-side device 800 includes: a processor 801, a network interface 802, and a memory 803. This network-side device can be... Figure 12 , Figure 14 or Figure 15 The data acquisition device shown is an example of a common public radio interface (CPRI). The network interface 802 is, for example, a CPRI.

[0926] In one implementation, the network-side device 800 is a first network element, wherein the processor 801 is used to acquire first information, the first information being information related to data collection provided by the first terminal;

[0927] The processor 801 is further configured to perform at least one of the following:

[0928] Based on the first information, it is determined that data collection will be performed on the first terminal;

[0929] Determine the second piece of information;

[0930] Alternatively, the network interface 802 may be used to perform at least one of the following:

[0931] Send the first information to the first terminal;

[0932] Send the second information to the first terminal.

[0933] In one implementation, the network-side device 800 is a second network element, the processor 801 is used to acquire first information, the first information being data collection-related information provided by the first terminal; and the network interface 802 is used to send the first information to the first network element.

[0934] In one implementation, the network-side device 800 is a third network element, and the processor 801 is used to acquire first information; or the network interface 802 is used to perform at least one of the following:

[0935] Send the identification information of the terminals in the third area to the first network element;

[0936] Send information related to data collection provided by terminals in the third area to the first network element;

[0937] Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

[0938] Furthermore, the network-side device 800 in this embodiment of the application also includes: a program or instructions stored in a memory 803 and executable on a processor 801, wherein the processor 801 calls the program or instructions in the memory 803 to execute. Figure 12 , Figure 14 or Figure 15 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

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

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

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

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

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

[0944] This application also provides a data acquisition system, including: a first terminal and at least one of the following: a first network element, a second network element, and a third network element. The first terminal can be used to perform the steps of the data acquisition method described above, and the first network element, the second network element, or the third network element can be used to perform the steps of the data acquisition method described above.

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

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

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

Claims

1. A data collection method, characterized in that, include: The first network element acquires first information, which is information related to data collection provided by the first terminal. The first network element performs at least one of the following: Send the first information to the first terminal; Based on the first information, it is determined that data collection will be performed on the first terminal; Determine the second piece of information; Send the second information to the first terminal.

2. The method according to claim 1, characterized in that, The first network element acquires first information, including at least one of the following: The first network element obtains the first information stored locally; The first network element obtains the first information from the second or third network element; The first network element obtains the first information from the first terminal.

3. The method according to claim 2, characterized in that, Before the first network element obtains the first information stored locally, the method further includes: The first network element obtains the first information from the first terminal and stores the first information locally.

4. The method according to any one of claims 1 to 3, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

5. The method according to any one of claims 1 to 4, characterized in that, The second information includes at least one of the following: A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area; The second time period is used to instruct the first terminal to perform data collection within the second time period; The second data type is used to instruct the first terminal to collect data of the second data type; The second scenario is used to instruct the first terminal to collect data under the second scenario.

6. The method according to any one of claims 1 to 4, characterized in that, The determination of the second information includes: The second information is determined based on at least one of the first information and the third information; The third piece of information refers to information related to data collection provided by the data requesting device.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The first network element receives the first request from the data requesting device; The first network element sends a second request to the first terminal; The first request includes at least one of the following: The third information is information related to data collection provided by the data collection device; Address information of the data requester's device; The second request includes at least one of the following: The first information or the second information; The third information; The address information of the first network element.

8. The method according to claim 7, characterized in that, The second request is transmitted via control plane messages or user plane messages.

9. The method according to any one of claims 6 to 8, characterized in that, The third information includes at least one of the following: A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located; The third time period is used to request the terminal to perform data collection during the third time period; A third data type, wherein the third data type is used to request the terminal to collect data of the third data type; The third scenario is used to request the terminal to collect data under the third scenario; Instructions for collecting user-plane data; The purpose of data collection.

10. The method according to claim 9, characterized in that, The method further includes: The first network element receives a response message for the second request from the first terminal, the response message including at least one of the following: Instructions for accepting or rejecting the second request; The reason information indicating the reason for rejection includes at least one of the following: The indication that the first terminal is not located in the third area; The indication that the first terminal is not located in a portion of the third region; The first terminal does not support instructions to perform data collection during the third time period; The first terminal does not support instructions to perform data collection during a portion of the third time period; The first terminal does not support instructions to collect data of the third data type; The first terminal does not support instructions to collect data of some data types in the third data type; The first terminal does not support instructions to collect data in the third scenario; The first terminal does not support instructions to collect data in some scenarios of the third scenario.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: The first network element sends fourth information to the third network element, the fourth information including at least one of the following: A third region, wherein the third region is used to request the terminal to perform data collection when the third region is located; Instructions to request information related to data collection provided by terminals within the third area; Instructions to request the identification information of terminals within the third area.

12. A data collection method, characterized in that, include: The first terminal performs at least one of the following: Obtain first information; Send the first information to the first network element, the second network element, or the third network element; Decide whether to accept or refuse to perform data collection; The second information is determined based on the first information or the second information is received from the first network element; The first information refers to the information related to data collection provided by the first terminal.

13. The method according to claim 12, characterized in that, The acquisition of the first information includes at least one of the following: Obtain the first information stored locally by the first terminal; The first information is obtained from the first network element.

14. The method according to claim 12 or 13, characterized in that, Before obtaining the first information stored locally by the first terminal, the method further includes: The first terminal stores the first information locally.

15. The method according to any one of claims 12 to 14, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

16. The method according to any one of claims 12 to 15, characterized in that, The second information includes at least one of the following: A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area; The second time period is used to instruct the first terminal to perform data collection within the second time period; The second data type is used to instruct the first terminal to collect data of the second data type; The second scenario is used to instruct the first terminal to collect data under the second scenario.

17. The method according to any one of claims 12 to 16, characterized in that, The process of determining whether to accept or reject data collection includes: Based on at least one of the first and third information, determine whether to accept or refuse to perform data collection; The third piece of information refers to information related to data collection provided by the data requesting device.

18. The method according to any one of claims 12 to 17, characterized in that, The method further includes: The first terminal receives the second request from the first network element; The second request includes at least one of the following: The first information or the second information; The third information is information related to data collection provided by the data collection device; The address information of the first network element.

19. The method according to claim 18, characterized in that, The second request is transmitted via control plane messages or user plane messages.

20. The method according to any one of claims 17 to 19, characterized in that, The third information includes at least one of the following: A third region, wherein the third region is used to request a terminal within the third region to perform data collection; The third time period is used to request the terminal to perform data collection during the third time period; A third data type, wherein the third data type is used to request the terminal to collect data of the third data type; The third scenario is used to request the terminal to collect data under the third scenario; Instructions for collecting user-plane data; The purpose of data collection.

21. The method according to claim 20, characterized in that, The method further includes: The first terminal sends a response message for the second request to the first network element, the response message including at least one of the following: Instructions for accepting or rejecting the second request; The reason information indicating the reason for rejection includes at least one of the following: The indication that the first terminal is not located in the third area; The indication that the first terminal is not located in a portion of the third region; The first terminal does not support instructions to perform data collection during the third time period; The first terminal does not support instructions to perform data collection during a portion of the third time period; The first terminal does not support instructions to collect data of the third data type; The first terminal does not support instructions to collect data of some data types in the third data type; The first terminal does not support instructions to collect data in the third scenario; The first terminal does not support instructions to collect data in some scenarios of the third scenario.

22. A data collection method, characterized in that, include: The second network element acquires the first information, which is information related to data collection provided by the first terminal. The second network element sends the first information to the first network element.

23. The method according to claim 22, characterized in that, The second network element acquires the first information, including at least one of the following: The second network element acquires the first information stored locally; The second network element obtains the first information from the first terminal.

24. The method according to claim 23, characterized in that, Before the second network element obtains the first information stored locally, the method further includes: The second network element obtains the first information from the first terminal and stores the first information locally.

25. The method according to any one of claims 22 to 24, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

26. A data collection method, characterized in that, include: The third network element performs at least one of the following: Obtain first information; Send the identification information of the terminals in the third area to the first network element; Send information related to data collection provided by terminals in the third area to the first network element; Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

27. The method according to claim 26, characterized in that, The acquisition of the first information includes at least one of the following: Obtain the first information stored locally by the third network element; Obtain the first information from the first terminal.

28. The method according to claim 26 or 27, characterized in that, Before obtaining the first information stored locally by the third network element, the method further includes: The first information is obtained from the first terminal and stored locally.

29. The method according to any one of claims 26 to 28, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

30. The method according to any one of claims 26 to 29, characterized in that, The method further includes: The third network element receives fourth information, which includes at least one of the following: The third region; Instructions to request information related to data collection provided by terminals within the third area; Instructions to request the identification information of terminals within the third area.

31. A data acquisition device, characterized in that, include: Processing module and sending module; The processing module is used to acquire first information, which is information related to data collection provided by the first terminal. The processing module is also configured to perform at least one of the following: Based on the first information, it is determined that data collection will be performed on the first terminal; Determine the second piece of information; Or the sending module may be used to perform at least one of the following: Send the first information to the first terminal; Send the second information to the first terminal.

32. The apparatus according to claim 31, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

33. The apparatus according to claim 31 or 32, characterized in that, The second information includes at least one of the following: A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area; The second time period is used to instruct the first terminal to perform data collection within the second time period; The second data type is used to instruct the first terminal to collect data of the second data type; The second scenario is used to instruct the first terminal to collect data under the second scenario.

34. A data acquisition device, characterized in that, include: Processing module, sending module, and receiving module; The processing module is used to perform at least one of the following: Obtain first information; Decide whether to accept or refuse to perform data collection; The second information is determined based on the first information; Alternatively, the sending module may be used to send first information to a first network element, a second network element, or a third network element; Alternatively, the receiving module may be used to receive second information from the first network element; The first information is information related to data collection provided by the first terminal.

35. The apparatus according to claim 34, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

36. The apparatus according to claim 34 or 35, characterized in that, The second information includes at least one of the following: A second area, the second area being used to instruct the first terminal to perform data collection when it is located within the second area; The second time period is used to instruct the first terminal to perform data collection within the second time period; The second data type is used to instruct the first terminal to collect data of the second data type; The second scenario is used to instruct the first terminal to collect data under the second scenario.

37. A data acquisition device, characterized in that, include: The processing module is used to acquire first information, which is information related to data collection provided by the first terminal; The sending module is used to send the first information to the first network element.

38. The apparatus according to claim 37, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

39. A data acquisition device, characterized in that, include: Processing unit and sending module; The processing module is used to acquire the first information; Or the sending module may be used to perform at least one of the following: Send the identification information of the terminals in the third area to the first network element; Send information related to data collection provided by terminals in the third area to the first network element; Wherein, the first information is information related to data collection provided by the first terminal, the terminal in the third area includes the first terminal, and the third area is used to request the terminal to perform data collection when it is in the third area.

40. The apparatus according to claim 39, characterized in that, The first information includes at least one of the following: Information about one or more areas where data collection is permitted or not permitted; Information on one or more time periods during which data collection is permitted or not permitted; Information on one or more data types that allow or disallow data collection; Information on one or more scenarios in which data collection is permitted or prohibited; Information for the first area; Instructions to allow or disallow terminals in the first area to perform data collection; Information of the first data type; Instructions to allow or disallow data collection of the first data type; Information from the first time period; Instructions to allow or disallow data collection during the first time period; Information from the first scene; Instructions for allowing or disallowing the collection of data in the first scenario.

41. A network-side device, characterized in that, The device includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the data acquisition method as claimed in any one of claims 1 to 11, the steps of the data acquisition method as claimed in any one of claims 22 to 25, or the steps of the data acquisition method as claimed in any one of claims 26 to 30.

42. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the data acquisition method as described in any one of claims 12 to 21.

43. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the data acquisition method as claimed in any one of claims 1 to 11, any one of claims 12 to 21, any one of claims 22 to 25, or any one of claims 26 to 30.

Images