Data collection method and apparatus, and readable storage medium

Abstract

A data collection method and apparatus, and a readable storage medium. The method comprises: acquiring first information, the first information comprising information related to terminal data collection, reporting and / or disclosure; on the basis of the first information, determining terminal data; and sending the terminal data to a first functional entity. The information related to terminal data collection, reporting and / or disclosure comprises one or more of the following information: subscription or authorization information related to terminal data collection, reporting and / or disclosure; policy information related to terminal data collection, reporting and / or disclosure; configuration information related to terminal data collection, reporting and / or disclosure; and request information related to terminal data collection, reporting and / or disclosure.

Description

A data acquisition method, apparatus and readable storage medium

[0001] This disclosure claims priority to Chinese Patent Application No. 202411582401.2, filed with the Chinese Patent Office on November 7, 2024, entitled “A Data Acquisition Method, Apparatus and Readable Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a data acquisition method, apparatus and readable storage medium. Background Technology

[0003] The 5th Generation Mobile Communication Technology System (5GS) incorporates Artificial Intelligence (AI) and Machine Learning (ML) technologies to optimize the functionality and performance of the communication system. Currently, the standard only supports data collection and reporting at the terminal application layer.

[0004] Terminal data (e.g., communication and measurement data of terminals in the system) is data in the communication system and is closely related to network architecture, functions and performance. However, the application layer data collection, reporting and / or opening in related technologies cannot realize network control over the collection, reporting and / or opening of terminal data. Summary of the Invention

[0005] This disclosure provides a data acquisition method, apparatus, and readable storage medium to achieve control over the acquisition, reporting, and / or access of terminal data.

[0006] In a first aspect, embodiments of this disclosure provide a data acquisition method applied to a terminal, comprising:

[0007] Obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0008] Based on the first information, determine the terminal data;

[0009] Send the terminal data to the first functional entity;

[0010] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0011] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0012] Terminal data collection, reporting, and / or sharing of related policy information;

[0013] Terminal data collection, reporting, and / or sharing of related configuration information;

[0014] Terminal data collection, reporting, and / or open request information.

[0015] Secondly, embodiments of this disclosure provide a data acquisition method applied to a second functional entity, comprising:

[0016] Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data;

[0017] Send the first information to the terminal;

[0018] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0019] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0020] Terminal data collection, reporting, and / or sharing of related policy information;

[0021] Terminal data collection, reporting, and / or sharing of related configuration information;

[0022] Terminal data collection, reporting, and / or open request information.

[0023] Thirdly, according to an embodiment of this disclosure, a data acquisition method is applied to a first functional entity, including:

[0024] Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0025] Receive terminal data;

[0026] Based on the first information, the terminal data is sent to the third functional entity;

[0027] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0028] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0029] Terminal data collection, reporting, and / or sharing of related policy information;

[0030] Terminal data collection, reporting, and / or sharing of related configuration information;

[0031] Terminal data collection, reporting, and / or open request information.

[0032] Fourthly, embodiments of this disclosure provide a data acquisition method applied to an access network device, comprising:

[0033] Receive terminal data collection, reporting, and / or open related configuration information from the first or second functional entity;

[0034] The terminal sends configuration information related to data collection, reporting, and / or opening to the terminal, which is used by the terminal to collect data.

[0035] Fifthly, embodiments of this disclosure provide a data acquisition device applied to a terminal, comprising: a memory, a transceiver, and a processor.

[0036] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0037] Obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0038] Based on the first information, determine the terminal data;

[0039] Send the terminal data to the first functional entity;

[0040] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0041] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0042] Terminal data collection, reporting, and / or sharing of related policy information;

[0043] Terminal data collection, reporting, and / or sharing of related configuration information;

[0044] Terminal data collection, reporting, and / or open request information.

[0045] Sixthly, embodiments of this disclosure provide a data acquisition device applied to a second functional entity, including: a memory, a transceiver, and a processor.

[0046] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0047] Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data;

[0048] Send the first information to the terminal;

[0049] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0050] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0051] Terminal data collection, reporting, and / or sharing of related policy information;

[0052] Terminal data collection, reporting, and / or sharing of related configuration information;

[0053] Terminal data collection, reporting, and / or open request information.

[0054] In a seventh aspect, embodiments of this disclosure provide a data acquisition device applied to a first functional entity, including: a memory, a transceiver, and a processor.

[0055] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0056] Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0057] Receive terminal data;

[0058] Based on the first information, the terminal data is sent to the third functional entity;

[0059] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0060] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0061] Terminal data collection, reporting, and / or sharing of related policy information;

[0062] Terminal data collection, reporting, and / or sharing of related configuration information;

[0063] Terminal data collection, reporting, and / or open request information.

[0064] Eighthly, embodiments of this disclosure provide a data acquisition device applied to access network equipment, comprising: a memory, a transceiver, and a processor.

[0065] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0066] Receive terminal data collection, reporting, and / or open related configuration information from the first or second functional entity;

[0067] The terminal sends configuration information related to data collection, reporting, and / or opening to the terminal, which is used by the terminal to collect data.

[0068] Ninthly, embodiments of this disclosure provide a data acquisition device applied to a terminal, comprising:

[0069] The first acquisition unit is used to acquire first information, which includes terminal data collection, reporting and / or open related information.

[0070] The first determining unit is configured to determine terminal data based on the first information;

[0071] The first sending unit is used to send the terminal data to the first functional entity;

[0072] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0073] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0074] Terminal data collection, reporting, and / or sharing of related policy information;

[0075] Terminal data collection, reporting, and / or sharing of related configuration information;

[0076] Terminal data collection, reporting, and / or open request information.

[0077] In a tenth aspect, embodiments of this disclosure provide a data acquisition device applied to a second functional entity, comprising:

[0078] A first processing unit is configured to determine or acquire first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data;

[0079] The first sending unit is used to send the first information to the terminal;

[0080] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0081] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0082] Terminal data collection, reporting, and / or sharing of related policy information;

[0083] Terminal data collection, reporting, and / or sharing of related configuration information;

[0084] Terminal data collection, reporting, and / or open request information.

[0085] Eleventhly, embodiments of this disclosure provide a data acquisition device applied to a first functional entity, comprising:

[0086] The first processing unit is configured to determine or acquire first information, the first information including terminal data collection, reporting and / or open related information;

[0087] The first receiving unit is used to receive terminal data;

[0088] The first sending unit is configured to send the terminal data to the third functional entity based on the first information;

[0089] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0090] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0091] Terminal data collection, reporting, and / or sharing of related policy information;

[0092] Terminal data collection, reporting, and / or sharing of related configuration information;

[0093] Terminal data collection, reporting, and / or open request information.

[0094] In a twelfth aspect, embodiments of this disclosure provide a data acquisition device applied to an access network device, comprising:

[0095] The first sending unit is used to send configuration information related to terminal data collection, reporting, and / or opening to the terminal. The configuration information related to terminal data collection, reporting, and / or opening is used by the terminal to collect data. The configuration information related to terminal data collection, reporting, and / or opening includes configuration information related to terminal data collection, reporting, and / or opening received from the first functional entity or the second functional entity.

[0096] In a thirteenth aspect, embodiments of this disclosure also provide a processor-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the data acquisition method described above.

[0097] In this embodiment of the disclosure, the terminal can determine terminal data based on the acquired first information and send the terminal data to the first functional entity. Since the first information includes information related to terminal data collection, reporting, and / or access, the solution of this embodiment of the disclosure can realize the control over the collection, reporting, and / or access of terminal data. Attached Figure Description

[0098] Figure 1 is a flowchart of one of the data acquisition methods provided in the embodiments of this disclosure;

[0099] Figure 2 is a second flowchart of the data acquisition method provided in the embodiments of this disclosure;

[0100] Figure 3 is a flowchart of the data acquisition method provided in the embodiment of this disclosure;

[0101] Figure 4 is a flowchart of the data acquisition method provided in the embodiments of this disclosure;

[0102] Figure 5 is a flowchart of the data acquisition method provided in the embodiments of this disclosure;

[0103] Figure 6 is a flowchart of the data acquisition method provided in the embodiments of this disclosure;

[0104] Figure 7 is a flowchart of the data acquisition method provided in the embodiments of this disclosure;

[0105] Figure 8 is a flowchart of the data acquisition method provided in the embodiment of this disclosure;

[0106] Figure 9 is a structural diagram of a data acquisition device provided in an embodiment of this disclosure;

[0107] Figure 10 is a second structural diagram of the data acquisition device provided in the embodiments of this disclosure;

[0108] Figure 11 is a third structural diagram of the data acquisition device provided in an embodiment of this disclosure;

[0109] Figure 12 is a fourth structural diagram of the data acquisition device provided in the embodiments of this disclosure;

[0110] Figure 13 is the fifth structural diagram of the data acquisition device provided in the embodiments of this disclosure;

[0111] Figure 14 is a structural diagram of the data acquisition device provided in the embodiment of this disclosure;

[0112] Figure 15 is the seventh structural diagram of the data acquisition device provided in the embodiments of this disclosure;

[0113] Figure 16 is the eighth structural diagram of the data acquisition device provided in the embodiments of this disclosure. Detailed Implementation

[0114] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0115] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0116] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0117] This disclosure provides a data acquisition method and apparatus for controlling the acquisition, reporting, and / or access of terminal data.

[0118] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0119] Referring to Figure 1, which is a flowchart of a data acquisition method provided in an embodiment of this disclosure, applied to a terminal, as shown in Figure 1, it includes the following steps:

[0120] Step 101: Obtain first information, which includes terminal data collection, reporting, and / or open related information.

[0121] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0122] 1. Terminal data collection, reporting, and / or sharing of related contractual or authorized information.

[0123] This information includes one or more of the following, or updates to one or more of the following:

[0124] The types of terminal data (e.g., sensing data, location data, wireless access data, etc.) or uses (e.g., for data analysis, model training, or inference, etc.) that are allowed to be collected, reported, and / or made public;

[0125] Areas where terminal data collection, reporting, and / or access are permitted (e.g., one or more cells or tracking areas, specific geographic areas);

[0126] Allows the collection, reporting, and / or sharing of time information for terminal data, such as a specific time period;

[0127] Application or business information that allows or authorizes the use of terminal data, such as application or business identifiers;

[0128] Information that allows or authorizes the use of machine learning models or inferences from terminal data, wherein the machine learning model can be an AI or ML model, and the information may include the type, identifier, applicable time, applicable region, accuracy, latency, etc. of the model or inference;

[0129] Information about the recipient or user of the terminal data that is permitted or authorized, such as the name, identifier, address, etc. of the recipient or user. The recipient or user may be a Model Training Function (MTF), an Inference Function (IF), etc.

[0130] 2. Terminal data collection, reporting, and / or sharing of related policy information.

[0131] 3. Terminal data collection, reporting, and / or access to related configuration information.

[0132] 4. Terminal data collection, reporting, and / or access request information.

[0133] The above 2, 3, and 4 may include one or more of the following information:

[0134] The data types (e.g., sensing data, location data, wireless access data, etc.) or uses (e.g., for data analysis, model training, or inference, etc.) of terminal data collection, reporting, and / or open access;

[0135] Terminal data collection, reporting, and / or access to regional and / or time information;

[0136] Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information (such as triggering events);

[0137] Access network information, wireless access technology information, and / or frequency-related information corresponding to the terminal data collected, reported, and / or made public;

[0138] Session information used to collect, report, and / or open the terminal data, such as the slice, data network, application, or service information to which the session belongs;

[0139] Information on machine learning models or inferences using terminal data, wherein the machine learning model can be an AI or ML model, and the information may include the type, identifier, applicable time, applicable region, accuracy, latency, etc. of the model or inference;

[0140] Application or business information that uses terminal data, such as application or business identifiers;

[0141] Terminal data collection, reporting, and / or access to first Quality of Service (QoS) information, such as one or more of the following: transmission rate, QoS category or identifier (e.g., 5G QoS Identifier (5QI)), and QoS characteristic parameters (e.g., data transmission latency, error rate).

[0142] In this step, the terminal can receive the first information from the second functional entity. The second functional entity may be, for example, a Data Collection Exposure Function (DCEF), a Data Collection Management Function (DCMF), a network function for registration management such as an Access and Mobility Management Function (AMF), a network function for session management such as a Session Management Function (SMF), or a network function for policy management such as a Policy Control Function (PCF).

[0143] For example, the terminal may receive a registration acceptance message sent by the AMF, which includes the first information; the terminal may receive a session establishment or modification acceptance message sent by the SMF, which includes the first information; or, the terminal may receive a terminal data acquisition capability request, response, or confirmation message or a terminal data acquisition, reporting, and / or opening request, response, or confirmation message sent by the DCMF, DCEF, or PCF, which includes the first information.

[0144] In this embodiment of the disclosure, the terminal may also send second information to the second functional entity. The second information is used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response. The second information includes one or more of the following:

[0145] The data types (e.g., sensing data, location data, wireless access data, etc.) or uses (e.g., for data analysis, model training, or inference, etc.) of terminal data collection, reporting, and / or open access;

[0146] Terminal data collection, reporting, and / or access to regional and / or time information;

[0147] Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information (e.g., triggering events);

[0148] Information on machine learning models or inferences using terminal data, wherein the machine learning model can be an AI or ML model, and the information may include the type, identifier, applicable time, applicable region, accuracy, latency, etc. of the model or inference;

[0149] Application or business information that uses terminal data, such as application or business identifiers;

[0150] Terminal types, such as one or more of the following: mobile broadband communication terminals, Internet of Things devices, drones, vehicles, etc.

[0151] Secondary QoS information acquired, reported, and / or made available by the terminal, such as one or more of the following: transmission rate, QoS category or identifier (e.g., 5QI), and QoS characteristic parameters (e.g., data transmission delay, error rate).

[0152] The terminal may also determine the second QoS information for terminal data collection, reporting, and / or access based on one or more of the following information:

[0153] The types or uses of data collected, reported, and / or made public by the terminal, such as sensing data, positioning data, wireless access data, etc.

[0154] Terminal data acquisition, reporting, and / or access to information such as latency, period, and / or triggering conditions (e.g., triggering events);

[0155] Information on machine learning models or inferences using terminal data, wherein the machine learning model can be an AI or ML model, and the information may include the type, identifier, applicable time, applicable region, accuracy, latency, etc. of the model or inference;

[0156] Application or business information that uses terminal data, such as application or business identifiers;

[0157] Resource usage of the terminal or network;

[0158] Energy consumption status of the terminal or network.

[0159] In this step, for example, the terminal may send a registration request message to the AMF, which includes the second information; the terminal may send a session establishment or modification request message to the SMF, which includes the second information; the terminal may send a policy request message to the PCF, which includes the second information; the terminal may send a terminal data acquisition capability request or response message or a terminal data acquisition (and / or reporting) request or response message to the DCMF or DCEF, which includes the second information.

[0160] The second information can be determined based on the first information. That is, the terminal can determine the second information based on the first information. For example, the terminal can determine the second information based on the first information, combined with its own strategies and capabilities.

[0161] In this embodiment of the disclosure, if the first information includes policy information related to terminal data collection, reporting, and / or access, the terminal may also send third information to the second functional entity. The third information is used to indicate the terminal's accepted policy information or configuration information related to terminal data collection, reporting, and / or access. The meaning of this configuration information can be found in the description of the foregoing embodiments.

[0162] Step 102: Determine the terminal data based on the first information.

[0163] In this step, the terminal can collect corresponding terminal data based on the first information.

[0164] Step 103: Send the terminal data to the first functional entity.

[0165] In this step, the terminal can send the terminal data to the first functional entity via control plane signaling or user plane connection. The first functional entity may be, for example, a DCEF or a Data Exposure Function (DEF).

[0166] If the connection is via the user plane, the terminal can receive terminal data collection, reporting, and / or open user plane information sent by the first functional entity, and establish a user plane connection with the first functional entity based on the user plane information. The user plane information includes one or more of the following:

[0167] The user plane address of the first functional entity;

[0168] Data transmission tunnel identifier, connection identifier, or association identifier;

[0169] QoS information that is permitted or authorized for terminal data transmission.

[0170] During the data acquisition process at the terminal, the terminal data is a data packet (or Protocol Data Unit (PDU)) encapsulated according to the control plane data acquisition protocol or the user plane data acquisition protocol.

[0171] If the terminal data is sent via control plane signaling, there is no limitation on the form of control plane signaling used.

[0172] In this embodiment of the disclosure, the terminal can determine terminal data based on the acquired first information and send the terminal data to the first functional entity. Since the first information includes information related to terminal data collection, reporting, and / or access, the solution of this embodiment of the disclosure can realize the control over the collection, reporting, and / or access of terminal data.

[0173] Based on the above embodiments, the terminal can also receive terminal data acquisition error indication information sent by the first functional entity, and send updated terminal data to the first functional entity according to the terminal data acquisition error indication information. The terminal data acquisition error indication information is used to indicate information about erroneous data packets and / or erroneous fields present in the sent terminal data. Based on this indication information, the terminal can correct or delete erroneous data packets or erroneous fields, thereby obtaining updated terminal data.

[0174] Referring to Figure 2, which is a flowchart of a data acquisition method provided in an embodiment of this disclosure, applied to a second functional entity, as shown in Figure 2, the method includes the following steps:

[0175] Step 201: Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data.

[0176] The explanation of the first information can be found in the description of the foregoing embodiments. The second functional entity can determine the first information itself or obtain it from other functional entities.

[0177] For example, regarding the collection, reporting, and / or sharing of terminal data related to contracts or authorizations, the second functional entity may provide network functions (such as Unified Data Management (UDM) or Unified Database Management (UDM) functions that manage terminal-related data. The UDR (Unified Repository) acquires terminal-related data stored in the network. This terminal data may include information related to terminal data collection, reporting, and / or sharing, such as: the type or purpose of data (permitted for collection, reporting, and / or sharing by the terminal) (e.g., sensing data, location data, wireless access data); the region and / or time period (permitted for collection, reporting, and / or sharing); user privacy settings regarding data collection and / or reporting; information on terminal data that is permitted or authorized for sharing (e.g., type or purpose, region, time period, collection frequency, accuracy, latency); terminal data recipient information (e.g., information on third-party servers used for model training or inference (identifier, address, or other information, referred to here as MTF and / or IF for terminal data recipients); application / service information using the terminal data (e.g., application / service identifier); and information on AI / ML models or inference models using the terminal data (e.g., model or inference type / identifier). The second network function entity can determine or acquire the contract or authorization information related to the terminal data collection, reporting, and / or sharing based on the information obtained from the UDM or UDR.

[0178] The second functional entity can obtain policy information related to terminal data collection, reporting, and / or access from the PCF.

[0179] The second functional entity can obtain configuration information related to terminal data collection, reporting, and / or access from itself.

[0180] For terminal data collection, reporting, and / or open request information, the second functional entity can obtain it from the third functional entity (such as MTF or IF).

[0181] Step 202: Send the first information to the terminal.

[0182] In this embodiment of the disclosure, the second functional entity may also receive second information sent by the terminal, the second information being used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response; or, it may receive fourth information sent by the third functional entity, the fourth information being used to indicate a request to collect, report, and / or open the terminal's data, and determine or obtain the first information based on the second information or the fourth information. The third functional entity may, for example, be a Model Training Function (MTF), an Inference Function (IF), etc.

[0183] The second information or the fourth information includes one or more of the following:

[0184] The types of data or uses of data collected, reported, and / or made public at the terminal;

[0185] Terminal data collection, reporting, and / or access to regional and / or time information;

[0186] Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information;

[0187] Information from machine learning models or inferences using terminal data;

[0188] Application or business information that uses terminal data;

[0189] Terminal type;

[0190] Terminal data collection, reporting, and / or access to secondary QoS information.

[0191] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0192] In some embodiments, the second network function entity may also receive third information sent by the terminal, the third information being used to indicate policy information or configuration information related to terminal data collection, reporting, and / or access that the terminal has accepted. An explanation of the above information can be found in the description of the foregoing method embodiments.

[0193] In this embodiment of the disclosure, the terminal can determine terminal data based on the acquired first information and send the terminal data to the first functional entity. Since the first information includes information related to terminal data collection, reporting, and / or access, the solution of this embodiment of the disclosure can realize the control over the collection, reporting, and / or access of terminal data.

[0194] Referring to Figure 3, which is a flowchart of a data acquisition method provided in an embodiment of this disclosure, applied to a first functional entity, as shown in Figure 3, the method includes the following steps:

[0195] Step 301: Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information.

[0196] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0197] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0198] Terminal data collection, reporting, and / or sharing of related policy information;

[0199] Terminal data collection, reporting, and / or sharing of related configuration information;

[0200] Terminal data collection, reporting, and / or open request information.

[0201] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0202] In this step, the first functional entity may obtain terminal-related data stored in the network from the network function (e.g., UDM or UDR) that manages terminal-related data. This terminal data may include information related to terminal data collection, reporting, and / or disclosure, such as: the type or purpose of data (e.g., sensing data, location data, wireless access data) that the terminal is allowed to collect, report, and / or disclose; the region and / or time period of the data that the terminal is allowed to collect, report, and / or disclose; user privacy settings for data collection and / or reporting; information on terminal data that is allowed or authorized to be disclosed (e.g., type or purpose, region, time period, collection frequency or period, accuracy, latency); terminal data recipient information (e.g., information on third-party servers used for model training or inference (identifier, address, or other information, referred to here as MTF and / or IF for terminal data recipients); application / service information using the terminal data (e.g., application / service identifier); and information on AI / ML models or inference using the terminal data (e.g., model or inference type / identifier). The first network functional entity may determine or obtain this first information based on the information obtained from the UDM or UDR.

[0203] Step 302: Receive terminal data.

[0204] In this step, the first network functional entity receives the terminal data via control plane signaling or user plane connection. The terminal data is used for machine learning model training or inference; for example, it can be used by the third or second network functional entity for machine learning model training or inference.

[0205] If a user plane connection is used, the first network function entity determines the user plane information for terminal data collection, reporting, and / or access, and establishes the user plane connection based on the user plane information to receive terminal data. For example, the first network function entity may determine whether to use control plane signaling or a user plane connection to receive terminal data based on factors such as terminal data collection type, data collection QoS requirements, data volume, terminal type (e.g., mobile broadband communication terminal, IoT device, drone, vehicle), and network status (e.g., resource usage). The interpretation of this user plane information can be found in the description of the foregoing embodiments.

[0206] Step 303: Based on the first information, send the terminal data to the third functional entity.

[0207] The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol. Here, the first functional entity can check the received terminal data to determine whether it conforms to the requirements of the first information. For example, it can determine whether the reported data type and format of the terminal data conform to the requirements of the first information. If it is determined that the terminal data does not conform to the requirements of the first information, the first functional entity sends a terminal data acquisition error indication message to the terminal and receives updated terminal data from the terminal.

[0208] In this embodiment of the disclosure, the terminal can determine terminal data based on the acquired first information and send the terminal data to the first functional entity. Since the first information includes information related to terminal data collection, reporting, and / or access, the solution of this embodiment of the disclosure can realize the control over the collection, reporting, and / or access of terminal data.

[0209] Referring to Figure 4, which is a flowchart of a data acquisition method provided in an embodiment of this disclosure, applied to an access network device, as shown in Figure 4, the method includes the following steps:

[0210] Step 401: Send configuration information related to terminal data collection, reporting and / or opening to the terminal. The configuration information related to terminal data collection, reporting and / or opening is used to obtain terminal data.

[0211] Step 402: Send the configuration information related to terminal data collection, reporting, and / or opening to the first functional entity or the second functional entity.

[0212] The explanation of the above information can be found in the foregoing method embodiments. The configuration information related to terminal data collection, reporting, and / or opening may include configuration information related to terminal data collection, reporting, and / or opening received by the access network device from the first functional entity or the second functional entity, and / or the configuration information of the access network device for terminal data collection, reporting, and / or opening.

[0213] The configuration information of the access network device for terminal data collection, reporting and / or opening can also refer to the configuration information related to terminal data collection, reporting and / or opening.

[0214] In this embodiment of the disclosure, the terminal can determine terminal data based on the acquired first information and send the terminal data to the first functional entity. Since the first information includes information related to terminal data collection, reporting, and / or access, the solution of this embodiment of the disclosure can realize the control over the collection, reporting, and / or access of terminal data.

[0215] The implementation process of the embodiments of this disclosure will be described in detail below with reference to different examples.

[0216] In the embodiment shown in Figure 5, DCMF (or enhanced AMF, SMF, or PCF) and DEF are introduced to authorize terminal data collection, reporting, and / or access, and to establish a user plane connection for terminal data reporting. The terminal negotiates data collection or reporting capabilities and policies with DCMF (or enhanced AMF, SMF, or PCF). This process may include:

[0217] Step 501: The terminal sends terminal data acquisition and / or reporting capability information or data reporting requests (corresponding to the second information) to the DCEF (AMF, SMF, or PCF), including one or more of the following:

[0218] The terminal supports the following data collection types or purposes, data formats, accuracy, periods, triggering conditions (such as triggering events), latency, information on AI / ML models or inferences using the terminal data (such as the type, identifier, applicable time, applicable area, accuracy, and latency of the AI / ML model or inference), terminal type (such as mobile broadband communication terminal, IoT device, drone, vehicle), application or service information using the terminal data, terminal data collection, reporting, and / or open second QoS information (such as transmission rate, QoS category / identifier (such as 5QI), QoS characteristic parameters (such as data transmission latency and error rate)).

[0219] Specifically, the data collection type or purpose may include one or more of the following: access layer data and non-access layer data collected by the terminal, such as: wireless interface measurement data (e.g., received signal power, latency, available access technology information, cell (serving cell, neighboring cell) information, access point information), performance data (e.g., data transmission latency, transmission rate and other QoS-related information), and may also include perception data (e.g., communication context information, including communication environment information), location information, information of nearby terminals, etc.

[0220] The terminal can dynamically adjust its data collection and / or reporting capabilities based on local or network AI strategies, resource usage, energy consumption status, sensing capabilities, application / service information, etc., and update these capabilities to the network.

[0221] Specifically, the terminal can determine the second QoS information of the transmitted terminal data based on one or more of the following: the type or purpose of the terminal data collection, reporting, and / or disclosure; the latency, periodicity, and / or triggering conditions of the terminal data collection, reporting, and / or disclosure; information about machine learning models or inference using the terminal data; application or service information using the terminal data; the resource usage of the terminal or network; and the energy consumption status of the terminal or network. For example, based on the AI / ML model or inference type / identifier, the terminal determines the QoS requirements of model training or inference for data collection, such as data volume, latency, and accuracy requirements, thereby determining the second QoS information of the transmitted terminal data.

[0222] Specifically, the terminal can send the aforementioned terminal data collection and / or reporting capability information or data reporting or access requests in the following ways:

[0223] The terminal can include terminal data acquisition and / or reporting capability information in the registration request message and send it to the network function that performs registration management, such as the AMF; or,

[0224] The terminal may include terminal data acquisition and / or reporting capability information in the session establishment or modification request message and send it to the SMF; or,

[0225] The terminal can include terminal data collection and / or reporting capability information in the policy request message and send it to the PCF; or,

[0226] Terminals can carry terminal data acquisition and / or reporting capability information in terminal data acquisition capability request or response messages, or terminal data acquisition and / or reporting request or response messages, and send them to network functions that manage data acquisition and / or reporting, such as DCMF.

[0227] The terminal data acquisition and / or reporting request or response message may carry a second QoS information requesting the transmission of the acquired terminal data. For example, the terminal may determine the QoS information of the acquired terminal data based on information from AI / ML models or inferences that use the terminal data. Specifically, the terminal determines the QoS requirements for data acquisition during model training or inference, such as data volume, latency, and accuracy, based on the AI / ML model or inference type / identifier, thereby determining the QoS information of the acquired terminal data.

[0228] Step 502: After receiving the terminal data collection and / or reporting capability information, the DCEF (AMF, SMF, or PCF) requests contracted data, obtains relevant contracted information for terminal data collection, and then determines the permitted or authorized terminal data collection and / or reporting information. Specifically:

[0229] AMF, SMF, PCF, or DCMF obtains terminal-related data stored in the network from network functions that manage terminal-related data (such as UDM or UDR). This terminal-related data includes information related to terminal data collection and / or reporting (which may be included in data sets such as subscription data, application function-provided data, or policy data, or may be an independent data collection and / or reporting data set), such as: the type or purpose of data (e.g., sensing data, location data, radio access data) that (allows) the terminal to collect and / or report; the area and / or time period of data (that (allows) the terminal to collect and / or report; and user privacy settings for data collection and / or reporting.

[0230] Based on terminal-related data stored in the network, AMF, SMF, PCF, or DCMF determine the permitted or authorized terminal data collection and / or reporting capabilities, i.e., the contract or authorization information related to terminal data collection and / or reporting, such as: the type or purpose of the data that the terminal is allowed to collect and / or report (e.g., sensing data, location data, wireless access data), the area and time information of the data that the terminal is allowed to collect and / or report, etc.

[0231] Step 503: AMF, SMF, PCF, or DCMF sends terminal data collection and / or reporting capability confirmation information to the terminal, which carries the terminal data collection and / or reporting capability information confirmed in step 502 (allowing or authorizing), i.e., the contract or authorization information related to terminal data collection and / or reporting.

[0232] Specifically, the "confirmed (permitted or authorized) terminal data collection and / or reporting capability information" here may include updates to previously confirmed (permitted or authorized) terminal data collection and / or reporting capability information.

[0233] AMF may include confirmation of terminal data collection and / or reporting capabilities in the registration acceptance message; or,

[0234] SMF can include confirmation of terminal data acquisition (and / or reporting capability information) in the session establishment or modification of the received message; or,

[0235] PCF can include confirmation of terminal data collection and / or reporting capabilities in the policy request response message or policy command message; or,

[0236] DCMF can carry confirmed terminal data acquisition and / or reporting capability information in the terminal data acquisition capability response or confirmation message, or the terminal data acquisition and / or reporting response or confirmation message.

[0237] Step 504: If step 503 carries updated terminal data acquisition and / or reporting capability information, the terminal can send terminal data acquisition and / or reporting capability update confirmation information to AMF, SMF, PCF or DCMF.

[0238] Step 505: In some embodiments, the AMF, SMF, PCF, or DCMF sends terminal data collection and / or reporting strategy (or configuration) information to the terminal.

[0239] Specifically, AMF, SMF, PCF, or DCMF can provide this policy (or configuration), which may include the following information:

[0240] Scope and requirements for terminal data collection and / or reporting: the type or purpose of the data collected and / or reported by the terminal (e.g., sensing data, positioning data, wireless access data, applicable applications / services), region, time information, data format, accuracy, latency, period, triggering conditions (triggering events), etc.

[0241] Transmission information of data collected and / or reported by the terminal, such as: session information of the terminal data being collected and / or reported (e.g., the slice to which the session belongs, data network, application / service information), access network information, wireless access technology information, frequency-related information, etc.

[0242] AMF, SMF, PCF, or DCMF can determine the policy (or configuration) based on the following information: terminal data collection and / or reporting of relevant network-side data (see step 502, such as subscription data), user privacy settings (see step 502), terminal type (such as mobile broadband communication terminal, IoT device, drone, vehicle), network status (such as resource usage), operator policies, service level agreements (SLAs) between operators and third parties, etc.

[0243] Step 506: In some embodiments, the terminal sends terminal data collection and / or reporting policy (or configuration) confirmation information (corresponding to the third information) to the AMF, SMF, PCF, or DCMF. This information may include the data collection and / or reporting policy accepted by the terminal, such as data collection accuracy, latency, period, triggering conditions ( / triggering events), access technology, etc. Specifically, the terminal may send terminal data collection and / or reporting policy confirmation information to the AMF, SMF, PCF, or DCMF.

[0244] Step 507: The AMF, SMF, PCF, or DCMF determines whether to use the Control Plane (CP) or the User Plane (UP) (here and below, the User Plane also includes dedicated transmission channels for transmitting AI-related data, or the data plane) for data collection and / or reporting. For example, the AMF, SMF, PCF, or DCMF determines whether to use the Control Plane or the User Plane based on factors such as the terminal data collection type, data collection QoS requirements, data volume, terminal type (e.g., mobile broadband communication terminal, IoT device, drone, vehicle), and network status (e.g., resource usage).

[0245] Step 508: If AMF, SMF, PCF, or DCMF determines that the user plane is used for terminal data collection and / or reporting, then AMF, SMF, PCF, or DCMF selects DEF and requests user plane information for terminal data collection and / or reporting from DEF. The request message carries the authorized terminal data collection type, the QoS information of the requested terminal data transmission, etc.

[0246] Step 509: DEF requests subscription data, obtains the relevant subscription information for terminal data access, and then determines the allowed or authorized terminal data access information, and accordingly determines the relevant parameters for transmitting terminal data, such as the QoS of authorized terminal data transmission. Specifically:

[0247] DEF obtains terminal data access information from network functions (such as UDM or UDR) that manage terminal-related data in the network. This information may include: terminal data information that is allowed or authorized to be accessed (e.g., type or purpose, region, time period, collection frequency, accuracy, latency), terminal data recipient information (e.g., information about third-party servers used for model training or inference (identifier, address, or other information, referred to here as MTF and / or IF for terminal data recipient), application / service information using terminal data (e.g., application / service identifier), and information about AI / ML models or inference using terminal data (e.g., model or inference type / identifier), etc.

[0248] DEF determines the permitted or authorized terminal data opening information based on the terminal data opening-related data stored in the network, including: permitted / authorized terminal data opening information, permitted / authorized terminal data recipient information, permitted / authorized application / service information for using terminal data, permitted / authorized AI / ML model or inference information for using terminal data, etc.

[0249] Step 510: DEF provides user plane information such as DEF address, data transmission tunnel identifier, connection identifier or association identifier, and QoS of authorized terminal data transmission to AMF, SMF, PCF or DCMF.

[0250] Specifically, DEF can determine the QoS information for authorized terminal data transmission based on information from AI / ML models or inference that use terminal data. In particular, DCEF determines the QoS requirements for data collection during model training or inference, such as data volume, latency, and accuracy, based on the AI / ML model or inference type / identifier, thereby determining the QoS information for authorized terminal data transmission.

[0251] Step 511: The AMF, SMF, PCF, or DCMF sends the user plane information collected and / or reported by the terminal to the terminal. Specifically,

[0252] AMF can carry user plane information about terminal data collection and / or reporting in the registration acceptance message or terminal configuration update message; or,

[0253] SMF can carry user plane information for terminal data acquisition and / or reporting in the session establishment or modification received message; or

[0254] PCF can carry user plane information about terminal data collection and / or reporting in policy request response messages or policy command messages; or...

[0255] DCMF can carry user plane information for terminal data acquisition and / or reporting in terminal data acquisition capability response or confirmation messages, or terminal data acquisition (and / or reporting) response or confirmation messages.

[0256] It should be noted that step 503 can be combined with step 511 and executed together. That is, AMF, SMF, PCF or DCMF can send the confirmed (allowed or authorized) terminal data collection and / or reporting capability information and the terminal data collection and / or reporting user plane information to the terminal through the same message.

[0257] Step 512: Based on the received user plane information of terminal data collection and / or reporting, the terminal establishes a user plane connection with DEF for transmitting data collected and / or reported by the terminal for AI / ML model training. The terminal performs data collection and / or reporting based on the terminal data collection and / or reporting capability information and terminal data collection and / or reporting strategy determined through negotiation with the network.

[0258] Step 513: In some embodiments, the terminal sends terminal data acquisition and / or reporting confirmation information to the AMF, SMF, PCF or DCMF.

[0259] Step 514: AMF, SMF, PCF, or DCMF storage terminal data acquisition and / or reporting context, including terminal identifier, DEF information used for transmitting terminal data, session information for data transmission (session identifier, QoS information, etc.), and data acquisition and / or reporting information (information type / purpose, region, time period, accuracy, latency, etc.).

[0260] Step 515: The terminal transmits the data collected by the terminal to the DEF. The specific process can be seen in the embodiments shown in Figure 7 or Figure 8.

[0261] Step 516: DEF transmits the data collected by the terminal to MTF and / or IF (e.g., a third-party server with AI / ML model training and / or inference capabilities).

[0262] In the embodiment shown in Figure 6, DCMF and DEF are merged into DCEF, which authorizes terminal data collection and reporting, and / or access, and establishes a user plane connection for terminal data reporting. The terminal negotiates data collection and / or reporting capabilities and policies with DCEF.

[0263] Step 601: The terminal sends terminal data acquisition and / or reporting capability information (corresponding to the second information) to DCEF, which may include the data acquisition type or purpose supported by the terminal, accuracy, data format, period, triggering conditions ( / events), latency, information on AI / ML models or inferences using terminal data (e.g., type, identifier, time period, region, accuracy, latency), terminal type (e.g., mobile broadband communication terminal, IoT device, drone, vehicle), etc.

[0264] The terminal can dynamically adjust its data collection and / or reporting capabilities based on local or network AI strategies, resource usage, energy consumption status, sensing capabilities, application / service information, etc., and update these capabilities to the network.

[0265] Specifically, the terminal may include terminal data acquisition and / or reporting capability information in a terminal data acquisition capability request or response message, or a terminal data acquisition and / or reporting request or response message, and send it to the DCEF. This message may be sent by the terminal to the AMF, and then forwarded by the AMF to the DCEF.

[0266] The terminal data acquisition and / or reporting request or response messages may carry QoS information (e.g., transmission rate, QoS category / identifier (e.g., 5QI), QoS characteristic parameters (e.g., data transmission latency, error rate)) requested by the terminal for transmission of the acquired terminal data. The terminal can determine a second QoS information for the acquired terminal data based on information from AI / ML models or inference using the terminal data. Specifically, the terminal determines the QoS requirements for data acquisition during model training or inference, such as data volume, latency, and accuracy requirements, based on the AI / ML model or inference type / identifier, thereby determining the second QoS information for the acquired terminal data.

[0267] Step 602: After receiving the terminal data collection and / or reporting capability information, DCEF requests contract data to obtain relevant contract information for terminal data collection, and then determines the permitted or authorized terminal data collection and / or reporting information. Specifically:

[0268] DCEF obtains terminal-related data stored in the network from network functions that manage terminal-related data (such as UDM or UDR).

[0269] Terminal-related data includes information related to terminal data collection (and / or reporting), such as: the type or purpose of data (e.g., sensing data, location data, wireless access data) that the terminal is allowed to collect and / or report, the area and / or time period of data that the terminal is allowed to collect and / or report, and the user's privacy settings for data collection and / or reporting.

[0270] The terminal-related data also includes terminal data openness-related data, which may include: terminal data information that is allowed or authorized to be opened (e.g., type or purpose, region, time period, collection frequency, accuracy, latency), terminal data recipient information (e.g., third-party server information (identifier, address or other information) for model training or inference, referred to here as MTF and / or IF for terminal data recipient), application / business information using terminal data (e.g., application / business identifier), and information on AI / ML models or inference using terminal data (e.g., model or inference type / identifier), etc.

[0271] Based on the terminal-related data stored in the network, DCEF determines the information that allows or authorizes terminal data collection and / or reporting, namely, the contract or authorization information related to terminal data collection and / or reporting, such as: the type or purpose of the data that the terminal is allowed to collect and / or report (e.g., sensing data, location data, wireless access data), the area and time information of the data that the terminal is allowed to collect and / or report, etc.

[0272] Step 603: DCEF sends terminal data collection and / or reporting capability confirmation information to the terminal, which carries the terminal data collection and / or reporting capability information confirmed in step 602 (allowing or authorizing).

[0273] Specifically, the "confirmed (permitted or authorized) terminal data collection and / or reporting capability information" here may include updates to previously confirmed (permitted or authorized) terminal data collection and / or reporting capability information.

[0274] Specifically, DCEF can carry confirmed terminal data acquisition and / or reporting capability information in the terminal data acquisition capability response or confirmation message, or the terminal data acquisition and / or reporting response or confirmation message.

[0275] Step 604: If step 603 carries updated terminal data acquisition and / or reporting capability information, the terminal can send terminal data acquisition and / or reporting capability update confirmation information to DCEF.

[0276] Step 605: DCEF sends a terminal data collection and / or reporting policy request information to PCF, including terminal identifier, terminal data collection and / or reporting capabilities, etc.

[0277] Step 606: The PCF sends terminal data acquisition and / or reporting policy information to the DCEF. This policy information may include the following:

[0278] Scope and requirements for terminal data collection and / or reporting: the type or purpose of the data collected and / or reported by the terminal (e.g., sensing data, positioning data, wireless access data, applicable applications / services), region, time information, data format, accuracy, latency, period, triggering conditions (triggering events), etc.

[0279] Transmission information of data collected and / or reported by the terminal, such as: session information of the terminal data being collected and / or reported (e.g., the slice to which the session belongs, data network, application / service information), access network information, wireless access technology information, frequency-related information, etc.

[0280] PCF can determine the policy based on the following information: terminal data collection and / or reporting of relevant network-side data (see step 602, such as subscription data), user privacy settings (see step 602), terminal type (such as mobile broadband communication terminal, IoT device, drone, vehicle), network status (such as resource usage), operator policies, and SLAs between operators and third parties.

[0281] Step 607a / 607b. PCF, or DCEF, based on the policy received from PCF (see step 606), sends terminal data collection and / or reporting policy (or configuration) information to the terminal.

[0282] Specifically, the strategy (or configuration) may include the following information:

[0283] Scope and requirements for terminal data collection and / or reporting: the type or purpose of the data collected and / or reported by the terminal (e.g., sensing data, positioning data, wireless access data, applicable applications / services), region, time information, data format, accuracy, latency, period, triggering conditions (triggering events), etc.

[0284] Transmission information of data collected and / or reported by the terminal, such as: session information of the terminal data being collected and / or reported (e.g., the slice to which the session belongs, data network, application / service information), access network information, wireless access technology information, frequency-related information, etc.

[0285] PCF can determine the policy based on the following information: terminal data collection and / or reporting of relevant terminal data (see step 602), user privacy settings (see step 602), terminal type (e.g., mobile broadband communication terminal, IoT device, drone, vehicle), network status (e.g., resource usage), operator policies, and SLAs between operators and third parties.

[0286] In some embodiments, the terminal sends terminal data collection and / or reporting policy (or configuration) confirmation information to the PCF or DCEF, which may include the data collection and / or reporting policy accepted by the terminal, such as data collection accuracy, latency, period, triggering conditions ( / triggering events), access technology, etc.

[0287] Step 608: The DCEF determines the permitted or authorized terminal data opening information and determines the relevant parameters for transmitting terminal data accordingly, such as the first QoS of authorized terminal data transmission. The DEF determines the permitted or authorized terminal data opening information based on the terminal data opening-related data stored in the network (see step 602), including: permitted / authorized terminal data opening information, permitted / authorized terminal data receiver information, permitted / authorized application / service information for using terminal data, permitted / authorized AI / ML model or inference information for using terminal data, etc.

[0288] DCEF determines whether to use the CP (Content Plane) or the UP (User Plane) (here and below, the User Plane also includes dedicated transmission channels for transmitting AI-related data, or the Data Plane) for data collection and / or reporting. For example, DCEF determines whether to use the Control Plane or the User Plane based on factors such as the terminal data collection type, data collection QoS requirements, data volume, terminal type (e.g., mobile broadband communication terminal, IoT device, drone, vehicle), and network status (e.g., resource usage).

[0289] Step 609: If the DCEF determines that the user plane is used for terminal data collection and / or reporting, the DCEF sends the user plane information for terminal data collection and / or reporting to the terminal, such as the DCEF address, data transmission tunnel identifier, connection identifier or association identifier, and QoS of authorized terminal data transmission.

[0290] Specifically, DCEF can determine the QoS information for authorized terminal data transmission based on information from AI / ML models or inference that use terminal data. In particular, DCEF determines the QoS requirements for data collection during model training or inference, such as data volume, latency, and accuracy, based on the AI / ML model or inference type / identifier, thereby determining the QoS information for authorized terminal data transmission.

[0291] Specifically, the DCEF can carry user plane information related to terminal data acquisition and / or reporting in the terminal data acquisition capability response or confirmation message, or the terminal data acquisition (and / or reporting) response or confirmation message. This message can be sent by the DCEF to the AMF, and then forwarded by the AMF to the terminal.

[0292] It should be noted that steps 603 and 607b above can be combined into step 609 for execution together. That is, DCEF can send the confirmed (allowed or authorized) terminal data collection and / or reporting capability information, terminal data collection and / or reporting policy, and terminal data collection and / or reporting user plane information to the terminal through the same message.

[0293] Step 610: The terminal establishes a user plane connection with DCEF based on the received user plane information of terminal data collection and / or reporting, for transmitting data collected and / or reported by the terminal for AI / ML model training. The terminal performs data collection and / or reporting based on the terminal data collection and / or reporting capability information and terminal data collection and / or reporting strategy determined through negotiation with DCEF.

[0294] Step 611: In some embodiments, the terminal sends terminal data acquisition and / or reporting confirmation information to the DCEF.

[0295] Step 612: DCEF storage terminal data acquisition and / or reporting context, including terminal identifier, session information of transmitted data (session identifier, QoS information, etc.), and data acquisition and / or reporting information (information type / purpose, region, time period, accuracy, latency, etc.).

[0296] Step 613: The terminal transmits the data collected by the terminal to the DCEF. For details, please refer to the embodiments in Figure 7 or Figure 8.

[0297] Step 614: DCEF transmits the data collected by the terminal to MTF and / or IF (e.g., a third-party server with AI / ML model training and / or inference capabilities).

[0298] In the embodiment shown in Figure 7, the DCEF (or DCMF / DEF) and the Access Network (AN) are configured through the control plane to collect and / or report data to the terminal; the terminal encapsulates data packets based on the data collection and / or reporting configuration and reports the collected data through the user plane; the DCEF (DEF) inspects the data packets. This may include:

[0299] Step 701: The MTF and / or IF (e.g., a third-party server with AI / ML model training and / or inference capabilities) send a terminal data acquisition request (corresponding to the fourth information) to the DCEF (or DEF / DCMF), which carries the terminal data acquisition and / or reporting requirements, such as data type or purpose, format, time information, region, accuracy, latency, period, triggering conditions ( / triggering events), information on the AI / ML model and / or inference using the data (e.g., model type or identifier, inference type or identifier, model / inference accuracy requirements), application / business identifier of the data, etc.

[0300] If the DEF receives the terminal data acquisition request, the DEF can forward the request to the DCMF, so that the DCMF can send terminal data acquisition and / or report configuration information to the terminal through the AN (see step 702).

[0301] Step 702: Based on the received terminal data acquisition request, DCEF (or DEF / DCMF) sends terminal data acquisition and / or reporting configuration information to the terminal via AN, such as data type, format, time period, region, precision, latency, period, triggering condition ( / triggering event), information on the AI / ML model and / or inference using the data (e.g., model type or identifier, inference type or identifier), application / business identifier using the data, etc.

[0302] DCEF (or DEF / DCMF) can also provide AN with information about the AI / ML models and / or inferences that use the data (e.g., model type or identifier, inference type or identifier, model / inference accuracy requirements).

[0303] Step 703: The AN sends terminal data acquisition and / or reporting configuration information to the terminal, including: 1) terminal data acquisition and / or reporting configuration information received from DCEF (or DEF / DCMF); 2) terminal data acquisition and / or reporting configuration information set by the AN, such as configuration information for acquiring and / or reporting wireless interface measurement data (e.g., received signal power / delay), such as data type, format, time period, region, accuracy, delay, period, trigger condition ( / trigger event), and information on AI / ML models and / or inference using the data.

[0304] The AN can determine the terminal data collection and / or reporting configuration information set above based on the AI / ML model and / or inference information of the usage data provided by DCEF (or DEF / DCMF).

[0305] Step 704: The terminal sends terminal data acquisition and / or reporting configuration confirmation information to the AN, including the terminal data acquisition and / or reporting configuration accepted by the terminal. Specifically, it includes the data acquisition and / or reporting configuration provided by DCEF (or DEF / DCMF) accepted by the terminal, and / or the data acquisition and / or reporting configuration provided by the AN accepted by the terminal.

[0306] Step 705: AN sends terminal data acquisition and / or configuration confirmation information to DCEF (or DEF / DCMF).

[0307] This information may include the terminal data acquisition and / or reporting configuration information set by the AN.

[0308] If the DCMF receives the configuration confirmation information, the DCMF can forward the negotiated terminal data collection and / or reporting configuration information to the DEF, so that the DEF can check whether the terminal data contained in the data packet sent by the terminal conforms to the data collection configuration (see step 711).

[0309] Step 706: DCEF (or DEF / DCMF) sends a terminal data acquisition response to MTF and / or IF.

[0310] Step 707: The terminal collects data according to the data collection and / or reporting configuration.

[0311] Step 708: The terminal determines whether to adopt the user plane data collection and / or reporting method. The terminal may determine whether to adopt the user plane data collection and / or reporting method based on local policies, QoS requirements / data volume for collection and / or reporting, and whether the terminal has established a user plane connection with DCEF (or DEF) for terminal data collection and / or reporting.

[0312] If the terminal determines to use the user plane data collection and / or reporting method, then perform the following steps:

[0313] Step 709: The terminal encapsulates the collected data into data packets (or PDUs) according to the user plane data acquisition protocol (or data acquisition and reporting protocol, or data reporting protocol).

[0314] Step 710: The terminal uses the established user plane connection to send a data packet carrying the collected terminal data to the DCEF (or DEF). If the terminal has not yet established a user plane connection for this terminal data collection and / or reporting, the terminal needs to establish a user plane connection for this terminal data collection and / or reporting first (for example, steps 601 and 609, 610 in the embodiment shown in Figure 6, and steps 501 and 508-512 in the embodiment shown in Figure 5).

[0315] Step 711: DCEF (or DEF) checks whether the received data packet conforms to the user plane data acquisition protocol, such as whether it conforms to the protocol format requirements. DCEF (or DEF) can also determine whether the terminal data contained in the data packet conforms to the data acquisition configuration based on the terminal data acquisition and / or reporting configuration negotiated in steps 701-705, such as: not containing data / information types that the network and / or user (or terminal) are not allowed to send.

[0316] Step 712: If the content (such as the data type and format of the data packet reported by the terminal) does not conform to the user plane data acquisition protocol and / or data acquisition configuration requirements, the DCEF (or DEF) discards the data packet and may send a rejection message to the terminal, which carries the error data packet and / or error field information.

[0317] Step 713: If the terminal receives a rejection message (i.e., terminal data acquisition error indication message) from DCEF (or DEF), it can be used by the terminal to correct or delete the error field in the error data packet, and then send the correct data packet.

[0318] Step 714: DCEF (or DEF) transmits the data collected by the terminal to MTF and / or IF.

[0319] In the embodiment shown in Figure 8, the DCEF (or DEF) is configured through user-facing terminal data collection and / or reporting; the terminal encapsulates data packets based on the data collection and / or reporting configuration and reports the collected data through the user face; the DCEF (or DEF) inspects the data packets. This process may include:

[0320] Step 801: The MTF and / or IF (e.g., a third-party server with AI / ML model training and / or inference capabilities) send a terminal data acquisition request to the DCEF (or DEF), which carries the terminal data acquisition (and / or reporting) requirements, such as data type or purpose, format, time period, region, accuracy, latency, period, triggering conditions ( / triggering events), information on the AI / ML model and / or inference using the data (e.g., model type or identifier, inference type or identifier, model / inference accuracy requirements), application / business identifier of the data, etc.

[0321] Step 802: DCEF (or DEF) sends a data acquisition request data packet to the terminal according to the user plane data acquisition protocol. The data packet contains data acquisition configuration information, such as data type, format, time period, region, precision, latency, period, triggering conditions ( / triggering events), information on the AI / ML model and / or inference using the data (e.g., model type or identifier, inference type or identifier, model / inference precision requirements), application / business identifier for using the data, etc.

[0322] Step 803: The terminal sends a data acquisition response data packet to the DCEF (or DEF) according to the user plane data acquisition protocol. The data acquisition configuration information confirmed by the terminal is the data acquisition (and / or reporting) configuration provided by the DCEF (or DEF) accepted by the terminal.

[0323] Step 804: DCEF (or DEF) sends a terminal data acquisition response to MTF and / or IF.

[0324] Step 805: The terminal collects data according to the configuration information and encapsulates the collected data into data packets (or PDUs) according to the user plane data collection protocol. For details, please refer to steps 708 and 709 in Figure 7.

[0325] Step 806: The terminal sends a data packet carrying the collected data to the DCEF (or DEF).

[0326] Step 807: DCEF checks the received terminal data packets and sends them to MTF / IF. See steps 711-714 in Figure 7 for details.

[0327] Specifically, DCEF (or DEF) checks whether the received data packets conform to the user plane data acquisition protocol, such as whether they meet the protocol format requirements. DCEF (or DEF) can also determine whether the terminal data contained in the data packets conforms to the data acquisition configuration based on the terminal data acquisition and / or reporting configuration negotiated in steps 701-705, such as: not containing data / information types that the network and / or user (or terminal) are not allowed to send.

[0328] If the content of the terminal data reporting packet (such as the reported data type and format) does not conform to the user plane data acquisition protocol and / or data acquisition configuration requirements, the DCEF (or DEF) will discard the packet and may send a rejection message to the terminal, which carries the error packet and / or error field information.

[0329] If the terminal receives a rejection message (i.e., terminal data acquisition error indication message) from DCEF (or DEF), it can be used by the terminal to correct or delete the erroneous fields in the erroneous data packet, and then send the correct data packet.

[0330] DCEF (or DEF) transmits the data collected by the terminal to MTF and / or IF.

[0331] As can be seen from the above solutions, this embodiment of the disclosure can support the network to authorize and inspect the data collected, reported and / or opened by the terminal, as well as to transmit and open the terminal data through the user plane, thereby achieving effective control over the collection, reporting and / or opening of terminal data.

[0332] The technical solutions provided in this disclosure can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and the 6th Generation Mobile Communication Technology (6G) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as the Evolved Packet Core (EPC) and the 5G Core (5GC).

[0333] The terminal devices involved in the embodiments of this disclosure can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in 5G or 6G systems, the terminal device may be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) telephones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile devices, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition, but are not limited to these in the embodiments of this disclosure.

[0334] As shown in Figure 9, the data acquisition device of this embodiment, applied to a terminal, includes: a processor 900, used to read a program from a memory 920 and execute the following processes:

[0335] Obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0336] Based on the first information, determine the terminal data;

[0337] Send the terminal data to the first functional entity;

[0338] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0339] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0340] Terminal data collection, reporting, and / or sharing of related policy information;

[0341] Terminal data collection, reporting, and / or sharing of related configuration information;

[0342] Terminal data collection, reporting, and / or open request information.

[0343] Transceiver 910 is used to receive and send data under the control of processor 900.

[0344] In Figure 9, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 910 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 930 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0345] The processor 900 is responsible for managing the bus architecture and general processing, while the memory 920 can store the data used by the processor 900 during operation.

[0346] The processor 900 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0347] The processor executes any of the methods described in the embodiments of this disclosure by invoking a computer program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.

[0348] The processor 900 is also used to read the program and perform the following steps:

[0349] Receive the first information from the second functional entity.

[0350] The processor 900 is also used to read the program and perform the following steps:

[0351] Send a second message to the second functional entity. The second message is used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response. The second message includes one or more of the following:

[0352] The types of data or uses of data collected, reported, and / or made public at the terminal;

[0353] Terminal data collection, reporting, and / or access to regional and / or time information;

[0354] Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information;

[0355] Information from machine learning models or inferences using terminal data;

[0356] Application or business information that uses terminal data;

[0357] Terminal type;

[0358] Terminal data collection, reporting, and / or access to secondary QoS information.

[0359] The processor 900 is also used to read the program and perform the following steps:

[0360] Based on the first information, determine the second information;

[0361] or,

[0362] The second QoS information for terminal data collection, reporting, and / or access is determined based on one or more of the following:

[0363] The types of data or uses of data collected, reported, and / or made public at the terminal;

[0364] Terminal data acquisition, reporting, and / or access information including latency, period, and / or triggering conditions;

[0365] Information from machine learning models or inferences using terminal data;

[0366] Application or business information that uses terminal data;

[0367] Resource usage of the terminal or network;

[0368] Energy consumption status of the terminal or network.

[0369] The processor 900 is also used to read the program and perform the following steps:

[0370] Send a third message to the second functional entity, the third message being used to indicate the terminal's acceptance of terminal data collection, reporting, and / or opening-related policy information or configuration information.

[0371] The processor 900 is also used to read the program and perform the following steps:

[0372] Receive terminal data collection, reporting, and / or open user plane information sent by the first functional entity;

[0373] Establish a user plane connection with the first functional entity based on the user plane information;

[0374] The user face information includes one or more of the following:

[0375] The user plane address of the first functional entity;

[0376] Data transmission tunnel identifier, connection identifier, or association identifier;

[0377] QoS information that is permitted or authorized for terminal data transmission.

[0378] The processor 900 is also used to read the program and perform the following steps:

[0379] Receive terminal data acquisition error indication information sent by the first functional entity;

[0380] Based on the terminal data acquisition error indication information, updated terminal data is sent to the first functional entity.

[0381] The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol.

[0382] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0383] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0384] As shown in Figure 10, the data acquisition device of this embodiment is applied to a second functional entity and includes: a processor 1000, used to read a program from a memory 1020 and execute the following processes:

[0385] Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data;

[0386] Send the first information to the terminal;

[0387] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0388] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0389] Terminal data collection, reporting, and / or sharing of related policy information;

[0390] Terminal data collection, reporting, and / or sharing of related configuration information;

[0391] Terminal data collection, reporting, and / or open request information.

[0392] Transceiver 1010 is used to receive and send data under the control of processor 1000.

[0393] In Figure 10, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1000 and memory represented by memory 1020. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 1010 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. Processor 1000 is responsible for managing the bus architecture and general processing, and memory 1020 may store data used by processor 1000 during operation.

[0394] The processor 1000 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0395] The processor 1000 is responsible for managing the bus architecture and general processing, while the memory 1020 can store the data used by the processor 1000 when performing operations.

[0396] The processor 1000 is also used to read the program and perform the following steps:

[0397] The system receives second information sent by the terminal, the second information being used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response; or,

[0398] Receive fourth information sent by a third functional entity, the fourth information being used to indicate a request to collect, report, and / or open the terminal data; determine or obtain the first information based on the second information or the fourth information.

[0399] The processor 1000 is also used to read the program and perform the following steps:

[0400] The terminal receives third information sent by the terminal, the third information being used to indicate the terminal's acceptance of terminal data collection, reporting, and / or access-related policy information or configuration information.

[0401] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0402] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0403] As shown in Figure 11, the data acquisition device of this embodiment is applied to a first functional entity and includes: a processor 1100, used to read a program from a memory 1120 and execute the following processes:

[0404] Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information;

[0405] Receive terminal data;

[0406] Based on the first information, the terminal data is sent to the third functional entity;

[0407] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0408] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0409] Terminal data collection, reporting, and / or sharing of related policy information;

[0410] Terminal data collection, reporting, and / or sharing of related configuration information;

[0411] Terminal data collection, reporting, and / or open request information.

[0412] Transceiver 1110 is used to receive and send data under the control of processor 1100.

[0413] In Figure 11, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1100 and memory represented by memory 1120. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 1110 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over a transmission medium. Processor 1100 is responsible for managing the bus architecture and general processing, and memory 1120 may store data used by processor 1100 during operation.

[0414] The processor 1100 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0415] The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store the data used by the processor 1100 when performing operations.

[0416] Processor 1100 is also used to read the program and perform the following steps:

[0417] The terminal data is received via control plane signaling or user plane connection.

[0418] Processor 1100 is also used to read the program and perform the following steps:

[0419] Determine the user plane information for terminal data collection, reporting, and / or access;

[0420] The user plane connection is established based on the user plane information, and the terminal data is received through the user plane connection.

[0421] The user face information includes one or more of the following:

[0422] The user plane address of the first functional entity;

[0423] Data transmission tunnel identifier, connection identifier, or association identifier;

[0424] QoS information that is permitted or authorized for terminal data transmission.

[0425] Processor 1100 is also used to read the program and perform the following steps:

[0426] The received terminal data is checked to determine whether the terminal data meets the requirements of the first information.

[0427] Processor 1100 is also used to read the program and perform the following steps:

[0428] If it is determined that the terminal data does not meet the requirements of the first information, a terminal data acquisition error indication message is sent to the terminal.

[0429] Receive updated terminal data sent by the terminal.

[0430] The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol.

[0431] The terminal data is used for training or inference of machine learning models.

[0432] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0433] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0434] As shown in Figure 12, the data acquisition device of this embodiment is applied to an access network device and includes: a processor 1200, used to read a program from a memory 1220 and execute the following processes:

[0435] Send terminal data collection, reporting, and / or opening related configuration information to the terminal, wherein the terminal data collection, reporting, and / or opening related configuration information is used to obtain terminal data;

[0436] Send the terminal data collection, reporting, and / or opening-related configuration information to the first or second functional entity.

[0437] Transceiver 1210 is used to receive and send data under the control of processor 1200.

[0438] In Figure 12, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1200 and memory represented by memory 1220. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 1210 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. Processor 1200 is responsible for managing the bus architecture and general processing, and memory 1220 may store data used by processor 1200 during operation.

[0439] The processor 1200 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0440] The processor 1200 is responsible for managing the bus architecture and general processing, while the memory 1220 can store the data used by the processor 1200 when performing operations.

[0441] The configuration information related to terminal data collection, reporting, and / or access includes:

[0442] The access network device receives configuration information related to terminal data collection, reporting, and / or opening from the first functional entity or the second functional entity, and / or the access network device receives configuration information related to terminal data collection, reporting, and / or opening.

[0443] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0444] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0445] As shown in Figure 13, the data acquisition device of this embodiment of the present disclosure is applied to a terminal and includes:

[0446] The first acquisition unit 1301 is used to acquire first information, the first information including terminal data collection, reporting and / or open related information; the first determination unit 1302 is used to determine terminal data according to the first information; the first sending unit 1303 is used to send the terminal data to the first functional entity.

[0447] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0448] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0449] Terminal data collection, reporting, and / or sharing of related policy information;

[0450] Terminal data collection, reporting, and / or sharing of related configuration information;

[0451] Terminal data collection, reporting, and / or open request information.

[0452] In some embodiments, the apparatus may further include:

[0453] The first receiving unit is configured to receive the first information from the second functional entity.

[0454] In some embodiments, the apparatus may further include:

[0455] The second sending unit is configured to send second information to the second functional entity. The second information is used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response. The second information includes one or more of the following:

[0456] The types of data or uses of data collected, reported, and / or made public at the terminal;

[0457] Terminal data collection, reporting, and / or access to regional and / or time information;

[0458] Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information;

[0459] Information from machine learning models or inferences using terminal data;

[0460] Application or business information that uses terminal data;

[0461] Terminal type;

[0462] Terminal data collection, reporting, and / or access to secondary QoS information.

[0463] In some embodiments, the apparatus may further include: a second determining unit, configured to:

[0464] Based on the first information, determine the second information;

[0465] or,

[0466] The second QoS information for terminal data collection, reporting, and / or access is determined based on one or more of the following:

[0467] The types of data or uses of data collected, reported, and / or made public at the terminal;

[0468] Terminal data acquisition, reporting, and / or access information including latency, period, and / or triggering conditions;

[0469] Information from machine learning models or inferences using terminal data;

[0470] Application or business information that uses terminal data;

[0471] Resource usage of the terminal or network;

[0472] Energy consumption status of the terminal or network.

[0473] In some embodiments, the apparatus may further include:

[0474] The third sending unit is used to send third information to the second functional entity. The third information is used to indicate the terminal's accepted terminal data collection, reporting and / or opening-related policy information or configuration information.

[0475] In some embodiments, the third sending unit is further configured to: send the terminal data to the first functional entity via control plane signaling or user plane connection.

[0476] In some embodiments, the apparatus may further include:

[0477] The first receiving unit is used to receive terminal data collection, reporting and / or open user plane information sent by the first functional entity;

[0478] The first processing unit is configured to establish a user plane connection with the first functional entity based on the user plane information.

[0479] The user face information includes one or more of the following:

[0480] The user plane address of the first functional entity;

[0481] Data transmission tunnel identifier, connection identifier, or association identifier;

[0482] QoS information that is permitted or authorized for terminal data transmission.

[0483] In some embodiments, the apparatus may further include:

[0484] The second receiving unit is used to receive terminal data acquisition error indication information sent by the first functional entity;

[0485] The third sending unit is used to send updated terminal data to the first functional entity based on the terminal data acquisition error indication information.

[0486] The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol.

[0487] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0488] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0489] As shown in Figure 14, the data acquisition device of this embodiment is applied to a second functional entity and includes:

[0490] The first processing unit 1401 is used to determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data; the first sending unit 1402 is used to send the first information to the terminal.

[0491] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0492] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0493] Terminal data collection, reporting, and / or sharing of related policy information;

[0494] Terminal data collection, reporting, and / or sharing of related configuration information;

[0495] Terminal data collection, reporting, and / or open request information.

[0496] In some embodiments, the apparatus may further include: a first receiving unit, configured to:

[0497] The system receives second information sent by the terminal, the second information being used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response; or,

[0498] Receive fourth information sent by a third functional entity, the fourth information being used to indicate a request to collect, report, and / or open the terminal data; determine or obtain the first information based on the second information or the fourth information.

[0499] In some embodiments, the apparatus may further include: a second receiving unit, configured to receive third information sent by the terminal, the third information being used to indicate policy information or configuration information related to terminal data collection, reporting, and / or opening that the terminal has accepted.

[0500] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0501] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0502] As shown in Figure 15, the data acquisition device of this embodiment is applied to a first functional entity and includes:

[0503] The first processing unit 1501 is used to determine or obtain first information, the first information including terminal data collection, reporting and / or open related information; the first receiving unit 1502 is used to receive terminal data; the first sending unit 1503 is used to send the terminal data to the third functional entity based on the first information.

[0504] The terminal data collection, reporting, and / or opening of related information includes one or more of the following:

[0505] Terminal data collection, reporting, and / or sharing of related contractual or authorized information;

[0506] Terminal data collection, reporting, and / or sharing of related policy information;

[0507] Terminal data collection, reporting, and / or sharing of related configuration information;

[0508] Terminal data collection, reporting, and / or open request information.

[0509] In some embodiments, the apparatus may further include:

[0510] The second processing unit is used to determine the user plane information for terminal data collection, reporting, and / or access;

[0511] The third processing unit is used to establish the user plane connection based on the user plane information and receive the terminal data through the user plane connection.

[0512] The user face information includes one or more of the following:

[0513] The user plane address of the first functional entity;

[0514] Data transmission tunnel identifier, connection identifier, or association identifier;

[0515] QoS information that is permitted or authorized for terminal data transmission.

[0516] In some embodiments, the first sending unit is further configured to check the received terminal data to determine whether the terminal data meets the requirements of the first information.

[0517] In some embodiments, the apparatus may further include:

[0518] The second sending unit is used to send terminal data acquisition error indication information to the terminal when it is determined that the terminal data does not meet the requirements of the first information.

[0519] The second receiving unit is used to receive updated terminal data sent by the terminal.

[0520] The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol.

[0521] The terminal data is used for training or inference of machine learning models.

[0522] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0523] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0524] As shown in Figure 16, the data acquisition device of this embodiment is applied to an access network device and includes:

[0525] The first sending unit 1601 is used to send configuration information related to terminal data collection, reporting and / or opening to the terminal, wherein the configuration information related to terminal data collection, reporting and / or opening is used to obtain terminal data;

[0526] The second sending unit 1602 sends the terminal data acquisition, reporting and / or opening related configuration information to the first functional entity or the second functional entity.

[0527] For an explanation of the above information, please refer to the description of the aforementioned method embodiments.

[0528] In some embodiments, the configuration information related to terminal data collection, reporting, and / or access includes:

[0529] The access network device receives configuration information related to terminal data collection, reporting, and / or opening from the first functional entity or the second functional entity, and / or the access network device receives information related to terminal data collection, reporting, and / or opening.

[0530] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0531] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0532] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0533] This disclosure also provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the data acquisition method described above.

[0534] This disclosure also provides a computer program product, including computer instructions. When executed by a processor, these computer instructions 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.

[0535] This disclosure also provides a processor-readable storage medium storing a program that, when executed by a processor, implements the various processes of the above-described data acquisition method embodiments and achieves the same technical effects. To avoid repetition, further details are omitted here. The readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magnetic optical discs (MO), etc.), optical storage (e.g., compact discs (CDs), digital video discs (DVDs), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor storage (e.g., read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND FLASH), solid-state drives (SSDs), etc.).

[0536] 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. Unless otherwise specified, 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.

[0537] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0538] This disclosure describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this disclosure with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0539] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0540] Furthermore, it should be noted that in the apparatus and method of this disclosure, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of this disclosure. Moreover, the steps performing the above series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of this disclosure can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof, which can be achieved by those skilled in the art using their basic programming skills after reading the description of this disclosure.

[0541] It should be noted that the above division of modules is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, a module can be a separate processing element, or it can be integrated into a chip in the aforementioned device. Alternatively, it can be stored as program code in the memory of the aforementioned device, and its function can be called and executed by a processing element of the device. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element mentioned here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0542] For example, each module, unit, subunit, or submodule can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs). As another example, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together to implement a system-on-a-chip (SOC).

[0543] The terms “first,” “second,” etc., used in this disclosure and in the claims are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this disclosure described herein may be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. Additionally, the use of “and / or” in the specification and claims indicates at least one of the connected objects, such as A and / or B and / or C, indicating seven possibilities: A alone, B alone, C alone, and both A and B, both B and C, both A and C, and A, B, and C. Similarly, the use of “at least one of A and B” in this specification and claims should be understood as “A alone, B alone, or both A and B.”

[0544] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this disclosure without departing from the spirit and scope of the embodiments of this disclosure. Therefore, if these modifications and variations to the embodiments of this disclosure fall within the scope of the claims of the embodiments of this disclosure and their equivalents, then the embodiments of this disclosure are also intended to include these modifications and variations.

Claims

A data acquisition method, applied to a terminal, the method comprising: Obtain first information, which includes terminal data collection, reporting, and / or open related information; Based on the first information, determine the terminal data; Send the terminal data to the first functional entity; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. According to the method of claim 1, wherein, The terminal data collection, reporting, and / or sharing of related contract or authorization information includes one or more of the following information or updates to one or more of the following information: The types of data or uses of terminal data that are allowed to be collected, reported, and / or made public; Areas where terminal data collection, reporting, and / or access are permitted; Time information that allows the collection, reporting, and / or release of terminal data; Applications or business information that allow or authorize the use of terminal data; Information that allows or authorizes the use of machine learning models or inferences from terminal data; Information about the recipients or users of terminal data that are permitted or authorized. According to the method of claim 1, wherein, The policy information related to terminal data collection, reporting, and / or access, or the configuration information related to terminal data collection, reporting, and / or access, or the request information for terminal data collection, reporting, and / or access, includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Access network information, wireless access technology information, and / or frequency-related information corresponding to the terminal data collected, reported, and / or made public; Session information used for collecting, reporting, and / or opening the terminal data; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal data collection, reporting, and / or access to the first Quality of Service (QoS) information. According to the method of claim 1, wherein, The acquisition of the first information includes: Receive the first information from the second functional entity. The method according to claim 4, further comprising: Send a second message to the second functional entity. The second message is used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response. The second message includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal type; Terminal data collection, reporting, and / or access to secondary QoS information. The method according to claim 2, 3 or 5, wherein, The information regarding the machine learning model or inference using terminal data includes one or more of the following: the type, identifier, applicable time, applicable region, accuracy, and / or latency of the machine learning model or inference; or, Terminal types include one or more of the following: mobile broadband communication terminals, Internet of Things (IoT) devices, drones, and vehicles; or, QoS information includes one or more of the following: transmission rate, QoS category or identifier, and QoS characteristic parameters. The method according to claim 5, further comprising: Based on the first information, determine the second information; or, The second QoS information for terminal data collection, reporting, and / or access is determined based on one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data acquisition, reporting, and / or access information including latency, period, and / or triggering conditions; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Resource usage of the terminal or network; Energy consumption status of the terminal or network. The method according to claim 4, further comprising: Send a third message to the second functional entity, the third message being used to indicate the terminal's acceptance of terminal data collection, reporting, and / or opening-related policy information or configuration information. According to the method of claim 1, wherein, Sending the terminal data to the first functional entity includes: The terminal data is sent to the first functional entity via control plane signaling or user plane connection. The method according to claim 9, further comprising: Receive terminal data collection, reporting, and / or open user plane information sent by the first functional entity; Establish a user plane connection with the first functional entity based on the user plane information; The user face information includes one or more of the following: The user plane address of the first functional entity; Data transmission tunnel identifier, connection identifier, or association identifier; QoS information that is permitted or authorized for terminal data transmission. The method according to claim 9, further comprising: Receive terminal data acquisition error indication information sent by the first functional entity; Based on the terminal data acquisition error indication information, updated terminal data is sent to the first functional entity. The method according to any one of claims 9-11, wherein, The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol. A data acquisition method, applied to a second functional entity, the method comprising: Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data; Send the first information to the terminal; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. The method according to claim 13, wherein, The terminal data collection, reporting, and / or sharing of related contract or authorization information includes one or more of the following information or updates to one or more of the following information: The types of data or uses of terminal data that are allowed to be collected, reported, and / or made public; Areas where terminal data collection, reporting, and / or access are permitted; Time information that allows the collection, reporting, and / or release of terminal data; Applications or business information that allow or authorize the use of terminal data; Information that allows or authorizes the use of machine learning models or inferences from terminal data; Information about the recipients or users of terminal data that are permitted or authorized. The method according to claim 13, wherein, The policy information related to terminal data collection, reporting, and / or access, or the configuration information related to terminal data collection, reporting, and / or access, or the request information for terminal data collection, reporting, and / or access, includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Access network information, wireless access technology information, and / or frequency-related information corresponding to the terminal data collected, reported, and / or made public; Session information used for collecting, reporting, and / or opening the terminal data; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal data collection, reporting, and / or the release of first QoS information. The method according to claim 13, further comprising: The system receives second information sent by the terminal, the second information being used to indicate the terminal's data acquisition capability information or to indicate the terminal's data reporting or opening request or response; or, Receive a fourth message sent by a third functional entity, the fourth message being used to indicate a request to collect, report, and / or open the terminal data; The first information is determined or obtained based on the second information or the fourth information. The method according to claim 16, wherein, The second information or the fourth information includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal type; Terminal data collection, reporting, and / or access to secondary QoS information. The method according to claim 14, 15 or 17, wherein, The information regarding the machine learning model or inference using terminal data includes one or more of the following: the type, identifier, applicable time, applicable region, accuracy, and / or latency of the machine learning model or inference; or, Terminal types include one or more of the following: mobile broadband communication terminals, Internet of Things (IoT) devices, drones, and vehicles; or, QoS information includes one or more of the following: transmission rate, QoS category or identifier, and QoS characteristic parameters. The method according to claim 13, further comprising: The terminal receives third information sent by the terminal, the third information being used to indicate the terminal's acceptance of terminal data collection, reporting, and / or access-related policy information or configuration information. A data acquisition method, applied to a first functional entity, the method comprising: Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information; Receive terminal data; Based on the first information, the terminal data is sent to the third functional entity; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. The method according to claim 20, wherein, The received terminal data includes: The terminal data is received via control plane signaling or user plane connection. The method according to claim 20, further comprising: Determine the user plane information for terminal data collection, reporting, and / or access; The user plane connection is established based on the user plane information, and the terminal data is received through the user plane connection. The user face information includes one or more of the following: The user plane address of the first functional entity; Data transmission tunnel identifier, connection identifier, or association identifier; QoS information that is permitted or authorized for terminal data transmission. The method according to claim 20, wherein, The step of sending the terminal data to the third functional entity based on the first information includes: The received terminal data is checked to determine whether the terminal data meets the requirements of the first information. The method according to claim 20, further comprising: If it is determined that the terminal data does not meet the requirements of the first information, a terminal data acquisition error indication message is sent to the terminal. Receive updated terminal data sent by the terminal. The method according to any one of claims 21-24, wherein, The terminal data is a data packet encapsulated according to a control plane data acquisition protocol or a user plane data acquisition protocol. The method according to claim 20, wherein, The terminal data is used for training or inference of machine learning models. The method according to claim 20, wherein, The terminal data collection, reporting, and / or sharing of related contract or authorization information includes one or more of the following information or updates to one or more of the following information: The types of data or uses of terminal data that are allowed to be collected, reported, and / or made public; Areas where terminal data collection, reporting, and / or access are permitted; Time information that allows the collection, reporting, and / or release of terminal data; Applications or business information that allow or authorize the use of terminal data; Information that allows or authorizes the use of machine learning models or inferences from terminal data; Information about the recipients or users of terminal data that are permitted or authorized. The method according to claim 20, wherein, The policy information related to terminal data collection, reporting, and / or access, or the configuration information related to terminal data collection, reporting, and / or access, or the request information for terminal data collection, reporting, and / or access, includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Access network information, wireless access technology information, and / or frequency-related information corresponding to the terminal data collected, reported, and / or made public; Session information used for collecting, reporting, and / or opening the terminal data; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal data collection, reporting, and / or the release of first QoS information. A data acquisition method, applied to an access network device, the method comprising: Receive terminal data collection, reporting, and / or open related configuration information from the first or second functional entity; The terminal sends configuration information related to data collection, reporting, and / or opening to the terminal, which is used by the terminal to collect data. The method according to claim 29, wherein, The configuration information related to terminal data collection, reporting, and / or access includes one or more of the following: The types of data or uses of data collected, reported, and / or made public at the terminal; Terminal data collection, reporting, and / or access to regional and / or time information; Terminal data acquisition, reporting, and / or open data format, accuracy, latency, period, frequency, and / or triggering condition information; Access network information, wireless access technology information, and / or frequency-related information corresponding to the terminal data collected, reported, and / or made public; Session information used for collecting, reporting, and / or opening the terminal data; Information from machine learning models or inferences using terminal data; Application or business information that uses terminal data; Terminal data collection, reporting, and / or the release of first QoS information. The method according to claim 29, wherein, The method further includes: Send the configuration information of the access network device for terminal data collection, reporting and / or access to the first functional entity or the second functional entity. A data acquisition device, applied to a terminal, the device comprising: Memory, transceiver Processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Obtain first information, which includes terminal data collection, reporting, and / or open related information; Based on the first information, determine the terminal data; Send the terminal data to the first functional entity; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device is applied to a second functional entity, the device comprising: Memory, transceiver Processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Determine or obtain first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data; Send the first information to the terminal; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device is applied to a first functional entity, the device comprising: Memory, transceiver, processor: Memory is used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Determine or obtain first information, which includes terminal data collection, reporting, and / or open related information; Receive terminal data; Based on the first information, the terminal data is sent to the third functional entity; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device, applied to access network equipment, the device comprising: Memory, transceiver Processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Receive terminal data collection, reporting, and / or open related configuration information from the first or second functional entity; The terminal sends configuration information related to data collection, reporting, and / or opening to the terminal, which is used by the terminal to collect data. A data acquisition device, applied to a terminal, the device comprising: The first acquisition unit is used to acquire first information, which includes terminal data collection, reporting and / or open related information. The first determining unit is configured to determine terminal data based on the first information; The first sending unit is used to send the terminal data to the first functional entity; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device is applied to a second functional entity, the device comprising: A first processing unit is configured to determine or acquire first information, the first information including terminal data collection, reporting and / or opening related information, the first information being used for the collection, reporting and / or opening of the terminal data; The first sending unit is used to send the first information to the terminal; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device is applied to a first functional entity, the device comprising: The first processing unit is configured to determine or acquire first information, the first information including terminal data collection, reporting and / or open related information; The first receiving unit is used to receive terminal data; The first sending unit is configured to send the terminal data to the third functional entity based on the first information; The terminal data collection, reporting, and / or opening of related information includes one or more of the following: Terminal data collection, reporting, and / or sharing of related contractual or authorized information; Terminal data collection, reporting, and / or sharing of related policy information; Terminal data collection, reporting, and / or sharing of related configuration information; Terminal data collection, reporting, and / or open request information. A data acquisition device, applied to access network equipment, the device comprising: The first sending unit is used to send configuration information related to terminal data collection, reporting, and / or opening to the terminal. The configuration information related to terminal data collection, reporting, and / or opening is used by the terminal to collect data. The configuration information related to terminal data collection, reporting, and / or opening includes configuration information related to terminal data collection, reporting, and / or opening received from the first functional entity or the second functional entity. A processor-readable storage medium storing a program for causing the processor to perform the method as described in any one of claims 1 to 31.

Images