User application data acquisition method and device, electronic equipment and storage medium

Abstract

The invention provides a user application data acquisition method and device, electronic equipment and a storage medium, and relates to the technical field of mobile communication. The method is executed by an NWDAF network element or a credit-granted AF network element, and comprises the following steps: determining an identifier corresponding to a target user; sending the identifier to the UDM network element to obtain a protocol data unit session identifier corresponding to the target user; sending the protocol data unit session identifier to the SMF network element to obtain a terminal private address corresponding to the target user; sending the terminal private address to the UPF network element to obtain a terminal public address corresponding to the terminal private address; and collecting user application data through the terminal public address. According to the invention, the corresponding PDU session identifier is determined through the identifier, and the private address of the terminal is determined through the PDU session identifier. And then matching the private address of the terminal with the public address of the terminal through the corresponding UPF network element. Therefore, user application data acquisition is realized.

Description

Background Art

[0002] With the development of mobile communication technology, the network can collect user application data to achieve corresponding data analysis and data control processes.

[0003] However, in the scenario where NAT (Network Address Translation) is deployed, the network can only identify the private address of the terminal, and it is impossible to collect user application data only through the private address of the terminal. Therefore, there is an urgent need for a method for collecting user applications in the scenario where NAT is deployed.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides a user application data collection method, device, electronic device and storage medium, which at least to a certain extent overcome the problem in the related art that the network cannot collect user applications in the scenario where NAT is deployed.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of an embodiment of the present disclosure, a method for collecting user application data is provided, which is executed by a network data analysis function network element or a trusted application function network element, and includes: determining an identifier corresponding to a target user; sending the identifier to a unified data management network element to obtain a protocol data unit session identifier corresponding to the target user; sending a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to the target user; sending the terminal private address to a user plane function network element to obtain a terminal public address corresponding to the terminal private address; and collecting user application data through the terminal public address.

[0008] In some embodiments of the present disclosure, an identifier is sent to a unified data management network element to obtain a protocol data unit session identifier corresponding to a target user, including: sending an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to the unified data management network element; receiving at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determining at least one target protocol data unit session identifier for user application data collection from the at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; wherein, sending the protocol data unit session identifier to the session management function network element includes: sending the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0009] In some embodiments of the present disclosure, sending a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user includes: sending a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to the target user and a user plane function network element address corresponding to the protocol data unit session identifier; wherein, sending the terminal private address to the user plane function network element includes: sending the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0010] In some embodiments of the present disclosure, when the method is executed by a network data analysis function network element, the identifier is a universal public user identifier or a subscription permanent identifier; wherein, user application data is collected through the terminal public address, including: associating the terminal public address with the universal public user identifier or the subscription permanent identifier to collect user application data through the terminal public address.

[0011] In some embodiments of the present disclosure, when the method is executed by a trusted application function network element, the identifier is a subscription permanent identifier, and determining the identifier corresponding to the target user includes: receiving a network data analysis function request sent by the network data analysis function network element; obtaining the subscription permanent identifier through the network data analysis function request; wherein, collecting user application data through the terminal public address includes: associating the terminal public address with the subscription permanent identifier to collect user application data through the terminal public address.

[0012] According to another aspect of the present disclosure, a method for collecting user application data is provided, the method being performed by a non-trusted application function network element, comprising: determining an identifier corresponding to a target user; sending the identifier to a network open function network element to obtain a terminal public address corresponding to the target user;

[0013] User application data is collected through the terminal public address; wherein the network open function network element is used to send an identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; the protocol data unit session identifier is sent to the session management function network element to obtain the terminal private address corresponding to the target user; the terminal private address is sent to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

[0014] In some embodiments of the present disclosure, the network open function network element is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; and send the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0015] In some embodiments of the present disclosure, the network open function network element is used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user and a user plane function network element address corresponding to the protocol data unit session identifier; and send the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0016] In some embodiments of the present disclosure, the identifier is a universal public user identifier, and determining the identifier corresponding to the target user includes: receiving a network data analysis function request sent by a network data analysis function network element; obtaining the universal public user identifier through the network data analysis function request; wherein, collecting user application data through the terminal public address includes: associating the terminal public address with the universal public user identifier to collect user application data through the terminal public address.

[0017] According to another aspect of the present disclosure, a user application data collection device is provided, which is applied to a network data analysis function network element or a trusted application function network element, including: a first identifier acquisition module, used to determine an identifier corresponding to a target user; a protocol data unit session identifier acquisition module, used to send an identifier to a unified data management network element to obtain a protocol data unit session identifier corresponding to the target user; a user terminal private address acquisition module, used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to the target user; a first public user terminal address acquisition module, used to send a terminal private address to a user plane function network element to obtain a terminal public address corresponding to the terminal private address; a first data collection module, used to collect user application data through the terminal public address.

[0018] In some embodiments of the present disclosure, a protocol data unit session identifier acquisition module is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; a user terminal private address acquisition module is used to send a target protocol data unit session identifier to a session management function network element corresponding to the session management function network element identifier.

[0019] In some embodiments of the present disclosure, a user terminal private address acquisition module is used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user and a user plane function network element address corresponding to the protocol data unit session identifier; a first public user terminal address acquisition module is used to send a terminal private address to a user plane function network element corresponding to the user plane function network element address.

[0020] In some embodiments of the present disclosure, when the device is applied to a network data analysis function network element, the identifier is a universal public user identifier or a subscription permanent identifier; the first data collection module is used to associate the terminal public address with the universal public user identifier or the subscription permanent identifier to collect user application data through the terminal public address.

[0021] In some embodiments of the present disclosure, when the device is applied to a trusted application function network element, the identifier is a subscription permanent identifier; the first identifier acquisition module is used to receive a network data analysis function request sent by the network data analysis function network element; the subscription permanent identifier is acquired through the network data analysis function request; the first data collection module is used to associate the terminal public address with the subscription permanent identifier to collect user application data through the terminal public address.

[0022] According to another aspect of the present disclosure, there is provided a user application data collection device, which is applied to a non-trusted application function network element, and includes: a second identifier acquisition module, used to determine an identifier corresponding to a target user; a second public user terminal address acquisition module, used to send an identifier to a network open function network element to obtain a terminal public address corresponding to the target user; and a second data collection module, used to collect user application data through the terminal public address.

[0023] Among them, the network open function network element is used to send an identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

[0024] In some embodiments of the present disclosure, the network open function network element is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; and send the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0025] In some embodiments of the present disclosure, the network open function network element is used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user and a user plane function network element address corresponding to the protocol data unit session identifier; and send the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0026] In some embodiments of the present disclosure, the identifier is a universal public user identifier, and the second identifier acquisition module is used to receive a network data analysis function request sent by a network data analysis function network element; obtain the universal public user identifier through the network data analysis function request; the second data collection module is used to associate the terminal public address with the universal public user identifier to collect user application data through the terminal public address.

[0027] According to another aspect of the present disclosure, an electronic device is provided, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned user application data collection method by executing the executable instructions.

[0028] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned user application data collection method is implemented.

[0029] According to another aspect of the present disclosure, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the user application data collection method provided in various optional ways in any embodiment of the present disclosure.

[0030] The technical method provided by the embodiment of the present disclosure can determine the corresponding PDU session identifier through the identifier, and determine the terminal private address through the PDU session identifier. After that, the terminal private address and the terminal public address can be matched through the corresponding UPF network element. Therefore, the present disclosure realizes the user application data collection. In addition, the method of the present disclosure has less modification to each network element, reducing the modification cost.

[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0033] Figure 1 A schematic diagram showing a system architecture in an embodiment of the present disclosure;

[0034] Figure 2 A schematic diagram showing another system architecture in an embodiment of the present disclosure;

[0035] Figure 3 A flow chart of a method for collecting user application data in an embodiment of the present disclosure is shown;

[0036] Figure 4 A flow chart of a method for collecting user application data through an NWDAF network element in an embodiment of the present disclosure is shown;

[0037] Figure 5 A flow chart of a method for collecting user application data through a trusted AF network element in an embodiment of the present disclosure is shown;

[0038] Figure 6 A flow chart of a method for obtaining user application data analysis results in an embodiment of the present disclosure is shown;

[0039] Figure 7 Another flow chart of a method for collecting user application data in an embodiment of the present disclosure is shown;

[0040] Figure 8 A flow chart of a method for collecting user application data through a non-trusted AF network element in an embodiment of the present disclosure is shown;

[0041] Fig. 9 A schematic diagram of a user application data collection device in an embodiment of the present disclosure is shown;

[0042] Fig.10 A schematic diagram of another user application data collection device in an embodiment of the present disclosure is shown;

[0043] Fig.11 A structural block diagram of an electronic device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0044] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0045] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0046] Figure 1 A schematic diagram showing an exemplary system architecture of a user application data collection method that can be applied to an embodiment of the present disclosure.

[0047] like Figure 1 As shown, the system architecture 100 may include a network data analysis function network element 101, a credit application function network element 102, a unified data management network element 103, a session management function network element 104, and a user plane function network element 105.

[0048] Among them, the network data analysis function network element 101 or the credit application function network element 102 can determine the identifier corresponding to the target user, and send the identifier to the unified data management network element 103 to obtain the protocol data unit session identifier corresponding to the target user. After that, the protocol data unit session identifier can be sent to the session management function network element 104 to obtain the terminal private address corresponding to the target user. Finally, the terminal private address can be sent to the user plane function network element 105 to obtain the terminal public address corresponding to the terminal private address, and the user application data can be collected through the terminal public address.

[0049] Those skilled in the art will know that Figure 1 The number of network data analysis function network element 101, credit application function network element 102, unified data management network element 103, session management function network element 104, and user plane function network element 105 is merely illustrative and is not limited in the embodiments of the present disclosure.

[0050] Alternatively, a schematic diagram of an exemplary system architecture of another user application data collection method provided by an embodiment of the present disclosure can be as follows: Figure 2 shown.

[0051] exist Figure 2 In the system architecture 200, a non-trusted application function network element 201, a network open function network element 202, a unified data management network element 203, a session management function network element 204, and a user plane function network element 205 may be included.

[0052] Among them, the non-trusted application function network element 201 can determine the identifier corresponding to the target user, and send the identifier to the network open function network element 202. Then, the network open function network element 202 can send the identifier to the unified data management network element 203 to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element 204 to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element 205 to obtain the terminal public address corresponding to the terminal private address.

[0053] Finally, the non-trusted application function network element 201 can obtain the terminal public address corresponding to the target user, and collect the user application data through the terminal public address.

[0054] Those skilled in the art will know that Figure 2 The number of the non-trusted application function network element 201, the network open function network element 202, the unified data management network element 203, the session management function network element 204, and the user plane function network element 205 is only illustrative, and the embodiment of the present disclosure does not limit this. The following is a detailed description of this exemplary implementation method in conjunction with the drawings and embodiments.

[0055] First, a method for collecting user application data is provided in an embodiment of the present disclosure. The method can be executed by any network data analysis function network element or trusted application function network element.

[0056] Figure 3 A flow chart of a method for collecting user application data in an embodiment of the present disclosure is shown as follows: Figure 3 As shown, the user application data collection method provided in the embodiment of the present disclosure includes the following steps S302 to S310.

[0057] S302: Determine an identifier corresponding to the target user.

[0058] Exemplarily, when the method is performed by a network data analysis function network element, the identifier may be a universal public user identifier or a subscription permanent identifier. When the method is performed by a trusted application function network element, the identifier is a subscription permanent identifier.

[0059] It should be noted that the network data analysis function network element can be expressed as NWDAF (Network DataAnalytics Function) network element. The general public user identifier can be expressed as GPSI (Generic Public Subscription Identifier). The subscription permanent identifier can be expressed as SUPI (Subscription Permanent Identifier). The application function network element can be expressed as AF (Application Function) network element.

[0060] Exemplarily, the identifier may be pre-deployed in the NWDAF network element. In an exemplary embodiment, when the method is performed by a trusted AF network element, the identifier may be a SUPI. In this case, determining the identifier corresponding to the target user may include: receiving a network data analysis function request sent by the NWDAF network element; and obtaining the SUPI through the network data analysis function request.

[0061] Exemplarily, the network data analysis function request sent by the NWDAF network element may include the SUPI. The trusted AF network element may parse the network data analysis function request to obtain the SUPI.

[0062] Alternatively, in another exemplary embodiment, when the method is executed by a trusted AF network element, the identifier is a SUPI. At this time, the trusted AF network element may send an identifier request to the NWDAF network element, thereby receiving the SUPI returned by the NWDAF network element.

[0063] S304: Send an identifier to the unified data management network element to obtain a protocol data unit session identifier corresponding to the target user.

[0064] It should be noted that the unified data management network element can be expressed as a UDM (Unified Data Management) network element.

[0065] In one embodiment, an identifier is sent to a UDM network element to obtain a protocol data unit session identifier corresponding to a target user, including: sending an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to the UDM network element; receiving at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the UDM network element; determining at least one target protocol data unit session identifier for user application data collection from the at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier.

[0066] Exemplarily, when the unified data management network element returns a single network slice selection assistance information and a data network name, the number of target protocol data unit session identifiers can be one.

[0067] It should be noted that the protocol data unit session identifier can be a PDU session ID (Protocol DataUnit session Identity). The single network slice selection assistance information can be expressed as S-NSSAI (Single-Network Slice Selection Assistance Information). The data network name can be expressed as DNN (Date Network Name). The session management function network element identifier can be used to indicate the corresponding SMF network element, and the protocol data unit session identifier can be used to indicate the corresponding PDU session.

[0068] In a possible implementation, a plurality of protocol data unit session identifiers may be stored in the UDM network element. Among them, any protocol data unit session identifier has a corresponding session management function network element identifier, S-NSSAI and DNN. Therefore, sending at least one of the S-NSSAI and DNN to the UDM network element can cause the UDM network element to screen the various session management function network element identifiers stored therein to determine the session management function network element identifier and protocol data unit session identifier that need to be returned.

[0069] Exemplarily, when only the identifier is sent to the UDM network element, the UDM network element can return multiple protocol data unit session identifiers and multiple session management function network element identifiers. Alternatively, when the identifier and S-NSSAI are sent to the UDM network element, the UDM network element can filter through the S-NASSAI to obtain multiple target protocol data unit session identifiers corresponding to the S-NASSAI and corresponding multiple session management function network element identifiers. Alternatively, when the identifier, S-NSSAI and DNN are sent to the UDM network element, the UDM network element can filter through the S-NASSAI and DNN to obtain a target protocol data unit session identifier corresponding to both the S-NASSAI and the DNN and a corresponding session management function network element identifier.

[0070] S306: Send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user.

[0071] In some embodiments, when at least one target protocol data unit session identifier for user application data collection is determined in step S304, the protocol data unit session identifier is sent to the session management function network element, including: sending the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0072] It should be noted that the session management function network element can be expressed as an SMF (Session Management Function) network element. The terminal private address can be expressed as a private UE IP address (private User Equipment Internet Protocol address). Among them, the SMF network element can include multiple terminal private addresses, so the SMF network element can be used to match the protocol data unit session identifier with the terminal private address.

[0073] In some embodiments, a protocol data unit session identifier is sent to an SMF network element to obtain a terminal private address corresponding to a target user, including: sending a protocol data unit session identifier to an SMF network element to obtain a terminal private address corresponding to the target user and a user plane function network element address corresponding to the protocol data unit session identifier.

[0074] In an exemplary embodiment, the SMF network element may also be used to determine a UPF (User plane Function) network element address serving the PDU session corresponding to the protocol data unit session identifier, i.e., a user plane function network element address. Afterwards, the user plane function network element address may be returned together with the terminal private address.

[0075] S308: Send the terminal private address to the user plane functional network element to obtain the terminal public address corresponding to the terminal private address.

[0076] It should be noted that the terminal public address can be expressed as a public UE IP address (public User Equipment Internet Protocol address). It should be noted that the user plane function network element can match the terminal private address with the terminal public address. The embodiment of the present disclosure does not limit the matching method.

[0077] In some embodiments, when the terminal private address corresponding to the target user and the user plane function network element address corresponding to the protocol data unit session identifier are obtained in step S306, the terminal private address is sent to the user plane function network element, including: sending the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0078] S310, collecting user application data through the terminal public address.

[0079] It should be noted that the user application data may be relevant data in UE Application (user equipment application).

[0080] In an exemplary embodiment, when the method is performed by a NWDAF network element, the identifier is a GPSI or a SUPI. In this case, collecting user application data through a terminal public address includes: associating the terminal public address with a universal public user identifier or a subscription permanent identifier to collect user application data through the terminal public address.

[0081] Exemplarily, the NWDAF network element can receive the terminal public address returned by the user plane function network element, and then associate the terminal public address with the identifier, so as to request the AF network element to collect user application data through the terminal public address, and the AF network element will send the collected user application data to the NWDAF network element.

[0082] In an exemplary embodiment, when the method is performed by a trusted AF network element, the identifier is SUPI. In this case, collecting user application data through the terminal public address includes: associating the terminal public address with the subscription permanent identifier to collect user application data through the terminal public address.

[0083] Exemplarily, the trusted AF network element may store the terminal public address corresponding to the user application when establishing a user plane link between the user application and the trusted AF network element. It should be noted that the terminal public address may be used to identify a PDU session for collecting user application data.

[0084] Since the authorized AF network element cannot match the terminal public address with the terminal private address, the authorized AF network element can match the terminal private address with the terminal public address through the user plane function network element. After that, the authorized AF network element can collect user application data through the terminal public address.

[0085] It should be noted that in the scenario where the operator deploys NAT, the NWDAF network element collects user application data, thereby realizing the process of analyzing the data requested by the consumer network element. Through the method provided in the present disclosure, user application data can be collected through the PDU session between the AF network element and the user application. In addition, in the scenario where the operator deploys NAT, other network elements in 5GC may also need to collect user application data. For example, the PCF network element may need user application data for policy formulation. At this time, user application data can also be collected through the method provided in the present disclosure.

[0086] The method provided by the embodiment of the present disclosure can determine the corresponding PDU session identifier through the identifier, and determine the terminal private address through the PDU session identifier. After that, the terminal private address and the terminal public address can be matched through the corresponding UPF network element. Therefore, the present disclosure realizes the user application data collection. In addition, the method of the present disclosure has less modification to each network element, reducing the modification cost.

[0087] For example, Figure 4 FIG. 1 shows a flow chart of a method for collecting user application data through an NWDAF network element. Figure 4 As shown, the method may include the following steps S402 to S412.

[0088] S402: The NWDAF network element sends first request information to the UDM network element.

[0089] Exemplarily, the first request information includes an identifier, and the identifier may be SUPI or GPSI. In a possible implementation manner, the first request information sent to the UDM network element may be expressed as Nudm_UECM_Get_Request.

[0090] S404: The UDM network element returns first response information corresponding to the first request information to the NWDAF network element. The first response information includes a protocol data unit session identifier corresponding to the target user.

[0091] In a possible implementation manner, the first response information corresponding to the first request information may be expressed as Nudm_UECM_Get_Response.

[0092] S406, the NWDAF network element sends a second request message to the SMF network element, where the second request message includes a protocol data unit session identifier.

[0093] In a possible implementation manner, the second request information sent to the SMF network element may be expressed as Nsmf_EventExposure_Subscribe. The second request information includes information of the private address of the requesting terminal and the address of the UPF network element.

[0094] S408, the SMF network element returns the second response information corresponding to the second request information to the NWDAF network element, and the second response information includes the terminal private address and the UPF network element address.

[0095] In a possible implementation manner, the second response information corresponding to the second request information may be expressed as Nsmf_EventExposure_Notification.

[0096] S410, the NWDAF network element requests the corresponding terminal public address from the corresponding UPF network element according to the above terminal private address and UPF network element address.

[0097] S412, the NWDAF network element collects user application data through the terminal public address.

[0098] Exemplarily, the NWDAF network element may send the terminal public address to the AF network element, or may send the terminal public address to the NEF network element, and forward it to the AF network element through the NEF network element, so that user application data can be collected through the AF network element.

[0099] For example, Figure 5 FIG. 1 shows a flow chart of a method for collecting user application data through a trusted AF network element. Figure 5 As shown, the method may include the following steps S502 to S514.

[0100] S502: The trusted AF network element stores the terminal public address corresponding to the user application.

[0101] S504, the trusted AF network element sends a first request message to the UDM network element.

[0102] Exemplarily, the first request information includes an identifier, and the identifier may be a SUPI. In a possible implementation manner, the first request information sent to the UDM network element may be expressed as Nudm_UECM_Get_Request.

[0103] S506, the UDM network element returns first response information corresponding to the first request information to the authorized AF network element. The first response information includes a protocol data unit session identifier corresponding to the target user.

[0104] In a possible implementation manner, the first response information corresponding to the first request information may be expressed as Nudm_UECM_Get_Response.

[0105] S508, the authorized AF network element sends a second request message to the SMF network element, where the second request message includes a protocol data unit session identifier.

[0106] In a possible implementation manner, the second request information sent to the SMF network element may be expressed as Nsmf_EventExposure_Subscribe. The second request information includes information of the private address of the requesting terminal and the address of the UPF network element.

[0107] S510, the SMF network element returns the second response information corresponding to the second request information to the authorized AF network element, and the second response information includes the terminal private address and the UPF network element address.

[0108] In a possible implementation manner, the second response information corresponding to the second request information may be expressed as Nsmf_EventExposure_Notification.

[0109] S512, the authorized AF network element requests the corresponding UPF network element for the corresponding terminal public address based on the above terminal private address and UPF network element address.

[0110] S514, the authorized AF network element collects user application data through the terminal public address.

[0111] For example, Figure 6 A flow chart of a method for NF network element to obtain user application data analysis results is shown. Figure 6 As shown, the method may include the following steps S602 to S618.

[0112] S602, the NF network element sends an analysis request to the NWDAF network element.

[0113] In an exemplary embodiment, the analysis request sent to the NWDAF network element may be expressed as Nnwdaf_AnalyticsSubscription_Subscribe.

[0114] S604, the NWDAF network element performs an AF network element discovery (AF Discovery) process.

[0115] Afterwards, when the AF network element is a trusted AF network element, step S606 is executed. When the AF network element is a non-trusted AF network element, step S608 is executed.

[0116] S606: The NWDAF network element sends an NWDAF request to the trusted AF network element.

[0117] In an exemplary embodiment, the NWDAF request sent to the AF network element may be expressed as Naf_Event_Exposure_Subscribe. The NWDAF request may include an identifier. Therefore, the trusted AF network element may determine the identifier through the NWDAF request, so as to perform subsequent user application data collection.

[0118] S608, the NWDAF network element sends a NEF request to the non-trusted AF network element through the NEF network element.

[0119] In an exemplary embodiment, the NEF request may include an identifier. Therefore, the untrusted AF network element may determine the identifier through the NEF request, so as to perform subsequent user application data collection.

[0120] S610: The AF network element collects user application data.

[0121] Afterwards, when the AF network element is a trusted AF network element, step S612 is executed. When the AF network element is a non-trusted AF network element, step S614 is executed.

[0122] S612: The authorized AF network element returns the user application data collection result to the NWDAF network element.

[0123] Exemplarily, the user application data collection result may be included in the response information corresponding to the NWDAF request. The response information may be expressed as Naf_Event_Exposure_Notify.

[0124] S614, the non-trusted AF network element returns the user application data collection result to the NWDAF network element through the NEF network element.

[0125] S616, the NWDAF network element analyzes the user application data collection result to obtain the user application data analysis result.

[0126] S618, the NWDAF network element returns the user application data analysis result to the NF network element.

[0127] In an exemplary embodiment, the user application data analysis result returned to the NF network element can be expressed as Nnwdaf_AnalyticsSubscription_Notify.

[0128] It should be noted that, illustratively, the trusted AF network element may associate the user application data with the NWDAF request, thereby realizing the collection of the user application data.

[0129] For example, Figure 7 FIG. 1 is a flow chart of another method for collecting user application data in an embodiment of the present disclosure. Figure 7 As shown, the user application data collection method provided in the embodiment of the present disclosure includes the following steps S702 to S706.

[0130] According to another aspect of the present disclosure, a method for collecting user application data is provided, the method being performed by an untrusted AF network element, comprising:

[0131] S702: Determine an identifier corresponding to the target user.

[0132] In some embodiments, the identifier may be a universal public user identifier, and determining the identifier corresponding to the target user includes: receiving a network data analysis function request sent by a network data analysis function network element; and obtaining the universal public user identifier through the network data analysis function request.

[0133] In an exemplary embodiment, the NWDAF network element may send the identifier to the NEF network element, which may then send the identifier to the untrusted AF network element.

[0134] S704, sending an identifier to the network open function network element to obtain the terminal public address corresponding to the target user, wherein the network open function network element is used to send an identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

[0135] In some embodiments, the network open function network element is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; and send the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0136] Exemplarily, when the unified data management network element returns a single network slice selection assistance information and a data network name, the number of target protocol data unit session identifiers can be one.

[0137] In some embodiments, the network open function network element is used to send a protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user and the user plane function network element address corresponding to the protocol data unit session identifier; and send the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0138] S706, collecting user application data through the terminal public address.

[0139] In some embodiments, the identifier may be a universal public user identifier. In this case, collecting user application data through the terminal public address includes: associating the terminal public address with the universal public user identifier to collect user application data through the terminal public address.

[0140] It should be noted that the implementation method of each step in S702 to S706 can refer to the corresponding description in the above S302 to S310, which will not be repeated here.

[0141] For example, Figure 8 FIG. 1 shows a flow chart of a method for collecting user application data through a non-trusted AF network element. Figure 8 As shown, the method may include the following steps S802 to S814.

[0142] S802: The untrusted AF network element stores the terminal public address corresponding to the user application.

[0143] S804, the non-trusted AF network element requests the NEF network element for the terminal public address.

[0144] In a possible implementation manner, the information requesting the terminal public address sent to the NEF network element may be expressed as Nnef_UEid_Get_Request.

[0145] S806: The NEF network element sends first request information to the UDM network element.

[0146] Exemplarily, the first request information includes an identifier, and the identifier may be a GPSI. In a possible implementation manner, the first request information sent to the UDM network element may be expressed as Nudm_UECM_Get_Request.

[0147] S808, the UDM network element returns first response information corresponding to the first request information to the non-trusted AF network element. The first response information includes a protocol data unit session identifier corresponding to the target user.

[0148] In a possible implementation manner, the first response information corresponding to the first request information may be expressed as Nudm_UECM_Get_Response.

[0149] S810, the NEF network element sends a second request message to the SMF network element, where the second request message includes a protocol data unit session identifier.

[0150] In a possible implementation manner, the second request information sent to the SMF network element may be expressed as Nsmf_EventExposure_Subscribe. The second request information includes information of the private address of the requesting terminal and the address of the UPF network element.

[0151] S812, the SMF network element returns the second response information corresponding to the second request information to the NEF network element, and the second response information includes the terminal private address and the UPF network element address.

[0152] In a possible implementation manner, the second response information corresponding to the second request information may be expressed as Nsmf_EventExposure_Notification.

[0153] S814, the NEF network element requests the corresponding terminal public address from the corresponding UPF network element according to the above terminal private address and UPF network element address.

[0154] S816, the UPF network element determines the terminal public address according to the terminal private address and the internal mapping, and returns the terminal public address to the NEF network element.

[0155] S818, the NEF network element returns the terminal public address to the untrusted AF network element.

[0156] In a possible implementation manner, the information returned to the non-trusted AF network element may be represented as Nnef_UEid_Get_Response.

[0157] S820, the non-trusted AF network element associates the user application data with the NWDAF request, thereby realizing the collection of the user application data.

[0158] Therefore, the method provided in the embodiment of the present disclosure can collect user application data through any network element among the NWDAF network element, the trusted AF network element, and the untrusted AF network element. Therefore, the embodiment of the present disclosure can be applicable to more application scenarios.

[0159] Based on the same inventive concept, the present disclosure also provides a user application data collection device, as described in the following embodiments. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0160] Fig. 9 A schematic diagram of a user application data collection device in an embodiment of the present disclosure is shown. Fig. 9 As shown, the device is applied to a network data analysis function network element or a credit application function network element, including:

[0161] A first identifier acquisition module 901, used to determine an identifier corresponding to a target user;

[0162] The protocol data unit session identifier acquisition module 902 is used to send an identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user;

[0163] The user terminal private address acquisition module 903 is used to send a protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user;

[0164] A first public user terminal address acquisition module 904 is used to send a terminal private address to a user plane function network element to acquire a terminal public address corresponding to the terminal private address;

[0165] The first data collection module 905 is used to collect user application data through the terminal public address.

[0166] In some embodiments of the present disclosure, the protocol data unit session identifier acquisition module 902 is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from the at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier;

[0167] The user terminal private address acquisition module 903 is used to send a target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0168] In some embodiments of the present disclosure, the user terminal private address acquisition module 903 is used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user and a user plane function network element address corresponding to the protocol data unit session identifier;

[0169] The first public user terminal address obtaining module 904 is configured to send a terminal private address to a user plane function network element corresponding to the user plane function network element address.

[0170] In some embodiments of the present disclosure, when the device is applied to a network data analysis function network element, the identifier is a universal public user identifier or a subscription permanent identifier; the first data collection module 905 is used to associate the terminal public address with the universal public user identifier or the subscription permanent identifier to collect user application data through the terminal public address.

[0171] In some embodiments of the present disclosure, when the device is applied to a credit-granting application function network element, the identifier is a subscription permanent identifier; the first identifier acquisition module 901 is used to receive a network data analysis function request sent by the network data analysis function network element; and acquire the subscription permanent identifier through the network data analysis function request;

[0172] The first data collection module 905 is used to associate the terminal public address with the subscription permanent identifier to collect user application data through the terminal public address.

[0173] Fig.10 A schematic diagram of another user application data collection device in an embodiment of the present disclosure is shown. Fig.10 As shown, the device is applied to a non-trusted application function network element, including:

[0174] The second identifier acquisition module 1001 is used to determine the identifier corresponding to the target user;

[0175] The second public user terminal address acquisition module 1002 is used to send an identifier to the network open function network element to obtain a terminal public address corresponding to the target user;

[0176] The second data collection module 1003 is used to collect user application data through the terminal public address.

[0177] Among them, the network open function network element is used to send an identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

[0178] In some embodiments of the present disclosure, the network open function network element is used to send an identifier, and zero to two of a single network slice selection auxiliary information and a data network name to a unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; and send the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

[0179] In some embodiments of the present disclosure, the network open function network element is used to send a protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to a target user and a user plane function network element address corresponding to the protocol data unit session identifier; and send the terminal private address to the user plane function network element corresponding to the user plane function network element address.

[0180] In some embodiments of the present disclosure, the identifier is a universal public user identifier, and the second identifier acquisition module 1001 is used to receive a network data analysis function request sent by a network data analysis function network element; and acquire the universal public user identifier through the network data analysis function request;

[0181] The second data collection module 1003 is used to associate the terminal public address with the universal public user identifier to collect user application data through the terminal public address.

[0182] The device provided by the embodiment of the present disclosure can determine the corresponding PDU session identifier through the identifier, and determine the terminal private address through the PDU session identifier. After that, the terminal private address and the terminal public address can be matched through the corresponding UPF network element. Therefore, the present disclosure realizes the user application data collection. In addition, the method of the present disclosure has less modification to each network element, reducing the modification cost.

[0183] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0184] Refer to the following Fig.11 1100 according to this embodiment of the present disclosure is described. Fig.11 The electronic device 1100 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0185] like Fig.11 As shown, the electronic device 1100 is in the form of a general computing device. The components of the electronic device 1100 may include but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including the storage unit 1120 and the processing unit 1110).

[0186] The storage unit stores program code, which can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps of various exemplary embodiments of the present disclosure described in the above “Specific Implementation Methods” section of this specification.

[0187] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 11201 and / or a cache storage unit 11202 , and may further include a read-only storage unit (ROM) 11203 .

[0188] The storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0189] Bus 1130 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0190] The electronic device 1100 may also communicate with one or more external devices 1140 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1100, and / or communicate with any device that enables the electronic device 1100 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1150. Furthermore, the electronic device 1100 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1160. As shown, the network adapter 1160 communicates with other modules of the electronic device 1100 via a bus 1130. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0191] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0192] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the above-mentioned method of the present disclosure is stored thereon. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Specific Implementation Methods” section of this specification.

[0193] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0194] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0195] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0196] In a specific implementation, the program code for performing the operation of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0197] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0198] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0199] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0200] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The description and examples are to be regarded as exemplary only, and the true scope of the present disclosure is indicated by the appended claims.

Claims

1. A method for collecting user application data, It is characterized in that The method is performed by a network data analysis function network element or a trusted application function network element, and includes: Determine an identifier corresponding to the target user; Sending the identifier to a unified data management network element to obtain a protocol data unit session identifier corresponding to the target user; Sending the protocol data unit session identifier to a session management function network element to obtain a terminal private address corresponding to the target user; Sending the terminal private address to the user plane functional network element to obtain a terminal public address corresponding to the terminal private address; User application data is collected through the terminal public address.

2. The user application data collection method according to claim 1, It is characterized in that The sending the identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user includes: Sending the identifier, and zero to two of the single network slice selection assistance information and the data network name to the unified data management network element; Receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of a single network slice selection auxiliary information and a data network name returned by the unified data management network element; Determine at least one target protocol data unit session identifier for collecting user application data from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; The sending of the protocol data unit session identifier to the session management function network element includes: The target protocol data unit session identifier is sent to a session management function network element corresponding to the session management function network element identifier.

3. The user application data collection method according to claim 1, It is characterized in that The sending the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user includes: Sending the protocol data unit session identifier to the session management function network element to obtain a terminal private address corresponding to the target user and a user plane function network element address corresponding to the protocol data unit session identifier; The sending the terminal private address to the user plane function network element includes: The terminal private address is sent to the user plane function network element corresponding to the user plane function network element address.

4. The user application data collection method according to any one of claims 1 to 3, It is characterized in that When the method is performed by a network data analysis function network element, the identifier is a universal public user identifier or a subscription permanent identifier; Wherein, the collecting of user application data through the terminal public address includes: The terminal public address is associated with the universal public user identifier or the subscription permanent identifier to collect user application data through the terminal public address.

5. The user application data collection method according to any one of claims 1 to 3, It is characterized in that When the method is executed by a trusted application function network element, the identifier is a subscription permanent identifier, and the step of determining the identifier corresponding to the target user includes: Receiving a network data analysis function request sent by the network data analysis function network element; Obtaining the subscription permanent identifier through the network data analysis function request; The collecting of user application data through the terminal public address includes: The terminal public address is associated with the subscription permanent identifier to collect user application data through the terminal public address.

6. A method for collecting user application data, It is characterized in that The method is performed by a non-trusted application function network element, and includes: Determine an identifier corresponding to the target user; Sending the identifier to a network open function network element to obtain a terminal public address corresponding to the target user; Collecting user application data through the terminal public address; Among them, the network open function network element is used to send the identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

7. The user application data collection method according to claim 6, It is characterized in that The network open function network element is used to send the identifier, and zero to two of the single network slice selection auxiliary information and the data network name to the unified data management network element; receive at least one session management function network element identifier, at least one protocol data unit session identifier, and zero to two of the single network slice selection auxiliary information and the data network name returned by the unified data management network element; Determine at least one target protocol data unit session identifier for user application data collection from at least one protocol data unit session identifier, and a session management function network element identifier corresponding to the target protocol data unit session identifier; send the target protocol data unit session identifier to the session management function network element corresponding to the session management function network element identifier.

8. The user application data collection method according to claim 6, It is characterized in that The network open function network element is used to send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user and the user plane function network element address corresponding to the protocol data unit session identifier; and send the terminal private address to the user plane function network element corresponding to the user plane function network element address.

9. The user application data collection method according to any one of claims 6 to 8, It is characterized in that The identifier is a universal public user identifier, and the identifier corresponding to the target user is determined, including: Receiving a network data analysis function request sent by a network data analysis function network element; Obtaining the universal public user identifier through the network data analysis function request; The collecting of user application data through the terminal public address includes: The terminal public address is associated with the universal public user identifier to collect user application data through the terminal public address.

10. A user application data collection device, It is characterized in that The device is applied to a network data analysis function network element or a credit application function network element, and includes: A first identifier acquisition module, used to determine an identifier corresponding to a target user; A protocol data unit session identifier acquisition module, used to send the identifier to a unified data management network element to acquire a protocol data unit session identifier corresponding to the target user; A user terminal private address acquisition module, used to send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; A first public user terminal address acquisition module, configured to send the terminal private address to a user plane function network element to acquire a terminal public address corresponding to the terminal private address; The first data collection module is used to collect user application data through the terminal public address.

11. A user application data collection device, It is characterized in that The device is applied to a non-trusted application function network element, including: A second identifier acquisition module, used to determine an identifier corresponding to a target user; A second public user terminal address acquisition module, used to send the identifier to the network open function network element to obtain the terminal public address corresponding to the target user; The second data collection module is used to collect user application data through the terminal public address. Among them, the network open function network element is used to send the identifier to the unified data management network element to obtain the protocol data unit session identifier corresponding to the target user; send the protocol data unit session identifier to the session management function network element to obtain the terminal private address corresponding to the target user; send the terminal private address to the user plane function network element to obtain the terminal public address corresponding to the terminal private address.

12. An electronic device, It is characterized in that include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the user application data collection method according to any one of claims 1 to 9 by executing the executable instructions.

13. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the user application data collection method according to any one of claims 1 to 9 is implemented.

Images