Information transmission methods, device, chip, and storage medium

WO2026232551A1PCT designated stage Publication Date: 2026-11-12GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094018
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

Smart Images

  • Figure CN2025094018_12112026_PF_FP_ABST
    Figure CN2025094018_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Information transmission methods, a device, a chip, and a storage medium, which relate to the technical field of communications. An information transmission method comprises: a first core network element sending data collection application information to a terminal device, the data collection application information comprising the mapping relationship between one or more sets of identification information and data collection configurations (610). A terminal device acquires data collection application information, the data collection application information comprising the mapping relationship between one or more sets of identification information and data collection configurations, whereby a data-collection-related message (e.g., including a request / response and a subscription / notification, etc.) transmitted between nodes comprises only identification information, and each node can learn a corresponding data collection configuration by referring to the data collection application information, thereby eliminating the need to include in the data-collection-related message data collection configurations having a relatively large data volume. Compared with the data collection configurations, the identification information has a much smaller data volume, thereby helping to save network and air interface resources consumed during interaction between nodes.
Need to check novelty before this filing date? Find Prior Art

Description

Information transmission methods, devices, chips and storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to an information transmission method, device, chip, and storage medium. Background Technology

[0002] Currently, the 3GPP (3rd Generation Partnership Project) standard is discussing how to collect data from terminal devices into the core network, so that the core network or third-party servers can use the collected data to train AI (Artificial Intelligence) models and deploy the AI ​​models on terminal devices, thereby realizing the aforementioned use cases such as AI+CSI (Channel State Information) feedback, AI+beam management, and AI+positioning technology.

[0003] To achieve the above functions, the terminal device needs to collect data. Before collecting data, the terminal device needs to know what data needs to be collected in the measurement; therefore, the data collection requirements need to be clearly stated in the data collection request. If the data collection request directly indicates the data collection requirements by including the data collection configuration, the amount of data in the data collection configuration may be large due to the variety of data to be collected, which will result in the consumption of a lot of network and air interface resources. Summary of the Invention

[0004] This application provides an information transmission method, device, chip, and storage medium. The technical solutions provided by this application are as follows.

[0005] According to one aspect of the embodiments of this application, an information transmission method is provided, the method being executed by a terminal device, the method comprising:

[0006] The system receives data collection application information sent by the first core network element, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0007] According to one aspect of the embodiments of this application, an information transmission method is provided, the method being executed by a first core network element, the method comprising:

[0008] Send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0009] In some embodiments, the method further includes:

[0010] Send a subscription request to the UDR (Unified Data Repository), the subscription request being used to request subscription to the data collection application information;

[0011] Receive the data collection application information sent by the UDR.

[0012] In some embodiments, the data collection application information is transmitted via CP (Control Plane) signaling; or, the data collection application information is transmitted via UP (User Plane) or a data connection.

[0013] According to one aspect of the embodiments of this application, an information transmission method is provided, the method being executed by an Application Function (AF), the method comprising:

[0014] Send data collection application information to the UDR, the data collection application information including a mapping relationship between one or more sets of identification information and data collection configuration.

[0015] According to one aspect of the embodiments of this application, an information transmission method is provided, the method being executed by a UDR, the method comprising:

[0016] Receive data collection application information sent by AF, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration;

[0017] Store the data collection application information.

[0018] In some embodiments, the method further includes:

[0019] Receive a subscription request sent by a first core network element, the subscription request being used to request subscription to the data collection application information;

[0020] Based on the subscription request, the data collection application information is sent to the first core network element.

[0021] According to one aspect of the embodiments of this application, an information transmission method is provided, the method being executed by a second core network element, the method comprising:

[0022] The terminal device receives a first request message, which is used to trigger the establishment of an association between the terminal device and a first core network element.

[0023] The agent establishes an association between the terminal device and the first core network element;

[0024] The system receives data collection application information from the first core network element and forwards it to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0025] According to one aspect of the embodiments of this application, a terminal device is provided, the terminal device comprising:

[0026] The receiving module is used to receive data collection application information sent by the first core network element. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0027] According to one aspect of the embodiments of this application, a first core network element is provided, the first core network element comprising:

[0028] The sending module is used to send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0029] In some embodiments, the first core network element further includes: a receiving module;

[0030] The sending module is also configured to send a subscription request to the UDR, the subscription request being used to request subscription to the data collection application information;

[0031] The receiving module is used to receive the data collection application information sent by the UDR.

[0032] In some embodiments, the sending module is configured to send the data collection application information to the terminal device via CP signaling, or to send the data collection application information to the terminal device via UP or a data connection.

[0033] According to one aspect of the embodiments of this application, an AF is provided, the AF comprising:

[0034] The sending module is used to send data collection application information to the UDR. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0035] According to one aspect of the embodiments of this application, a UDR is provided, the UDR comprising:

[0036] The receiving module is used to receive data collection application information sent by AF, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration;

[0037] The processing module is used to store the data collection application information.

[0038] In some embodiments, the UDR further includes a transmission module;

[0039] The receiving module is also configured to receive a subscription request sent by the first core network element, the subscription request being used to request subscription to the data collection application information;

[0040] The sending module is used to send the data collection application information to the first core network element based on the subscription request.

[0041] According to one aspect of the embodiments of this application, a second core network element is provided, the second core network element comprising:

[0042] The receiving module is used to receive a first request message sent by the terminal device, wherein the first request message is used to trigger the establishment of an association between the terminal device and the first core network element;

[0043] The sending module is used to proxy the terminal device to establish an association with the first core network element;

[0044] The receiving module is also used to receive data collection application information from the first core network element;

[0045] The sending module is further configured to forward the data collection application information to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0046] According to one aspect of the embodiments of this application, a communication device is provided, the communication device including a processor and a memory, the memory storing a computer program, the processor executing the computer program to cause the communication device to perform the method on the terminal device side, or the method on the first core network element side, or the method on the AF side, or the method on the UDR side, or the method on the second core network element side.

[0047] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, the storage medium storing a computer program, the computer program being executed by a processor to implement the method on the terminal device side, or the method on the first core network element side, or the method on the AF side, or the method on the UDR side, or the method on the second core network element side.

[0048] According to one aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is running, are used to implement the above-mentioned terminal device side method, or implement the above-mentioned first core network element side method, or implement the above-mentioned AF side method, or implement the above-mentioned UDR side method, or implement the above-mentioned second core network element side method.

[0049] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, wherein a processor reads from the computer-readable storage medium and executes the computer instructions to implement the method on the terminal device side, or the method on the first core network element side, or the method on the AF side, or the method on the UDR side, or the method on the second core network element side.

[0050] The technical solutions provided in this application embodiment may have the following beneficial effects:

[0051] Data collection application information is obtained through terminal devices. This information includes a mapping relationship between one or more sets of identification information and data collection configuration. This allows data collection-related messages (such as requests / responses and subscriptions / notifications) to contain only identification information when transmitted between nodes. Each node can obtain the corresponding data collection configuration by consulting the data collection application information. There is no need to include the large amount of data collection configuration in the data collection-related messages. Compared with the data collection configuration, the identification information has a much smaller data volume, which helps to save network and air interface resources used when interacting between nodes. Attached Figure Description

[0052] Figure 1 is a schematic diagram of a network architecture provided in one embodiment of this application;

[0053] Figure 2 is an architecture diagram of a 5G system provided in an embodiment of this application;

[0054] Figure 3 is an architecture diagram of a 5G system provided in another embodiment of this application;

[0055] Figure 4 is a schematic diagram of the interaction between NWDAF and other network elements (NF) provided in an embodiment of this application;

[0056] Figure 5 is a schematic diagram of data transmission via DCCF according to an embodiment of this application;

[0057] Figure 6 is a flowchart of an information transmission method provided in an embodiment of this application;

[0058] Figure 7 is a schematic diagram of the transmission of identification information corresponding to the data collection configuration between nodes according to an embodiment of this application;

[0059] Figure 8 is a flowchart illustrating the association between a terminal device and a first core network element according to an embodiment of this application;

[0060] Figure 9 is a flowchart of a terminal device requesting data collection application information from a first core network element according to an embodiment of this application;

[0061] Figure 10 is a flowchart of data collection performed by an AF-triggered terminal device according to an embodiment of this application;

[0062] Figure 11 is a flowchart of how data collection application information is generated by AF and provided to UDR according to an embodiment of this application;

[0063] Figure 12 is a flowchart illustrating how to synchronize changes between nodes when data collection application information changes, according to an embodiment of this application.

[0064] Figure 13 is a flowchart of data collection for application information via CP signaling transmission according to an embodiment of this application;

[0065] Figure 14 is a flowchart of data collection and application information transmission via UP or data connection according to an embodiment of this application;

[0066] Figure 15 is a block diagram of a terminal device provided in an embodiment of this application;

[0067] Figure 16 is a block diagram of a first core network element provided in an embodiment of this application;

[0068] Figure 17 is a block diagram of an AF provided in one embodiment of this application;

[0069] Figure 18 is a block diagram of a UDR provided in one embodiment of this application;

[0070] Figure 19 is a block diagram of a second core network element provided in one embodiment of this application;

[0071] Figure 20 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0072] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0073] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0074] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) systems, B5G (Beyound 5G) systems, 6th-Generation (6G) systems, or other communication systems.

[0075] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0076] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0077] The communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.

[0078] The embodiments of this application can be applied to both non-terrestrial networks (NTN) and terrestrial networks (TN). NTN typically uses satellite communication to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and other NTN systems may be included in the future.

[0079] Please refer to Figure 1, which shows a schematic diagram of a network architecture 100 provided in one embodiment of this application. The network architecture 100 may include: a terminal device 10, an access network device 20, and a core network element 30.

[0080] Terminal device 10 can refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. In some embodiments, terminal device 10 can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in 5GS (5th Generation System), or terminal device in the future evolved PLMN (Public Land Mobile Network), etc., and this application embodiment is not limited to these. For ease of description, the devices mentioned above are collectively referred to as terminal devices. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. Terminal equipment can also be simply referred to as terminal or UE, the meaning of which can be understood by those skilled in the art.

[0081] Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned devices providing wireless communication functionality to terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between terminal device 10 and core network element 30 through access network device 20. For example, in an LTE (Long Term Evolution) system, access network device 20 may be one or more eNodeBs in an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, access network device 20 may be one or more gNBs in a RAN (Radio Access Network). In the embodiments of this application, unless otherwise specified, the term "network device" refers to access network device 20, such as a base station.

[0082] Core network element 30 is a network element deployed in the core network. Its main functions are to provide user connectivity, manage users, and bear services, serving as an interface to external networks. For example, core network elements in a 5G NR system may include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, and SMF (Session Management Function) entities.

[0083] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via some air interface technology, such as the NG interface in a 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via some air interface technology, such as the Uu interface.

[0084] The "5G NR system" in this application embodiment can also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this application embodiment can be applied to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (such as B5G (Beyond 5G, a fifth-generation mobile communication technology) systems, 6G systems (6th Generation System, a sixth-generation mobile communication system)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems. This application does not limit these applications.

[0085] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0086] Please refer to Figure 2, which illustrates a schematic diagram of the system architecture of the 5GS (5th Generation System) provided in this embodiment of the application. As shown in Figure 2, the system architecture 200 may include: UE (i.e., the "terminal device" described above), (R)AN (Radio Access Network), Core, and DN (Data Network). The UE, (R)AN, and Core are the main components of the architecture, logically divided into user plane and control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In the figure, the NG2 reference point is located between the (R)AN control plane and the Core control plane, and the NG3 reference point is located between the (R)AN user plane and the Core user plane. Additionally, the NG6 reference point may be located between the Core user plane and the data network.

[0087] UE (User Equipment): Serves as the entry point for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to users, and receives user input. The UE will employ next-generation air interface technology to establish signal and data connections with the (R)AN, thereby transmitting control signals and service data to the mobile network.

[0088] (R)AN: Similar to a base station in a traditional network, it is deployed close to the UE to provide network access for authorized users in a specific area. It can also transmit user data using transmission tunnels of different quality depending on the user's level and service requirements. (R)AN can manage its own resources, make reasonable use of them, and provide access services to the UE on demand, forwarding control signals and user data between the UE and the core network.

[0089] Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing UE with functions such as session management, mobility management, policy management, and security authentication. When the UE attaches, it provides network access authentication; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates network resources for the UE; when the UE is idle, it provides a fast recovery mechanism; when the UE detaches, it releases network resources for the UE; when the UE has service data, it provides data routing functions, such as forwarding uplink data to the DN; or receiving downlink data from the UE from the DN, forwarding it to the (R)AN, and then sending it to the UE.

[0090] DN: This is the data network that provides services to users. Generally, the client is located at the UE (User Equipment), and the server is located in the data network. The data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as for configuring IMS (IP Multimedia Core Network Subsystem) services.

[0091] One of the most important features of the 5G network architecture is its service-oriented architecture. Core network elements (service providers) can offer specific services, which are then accessed by other network elements (consumers) through predefined APIs (Application Programming Interfaces). Figure 3 is a detailed diagram of the architecture defined based on Figure 2. The UE connects to the access network equipment via the Access Stratum (AS) layer, exchanging access stratum messages and radio data. The UE connects to the AMF via the Non-Access Stratum (NAS) layer, exchanging NAS messages. The AMF is responsible for managing UE mobility, while the SMF is responsible for UE session management. In addition to managing mobile terminal mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF (Policy Control Function) is responsible for formulating policies related to UE mobility management, session management, and charging. The UPF (User Plane Function) connects to the access network equipment and external data networks for data transmission.

[0092] In addition, the 5G network has added NWDAF (Network Data Analytics Function) to the core network. It can collect data from various network elements and network management systems in the core network to perform big data statistics, analysis or intelligent data analysis, and obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control UE access based on the data analysis results.

[0093] Specifically, the NWDAF network element can collect data from other network elements for big data analysis. To this end, as shown in sub-graphs (a) and (b) of Figure 4, the interfaces between the NWDAF and other network elements (NFs) are defined. These include NFs requesting analysis results from the NWDAF (identified by an Analytic ID), and the NWDAF sending analysis results to the NFs.

[0094] Data delivery via the DCCF (Data Collection Coordination Function) is illustrated in Figure 5. Each piece of data received from a data source NF is sent to the DCCF, which then distributes it to all consumer / notification endpoints specified by the data consumer or determined by the DCCF. Each data consumer can specify multiple notification endpoints in its requests to the DCCF; these endpoints may include the requesting data consumer, the ADRF (Analysis Data Storage Function), or other NFs. The DCCF can also select the ADRF or other notification endpoints based on its configuration. The DCCF supports data formatting and processing for each consumer / notification endpoint to ensure that the data format conforms to the data request received from each consumer NF.

[0095] When the DCCF determines the data collection status of a data request:

[0096] If the requested data has not yet been collected from the data source, DCCF will send a new subscription / request to the data source and specify the notification target as DCCF;

[0097] If the requested data portion is covered by an existing subscription to the data source, DCCF will send a request to the existing data source to modify the subscription, and / or create a new subscription for the new requested data that cannot be provided by the current data source;

[0098] If the requested data has already been collected from the data source, DCCF determines that there is no need to create or modify a subscription to the data source.

[0099] When DCCF receives a notification, it processes it according to the formatting and processing instructions for each consumer and notification endpoint. Subsequently, DCCF sends the notification to the consumer and notification endpoint via the Ndccf_DataManagement service.

[0100] Current wireless communication systems offer greater flexibility than their predecessors, emphasizing broad applicability to various scenarios and full utilization of limited resources. However, most current systems are still based on theoretical modeling of real-world communication environments or simple parameter selection. The gains from this approach are gradually diminishing in dynamic and complex communication environments. Therefore, it is necessary to adopt new methods and approaches, combining them with traditional wireless communication theories and systems, to find alternative solutions, break through performance bottlenecks, and further improve the performance of wireless communication systems.

[0101] Based on this, we began researching AI (Artificial Intelligence) / ML (Machine Learning) enabled wireless air interface technologies, with the main research use cases including:

[0102] AI+CSI (Channel State Information) feedback: AI / ML technology is used to compress and decompress CSI, reducing air interface transmission overhead and improving the accuracy of CSI feedback information;

[0103] AI+beam management: Utilizes AI / ML technology to predict beam information in the time and spatial domains, reducing measurement overhead and latency, and improving the accuracy of beam selection;

[0104] AI+ Positioning Technology: Utilizes AI / ML technology to predict UE location information, improving the accuracy of UE location information in NLOS (Non-Line of Sight) scenarios.

[0105] Building upon this foundation, further research is needed on the lifecycle management of AI models, including model generation, deployment, transmission, monitoring, and updates. Current standard research and discussions suggest the option of generating models on the core network or third-party servers. In this scenario, the core network or third-party servers need to collect UE measurement data for model training.

[0106] Currently, the 3GPP (3rd Generation Partnership Project) standard is discussing how to collect UE data into the core network, so that the core network or third-party servers can use the collected data to train AI models and deploy the AI ​​models on the UE, thereby realizing the aforementioned use cases such as AI+CSI feedback, AI+beam management, and AI+positioning technology, to improve the performance of CSI feedback, beam management, and positioning.

[0107] CSI feedback and beam management are fundamental functions of RAN nodes (e.g., gNBs). Applying AI to CSI feedback and beam management primarily involves RAN nodes and / or UEs performing inference on relevant AI models. However, AI model training still needs to be completed in the core network or application layer. Therefore, the core network needs to collect data from RAN nodes and / or UEs for model training, and then send the trained model back to the RAN nodes and / or UEs for AI model inference. To generate the data required for AI model training, the RAN node or UE first triggers an over-the-air measurement process to obtain the necessary data, and then triggers the core network's data collection process.

[0108] Before collecting data, the RAN node or UE needs to know what data needs to be collected in the measurement; therefore, the data collection requirements need to be clearly stated in the data collection request. However, existing solutions do not provide such a description.

[0109] If a data collection request carries a data collection requirement, the data collection request may consume a lot of network and air interface resources when interacting between the UE, RAN node, core network element and AF, due to the large variety of data collection types and the potentially large amount of data. Transmission via CP (Control Plane) may easily cause signaling storms; transmission via UP (User Plane) or data connection may result in packet loss and latency when network resources are limited.

[0110] Please refer to Figure 6, which shows a flowchart of an information transmission method provided in one embodiment of this application. This method can be applied to the network architectures shown in Figures 1 to 3. The method may include the following step 610.

[0111] Step 610: The first core network element sends data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0112] The terminal equipment receives data collection and application information sent by the first core network element.

[0113] Data collection configuration is used to clarify data collection needs, thereby optimizing resource utilization and improving AI model training efficiency. For example, a data collection configuration can configure one or more of the following related parameters: the type of data collected, the data collection period, the start and end times of data collection, the triggering conditions for data collection, and the purpose of data collection; this application does not limit these parameters. It should be understood that a data collection configuration may include one or more of the above-mentioned related parameters. Different data collection configurations may have one or more parameters that differ.

[0114] In this embodiment, there is a mapping relationship between data collection configurations and identification information. The identification information corresponding to the data collection configuration is used to uniquely identify the data collection configuration. Different data collection configurations have different identification information, thereby distinguishing different data collection configurations through the identification information. The identification information can also be called ID (Identifier), index, number, or other names, which are not limited in this application.

[0115] In some embodiments, a data collection configuration corresponds to an identification information, and a data collection configuration and its corresponding identification information constitute a set of mapping relationships. The data collection application information may include only one set of mapping relationships or multiple sets of mapping relationships. Optionally, the data collection application information includes multiple sets of mapping relationships, where any two sets of mapping relationships contain different data collection configurations (e.g., one or more parameters mentioned above are different); and the identification information contained in any two sets of mapping relationships is also different, thereby enabling the differentiation of different data collection configurations through different identification information.

[0116] In some embodiments, data collection application information is generated and / or modified by the AF. The AF may provide the generated and / or modified data collection application information to a first core network element, or the first core network element may obtain the data collection application information generated and / or modified by the AF. This process is described in the following embodiments.

[0117] In some embodiments, the data collection application information can also be understood as a mapping table between identification information and data collection configuration. Alternatively, the data collection application information includes a mapping table between identification information and data collection configuration.

[0118] In some embodiments, the first core network element is a policy control network element or a data collection network element. Exemplarily, the measurement control network element is a PCF. Exemplarily, the data collection network element is a DCF (Data Collection Function). The policy control network element is a core component of the core network control plane, primarily responsible for the formulation, execution, and dynamic adjustment of policy rules to achieve optimized allocation of network resources and QoS (Quality of Service) assurance. The functions of the PCF include: policy decision-making and implementation, QoS assurance and resource optimization, charging control, and user behavior monitoring. In the 5G network architecture, the policy control network element is called PCF. With the development and evolution of communication technologies, the policy control network element may also be called by other names, which this application does not limit. The data collection network element is a dedicated function designed for scenarios such as AI / ML model training. Its core responsibility is to coordinate and manage the data collection process. The functions of the data collection network element include: data collection policy configuration, data subscription and dynamic synchronization, cross-entity coordination, and transmission optimization. In the 5G network architecture, the data collection network element is called DCF. With the development and evolution of communication technology, the data collection network element may also be called other names, and this application does not limit it.

[0119] In some embodiments, data collection application information is transmitted via CP signaling. CP is responsible for transmitting network signaling and serves as the communication channel for control functions such as device access, session management, and mobility management.

[0120] In some embodiments, data collection application information is transmitted via a UP or data connection. The UP is responsible for transmitting user data traffic (such as audio and video, internet data, etc.) and directly carries the business content.

[0121] As shown in Figure 7, to prevent excessive network and air interface resources from being consumed when data collection requests interact between terminal devices, RAN nodes, first core network elements (e.g., DCF), and AF, the AF is responsible for creating and maintaining data collection application information and configuring it for all data collection-related entities, including terminal devices, RAN nodes, and first core network elements (e.g., DCF), before requesting data collection. Data collection-related messages (including requests / responses and subscriptions / notifications) only contain identification information when transmitted between terminal devices, RAN nodes, first core network elements (e.g., DCF), and AF. Each node obtains the corresponding data collection configuration by consulting the data collection application information.

[0122] In some embodiments, data collection application information is generated by the AF and provided to the UDR, which then saves the data collection application information as application data (Data Set). This process is described in the following embodiments.

[0123] For example, as shown in Table 1 below, an example of data collection application information is given.

[0124] Table 1

[0125] Table 1 above shows the mapping relationships between three sets of identification information and data collection configurations. The first set of mapping relationships includes: identification information 1, corresponding to specific configuration parameters for CSI feedback in the data collection configuration. The second set of mapping relationships includes: identification information 2, corresponding to specific configuration parameters for beam management in the data collection configuration. The third set of mapping relationships includes: identification information 3, corresponding to specific configuration parameters for positioning in the data collection configuration.

[0126] The application scope in Table 1 above refers to the range of terminal devices using this data collection configuration. This application scope can be indicated by any of the following: S-NSSAI (Single-Network Slice Selection Assistance Information) and DNN (Data Network Name); the terminal device's group identifier; SUPI (Subscription Permanent Identifier); any identification or indication information of the terminal device; or PLMN ID (Public Land Mobile Network Identity). For example, assuming the application scope corresponding to identifier information 1 is indicated by S-NSSAI and DNN, it means that the data collection configuration corresponding to identifier information 1 applies to terminal devices in the network indicated by S-NSSAI and DNN. As another example, assuming the application scope corresponding to identifier information 1 is indicated by any identification or indication information of the terminal device, it means that the data collection configuration corresponding to identifier information 1 applies to the terminal devices indicated by any identification or indication information of that terminal device.

[0127] Furthermore, the data collection application information shown in Table 1 above is merely an example for ease of understanding. This application embodiment does not limit the number of data collection configurations, the specific configuration parameters of the data collection configurations, or the division method of the data collection configurations contained in the data collection application information.

[0128] Furthermore, in this embodiment, the number of bits occupied by the identification information is not limited, and can be determined based on the number of data collection configurations. For example, 1 bit can distinguish up to 2 different data collection configurations, 2 bits can distinguish up to 4 different data collection configurations, and 3 bits can distinguish up to 8 different data collection configurations.

[0129] The technical solution provided in this application embodiment obtains data collection application information through a terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration. This allows data collection-related messages (such as requests / responses and subscriptions / notifications) to contain only identification information when transmitted between nodes. Each node can obtain the corresponding data collection configuration by consulting the data collection application information. There is no need to include the large amount of data collection configuration in the data collection-related messages. Compared with the data collection configuration, the amount of data is much smaller, which helps to save network and air interface resources occupied when interacting between nodes.

[0130] The following describes how terminal devices acquire data to collect application information.

[0131] Method 1: Terminal devices obtain data collection and application information by establishing an association with the first core network element.

[0132] Figure 8 shows a flowchart illustrating the process of establishing an association between a terminal device and a first core network element. This process may include one or more of the following steps 810 to 830.

[0133] Step 810: The terminal device sends a first request message, which is used to trigger the establishment of an association between the terminal device and the first core network element.

[0134] Optionally, the terminal device sends a first request message to a second core network element, and the second core network element receives the first request message sent by the terminal device. After receiving the first request message, the second core network element proxies the establishment of an association between the terminal device and the first core network element. The above-mentioned triggering of the establishment of an association between the terminal device and the first core network element can be understood as the terminal device triggering the second core network element to proxies the establishment of an association between the terminal device and the first core network element.

[0135] Optionally, the second core network element is an access management network element or a routing agent network element.

[0136] For example, the access management network element is called AMF. The access management network element has functions such as access control and mobility management, session management message forwarding, security anchor function, and multi-access support. The access management network element is the first control point for terminal equipment accessing the network, responsible for handling terminal equipment registration, authentication, access permission control, and mobility management (such as handover and location updates). The access management network element acts as a signaling relay node between the terminal equipment and the session management network element (such as SMF), responsible for forwarding session-related NAS messages (such as PDU session establishment requests) to ensure correct routing of control plane signaling. In addition, the access management network element integrates the Security Anchor Function (SEAF), responsible for generating and managing session keys to ensure the encryption and integrity of communication. Besides 3GPP access, the access management network element also supports the management of non-3GPP access (such as Wi-Fi), including authentication and mobility state maintenance. In the 5G network architecture, the access management network element is called AMF. With the development and evolution of communication technologies, the access management network element may also be called by other names, which this application does not limit.

[0137] For example, the routing proxy network element functions as a routing proxy. The routing proxy network element has functions such as signaling routing and load balancing, service-based architecture support, and dynamic scaling adaptation. The routing proxy network element (usually implemented by the access management network element or an independent network element) is responsible for dynamically routing requests from terminal devices to appropriate core network functional units. For example, during the terminal device registration process, the routing proxy selects the corresponding policy control network element or session management network element to establish an association based on the terminal device's capabilities, network load, and policies. Under the 5G service-based architecture (SBA), the routing proxy implements service calls between different network functions (NFs) through the HTTP / 2 protocol, such as forwarding terminal device requests to UDM (Unified Data Management) or PCF. When the core network dynamically scales up or down, the routing proxy adjusts the routing path through mechanisms such as consistent hashing to ensure that requests are distributed to the correct instance, reducing data migration overhead. With the development and evolution of communication technologies, the routing proxy network element may also be called by other names, which this application does not limit.

[0138] Optionally, the first request message is a registration request message, which is used to trigger the establishment of an association between the terminal device and the first core network element. After receiving the registration request message, the second core network element acts as an intermediary to establish an association between the terminal device and the first core network element. That is, the terminal device does not directly establish an association with the first core network element, but rather achieves the association through the second core network element as an intermediary.

[0139] Optionally, the first request message includes capability information, which indicates whether the terminal device has data collection capabilities. For example, the capability information indicates that the terminal device has data collection capabilities. Here, data collection capability refers to the ability to collect data, such as the ability to collect data based on a data collection configuration.

[0140] Step 820: The second core network element proxy terminal device establishes an association with the first core network element.

[0141] Optionally, the second core network element sends a third request message to the first core network element, and the first core network element receives the third request message. The third request message is used to request the establishment of an association between the terminal device and the first core network element. Optionally, the third request message can also be called an association establishment request. It should be understood that since the second core network element acts as an intermediary for the terminal device to establish an association with the first core network element, the terminal device and the first core network element do not directly establish an association; rather, the association is established between the second core network element and the first core network element.

[0142] Optionally, the third request message includes capability information, which indicates whether the terminal device has data collection capabilities. Optionally, the capability information included in the third request message is the same as the capability information included in the first request message. For example, if the capability information included in the first request message indicates that the terminal device has data collection capabilities, then the capability information included in the third request message also indicates that the terminal device has data collection capabilities.

[0143] Optionally, the association between the terminal device and the first core network element is established under one or more of the following conditions: the capability information in the first request message indicates that the terminal device has the ability to collect data; or the terminal device obtains the permission to collect data from the subscription information management network element.

[0144] The subscription information management network element is primarily responsible for the storage, management, and distribution of user and service policy data. This element can be a UDM (User Depository Management) or a UDR (User Depository Controller). The UDM mainly stores users' permanent subscription information, such as QoS parameters, session-level restrictions, and service permissions. The UDR extends the functionality of the traditional UDM, supporting more flexible application data management, such as data collection policies and policy distribution.

[0145] Optionally, the second core network element sends an authorization request to the subscription information management network element. This authorization request authorizes whether the terminal device has the permission to collect data. For example, after receiving the first request message, if the capability information included in the first request message indicates that the terminal device has the capability to collect data, the second core network element sends an authorization request to the subscription information management network element. The subscription information management network element then sends an authorization response back to the second core network element. This authorization response can indicate that the terminal device has the permission to collect data, or it can indicate that the terminal device does not have the permission to collect data. If the authorization response indicates that the terminal device has the permission to collect data, the conditions for establishing an association are met. The second core network element then sends a third request message to the first core network element, acting as an agent to establish an association between the terminal device and the first core network element.

[0146] Step 830: The second core network element receives data collection application information from the first core network element and forwards it to the terminal device. The data collection application information is carried in a container.

[0147] After the second core network element proxies the terminal device and establishes an association with the first core network element, the second core network element can receive data collection application information from the first core network element. Optionally, the data collection application information is carried in a container. After receiving the data collection application information carried in the container, the second core network element directly forwards it to the terminal device without processing. Accordingly, the terminal device obtains the data collection application information from the container.

[0148] For example, the first core network element is PCF. After receiving the third request message, if the capability information in the third request message indicates that the terminal device has data collection capability, then PCF subscribes to data collection application information from UDR. PCF sends the data collection application information to the second core network element based on the data collection application information received from UDR, so as to forward the data collection application information to the terminal device through the second core network element.

[0149] For example, the first core network element is DCF. DCF can provide data collection application information to terminal devices through CP signaling, or through UP or data connection.

[0150] Through the above method 1, the terminal device can obtain data collection and application information by establishing a connection with the first core network element.

[0151] Method 2: The terminal device directly requests data collection and application information from the first core network element.

[0152] Figure 9 illustrates a flowchart of a terminal device requesting data collection application information from a first core network element. This process may include one or more steps from steps 910 to 920.

[0153] Step 910: The terminal device sends a second request message to the first core network element. The second request message is used to request data collection application information from the first core network element.

[0154] The first core network element receives the second request message sent by the terminal device.

[0155] Optionally, the terminal device forwards the second request message to the first core network element through the second core network element. For example, the terminal device sends the second request message to the second core network element, and the second core network element forwards the second request message to the first core network element.

[0156] Optionally, the second request message includes capability information, which indicates whether the terminal device has data collection capabilities. For example, the capability information indicates that the terminal device has data collection capabilities.

[0157] Optionally, the second request message may be transmitted via CP signaling, or via UP or a data connection.

[0158] Step 920: The first core network element sends data collection application information to the terminal device.

[0159] The terminal equipment receives data collection and application information sent by the first core network element.

[0160] Optionally, the first core network element forwards data collection application information to the terminal device through the second core network element. For example, the first core network element sends data collection application information to the second core network element, and the second core network element forwards the data collection application information to the terminal device.

[0161] Optionally, after receiving the second request message, the first core network element sends data collection application information to the terminal device.

[0162] Optionally, after receiving the second request message, if the capability information in the second request message indicates that the terminal device has data collection capability, the first core network element sends data collection application information to the terminal device.

[0163] Optionally, data collection application information can be transmitted via CP signaling, or via UP or data connection.

[0164] Through method 2 described above, the terminal device can directly request data collection and application information from the first core network element.

[0165] The following describes the process by which the AF triggers the terminal device to collect data. As shown in Figure 10, this process may include one or more of the following steps 1010 to 1020.

[0166] Step 1010: AF sends a data collection request, which includes first identification information. The data collection request is used to request the terminal device to collect measurement data based on the data collection configuration corresponding to the first identification information.

[0167] The terminal device receives a data collection request. Optionally, the data collection request sent by the AF passes through the first core network element (e.g., PCF or DCF) and the RAN node in sequence before being sent to the terminal device.

[0168] In this embodiment of the application, since each data collection configuration has corresponding identification information, the data collection request only needs to include the identification information corresponding to the data collection configuration, without including the data collection configuration itself, thereby saving the amount of information in the data collection request and saving network and air interface resources.

[0169] The first identification information can be any identification information corresponding to a data collection configuration, indicating that AF requires the terminal device to collect measurement data based on the data collection configuration corresponding to the first identification information.

[0170] Step 1020: The terminal device collects measurement data based on the data collection configuration corresponding to the first identification information.

[0171] Optionally, the terminal device determines the data collection configuration corresponding to the first identification information based on the data collection application information.

[0172] Based on the above description, since the terminal device has already acquired and stored data collection application information, which includes a mapping relationship between one or more sets of identification information and data collection configuration, after receiving a data collection request, the terminal device finds the data collection configuration corresponding to the first identification information carried in the data collection request from the above mapping relationship.

[0173] After determining the data collection configuration corresponding to the first identification information, the terminal device collects measurement data based on the data collection configuration.

[0174] Using the above method, the data collection request only needs to include the identification information corresponding to the data collection configuration, without needing to include the data collection configuration itself, thereby saving the amount of information in the data collection request and saving network and air interface resources.

[0175] As described above, data collection application information can be generated by the AF and provided to the UDR for storage. The following is a description of this process. As shown in Figure 11, this process may include one or more of the following steps 1110 to 1120.

[0176] Step 1110: The AF sends data collection application information to the UDR. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0177] After generating the data collection application information, the AF can provide the generated data collection application information to the UDR, and the UDR will receive the data collection application information sent by the AF.

[0178] Step 1120: UDR stores data to collect application information.

[0179] The UDR stores the received data collection application information locally as application data. The first core network element can obtain this data collection application information from the UDR and provide it to the terminal device. For example, the first core network element subscribes to data collection application information from the UDR, and the UDR notifies the first core network element to retrieve any new or changed data collection application information.

[0180] Figure 11 above illustrates the process by which data collection application information is generated by the AF and provided to the UDR for storage. Subsequently, the AF may change the data collection application information, and this change will also be synchronized to the UDR, the first core network element, and the terminal equipment. The following is an explanation of this change and synchronization process through Figure 12.

[0181] In some embodiments, as shown in FIG12, a flowchart is illustrated for synchronizing changes between nodes when data collection application information changes. This process may include one or more of the following steps 1210 to 1250.

[0182] Step 1210: In the event of a change in the data collection application information, the AF sends a second change synchronization information to the UDR. The second change synchronization information is used to synchronize the change in the data collection application information to the UDR.

[0183] UDR receives the second change synchronization information sent by AF.

[0184] Optionally, changes may include one or more of the following: adding, updating, or deleting.

[0185] After the AF adds data collection application information, or adds one or more sets of identification information and mapping relationships between data collection configurations, it can send second change synchronization information to the UDR. This second change synchronization information is used to synchronize the added data collection application information, or the added one or more sets of identification information and mapping relationships between data collection configurations, to the UDR. Here, "adding" refers to adding mapping relationships between identification information and data collection configurations that were not previously present. Optionally, in the case of additions, the second change synchronization information may include the added data collection application information, or the added one or more sets of identification information and mapping relationships between data collection configurations.

[0186] After the AF has updated data collection application information, or updates the mapping relationship between one or more sets of identification information and data collection configuration, it can send second change synchronization information to the UDR. The second change synchronization information is used to synchronize the updated data collection application information, or the updated mapping relationship between one or more sets of identification information and data collection configuration, to the UDR. Here, "updating" refers to updating existing identification information or data collection configuration, such as modifying the data collection configuration corresponding to a certain identification information, or modifying the identification information corresponding to a certain data collection configuration. Optionally, in the case of updates, the second change synchronization information may include the updated data collection application information, or the updated mapping relationship between one or more sets of identification information and data collection configuration.

[0187] After the AF (Application Function) has deleted data collection application information, or deleted the mapping relationship between one or more sets of identification information and data collection configuration, it can send second change synchronization information to the UDR (User DR). The second change synchronization information is used to synchronize the deleted data collection application information, or the deleted mapping relationship between one or more sets of identification information and data collection configuration, to the UDR. Here, deletion refers to removing the previously existing mapping relationship between one or more sets of identification information and data collection configuration. Optionally, in the case of deletion, the second change synchronization information may include the identification information corresponding to the data collection configuration to be deleted.

[0188] Optionally, the second change synchronization information may also include an application identifier corresponding to the data collection application, which is used to distinguish different applications.

[0189] Step 1220: The UDR modifies the data collection application information stored in the UDR according to the second change synchronization information.

[0190] Based on the second change synchronization information, the UDR performs change operations such as adding, updating, and deleting on the data collection application information stored in the UDR, thereby maintaining the consistency between the data collection application information stored in the UDR and the data collection application information stored on the AF side.

[0191] Step 1230: The UDR sends a notification message to the first core network element. The notification message is used to indicate that the data collection application information stored in the UDR has changed.

[0192] The first core network element receives notification information sent by the UDR. When the data collection application information stored in the UDR changes, the UDR will also synchronize the change to the first core network element.

[0193] Optionally, the first core network element subscribes to data collection application information from the UDR. The UDR notifies the first core network element to retrieve any new or changed data collection application information. The first core network element sends a subscription request to the UDR, and the UDR receives the subscription request. The subscription request is used to request subscription to data collection application information.

[0194] Step 1240: The first core network element sends first change synchronization information to the terminal device. The first change synchronization information is used to synchronize changes in data collection application information to the terminal device.

[0195] The terminal device receives the first change synchronization information sent by the first core network element. The first change synchronization information is the same as or similar to the second change synchronization information, as detailed above, and will not be repeated here.

[0196] Optionally, the second core network element receives the first change synchronization information from the first core network element and forwards it to the terminal device. The first change synchronization information is carried in a container.

[0197] Step 1250: The terminal device modifies the data collection application information stored in the terminal device according to the first change synchronization information.

[0198] Based on the first change synchronization information, the terminal device performs change operations such as adding, updating, and deleting on the data collection application information stored in the terminal device, thereby maintaining the consistency between the data collection application information stored in the terminal device and the data collection application information stored on the UDR and AF sides.

[0199] The above method enables the synchronization of changes to data collection and application information across nodes, which helps improve flexibility.

[0200] Please refer to Figure 13, which shows a flowchart of data collection for application information via CP signaling transmission. This process may include one or more steps from 1301 to 1314. In the embodiment shown in Figure 13, the first core network element is DCF and the second core network element is AMF.

[0201] Step 1301: DCF sends a subscription request to UDR. The subscription request is used to request changes to the data collection application information.

[0202] DCF subscribes to UDR for any modifications to the data collection application information by calling the Nudr_DM_Subscribe service operation. Optionally, the subscription request includes one or more of the following parameters: AF service parameter configuration information (such as AF service identifier, service type), SUPI (User Permanent Identifier), Data Set: set to "Application Data", Data Subset: set to "Service specific information".

[0203] UDR serves as a unified data repository, responsible for managing network slices, policies, and service-related data. DCF synchronizes data collection needs in real time through a subscription mechanism, avoiding redundant queries.

[0204] Step 1302, AF initiates a data collection request.

[0205] Create request: AF calls the Nnef_ServiceParameter_Create service operation. The request must include data collection application information, which includes one or more sets of identification information and the mapping relationship between data collection configuration.

[0206] Update / delete requests: AF calls Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete, carrying the Transaction Reference ID obtained from the creation response. The Transaction Reference ID is used to uniquely identify the request and ensure the atomicity of the operation.

[0207] Request content: Includes data collection application information (such as a mapping table between identification information and data collection configuration).

[0208] Step 1303, NEF Authorization and Data Mapping.

[0209] The NEF (Network Exposure Function) authorizes AF requests and performs the following mappings:

[0210] 1. AF Service Identifier Mapping: Converts AF service identifiers into a locally configured DNN and S-NSSAI combination.

[0211] 2. External application identifier mapping: Convert external application IDs into application identifiers known within the core network.

[0212] Creation / Update Operation: NEF stores the AF request information in the "Application Data" of the UDR and associates it with the transaction reference ID.

[0213] Deletion operation: NEF removes the corresponding data collection configuration from the UDR.

[0214] Step 1304, NEF responds to AF.

[0215] For a creation request, the response message includes a transaction reference ID for use in subsequent operations.

[0216] Step 1305: The UDR sends a notification message to the DCF, which indicates that the data collection application information stored in the UDR has changed.

[0217] UDR notifies DCF of any modifications to the data collection application information by calling Nudr_DM_Notify.

[0218] Step 1306: Based on the notification information, the DCF modifies the data collection application information stored in the DCF.

[0219] DCF stores, modifies, or deletes data collection application information based on the content received in Nudr_DM_Notify.

[0220] Step 1307: The terminal device sends a registration request message to the AMF.

[0221] The registration request message includes capability information, indicating that the terminal device has the ability to collect data. The registration request message is one possible implementation of the first request message mentioned in the above embodiments.

[0222] Step 1308: If the terminal device indicates in the registration request message that it has the ability to collect data, the AMF checks with the UDM whether the terminal device is authorized to perform data collection.

[0223] Step 1309: If the terminal device is authorized to perform data collection, the AMF initiates an association establishment request to the DCF.

[0224] Step 1310: Upon any modification to the data collection application information received from the UDR, the DCF encapsulates the updated data collection application information into a container and transmits it to the terminal device via the AMF.

[0225] Step 1311: If the terminal device is in an idle state, the AMF initiates the paging process by sending a paging message. Once the paging message is received, the terminal device will initiate a UE-triggered service request process.

[0226] Step 1312: If the terminal device is in a connected state, the AMF will pass through the container containing updated data collection application information received from the DCF to the terminal device.

[0227] Step 1312 is the step in which the AMF sends the first change synchronization information to the terminal device. The first change synchronization information may include a container encapsulating updated data collection application information.

[0228] Step 1313: The terminal device updates the data collection application information provided by the DCF and sends the results to the AMF.

[0229] Step 1314: AMF forwards the terminal device's response to DCF.

[0230] In this embodiment, the execution order of steps 1307 and subsequent steps with steps 1301-1306 is not limited and they can occur in parallel. Furthermore, some steps in the process shown in steps 1301-1314 are optional. For example, if the terminal device is in a connected state, step 1311 need not be executed. For example, if the protocol stipulates that the UDR needs to send data collection application information to the DCF, the DCF does not need to execute step 1301 to send a subscription request to the UDR. As another example, after updating the data collection application information, the terminal device does not need to send the result to the AMF, and the AMF does not need to execute step 1314.

[0231] Please refer to Figure 14, which shows a flowchart of data collection for application information via UP or data connection. This process may include one or more steps from 1401 to 1411. In the embodiment shown in Figure 14, the first core network element is DCF and the second core network element is AMF.

[0232] Step 1401: DCF sends a subscription request to UDR. The subscription request is used to request subscription data collection application information.

[0233] Step 1402, AF initiates a data collection request.

[0234] Step 1403, NEF Authorization and Data Mapping.

[0235] Step 1404, NEF responds to AF.

[0236] Step 1405: The UDR sends a notification message to the DCF, which indicates that the data collection application information stored in the UDR has changed.

[0237] Step 1406: Based on the notification information, the DCF modifies the data collection application information stored in the DCF.

[0238] Step 1407: The terminal device sends a registration request message to the AMF.

[0239] Step 1408: If the terminal device indicates in the registration request message that it has the ability to collect data, the AMF checks with the UDM whether the terminal device is authorized to perform data collection.

[0240] Step 1409: If the terminal device is authorized to perform data collection, the AMF initiates an association establishment request to the DCF.

[0241] Steps 1401 to 1409 are the same as steps 1301 to 1309, and will not be repeated here.

[0242] Step 1410: If the DCF decides to provide data collection application information to the terminal device via UP or data connection, the DCF may initiate the establishment of UP or data connection to the terminal device (if no connection exists between the two).

[0243] Step 1411: DCF provides data collection application information to the terminal device via UP or data connection.

[0244] In this embodiment, the execution order of steps 1407 and subsequent steps with steps 1401-1406 is not limited and they can occur in parallel. Furthermore, some steps in the process shown in steps 1401-1411 are optional. For example, if the protocol stipulates that the UDR needs to send data collection application information to the DCF, the DCF may not need to execute step 1401 to send a subscription request to the UDR.

[0245] In the above method embodiments, the technical solution of this application is described and explained only from the perspective of the interaction between nodes such as terminal device, first core network element, AF, UDR, and second core network element. The steps executed by the terminal device can be implemented independently as an information transmission method on the terminal device side. The steps executed by the first core network element can be implemented independently as an information transmission method on the first core network element side. The steps executed by the AF can be implemented independently as an information transmission method on the AF side. The steps executed by the UDR can be implemented independently as an information transmission method on the UDR side. The steps executed by the second core network element can be implemented independently as an information transmission method on the second core network element side.

[0246] Furthermore, the various embodiments of this application can be combined in any way to form new embodiments, all of which are within the protection scope of this application.

[0247] The following are embodiments of the device described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the embodiments of the device described in this application, please refer to the embodiments of the method described in this application.

[0248] Please refer to Figure 15, which shows a block diagram of a terminal device provided in one embodiment of this application. This terminal device has the function of performing the information transmission method described above on the terminal device side. As shown in Figure 15, the terminal device 1500 may include a receiving module 1510.

[0249] The receiving module 1510 is used to receive data collection application information sent by the first core network element. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0250] In some embodiments, as shown in FIG15, the terminal device 1500 further includes: a sending module 1520, configured to send a first request message, the first request message being used to trigger the establishment of an association between the terminal device and the first core network element.

[0251] In some embodiments, the first request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

[0252] In some embodiments, the association between the terminal device and the first core network element is established under one or more of the following conditions: the capability information in the first request message indicates that the terminal device has data collection capabilities; or the terminal device obtains data collection permissions from the subscription information management network element.

[0253] In some embodiments, as shown in FIG15, the terminal device 1500 further includes: a sending module 1520, configured to send a second request message to the first core network element, the second request message being used to request the data collection application information to be obtained from the first core network element.

[0254] In some embodiments, the second request message is transmitted via CP signaling; or, the second request message is transmitted via UP or a data connection.

[0255] In some embodiments, the data collection application information is transmitted via CP signaling; or, the data collection application information is transmitted via UP or a data connection.

[0256] In some embodiments, as shown in FIG15, the terminal device 1500 further includes a processing module 1530.

[0257] The receiving module 1510 is further configured to receive first change synchronization information, which is used to synchronize changes in the data collection application information to the terminal device.

[0258] The processing module 1530 is used to modify the stored data collection application information according to the first change synchronization information.

[0259] In some embodiments, as shown in FIG15, the terminal device 1500 further includes a processing module 1530.

[0260] The receiving module 1510 is also used to receive a data collection request, the data collection request including first identification information.

[0261] The processing module 1530 is used to collect measurement data based on the data collection configuration corresponding to the first identification information.

[0262] Please refer to Figure 16, which shows a block diagram of a first core network element provided in an embodiment of this application. This first core network element has the function of executing the information transmission method described above for the first core network element side. As shown in Figure 16, the first core network element 1600 may include a transmitting module 1610.

[0263] The sending module 1610 is used to send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0264] In some embodiments, as shown in FIG16, the first core network element 1600 further includes a receiving module 1620, configured to receive a third request message, the third request message being used to request the establishment of an association between the terminal device and the first core network element.

[0265] In some embodiments, the third request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

[0266] In some embodiments, the association between the terminal device and the first core network element is established under one or more of the following conditions: the terminal device has data collection capabilities; and the terminal device obtains data collection permissions from the subscription information management network element.

[0267] In some embodiments, as shown in FIG16, the first core network element 1600 further includes: a receiving module 1620, configured to receive a second request message sent by the terminal device, the second request message being used to request to obtain the data collection application information from the first core network element.

[0268] In some embodiments, the second request message is transmitted via CP signaling; or, the second request message is transmitted via UP or a data connection.

[0269] In some embodiments, the data collection application information is transmitted via CP signaling; or, the data collection application information is transmitted via UP or data connection.

[0270] In some embodiments, the first core network element is a PCF or a DCF.

[0271] In some embodiments, as shown in FIG16, the first core network element 1600 further includes: a receiving module 1620, configured to receive notification information sent by the unified data repository UDR, the notification information being used to indicate that the data collection application information stored in the UDR has changed.

[0272] The sending module 1610 is further configured to send first change synchronization information to the terminal device, the first change synchronization information being used to synchronize changes in the data collection application information to the terminal device.

[0273] In some embodiments, the changes include one or more of the following: adding, updating, and deleting.

[0274] In some embodiments, the sending module 1610 is further configured to send a subscription request to the UDR, the subscription request being used to request subscription to the data collection application information.

[0275] Please refer to Figure 17, which shows a block diagram of an AF provided in one embodiment of this application. This AF has the function of performing the information transmission method described above on the AF side. As shown in Figure 17, the AF 1700 may include: a transmitting module 1710.

[0276] The sending module 1710 is used to send data collection application information to the UDR, the data collection application information including a mapping relationship between one or more sets of identification information and data collection configuration.

[0277] In some embodiments, the sending module 1710 is further configured to send second change synchronization information to the UDR when the data collection application information changes, the second change synchronization information being used to synchronize the changes in the data collection application information to the UDR.

[0278] In some embodiments, the changes include one or more of the following: adding, updating, and deleting.

[0279] In some embodiments, the sending module 1710 is further configured to send a data collection request, the data collection request including first identification information, the data collection request being used to request the terminal device to collect measurement data based on the data collection configuration corresponding to the first identification information.

[0280] Please refer to Figure 18, which shows a block diagram of a UDR provided in one embodiment of this application. This UDR has the function of performing the information transmission method described above on the UDR side. As shown in Figure 18, the UDR 1800 may include a receiving module 1810 and a processing module 1820.

[0281] The receiving module 1810 is used to receive data collection application information sent by AF, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0282] The processing module 1820 is used to store the data collection application information.

[0283] In some embodiments, the receiving module 1810 is further configured to receive second change synchronization information sent by the AF, the second change synchronization information being used to synchronize the change of the data collection application information to the UDR when the data collection application information changes.

[0284] The processing module 1820 is further configured to modify the stored data collection application information according to the second change synchronization information.

[0285] In some embodiments, as shown in FIG18, the UDR 1800 further includes: a sending module 1830, configured to send notification information to a first core network element, the notification information being used to indicate that the data collection application information stored in the UDR has changed.

[0286] In some embodiments, the changes include one or more of the following: adding, updating, and deleting.

[0287] In some embodiments, the receiving module 1810 is further configured to receive a subscription request sent by a first core network element, the subscription request being used to request subscription to the data collection application information.

[0288] Please refer to Figure 19, which shows a block diagram of a second core network element provided in an embodiment of this application. This second core network element has the function of performing the information transmission method described above for the second core network element side. As shown in Figure 19, the second core network element 1900 may include a receiving module 1910 and a transmitting module 1920.

[0289] The receiving module 1910 is used to receive a first request message sent by the terminal device, the first request message being used to trigger the establishment of an association between the terminal device and the first core network element.

[0290] The sending module 1920 is used to proxy the terminal device to establish an association with the first core network element.

[0291] The receiving module 1910 is also used to receive data collection application information from the first core network element.

[0292] The sending module 1920 is further configured to forward the data collection application information to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0293] In some embodiments, the first request message includes capability information, which is used to indicate that the terminal device has data collection capabilities.

[0294] In some embodiments, the sending module 1920 is further configured to send an authorization request to the subscription information management network element, the authorization request being used to authorize whether the terminal device has the permission to collect data.

[0295] In some embodiments, the association between the terminal device and the first core network element is established under one or more of the following conditions: the first request message includes information that the terminal device has data collection capabilities; and the terminal device obtains data collection permissions from the subscription information management network element.

[0296] In some embodiments, the sending module 1920 is configured to send a third request message to the first core network element, the third request message being used to request the establishment of an association between the terminal device and the first core network element.

[0297] In some embodiments, the receiving module 1910 is further configured to receive first change synchronization information from the first core network element and forward it to the terminal device. The first change synchronization information is carried in a container and is used to synchronize the changes of the data collection application information to the terminal device.

[0298] In some embodiments, the first core network element is a PCF or DCF, and / or the second core network element is an AMF or a routing proxy function.

[0299] It should be noted that the above embodiments only illustrate the division of the above functional modules when implementing the functions of the device. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0300] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here. For details not described in detail in the apparatus embodiments, please refer to the above method embodiments.

[0301] Please refer to Figure 20, which shows a schematic diagram of the structure of a communication device provided in one embodiment of this application. Optionally, the communication device can be any one of the following devices: terminal device, first core network element, AF, UDR, second core network element, etc. The communication device 2000 may include: processor 2001, transceiver 2002, and memory 2003. The processor 2001 is used to implement various processing functions of the communication device 2000, such as generating information to be sent, processing received information, controlling transmission and / or reception, etc., and is used to implement the functions of the aforementioned processing module. The transceiver 2002 is used to implement transmission and / or reception functions, and is used to implement the functions of the aforementioned receiving module and / or transmitting module.

[0302] The processor 2001 includes one or more processing cores, and the processor 2001 executes various functional applications and information processing by running software programs and modules.

[0303] The transceiver 2002 may include a receiver and a transmitter, for example, the receiver and transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0304] The memory 2003 can be connected to the processor 2001 and the transceiver 2002.

[0305] The memory 2003 can be used to store a computer program executed by the processor, and the processor 2001 is used to execute the computer program so that the communication device 2000 performs the various steps in the above method embodiments.

[0306] In some embodiments, the communication device 2000 is a terminal device, and the transceiver 2002 is used to receive data collection application information sent by the first core network element. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0307] In some embodiments, the communication device 2000 is a first core network element, and the transceiver 2002 is used to send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0308] In some embodiments, the communication device 2000 is an AF, and the transceiver 2002 is used to send data collection application information to the UDR. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0309] In some embodiments, the communication device 2000 is a UDR, the transceiver 2002 is used to receive data collection application information sent by the AF, the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration; the processor 2001 is used to store the data collection application information.

[0310] In some embodiments, the communication device 2000 is a second core network element, and the transceiver 2002 is used to receive a first request message sent by a terminal device. The first request message is used to trigger the establishment of an association between the terminal device and the first core network element; to act as an agent for the terminal device to establish an association with the first core network element; to receive data collection application information from the first core network element and forward it to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

[0311] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0312] Furthermore, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, statically accessible memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0313] This application embodiment also provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the methods described above on the terminal device side, or on the first core network element side, or on the AF side, or on the UDR side, or on the second core network element side. In some embodiments, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0314] This application embodiment also provides a chip, the chip including programmable logic circuits and / or program instructions, which, when the chip is running, are used to implement the above-mentioned terminal device side method, or implement the above-mentioned first core network element side method, or implement the above-mentioned AF side method, or implement the above-mentioned UDR side method, or implement the above-mentioned second core network element side method.

[0315] This application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the method on the terminal device side, or the method on the first core network element side, or the method on the AF side, or the method on the UDR side, or the method on the second core network element side.

[0316] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0317] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0318] In some embodiments of this application, "predefined" can be achieved by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0319] In some embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as BLE protocol, Wi-Fi protocol, and related protocols applied in future communication systems. This application does not limit the scope of these protocols.

[0320] In some embodiments of this application, the names of the various devices or network elements involved may become other names as communication technology develops and evolves. This application does not limit the names of the various devices or network elements, but any scheme that performs the steps of the various devices or network elements involved in this application, or realizes the functions of the various devices or network elements involved in this application, is within the protection scope of this application.

[0321] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0322] In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0323] Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0324] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0325] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An information transmission method, characterized in that, The method is executed by a terminal device, and the method includes: The system receives data collection application information sent by the first core network element, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

2. The method according to claim 1, characterized in that, The method further includes: A first request message is sent, which is used to trigger the establishment of an association between the terminal device and the first core network element.

3. The method according to claim 2, characterized in that, The first request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

4. The method according to claim 2 or 3, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The capability information in the first request message indicates that the terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

5. The method according to claim 1, characterized in that, The method further includes: A second request message is sent to the first core network element, the second request message being used to request the data collection application information to be obtained from the first core network element.

6. The method according to claim 5, characterized in that, The second request message is transmitted via control plane CP signaling; or, The second request message is transmitted via the user plane UP or a data connection.

7. The method according to any one of claims 1 to 6, characterized in that, The data collection application information is transmitted via CP signaling; or... The data collection application information is transmitted via UP or data connection.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receive first change synchronization information, the first change synchronization information being used to synchronize changes to the data collection application information to the terminal device; Based on the first change synchronization information, the stored data collection application information is modified.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive a data collection request, wherein the data collection request includes first identification information; Based on the data collection configuration corresponding to the first identification information, measurement data is collected.

10. An information transmission method, characterized in that, The method is executed by a first core network element, and the method includes: Send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

11. The method according to claim 10, characterized in that, The method further includes: A third request message is received, which is used to request the establishment of an association between the terminal device and the first core network element.

12. The method according to claim 11, characterized in that, The third request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

13. The method according to claim 11 or 12, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

14. The method according to claim 10, characterized in that, The method further includes: The terminal device receives a second request message, which requests to obtain the data collection application information from the first core network element.

15. The method according to claim 14, characterized in that, The second request message is transmitted via control plane CP signaling; or, The second request message is transmitted via the user plane UP or a data connection.

16. The method according to any one of claims 10 to 15, characterized in that, The data collection application information is transmitted via CP signaling; or... The data collection application information is transmitted via UP or data connection.

17. The method according to any one of claims 10 to 16, characterized in that, The first core network element is either a policy control function (PCF) or a data collection function (DCF).

18. The method according to any one of claims 10 to 17, characterized in that, The method further includes: Receive notification information sent by the Unified Data Repository (UDR), the notification information being used to indicate that the data collection application information stored in the UDR has changed; Send first change synchronization information to the terminal device, the first change synchronization information being used to synchronize changes to the data collection application information to the terminal device.

19. The method according to claim 18, characterized in that, The changes include one or more of the following: addition, update, and deletion.

20. The method according to any one of claims 10 to 19, characterized in that, The method further includes: Send a subscription request to the UDR, the subscription request being used to request subscription to the data collection application information.

21. An information transmission method, characterized in that, The method is executed by application function AF, and the method includes: Send data collection application information to the Unified Data Repository (UDR), which includes a mapping relationship between one or more sets of identification information and data collection configuration.

22. The method according to claim 21, characterized in that, The method further includes: If the data collection application information changes, a second change synchronization information is sent to the UDR. The second change synchronization information is used to synchronize the change of the data collection application information to the UDR.

23. The method according to claim 22, characterized in that, The changes include one or more of the following: addition, update, and deletion.

24. The method according to any one of claims 21 to 23, characterized in that, The method further includes: Send a data collection request, the data collection request including first identification information, the data collection request being used to request the terminal device to collect measurement data based on the data collection configuration corresponding to the first identification information.

25. An information transmission method, characterized in that, The method is executed by the Unified Data Repository (UDR), and the method includes: Receive data collection application information sent by the application function AF, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration; Store the data collection application information.

26. The method according to claim 25, characterized in that, The method further includes: The system receives second change synchronization information sent by the AF, which is used to synchronize the changes in the data collection application information to the UDR when the data collection application information changes. Based on the second change synchronization information, the stored data collection application information is modified.

27. The method according to claim 25 or 26, characterized in that, The method further includes: A notification message is sent to the first core network element, the notification message being used to indicate that the data collection application information stored in the UDR has changed.

28. The method according to claim 26 or 27, characterized in that, The changes include one or more of the following: addition, update, and deletion.

29. The method according to any one of claims 25 to 28, characterized in that, The method further includes: The system receives a subscription request sent by a first core network element, the subscription request being used to request subscription to the data collection application information.

30. An information transmission method, characterized in that, The method is executed by a second core network element, and the method includes: The terminal device receives a first request message, which is used to trigger the establishment of an association between the terminal device and a first core network element. The agent establishes an association between the terminal device and the first core network element; The system receives data collection application information from the first core network element and forwards it to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

31. The method according to claim 30, characterized in that, The first request message includes capability information, which is used to indicate that the terminal device has data collection capabilities.

32. The method according to claim 30 or 31, characterized in that, The method further includes: An authorization request is sent to the contract information management network element, the authorization request being used to authorize whether the terminal device has the permission to collect data.

33. The method according to any one of claims 30 to 32, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The first request message includes information that the terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

34. The method according to any one of claims 30 to 33, characterized in that, The process of establishing an association between the proxy terminal device and the first core network element includes: A third request message is sent to the first core network element, the third request message being used to request the establishment of an association between the terminal device and the first core network element.

35. The method according to any one of claims 30 to 34, characterized in that, The method further includes: The first change synchronization information is received from the first core network element and forwarded to the terminal device. The first change synchronization information is carried in a container and is used to synchronize the changes of the data collection application information to the terminal device.

36. The method according to any one of claims 30 to 35, characterized in that, The first core network element is a policy control function (PCF) or a data collection function (DCF), and / or the second core network element is an access and mobility management function (AMF) or a routing proxy function.

37. A terminal device, characterized in that, The terminal device includes: The receiving module is used to receive data collection application information sent by the first core network element. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

38. The terminal device according to claim 37, characterized in that, The terminal device also includes: The sending module is used to send a first request message, which is used to trigger the establishment of an association between the terminal device and the first core network element.

39. The terminal device according to claim 38, characterized in that, The first request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

40. The terminal device according to claim 38 or 39, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The capability information in the first request message indicates that the terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

41. The terminal device according to claim 37, characterized in that, The terminal device also includes: The sending module is used to send a second request message to the first core network element, the second request message being used to request the data collection application information to be obtained from the first core network element.

42. The terminal device according to claim 41, characterized in that, The second request message is transmitted via control plane CP signaling; or, The second request message is transmitted via the user plane UP or a data connection.

43. The terminal device according to any one of claims 37 to 42, characterized in that, The data collection application information is transmitted via CP signaling; or... The data collection application information is transmitted via UP or data connection.

44. The terminal device according to any one of claims 37 to 43, characterized in that, The terminal device further includes: a processing module; The receiving module is further configured to receive first change synchronization information, which is used to synchronize the changes of the data collection application information to the terminal device. The processing module is used to modify the stored data collection application information according to the first change synchronization information.

45. The terminal device according to any one of claims 37 to 44, characterized in that, The terminal device further includes: a processing module; The receiving module is further configured to receive a data collection request, wherein the data collection request includes first identification information; The processing module is used to collect measurement data based on the data collection configuration corresponding to the first identification information.

46. ​​A first core network element, characterized in that, The first core network element includes: The sending module is used to send data collection application information to the terminal device. The data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration.

47. The first core network element according to claim 46, characterized in that, The first core network element also includes: The receiving module is used to receive a third request message, which is used to request the establishment of an association between the terminal device and the first core network element.

48. The first core network element according to claim 47, characterized in that, The third request message includes capability information, which is used to indicate whether the terminal device has data collection capabilities.

49. The first core network element according to claim 47 or 48, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

50. The first core network element according to claim 46, characterized in that, The first core network element also includes: The receiving module is used to receive a second request message sent by the terminal device, the second request message being used to request the data collection application information to be obtained from the first core network element.

51. The first core network element according to claim 50, characterized in that, The second request message is transmitted via control plane CP signaling; or, The second request message is transmitted via the user plane UP or a data connection.

52. The first core network element according to any one of claims 46 to 51, characterized in that, The data collection application information is transmitted via CP signaling; or... The data collection application information is transmitted via UP or data connection.

53. The first core network element according to any one of claims 46 to 52, characterized in that, The first core network element is either a policy control function (PCF) or a data collection function (DCF).

54. The first core network element according to any one of claims 46 to 53, characterized in that, The first core network element also includes: A receiving module is used to receive notification information sent by a unified data repository (UDR), the notification information being used to indicate that the data collection application information stored in the UDR has changed; The sending module is further configured to send first change synchronization information to the terminal device, the first change synchronization information being used to synchronize changes in the data collection application information to the terminal device.

55. The first core network element according to claim 54, characterized in that, The changes include one or more of the following: addition, update, and deletion.

56. The first core network element according to any one of claims 46 to 54, characterized in that, The sending module is also used to send a subscription request to the UDR, the subscription request being used to request subscription to the data collection application information.

57. An application function AF, characterized in that, The AF includes: The sending module is used to send data collection application information to the Unified Data Repository (UDR), which includes a mapping relationship between one or more sets of identification information and data collection configuration.

58. The AF according to claim 57, characterized in that, The sending module is further configured to send a second change synchronization information to the UDR when the data collection application information changes, wherein the second change synchronization information is used to synchronize the change of the data collection application information to the UDR.

59. The AF according to claim 58, characterized in that, The changes include one or more of the following: addition, update, and deletion.

60. The AF according to any one of claims 57 to 59, characterized in that, The sending module is further configured to send a data collection request, the data collection request including first identification information, the data collection request being used to request the terminal device to collect measurement data based on the data collection configuration corresponding to the first identification information.

61. A unified data repository (UDR), characterized in that, The UDR includes: The receiving module is used to receive data collection application information sent by the application function AF, wherein the data collection application information includes a mapping relationship between one or more sets of identification information and data collection configuration; The processing module is used to store the data collection application information.

62. The UDR according to claim 61, characterized in that, The receiving module is further configured to receive second change synchronization information sent by the AF, wherein the second change synchronization information is used to synchronize the change of the data collection application information to the UDR when the data collection application information changes; The processing module is further configured to modify the stored data collection application information according to the second change synchronization information.

63. The UDR according to claim 61 or 62, characterized in that, The UDR also includes: The sending module is used to send notification information to the first core network element, the notification information being used to indicate that the data collection application information stored in the UDR has changed.

64. The UDR according to claim 62 or 63, characterized in that, The changes include one or more of the following: addition, update, and deletion.

65. The UDR according to any one of claims 61 to 64, characterized in that, The receiving module is also configured to receive a subscription request sent by the first core network element, the subscription request being used to request subscription to the data collection application information.

66. A second core network element, characterized in that, The second core network elements include: The receiving module is used to receive a first request message sent by the terminal device, wherein the first request message is used to trigger the establishment of an association between the terminal device and the first core network element; The sending module is used to proxy the terminal device to establish an association with the first core network element; The receiving module is also used to receive data collection application information from the first core network element; The sending module is further configured to forward the data collection application information to the terminal device. The data collection application information is carried in a container and includes a mapping relationship between one or more sets of identification information and data collection configuration.

67. The second core network element according to claim 66, characterized in that, The first request message includes capability information, which is used to indicate that the terminal device has data collection capabilities.

68. The second core network element according to claim 66 or 67, characterized in that, The sending module is also used to send an authorization request to the contract information management network element, the authorization request being used to authorize whether the terminal device has the permission to collect data.

69. The second core network element according to any one of claims 66 to 68, characterized in that, The association between the terminal device and the first core network element is established under one or more of the following conditions: The first request message includes information that the terminal device has data collection capabilities; The terminal device is authorized to collect data, as obtained from the contract information management network element.

70. The second core network element according to any one of claims 66 to 69, characterized in that, The sending module is used to send a third request message to the first core network element, the third request message being used to request the establishment of an association between the terminal device and the first core network element.

71. The second core network element according to any one of claims 66 to 70, characterized in that, The receiving module is further configured to receive first change synchronization information from the first core network element and forward it to the terminal device. The first change synchronization information is carried in a container and is used to synchronize the changes of the data collection application information to the terminal device.

72. The second core network element according to any one of claims 66 to 71, characterized in that, The first core network element is a policy control function (PCF) or a data collection function (DCF), and / or the second core network element is an access and mobility management function (AMF) or a routing proxy function.

73. A communication device, characterized in that, The communication device includes a processor, a memory, and a transceiver. The memory stores a computer program, and the processor executes the computer program to cause the communication device to perform the method as claimed in any one of claims 1 to 9, or the method as claimed in any one of claims 10 to 20, or the method as claimed in any one of claims 21 to 24, or the method as claimed in any one of claims 25 to 29, or the method as claimed in any one of claims 30 to 36.

74. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that is executed by a processor to implement the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 20, or the method as described in any one of claims 21 to 24, or the method as described in any one of claims 25 to 29, or the method as described in any one of claims 30 to 36.

75. A chip, characterized in that, The chip includes programmable logic circuitry and / or program instructions, which, when the chip is running, are used to implement the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 20, or the method as described in any one of claims 21 to 24, or the method as described in any one of claims 25 to 29, or the method as described in any one of claims 30 to 36.

76. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, which a processor reads from and executes to implement the method as claimed in any one of claims 1 to 9, or the method as claimed in any one of claims 10 to 20, or the method as claimed in any one of claims 21 to 24, or the method as claimed in any one of claims 25 to 29, or the method as claimed in any one of claims 30 to 36.