Data processing method and apparatus, and computer-readable storage medium

Abstract

This application provides a data processing method and apparatus, as well as a computer-readable storage medium, to reduce the storage space occupied by redundant PFDs stored in a UDR. After acquiring a first PFD, the first device acquires a second PFD from a second device and transmits a PFD set to the UDR based on the first and second PFDs, thereby enabling the UDR to update the PFD information in the second PFD based on the PFD set. The PFD set includes at least one of the first and second PFDs, the first PFD including a first triplet and a first application ID, and the second PFD including a second triplet and a second application ID. Implementing a method for transmitting PFD sets reduces the storage space occupied by redundant PFDs stored in the UDR, ensures that the SMF can determine a unique PFD based on the ID of the application to be processed or triplet information of the application to be processed, reduces the operation of the SMF to select a PFD from multiple PFDs stored in the UDR corresponding to the application to be processed, and further reduces the complexity of the SMF's operation.

Description

Technical Field

[0001] This application claims priority to Chinese Patent Application No. 202310335248.2, titled "Data Processing Method and Apparatus, and Computer-Readable Storage Medium", filed with the China National Intellectual Property Administration on March 24, 2023, and Chinese Patent Application No. 202311238539.6, titled "Data Processing Method and Apparatus, and Computer-Readable Storage Medium", filed with the China National Intellectual Property Administration on September 22, 2023, and the entire contents of both are incorporated herein by reference.

[0002] Embodiments of this application relate to the field of wireless networks, and in particular, to data processing methods and apparatuses, and computer-readable storage media.

Background Art

[0003] With the rapid development of wireless network technology, in order to efficiently manage and monitor the network, in application identification technology, traffic is classified based on application characteristics or protocol characteristics of the traffic, etc., in order to implement sophisticated traffic management and control.

[0004] In actual application, the application identification technology, specifically the network data analytics function (NWDAF), can further collect information about traffic flows traversing the core network, perform application feature extraction on the traffic flow information, determine the application corresponding to the traffic flow information, and generate application-level packet flow description (PFD) information based on a triplet of traffic flow information. The NWDAF provides the PFD information to the NEF (PFDF). The session management function (SMF) installs the PFD obtained from the NEF (PFDF) into the user plane function (UPF). The UPF identifies the purpose of the traffic flow based on the PFD of the traffic flow in order to charge for the traffic flow and allocate network resources to the traffic flow.

[0005] In a scenario where both the NWDAF and the application function (AF) provide the application's PFD, if both the NWDAF and AF provide the same application A's PFD information to the network exposure function (NEF), when the NEF dumps application A's PFD information to the unified data repository (UDR), the NEF stores multiple iterative PFD entries for application A because there are multiple optional PFD entries, and the NEF dumps application A's PFD information directly to the UDR. This leads to the occupancy of storage space within the UDR, increases the complexity of selecting PFD information by the SMF, and reduces the accuracy of the management performed by the SMF on application A's traffic flow based on the PFD information stored in the UDR. [Overview of the project]

[0006] This application provides a data processing method and apparatus, as well as a computer-readable storage medium, to avoid cases where redundant PFD information is dumped to the UDR by the NEF, and to reduce the storage space occupied by redundant PFDs stored in the UDR. [Means for solving the problem]

[0007] A first aspect of this application provides a data processing method comprising: a first device obtaining a first packet flow description PFD, the first PFD comprising a first triplet and a first application identity document (ID); the first device obtaining a second PFD transmitted by a second device, the second PFD comprising a second triplet and a second application ID; and the first device transmitting a PFD set to a UDR based on the first and second PFDs, the PFD set comprising at least one of the first or second PFD.

[0008] In this embodiment of the present application, after obtaining a first PFD, the first device obtains a second PFD from the second device and transmits a PFD set to the UDR based on the first and second PFDs, thereby enabling the UDR to update the PFD information in the second PFD based on the PFD set. The PFD set includes at least one of the first and second PFDs, where the first PFD includes a first triplet and a first application ID, and the second PFD includes a second triplet and a second application ID. The NEF does not dump redundant PFDs to the UDR by implementing a method for transmitting the PFD set. This reduces the storage space occupied by redundant PFDs stored in the UDR, ensures that the SMF can determine a unique PFD based on the ID of the application to be processed or the triplet information of the application to be processed, reduces the operation of the SMF to select a PFD from multiple PFDs stored in the UDR corresponding to the application to be processed, and further reduces the complexity of the SMF's operation.

[0009] In a possible embodiment of the first aspect, the first PFD further includes a first string, and the second PFD further includes a second string, the first string being used to describe the source of the first PFD, and the second string being used to describe the source of the second PFD. In this embodiment of the present application, the first PFD carries the first string for describing the source of the first PFD, and the second PFD carries the second string for describing the source of the second PFD, thereby allowing a device using the first or second PFD to easily determine the reliability of the first or second PFD based on the source of the first or second PFD. This improves the flexibility of the solution.

[0010] In a possible embodiment of the first aspect, the first device transmits a PFD set to the UDR based on a first PFD and a second PFD, and the PFD set includes at least one of the first PFD or the second PFD, or the first device transmits a PFD set to the UDR when it determines that the first triplet is different from the second triplet and the first application ID is different from the second application ID, and the PFD set includes the first PFD and the second PFD, or the first device determines that the first triplet is different from the second triplet and the first application ID is different from the second application ID The first device determines that the first string is different from the second string when it determines that the first string is the same as the application ID, or that the first triplet is the same as the second triplet, and the first device determines that the first string indicates that the source of the first PFD is AF, and sends the PFD set to the UDR, including that the PFD set contains the first PFD, or the first device determines that the first string indicates that the source of the first PFD is NWDAF, and sends the PFD set to the UDR, including that the PFD set contains the second PFD.

[0011] In this embodiment of the present application, when the first device determines that the first triplet is different from the second triplet and the first application ID is different from the second application, the set of PFDs transmitted by the first device to the UDR includes the first PFD and the second PFD. Alternatively, if the first device determines that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or if the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is different from the second string, and the first device determines that the first string indicates that the source of the first PFD is AF, and the PFD set sent to the UDR by the first device includes the first PFD, or the first device determines that the first string indicates that the source of the first PFD is NWDAF, and the PFD set sent to the UDR includes the second PFD. The first and second PFDs, having different triplets and application IDs, are sent to the UDR. Alternatively, when the first PFD and the second PFD have different triplets or different application IDs, the first device further determines that the first string is different from the second string, and if the first string indicates that the source of the first PFD is AF, it sends the first PFD to the UDR, or if the first string indicates that the source of the first PFD is NWDAF, it sends the second PFD to the UDR. This avoids sending redundant PFDs to the UDR. In addition, since the reliability of PFDs obtained by NWDAF through analysis is limited by the volume and type of data collected by NWDAF, when both the first and second PFDs relate to the same application, the PFD whose source is AF is preferentially sent to the UDR. This improves the reliability of PFDs sent to the UDR by the first device.

[0012] In a possible embodiment of the first aspect, the first PFD further includes first time information, and the second PFD further includes second time information. The first device sends a PFD set to the UDR based on the first PFD and the second PFD, and the PFD set includes at least one of the first PFD or the second PFD, when the first device determines that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or the first triplet is the same as the second triplet and the first application ID is different from the second application ID, when the first device determines that the first string is the same as the second string, and the first device determines, based on the first time information and the second time information, that the first PFD was generated before the second PFD, and sends a PFD set to the UDR, and the PFD set includes the second PFD, or the first device The first device determines, based on first and second time information, that the first PFD was generated after the second PFD, and sends a PFD set to the UDR, the PFD set containing the first PFD; or, when the first device determines that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on first and second time information, that the first PFD expires before the second PFD, and sends a PFD set to the UDR, the PFD set containing the second PFD; or, based on first and second time information, that the first PFD expires after the second PFD, and sends a PFD set to the UDR, the PFD set containing the first PFD.

[0013] In this embodiment of the present application, the first device transmits a set of PFDs to the UDR based on a first PFD and a second PFD. Specifically, the first device may determine that a first triplet is different from a second triplet and a first application ID is the same as a second application ID, or that a first triplet is the same as a second triplet and a first application ID is different from a second application ID, thereby the first device may determine that a first string is the same as a second string, and the first device may determine, based on first and second time information, that a first PFD was generated before a second PFD and the set of PFDs transmitted to the UDR includes a second PFD, or the first device may determine, based on first and second time information, that a first PFD was generated after a second PFD and the set of PFDs transmitted to the UDR includes a first PFD. Alternatively, if the first device determines that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on the first and second time information, that the first PFD expires before the second PFD, and the set of PFDs sent by the first device to the UDR includes the second PFD; or, based on the first and second time information, the first device determines that the first PFD expires after the second PFD, and the set of PFDs sent by the first device to the UDR includes the second PFD. The first device does not send redundant PFDs to the UDR. In addition, if the first and second PFDs have the same triplet and the same application ID, the first device preferentially sends the PFD with the later expiration date to ensure the maximum validity period of the PFDs sent to the UDR. When the first and second PFDs have different triplets or different application IDs, and the first and second PFDs have the same source, the first device will prioritize sending the PFD with the later generation time to ensure that the PFD sent to the UDR is the most timely PFD available. In this way, the reliability of the solution is improved.

[0014] In possible embodiments of the first aspect, the first time information includes the expiration date and generation date of the first PFD, or the validity period and generation date of the first PFD, and the second time information includes the expiration date and generation date of the second PFD, or the validity period and generation date of the second PFD. In this embodiment of the present application, the first time information may include the expiration date and generation date of the first PFD, or the validity period and generation date of the first PFD. The second time information may include the expiration date and generation date of the second PFD, or the validity period and generation date of the second PFD. The generation and expiration dates of the PFDs are marked with time information in different representation formats to provide a basis for the first device to process redundant PFDs. This improves the flexibility of the solution.

[0015] In a possible embodiment of the first aspect, the generation of the first PFD occurs after the generation of the second PFD.

[0016] The first device transmits a set of PFDs to the UDR based on the first PFD and the second PFD, and the set of PFDs includes at least one of the first PFD or the second PFD. The first device sends a PFD set to the UDR when the first application ID is the same as the second application ID, and at least one of the following occurs: the first triplet is different from the second triplet, the first uniform resource locator (URL) is different from the second URL, and the first domain name (DN) is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, and the PFD set contains the first PFD and the second PFD, or The first device sends a PFD set to the UDR when the first application ID is the same as the second application ID, and at least one of the following occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, and the PFD set includes the first PFD. Includes.

[0017] In this embodiment of the present application, the first device transmits a set of PFDs to the UDR based on a first PFD and a second PFD. Specifically, the set of PFDs transmitted to the UDR by the first device includes a first PFD and a second PFD, where the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF. The set of PFDs sent to the UDR by the first device includes the first PFD when the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF. When there are multiple related PFDs, it is ensured that the PFD with the highest confidence is stored in the UDR for later selection. This improves the reliability of the solution and also simplifies the behavior when another network element subsequently selects a PFD.

[0018] In a possible embodiment of the first aspect, the generation of the first PFD occurs after the generation of the second PFD.

[0019] The first device transmits a set of PFDs to the UDR based on the first PFD and the second PFD, and the set of PFDs includes at least one of the first PFD or the second PFD. When the first device sends a PFD set to the UDR, and the PFD set contains the first PFD, or when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, the first device sends a PFD set to the UDR, and the PFD set contains the first PFD, or The first device sends a PFD set to the UDR when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, and the PFD set includes the second PFD. Includes.

[0020] In this embodiment of the present application, the first device transmits a set of PFDs to the UDR based on a first PFD and a second PFD. Specifically, the set of PFDs transmitted to the UDR includes a first PFD, where the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF. The set of UDRs transmitted to the UDR includes a second PFD, where the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF. When there are multiple related PFDs, it is ensured that the PFD with the highest confidence is stored in the UDR for later selection. This improves the reliability of the solution and simplifies the subsequent selection of the PFD by another network element.

[0021] In a possible embodiment of the first aspect, the second PFD further includes a third string indicating that the PFD is a PFD generated by a pre-configured device.

[0022] In this embodiment of the present application, a mark is added to the PFD whose source is a pre-configured device in order to help distinguish between different sources of PFDs. This effectively reduces the reduction of PFD content when there are only two cases of PFD sources and helps reduce the consumption of network resources in the PFD transmission process.

[0023] In a possible implementation of the first aspect, the first device includes a NEF, the second device includes an integrated data repository UDR, or the first device includes an application function AF, and the second device includes a NWDAF. In this embodiment of the present application, when the first device is a NEF, the second device is a UDR, or when the first device is an AF, the second device is a NWDAF. This method may be executed by the NEF to efficiently manage the PFDs of all applications in the network, or may be executed by the AF to effectively reduce the data processing pressure of the NEF.

[0024] In a possible implementation of the first aspect, when the first device includes a NWDAF, the second device includes a UDR or a NEF, the first PFD is a PFD generated by the NWDAF, or when the first device includes a NEF, the second device includes a UDR.

[0025] In this embodiment of the present application, when the first device is a NWDAF, the second device includes a NEF or a UDR, or when the first device includes a NEF, the second device includes a UDR. This method may be executed by both the NWDAF and the NEF. The flexible execution environment provides more possibilities for implementing the solution, improves the flexibility of implementing the solution, and reduces the data processing pressure of each node.

[0026] The second aspect of the present application provides a data processing method, and this method includes the following steps.

[0027] The integrated data repository UDR obtains a PFD information query request from the first device, The UDR sends the second PFD to the first device, and the second PFD includes a second triplet and a second application ID. The UDR obtains a PFD set from the first device, and the PFD set includes at least one of the first PFD and the second PFD. The first PFD includes a first triplet and a first application ID.

[0028] In a possible implementation of the second aspect, the second PFD further includes a second string, the first PFD further includes a first string, the first string is used to describe the source of the first PFD, and the second string is used to describe the source of the second PFD.

[0029] In a possible implementation of the second aspect, the first PFD further includes first time information, and the second PFD further includes second time information.

[0030] In a possible implementation of the second aspect, the second PFD further includes a third string, and the third string indicates that the PFD is a PFD generated by a preset device.

[0031] A third aspect of the present application is a data processing device, an acquisition unit configured to acquire a first packet flow description PFD, the first PFD including a first triplet and a first application ID, the acquisition unit is further configured to acquire a second PFD transmitted by a second device, the second PFD including a second triplet and a second application ID, a transmission unit configured to transmit a PFD set to a UDR based on the first PFD and the second PFD, the PFD set including at least one of the first PFD or the second PFD and providing a data processing device including.

[0032] In a possible implementation of the third aspect, the first PFD further includes a first string, the second PFD further includes a second string, the first string is used to describe the source of the first PFD, and the second string is used to describe the source of the second PFD.

[0033] In a possible implementation of the third aspect, the transmission unit is When it is determined that the first triplet is different from the second triplet and the first application ID is different from the second application ID, the first device sends a PFD set to the UDR, and the PFD set includes the first PFD and the second PFD, or When it is determined that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or when it is determined that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is different from the second string, and the first device determines that the first string indicates that the source of the first PFD is AF, and sends the PFD set to the UDR, and the PFD set contains the first PFD, or the first device determines that the first string indicates that the source of the first PFD is NWDAF, and sends the PFD set to the UDR, and the PFD set contains the second PFD. It is specifically configured in this way.

[0034] In a possible embodiment of the third aspect, the first PFD further includes first time information, and the second PFD further includes second time information.

[0035] The transmitting unit is, When the first triplet is determined to be different from the second triplet and the first application ID is the same as the second application ID, or when the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is the same as the second string, and based on the first and second time information, the first device determines that the first PFD was generated before the second PFD, and sends the PFD set to the UDR, the PFD set containing the second PFD, or the first device determines, based on the first and second time information, that the first PFD was generated after the second PFD, and sends the PFD set to the UDR, the PFD set containing the first PFD, or When it is determined that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on the first and second time information, that the first PFD expires before the second PFD and sends a PFD set to the UDR, the PFD set containing the second PFD, or the first device determines, based on the first and second time information, that the first PFD expires after the second PFD and sends a PFD set to the UDR, the PFD set containing the first PFD, It is specifically configured in this way.

[0036] In a possible embodiment of the third aspect, the first time information includes the expiration date of the first PFD and the generation date of the first PFD, or the validity period of the first PFD and the generation date of the first PFD, and the second time information includes the expiration date of the second PFD and the generation date of the second PFD, or the validity period of the second PFD and the generation date of the second PFD.

[0037] In a possible embodiment of the third aspect, the generation time of the first PFD is after the generation time of the second PFD.

[0038] The transmitting unit is, When the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is generated by AF, the first device sends a PFD set to the UDR, and the PFD set includes the first PFD and the second PFD, or When the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, then the first device sends a PFD set to the UDR, and the PFD set includes the first PFD. It is specifically configured in this way.

[0039] In a possible embodiment of the third aspect, the generation time of the first PFD is after the generation time of the second PFD.

[0040] The transmitting unit is, When the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, the first device sends a PFD set to the UDR, and the PFD set includes the first PFD, or When the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, the first device sends a PFD set to the UDR, and the PFD set includes the second PFD. It is specifically configured in this way.

[0041] In a possible embodiment of the third aspect, the second PFD further includes a third string indicating that the PFD is a PFD generated by a pre-configured device.

[0042] In a possible embodiment of the third aspect, the first device includes a network exposure function NEF, the second device includes an integrated data repository UDR, or the first device includes an application function AF, the second device includes an NWDAF.

[0043] In a possible embodiment of the third aspect, when the first device includes an NWDAF, the second device includes a UDR or NEF, and the first PFD is a PFD generated by the NWDAF, or when the first device includes an NEF, the second device includes a UDR.

[0044] A fourth aspect of this application is a data processing device, An acquisition unit configured to acquire a PFD information inquiry request sent by a first device, A transmission unit configured to send a second PFD to the first device, the second PFD including a second triplet and a second application ID, and Includes, The acquisition unit provides a data processing device that acquires a set of PFDs transmitted by a first device, the set of PFDs further configured to include at least one of a first PFD and a second PFD, the first PFD including a first triplet and a first application ID.

[0045] In a possible embodiment of the fourth aspect, the second PFD further includes a second string, the first PFD further includes a first string, the first string is used to describe the source of the first PFD, and the second string is used to describe the source of the second PFD.

[0046] In a possible embodiment of the fourth aspect, the first PFD further includes first time information, and the second PFD further includes second time information.

[0047] In a possible embodiment of the fourth aspect, the second PFD further includes a third string indicating that the PFD is a PFD generated by a pre-configured device.

[0048] A fifth aspect of this application provides a data processing device including a processor and memory. The memory is configured to store instructions. The processor is configured to execute instructions. When the processor executes instructions, a method according to the first aspect or any one of possible embodiments thereof is performed.

[0049] A sixth aspect of this application provides a data processing device including a processor and memory. The memory is configured to store instructions. The processor is configured to execute instructions. When the processor executes instructions, a method according to the second aspect or any one of possible embodiments thereof is performed.

[0050] A seventh aspect of this application provides a computer-readable storage medium containing a program. When the program is run on a computer, the computer is enabled to perform a method according to the first aspect or any one of possible embodiments thereof.

[0051] An eighth aspect of this application provides a computer-readable storage medium containing a program. When the program is run on a computer, the computer is enabled to perform a method according to the second aspect or any one of possible embodiments thereof.

[0052] A ninth aspect of this application provides a computer program product including instructions. When the computer program product is run on a computer, the computer is enabled to perform a method according to the first aspect or any possible embodiment thereof.

[0053] A tenth aspect of this application provides a computer program product including instructions. When the computer program product is run on a computer, the computer is enabled to perform a method according to the second aspect or any one of possible embodiments of the second aspect. [Brief explanation of the drawing]

[0054] [Figure 1] This is a diagram of the architecture of a 5G network according to one embodiment of this application. [Figure 2] This is a schematic flowchart of a data processing method according to one embodiment of this application. [Figure 3] This is another schematic flowchart of a data processing method according to one embodiment of this application. [Figure 4] This is another schematic flowchart of a data processing method according to one embodiment of this application. [Figure 5] This is a diagram of a PFD according to one embodiment of the present application. [Figure 6] This is another diagram of a PFD according to one embodiment of this application. [Figure 7] This is a schematic flowchart of a data processing method according to one embodiment of this application. [Figure 8] This is a diagram of a data processing device according to one embodiment of the present application. [Figure 9] Another diagram of a data processing device according to one embodiment of this application. [Figure 10] This is a diagram showing another structure of a data processing device according to one embodiment of this application. [Figure 11] This is a diagram showing another structure of a data processing device according to one embodiment of this application. [Modes for carrying out the invention]

[0055] The embodiments of this application will be described below with reference to the accompanying drawings. The terms used in the embodiments of this application are used solely to describe the specific embodiments of this application and are not intended to limit this application. Those skilled in the art will know that, with advancements in the technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application may be further applicable to similar technical problems.

[0056] In the specification, claims, and accompanying drawings of this application, terms such as “first” and “second” are intended to distinguish similar subjects, but do not necessarily indicate a specific order or sequence. It should be understood that these terms are interchangeable in appropriate contexts, and this is merely a method of distinction for describing subjects having the same attributes in the embodiments of this application. In addition, the terms “includes,” “contains,” and any other variations thereof constitute non-exclusive inclusion, such that a process, method, system, product, or device containing a set of units may include other units that are not necessarily limited to those units, are not expressly enumerated, or are specific to such a process, method, product, or device.

[0057] For a better understanding of the solution provided in this application, the architecture of the 5G network will be described first. Please refer to Figure 1. Figure 1 is a diagram of the architecture of a 5G network according to one embodiment of this application.

[0058] A 5G network includes NEF, network repository function (NRF), NWDAF, AF, policy control function (PCF), UDR, unified data management (UDM), access and mobility management function (AMF), SMF, binding support function (BSF), radio access network (RAN), UPF, data network (DN), and user equipment (UE).

[0059] Figure 1 shows the connectivity relationships between network elements in a 5G network. The NEF is configured to provide the AF with a secure path and the ability to provide network function IDs for opening services, and to retrieve information provided by the AF. The NEF includes NEF(PFDF). As a logical function of the NEF, NEF(PFDF) receives PFDs provided by the AF and PFDs provided by NWDAF, and stores the received PFDs in the UDR.

[0060] NWDAF is configured to collect data from network elements, third-party AFs, RANs, or network management systems, perform model training and inference based on the data from network elements, third-party AFs, RANs, or network management systems, and provide data analysis results to the consumer (network element or third-party AF). Based on the data analysis results, the consumer can select quality of service parameters for services, formulate traffic routing paths, or select background data transmission policies.

[0061] AF is configured to forward application-side requests to the network and provide application-side data to the network (e.g., QoS requests or user status event subscriptions).

[0062] The UDR is configured to store subscription data, policy data, capability disclosure-related data, and application data.

[0063] To improve network management efficiency, application identification technology classifies packets based on application or protocol features within the packet to obtain the Application File Format (PFD) of the sending application. The UPF manages traffic requests initiated by the application based on the application description in the PFD. For example, it controls user access to applications over the network based on application access management, for instance, allowing access to office-related applications and disabling access to video or game applications; it controls the available bandwidth for users to access applications over the network based on application bandwidth management, for example, limiting the maximum available bandwidth for video or game applications to 100M and ensuring a maximum available bandwidth of 200M for office applications; or it controls user access to various applications over various links based on the application's intelligent link selection function, for example, allowing access to office applications over high-speed links and access to video or game applications over low-speed links.

[0064] In the process where the UPF manages the network, the SMF needs to obtain PFD information corresponding to packet triplets from the UDR. For example, the PFD for application A stored in the UDR may be PFD1 provided by application A's AF, or PFD2 generated by the NWDAF by using auxiliary application discovery techniques to collect service traffic information for application A in the SMF or UPF. In some possible cases, the UDR may store both PFD1 and PFD2.

[0065] In certain application scenarios, when the UPF uses the SMF to retrieve one of the PFD1 and / or PFD2 of Application A provided by the NWDAF and / or AF within the UDR, and uses the retrieved PFD to manage Application A's traffic, multiple PFDs may exist within the UDR. Therefore, the SMF randomly selects one of the PFDs stored in the UDR corresponding to Application A to complete processing for Application A's traffic. The PFD provided by the NWDAF may differ from that provided by the AF, and the PFD generated by the NWDAF is retrieved by the NWDAF after the NWDAF has collected and analyzed service traffic information for Application A within the SMF or UPF. Thus, the accuracy of the PFD generated by the NWDAF is limited by the service traffic information for Application A that can be collected by the NWDAF. In scenarios where both the NWDAF and AF provide PFDs, how to help the SMF efficiently select the highest-confidence PFD from the UDR to improve the accuracy of the UPF in identifying the data traffic purpose of the application is now an urgent issue that needs to be addressed.

[0066] In consideration of the aforementioned problems, this application proposes that the PFDs stored in the UDR may be managed by the NEF to ensure that each application has a unique corresponding PFD stored in the UDR, and that the PFDs stored in the UDR corresponding to each application are the most reliable PFDs in multiple methods of obtaining PFDs, in order to reduce the difficulty of selecting the most reliable PFD from the UDR by the SMF.

[0067] The solutions provided in this application can be implemented in various ways, and the implementation methods will be described individually below with reference to the attached drawings.

[0068] First, a specific case in which the solution provided in this application is implemented in an NEF will be described. Please refer to Figure 2. Figure 2 is a schematic flowchart of a data processing method according to one embodiment of this application.

[0069] 201:NEF receives the first PFD transmitted by AF or NWDAF.

[0070] The NEF receives the first PFD transmitted by the AF or NWDAF, and the first PFD contains the first triplet and the first application ID.

[0071] Optionally, the first PFD may further contain a first string. The first string is used to describe the source of the first PFD, i.e., to describe the first PFD as a PFD generated by NWDAF or AF. For example, the first string is 0 or 1. When the first string is 0, it indicates that the first PFD is a PFD generated by AF. When the first string is 1, it indicates that the first PFD is a PFD generated by NWDAF.

[0072] Please note that the description of the specific content of the first string here is merely an example. In actual application, the first string may be AF or NWDAF. When the first PFD has multiple sources, the names of the other sources in the first PFD may be used directly for distinction, or different numbers may be used for distinction. This is not limited here.

[0073] Optionally, the first PFD may further include first time information, which is the time of creation of the first PFD and the validity period of the first PFD, or the time of creation of the first PFD and the expiration date of the first PFD.

[0074] Optionally, the first PFD may further include at least one of the following: a first flow descriptor, a first uniform resource locator (URL), and first domain name information. This is not limited here.

[0075] Please note that the description of the contents of the first PDF provided here is merely an example, and the first PDF may contain other content. This is not a limitation.

[0076] The NEF may obtain a first PFD from the AF, or from the NWDAF, or simultaneously from both the AF and the NWDAF.

[0077] For example, when NEF obtains the first PFD from AF, AF provides the first PFD to NEF using the PFD Management_Create / Update / Delete Request.

[0078] For example, when NEF obtains the first PFD from NWDAF, NEF sends an NWDAF analytics subscription packet, Nnwdaf_AnalyticsSubscription_Subscribe, to NWDAF to subscribe to PFD information from NWDAF.

[0079] After receiving the NWDAF analytics subscription packet sent by NEF, NWDAF sends the first PFD information to NEF using NWDAF Analytics Subscription Notification: Nnwdaf_AnalyticsSubscription_Notify.

[0080] It should be noted that the descriptions of packet exchanges between the NEF and the AF, and between the NEF and the NWDAF, when the NEF obtains the first PFD are merely illustrative. In actual application, any packet format and content pre-agreed by the NEF and NWDAF may be used to trigger the NWDAF to report the most recent first PFD within the NWDAF to the NEF. This is not limited here.

[0081] Specifically, there are three possible cases for the first PFD information transmitted to the NEF by the NWDAF:

[0082] Case 1: The first PFD is a PFD generated by NWDAF.

[0083] When the first PFD is a PFD generated by NWDAF, before sending the first PFD information to the NEF, NWDAF collects traffic information from the UPF corresponding to at least one application ID. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form the first PFD.

[0084] Case 2: The first PFD is a PFD generated by NWDAF and a PFD collected by NWDAF.

[0085] When the first PFD is a PFD generated by NWDAF and a PFD collected by NWDAF, before sending the first PFD information to NEF, NWDAF collects traffic information from UPF corresponding to at least one application ID. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID in order to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form a set of PFDs generated by NWDAF.

[0086] NWDAF may send further event exposure subscription packets, Nnef_EventExposure_Subscribe, to the NEF to collect PFDs that can be successfully used by the NEF. The NEF uses event exposure notification packets, Nnef_EventExposure_notify, to report to NWDAF the PFDs currently in use by the NEF.

[0087] NWDAF may send further data management retrieval request packets, Nadrf_DataManagement_RetrievalRequest, to the ADRF to retrieve the PFDs stored in the ADRF.

[0088] Based on the aforementioned cases, the first PFD may include a set of PFDs generated by the NWDAF and PFDs currently in use in the NEF, a set of PFDs generated by the NWDAF and PFDs stored in the ADRF, or a set of PFDs generated by the NWDAF, PFDs currently in use in the NEF, and PFDs stored in the ADRF.

[0089] Furthermore, the first PFD may also be a PFD obtained by performing deduplication on the PFD set generated by NWDAF and the PFD currently in use in NEF, the PFD set generated by NWDAF and the PFD stored in ADRF, or the PFD set generated by NWDAF, the PFD currently in use in NEF, and the PFD stored in ADRF.

[0090] Case 3: The first PFD is a PFD generated by NWDAF and a PFD collected by NWDAF that has not been reported to NEF.

[0091] When the first PFD is a PFD generated by NWDAF and a PFD collected by NWDAF, before sending the first PFD information to NEF, NWDAF collects traffic information from UPF corresponding to at least one application ID. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID in order to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form a set of PFDs generated by NWDAF.

[0092] NWDAF may send further event exposure subscription packets, Nnef_EventExposure_Subscribe, to the NEF to collect PFDs that can be successfully used by the NEF. The NEF uses event exposure notification packets, Nnef_EventExposure_notify, to report to NWDAF the PFDs currently in use by the NEF.

[0093] NWDAF may send further data management retrieval request packets, Nadrf_DataManagement_RetrievalRequest, to the ADRF to retrieve the PFDs stored in the ADRF.

[0094] Based on the aforementioned cases, the first PFD may include PFDs from the PFD set generated by NWDAF and PFDs currently in use at NEF that have not been reported to NEF, PFDs from the PFD set generated by NWDAF and PFDs stored in ADRF that have not been reported to NEF, or PFDs from the PFD set generated by NWDAF, PFDs currently in use at NEF, and PFDs stored in ADRF that have not been reported to NEF.

[0095] Please note that the above description of the first PFD is merely an example. In actual application, the first PFD may be any PFD transmitted to the NEF by the AF or any PFD transmitted to the NEF by the NWDAF. This is not limited here.

[0096] 202:NEF sends a PFD information inquiry request to UDR.

[0097] After the NEF has received the first PFD transmitted by the AF and / or the first PFD transmitted by the NWDAF, the NEF sends a PFD information query request to the UDR to query the PFD information stored in the UDR.

[0098] 203:NEF receives the second PFD sent by UDR.

[0099] After the NEF sends a PFD information inquiry request to the UDR, the NEF retrieves a second PFD sent by the UDR, which includes a second triplet and a second application ID, and the second PFD includes all PFDs stored in the UDR.

[0100] Optionally, the second PFD may further contain a second string, which is used to describe the source of the second PFD, i.e., to describe the second PFD as a PFD generated by NWDAF or AF. For example, the second string is 0 or 1. When the second string is 0, it indicates that the second PFD is a PFD generated by AF. When the second string is 1, it indicates that the second PFD is a PFD generated by NWDAF.

[0101] Please note that the explanation of the specific content of the second string provided here is merely an example. In actual application, the second string may be AF or NWDAF. When the second PFD has multiple sources, the names of the other sources in the second PFD may be used directly for distinction, or different numbers may be used for distinction. This is not limited here.

[0102] Optionally, the second PFD may further include second time information, which is the time of creation of the second PFD and the validity period of the second PFD, or the time of creation of the second PFD and the expiration date of the second PFD.

[0103] Please note that the description of the contents of the second PFD provided here is merely an example, and the second PFD may include other content. This is not a limitation.

[0104] 204: The NEF sends the PFD set to the UDR based on the first PFD and the second PFD.

[0105] After obtaining the first and second PFDs, the NEF sends a set of PFDs to the UDR based on the contents of the first and second PFDs, the set of PFDs including at least one of the first or second PFDs.

[0106] If the NEF optionally decides that the first PFD is different from the second PFD, it sends a PFD set to the UDR, which includes the first and second PFDs. Specifically, as described herein, the difference between the first PFD and the second PFD means that the first triplet is different from the second triplet, and the first application ID is different from the second application ID.

[0107] Optionally, if the first PFD contains the first string and the second PFD contains the second string, the NEF determines that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, or the first triplet is different from the second triplet and the first application ID is the same as the second application ID, and then the NEF determines that the first string is different from the second string. If the first string indicates that the source of the first PFD is AF, the PFD set sent by the NEF to the UDR contains the first PFD. Alternatively, if the first string indicates that the source of the second PFD is AF, the PFD set sent by the NEF to the UDR contains the second PFD.

[0108] Optionally, if the first PFD contains a first string and first time information, and the second PFD contains a second string and second time information, the NEF determines that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, or that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, and determines that the first string is the same as the second string. If the NEF determines, based on the first and second time information, that the generation time of the first PFD is before the generation time of the second PFD, the PFD set sent by the NEF to the UDR includes the second PFD. Alternatively, if the NEF determines, based on the first and second time information, that the generation time of the first PFD is after the generation time of the second PFD, the PFD set sent by the NEF to the UDR includes the second PFD.

[0109] Optionally, if the first PFD contains a first string and first time information, and the second PFD contains a second string and second time information, the NEF determines that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID. If the NEF determines that the expiration date of the first PFD is after the expiration date of the second PFD, the PFD set sent by the NEF to the UDR includes the first PFD. Alternatively, if the NEF determines that the expiration date of the first PFD is before the expiration date of the second PFD, the PFD set sent by the NEF to the UDR includes the second PFD.

[0110] The NEF may determine the contents of the PFD set sent to the UDR by determining whether the first triplet is the same as the second triplet, whether the first application ID is the same as the second application ID, whether the first string is the same as the second string, and the order of the first and second time information, or it may otherwise obtain the PFD set for a specific case that the NEF sends to the UDR in the aforementioned multiple cases. This is not limited here.

[0111] 205: The UDR updates the second PFD based on the PFD set.

[0112] After receiving the PFD set transmitted by the NEF, the UDR updates a second PFD stored in the UDR based on the PFDs in the PFD set.

[0113] For example, a PFD set contains a first PFD. To retrieve the updated second PFD, the UDR removes from the PFD information any PFDs whose triplets are the same as the first triplets and / or whose application IDs are the same as the first triplets, and stores the first PFD.

[0114] Optionally, the example continues to use the case where the PFD set includes a first PFD. The UDR deletes the PFD information stored in the UDR and stores the first PFD in order to obtain the updated second PFD.

[0115] Please note that the descriptions of the PFDs included in the PFD set and the descriptions of updating PFD information by UDRs based on the PFD set are for illustrative purposes only. In actual application, configuration should be performed by referring to specific application scenarios. This is not limited here.

[0116] In this embodiment of the present application, after obtaining a first PFD transmitted by the AF and / or a first PFD transmitted by the NWDAF, the NEF obtains a second PFD from the UDR and transmits a PFD set to the UDR based on the first and second PFDs, thereby enabling the UDR to update the PFD information in the second PFD based on the PFD set. The PFD set includes at least one of the first and second PFDs, the first PFD includes a first triplet and a first application ID, and the second PFD includes a second triplet and a second application ID. In this way, the SMF can determine a unique PFD based on the ID of the application to be processed or the triplet information of the application to be processed, and it is ensured that the PFD is the highest-confidence PFD currently stored in the UDR corresponding to the application to be processed. This reduces the complexity of the SMF's operation by reducing the operation of obtaining the highest-confidence PFD from multiple PFDs stored in the UDR corresponding to the application to be processed.

[0117] Next, a specific case in which the solution provided in this application is implemented in AF will be described. Please refer to Figure 3. Figure 3 is another schematic flowchart of a data processing method according to one embodiment of this application.

[0118] 301:AF uses NEF to send NWDAF analysis subscription packets to NWDAF.

[0119] AF uses NEF to send an NWDAF analytics subscription packet (Nnwdaf_AnalyticsSubscription_Subscribe) to NWDAF in order to subscribe to a second PFD stored in NWDAF.

[0120] It should be noted that the description here of AF obtaining the latest PFD information in NWDAF using NWDAF analysis subscription packets sent to NWDAF by NEF is merely an example. In actual application, any packet format and content pre-agreed by AF and NWDAF may be used to trigger NWDAF to report a second PFD stored in NWDAF to AF. This is not limited here.

[0121] Please note that there is no specific order for performing steps 301 and 302, and the explanation here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario.

[0122] 302: AF obtains the first PFD.

[0123] The AF obtains the first PFD generated by the AF, which includes the first triplet and the first application ID.

[0124] Optionally, the first PFD may further contain a first string. The first string is used to describe the source of the first PFD, i.e., to describe the first PFD as a PFD generated by NWDAF or AF. For example, the first string is 0 or 1. When the first string is 0, it indicates that the first PFD is a PFD generated by AF. When the first string is 1, it indicates that the first PFD is a PFD generated by NWDAF.

[0125] Please note that the description of the specific content of the first string here is merely an example. In actual application, the first string may be AF or NWDAF. When the first PFD has multiple sources, the names of the other sources in the first PFD may be used directly for distinction, or different numbers may be used for distinction. This is not limited here.

[0126] Optionally, the first PFD may further include first time information, which is the time of creation of the first PFD and the validity period of the first PFD, or the time of creation of the first PFD and the expiration date of the first PFD.

[0127] Optionally, the first PFD may further include at least one of the following: a first flow descriptor, a first URL, and first domain name information. This is not limited here.

[0128] Please note that the description of the contents of the first PDF provided here is merely an example, and the first PDF may contain other content. This is not a limitation.

[0129] Please note that there is no specific order for performing steps 302, 301, and 303, and the explanation here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario.

[0130] 303:AF uses NEF to receive the second PFD transmitted by NWDAF.

[0131] After AF sends an NWDAF analytics subscription packet to NWDAF using NEF, AF uses NEF to retrieve a second PFD sent by NWDAF. The second PFD is retrieved using NWDAF Analytics Subscription Notify (Nnwdaf_AnalyticsSubscription_Notify). The second PFD contains a second triplet and a second application ID, and the second PFD contains all PFDs stored in the UDR.

[0132] Optionally, the second PFD may further contain a second string, which is used to describe the source of the second PFD, i.e., to describe the second PFD as a PFD generated by NWDAF or AF. For example, the second string is 0 or 1. When the second string is 0, it indicates that the second PFD is a PFD generated by AF. When the second string is 1, it indicates that the second PFD is a PFD generated by NWDAF.

[0133] Please note that the explanation of the specific content of the second string provided here is merely an example. In actual application, the second string may be AF or NWDAF. When the second PFD has multiple sources, the names of the other sources in the second PFD may be used directly for distinction, or different numbers may be used for distinction. This is not limited here.

[0134] Optionally, the second PFD may further include second time information, which is the time of creation of the second PFD and the validity period of the second PFD, or the time of creation of the second PFD and the expiration date of the second PFD.

[0135] Please note that the description of the contents of the second PFD provided here is merely an example, and the second PFD may include other content. This is not a limitation.

[0136] It should be noted that the description here of packet exchange between AF and NWDAF using NEF when AF obtains a second PFD is merely an example. In actual application, any packet format and content pre-agreed by AF and NWDAF may be used to trigger NWDAF to report the latest second PFD within NWDAF to AF using NEF. This is not limited here.

[0137] Specifically, there are three possible cases for the second PFD information transmitted to AF by NWDAF using NEF:

[0138] Case 1: The second PFD is a PFD generated by NWDAF.

[0139] When the second PFD is a PFD generated by NWDAF, before sending the second PFD information to AF using NEF, NWDAF collects traffic information from UPF corresponding to at least one application ID. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form the second PFD.

[0140] Case 2: The second PFD is the PFD generated by NWDAF and the PFD collected by NWDAF.

[0141] When the second PFD is a PFD generated by NWDAF and a PFD collected by NWDAF, NWDAF collects traffic information from UPF corresponding to at least one application ID before sending the second PFD information to AF using NEF. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID in order to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form a set of PFDs generated by NWDAF.

[0142] Optionally, NWDAF may send further Event Exposure Subscription packets Nnef_EventExposure_Subscribe to the NEF to collect PFDs that can be successfully used by the NEF. The NEF uses Event Exposure Notification packets Nnef_EventExposure_notify to report to NWDAF the PFDs currently in use by the NEF.

[0143] Optionally, the NWDAF may send an additional Data Management Retrieval Request packet, Nadrf_DataManagement_RetrievalRequest, to the ADRF to retrieve the PFD stored in the ADRF.

[0144] Based on the aforementioned cases, the second PFD may include a set of PFDs generated by the NWDAF and PFDs currently in use in the NEF, a set of PFDs generated by the NWDAF and PFDs stored in the ADRF, or a set of PFDs generated by the NWDAF, PFDs currently in use in the NEF, and PFDs stored in the ADRF.

[0145] Furthermore, the second PFD may be a PFD obtained by performing deduplication on the PFD set generated by NWDAF and the PFD currently in use in NEF, the PFD set generated by NWDAF and the PFD stored in ADRF, or the PFD set generated by NWDAF, the PFD currently in use in NEF, and the PFD stored in ADRF.

[0146] Case 3: The second PFD is a PFD generated by NWDAF and a PFD collected by NWDAF that has not been reported to NEF.

[0147] When the second PFD is a PFD generated by NWDAF and a PFD collected by NWDAF, NWDAF collects traffic information from UPF corresponding to at least one application ID before sending the second PFD information to AF using NEF. NWDAF performs derivation using a machine learning algorithm based on the traffic information corresponding to at least one application ID in order to obtain a PFD that can describe the application corresponding to the application ID. All PFDs corresponding to applications within at least one application ID form a set of PFDs generated by NWDAF.

[0148] NWDAF may send further event exposure subscription packets, Nnef_EventExposure_Subscribe, to the NEF to collect PFDs that can be successfully used by the NEF. The NEF uses event exposure notification packets, Nnef_EventExposure_notify, to report to NWDAF the PFDs currently in use by the NEF.

[0149] NWDAF may send further data management retrieval request packets, Nadrf_DataManagement_RetrievalRequest, to the ADRF to retrieve the PFDs stored in the ADRF.

[0150] Based on the aforementioned cases, the second PFD may include PFDs from the PFD set generated by NWDAF and PFDs currently in use at NEF that have not been reported to NEF, PFDs from the PFD set generated by NWDAF and PFDs stored in ADRF that have not been reported to NEF, or PFDs from the PFD set generated by NWDAF, PFDs currently in use at NEF, and PFDs stored in ADRF that have not been reported to NEF.

[0151] Please note that the above description of the second PFD is merely an example. In actual application, the second PFD may be any PFD generated by the AF and / or any PFD sent to the AF by the NWDAF using the NEF. This is not limited here.

[0152] Please note that there is no specific order for performing steps 302 and 303, and the explanation provided here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario.

[0153] 304:AF sends the PFD set to the UDR using NEF based on the first PFD and the second PFD.

[0154] After obtaining the first and second PFDs, the AF sends a set of PFDs to the UDR using the NEF based on the contents of the first and second PFDs, the set of PFDs including at least one of the first or second PFDs.

[0155] Optionally, when the AF determines that the first PFD is different from the second PFD, the AF sends a set of PFDs to the UDR using the NEF, and the set of PFDs includes the first and second PFDs. Specifically, as described herein, the difference between the first PFD and the second PFD means that the first triplet is different from the second triplet, and the first application ID is different from the second application ID.

[0156] Optionally, if the first PFD contains the first string and the second PFD contains the second string, AF determines that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, or the first triplet is different from the second triplet and the first application ID is the same as the second application ID, and then AF determines that the first string is different from the second string. If the first string indicates that AF is the source of the first PFD, the PFD set sent by AF to the UDR using NEF contains the first PFD. Alternatively, if the first string indicates that AF is the source of the second PFD, the PFD set sent by AF to the UDR using NEF contains the second PFD.

[0157] Optionally, if the first PFD contains a first string and first time information, and the second PFD contains a second string and second time information, the AF determines that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, or that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, and that the first string is the same as the second string. If the AF determines, based on the first and second time information, that the generation time of the first PFD is before the generation time of the second PFD, the PFD set sent by the AF to the UDR using the NEF includes the second PFD. Alternatively, if the AF determines, based on the first and second time information, that the generation time of the first PFD is after the generation time of the second PFD, the PFD set sent by the AF to the UDR using the NEF includes the second PFD.

[0158] Optionally, if the first PFD contains a first string and first time information, and the second PFD contains a second string and second time information, the AF determines that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID. If the AF determines that the expiration date of the first PFD is after the expiration date of the second PFD, the PFD set sent by the AF to the UDR using the NEF includes the first PFD. Alternatively, if the AF determines that the expiration date of the first PFD is before the expiration date of the second PFD, the PFD set sent by the AF to the UDR using the NEF includes the second PFD.

[0159] The AF may determine the contents of the PFD set sent to the UDR by determining whether the first triplet is the same as the second triplet, whether the first application ID is the same as the second application ID, and whether the first string is the same as the second string, and by determining the order of the generation times of the first and second PFDs and / or the order of the expiration times of the first and second PFDs based on the first and second time information, or by other means, it may obtain the PFD set for a particular case that is sent to the UDR by the NEF in the aforementioned multiple cases. This is not limited herein.

[0160] 305:UDR updates the second PFD based on the PFD set.

[0161] After receiving the PFD set transmitted by the NEF, the UDR updates a second PFD stored in the UDR based on the PFDs in the PFD set.

[0162] For example, a PFD set contains a first PFD. To retrieve the updated second PFD, the UDR removes from the PFD information any PFDs whose triplets are the same as the first triplets and / or whose application IDs are the same as the first triplets, and stores the first PFD.

[0163] Optionally, the example continues to use the case where the PFD set includes a first PFD. The UDR deletes the PFD information stored in the UDR and stores the first PFD in order to obtain the updated second PFD.

[0164] Please note that the descriptions of the PFDs included in the PFD set and the descriptions of updating PFD information by UDRs based on the PFD set are for illustrative purposes only. In actual application, configuration should be performed by referring to specific application scenarios. This is not limited here.

[0165] In this embodiment of the present application, the AF may obtain a first PFD generated by the AF, obtain a second PFD from the NWDAF using the NEF after obtaining the first PFD, and send a set of PFDs to the UDR using the NEF based on the first and second PFDs, the set of PFDs including at least one of the first and second PFDs, the first PFD including a first triplet and a first application ID, and the second PFD including a second triplet and a second application ID. In this way, the UDR can efficiently update the PFD information in the second PFD based on the PFDs. Processing the first and second PFDs in the AF and sending the set of PFDs to the UDR reduces the computational pressure on the NEF and improves the mobility of PFD redundancy processing in the network.

[0166] In another embodiment of the solution provided in this application, the NWDAF may retrieve a second PFD stored in the UDR, collect application traffic information from the UPF, and retrieve a first PFD by analysis based on the application traffic information. After retrieving the second and first PFDs, the NWDAF analyzes the first and second PFDs, uses a second identifier carried in the second PFD to determine whether to update the second PFD with the first PFD, and transmits at least one of the first or second PFDs to the UDR for storage for subsequent use. For specific embodiments, please refer to Figure 4, which is another schematic flowchart of a data processing method according to one embodiment of this application.

[0167] 401:NEF sends a PFD information subscription packet to NWDAF.

[0168] The NEF sends a PFD information request packet to the NWDAF, which carries a second application ID.

[0169] For example, the PFD information subscription packet may be Nnwdaf_AnalyticsSubscription_Subscribe.

[0170] The description of the second application ID carried in the PFD request packet here is merely an example, and it should be understood that the PFD information subscription packet does not necessarily have to carry an application ID. This is not a limitation here.

[0171] 402:NWDAF uses NEF to send a PFD information inquiry request to the UDR.

[0172] After obtaining the PFD information subscription packet from the NEF, the NWDAF uses the NEF to send a PFD information query request to the UDR, which carries a second application ID.

[0173] For example, the NWDAF sends a PFD information request to the UDR in two steps: first, the NWDAF sends the PFD information request to the NEF, and then the NEF forwards the PFD information request to the UDR.

[0174] The PFD information query request sent to the NEF by NWDAF may also be Nnef_PFDManagement_Fetch(Event ID=In use PFDs,Event Filter=Application ID).

[0175] The PFD information query request forwarded to the UDR by the NEF may also be Nudr_DM_Query(Data Key=ApplicationID).

[0176] It should be understood that the description of the PFD information request content here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0177] 403:UDR sends a second PFD to NWDAF using NEF.

[0178] After the UDR receives a PFD information query request from the NWDAF, the UDR uses the NEF to send a second PFD to the NWDAF, which includes a second application ID, a second triplet, and a second string, the second string being used to describe the source of the second PFD. For example, the second string could indicate whether the source of the second PFD is the NWDAF or the AF. This is not limited here.

[0179] Optionally, the second PFD may further include a second URL and a second DN.

[0180] Specifically, in order to obtain a second PFD, the UDR searches through all the PFD information stored in the UDR for the PFD whose application ID matches the second application ID, and then uses the NEF to send the second PFD to the NWDAF.

[0181] For example, the UDR sends a second PFD to the NWDAF using the NEF in two steps: first, the UDR sends the second PFD to the NEF, and then the NEF forwards the second PFD to the NWDAF.

[0182] The UDR sending the second PFD to the NEF may be done using Nudr_DM_Notify(PFD information(PFD,source), and the NEF forwarding the second PFD to the NWDAF may be done using Nnef_PFDManagement_Fetch Response(PFD information(PFD,source).

[0183] It should be understood that the description here of the UDR using NEF to send a second PFD to the NWDAF is merely an example. In actual application, the configuration should be performed referring to a specific application scenario. This is not limited here.

[0184] For example, the format of the PFD stored in the UDR may differ from the format of the PFD in the transfer process. For example, when multiple PFDs are stored in the UDR, the format of the PFDs may be a list or a table. Here, a table is used as an example. For a specific format of the table, please refer to Figure 5. Figure 5 is a diagram of a PFD according to one embodiment of the present application.

[0185] From Figure 5, it can be seen that when PFDs are stored in the UDR, PFDs associated with an application are uniformly stored. For example, the second application ID corresponds to the PFD ID list, triplet list, URL list, DN list, and source information list. The PFD ID list stores multiple PFD IDs, for example, a first PFD ID, a second PFD ID, and a third PFD ID. These PFD IDs may be unique within the application or globally unique; this is not limited here.

[0186] The triplet list stores multiple triplets, such as a first triplet, a second triplet, and a third triplet.

[0187] The URL list stores multiple URLs, such as the first URL, the second URL, and the third URL.

[0188] The DN list stores multiple DNs, such as the first DN, the second DN, and the third DN.

[0189] The Source information list stores multiple strings, such as the first string, the second string, and the third string.

[0190] As shown in Figure 5, when a PFD is stored in a UDR, it also includes the correspondence between elements in the list. The specific storage method is not limited here.

[0191] In another possible case, the storage configuration of the PFD in the UDR is shown in Figure 6. Figure 6 is another diagram of the PFD according to one embodiment of the present application.

[0192] From Figure 6, it can be seen that when multiple PFDs are stored in the UDR, and when PFDs associated with an application are stored uniformly, further classification is performed based on the source of the PFD.

[0193] For example, the source for application 1 includes NWDAF and AF, the source for PFD1 and PFD2 is NWDAF, and the source for PFD3 and PFD4 is AF.

[0194] In UDR storage, the storage format for Application 1 and the PFDs corresponding to Application 1 is shown in Figure 6. The application ID corresponding to Application 1 is applicationID1, and PFDs whose source is NWDAF are marked with string 1 in the source field, while PFDs whose source is AF are marked with string 2 in the source field. In addition, the PFD information field stores information about PFD1, PFD2, PFD3, and PFD4.

[0195] Specifically, regarding information about PFD1, PFD ID1, Triplet 1, URL1, and DN1 may be stored in the PFD information field; regarding information about PFD2, PFD ID2, Triplet 2, URL2, and DN2 may be stored in the PFD information field; regarding information about PFD3, PFD ID3, Triplet 3, URL3, and DN3 may be stored in the PFD information field; and regarding information about PFD4, PFD ID4, Triplet 4, URL4, and DN4 may be stored in the PFD information field.

[0196] As shown in Figure 6, when a PFD is stored in a UDR, the correspondence between elements is further implied. The specific storage method is not limited here.

[0197] It should be understood that the description of the PFD storage format in the UDR provided here is merely illustrative. In actual application, the specific storage format and contents of the PFD may be adjusted by referring to the specific application scenario and requirements to facilitate memorization. This is not limited here.

[0198] The representation format of the second PFD in the transfer process is as follows: Second PFD ID, The second triplet, The second URL, The second DN, and Second string (second source information) That is the case.

[0199] It should be understood that the description of the second PFD's different form here is merely illustrative. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0200] 404:NWDAF generates a first PFD based on the traffic characteristics information of the first application collected by UPF.

[0201] NWDAF generates a first PFD based on the traffic characteristics information of a first application collected by UPF. The first PFD contains a first triplet, a first application ID, and a first string. The first string is used to describe the source of the first PFD. For example, the first string indicates that the source of the first PFD is NWDAF or AF. The application ID of the first application contains the first application ID, and both the first and second PFDs are PFDs corresponding to the first application. Therefore, the application ID of the first application contains the application ID of the second application.

[0202] Optionally, since the application ID of the first application changes during the port switching process, the application IDs of the first and second applications may be the same or different. This is not a restriction here.

[0203] Optionally, the first PFD may further include the first URL and the first DN.

[0204] The form of the first PFD in the transfer process and the form of the first PFD stored in the UDR are the same as the form of the second PFD. Further details are not provided here.

[0205] 405:NWDAF analyzes the first and second PFDs to generate a PFD set.

[0206] After obtaining the first PFD and the second PFD, NWDAF obtains a PFD set by analyzing the contents of the first PFD and the second PFD, the PFD set containing at least one of the first PFD and the second PFD.

[0207] In this embodiment of the present application, the first PFD is generated by the NWDAF, the second PFD is a PFD obtained by the NWDAF from the UDR using the NEF, and the NWDAF obtains the second PFD using the NEF before the NWDAF generates the first PFD. Thus, the first PFD is a newer PFD than the second PFD.

[0208] Furthermore, in more feasible cases, the first PFD may further carry first time information, and the second PFD may further carry second time information, and the NWDAF may determine the relevance of the first and second PFDs based on the first and second time information. This is not limited here.

[0209] Specifically, when analyzing the first and second PFDs, NWDAF performs deduplication on the first and second PFDs by analyzing whether the first application ID is the same as the second application ID, whether the first triplet is the same as the second triplet, whether the first URL is the same as the second URL, whether the first DN is the same as the second DN, and whether the first string is the same as the second string. The definition of whether the first URL is the same as the second URL may be that all the content in the URL is exactly the same, or that some selected features in the first URL, such as the host name, are the same as those in the second URL. If the selected features are the same, the first URL is considered the same as the second URL; otherwise, the first URL is considered different from the second URL. This is not limited here.

[0210] The deduplication process includes the following four scenarios:

[0211] When the first application ID of the first PFD is the same as the second application ID of the second PFD, and some fields of the PFDs are different, if the first string indicates that the source of the first PFD is NWDAF and the second string indicates that the source of the second PFD is AF, then some fields of the PFDs may be considered different when at least one of the following occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the PFD set includes the first PFD and the second PFD. In some cases, the PFD set does not need to be sent to the UDR, as it is only necessary to inform the UDR that a PFD needs to be updated or added. This is not limited here. For example, information regarding the addition of the first PFD may be forwarded to the UDR using an add packet, or information regarding the addition of the first PFD may be forwarded to the UDR using an add packet, and information regarding the update of the second PFD may be forwarded to the UDR using an update packet. This is not restricted here.

[0212] When the first application ID is the same as the second application ID, and some fields of the PFD are different, if the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, then some fields of the PFD may be considered different, and the PFD set includes the first PFD, when at least one of the following occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN. In specific implementation, the second PFD may directly replace the first PFD, or the second PFD may be updated based on the parts of the first PFD that are different from the second PFD, and the updated content is updated in the PFD set. For example, when a second PFD carries a second PFD ID, the PFD set further includes the correspondence between the first PFD and the second PFD ID, and the UDR is notified to replace the second PFD with the first PFD using an update packet, or the second PFD may remain unchanged and the first PFD is added to the UDR. This is not limited here.

[0213] The PFD set includes the first PFD when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF. In specific implementation, the second PFD may directly replace the first PFD, or the second PFD may be updated based on a portion of the first PFD that is different from the second PFD, and the updated content is updated in the PFD set. For example, when the second PFD carries the second PFD ID, the PFD set includes the correspondence between the first PFD and the second PFD ID, and the UDR is notified to replace the second PFD with the first PFD using the update packet. This is not limited here.

[0214] A PFD set includes a second PFD when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF. In specific implementations, PFD updates do not need to be performed at the UDR. In some cases, the PFD set does not need to be sent to the UDR, as it only notifies the UDR that a PFD needs to be updated or added. This is not limited here.

[0215] In this embodiment of the present application, when NWDAF analyzes a first PFD and a second PFD to generate a PFD set, the main principle followed is as follows: when the first PFD competes with the second PFD (i.e., when the first PFD and the second PFD are repeated), if there are PFDs in the first and second PFDs whose source is AF, then the PFD whose source is AF is unconditionally reserved. If the PFDs have the same source, the most recent PFD is reserved preferentially. If the PFD carries time information, the timeliness of the PFD is determined based on the time information. If the PFD does not carry time information, the PFD obtained directly from the NWDAF is the most recent by default and is reserved preferentially.

[0216] It should be understood that the specific basis and results of analyzing the first and second PFDs by NWDAF to generate a PFD set described here are merely illustrative. In actual application, the PFD set may be obtained by one or more decision methods or by analysis from different perspectives. This is not limited here.

[0217] Furthermore, since the UDR sends a second PFD to the NWDAF in step 403, after the PFD set is generated, the NWDAF may further update the PFD set based on the second PFD to obtain an updated PFD set. The updated PFD set may include only the parts that need to be changed from the second PFD, and the contents of these parts that need to be changed are identified.

[0218] For example, when a PFD set includes a first PFD and a second PFD, after the PFD set is updated based on the second PFD, the updated PFD set includes the first PFD and an incremental update identifier, which instructs the NEF to directly add the contents of the updated PFD set to the UDR after receiving the updated PFD set. The specific format and contents of the incremental update identifier are not limited here.

[0219] Alternatively, when a PFD set includes a second PFD, after the PFD set is updated based on the second PFD, the updated PFD set will only contain the incremental update identifier.

[0220] Alternatively, when a PFD set includes a first PFD, after the PFD set is updated based on the second PFD, the updated PFD set includes the first PFD and a delta update identifier, the delta update identifier instructing the UDR to remove the second PFD. The specific format and content of the delta update identifier are not limited here.

[0221] It should be understood that the explanation of how to update specific content within a PFD set here is merely an example. In actual application, identification should be performed by referring to a specific application scenario. This is not limited here.

[0222] In this embodiment of the present application, PFD set transfer for PFD delta or PFD increment in UDR reduces the bandwidth occupied for PFD transfer, saves network resources, and improves information transfer efficiency.

[0223] 406: NWDAF sends the PFD set to NEF.

[0224] After NWDAF analyzes the first and second PFDs to generate a PFD set, NWDAF sends the PFD set to NEF, which includes at least one of the first and second PFDs.

[0225] Specifically, NWDAF sending a PFD set to NEF may also be done via Nnwdaf_AnalyticsSubscription_Notify(Derived PFD info).

[0226] It should be understood that the description of the PFD set transmission method here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0227] 407:NEF sends the acquired PFD set to the UDR.

[0228] After obtaining the PFD set from the NWDAF, the NEF sends the PFD set to the UDR.

[0229] Specifically, sending the PFD set obtained by NEF to the UDR can also be done via Nudr_DM_Update / Create Request / Response.

[0230] It should be understood that the description of the PFD set transmission method here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0231] In this embodiment of the present application, the NWDAF collects a second PFD stored in the UDR, generates a first PFD based on application traffic information, analyzes the first and second PFDs to generate a PFD set, and transmits the PFD set to the UDR, thereby enabling the UDR to update the PFD information in the second PFD based on the PFD set. The PFD set includes at least one of the first and second PFDs to ensure that the PFD with the highest confidence is stored in the UDR for later selection when there are multiple relevant PFDs. This improves the reliability of the solution and also simplifies the operation when a PFD is subsequently selected by another network element.

[0232] In another embodiment of the solution provided in this application, the NWDAF may retrieve a second PFD stored in the UDR, collect application traffic information from the UPF, and retrieve a first PFD by analysis based on the application traffic information. After retrieving the second and first PFDs, the NWDAF transmits the first and second PFDs to the NEF. The NEF analyzes the first and second PFDs, uses a second identifier carried in the second PFD to determine whether to update the second PFD with the first PFD, and transmits at least one of the first or second PFDs to the UDR for storage for subsequent use. For specific embodiments, please refer to Figure 7, which is a schematic flowchart of a data processing method according to one embodiment of this application.

[0233] 701:NEF sends the PFD information subscription packet to NWDAF.

[0234] 702:NWDAF uses NEF to send a PFD information inquiry request to the UDR.

[0235] 703:UDR uses NEF to send a second PFD to NWDAF.

[0236] 704:NWDAF generates a first PFD based on the traffic characteristics information of the first application collected by UPF.

[0237] It can be understood that the embodiments of steps 701 to 704 are similar to the embodiments of steps 401 to 404 in Figure 4. This is not limited here.

[0238] 705: NWDAF transmits the first PFD and the second PFD to NEF.

[0239] After obtaining the first and second PFDs, NWDAF transmits the first and second PFDs to NEF.

[0240] Specifically, NWDAF sending the first and second PFDs to NEF may be done via Nnwdaf_AnalyticsSubscription_Notify(Derived PFD info).

[0241] It should be understood that the description of the specific transfer pattern in which the NWDAF sends the first and second PFDs to the NEF is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0242] 706:NEF analyzes the first and second PFDs to generate a PFD set.

[0243] After obtaining the first PFD and the second PFD, the NEF obtains a PFD set by analyzing the contents of the first PFD and the second PFD, the PFD set containing at least one of the first PFD and the second PFD.

[0244] In this embodiment of the present application, the first PFD is generated by NWDAF, the second PFD is a PFD obtained by NWDAF from UDR using NEF, and NWDAF obtains the second PFD using NEF before NWDAF. Thus, the first PFD is a newer PFD than the second PFD.

[0245] Furthermore, in more feasible cases, the first PFD may further carry first time information, and the second PFD may further carry second time information, and the NEF may determine the relevance of the first and second PFDs based on the first and second time information. This is not limited here.

[0246] Specifically, when analyzing the first and second PFDs, NEF analyzes whether the first application ID is the same as the second application ID, whether the first triplet is the same as the second triplet, whether the first URL is the same as the second URL, whether the first DN is the same as the second DN, and whether the first string is the same as the second string, in order to perform deduplication on the first and second PFDs. The deduplication process includes the following four scenarios:

[0247] When the first application ID of the first PFD is the same as the second application ID of the second PFD, and some fields of the PFDs are different, if the first string indicates that the source of the first PFD is NWDAF and the second string indicates that the source of the second PFD is AF, then some fields of the PFDs may be considered different when at least one of the following occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the PFD set includes the first PFD and the second PFD. In some cases where only the fact that a PFD needs to be updated or added is notified to the UDR, the PFD set does not need to be sent to the UDR. This is not limited here. Information regarding the addition of the first PFD may be forwarded to the UDR using an add packet, or information regarding the addition of the first PFD may be forwarded to the UDR using an add packet, and information regarding the update of the second PFD may be forwarded to the UDR using an update packet. This is not limited here.

[0248] When the first application ID is the same as the second application ID, and some fields of the PFD are different, if the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, then some fields of the PFD may be considered different, and the PFD set includes the first PFD, when at least one of the following occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN. In specific implementation, the second PFD may directly replace the first PFD, or the second PFD may be updated based on the parts of the first PFD that are different from the second PFD, and the updated content is updated in the PFD set. For example, when a second PFD carries a second PFD ID, the PFD set includes the correspondence between the first PFD and the second PFD ID, and the UDR is notified to replace the second PFD with the first PFD using an update packet, or the second PFD may remain unchanged and the first PFD is added to the UDR. This is not limited here.

[0249] The PFD set includes the first PFD when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF. In specific implementation, the second PFD may directly replace the first PFD, or the second PFD may be updated based on a portion of the first PFD that is different from the second PFD, and the updated content is updated in the PFD set. For example, when the second PFD carries the second PFD ID, the PFD set includes the correspondence between the first PFD and the second PFD ID, and the UDR is notified to replace the second PFD with the first PFD using the update packet. This is not limited here.

[0250] A PFD set includes a second PFD when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF. In specific implementations, PFD updates do not need to be performed at the UDR. In some cases, the PFD set does not need to be sent to the UDR, as it only notifies the UDR that a PFD needs to be updated or added. This is not limited here.

[0251] In this embodiment of the present application, when the NEF analyzes a first PFD and a second PFD to generate a PFD set, the main principle followed is as follows: when the first PFD competes with the second PFD (i.e., when the first PFD and the second PFD are repeated), if there are PFDs in the first and second PFDs whose source is AF, then the PFD whose source is AF is unconditionally reserved. If the PFDs have the same source, the most recent PFD is reserved preferentially. If the PFD carries time information, the timeliness of the PFD is determined based on the time information. If the PFD does not carry time information, the first PFD is the most recent by default and is reserved preferentially.

[0252] It should be understood that the specific basis and results of analyzing the first and second PFDs by NEF to generate a PFD set described here are merely illustrative. In actual application, the PFD set may be obtained by one or more decision methods or by analysis from different perspectives. This is not limited here.

[0253] Furthermore, since the UDR sends a second PFD to the NWDAF in step 703, after the PFD set is generated, the NEF may further update the PFD set based on the second PFD to obtain an updated PFD set. The updated PFD set may include only the parts that need to be changed from the second PFD, and the contents of these parts that need to be changed are identified.

[0254] For example, when a PFD set includes a first PFD and a second PFD, after the NEF updates the PFD set based on the second PFD, the updated PFD set includes the first PFD and an incremental update identifier, which instructs the NEF to directly add the contents of the updated PFD set to the UDR after receiving the updated PFD set. The specific format and contents of the incremental update identifier are not limited here.

[0255] Alternatively, when a PFD set includes a second PFD, after the NEF updates the PFD set based on the second PFD, the updated PFD set will only contain the incremental update identifier.

[0256] Alternatively, when a PFD set includes a first PFD, if the NEF updates the PFD set based on a second PFD, the updated PFD set will include the first PFD and a delta update identifier, and the delta update identifier will instruct the UDR to remove the second PFD. The specific format and content of the delta update identifier are not limited here.

[0257] It should be understood that the explanation of how to update specific content within a PFD set here is merely an example. In actual application, identification should be performed by referring to a specific application scenario. This is not limited here.

[0258] In this embodiment of the present application, PFD set transfer for PFD delta or PFD increment in UDR reduces the bandwidth occupied for PFD transfer, saves network resources, and improves information transfer efficiency.

[0259] 707:NEF sends the PFD set to the UDR.

[0260] After the NEF analyzes the first and second PFDs to generate a PFD set, the NEF sends the PFD set to the UDR, which includes at least one of the first and second PFDs.

[0261] Specifically, sending the PFD set obtained by NEF to the UDR can also be done via Nudr_DM_Update / Create Request / Response.

[0262] It should be understood that the description of the PFD set transmission method here is merely an example. In actual application, the configuration should be performed by referring to a specific application scenario. This is not limited here.

[0263] In this embodiment of the present application, the NEF collects the first PFD generated by the NWDAF and the second PFD stored in the UDR, analyzes the first and second PFDs to generate a PFD set, and transmits the PFD set to the UDR, thereby enabling the UDR to update the PFD information in the second PFD based on the PFD set. The PFD set includes at least one of the first and second PFDs to ensure that the PFD with the highest confidence is stored in the UDR for later selection when there are multiple relevant PFDs. This improves the reliability of the solution and also simplifies the operation when selecting a PFD by another network element thereafter.

[0264] The aforementioned solution provided in this embodiment of the present application describes a first PFD carrying a first string to identify the source of the first PFD, and a second PFD carrying a second string to identify the source of the second PFD. In addition, in some specific cases, other identifiers may be used to distinguish the sources of the first and second PFDs. For example, if the PFD carries a third string, by default, the source of the PFD may be considered a pre-configured device. The pre-configured device may be an NWDAF or an AF; this is not limited herein.

[0265] Referring to the solutions described in Figures 4 and 7, when the pre-configured device is an AF, the first PFD includes a first triplet, a first application ID, a first URL, and a first DN, and the second PFD includes a second triplet, a second application ID, a second URL, and a second DN. Optionally, if the source of the second PFD is an AF, the second PFD may further include a third string.

[0266] When the pre-configured device is an NWDAF, the first PFD includes a first triplet, a first application ID, a first URL, a first DN, and a third string, and the second PFD includes a second triplet, a second application ID, a second URL, and a second DN. Optionally, if the source of the second PFD is an NWDAF, the second PFD may further include a third string.

[0267] In this embodiment of the present application, a mark is added to the PFD whose source is a pre-configured device in order to help distinguish between different sources of PFDs. This effectively reduces the reduction of PFD content when there are only two cases of PFD sources and helps reduce the consumption of network resources in the PFD transmission process.

[0268] The above describes the data processing method provided in the embodiments of this application. The following describes the data processing device provided in the embodiments of this application with reference to the attached drawings.

[0269] Please refer to Figure 8. Figure 8 is a diagram of a data processing device according to one embodiment of the present application.

[0270] The data processing device 800 is Acquisition unit 801 is configured to acquire a first packet flow description PFD, the first PFD including a first triplet and a first application ID, The acquisition unit 801 acquires a second PFD transmitted by a second device, and the second PFD is further configured to include a second triplet and a second application ID, A transmitting unit 802 is configured to transmit a PFD set to the UDR based on a first PFD and a second PFD, and the PFD set includes at least one of the first PFD or the second PFD. Includes.

[0271] Optionally, the first PDF may further contain the first string, and the second PDF may further contain the second string, with the first string used to describe the source of the first PDF, and the second string used to describe the source of the second PDF.

[0272] Optionally, the transmitting unit 802 is: When it is determined that the first triplet is different from the second triplet and the first application ID is different from the second application ID, the first device sends a PFD set to the UDR, and the PFD set includes the first PFD and the second PFD, or When it is determined that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is different from the second string, and the first device determines that the first string indicates that the source of the first PFD is AF, and transmits the PFD set to the UDR, where the PFD set includes the first PFD, or the first device determines that the first string indicates that the source of the first PFD is NWDAF, and transmits the PFD set to the UDR, where the PFD set includes the second PFD. is specifically configured as follows.

[0273] Optionally, the first PFD further includes first time information, and the second PFD further includes second time information.

[0274] The transmission unit 802 When it is determined that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is the same as the second string, and the first device determines, based on the first time information and the second time information, that the first PFD was generated before the second PFD, and transmits the PFD set to the UDR, where the PFD set includes the second PFD, or the first device determines, based on the first time information and the second time information, that the first PFD was generated after the second PFD, and transmits the PFD set to the UDR, where the PFD set includes the first PFD, or When it is determined that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on the first time information and the second time information, that the first PFD expires before the second PFD, and transmits a PFD set to the UDR, where the PFD set includes the second PFD, or the first device determines, based on the first time information and the second time information, that the first PFD expires after the second PFD, and transmits a PFD set to the UDR, where the PFD set includes the first PFD. is specifically configured as follows.

[0275] Optionally, the first time information includes the expiration time and generation time of the first PFD, or the validity period and generation time of the first PFD, and the second time information includes the expiration time and generation time of the second PFD, or the validity period and generation time of the second PFD.

[0276] Optionally, the generation time of the first PFD is after the generation time of the second PFD.

[0277] The transmission unit 802 When the first application ID is the same as the second application ID and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD was generated by AF, the first device transmits a PFD set to the UDR, where the PFD set includes the first PFD and the second PFD, or When the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, then the first device sends a PFD set to the UDR, and the PFD set includes the first PFD. It is specifically configured in this way.

[0278] Optionally, the generation time of the first PFD is after the generation time of the second PFD.

[0279] The transmitting unit 802 is, When the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, the first device sends a PFD set to the UDR, and the PFD set includes the first PFD, or When the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, the first device sends a PFD set to the UDR, and the PFD set includes the second PFD. It is specifically configured in this way.

[0280] Optionally, the second PFD may further include a third string, which indicates that the PFD was generated by a pre-configured device.

[0281] Optionally, the first device includes a network exposure function (NEF) and the second device includes an integrated data repository (UDR), or the first device includes an application function (AF) and the second device includes an NWDAF.

[0282] Optionally, when the first device includes an NWDAF, the second device includes a UDR or NEF, and the first PFD is a PFD generated by the NWDAF, or when the first device includes an NEF, the second device includes a UDR.

[0283] Please refer to Figure 9. Figure 9 is another diagram of a data processing device according to one embodiment of the present application.

[0284] The data processing device 900 is An acquisition unit 901 configured to acquire a PFD information inquiry request sent by a first device, A transmission unit 902 is configured to transmit a second PFD to the first device, and the second PFD includes a second triplet and a second application ID. Includes, The acquisition unit 901 acquires a PFD set transmitted by the first device, the PFD set being further configured to include at least one of a first PFD and a second PFD, the first PFD including a first triplet and a first application ID.

[0285] Optionally, the second PDF may further contain the second string, the first PDF may further contain the first string, the first string may be used to describe the source of the first PDF, and the second string may be used to describe the source of the second PDF.

[0286] Optionally, the first PFD further includes first time information, and the second PFD further includes second time information.

[0287] Optionally, the second PFD may further include a third string, which indicates that the PFD was generated by a pre-configured device.

[0288] Please refer to Figure 10. Figure 10 is a diagram of another structure of a data processing device according to one embodiment of the present application. The data processing device 1000 includes a processor 1010, a communication interface 1020, and a memory 1030. The processor 1010, the communication interface 1020, and the memory 1030 may be connected to each other via an internal bus 1040, or they may communicate to each other by other means such as wireless transmission. In this embodiment of the present application, connection via bus 1040 is used as an example. Bus 1040 may be a Peripheral Components Interconnection (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1040 may be classified into an address bus, a data bus, and a control bus, etc. For ease of representation, Figure 10 has only one thick line to represent the bus, but this does not mean that there is only one bus or only one type of bus.

[0289] The processor 1010 may include at least one general-purpose processor, for example, a central processing unit (CPU), or a combination of a CPU and a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a composite programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (GAL), or any combination thereof. The processor 1010 executes various types of digital memory instructions, for example, software or firmware programs stored in memory 1030, thereby enabling the data processing unit 1000 to provide multiple services.

[0290] Memory 1030 is configured to store program code, and processor 1010 controls the execution of the program code to perform processing steps of the data processing method in the embodiments described above. The program code may include one or more software modules. One or more software modules may be the software modules provided in Figure 8, for example, an acquisition unit or a transmission unit. The acquisition unit is configured to acquire a first packet flow description PFD, the first PFD including a first triplet and a first application ID, and to acquire a second PFD transmitted by a second device, the second PFD including a second triplet and a second application ID, and is further configured to acquire a second PFD transmitted by a second device, the second PFD including a second triplet and a second application ID. The transmission unit is configured to transmit a PFD set to the UDR based on the first and second PFDs, the PFD set including at least one of the first or second PFDs.

[0291] It should be noted that this embodiment may be implemented by a general-purpose physical server, such as an ARM server or an x86 server, or by a virtual machine implemented on a general-purpose physical server in combination with NFV technology. The virtual machine is a software-accelerated full computer system that has the functionality of a full hardware system and operates in a completely isolated environment. This is not specifically limited in this application.

[0292] Memory 1030 may include a volatile memory, such as a random access memory (RAM). Memory 1030 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state disk (SSD). Memory 1030 may further include a combination of the aforementioned types. Memory 1030 stores program code and may execute steps 201 to 204 and any optional steps thereof in FIG. 2, steps 301 to 304 and any optional steps thereof in FIG. 3, steps 402, 404 to 406, and any optional steps thereof in FIG. 4, or steps 701, 706, 707, and any optional steps thereof in FIG. 7. Details are not described again here.

[0293] Communication interface 1020 may be a wired interface (e.g., an Ethernet interface), an internal interface (e.g., a high-speed serial computer expansion bus standard (PCIe) bus interface), a wired interface (e.g., an Ethernet interface), or a wireless interface (e.g., a cellular network interface or a wireless local area network interface), and is configured to communicate with another device or module.

[0294] Note that FIG. 10 shows only a possible embodiment of this embodiment of the present application. In actual application, data processing device 1000 may further include more or fewer components. This is not limited here. For content not shown or described in this embodiment of the present application, refer to the relevant descriptions in FIGS. 2, 3, 4, or 7. Details are not described again here.

[0295] It should be understood that the computing device shown in FIG. 10 may alternatively be a computer cluster including at least one server. This is not specifically limited in the present application.

[0296] Please refer to Figure 11. Figure 11 is a diagram of another structure of a data processing device according to one embodiment of the present application. The data processing device 1100 includes a processor 1110, a communication interface 1120, and a memory 1130. The processor 1110, the communication interface 1120, and the memory 1130 may be connected to each other via an internal bus 1140, or they may communicate to each other by other means such as wireless transmission. In this embodiment of the present application, connection via bus 1140 is used as an example. Bus 1140 may be a Peripheral Components Interconnection (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1140 may be classified into an address bus, a data bus, and a control bus, etc. For ease of representation, Figure 11 has only one thick line to represent the bus, but this does not mean that there is only one bus or only one type of bus.

[0297] The processor 1110 may include at least one general-purpose processor, for example, a central processing unit (CPU), or a combination of a CPU and a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a composite programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (GAL), or any combination thereof. The processor 1110 executes various types of digital memory instructions, for example, software or firmware programs stored in memory 1130, thereby enabling the data processing unit 1100 to provide multiple services.

[0298] Memory 1130 is configured to store program code, and processor 1110 controls the execution of the program code to perform processing steps of the data processing method in the embodiments described above. The program code may include one or more software modules. One or more software modules may be the software modules provided in Figure 9, for example, an acquisition unit or a transmission unit. The acquisition unit is configured to acquire a PFD information inquiry request sent by a first device, and to acquire a PFD set sent by the first device, the PFD set is further configured to include at least one of a first PFD and a second PFD, the first PFD including a first triplet and a first application ID. The transmission unit is configured to transmit a second PFD to the first device, the second PFD including a second triplet and a second application ID.

[0299] It should be noted that this embodiment may be implemented by a general-purpose physical server, such as an ARM server or an x86 server, or by a virtual machine implemented on a general-purpose physical server in combination with NFV technology. The virtual machine is a software-accelerated full computer system that has the functionality of a full hardware system and operates in a completely isolated environment. This is not specifically limited in this application.

[0300] Memory 1130 may include volatile memory, such as random access memory (RAM). Memory 1130 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state disk (SSD). Memory 1130 may further include combinations of the aforementioned types. Memory 1130 may store program code and perform step 205 and its optional steps in Figure 2, step 305 and its optional steps in Figure 3, step 403 and its optional steps in Figure 4, or step 703 and its optional steps in Figure 7. Further details are not described here.

[0301] The communication interface 1120 may be a wired interface (e.g., an Ethernet interface), an internal interface (e.g., a PCIe bus interface), a wired interface (e.g., an Ethernet interface), or a wireless interface (e.g., a cellular network interface or a wireless local area network interface), and may be configured to communicate with another device or module.

[0302] Please note that Figure 11 is merely a possible embodiment of this embodiment of the present application. In actual application, the computing device 1100 may further include more or fewer components. This is not limited herein. For anything not shown or described in this embodiment of the present application, please refer to the relevant descriptions in Figures 2, 3, 4, or 7. Further details are again not described here.

[0303] It should be understood that the computing device shown in Figure 11 may also be a computer cluster including at least one server. This is not specifically limited in this application.

[0304] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed on a processor, a procedure is carried out by the NEF or AF in the manner shown in Figure 2 or Figure 3.

[0305] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed on a processor, a procedure is carried out by the NEF or NWDAF in the manner shown in Figure 4 or Figure 7.

[0306] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed on a processor, the procedure performed by the UDR in the manner shown in Figure 2 or Figure 3 is carried out.

[0307] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed on a processor, a procedure performed by the UDR is carried out in the manner shown in Figure 4 or Figure 7.

[0308] One embodiment of this application further provides a computer program product. When the computer program product is run on a processor, the procedure performed by the NEF or AF in the manner shown in Figure 2 or Figure 3 is carried out.

[0309] One embodiment of this application further provides a computer program product. When the computer program product is run on a processor, the procedure performed by the NEF or NWDAF in the manner shown in Figure 4 or Figure 7 is carried out.

[0310] One embodiment of this application further provides a computer program product. When the computer program product is run on a processor, the procedure performed by the UDR in the manner shown in Figure 2 or Figure 3 is carried out.

[0311] One embodiment of this application further provides a computer program product. When the computer program product is run on a processor, the procedure performed by the UDR in the manner shown in Figure 4 or Figure 7 is carried out.

[0312] For the sake of brevity, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units can be described by referring to the corresponding processes in the method embodiments described above. Further details are not provided here.

[0313] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the apparatus embodiments described are merely illustrative. For example, the division of units is merely a division of logical functions and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the interconnections or direct connections or communication connections presented or described may be implemented through some interfaces. Indirect connections or communication connections between apparatus or units may be implemented electronically, mechanically, or in other forms.

[0314] Units described as separate parts may or may not be physically separate, and parts presented as units may or may not be physical units, specifically, they may be located in one location or distributed across multiple network units. Some or all of the units may be selected according to the actual requirements to achieve the objectives of the solution of the embodiment.

[0315] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0316] When an integrated unit is implemented in the form of a software function unit and sold or used as an independent product, the integrated unit may be stored on a computer-readable storage medium. Based on this understanding, the technical solution of this application may be implemented in the form of a software product, either essentially, or in part with respect to the prior art, or all or part of the technical solution. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of the embodiment of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. [Explanation of symbols]

[0317] 800 Data Processing Devices 801 units acquired 802 Transmitter Unit 900 Data Processing Units 901 acquired units 902 Transmitter Unit 1000 Data Processing Devices 1010 Processor 1020 Communication Interface 1030 memory 1040 Internal bus 1100 Data Processing Device 1110 processor 1120 Communication Interface 1130 memory 1140 Internal bus

Claims

1. A step of obtaining a first packet flow description PFD by a first device, wherein the first PFD includes a first triplet and a first application identity ID. The first device obtains a second PFD transmitted by a second device, wherein the second PFD includes a second triplet and a second application ID. A step of sending a set of PFDs to the integrated data repository UDR based on the first PFD and the second PFD by the first device, wherein the set of PFDs includes at least one of the first PFD or the second PFD. A data processing method that includes this.

2. The method according to claim 1, wherein the first PDF further comprises a first string, the second PDF further comprises a second string, the first string is used to describe the source of the first PDF, and the second string is used to describe the source of the second PDF.

3. The first device transmits the PFD set to the UDR based on the first PFD and the second PFD, wherein the PFD set includes at least one of the first PFD or the second PFD, the step is: When the first device determines that the first triplet is different from the second triplet and the first application ID is different from the second application ID, the first device transmits the PFD set to the UDR, wherein the PFD set includes the first PFD and the second PFD, or Steps of sending the PFD set to the UDR, wherein the PFD set includes the first PFD, or Steps of sending the PFD set to the UDR, wherein the first device determines that the first string is different from the second string and the first application ID is the same as the second application ID, or the first device determines that the first string is the same as the second string and the first application ID is different from the second application ID, and the first device determines that the first string indicates that the source of the first PFD is application function AF, and the PFD set includes the second PFD, The method according to claim 2, including the method described in claim 2.

4. The first PFD further includes first time information, and the second PFD further includes second time information. The first device transmits the PFD set to the UDR based on the first PFD and the second PFD, wherein the PFD set includes at least one of the first PFD or the second PFD, the step is: Steps include: when the first device determines that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or when the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is the same as the second string, and the first device determines, based on the first time information and the second time information, that the first PFD was generated before the second PFD, and transmits the PFD set to the UDR, wherein the PFD set includes the second PFD; or, when the first device determines, based on the first time information and the second time information, that the first PFD was generated after the second PFD, and transmits the PFD set to the UDR, wherein the PFD set includes the first PFD; Steps include: when the first device determines that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on the first time information and the second time information, that the first PFD expires before the second PFD, and transmits the PFD set to the UDR, wherein the PFD set includes the second PFD; or, when the first device determines, based on the first time information and the second time information, that the first PFD expires after the second PFD, and transmits the PFD set to the UDR, wherein the PFD set includes the first PFD. The method according to claim 2, including the method described in claim 2.

5. The method according to claim 4, wherein the first time information includes the expiration date of the first PFD and the time of creation of the first PFD, or the validity period of the first PFD and the time of creation of the first PFD, and the second time information includes the expiration date of the second PFD and the time of creation of the second PFD, or the validity period of the second PFD and the time of creation of the second PFD.

6. The generation time of the first PFD is after the generation time of the second PFD. The first device transmits the PFD set to the UDR based on the first PFD and the second PFD, wherein the PFD set includes at least one of the first PFD or the second PFD, the step is: Steps to transmit the PFD set by the first device to the UDR when the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first domain name DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, wherein the PFD set includes the first PFD and the second PFD, or Steps include: sending the PFD set by the first device to the UDR when the first application ID is the same as the second application ID, at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, wherein the PFD set includes the first PFD. The method according to claim 2, including the method described in claim 2.

7. The generation time of the first PFD is after the generation time of the second PFD. The first device transmits the PFD set to the UDR based on the first PFD and the second PFD, wherein the PFD set includes at least one of the first PFD or the second PFD, the step is: A step in which the first device transmits the PFD set to the UDR when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, wherein the PFD set includes the first PFD, or Steps include: transmitting the PFD set to the UDR by the first device when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, wherein the PFD set includes the second PFD; The method according to claim 2, including the method described in claim 2.

8. The method according to claim 1, wherein the second PFD further comprises a third string, the third string indicating that the PFD is a PFD generated by a pre-configured device.

9. The method according to any one of claims 1 to 5, wherein the first device includes a network exposure function NEF and the second device includes a UDR, or the first device includes an AF and the second device includes an NWDAF.

10. The method according to any one of claims 6 to 8, wherein when the first device comprises an NWDAF, the second device comprises a UDR or an NEF, and the first PFD is a PFD generated by the NWDAF, or when the first device comprises an NEF, the second device comprises a UDR.

11. The integrated data repository UDR obtains a PFD information query request from the first device, The steps include: transmitting a second PFD to the first device using the UDR, wherein the second PFD includes a second triplet and a second application identity ID; A step of obtaining the PFD set from the first device using the UDR, wherein the PFD set includes at least one of a first PFD and a second PFD, and the first PFD includes a first triplet and a first application ID. A data processing method that includes this.

12. The method according to claim 11, wherein the second PDF further comprises a second string, the first PDF further comprises a first string, the first string is used to describe the source of the first PDF, and the second string is used to describe the source of the second PDF.

13. The method according to claim 11 or 12, wherein the first PFD further includes first time information, and the second PFD further includes second time information.

14. The method according to claim 11, wherein the second PFD further comprises a third string, the third string indicating that the PFD is a PFD generated by a pre-configured device.

15. An acquisition unit is configured to acquire a first packet flow description PFD, wherein the first PFD includes a first triplet and a first application ID, The acquisition unit is further configured to acquire a second PFD transmitted by a second device, and the second PFD includes a second triplet and a second application ID. A transmitting unit configured to transmit a PFD set to the UDR based on the first PFD and the second PFD, wherein the PFD set includes at least one of the first PFD or the second PFD. A data processing device equipped with the following features.

16. The apparatus according to claim 15, wherein the first PDF further comprises a first string, the second PDF further comprises a second string, the first string is used to describe the source of the first PDF, and the second string is used to describe the source of the second PDF.

17. The aforementioned transmission unit is When it is determined that the first triplet is different from the second triplet and the first application ID is different from the second application ID, the first device transmits the PFD set to the UDR, and the PFD set includes the first PFD and the second PFD, or When it is determined that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or when it is determined that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is different from the second string, and the first device determines that the first string indicates that the source of the first PFD is AF, and sends the PFD set to the UDR, and the PFD set includes the first PFD, or the first device determines that the first string indicates that the source of the first PFD is NWDAF, and sends the PFD set to the UDR, and the PFD set includes the second PFD. The apparatus according to claim 16, which is particularly configured as follows.

18. The first PFD further includes first time information, and the second PFD further includes second time information. The aforementioned transmission unit is When it is determined that the first triplet is different from the second triplet and the first application ID is the same as the second application ID, or that the first triplet is the same as the second triplet and the first application ID is different from the second application ID, the first device determines that the first string is the same as the second string, and based on the first time information and the second time information, the first device determines that the first PFD was generated before the second PFD, and sends the PFD set to the UDR, the PFD set including the second PFD, or the first device determines, based on the first time information and the second time information, that the first PFD was generated after the second PFD, and sends the PFD set to the UDR, the PFD set including the first PFD, or When it is determined that the first triplet is the same as the second triplet and the first application ID is the same as the second application ID, the first device determines, based on the first time information and the second time information, that the first PFD expires before the second PFD, and transmits the PFD set to the UDR, the PFD set including the second PFD, or the first device determines, based on the first time information and the second time information, that the first PFD expires after the second PFD, and transmits the PFD set to the UDR, the PFD set including the first PFD, The apparatus according to claim 16, which is particularly configured as follows.

19. The apparatus according to claim 18, wherein the first time information includes the expiration date of the first PFD and the generation date of the first PFD, or the validity period of the first PFD and the generation date of the first PFD, and the second time information includes the expiration date of the second PFD and the generation date of the second PFD, or the validity period of the second PFD and the generation date of the second PFD.

20. The generation time of the first PFD is after the generation time of the second PFD. The aforementioned transmission unit is When the first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is generated by AF, the first device sends the PFD set to the UDR, and the PFD set includes the first PFD and the second PFD, or The first application ID is the same as the second application ID, and at least one of the following cases occurs: the first triplet is different from the second triplet, the first URL is different from the second URL, and the first DN is different from the second DN, and the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, the first device sends the PFD set to the UDR, and the PFD set includes the first PFD. The apparatus according to claim 16, which is particularly configured as follows.

21. The generation time of the first PFD is after the generation time of the second PFD. The aforementioned transmission unit is When the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is NWDAF, the first device transmits the PFD set to the UDR, and the PFD set includes the first PFD, or The first device transmits the PFD set to the UDR when the first application ID is different from the second application ID, the first triplet is the same as the second triplet, the first string indicates that the source of the first PFD is NWDAF, and the second string indicates that the source of the second PFD is AF, and the PFD set includes the second PFD. The apparatus according to claim 16, which is particularly configured as follows.

22. The apparatus according to claim 15, wherein the second PFD further comprises a third string, the third string indicating that the PFD is a PFD generated by a pre-configured device.

23. The apparatus according to any one of claims 15 to 19, wherein the first device comprises a network publishing function NEF, the second device comprises an integrated data repository UDR, or the first device comprises an application function AF, and the second device comprises an NWDAF.

24. The apparatus according to any one of claims 20 to 22, wherein when the first device comprises an NWDAF, the second device comprises a UDR or an NEF, and the first PFD is a PFD generated by the NWDAF, or when the first device comprises an NEF, the second device comprises a UDR.

25. An acquisition unit configured to acquire a PFD information inquiry request sent by a first device, A transmission unit configured to transmit a second PFD to the first device, the second PFD including a second triplet and a second application identity ID, and Equipped with, A data processing device, wherein the acquisition unit acquires a set of PFDs transmitted by the first device, the set of PFDs comprising at least one of a first PFD and a second PFD, the first PFD comprising a first triplet and a first application ID.

26. The apparatus according to claim 25, wherein the second PDF further comprises a second string, the first PDF further comprises a first string, the first string is used to describe the source of the first PDF, and the second string is used to describe the source of the second PDF.

27. The apparatus according to claim 25 or 26, wherein the first PFD further includes first time information, and the second PFD further includes second time information.

28. The apparatus according to claim 25, wherein the second PFD further comprises a third string, the third string indicating that the PFD is a PFD generated by a pre-configured device.

29. A data processing device comprising a processor and memory, wherein the memory is configured to store instructions, the processor is configured to execute the instructions, and when the processor executes the instructions, the method according to any one of claims 1 to 6 is performed.

30. A data processing device comprising a processor and memory, wherein the memory is configured to store instructions, the processor is configured to execute the instructions, and when the processor executes the instructions, the method according to any one of claims 7 to 9 is performed.

31. A computer-readable storage medium containing a program, wherein when the program is run on a computer, the computer is enabled to perform the method according to any one of claims 1 to 10.

32. A computer-readable storage medium containing a program, wherein when the program is run on a computer, the computer is enabled to perform the method according to any one of claims 11 to 14.

33. A computer program product comprising instructions, wherein when the computer program product is run on a computer, the computer is enabled to perform the method according to any one of claims 1 to 10.

34. A computer program product comprising instructions, wherein when the computer program product is run on a computer, the computer is enabled to perform the method described in any one of claims 11 to 14.

Images