Communication method, apparatus and system

Abstract

Provided in the present application is a communication method, comprising: receiving a first message from a first data storage network element, wherein the first message comprises information of a first terminal, and the first message is used for indicating that first data associated with the first terminal is stored in the first data storage network element; and in response to the first message, associating the information of the first terminal with information of the first data storage network element. On the basis of the solution, a first network element can implement the association and collection of information of a terminal and a data storage network element, and when it is necessary for a consumer network element to acquire related data of a first terminal, a central network element can determine, on the basis of the collected information, which data storage network element the data of the first terminal is stored in, such that the consumer network element can fully acquire required data.

Description

A communication method, apparatus and system

[0001] This application claims priority to Chinese Patent Application No. 202411192294.2, filed on August 27, 2024, entitled "A Communication Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a communication method, apparatus, and system. Background Technology

[0003] The fifth-generation (5G) communication system introduces network data analytics function (NWDAF) network elements, data collection coordination function (DCCF) network elements, and analytics data repository function (ADRF) network elements. DCCF, NWDAF, and ADRF provide functions for collecting, inferring, computing, and storing network data and analytical information to support network data analysis, optimize user experience, and improve network intelligence.

[0004] With the development of mobile network technology, analyzing data generated by terminals to create terminal profiles is an important function in future communication network services. However, the mobility of terminals means that data generated by the same terminal cannot be stored on the same device, but is instead stored in a distributed manner across different network nodes.

[0005] In view of this, how consumer network elements can fully obtain the required data is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method that establishes an association between a terminal and related terminal data, so that the consumer can fully obtain the required data.

[0007] Firstly, a communication method is provided. This method can be executed by a first network element (e.g., a DCCF, ADRF, or Unified Data Repository (UDR) network element) or by a component of the first network element (e.g., a chip or circuit), and this application does not limit the execution of this method.

[0008] The method includes: receiving a first message from a first data storage network element; wherein the first message includes information about a first terminal, and the first message is used to indicate that a first data associated with the first terminal is stored in the first data storage network element; and in response to the first message, associating the information of the first terminal with the information of the first data storage network element.

[0009] Based on the above scheme, the first network element can associate the information of the first terminal with the information of the first data storage network element according to the content of the first message, thereby realizing the association and aggregation of information between the terminal and the data storage network element. When the consumer network element needs to obtain relevant data from the first terminal, the central network element can determine which data storage network elements the first terminal's data is stored in based on the aggregated information, thus enabling the consumer network element to obtain the required data completely.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, associating the information of the first terminal with the information of the first data storage network element includes: updating first list information based on the information of the first data storage network element, wherein the first list information corresponds to the information of the first terminal, and the updated first list information includes information of at least one data storage network element, wherein the at least one data storage network element is used to store data associated with the first terminal, and the data associated with the first terminal includes the first data.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes information of the first data, which includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information of the data associated with the first terminal stored in each of the at least one data storage network element.

[0012] Based on the above scheme, the information of the first terminal and the information of the first data storage network element are used to uniquely identify the first terminal and the first data storage network element, respectively. The first message and the first list information can also include more content, thereby more accurately determining which data storage network element the consumer network element needs to acquire stores, avoiding the acquisition of redundant data, and improving the efficiency of the consumer network element in fully acquiring the data.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving a second message, the second message including information of the first terminal, the second message being used to indicate obtaining information of the at least one data storage network element; and sending the first list information.

[0015] Based on the above scheme, since the second message indicates the information of the data storage network element storing all the data of the first terminal, the first network element can directly send the first list information. The consumer network element can completely obtain the information of all data storage network elements storing the data of the first terminal. Thus, the consumer network element can accurately send a request to the data storage network element to obtain the data associated with the first terminal based on the information of the first list, thereby improving the accuracy and completeness of data acquisition.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the second message further includes information about second data associated with the first terminal; the second message is used to indicate the acquisition of information about at least one second data storage network element, the at least one second data storage network element being used to store the second data; and the information about the at least one second data storage network element is sent.

[0017] Based on the above scheme, the second message can also include information about the second data, so that the first network element can more accurately determine which data storage network element the consumer network element needs to obtain is stored in, avoiding sending a message to obtain data to a data storage network element that does not store the required data, and improving the efficiency of the consumer network element in obtaining the required data completely.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is a Data Collection Coordination Function (DCCF) network element, an ADRF network element, or a Unified Database (UDR) network element.

[0019] Based on the above scheme, different network elements can be used to associate and aggregate information between terminals and data storage network elements, thereby improving the flexibility of obtaining terminal data in the network.

[0020] Secondly, a communication method is provided. This method can be executed by a first data storage network element (e.g., an ADRF network element) or by a component of the first network element (e.g., a chip or circuit), and this application does not limit the execution of this method.

[0021] The method includes: receiving first data; sending a first message to a first network element, the first message including information about the first terminal, the first message being used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the information of the first terminal includes the identifier of the first terminal, the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes information of the first data, the information of the first data includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information of the data associated with the first terminal stored in each of the at least one data storage network element.

[0023] It should be understood that the beneficial effects of the second aspect and its various implementations are similar to those of the first aspect and its various implementations, and will not be elaborated upon here.

[0024] Thirdly, a communication system is provided, including a first network element and a first data storage network element, wherein the first data storage network element receives first data; the first data storage network element sends a first message to the first network element, the first message including information of a first terminal, the first message being used to indicate that the first data associated with the first terminal is stored in the first data storage network element; the first network element responds to the first message by associating the information of the first terminal with the information of the first data storage network element.

[0025] In conjunction with the third aspect, in some implementations of the third aspect, associating the information of the first terminal with the information of the first data storage network element includes: updating first list information based on the information of the first data storage network element, wherein the first list information corresponds to the information of the first terminal, and the updated first list information includes information of at least one data storage network element, wherein the at least one data storage network element is used to store data associated with the first terminal, and the data associated with the first terminal includes the first data.

[0026] In conjunction with the third aspect, in some implementations of the third aspect, the information of the first terminal includes the identifier of the first terminal, the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes information of the first data, the information of the first data includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information of the data associated with the first terminal stored in each of the at least one data storage network element.

[0027] In conjunction with the third aspect, in some implementations of the third aspect, updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

[0028] It should be understood that the beneficial effects of the third aspect and its various implementations are similar to those of the first aspect and its various implementations, and will not be elaborated upon here.

[0029] Fourthly, a communication device is provided, which has the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect above. These modules, units, or means can be implemented in software, hardware, or a combination of both. Examples include processing units and transceiver units.

[0030] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0031] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0032] For example, if the communication device is the aforementioned first network element or a component of the first network element (e.g., a chip or circuit), then the communication device includes:

[0033] The processing unit is used to perform processing-related operations on the first network element side, such as associating the information of the first terminal with the information of the first data storage network element in response to the first message.

[0034] The transceiver unit is used to perform transceiver-related operations on the first network element side, such as receiving a first message from the first data storage network element; wherein the first message includes information about the first terminal, and the first message is used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0035] Optionally, associating the information of the first terminal with the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element, wherein the first list information corresponds to the information of the first terminal, and the updated first list information includes the information of at least one data storage network element, wherein the at least one data storage network element is used to store data associated with the first terminal, and the data associated with the first terminal includes the first data.

[0036] Optionally, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes the information of the first data, which includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

[0037] Optionally, updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

[0038] Optionally, the transceiver unit is further configured to: receive a second message, the second message including information of the first terminal, the second message being used to indicate obtaining information of the at least one data storage network element; and send the first list information.

[0039] Optionally, the second message further includes information about second data associated with the first terminal; the second message is used to indicate the acquisition of information about at least one second data storage network element, the at least one second data storage network element being used to store the second data; and to send information about the at least one second data storage network element.

[0040] Fifthly, a communication device is provided, which has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. These modules, units, or means can be implemented in software, hardware, or a combination of both. Examples include processing units and transceiver units.

[0041] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0042] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0043] For example, if the communication device is the aforementioned first ADRF network element or a component of the first ADRF network element (e.g., a chip or circuit), then the communication device includes:

[0044] The transceiver unit is used to perform transceiver-related operations on the first data storage network element side, such as receiving first data and sending a first message to the first network element, the first message including information of the first terminal, the first message being used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0045] Optionally, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes the information of the first data, which includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

[0046] A sixth aspect provides a communication device including a processor coupled to a memory for storing a computer program, the processor for running the computer program such that the communication device performs a method as described in any possible implementation of the first aspect above; or, causes the communication device to perform a method as described in any possible implementation of the second aspect above.

[0047] In a seventh aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including a method for performing any implementation of the first aspect above; or a method for performing any implementation of the second aspect above.

[0048] Eighthly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface to execute the method provided by any implementation of the first aspect above; or, executing the method provided by any implementation of the second aspect above.

[0049] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions. The processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the implementations of the first aspect above; or, to execute the method provided by any of the implementations of the second aspect above.

[0050] Ninthly, a communication system is provided, including a first network element for performing the method provided in the first aspect and a first ADRF network element for performing the method provided in the second aspect.

[0051] In a tenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to perform the method provided in any implementation of the first aspect; or to perform the method provided in any implementation of the second aspect. Attached Figure Description

[0052] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0053] Figure 2 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0054] Figure 3 is a schematic diagram of a communication method 300 applicable to an embodiment of this application.

[0055] Figure 4 is a schematic diagram of a communication method 400 applicable to an embodiment of this application.

[0056] Figure 5 is a schematic diagram of a communication method 500 applicable to an embodiment of this application.

[0057] Figure 6 is a schematic diagram of a communication method 600 applicable to an embodiment of this application.

[0058] Figure 7 is a structural schematic diagram of a communication device 700 provided in an embodiment of this application.

[0059] Figure 8 is a structural schematic diagram of a communication device 800 provided in an embodiment of this application.

[0060] Figure 9 is a schematic diagram of the structure of a chip system 900 provided in an embodiment of this application. Detailed Implementation

[0061] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0062] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) systems (or New Radio (NR) systems), beyond 5G (B5G) mobile communication systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication networks. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0063] The technical solutions provided in this application can also be applied to machine-type communication (MTC), device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks, for example, can include vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as vehicle-to-other-device (V2X), where X can represent anything. For example, V2X can include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0064] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0065] As shown in Figure 1, this network architecture takes the 5G system (5GS) as an example.

[0066] This network architecture can be divided into two parts: the access network and the core network. This network architecture may include, but is not limited to: unified data management (UDM), network exposure function (NEF), network repository function (NRF), policy control function (PCF), application function (AF), access and mobility management function (AMF), session management function (SMF), user equipment (UE), radio access network equipment, user plane function (UPF), and data network (DN). Here, DN can be the Internet; UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF are network elements in the core network. Since Figure 1 uses a 5G system as an example, this core network can be called the 5G core network (5GC or 5GCN).

[0067] The following is a brief introduction to each network element shown in Figure 1.

[0068] 1. User equipment (UE): can also be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device.

[0069] Terminal devices can be devices that provide voice / data to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, handheld computers, mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMNs), etc., and the embodiments of this application are not limited to these.

[0070] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0071] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object interconnection.

[0072] It should be noted that terminal devices and access network devices can communicate with each other using some air interface technology (such as New Radio (NR) or LTE). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE).

[0073] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0074] 2. Radio access network (RAN): This provides authorized users in a specific area with access to a communication network. Specifically, it can include wireless network equipment in the 3rd generation partnership project (3GPP) network or access points in non-3GPP networks.

[0075] The RAN manages radio resources, provides access services to user equipment, and forwards control signals and user equipment data between the user equipment and the core network. The RAN can also be understood as a base station in a traditional network.

[0076] For example, the access network device in this application embodiment can be any kind of communication device with wireless transceiver function for communicating with user equipment. This access network device includes, but is not limited to: evolved Node B (eNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WIFI) system, etc. It can also be a gNB in ​​a 5G, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0077] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that access network equipment can be one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN), and this application does not limit this.

[0078] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open-radio access network (O-RAN) system, CU can also be called an open-central unit (O-CU) (open CU); DU can also be called an open-distributed unit (O-DU) (open DU); CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0079] 3. User Plane Function (UPF) Network Element: Used for packet routing and forwarding, as well as Quality of Service (QoS) processing of user plane data. User data can access the data network (DN) through this network element. In the embodiments of this application, it can be used to implement the functions of the user plane network element.

[0080] 4. Data Network (DN): A network used to provide data transmission. Examples include carrier networks, the Internet, and third-party service networks.

[0081] 5. Authentication server function (AUSF) network element: mainly used for user authentication, etc.

[0082] 6. Access and Mobility Management Function (AMF) Network Element: Primarily used for mobility management and access management, it can be used to implement other functions of the Mobility Management Entity (MME) besides session management, such as access authorization / authentication.

[0083] 7. Session Management Function (SMF) network element: mainly used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection and management of user plane functions, policy control and charging function interface endpoints, and downlink data notification, etc.

[0084] 8. Policy control function (PCF) network element: A unified policy framework used to guide network behavior, providing policy rule information to network elements (such as AMF, SMF, etc.) or terminal devices.

[0085] 9. Network Repository Function (NRF) Network Element: Used to store network function entities and their description information, as well as support functions such as service discovery and network element entity discovery.

[0086] 10. Network Exposure Function (NEF) element: Used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0087] 11. Unified Data Management (UDM) Network Element: Used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.

[0088] 12. Application function (AF) network element: used for application data routing, accessing network open function network elements, and interacting with the policy framework for policy control, etc.

[0089] 13. Network Data Analytics Function (NWDAF) Network Elements: NWDAF can be divided into analytics logical function (AnLF) and model training logical function (MTLF). AnLF can be used to collect network data (e.g., network performance, service load in specific areas, user service experience, etc.) and user data (e.g., user connection management, mobility management, session management, access services, etc.) as input data, and to obtain analysis results based on the input data. For example, the analysis results include statistical analysis of historical data or prediction results of future data. MTLF can be used for model training and to provide trained models to AnLF.

[0090] In the embodiments of this application, the NWDAF can be a separate network element or it can be co-located with other network elements. For example, the NWDAF network element can be co-located with the AMF or with the SMF.

[0091] It should be noted that the aforementioned communication system may also include a unified data repository (UDR) network element. The UDR primarily includes the following functions: UDM (Unified Data Provider) function stores or retrieves subscription data; PCF (Policy Function) stores or retrieves policy data; and it stores or retrieves exposed data. The UDR and the network function (NF) accessing it share the same public land mobile network (PLMN), meaning they are on the same network, and the Nudr interface is an internal PLMN interface.

[0092] It should be understood that the network elements included in the communication systems listed above are merely illustrative examples and this application is not limited thereto.

[0093] In the above network architecture, the N2 interface is the interface between the RAN and AMF network elements, used for transmitting radio parameters and non-access stratum (NAS) signaling; the N3 interface is the interface between the RAN and UPF network elements, used for transmitting user plane data; the N4 interface is the interface between the SMF and UPF network elements, used for transmitting information such as service policies, tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages; and the N6 interface is the interface between the DN and UPF network elements, used for transmitting user plane data.

[0094] It should be understood that in the above network architecture, network elements can interact with each other through service-oriented interfaces. For example, the NWDAF network element can collect data generated by the terminal on the network element through service-oriented interfaces (such as Namf, Nsmf, etc.) provided by other network elements (such as AMF, SMF, etc.), and provide data analysis results (analytes), models (also known as machine learning models), and data to other network elements (such as AMF, PCF, etc.) through the Nnwdaf interface.

[0095] It should be understood that the network architecture described above in the embodiments of this application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0096] It should be noted that the names of the various network elements and interfaces in this application are merely examples. This application does not preclude the possibility of different names for the various network elements in the future, or the merging of functions between various network elements. With the evolution of technology, any device or network element capable of implementing the functions of the aforementioned network elements is within the scope of protection of this application. Secondly, the aforementioned network elements can also be referred to as entities, devices, apparatuses, or modules, etc., and this application does not specifically limit this. In this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the NWDAF network element is abbreviated as NWDAF. In this case, "NWDAF" should be understood as the NWDAF network element. The following omits descriptions of the same or similar cases.

[0097] In addition, the aforementioned network architecture may also include a data collection coordination function (DCCF) network element and an analytics data repository function (ADRF) network element, as shown in Figures 2 and 3 below. The DCCF can work in conjunction with the NWDAF to coordinate the collection and distribution of data requested by the NF consumer, reducing redundant data collection. It also has the function of preprocessing the collected data according to parameters specified by the consumer, thus achieving data collection coordination. The ADRF is used for data storage and model storage.

[0098] Figure 2 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0099] The NWDAF can request the DCCF to collect data from certain network elements through the Ndccf interface. For example, the DCCF can learn about the specific network elements serving the UE through service interfaces provided by NRF, UDM, and binding support function (BSF), and then initiate data collection requests to these network elements. After collection, the DCCF can directly feed back the data to the NWDAF, or feed it back to the NWDAF through MFAF. The ADRF can be used to store data collected by the network (e.g., NWDAF or DCCF), as well as models and analysis results trained by NWDAF, and to provide services for retrieving historical data (from various network elements) and analysis results (from NWDAF). Each network element can directly store and retrieve historical data (analysis results) through the ADRF's Nadrf interface, or store and retrieve it through DCCF or MFAF. Furthermore, the ADRF can subscribe to a data notification service from the DCCF, so that the DCCF will automatically feed back data to the ADRF after receiving data that meets the specified conditions.

[0100] It should be understood that 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.

[0101] With the development of mobile networks, future communication networks will connect to a large number of terminals of various types, generating massive amounts of data. Due to the mobility of these terminals, data generated by the same terminal will be stored in different storage devices, employing a distributed storage method (e.g., distributed data storage can be achieved through a distributed database). Distributed databases distribute data across multiple nodes, achieving data distribution and sharing through network connections. In mobile networks, data storage nodes are determined based on geographic location (AOI), and data collection network elements will store data collected in the corresponding area in data storage devices (e.g., ADRF) within that area.

[0102] Specifically, distributed databases primarily achieve data storage through data sharding. Sharding refers to dividing data into several fragments and storing these fragments on different nodes. Current mainstream data sharding methods include hash-based methods, consistent hashing methods, and range-based methods. For the specific implementation process of data sharding, please refer to relevant existing technologies; this application will not elaborate further here. Furthermore, to further improve data high availability and fault tolerance, each data fragment can be replicated multiple times and stored on multiple nodes.

[0103] Based on the standard TS23.288 data collection architecture, the data storage process can include the following:

[0104] (1) Network elements can collect data from different data sources through DCCF and store the collected data in ADRF.

[0105] (2) NWDAF can collect data from different data sources and store it locally (NWDAF).

[0106] (3) Data sources can store data in ADRF.

[0107] For methods (2) and (3), when the data stored in NWDAF / ADRF does not pass through DCCF, NWDAF / ADRF needs to register with DCCF the "service operation" and "data specification" corresponding to the data it collects.

[0108] The service operation may include the message name used to collect data (e.g., Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe). The data specification may include the event ID or analytics ID that generated the data, as well as information for filtering the data using that ID (e.g., the event ID can be an event ID, the analytics ID can be an analytics ID, and the information for filtering the data may include the type of data being targeted (e.g., the data is targeted at a group of UEs, or at a UE group identifier, or at any UE)).

[0109] Based on distributed data storage, consumers need to know the data storage node where the required data is stored in order to retrieve the data from the corresponding node. However, UE mobility means that data generated by the same terminal cannot be stored on the same device, and UE mobility is unpredictable. Therefore, consumers cannot determine the data storage device for storing UE data in advance. Furthermore, during data storage, when ADRF or NWDAF registers its collected data information with DCCF, it only registers information such as data operations and the time used for data collection. Therefore, when a consumer requests historical data at the UE granularity from DCCF, DCCF cannot determine whether the UE's historical data is stored in ADRFs or which ADRFs store it. Consequently, consumers cannot determine the storage location of the required data, and DCCF cannot send the required complete data to the consumer.

[0110] In view of this, embodiments of this application provide a communication method, apparatus, and system. The method aggregates information such as the UE to which the UE data belongs and the data type of the stored UE data through a central network element. This enables a data consuming network element to obtain information about all data storage network elements storing the UE data from the central network element that manages and stores the UE data when acquiring UE data. Then, it sends UE data requests to different data storage network elements to obtain complete UE data.

[0111] The technical solution provided in this application will be described in detail below with reference to the accompanying drawings.

[0112] Figure 3 is a schematic diagram of a communication method 300 applicable to an embodiment of this application.

[0113] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application may be a first network element (as a central network element, used to coordinate data or provide relevant information for required data, such as DCCF, ADRF or UDR), a second network element (used for data storage, such as ADRF), a third network element (as a data consumer, such as NWDAF) and a fourth network element (used for data collection coordination, such as DCCF); or, it may be a functional module among the first to fourth network elements that can call and execute the program.

[0114] Without loss of generality, the communication method provided in the embodiments of this application will be described in detail below using the interaction between the first network element, the second network element, the third network element, and the fourth network element as an example.

[0115] It should be understood that Figure 3 illustrates the steps or operations of the communication method, but these steps or operations are merely examples. Other operations or variations of the operations shown in Figure 3 may also be performed in the embodiments of this application.

[0116] Method 300 may include the following steps:

[0117] S301: The first network element receives the first message from the first data storage network element; correspondingly, the first data storage network element sends the first message to the first network element.

[0118] The first message includes information about the first terminal, and the first message is used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0119] Optionally, the first network element can be a DCCF network element, an ADRF network element, or a UDR network element, and the first data storage network element can be an ADRF network element. The specific types of the first network element and the first data storage network element are not limited in the embodiments of this application.

[0120] In this scenario, different network elements can be used to associate and aggregate information between terminals and data storage network elements, thereby improving the flexibility of obtaining terminal data in the network.

[0121] Optionally, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes the information of the first data, and the information of the first data includes the data type of the first data and / or the first time the first data was generated.

[0122] In this scenario, the information of the first terminal and the information of the first data storage network element are used to uniquely identify the first terminal and the first data storage network element, respectively. The first message and the first list information can also include more content, thereby more accurately determining which data storage network element the consumer network element needs to retrieve stores, avoiding the retrieval of redundant data, and improving the efficiency of the consumer network element in fully retrieving the data.

[0123] It should be noted that the identifier of the first terminal is a unique identifier used to identify the first terminal in the network, and the specific form of the identifier of the first terminal is not limited in the embodiments of this application. For example, in a 5G network, the identifier of the first terminal can be SUPI, and if GPSI is stored in AF, then the identifier of the first terminal can also be GPSI. In future communication networks, the identifier of the first terminal can also be other information that can identify the first terminal.

[0124] It should be understood that the identifier of the first data storage network element is a unique identifier used to identify the first data storage network element in the network. The specific form of the identifier of the first data storage network element is not limited in the embodiments of this application.

[0125] In addition, regarding the data type of the first data and the first time the first data was generated, please refer to the corresponding description of "data attribute information" in step S402 of method 400 below, which will not be repeated here.

[0126] Optionally, the first network element may also receive a third message from the second data storage network element. This application embodiment does not limit the number of data storage network elements.

[0127] For example, the third message may include information about the first terminal, and the third message is used to indicate that the second data associated with the first terminal is stored in the second data storage network element. That is, data from the same terminal can be sent to the first network element by multiple different data storage network elements. It should be understood that the second data may be the same as or different from the first data.

[0128] For example, the third message may also include information about the second terminal, indicating that third data associated with the second terminal is stored in the second data storage network element. That is, data from different terminals can be sent to the first network element by multiple different data storage network elements.

[0129] Optionally, the first network element may also receive a fourth message from the first data storage network element. In this embodiment of the application, there is no limitation on the number of messages sent from the first data storage network element to the first network element, nor on the number of terminals involved in the messages sent from the first data storage network element to the first network element.

[0130] For example, the fourth message may include information about the first terminal, and the fourth message is used to indicate that the second data associated with the first terminal is stored in the first data storage network element.

[0131] For example, the fourth message may include information about the second terminal, and the fourth message is used to indicate that the third data associated with the second terminal is stored in the first data storage network element.

[0132] S302: The first network element responds to the first message by associating the information of the first terminal with the information of the first data storage network element.

[0133] Optionally, associating the information of the first terminal with the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element, wherein the first list information corresponds to the information of the first terminal, and the updated first list information includes the information of at least one data storage network element, wherein the at least one data storage network element is used to store data associated with the first terminal, and the data associated with the first terminal includes the first data.

[0134] It should be noted that the "data associated with the first terminal" can be data generated in relevant network elements after the first terminal accesses the network. For example, the data associated with the first terminal may include the context of the first terminal, the location information of the first terminal, or statistical analysis information about the first terminal generated by the network. This application embodiment does not limit the specific content of the "data associated with the first terminal".

[0135] In this scenario, the first network element can associate the information of the first terminal with the information of the first data storage network element based on the content of the first message, thereby achieving the association and aggregation of information between the terminal and the data storage network element. When the consumer network element needs to obtain relevant data from the first terminal, the central network element can determine which data storage network elements the first terminal's data is stored in based on the aggregated information, thus enabling the consumer network element to obtain the required data completely.

[0136] Optionally, updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

[0137] It should be understood that "updating the first list information" may include at least one of the following: when there is no first list information corresponding to the information of the first terminal in the first network element, the first list information is established based on the information of the first data storage network element and the information of the first data. When there is already first list information corresponding to the information of the first terminal in the first network element, content related to the information of the first data storage network element and / or the information of the first data is added or deleted from the first list information based on the information of the first data storage network element and the information of the first data.

[0138] Optionally, the first list information may also include information about the data associated with the first terminal stored in each of the at least one data storage network element.

[0139] Optionally, after step S302, method 300 may further include step S303: the first network element receives a second message, the second message including information of the first terminal, the second message being used to indicate obtaining information of the at least one data storage network element.

[0140] Specifically, the second message can be used to instruct the storage network element to obtain information (i.e., the first list information) of all data associated with the first terminal. After receiving the second message, the first network element can determine the information to be sent as the first list information based on the second message, and then send the first list information.

[0141] In this scenario, since the second message indicates the information of the data storage network element storing all data of the first terminal, the first network element can directly send the first list information. The consumer network element can then fully obtain the information of all data storage network elements storing the data of the first terminal. Consequently, the consumer network element can accurately send a request to the data storage network element to obtain the data associated with the first terminal based on the information of the first list, thereby improving the accuracy and completeness of the data acquisition.

[0142] Optionally, the second message further includes information about second data associated with the first terminal; the second message is used to indicate the acquisition of information about at least one second data storage network element, the at least one second data storage network element being used to store the second data; and to send information about the at least one second data storage network element.

[0143] Specifically, the second message can be used to instruct the storage network element to obtain information of a portion of the data (second data) associated with the first terminal. The "data associated with the first terminal" includes the second data. After receiving the second message, the first network element can determine the information of at least one second data storage network element based on the second message and the first list information, and then send the information of the at least one second data storage network element. The first list information includes the information of the at least one second data storage network element.

[0144] In this scenario, since the second message also includes information about the second data, the first network element can more accurately determine which data storage network element the consumer network element needs to retrieve is located in, thus avoiding sending a data retrieval message to a data storage network element that does not store the required data, thereby improving the efficiency of the consumer network element in fully retrieving the required data.

[0145] Figure 4 is a schematic diagram of a communication method 400 applicable to an embodiment of this application.

[0146] S401: ADRF receive data #1.

[0147] In this context, data #1 is associated with terminal #1. Specifically, data #1 can be data generated in relevant network elements after terminal #1 accesses the network. Data #1 can be sent by terminal #1; alternatively, it can be sent by relevant network elements. This application does not limit the sending end of data #1.

[0148] Optionally, after receiving data #1, the ADRF can identify the UE ID contained in data #1, that is, the ADRF can determine the terminal device (terminal #1) corresponding to data #1 based on data #1. Here, the UE ID represents a unique identifier used to identify the UE in the network. For example, in a 5G network, the UE ID can be SUPI, and if the AF stores UE ID information as GPSI, then the UE ID can also be GPSI. In future communication networks, the UE ID can also be other information that can identify the UE.

[0149] It should be understood that if the ADRF already stores other data #2 corresponding to terminal #1, the UE ID of terminal #1, data #2, and data #1 can be associated, so that the ADRF can obtain data #1 and / or data #2 through the UE ID of terminal #1. If the ADRF does not store other data for terminal #1, the UE ID of terminal #1 and its corresponding data #1 can be added to the storage unit of the ADRF, so that the ADRF can obtain data #1 through the UE ID of terminal #1.

[0150] S402: ADRF sends message #1 to central network element #1; correspondingly, central network element #1 receives message #1 from ADRF.

[0151] Specifically, the central network element #1 can be a central DCCF, a central ADRF, or other network elements that can be used for data collection coordination or storage. The embodiments in this application are not limited in this respect.

[0152] It should be noted that method 400 may include multiple ADRFs, such as ADRF#1 and ADRF#2. In method 400, each ADRF performs similar actions, namely, associating the received data with the corresponding UE ID and registering, updating, and / or deleting it with the central network element #1. This explanation uses only one ADRF as an example and does not constitute a limitation on the number of ADRFs that may be included in this application.

[0153] It should be understood that message #1 is used to instruct the registration, update and / or deletion of terminal #1 in central network element #1, and message #1 may include the UE ID of terminal #1.

[0154] Optionally, message #1 may also include data attribute information corresponding to data #1 sent by terminal #1 to ADRF, thereby facilitating the central network element to coordinate and manage the data.

[0155] For example, the data attribute information may include at least one of the following:

[0156] (1) Data type: indicates the data type corresponding to the UE ID, that is, the data type of data #1 of terminal #1.

[0157] Specifically, the data type can be an identifier corresponding to the ADRF event "collecting information from terminal #1" (e.g., an event ID already defined in the current protocol: Loss of connectivity, UE reachability, etc.); or, the data type can also refer to a specific general type of data (e.g., the data type can include location information, communication characteristic information, or context information in the network, etc.).

[0158] (2) Period: Indicates the time when the data is generated, that is, the time when data #1 of terminal #1 is generated.

[0159] Specifically, the period can represent a specific point in time or a time interval. For example, if the ADRF only stores one piece of data from terminal #1, the corresponding period can be a point in time. If the ADRF contains multiple pieces of data from terminal #1, the corresponding period can be a time interval, representing the range of the total duration of the multiple pieces of data.

[0160] (3) Optional operation indication: indicates the registration, update or deletion of the UE ID and / or corresponding data attribute information stored in the central network element #1, that is, the specific function of message #1.

[0161] Specifically, when ADRF sends information corresponding to registration, update, and / or deletion to central network element #1, if the same message with the same name is used (i.e., one message #1 represents multiple functions in registration, update, or deletion), the specific function of message #1 can be indicated through the "Optional Indicator" field to identify its specific role. However, when ADRF sends information corresponding to registration, update, and / or deletion to central network element #1, if multiple different message indicators are used (e.g., message #1#1 can represent registration, message #1#2 can represent update, message #1#3 can represent deletion, etc.), the data attribute information may not include the optional indicator content.

[0162] It should be understood that the names of the above fields are only used to indicate the corresponding functions, and the specific names of the above fields are not limited in the embodiments of this application.

[0163] The ADRF can trigger a process of registering, updating, and / or deleting UE ID and data attribute information to the central network element #1 (i.e., step S402) after each execution of step S401; or the ADRF can trigger a process uniformly after multiple executions of step S401 (for example, step S402 can be triggered periodically according to the internal implementation), and register, update, and / or delete at least one UE ID and / or data attribute information corresponding to the data sent by each terminal in the central network element #1.

[0164] S403: Central network element #1 processes the UE's data storage attribute (UE collection data profile) information according to message #1.

[0165] The UE collection data profile can include UE information and data information. The UE information can include the UE ID corresponding to the stored data, and the data information corresponds to the UE information and can include ADRF information (e.g., ADRF ID) indicating the storage location of the corresponding UE data. The central network element #1 can determine the data type and storage location of a certain UE (the UE corresponding to the UE ID) based on the UE collection data profile. That is, the data storage attribute information of the UE can be regarded as a set of associations between the UE ID and its corresponding data information.

[0166] Optionally, the UE collection data profile can be a list that maps UE information and data information.

[0167] Specifically, if the UE ID in the UE's data storage attribute information is a UE identifier (e.g., SUPI) uniformly used in the core network, then when the UE ID of terminal #1 carried in message #1 is also SUPI, the central network element #1 can directly search for the content corresponding to the SUPI in the UE collection data profile and update the SUPI, the data attribute information corresponding to the SUPI, and / or ADRFID in the UE collection data profile. However, when the UE ID of terminal #1 carried in message #1 is a UE identifier used in the AF (e.g., GPSI), the central network element #1 can first confirm the SUPI information corresponding to the GPSI (e.g., confirm the SUPI information corresponding to the GPSI information through UDM or NEF), and then update the SUPI, the data attribute information corresponding to the SUPI, and / or ADRFID in the UE collection data profile.

[0168] It should be understood that the "processing UE data storage attribute information" may include at least one of the following: central network element #1 adds UE information and corresponding data information to the UE data storage attribute information; central network element #1 updates the data information corresponding to the UE information in the UE data storage attribute information; and central network element #1 deletes the data information corresponding to the UE information in the UE data storage attribute information.

[0169] S404: The consumer sends message #2 to the local DCCF; correspondingly, the local DCCF receives message #2 from the consumer.

[0170] The consumer can be an NWDAF or other network element; any network element or device capable of initiating a data acquisition request can act as a consumer. This application embodiment does not limit the specific type of consumer. Additionally, message #2 is used to indicate a request to acquire data from at least one UE.

[0171] Optionally, message #2 may include at least one of the following:

[0172] (1) UE ID list: can include at least one UE ID, which indicates which UE data the consumer requests.

[0173] (2) History data / time period: Corresponding to the UE ID, each UE ID in the UE ID list can correspond to at least one "history data / time period", which is used to indicate which point in time or time period the consumer needs for each UE that requests data.

[0174] (3) Sorting rule: Corresponding to the UE ID, each UE ID in the UE ID list can have its own sorting rule; multiple UE IDs in the UE ID list can also have the same sorting rule. The sorting rule indicates that the UE data obtained by DCCF is sorted in the corresponding order.

[0175] Optionally, the data can be sorted according to "historical data / time period". That is, after the local DCCF obtains all the data requested by the consumer, it can sort all the data to be obtained for each UE in ascending / descending order according to "historical data / time period".

[0176] Alternatively, the data can be sorted according to the "reception time of the local DCCF". That is, based on the time when each data is received by the local DCCF, all the data to be acquired by each UE can be sorted in ascending / descending order.

[0177] It should be noted that after receiving message #2, the local DCCF can determine which UEs' historical data needs to be retrieved based on the UE ID list and historical data / time period fields carried within it (i.e., the local DCCF can determine the data to be retrieved). When the local DCCF can directly identify the network element storing the data to be retrieved (e.g., ADRF), it can directly send information to the corresponding network element to request the data. However, the mobility of UEs makes it difficult for the local DCCF to directly identify the data storage network element that stores all UE data, thus preventing it from returning all the required UE data to the consumer. Therefore, based on this situation, after receiving message #2, the local DCCF can retrieve the UE data to be retrieved in the following way:

[0178] Method 1:

[0179] After the local DCCF obtains the data storage network element (e.g., ADRF) for storing the required data through the central network element #1, the local DCCF sends a message to the ADRF to request the data of the corresponding UE. For details, please refer to the descriptions in steps S405a-S408a.

[0180] S405a: The local DCCF sends message #3 to the central network element #1; correspondingly, the central network element #1 receives message #3 from the local DCCF.

[0181] Among them, message #3 is used to request the list of data storage network elements that store UE historical data information, that is, message #3 may include a list of UE IDs.

[0182] Optionally, message #3 may also include historical data / time period corresponding to the UE ID list, so that message #3 can be used to request data of a certain UE within a certain time period.

[0183] S406a: Central network element #1 sends message #4 to the local DCCF; correspondingly, the local DCCF receives message #4 from central network element #1.

[0184] It should be understood that after receiving message #3, central network element #1 can determine the data storage network element (ADRF) information for storing each UE's data based on the UE ID list. Specifically, central network element #1 can query the UE collection data profile based on the UE ID list to determine the data storage network element information for storing the corresponding UE's data, and return this information to the local DCCF.

[0185] Optionally, when message #3 also includes historical data / time periods corresponding to the UE ID list, the central network element #1 can determine the data storage network element information for storing data within the corresponding time period for each UE based on the UE ID list and the historical data / time period. Specifically, the central network element #1 can query the UE collection data profile based on the UE ID list and the historical data / time period to determine the data storage network element information for storing data within the corresponding time period for each UE, and return this information to the local DCCF.

[0186] It should be noted that message #4 may include only the ADRFID list; or it may include both the UE ID list and the ADRFID list, and this application does not limit this. The ADRFID list may include at least one ADRFID, and each UE ID in the UE ID list corresponds to at least one ADRFID.

[0187] S407a: The local DCCF sends message #5 to the ADRF; correspondingly, the ADRF receives message #5 from the local DCCF.

[0188] It should be understood that after receiving message #4, the local DCCF can send message #5 according to the data storage network element of the UE data indicated in message #4. Message #5 is used to indicate a request to obtain all data of the UE within the corresponding time period.

[0189] In one possible implementation, all the data required by the consumer is stored in the same ADRF, so that the local DCCF can send message #5 to the ADRF. Message #5 may include a list of UE IDs, data types, and / or periods. Here, the UE ID is the UE information corresponding to all the data required by the consumer, the data type is the data type requested by the consumer for each UE, and the period is the period (i.e., the historical data / time period in S504) requested by the consumer for each UE.

[0190] In another possible implementation, all the data to be retrieved by the consumer is stored in multiple ADRFs, so the local DCCF needs to send message #5 to each of the multiple ADRFs.

[0191] Optionally, the local DCCF sends the same message #5 to multiple ADRFs. Message #5 may include information about all the data the consumer is requesting (including a list of UE IDs, data types, or periods).

[0192] Optionally, since the data storage network elements store UE data with different periods and data types, the local DCCF can send different messages #5 to multiple ADRFs respectively.

[0193] For example, the local DCCF can send message #5#1 to ADRF#1 and message #5#2 to ADRF#2. Message #5#1 may include a UE ID list #1, data type #1, and / or period #1 corresponding to the UE data stored in ADRF#1, and message #5#2 may include a UE ID list #2, data type #2, and / or period #2 corresponding to the UE data stored in ADRF#2.

[0194] For example, period #1 could be the intersection of the "historical data / time period" carried in the consumer request (corresponding to S504) and the duration of UE data stored in ADRF #1. Period #2 could be the intersection of the "historical data / time period" carried in the consumer request and the duration of UE data stored in ADRF #2.

[0195] S408a: ADRF sends message #6 to the local DCCF; correspondingly, ADRF receives message #6 from central network element #1.

[0196] In this context, message #6 represents the UE data stored by the ADRF, which can be sent by at least one ADRF (e.g., ADRF #1 sends message #6#1, and ADRF #2 sends message #6#2). Specifically, after receiving message #5, each ADRF can determine the corresponding UE data that needs to be sent to the local DCCF based on message #5, and then return message #6 to the local DCCF.

[0197] It should be understood that message #6 may include a list of UE IDs and the data to be acquired for each UE in the list.

[0198] Method 2:

[0199] The central network element #1 sends a message to the ADRF to request data from the corresponding UE. For details, please refer to the descriptions in steps S405b-S408b.

[0200] S405b: The local DCCF sends message #3 to the central network element #1; correspondingly, the central network element #1 receives message #3 from the local DCCF.

[0201] The details of message #3 can be found in step S505a, and will not be repeated here.

[0202] S407b: Central network element #1 sends message #5 to ADRF; correspondingly, ADRF receives message #5 from central network element #1.

[0203] It should be understood that after receiving message #3, central network element #1 can determine the data storage network element (ADRF) information for storing each UE's data based on the UE ID list. Specifically, central network element #1 can query the UE collection data profile based on the UE ID list to determine the data storage network element information for storing the corresponding UE's data, and then send message #5 to the corresponding data storage network element.

[0204] Optionally, when message #3 also includes historical data / time periods corresponding to the UE ID list, the central network element #1 can determine the storage network element information for storing data within the corresponding time period for each UE based on the UE ID list and the historical data / time period. Specifically, the central network element #1 can query the UE collection data profile based on the UE ID list and the historical data / time period to determine the data storage network element information for storing data within the corresponding time period for each UE, and send message #5 to the corresponding data storage network element.

[0205] In one possible implementation, all the data required by the consumer is stored in the same ADRF, so that the central network element #1 can send message #5 to the ADRF. Message #5 may include a list of UE IDs, data types, and / or periods. Here, the UE ID is the UE information corresponding to all the data required by the consumer, the data type is the data type requested by the consumer for each UE, and the period is the period (i.e., the historical data / time period in S504) for each UE.

[0206] Optionally, message #5 may also include a local DCCF identifier (local DCCF ID) to instruct each ADRF to directly send the stored data of the corresponding UE to the local DCCF.

[0207] In another possible implementation, all the data to be acquired by the consumer is stored in multiple ADRFs, so the central network element #1 needs to send message #5 to multiple ADRFs respectively.

[0208] Optionally, the central network element #1 sends the same message #5 to multiple ADRFs respectively. Message #5 may include information about all data requested by the consumer (including UE ID list, data type, or period).

[0209] Optionally, since the data storage network elements store UE data with different periods and data types, the local DCCF can send different messages #5 to multiple ADRFs respectively.

[0210] For example, central network element #1 can send message #5#1 to ADRF #1 and message #5#2 to ADRF #2. Message #5#1 may include a UE ID list #1, data type #1, and / or period #1 corresponding to the UE data stored in ADRF #1, and message #5#2 may include a UE ID list #2, data type #2, and / or period #2 corresponding to the UE data stored in ADRF #2.

[0211] For example, period #1 could be the intersection of the "historical data / time period" carried in the consumer request (corresponding to S504) and the duration of UE data stored in ADRF #1. Period #2 could be the intersection of the "historical data / time period" carried in the consumer request and the duration of UE data stored in ADRF #2.

[0212] Optionally, message #5 may also include a local DCCF identifier (local DCCF ID) to instruct each ADRF to directly send the stored data of the corresponding UE to the local DCCF.

[0213] S408b: ADRF sends message #6 to the local DCCF; correspondingly, ADRF receives message #6 from central network element #1.

[0214] The details of message #6 can be found in step S408a, and will not be repeated here.

[0215] It should be noted that, based on the above two methods, the local DCCF can completely obtain the required UE data, and the application scenarios of the above two methods are not limited in this application embodiment.

[0216] S409: The local DCCF sends message #7 to the consumer; correspondingly, the consumer receives message #7 from the local DCCF.

[0217] Message #7 is used to indicate that the consumer is requesting all the data to be retrieved. Specifically, message #7 may include a list of UE IDs and all the data to be retrieved corresponding to each UE in the list.

[0218] Optionally, if the message #2 sent by the consumer to the local DCCF in step S404 includes a "sorting rule" field, then before step S409, method 400 may further include: the local DCCF sorting the data of each UE in message #6 (at least one ADRF sender UE data) according to the "sorting rule". For details on the sorting method, please refer to the relevant description in step S404; this application will not elaborate further here.

[0219] In one possible implementation, the local DCCF and central network element #1 in method 400 can be the same network element, thus the actions corresponding to the local DCCF and central network element #1 in method 400 can be combined. That is, the ADRF can register, update, and / or delete UE data information with the local DCCF, and after receiving message #2 sent by the consumer, the local DCCF does not need to send a query request (message #3) to other devices, but can directly determine the storage location of the data to be obtained and send a message to the corresponding ADRF to request the data. Alternatively, the ADRF can register, update, and / or delete UE data information with the central network element #1, and the consumer can directly send message #2 to the central network element #1. After receiving message #2, the central network element #1 determines the storage location of the data to be obtained and sends a message to the corresponding ADRF to request the data.

[0220] In the above scheme, the consumer requests data from at least one UE by sending message #2 to the local DCCF or central network element #1. However, in actual implementation, the local DCCF may not be able to communicate directly with the central network element #1 (for example, the central network element #1 is not open to the local DCCF). As shown in Figure 5, in this case, the local DCCF can send a request message directly to the ADRF, and then the ADRF can obtain the complete ADRFID list through the central network element #1.

[0221] Figure 5 is a schematic diagram of a communication method 500 applicable to an embodiment of this application.

[0222] For ease of understanding, Figure 5 illustrates an example where the data the consumer needs to obtain is stored in ADRF#1 and ADRF#2, where ADRF#1 is a local ADRF. It should be understood that the data the consumer needs to obtain can also be stored in more ADRFs, and the number of ADRFs does not constitute a limitation on the embodiments of this application.

[0223] S501a: ADRF#1 receives data #3.

[0224] S502a: ADRF#1 sends message #8 to central network element #1; correspondingly, central network element #1 receives message #8 from ADRF#1.

[0225] S503a: Central network element #1 processes the UE's data storage attribute (UE collection data profile) information according to message #8.

[0226] It should be understood that steps S601a-S603a are similar to steps S501-S503 in method 500, and will not be described in detail here.

[0227] S501b: ADRF#2 receives data #4.

[0228] S502b: ADRF#2 sends message #9 to central network element #1; correspondingly, central network element #1 receives message #9 from ADRF#2.

[0229] S503b: Central network element #1 processes the UE's data storage attribute (UE collection data profile) information according to message #9.

[0230] It should be understood that steps S501b-S503b are similar to steps S501a-S503a, and will not be described in detail here. That is, each ADRF will summarize the received data in the central network element #1.

[0231] Furthermore, S501a-S503a and S501b-S503b are steps that are executed independently depending on different data storage network elements. The execution order of S501a-S503a and S501b-S503b is not limited in the embodiments of this application.

[0232] S504: The consumer sends message #10 to the local DCCF; correspondingly, the local DCCF receives message #10 from the consumer.

[0233] It should be understood that the specific content of message #10 can be referred to the relevant description of message #2 in step S404 of method 400 above, and will not be repeated here.

[0234] S505: The local DCCF sends message #11 to ADRF#1; correspondingly, ADRF#1 receives message #11 from the local DCCF.

[0235] Specifically, upon receiving message #10, the local DCCF can directly send message #11 to the local data storage network element ADRF #1 to request all data of the UE within the corresponding time period. Message #11 may include a list of UE IDs that the consumer needs to obtain.

[0236] Optionally, message #11 may also include historical data / time periods corresponding to the UE ID list.

[0237] S506: ADRF#1 sends message #12 to central network element #1; correspondingly, central network element #1 receives message #12 from ADRF#1.

[0238] Among them, message #12 is used to request the list of data storage network elements that store historical data of UEs, that is, message #12 may include a list of UE IDs.

[0239] Optionally, message #12 may also include historical data / time periods corresponding to the UE ID list.

[0240] S507: Central network element #1 sends message #13 to ADRF #1; correspondingly, ADRF #1 receives message #13 from central network element #1.

[0241] It should be understood that after receiving message #12, central network element #1 can determine the data storage network element (ADRF) information for storing each UE's data based on the UE ID list. Specifically, central network element #1 can query the UE collection data profile based on the UE ID list and historical data / time period to determine the data storage network element information for storing data within the corresponding time period for each UE, and send message #13 to the local data storage network element (ADRF#1). In the scenario shown in method 500 of this application, the UE data to be acquired is stored in ADRF#1 and ADRF#2.

[0242] Optionally, when message #12 also includes historical data / time periods corresponding to the UE ID list, the central network element #1 can determine the data storage network element information for storing data within the corresponding time period for each UE based on the UE ID list and the historical data / time period. Specifically, the central network element #1 can query the UE collection data profile based on the UE ID list and the historical data / time period to determine the data storage network element information for storing data within the corresponding time period for each UE, and send message #13 to the local data storage network element (ADRF #1).

[0243] It should be noted that message #13 may include only the ADRFID list; or it may include both the UE ID list and the ADRFID list, and this application does not limit this. The ADRFID list may include at least one ADRFID, and each UE ID in the UE ID list corresponds to at least one ADRFID.

[0244] S508: ADRF#1 sends message #14 to ADRF#2; correspondingly, ADRF#1 receives message #14 from ADRF#2.

[0245] It should be understood that ADRF#1 can send message #14 to other data storage network elements (e.g., ADRF#2) that store UE data based on message #13. Message #14 is used to indicate a request to obtain all data of the UE within the corresponding time period.

[0246] It should be understood that when the data to be acquired is stored in more ADRFs, ADRF#1 can also send information to other ADRFs to acquire the UE's data within the corresponding time period.

[0247] S509: ADRF#2 sends message #15 to ADRF#1; correspondingly, ADRF#1 receives message #15 from ADRF#2.

[0248] Message #15 contains the UE data stored in ADRF #2. Specifically, local ADRF #1 can summarize the data to be acquired; that is, ADRF #2 can determine the data of the corresponding UE at the corresponding time based on message #14, and then send the data to ADRF #1.

[0249] It should be understood that message #15 may include a list of UE IDs and the data to be acquired for each UE in the list.

[0250] S510: ADRF#1 sends message #16 to the local DCCF; correspondingly, the local DCCF receives message #16 from ADRF#1.

[0251] Message #16 is a response message for retrieving data, including all data to be retrieved by the consumer (data #3 stored in ADRF #1 and data #4 stored in ADRF #2). Specifically, message #16 may include a list of UE IDs and all the data to be retrieved corresponding to each UE in the list.

[0252] As one possible implementation, in step S507, the central network element #1 can also send message #13 to all data storage network elements corresponding to the data to be acquired, so that in steps S508-S510, the local ADRF #1 does not need to summarize the data first, but each ADRF sends its own stored data to be acquired to the local DCCF.

[0253] S511: The local DCCF sends message #17 to the consumer; correspondingly, the consumer receives message #17 from the local DCCF.

[0254] Message #17 is used to indicate that the consumer is requesting all the data to be retrieved. Similarly, message #17 can include a list of UE IDs and all the data to be retrieved corresponding to each UE in the list.

[0255] Optionally, if the message #10 sent by the consumer to the local DCCF in step S504 includes a "sorting rule" field, then before step S511, method 500 may further include: the local DCCF sorting the data of each UE in message #16 according to the "sorting rule". For details on the sorting method, please refer to the relevant description in step S404; this application will not elaborate further here.

[0256] In one possible implementation, the central network element #1 of methods 400 and 500 can also be a UDR. When the consumer is an NWDAF, the data to be acquired is AI data. Therefore, information about the data storage network element storing the UE's AI data can also be added to the UDR (for example, information about the ADRF used to store the UE's AI data can be indicated by adding a new field #1 (such as UE AI data register)). In this scenario, the consumer can also acquire data in the manner shown in Figure 6.

[0257] Figure 6 is a schematic diagram of a communication method 600 applicable to an embodiment of this application.

[0258] It should be noted that Figure 6 is only for illustration, taking the central network element #1 as a UDR in method 400 as an example, and does not limit the possibility of combining method 500 with "central network element #1 as a UDR".

[0259] S601: ADRF receive data #5.

[0260] S602: ADRF sends message #18 to UDR; correspondingly, UDR receives message #18 from ADRF.

[0261] It should be noted that an ADRF may include multiple ADRFs. For example, an ADRF may include ADRF#1 and ADRF#2. In method 600, each ADRF performs similar actions, namely, associating the received data with the corresponding UE ID and registering, updating, and / or deleting it with the UDR. Further details are omitted here, and the number of ADRFs is not limited in the embodiments of this application.

[0262] It should be understood that message #18 is used to instruct the registration, update and / or deletion of terminal #1 in the UDR, and message #18 may include the UE ID of terminal #1.

[0263] Optionally, message #18 may also include data attribute information corresponding to data #5 sent by terminal #1 to ADRF, thereby facilitating the central network element's coordination and management of the data. For details regarding the content of the data attribute information, please refer to the relevant description in step S402 of method 400; this application will not elaborate further here.

[0264] Optionally, since the UDR includes information about the data storage network element storing the UE's AI data, the data attribute information may also include information about the data storage network element storing the AI ​​data. For example, the "UE AI data register" field can indicate that the registration information is used to indicate the information of the data storage network element storing the UE's AI data in the UDR. Alternatively, instead of setting a separate field, the name of information #18 can be used to indicate the information of the data storage network element storing the UE's AI data in the UDR.

[0265] Similarly, ADRF can trigger a process of registering, updating, and / or deleting UE ID and data attribute information with UDR after each execution of step S601 (i.e., step S602); or ADRF can trigger a process uniformly after multiple executions of step S601 (e.g., triggering periodically according to internal implementation) to register, update, and / or delete at least one UE ID and / or data attribute information corresponding to the data sent by each terminal in UDR.

[0266] S603: UDR processes UE data collection data profile information based on message #18.

[0267] For details regarding the process by which the UDR processes the UE collection data profile according to message #18, please refer to the relevant description of step S403 in method 400, which will not be repeated here.

[0268] Optionally, the UE collection data profile information can be stored using the newly added field #1 (UE AI data register).

[0269] S604: The consumer sends message #19 to the local DCCF; correspondingly, the local DCCF receives message #19 from the consumer.

[0270] Message #19 is used to indicate a request to obtain data from at least one UE. It should be understood that the specific content of message #19 can be found in the relevant description in step S404 of method 400, and will not be repeated here.

[0271] It should be noted that when the local DCCF can directly identify the network element storing the data to be retrieved (e.g., ADRF), the local DCCF can directly send information to the corresponding network element to request the data. However, the mobility of the UE makes it difficult for the local DCCF to directly identify all network elements storing the data to be retrieved. Therefore, based on this situation, after the local DCCF receives message #19, it can obtain the UE data to be retrieved in the following way:

[0272] Method 1:

[0273] S605a: The local DCCF sends message #20 to the UDR; correspondingly, the UDR receives message #20 from the local DCCF.

[0274] Among them, message #20 is used to request the list of data storage network elements that store UE historical data information. That is, message #20 may include a list of UE IDs and a new field #1 (UE AI data register).

[0275] Optionally, message #20 may also include historical data / time periods corresponding to the UE ID list.

[0276] S606a: The UDR sends message #21 to the local DCCF; correspondingly, the local DCCF receives message #21 from the UDR.

[0277] S607a: The local DCCF sends message #22 to the ADRF; correspondingly, the ADRF receives message #22 from the local DCCF.

[0278] S608a: ADRF sends message #23 to the local DCCF; correspondingly, ADRF receives message #23 from UDR.

[0279] Method 2:

[0280] S605b: The local DCCF sends message #20 to the UDR; correspondingly, the UDR receives message #20 from the local DCCF.

[0281] Among them, message #20 is used to request the list of data storage network elements that store UE historical data information. That is, message #20 may include a list of UE IDs and a new field #1 (UE AI data register).

[0282] Optionally, message #20 may also include historical data / time periods corresponding to the UE ID list.

[0283] S607b: UDR sends message #22 to ADRF; correspondingly, ADRF receives message #22 from UDR.

[0284] S608b: ADRF sends message #23 to the local DCCF; correspondingly, ADRF receives message #23 from UDR.

[0285] It should be noted that for the specific details of steps S606a-S608a and S606b-S608b, please refer to the relevant descriptions in steps S406a-S408a and S406b-S408b of method 400, which will not be repeated here.

[0286] S609: The local DCCF sends message #24 to the consumer; correspondingly, the consumer receives message #24 from the local DCCF.

[0287] It should be noted that the specific content of message #24 can be found in the description of message #7 in step S409 of method 400, and will not be repeated here.

[0288] To facilitate understanding of the above embodiments provided in this application, the following points are made.

[0289] (1) In the embodiments of this application, "instruction" may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of indicating A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0290] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0291] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface. In this application, descriptions relating to network element A sending messages, information, or data to network element B, and network element B receiving messages, information, or data from network element A, are intended to indicate which network element the message, information, or data is to be sent to, without specifying whether the transmission is direct or indirect via other network elements. Descriptions such as "when," "under the circumstances," "if," and "if" all indicate that the device will take corresponding actions under certain objective circumstances, not that they limit the time frame, nor do they require the device to perform a judgment action during implementation, nor do they imply any other limitations.

[0292] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0293] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0294] (5) In this application, “predefined” can be achieved by pre-storing the corresponding code, table or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method.

[0295] (6) In this application, the “protocol” may refer to standard protocols in the field of communications, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied in future communication networks. This application does not limit the scope of the term.

[0296] (7) In this application, the words “exemplary,” “for example,” “exemplary,” “as another example,” etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as an “exemplary” in this application should not be construed as being more preferred or advantageous than other embodiments or designs.

[0297] (8) In this application, “comprising,” “including,” “having,” and variations thereof mean “including but not limited to,” unless otherwise specifically emphasized. “At least one” means one or more, and “more” means two or more.

[0298] (9) In this application, "and / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple.

[0299] (10) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0300] (11) Some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0301] The methods of the embodiments of this application have been described in detail above with reference to Figures 3 to 6. In order to realize the functions of the methods provided in this application, both the first network element and the first data storage network element may include hardware structures and / or software modules, and the above functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a certain function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0302] The communication device of the present application embodiment is described below with reference to Figures 7 to 9.

[0303] Figure 8 is a structural schematic diagram of a communication device 700 provided in an embodiment of this application.

[0304] The device 700 includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 can communicate with the outside world, and the processing unit 720 is used for data processing. The transceiver unit 710 can also be referred to as a communication interface or a communication unit.

[0305] Optionally, the transceiver unit 710 may also be referred to as a communication interface or communication unit, including a transmitting unit and / or a receiving unit. The transceiver unit 710 may be a transceiver (including a transmitter and / or receiver), an input / output interface (including input and / or output interfaces), or pins or circuits, etc. The transceiver unit 710 can be used to perform the transmitting and / or receiving steps in the above method embodiments.

[0306] Optionally, the processing unit 720 may be a processor (which may include one or more) or a processing circuit with processor functions, and may be used to perform other steps in the above method embodiments besides sending and receiving.

[0307] Optionally, the device 700 further includes a storage unit, which may be a memory, an internal storage unit (e.g., a register or cache), or an external storage unit (e.g., a read-only memory or a random access memory). The storage unit stores instructions, and the processing unit 720 executes the instructions stored in the storage unit to cause the communication device to perform the aforementioned method.

[0308] In addition, the transceiver unit 710 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit 720 may be a processing circuit.

[0309] It should be noted that the device in Figure 7 can also be a chip or a chip system, such as a system-on-a-chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. This application does not impose any limitations on this.

[0310] The device 700 can be used to perform the actions performed by the first network element in the above method embodiment. In this case, the device 700 can be the first network element or a component that can be configured in the first network element.

[0311] The transceiver unit 710 is used to perform transceiver-related operations on the first network element side in the above method embodiment. For example, it is used to perform transceiver-related operations on the first network element side, such as receiving a first message from the first data storage network element. The first message includes information about the first terminal and is used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0312] The processing unit 720 is used to perform processing-related operations on the first network element side in the above method embodiment. For example, it is used to perform processing-related operations on the first network element side, such as associating the information of the first terminal with the information of the first data storage network element in response to the first message.

[0313] Optionally, associating the information of the first terminal with the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element, wherein the first list information corresponds to the information of the first terminal, and the updated first list information includes the information of at least one data storage network element, wherein the at least one data storage network element is used to store data associated with the first terminal, and the data associated with the first terminal includes the first data.

[0314] Optionally, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes the information of the first data, which includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

[0315] Optionally, updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

[0316] Optionally, the transceiver unit 710 is further configured to: receive a second message, the second message including information of the first terminal, the second message being used to indicate obtaining information of the at least one data storage network element; and send the first list information.

[0317] Optionally, the second message further includes information about second data associated with the first terminal; the second message is used to indicate the acquisition of information about at least one second data storage network element, the at least one second data storage network element being used to store the second data; and to send information about the at least one second data storage network element.

[0318] Alternatively, the device 700 can be used to perform the actions performed by the first data storage network element in the above method embodiment. In this case, the device 700 can be the first data storage network element or a component configurable in the first data storage network element.

[0319] The transceiver unit 710 is used to perform transceiver-related operations on the first data storage network element side in the above method embodiment, for example, to receive first data; to send a first message to the first network element, the first message including information of the first terminal, the first message being used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

[0320] Optionally, the information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; the first message also includes the information of the first data, which includes the data type of the first data and / or the first time the first data was generated; the first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

[0321] It should be understood that the device 700 here is embodied in the form of a functional unit. The term "unit" here may refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memories for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functions.

[0322] The apparatus 700 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as the first network element, or the first data storage network element) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0323] Figure 8 is a structural schematic diagram of a communication device 800 provided in an embodiment of this application.

[0324] As shown in Figure 8, the device 800 includes a processor 810 and a transceiver 820. The processor 810 and the transceiver 820 communicate with each other through an internal connection path. The processor 810 is used to execute instructions to control the transceiver 820 to send and / or receive signals.

[0325] Optionally, the device 800 may further include a memory 830, which communicates with the processor 810 and the transceiver 820 via an internal connection path. The memory 830 is used to store instructions, and the processor 810 can execute the instructions stored in the memory 830.

[0326] In one possible implementation, the device 800 is used to implement the various processes and steps corresponding to the terminal device in the above method embodiments.

[0327] It should be understood that the device 800 can be specifically a terminal device in the above embodiments, or it can be a chip or a chip system. Correspondingly, the transceiver 820 can be the transceiver circuit of the chip, which is not limited here. For example, the device 800 can be used to execute the various steps and / or processes corresponding to the first network element in the above method embodiments.

[0328] In one possible implementation, the device 800 is used to implement the various processes and steps corresponding to the network device in the above method embodiments.

[0329] It should be understood that the device 800 can be specifically a network device as described in the above embodiments, or it can be a chip or a chip system. Correspondingly, the transceiver 820 can be the transceiver circuit of the chip, which is not limited here. For example, the device 800 can be used to execute the various steps and / or processes corresponding to the first data storage network element in the above method embodiments.

[0330] Optionally, the memory 830 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 810 may be used to execute instructions stored in the memory, and when the processor 810 executes instructions stored in the memory, the processor 810 is used to perform the various steps and / or processes of the method embodiments corresponding to the first network element or the first data storage network element described above.

[0331] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0332] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The processor in the embodiments of this application can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0333] It is understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous linked dynamic random access memory, and direct memory bus random access memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0334] Figure 9 is a schematic diagram of the structure of a chip system 900 provided in an embodiment of this application.

[0335] As shown in Figure 9, the chip system 900 (or processing system) includes logic circuits 910 and input / output interface 920.

[0336] The logic circuit 910 can be a processing circuit in the chip system 900. The logic circuit 910 can be coupled to the storage unit, calling instructions from the storage unit, enabling the chip system 900 to implement the methods and functions of the embodiments of this application. The input / output interface 920 can be an input / output circuit in the chip system 900, outputting processed information from the chip system 900, or inputting data or signaling information to be processed into the chip system 900 for processing.

[0337] As one approach, the chip system 900 is used to implement the operations performed by the first network element in the various method embodiments described above.

[0338] As one approach, the chip system 900 is used to implement the operations performed by the first data storage network element in the various method embodiments described above.

[0339] This application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0340] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0341] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0342] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0343] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0344] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0345] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0346] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0348] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method applied to a first network element, characterized in that, include: Receive the first message from the first data storage network element; The first message includes information about the first terminal, and the first message is used to indicate that the first data associated with the first terminal is stored in the first data storage network element. In response to the first message, the information of the first terminal is associated with the information of the first data storage network element.

2. The method according to claim 1, characterized in that, The information associated with the first terminal and the information of the first data storage network element includes: The first list information is updated based on the information of the first data storage network element. The first list information corresponds to the information of the first terminal. The updated first list information includes information of at least one data storage network element. The at least one data storage network element is used to store data associated with the first terminal. The data associated with the first terminal includes the first data.

3. The method according to claim 2, characterized in that, The information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; The first message also includes information about the first data, which includes the data type of the first data and / or the first time the first data was generated; The first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

4. The method according to claim 2 or 3, characterized in that, The step of updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

5. The method according to any one of claims 2 to 4, characterized in that, The method further includes: Receive a second message, the second message including information of the first terminal, the second message being used to indicate obtaining information of the at least one data storage network element; Send the first list information.

6. The method according to claim 5, characterized in that, The second message also includes information about second data, which is associated with the first terminal; The second message is used to indicate the acquisition of information of at least one second data storage network element, wherein the at least one second data storage network element is used to store the second data; Send information from the at least one second data storage network element.

7. The method according to any one of claims 1 to 6, characterized in that, The first network element is a DCCF network element, ADRF network element, or Unified Database UDR network element.

8. A communication method applied to a first data storage network element, characterized in that, include: Receive the first data; Send a first message to a first network element. The first message includes information about a first terminal. The first message is used to indicate that the first data associated with the first terminal is stored in the first data storage network element.

9. The method according to claim 8, characterized in that, The information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; The first message also includes information about the first data, which includes the data type of the first data and / or the first time the first data was generated; The first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

10. A communication system, comprising a first network element and a first data storage network element, characterized in that, include: The first data storage network element receives the first data; The first data storage network element sends a first message to the first network element. The first message includes information about the first terminal. The first message is used to indicate that the first data associated with the first terminal is stored in the first data storage network element. The first network element responds to the first message by associating the information of the first terminal with the information of the first data storage network element.

11. The communication system according to claim 10, characterized in that, The information associated with the first terminal and the information of the first data storage network element includes: The first list information is updated based on the information of the first data storage network element. The first list information corresponds to the information of the first terminal. The updated first list information includes information of at least one data storage network element. The at least one data storage network element is used to store data associated with the first terminal. The data associated with the first terminal includes the first data.

12. The communication system according to claim 10 or 11, characterized in that, The information of the first terminal includes the identifier of the first terminal, and the information of the first data storage network element includes the identifier of the first data storage network element; The first message also includes information about the first data, which includes the data type of the first data and / or the first time the first data was generated; The first list information also includes information about the data associated with the first terminal stored in each of the at least one data storage network element.

13. The communication system according to claim 11 or 12, characterized in that, The step of updating the first list information based on the information of the first data storage network element includes: updating the first list information based on the information of the first data storage network element and the information of the first data.

14. A communication device, characterized in that, The apparatus includes a unit for performing the method as described in any one of claims 1 to 7, and / or the apparatus includes a unit for performing the method as described in claim 8 or 9.

15. A communication system, characterized in that, Includes the communication device as described in claim 14.

16. A communication device, characterized in that, The device includes a processor coupled to a memory for storing computer programs or instructions, and the processor is configured to execute the computer programs or instructions in the memory, causing the device to perform the method as described in any one of claims 1 to 7.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

18. A chip or chip system, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a communication device equipped with the chip system to perform the method of any one of claims 1 to 7.

19. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 7.

Images