Data analysis method and apparatus, electronic device, and storage medium

Abstract

The embodiment discloses a data analysis method and device, electronic equipment and computer storage medium. The method is applied to a first network function entity, and comprises the following steps: obtaining a data analysis request for network data; when the data analysis request is irrelevant to session binding information, querying a target NWDAF entity registered in a storage function entity through the storage function entity; when the data analysis request is relevant to the session binding information, querying the target NWDAF entity registered in a BSF entity through the BSF entity, or querying the target NWDAF entity through a PCF entity when the PCF entity determines the target NWDAF entity in advance; sending the data analysis request to the target NWDAF entity; and receiving a data analysis result sent by the target NWDAF entity.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of wireless communication, and particularly relates to a data analysis method and device, an electronic device, and a storage medium. BACKGROUND

[0002] In the related art, the 3rd Generation Partnership Project (3GPP) defines a Network Data Analytics Function (NWDAF), and the NWDAF entity can collect network data and provide analysis capabilities for analysis demanders such as an Application Function (AF) entity and a Network Exposure Function (NEF) entity. However, for the AF entity or the NEF entity, how to query available NWDAF entities to obtain data analysis results of the available NWDAF entities is a technical problem to be solved. SUMMARY

[0003] Embodiments of the present application provide a data analysis method and device, an electronic device, and a storage medium.

[0004] Embodiments of the present application provide a data analysis method, which is applied to a first network function entity, and the method comprises the following steps.

[0005] Obtaining a data analysis request for network data;

[0006] When the data analysis request is irrelevant to session binding information, querying a target Network Data Analytics Function (NWDAF) entity registered in a storage function entity through the storage function entity; when the data analysis request is relevant to the session binding information, querying a target NWDAF entity registered in a Binding Support Function (BSF) entity through the BSF entity, or querying the target NWDAF entity through a Policy Control Function (PCF) entity when the PCF entity determines the target NWDAF entity in advance;

[0007] Sending the data analysis request to the target NWDAF entity;

[0008] Receiving a data analysis result sent by the target NWDAF entity.

[0009] In some embodiments, the querying the target NWDAF entity registered in the storage function entity through the storage function entity comprises: querying the target NWDAF entity from the storage function entity according to first reference information, the first reference information comprising at least one of: an identifier of a user equipment initiating the data analysis request, an Internet Protocol (IP) address of the user equipment, IP domain information of the user equipment, a location of the user equipment, or an analysis identifier of the data analysis request.

[0010] It can be seen that the embodiments of the present application can more accurately query the target NWDAF entity from the storage function entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the location of the user equipment, or the analysis identifier of the data analysis request.

[0011] In some embodiments, the querying the target NWDAF entity registered in the BSF entity through the BSF entity comprises: querying the target NWDAF entity from the BSF entity according to second reference information, the second reference information comprising at least one of: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, or an identifier of a session created by the user equipment; and the querying the target NWDAF entity through the PCF entity comprises: querying the target NWDAF entity from the PCF entity according to the second reference information, the second reference information comprising at least one of: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, or an identifier of a session created by the user equipment.

[0012] It can be seen that the embodiments of the present application can more accurately query the target NWDAF entity from the BSF entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the analysis identifier of the data analysis request, or the identifier of the session created by the user equipment. The target NWDAF entity can also be more accurately queried from the PCF entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the analysis identifier of the data analysis request, or the identifier of the session created by the user equipment.

[0013] In some embodiments, after receiving the data analysis result sent by the target NWDAF entity, the method further comprises: sending Quality of Service (QoS) invocation information to the PCF entity according to the data analysis result.

[0014] It can be seen that the first network function entity can send QoS invocation information more suitable for the PCF to the PCF entity according to the data analysis result, which is beneficial to optimizing network services based on the QoS invocation information.

[0015] The embodiment of the present application further provides another data analysis method, which is applied to a target NWDAF entity, and the method comprises the following steps:

[0016] receiving a data analysis request for network data sent by a first network function entity; the data analysis request is sent by the first network function entity after determining the target NWDAF entity; the first network function entity is used to query the target NWDAF entity registered in a storage function entity through the storage function entity when determining that the data analysis request is irrelevant to session binding information; the first network function entity is used to query the target NWDAF entity registered in a BSF entity through the BSF entity when determining that the data analysis request is relevant to session binding information, or the first network function entity is used to query the target NWDAF entity through a PCF entity when the PCF entity determines the target NWDAF entity in advance;

[0017] performing data analysis according to the data analysis request to obtain a data analysis result;

[0018] sending the data analysis result to the first network function entity.

[0019] In some embodiments, before receiving the data analysis request sent by the first network function entity, the method further comprises the following steps: sending a first registration request to the storage function entity; the storage function entity is used to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the first network function entity or the PCF entity.

[0020] It can be seen that after the target NWDAF entity further sends a first registration request to the storage function entity, if the first network function entity or the PCF entity sends a request for querying the target NWDAF entity to the storage function entity, the storage function entity can reasonably determine the target NWDAF entity according to the registration result corresponding to the first registration request received in advance.

[0021] In some embodiments, before receiving the data analysis request sent by the first network function entity, the method further comprises the following steps: after receiving binding indication information, sending a second registration request to the BSF entity; the BSF entity is used to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the first network function entity; and the binding indication information is used to indicate that session binding has been completed.

[0022] Understandably, after the target NWDAF entity sends the second registration request to the BSF entity, if the first network function entity sends a request to query the target NWDAF entity to the BSF entity, the BSF entity can reasonably determine the target NWDAF entity according to the registration result corresponding to the second registration request.

[0023] In some embodiments, the binding indication information is locally pre-configured information or information sent by the PCF entity. It can be seen that since the NWDAF entity can obtain the binding indication information from the local or the PCF entity, the flexible acquisition of the binding indication information can be achieved.

[0024] In some embodiments, before performing data analysis according to the data analysis request, the method further comprises: selecting a data source according to a judgment result of whether the data analysis request is related to session binding information; and obtaining the network data from the selected data source.

[0025] It can be seen that the target NWDAF entity can more reasonably select a data source according to a judgment result of whether the data analysis request is related to session binding information, so as to obtain network data required for data analysis from the data source.

[0026] Embodiments of the present application provide a data analysis device, the device is applied to a first network function entity, the device comprises:

[0027] The acquisition module is configured to acquire a data analysis request for network data.

[0028] The first processing module is configured to, when the data analysis request is not related to session binding information, query a target NWDAF entity registered in a storage function entity through the storage function entity; when the data analysis request is related to session binding information, query a target NWDAF entity registered in a BSF entity through the BSF entity, or when a PCF entity pre-determines the target NWDAF entity, query the target NWDAF entity through the PCF entity.

[0029] The transceiver module is configured to send the data analysis request to the target NWDAF entity, and receive a data analysis result of the network data sent by the target NWDAF entity.

[0030] Embodiments of the present application provide another data analysis device, the device is applied to a target NWDAF entity, the device comprises:

[0031] The second processing module is configured to receive a data analysis request for network data sent by the first network function entity; perform data analysis according to the data analysis request to obtain a data analysis result; the data analysis request is sent by the first network function entity after determining the target NWDAF entity; the first network function entity is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity when determining that the data analysis request is irrelevant to session binding information; query the target NWDAF entity registered in a BSF entity through the BSF entity when determining that the data analysis request is relevant to session binding information, or query the target NWDAF entity through a PCF entity when the PCF entity determines the target NWDAF entity in advance;

[0032] The sending module is configured to send the data analysis result to the first network function entity.

[0033] Embodiments of the present application provide an electronic device, comprising a processor and a memory for storing a computer program capable of running on the processor; wherein the processor is configured to run the computer program to execute any of the above-mentioned data analysis methods applied to the first network function entity or the target NWDAF entity.

[0034] Embodiments of the present application also provide a computer storage medium having a computer program stored thereon, which, when executed by a processor, implements any of the above-mentioned data analysis methods applied to the first network function entity or the target NWDAF entity.

[0035] It can be seen that when the data analysis request for network data is irrelevant to session binding information, the target NWDAF entity has been registered in the storage function entity, so the target NWDAF entity can be accurately queried from the storage function entity; when the data analysis request for network data is relevant to session binding information, the target NWDAF entity has been registered in the BSF entity, so the target NWDAF entity can be accurately queried from the BSF entity; when the data analysis request for network data is relevant to session binding information and the PCF entity determines the target NWDAF entity in advance, the target NWDAF entity can be accurately queried from the BSF entity; in the embodiments of the present application, after the target NWDAF entity for analyzing network data is accurately determined, the data analysis result from the target NWDAF entity can be obtained by sending a data analysis request to the target NWDAF entity, thereby facilitating the opening of the data analysis result of the target NWDAF entity to the outside. BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1An interaction flowchart for network data analysis proposed for the related art;

[0037] Figure 2 A flowchart of a data analysis method applied to a first network function entity for an embodiment of the present application;

[0038] Figure 3 A flowchart of a data analysis method applied to a target NWDAF entity for an embodiment of the present application;

[0039] Figure 4 A network architecture diagram proposed for a scenario in which a data analysis request is irrelevant to session binding information in an embodiment of the present application;

[0040] Figure 5 A network architecture diagram proposed for a scenario in which a data analysis request is relevant to session binding information in an embodiment of the present application;

[0041] Figure 6 A structural diagram of a data analysis apparatus applied to a first network function entity for an embodiment of the present application;

[0042] Figure 7 A structural diagram of a data analysis apparatus applied to a NWDAF entity for an embodiment of the present application;

[0043] Figure 8 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] In the related art, a NWDAF entity can collect network data and provide analysis capabilities for demanders such as AF entities, network function (NF) entities, etc., and can provide a basic architecture for a big data analysis-oriented service and network coordination scheme based on the NWDAF entity. Based on the definition of 3GPP, an AF entity or a NEF entity can subscribe to or request a data analysis result from the NWDAF entity based on a service interface, and the NWDAF entity can notify the AF entity or the NEF entity of the corresponding data analysis result after completing the data analysis.

[0045] REFERENCE Figure 1The NEF entity can control analytics exposure mapping information; the AF entity can send a subscription request or a request for canceling subscription to the NWDAF entity through the NEF entity, the subscription request representing a request for subscribing to data analytics results, and the request for canceling subscription representing a request for canceling subscription to data analytics results; the MWDAF entity, after receiving the subscription request, can perform data analytics on previously received network data to obtain data analytics results, and send first notification information to the NEF entity, and the NEF entity can send second notification information to the AF entity. Here, the first notification information and the second notification information both carry data analytics results. Exemplarily, the subscription request sent by the AF entity to the NEF entity can be denoted as Nnef_AnalyticsExposure_Subscribe, the request for canceling subscription sent by the AF entity to the NEF entity can be denoted as Nnef_AnalyticsExposure_Unsubscribe; the subscription request sent by the NEF entity to the NWDAF entity can be denoted as Nnwdaf_AnalyticsSubscription_Subscribe, the request for canceling subscription sent by the NEF entity to the NWDAF entity can be denoted as Nnwdaf_AnalyticsSubscription_Unsubscribe, the first notification information can be denoted as Nnwdaf_AnalyticsSubscription_Notify, and the second notification information can be denoted as Nnef_AnalyticsExposure_Notify.

[0046] In actual scenarios, especially in experience scenarios, how to realize opening of the data analysis result of the NWDAF entity is a technical problem to be solved. The reasons why the data analysis result of the NWDAF entity cannot be opened are exemplarily described as follows. First, the interface and process for the NWDAF entity to open the data analysis result to the AF entity or the NEF entity are not defined in the related art; second, how the AF entity or the NEF entity realizes addressing of the NWDAF entity is not solved; for example, in the related art, the AF entity or the NEF entity can only have an IP address of a user equipment or a combination of the IP address and domain information, and cannot address the available NWDAF entity through service registration information defined by the NWDAF entity, for example, the service registration information defined by the NWDAF entity can be a tracking area identity (TAI) or single network slice selection assistance information (S-NSSAI). It can be seen from the above description that, for the AF entity or the NEF entity, how to query the available NWDAF entity to obtain the data analysis result of the available NWDAF entity is a technical problem to be solved.

[0047] To solve the above technical problems, the technical solutions of the embodiments of the present application are proposed.

[0048] The embodiments of the present application are further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the embodiments provided herein are only used to explain the embodiments of the present application and not to limit the embodiments of the present application. In addition, the embodiments provided below are used to implement some embodiments of the present application, and the technical solutions described in the embodiments of the present application can be implemented in any combination manner without conflict.

[0049] It should be noted that, in the embodiments of the present application, the terms "comprise", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the method or device comprising a series of elements not only includes the elements explicitly described, but also includes other elements not explicitly listed or inherent to the method or device. Without more limitations, the element defined by the sentence "comprises a" does not exclude the presence of other related elements (such as steps in the method or units in the device, for example, the unit can be part of the circuit, part of the processor, part of the program or software, etc.) in the method or device comprising the element.

[0050] For example, the data analysis method provided by the embodiments of the present application includes a series of steps, but the data analysis method provided by the embodiments of the present application is not limited to the steps described, and similarly, the data analysis device provided by the embodiments of the present application includes a series of modules, but the device provided by the embodiments of the present application is not limited to including the explicitly described modules, and can also include modules required for obtaining relevant information or processing based on information.

[0051] The embodiments of the present application provide a data analysis method applied to a first network function entity. Exemplarily, the first network function entity can be an NEF entity or an AF entity.

[0052] Figure 2 A flowchart of the data analysis method applied to the first network function entity according to an embodiment of the present application is shown in FIG. 2, which can include the following steps. Figure 2

[0053] Step 201: Obtain a data analysis request for network data.

[0054] In the embodiments of the present application, the first network function entity can generate a data analysis request for network data.

[0055] Step 202: When the data analysis request is irrelevant to session binding information, query a target NWDAF entity registered in a storage function entity through the storage function entity; when the data analysis request is relevant to the session binding information, query the target NWDAF entity registered in a BSF entity through the BSF entity, or when the PCF entity determines the target NWDAF entity in advance, query the target NWDAF entity through the PCF entity.

[0056] Exemplarily, the storage function entity can be a network storage function (NRF) entity.

[0057] The BSF entity and the PCF entity are defined in 3GPP for implementing session binding. Exemplarily, the BSF entity can be used to store session binding information of a user equipment (UE), and the PCF entity can invoke a service application programming interface (API) of the BSF entity to register and unregister the session binding information when creating a protocol data unit (PDU) session, that is, the PCF entity triggers the creation or deletion of the session binding information on the BSF entity.

[0058] Here, the target NWDAF entity represents an NWDAF entity capable of analyzing network data at the current moment.​

[0059] In some embodiments, each NWDAF entity in the cellular network can send a first registration request to the storage function entity in advance to realize the registration of the corresponding NWDAF entity in the storage function entity; for example, the first registration request can include at least one of the following: an identifier of a user equipment served by the NWDAF entity, an IP address segment of a user equipment served by the NWDAF entity, IP domain information of a user equipment served by the NWDAF entity, an identifier of the NWDAF entity, a service area of the NWDAF entity, and an analytics identifier (Analytics ID) of a data analysis request. For example, the identifier of the user equipment served by the NWDAF entity can be at least one of a subscription permanent identifier (SUPI) and a generic public subscription identifier (GPSI), and the IP address segment of the user equipment served by the NWDAF entity can be an Internet Protocol version 4 (IPv4) address segment or an Internet Protocol version 6 (IPv6) address segment.

[0060] In some embodiments, when a user equipment creates a PDU session, a session management function (SMF) entity can obtain session policy information through a PCF entity; then, the first network function entity can address the PCF entity through the execution of a policy control and charging (PCC) capability call, so as to realize the session binding through the PCF entity; after the first network function entity addresses the PCF entity, if the PCF entity obtains a data analysis request of network data, the PCF entity can query a target NWDAF entity from a storage function entity, where the PCF entity can query the target NWDAF entity according to at least one of the following: an analytics identifier of the data analysis request, a TAI, an S-NSSAI, and an identifier of a user equipment served by the NWDAF entity.

[0061] In some embodiments, after querying the target NWDAF entity from the storage function entity, the PCF entity can send a data analysis request to the target NWDAF entity; the target NWDAF entity can perform data analysis on network data to obtain a data analysis result, and the target NWDAF entity can send the data analysis result to the PCF entity and also send a second registration request to the BSF entity. By way of example, the second registration request can include at least one of the following: an identifier of a user equipment served by the target NWDAF entity, an IP address segment of the user equipment served by the target NWDAF entity, IP domain information of the user equipment served by the target NWDAF entity, a data network name (DNN), an S-NSSAI, an identifier of a session created by the user equipment, an identifier of the target NWDAF entity, and an analysis identifier of the data analysis request. By way of example, the session created by the user equipment can be a PDU session or an N7 session, and the identifier of the session created by the user equipment can be an identity document (ID) or other identifier.

[0062] Step 203: sending a data analysis request to the target NWDAF entity.

[0063] Step 204: receiving a data analysis result sent by the target NWDAF entity.

[0064] Here, the data analysis result is a result obtained by analyzing network data according to the data analysis request.

[0065] By way of example, after receiving the data analysis result, the NEF entity or the AF entity can further decide whether to implement service optimization by applying itself or to implement experience optimization by network QoS capability exposure.

[0066] In actual applications, steps 201 to 204 can be implemented based on a processor of the AF entity or the NEF entity, and the processor can be at least one of an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a central processing unit (CPU), a controller, a microcontroller, or a microprocessor.

[0067] It can be seen that when the data analysis request for network data is irrelevant to the session binding information, the target NWDAF entity can be accurately queried from the storage function entity since the target NWDAF entity has been registered in the storage function entity; when the data analysis request for network data is relevant to the session binding information, the target NWDAF entity can be accurately queried from the BSF entity since the target NWDAF entity has been registered in the BSF entity; when the data analysis request for network data is relevant to the session binding information and the target NWDAF entity is determined in advance by the PCF entity, the target NWDAF entity can be accurately queried from the BSF entity; in the embodiment of the application, after the target NWDAF entity for analyzing network data is accurately determined, the data analysis result from the target NWDAF entity can be obtained by sending a data analysis request to the target NWDAF entity, thereby facilitating the opening of the data analysis result of the target NWDAF entity to the outside.

[0068] In some embodiments of the application, the process of querying the target NWDAF entity registered in the storage function entity through the storage function entity can include: querying the target NWDAF entity from the storage function entity according to first reference information, the first reference information including at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, a location of the user equipment, and an analysis identifier of the data analysis request.

[0069] For example, the identifier of the user equipment initiating the data analysis request can be at least one of SUPI and GPSI. The number of user equipments initiating the data analysis request can be greater than 1. In the case of multiple user equipments initiating the data analysis request, the IP address of the user equipment can be presented in the form of a list of IP addresses, the IP domain information of the user equipment can be presented in the form of a list of IP domains, and the identifier of the user equipment initiating the data analysis request can be presented in the form of a list of identifiers.

[0070] It can be seen that the embodiment of the application can more accurately query the target NWDAF entity from the NRF entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the location of the user equipment, or the analysis identifier of the data analysis request.

[0071] In some embodiments of the present application, the process of querying the target NWDAF entity registered in the BSF entity through the BSF entity can comprise: querying the target NWDAF entity from the BSF entity according to second reference information, the second reference information comprising at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, and an identifier of a session created by the user equipment.

[0072] For example, the identifier of the user equipment initiating the data analysis request can be at least one of SUPI and GPSI. The session created by the user equipment can be a PDU session or an N7 session, and the identifier of the session created by the user equipment can be an ID or other identifier.

[0073] As can be seen, the embodiments of the present application can more accurately query the target NWDAF entity from the BSF entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the analysis identifier of the data analysis request, or the identifier of the session created by the user equipment.

[0074] In some embodiments of the present application, the process of querying the target NWDAF entity through the PCF entity can comprise: querying the target NWDAF entity from the PCF entity according to second reference information.

[0075] As can be seen, the embodiments of the present application can more accurately query the target NWDAF entity from the PCF entity according to the identifier of the user equipment initiating the data analysis request, the IP address of the user equipment, the IP domain information of the user equipment, the analysis identifier of the data analysis request, or the identifier of the session created by the user equipment.

[0076] In some embodiments of the present application, after receiving the data analysis result sent by the target NWDAF entity, the first network function entity can send QoS invocation information to the PCF entity according to the data analysis result.

[0077] In the embodiments of the present application, after receiving the data analysis result, the first network function entity can generate QoS invocation information according to the data analysis result, and then send the QoS invocation information to the PCF entity.

[0078] As can be seen, the first network function entity can send QoS invocation information more suitable for the PCF to the PCF entity according to the data analysis result, which is conducive to optimizing network services based on the QoS invocation information.

[0079] Figure 3 For a flowchart of a data analysis method applied to a target NWDAF entity according to an embodiment of the present application, as shown in Figure 3As shown, the flow can include:

[0080] Step 301: receiving a data analysis request of network data sent by a first network function entity; the data analysis request is sent by the first network function entity after determining a target NWDAF entity.

[0081] Here, the first network function entity is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity when it is determined that the data analysis request is irrelevant to session binding information; or query the target NWDAF entity registered in a BSF entity through the BSF entity when it is determined that the data analysis request is relevant to session binding information, or query the target NWDAF entity through a PCF entity when the PCF entity determines the target NWDAF entity in advance.

[0082] Step 302: performing data analysis according to the data analysis request to obtain a data analysis result.

[0083] Step 303: sending the data analysis result to the first network function entity.

[0084] In actual application, steps 301 to 303 can be implemented based on a processor of the target NWDAF entity, and the processor can be at least one of an ASIC, a DSP, a DSPD, a PLD, a FPGA, a CPU, a controller, a microcontroller, and a microprocessor.

[0085] It can be seen that when the data analysis request for network data is irrelevant to session binding information, the target NWDAF entity has been registered in the storage function entity, so the target NWDAF entity can be accurately queried from the storage function entity; when the data analysis request for network data is relevant to session binding information, the target NWDAF entity has been registered in the BSF entity, so the target NWDAF entity can be accurately queried from the BSF entity; when the data analysis request for network data is relevant to session binding information and the PCF entity determines the target NWDAF entity in advance, the target NWDAF entity can be accurately queried from the BSF entity; in the embodiment of the application, after the target NWDAF entity for analyzing network data is accurately determined, the data analysis result from the target NWDAF entity can be obtained by sending a data analysis request to the target NWDAF entity, so as to facilitate the opening of the data analysis result of the target NWDAF entity to the outside.

[0086] In some embodiments of the present application, before the target NWDAF entity receives the data analysis request sent by the first network function entity, the target NWDAF entity can also send a first registration request to the storage function entity, and the storage function entity is configured to determine the target NWDAF entity according to a request sent by the first network function entity or the PCF entity to query the target NWDAF entity.

[0087] As can be seen, after the target NWDAF entity also sends the first registration request to the storage function entity, if the first network function entity or the PCF entity sends a request to the storage function entity to query the target NWDAF entity, the storage function entity can reasonably determine the target NWDAF entity according to the registration result corresponding to the first registration request received in advance.

[0088] In some embodiments of the present application, before the target NWDAF entity receives the data analysis request sent by the first network function entity, if the target NWDAF entity receives the binding indication information, the target NWDAF entity can also send a second registration request to the BSF entity; the BSF entity is configured to determine the target NWDAF entity according to a request sent by the NEF entity or the AF entity to query the target NWDAF entity; and the binding indication information is used to indicate that the session binding has been completed.

[0089] As can be understood, after the target NWDAF entity sends the second registration request to the BSF entity, if the first network function entity sends a request to the BSF entity to query the target NWDAF entity, the BSF entity can reasonably determine the target NWDAF entity according to the registration result corresponding to the second registration request.

[0090] In some embodiments of the present application, the binding indication information is locally pre-configured information or information sent by the PCF entity, and as can be seen, since the NWDAF entity can obtain the binding indication information from the local or the PCF entity, the flexible acquisition of the binding indication information can be achieved.

[0091] In some embodiments of the present application, before the target NWDAF entity performs data analysis according to the data analysis request, the target NWDAF entity can also determine whether the data analysis request is related to the session binding information, obtain a determination result, select a data source according to the determination result, and obtain network data from the selected data source.

[0092] Exemplarily, the target NWDAF entity can select a data source from an SMF, an NF, an Operation Administration and Maintenance (OAM), a User Plane Function (UPF), and the like according to the judgment result. In one example, if the data analysis request is irrelevant to the session binding information, the data source selected by the target NWDAF entity can be an NF entity or an OAM entity; in another example, if the data analysis request is relevant to the session binding information, the data source selected by the target NWDAF entity can be a UPF entity.

[0093] After selecting the data source, the target NWDAF entity can send trigger information for collecting data to the selected data source, so as to trigger the data source to collect data.

[0094] Exemplarily, the data collected by the data source includes at least one of the following: an identifier of a user equipment, resource utilization of a cell uplink / downlink Physical Resource Block (PRB), cell uplink / downlink throughput, and the like, a location of the user equipment, a number of session connections, a number of registered user equipments, and the like.

[0095] It can be seen that the target NWDAF entity can reasonably select a data source according to the judgment result of whether the data analysis request is relevant to the session binding information, so as to obtain network data required for data analysis from the data source.

[0096] The technical solutions of the embodiments of the present application will be described below in combination with the accompanying drawings, respectively for a scenario in which the data analysis request is irrelevant to the session binding information, and a scenario in which the data analysis request is relevant to the session binding information.

[0097] Exemplarily, in the scenario in which the data analysis request is irrelevant to the session binding information, the data analysis request can be a request for obtaining a network bandwidth analysis prediction result at a cell level sent by a video application to the NWDAF entity; the video application can adjust the code rate of the video according to the network bandwidth analysis prediction result, and send the video after code rate adjustment to the user equipment. In the scenario in which the data analysis request is irrelevant to the session binding information, the data analysis request can also be a request for obtaining an analysis result of event monitoring type information; here, by obtaining the analysis result of the event monitoring type information, the business optimization of the self can be enabled. For example, the analysis result of the event monitoring type information can be: an analysis prediction result of a mobile event of a user equipment, a network resource related analysis prediction result of a cell where the user equipment is located, and the like.

[0098] Reference Figure 4NWDAF1 and NWDAF2 represent two different NWDAF entities, in the scenario that the data analysis request is irrelevant to the session binding information, the interaction flow of the data analysis method can include the following steps:

[0099] Step A0: NWDAF1 and NWDAF2 respectively send a first registration request to the NRF entity to realize the registration of the data analysis service. NWDAF1 and NWDAF2 respectively send a first registration request to the NRF entity.

[0100] Step A1: When the user equipment creates a PDU session, the SMF entity obtains the session policy information through the PCF entity.

[0101] Exemplarily, the SMF entity can obtain the session policy information from the PCF entity according to the private IP address of the user equipment.

[0102] Step A2: When the AF entity or the NEF entity determines that the network feedback data analysis result is needed, a data analysis request is generated, and if it is determined that the data analysis request is irrelevant to the session binding information, the target NWDAF entity is queried through the NRF entity. Here, the target NWDAF entity is NWDAF1.

[0103] Step A3: The AF entity or the NEF entity subscribes to the data analysis result of the NWDAF1.

[0104] Here, the AF entity or the NEF entity can realize the subscription of the data analysis result by sending a data analysis request to the NWDAF1; the AF entity can directly subscribe to the data analysis result of the NWDAF1, or can subscribe to the data analysis result of the NWDAF1 through the NEF entity. Exemplarily, the data analysis result can be the result of related analysis on network resources, and the data analysis request can include at least one of the following: analysis identifier of the data analysis request, identifier of the user equipment initiating the data analysis request, IP address of the user equipment, IP domain information of the user equipment, service identifier of the data analysis request, time, location of the user equipment, model accuracy requirement. Exemplarily, the IP address in the data analysis request sent by the AF entity can be a public IP address, and the IP address in the data request sent by the NEF entity can be a private IP address.

[0105] Exemplarily, the identity of the user equipment initiating the data analysis request can be at least one of SUPI and GPSI. The number of user equipment initiating the data analysis request can be greater than 1, in the case that the user equipment initiating the data analysis request is multiple devices, the IP address of the user equipment can be presented in the form of a list of IP addresses, the IP domain information of the user equipment can be presented in the form of a list of IP domains, the identity of the user equipment initiating the data analysis request can be presented in the form of a list of identities, and the service identity of the data analysis request can be presented in the form of a list of identities.

[0106] Step A4: NWDAF1 triggers data source to collect network data.

[0107] Exemplarily, in the network resource related analysis scenario, the data source at least includes SMF, UPF, AMF, wireless OAM and the like. The NWDAF1 can address the SMF entity through a Unified Data Management (UDM) entity according to the identity of the user equipment and the like information sent by the AF entity or the NEF entity, and the SMF entity further feeds back the information of the UPF entity to the NWDAF entity. The NWDAF entity can address the Access and Mobility Management Function (AMF) entity through the UDM entity according to the location information sent by the AF entity or the NEF entity, and the AMF entity further feeds back the information of the RAN or the information of the wireless network management to the NWDAF entity.

[0108] Step A5: The NWDAF1 performs data analysis according to the data analysis request, and obtains data analysis results; and feeds back the data analysis results to the AF entity or the NEF entity.

[0109] Step A6: After receiving the data analysis results, the AF entity or the NEF entity can execute local policy optimization according to the data analysis results. For example, whether to locally adjust the video code rate can be decided according to the available resources of the user equipment in the network.

[0110] Exemplarily, in the scenario related to the session binding information of the data analysis request, the data analysis request can be a request sent by a video application to the NWDAF entity to obtain service QoS policy suggestion of a certain user; and the video application can send a corresponding service QoS capability invocation request to the PCF entity according to the service QoS policy suggestion of the certain user. In the scenario related to the session binding information of the data analysis request, the data analysis request can also be a request to obtain Quality of Experience (QoE) analysis information or QoS analysis information of the user equipment, and the identity of the data analysis request corresponding to the QoS analysis information can be UE QoS profie.

[0111] Figure 5 The network architecture diagram is proposed for the scenario related to the session binding information of the data analysis request in the embodiments of the present application, referring to Figure 5 , NWDAF1 and NWDAF2 represent two different NWDAF entities, the AF entity or the NEF entity can interact with the PCF entity, the NWDAF1 and the NWDAF2 can both interact with the BSF entity, the PCF entity is in communication connection with the AMF entity and the SMF entity respectively, the AMF entity is in communication connection with the user equipment, the RAN and the SMF entity respectively, the RAN is in communication connection with the UPF entity and the wireless gateway respectively; in the NWDAF1 and the NWDAF2, each NWDAF entity can be in communication connection with the UPF entity and the wireless grid.

[0112] In the scenario related to the session binding information of the data analysis request, an interaction process of the data analysis method can include the following steps:

[0113] Step B0: The BSF entity sends a registration request to the NRF entity to realize the registration of the data analysis service. The NWDAF1 and the NWDAF2 send a first registration request to the NRF entity respectively to realize the registration of the data analysis service.

[0114] In some embodiments, the registration information sent by the BSF entity to the NRF entity can include at least one of the following: the IP address segment supported by the BSF entity, the IP domain information supported by the BSF entity, and the identifier of the user equipment supported by the BSF entity. Illustratively, the IP address segment supported by the BSF entity can be an IPv4 address segment or an IPv6 address segment, and the identifier of the user equipment supported by the BSF entity can be at least one of SUPI and GPSI.

[0115] Step B1: When the user equipment creates a PDU session, the SMF entity obtains session policy information through the PCF entity.

[0116] Step B2: The AF entity or the NEF entity addresses the PCF entity for realizing session binding through a PCC capability call, so as to realize session binding through the PCF entity.

[0117] Step B3: If the PCF entity obtains a data analysis request of network data, the target NWDAF entity is queried from the NRF entity. Here, the target NWDAF entity is the NWDAF1.

[0118] Illustratively, the data analysis request obtained by the PCF entity can be different from the data analysis request obtained by the AF entity or the NEF entity.

[0119] Step B4: The PCF entity sends a data analytics request to the NWDAF1.

[0120] Exemplarily, the data analytics request sent by the PCF entity to the NWDAF1 can include at least one of the following: an analysis identifier of the data analytics request, an identifier of a user equipment initiating the data analytics request, an IP address of the user equipment, a service identifier of the data analytics request, and binding indication information.

[0121] Step B5: The NWDAF1 sends a data analytics result to the PCF entity.

[0122] Step B6: After obtaining the binding indication information, the NWDAF1 sends a second registration request to the BSF entity.

[0123] Step B7: The AF entity or the NEF entity generates a data analytics request when determining that network feedback of a data analytics result is needed, and queries a target NWDAF entity through the BSF entity if it is determined that the data analytics request is related to session binding information.

[0124] Step B8: The AF entity or the NEF entity subscribes to a data analytics result from the NWDAF1.

[0125] The implementation manner of this step is the same as that of step A3. Exemplarily, the IP address in the data analytics request sent by the AF entity can be a public network IP address, and the IP address in the data request sent by the NEF entity can be a private network IP address.

[0126] Step B9: The NWDAF1 triggers a data source to collect network data.

[0127] Step B10: The NWDAF1 performs data analytics according to the data analytics request to obtain a data analytics result, and feeds back the data analytics result to the AF entity or the NEF entity.

[0128] Exemplarily, the data analytics result can include at least one of the following: an analysis identifier of the data analytics request, an identifier of a user equipment initiating the data analytics request, a service identifier of the data analytics result, a location of the user equipment, a time, a 5G QoS Identifier (5QI), an Allocation and Retention Priority (ARP), a Guaranteed Bit Rate (GBR), and a Maximum Bit Rate (MBR).

[0129] Step B11: After receiving the data analytics result, the AF entity or the NEF entity can send QoS invocation information to a PCF entity for implementing session binding according to the data analytics result.

[0130] Exemplarily, the QoS invocation information can include at least one of the following: an identifier of the user equipment, a service identifier, 5QI, ARP, GBR, MBR.

[0131] In the scenario that the data analysis request is related to the session binding information, another interaction procedure of the data analysis method can include the following steps:

[0132] Steps C0 to C3: The implementation manners of steps B0 to B3 are the same.

[0133] Step C4: The PCF entity sends the data analysis request to the NWDAF1.

[0134] Exemplarily, the data analysis request sent by the PCF entity to the NWDAF1 can include at least one of the following: an analysis identifier of the data analysis request, an identifier of the user equipment initiating the data analysis request, an IP address of the user equipment, a service identifier of the data analysis request.

[0135] Step C5: The NWDAF1 sends the data analysis result to the PCF entity.

[0136] Step C6: The AF entity or the NEF entity generates a data analysis request when it is determined that network feedback of the data analysis result is needed, and queries a target NWDAF entity through a PCF entity if it is determined that the data analysis request is related to the session binding information.

[0137] Step C7: The AF entity or the NEF entity sends the data analysis request to the NWDAF1.

[0138] Steps C8 to C10: The implementation manners of steps B9 to B11 are the same.

[0139] Based on the foregoing description, it can be seen that the embodiments of the present application propose a data analysis method, which can realize the opening of the data analysis result of the NWDAF entity through the interaction between the AF entity or the NEF entity and the NWDAF entity in the presence or absence of session binding, that is, the embodiments of the present application can better realize the collaborative configuration of network elements, guarantee the service experience of users, and provide an implementation scheme for the opening of core network data analysis.

[0140] Compared with the data analysis scheme provided in the related art, the embodiments of the present application can realize the opening of the data analysis result of the NWDAF entity to the AF entity or the NEF entity for the scenario with session binding and the scenario without session binding, respectively, and the AF entity can initiate a more adaptive QoS request in combination with the data analysis result of the NWDAF when applying for QoS capability scheduling.

[0141] Those skilled in the art can understand that, in the above method of the specific embodiment, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process, and the specific execution order of each step should be determined according to its function and possible internal logic.

[0142] On the basis of the data analysis method applied to the NEF entity or the AF entity proposed in the foregoing embodiments, the embodiment of the present application further proposes a data analysis apparatus applied to the NEF entity or the AF entity.

[0143] Figure 6 A structural schematic diagram of the data analysis apparatus applied to the first network function entity of the embodiment of the present application is shown in FIG. 6, which can include: Figure 6

[0144] The acquisition module 601 is configured to acquire a data analysis request for network data.

[0145] The first processing module 602 is configured to query a target NWDAF entity registered in a storage function entity through the storage function entity when the data analysis request is irrelevant to session binding information, or query the target NWDAF entity registered in a BSF entity through the BSF entity when the data analysis request is relevant to the session binding information, or query the target NWDAF entity through a PCF entity when the target NWDAF entity is determined in advance by the PCF entity.

[0146] The transceiver module 603 is configured to send the data analysis request to the target NWDAF entity, and receive a data analysis result of the network data sent by the target NWDAF entity.

[0147] In some embodiments, the first processing module 602 is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity, including:

[0148] According to first reference information, the target NWDAF entity is queried from the storage function entity, and the first reference information includes at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, a location of the user equipment, and an analysis identifier of the data analysis request.

[0149] In some embodiments, the first processing module 602 is configured to query the target NWDAF entity registered in a BSF entity through the BSF entity, including:

[0150] ​According to second reference information, the target NWDAF entity is queried from the BSF entity, and the second reference information includes at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, and an identifier of a session created by the user equipment.

[0151] In some embodiments, the first processing module 602 is configured to query the target NWDAF entity from the PCF entity, and the method includes the following steps.

[0152] According to second reference information, the target NWDAF entity is queried from the PCF entity, and the second reference information includes at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, and an identifier of a session created by the user equipment.

[0153] In some embodiments, the transceiver module 603 is further configured to, after receiving the data analysis result sent by the target NWDAF entity, send QoS invocation information to the PCF entity according to the data analysis result.

[0154] Based on the data analysis method applied to the NWDAF entity proposed in the foregoing embodiments, the embodiments of the present application further propose a data analysis device applied to the NWDAF entity.

[0155] Figure 7 A structural schematic diagram of the data analysis device applied to the NWDAF entity of the embodiments of the present application is shown in FIG. 7, which can include the following modules. Figure 7

[0156] The second processing module 701 is configured to receive a data analysis request of network data sent by a first network function entity, perform data analysis according to the data analysis request, and obtain a data analysis result. The data analysis request is sent by the first network function entity after the target NWDAF entity. The first network function entity is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity when it is determined that the data analysis request is irrelevant to session binding information, or query the target NWDAF entity registered in a BSF entity through the BSF entity when it is determined that the data analysis request is relevant to the session binding information, or query the target NWDAF entity through a PCF entity when the PCF entity determines the target NWDAF entity in advance.

[0157] The sending module 702 is configured to send the data analysis result to the first network function entity.

[0158] ​In some embodiments, the second processing module 701 is further configured to send a first registration request to a storage function entity before receiving the data analysis request sent by the first network function entity, and the storage function entity is configured to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the first network function entity or a PCF entity.

[0159] In some embodiments, the second processing module 701 is further configured to send a second registration request to the BSF entity after receiving the binding indication information, and the BSF entity is configured to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the NEF entity or the AF entity, and the binding indication information is used to indicate that the session binding has been completed.

[0160] In some embodiments, the binding indication information is locally pre-configured information or information sent by a PCF entity.

[0161] In some embodiments, the second processing module 701 is further configured to select a data source according to a result of determining whether the data analysis request is related to session binding information before performing data analysis according to the data analysis request, and obtain the network data from the selected data source.

[0162] In actual application, the obtaining module 601, the first processing module 602, the transceiver module 603, the second processing module 701 and the sending module 702 can all be implemented based on a processor.

[0163] It should be noted that the above description of the device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects to the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0164] It should be noted that in the embodiments of the present application, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a plurality of instructions for causing a computer device (which can be a terminal, a server, etc.) to execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk, and various media that can store program codes. Thus, the embodiments of the present application are not limited to any specific hardware and software combination.

[0165] Correspondingly, the embodiments of the present application further provide a computer program product, which comprises computer executable instructions for implementing any of the data analysis methods provided by the embodiments of the present application.

[0166] Correspondingly, the embodiments of the present application further provide a computer storage medium, which stores computer executable instructions for implementing any of the data analysis methods provided by the embodiments of the present application.

[0167] The embodiments of the present application further provide an electronic device, Figure 8 A schematic diagram of the composition structure of the electronic device provided by the embodiments of the present application is shown in Figure 8 As shown, the electronic device 80 can include:

[0168] The memory 801 is configured to store executable instructions.

[0169] The processor 802 is configured to execute the executable instructions stored in the memory 801, so as to implement any of the data analysis methods applied to the NEF entity, the AF entity or the NWDAF entity.

[0170] The computer readable storage medium and the memory 801 can be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Ferromagnetic Random Access Memory (FRAM), a Flash Memory, a magnetic surface memory, an optical disk, a Compact Disc Read-Only Memory (CD-ROM) or other memories; or can be various terminals including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc.

[0171] In some embodiments, the apparatus provided by the embodiments of the present application has functions or includes modules which can be used to execute the methods described in the above method embodiments, and the specific implementation can refer to the description of the above method embodiments. For brevity, it will not be repeated here.

[0172] The above description of the various embodiments tends to emphasize differences between the various embodiments, and the same or similar parts can be mutually referred to for brevity, which will not be repeated here.

[0173] The methods disclosed in the various method embodiments provided in the present application can be combined arbitrarily without conflict, to obtain new method embodiments.

[0174] The features disclosed in the various product embodiments provided in the present application can be combined arbitrarily without conflict, to obtain new product embodiments.

[0175] The features disclosed in the various method or device embodiments provided in the present application can be combined arbitrarily without conflict, to obtain new method embodiments or device embodiments.

[0176] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software plus a general hardware platform, of course, they can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product in essence or in the form of a part of the prior art that makes a contribution. The computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the various embodiments of the present application.

[0177] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative and not restrictive, and those of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.

Claims

1. A data analysis method, characterized by, Applied to a first network function entity, the method comprises: Obtaining a data analysis request for network data; When the data analysis request is irrelevant to session binding information, querying a target network data analysis function (NWDAF) entity registered in a storage function entity through the storage function entity; when the data analysis request is relevant to session binding information, querying a target NWDAF entity registered in a binding support function (BSF) entity through the BSF entity, or, when a policy control function (PCF) entity determines a target NWDAF entity in advance, querying the target NWDAF entity through the PCF entity; Sending the data analysis request to the target NWDAF entity; Receiving a data analysis result sent by the target NWDAF entity.

2. The method of claim 1, wherein, The querying of the target NWDAF entity registered in the storage function entity through the storage function entity comprises: According to first reference information, querying the target NWDAF entity from the storage function entity, the first reference information comprising at least one of the following: an identifier of a user equipment initiating the data analysis request, an Internet Protocol (IP) address of the user equipment, IP domain information of the user equipment, a location of the user equipment, and an analysis identifier of the data analysis request.

3. The method of claim 1, wherein, The querying of the target NWDAF entity registered in the BSF entity through the BSF entity comprises: According to second reference information, querying the target NWDAF entity from the BSF entity, the second reference information comprising at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, and an identifier of a session created by the user equipment. The querying of the target NWDAF entity through the PCF entity comprises: According to second reference information, querying the target NWDAF entity from the PCF entity, the second reference information comprising at least one of the following: an identifier of a user equipment initiating the data analysis request, an IP address of the user equipment, IP domain information of the user equipment, an analysis identifier of the data analysis request, and an identifier of a session created by the user equipment.

4. The method according to any one of claims 1 to 3, characterized in that, After receiving the data analysis result sent by the target NWDAF entity, the method further comprises: According to the data analysis result, sending quality of service (QoS) invocation information to the PCF entity.

5. A data analysis method characterized by, Applied to a target network data analysis function (NWDAF) entity, the method comprises: receiving a data analysis request for network data sent by a first network function entity; the data analysis request is sent by the first network function entity after determining the target NWDAF entity; the first network function entity is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity when determining that the data analysis request is irrelevant to session binding information; query the target NWDAF entity registered in a binding support function (BSF) entity through the BSF entity when determining that the data analysis request is relevant to session binding information, or query the target NWDAF entity through a policy control function (PCF) entity when the target NWDAF entity is determined in advance by the PCF entity; performing data analysis according to the data analysis request to obtain a data analysis result; sending the data analysis result to the first network function entity.

6. The method of claim 5, wherein, Before receiving the data analysis request sent by the first network function entity, the method further comprises: sending a first registration request to the storage function entity, and the storage function entity is configured to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the first network function entity or the PCF entity.

7. The method of claim 5, wherein, Before receiving the data analysis request sent by the first network function entity, the method further comprises: after receiving binding indication information, sending a second registration request to the BSF entity; the BSF entity is configured to determine the target NWDAF entity according to a request for querying the target NWDAF entity sent by the first network function entity; and the binding indication information is used to indicate that session binding has been completed.

8. The method of claim 7, wherein, The binding indication information is information pre-configured locally or information sent by a PCF entity.

9. The method of claim 5, wherein, Before performing data analysis according to the data analysis request, the method further comprises: selecting a data source according to a judgment result of whether the data analysis request is relevant to session binding information; obtaining the network data from the selected data source.

10. A data analysis device, characterized by, The apparatus is applied to a first network function entity, and the apparatus comprises: an obtaining module configured to obtain a data analysis request for network data; a first processing module configured to query a target network data analysis function (NWDAF) entity registered in a storage function entity through the storage function entity when the data analysis request is irrelevant to session binding information, query a target NWDAF entity registered in a binding support function (BSF) entity through the BSF entity when the data analysis request is relevant to session binding information, or query the target NWDAF entity through a policy control function (PCF) entity when the target NWDAF entity is determined in advance by the PCF entity; a transceiver configured to send a data analysis request to the target NWDAF entity and receive a data analysis result sent by the target NWDAF entity.

11. A data analysis device, characterized by The apparatus is applied to a target network data analysis function (NWDAF) entity, and the apparatus comprises: The second processing module is configured to receive a data analysis request for network data sent by a first network function entity; perform data analysis according to the data analysis request to obtain a data analysis result; the data analysis request is sent by the first network function entity after the target NWDAF entity is determined; the first network function entity is configured to query the target NWDAF entity registered in a storage function entity through the storage function entity when it is determined that the data analysis request is irrelevant to session binding information; query the target NWDAF entity registered in a binding support function (BSF) entity through the BSF entity when it is determined that the data analysis request is relevant to session binding information, or query the target NWDAF entity through a policy control function (PCF) entity when the target NWDAF entity is determined by the PCF entity in advance; The sending module is configured to send the data analysis result to the first network function entity.

12. An electronic device, comprising: The electronic device comprises a processor and a memory for storing a computer program capable of running on the processor; wherein, The processor is configured to run the computer program to perform the data analysis method of any one of claims 1 to 9.

13. A computer storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the data analysis method of any one of claims 1 to 9.

Images