A method, device, related equipment and medium for obtaining data information

Abstract

The embodiment of the present application provides a data information acquisition method, device, related equipment and medium, wherein one method includes: acquiring a capability call contract request sent by a second functional network element based on contract request parameter information; the contract request parameter information is determined by the authentication response parameter information; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second functional network element based on the first contract rule; obtaining access parameter information from the contract request parameter information, and performing contract verification on the capability call contract request based on the access parameter information; generating capability call contract response information for the capability call contract request when the contract verification is successful, and returning the capability call contract response information to the second functional network element; the capability call contract response information is used to indicate that the second functional network element accesses the first functional network element. The present application can improve the efficiency of data information acquisition.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, specifically to the field of 5G (5th Generation mobile network) technology, and in particular to a data information acquisition method, device, related equipment and medium. Background Art

[0002] In the core network of the 5G system, there is a network exposure function device that can have the functions of collecting, analyzing and reorganizing network capabilities. The network exposure function device can be a network capability exposure function (NEF) entity that can support one or more functions. Among them, it can be understood that each network element of the 5G core network and the external network element need to notify the NEF entity of their network service capabilities, so that each network element can obtain the service capability information of the network element of interest through the NEF entity. This means that in the existing 5G system, it is difficult to directly interact with data between network elements in the external network and network elements in the internal network (i.e., the 5G core network), that is, it is necessary to indirectly provide information conversion and communication between the external network and the internal network (5G core network) through the NEF entity, thereby reducing the efficiency of obtaining information between these network elements. Summary of the invention

[0003] The embodiments of the present application provide a data information acquisition method, apparatus, related equipment and medium, which can improve the efficiency of information acquisition between network elements.

[0004] On the one hand, an embodiment of the present application provides a method for acquiring data information, which is executed by a first functional network element; the method includes:

[0005] Obtaining a capability call signing request sent by the second functional network element based on the signing request parameter information; the signing request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second functional network element;

[0006] Acquire access parameter information for requesting access to the first function network element from the contract request parameter information carried by the capability call contract request, and perform contract verification on the capability call contract request based on the access parameter information;

[0007] When the contract verification is successful, capability call contract response information is generated for the capability call contract request, and the capability call contract response information is returned to the second functional network element; the capability call contract response information is used to instruct the second functional network element to access the first functional network element.

[0008] On the one hand, an embodiment of the present application provides a method for acquiring data information, which is executed by a first functional network element; the method includes:

[0009] receiving a capability invocation request forwarded by a network open function device associated with a first function network element; the capability invocation request is sent by a second function network element associated with the network open function device, and the capability invocation request carries request parameter data information;

[0010] Obtaining request parameter data information from the capability call request, and performing authentication processing on the capability call request based on the request parameter data information;

[0011] When the authentication is successful, a capability call request is received, and request response parameter information for the capability call request is generated, and the request response parameter information is forwarded to the second functional network element through the network open function device; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0012] On the one hand, an embodiment of the present application provides a method for acquiring data information, which is executed by a second functional network element; the method includes:

[0013] receiving the authentication response parameter information returned by the network open function device, and determining the contract request parameter information based on the authentication response parameter information; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second function network element;

[0014] Adding the contract request parameter information to the capability call contract request, and sending the capability call contract request to the first functional network element, so that the first functional network element performs contract verification on the capability call contract request according to the access parameter information in the contract request parameter information;

[0015] Receive capability call contract response information returned by the first functional network element when the contract verification is successful, and access the first functional network element based on the capability call contract response information.

[0016] On the one hand, an embodiment of the present application provides a method for acquiring data information, which is executed by a second functional network element; the method includes:

[0017] Sending a capability call request to a network open function device associated with the second function network element, so that the network open function device forwards the capability call request to the first function network element, and the first function network element is used to authenticate the capability call request based on the request parameter data information carried in the capability call request;

[0018] Receive request response parameter information for the capability call request returned by the first functional network element through the network open function device when the authentication is successful; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0019] On the one hand, an embodiment of the present application provides a data information acquisition device, the device comprising:

[0020] A contract request acquisition module, used to acquire a capability call contract request sent by the second functional network element based on the contract request parameter information; the contract request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second functional network element;

[0021] A contract verification module, used to obtain access parameter information for requesting access to the first function network element from the contract request parameter information carried by the capability call contract request, and perform contract verification on the capability call contract request based on the access parameter information;

[0022] The contract signing response returning module is used to generate capability calling contract signing response information for the capability calling contract signing request when the contract signing verification is successful, and return the capability calling contract signing response information to the second functional network element; the capability calling contract signing response information is used to instruct the second functional network element to access the first functional network element.

[0023] The authentication response parameter information at least includes authentication success indication information; the authentication success indication information is obtained by the network open function device when confirming the reception of the capability call request after successful authentication processing; the capability call request is generated by the second function network element based on the request parameter data information; the requested event type in the request parameter data information at least includes: the target event type associated with the first function network element in the authentication response parameter information; the target event type is the same as the event type of the signed event in the capability call signing response information;

[0024] The device also includes:

[0025] The event response returning module is used to return the event response information of the signed event to the second functional network element within the interval time of the signing request parameter information when it is detected that the signed event corresponding to the target event type occurs.

[0026] Among them, the first functional network element is the first application functional entity, and the second functional network element is the second application functional entity; the request parameter data information includes at least: identification information of the second application functional entity, target event type, delay index for responding to events, effective time for capability call, call number threshold for capability call, and interval time for responding to events.

[0027] On the one hand, an embodiment of the present application provides a data information acquisition device, the device comprising:

[0028] A call request receiving module, used to receive a capability call request forwarded by a network open function device associated with a first function network element; the capability call request is sent by a second function network element associated with the network open function device, and the capability call request carries request parameter data information;

[0029] An authentication processing module is used to obtain request parameter data information from the capability call request and perform authentication processing on the capability call request based on the request parameter data information;

[0030] The request response returning module is used to receive the capability calling request when the authentication is successful, and generate the request response parameter information for the capability calling request, and forward the request response parameter information to the second function network element through the network open function device; the request response parameter information is used to instruct the second function network element to access the first function network element.

[0031] The request parameter data information carries identification information of the second function network element for which the subscription is requested, and authentication information of the second function network element;

[0032] Among them, the authentication processing module includes:

[0033] An authentication information acquisition unit, used to acquire authentication information from a capability call request;

[0034] A searching unit, configured to search for contract verification information matching the identification information of the second functional network element;

[0035] The authentication processing unit is used to authenticate the authentication information based on the contract verification information if the contract verification information is found, and to authorize the capability call request when the authentication is successful.

[0036] The request parameter data information carries the target event type for the requested contract; the request response return module includes:

[0037] A legal request receiving unit, used to determine that the capability invocation request is a legal request when the authentication is successful, receive the legal request, and generate a signing instruction for the legal request;

[0038] An event type signing unit, used to determine the target event type as a signing event type based on the signing instruction, and generate request response parameter information for the signing event type;

[0039] The request response sending unit is used to send the request response parameter information to the network open function device, so that the network open function device forwards the request response parameter information to the second function network element.

[0040] Among them, the first functional network element is deployed on the first platform; the second functional network element is deployed on the second platform; the first platform is different from the second platform, or the first platform and the second platform are the same platform.

[0041] On the one hand, an embodiment of the present application provides a data information acquisition device, the device comprising:

[0042] An authentication response receiving module is used to receive the authentication response parameter information returned by the network open function device, and determine the contract request parameter information based on the authentication response parameter information; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second function network element;

[0043] A contract signing request sending module, used to add contract signing request parameter information to the capability call contract signing request, and send the capability call contract signing request to the first functional network element, so that the first functional network element performs contract signing verification on the capability call contract signing request according to the access parameter information in the contract signing request parameter information;

[0044] The contract signing response receiving module is used to receive the capability calling contract signing response information returned by the first functional network element when the contract signing verification is successful, and access the first functional network element based on the capability calling contract signing response information.

[0045] The device further comprises:

[0046] An identification acquisition module, used to acquire the first identification information of the second functional network element, the authentication information of the second functional network element, and the target event type requested by the second functional network element;

[0047] A request parameter determination module, used to determine request parameter data information based on the first identification information, the authentication information and the target event type;

[0048] A call request generation module is used to add request parameter data information to the capability call request; the capability call request is used to instruct the network open function device to authenticate the authentication information based on the contract verification information matching the first identification information, and when the authentication is successful and it is determined that the target event type is associated with the first functional network element, generate authentication response parameter information for the capability call request.

[0049] Among them, the authentication response parameter information includes at least one of the following: prompt information for indicating the reception of the capability call request, the second identification information of the first functional network element, the IP (Internet Protocol) address information of the first functional network element, the endpoint address (Endpoint Address) information of the first functional network element and the access parameter information; wherein the access parameter information is the access token information or target key information configured by the network open function device for the second functional network element for accessing the first functional network element.

[0050] Among them, the contract request parameter information includes at least: the first identification information of the second functional network element, the target event type, the access parameter information, the delay indicator for responding to the event, the effective time for capability calling, the call number threshold for capability calling, and the interval time for responding to the event.

[0051] On the one hand, an embodiment of the present application provides a data information acquisition device, the device comprising:

[0052] A call request sending module, used to send a capability call request to a network open function device associated with a second function network element, so that the network open function device forwards the capability call request to the first function network element, and the first function network element is used to authenticate the capability call request based on the request parameter data information carried in the capability call request;

[0053] The request response receiving module is used to receive the request response parameter information for the capability call request returned by the first functional network element through the network open function device when the authentication is successful; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0054] An embodiment of the present application provides a computer device, including: a processor and a memory;

[0055] The processor is connected to the memory, wherein the memory is used to store a computer program. When the computer program is executed by the processor, the computer device executes the method provided in the embodiment of the present application.

[0056] On the one hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program is suitable for being loaded and executed by a processor so that a computing device having the processor executes the method provided by the embodiment of the present application.

[0057] In one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the 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 method provided in the embodiment of the present application.

[0058] In the embodiment of the present application, the first functional network element, the second functional network element and the network open function device can ensure, through corresponding signing rules, that the second functional network element can be directly connected to the first functional network element, so that data interaction can be directly realized between the first functional network element and the second functional network element, thereby improving the efficiency of obtaining information between the two network elements. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0060] Figure 1 is a schematic diagram of a network architecture of a communication system provided in an embodiment of the present application;

[0061] Figure 2 This is a schematic diagram of a network architecture based on a 5G communication system provided in an embodiment of the present application;

[0062] Figure 3 This is a schematic diagram of a process for obtaining data information provided by an embodiment of the present application;

[0063] Figure 4 This is a schematic diagram of a scenario for data interaction provided by an embodiment of the present application;

[0064] Figure 5 This is a schematic diagram of a process for obtaining data information provided by an embodiment of the present application;

[0065] Figure 6 This is a schematic diagram of a scenario in which data interaction between network elements is realized through a network open function device transfer provided by an embodiment of the present application;

[0066] Figure 7 This is a schematic diagram of a process for obtaining data information provided by an embodiment of the present application;

[0067] Figure 8 This is a schematic diagram of a process for obtaining data information provided by an embodiment of the present application;

[0068] Fig. 9 It is an interactive timing diagram of a data information acquisition method provided in an embodiment of the present application;

[0069] Fig.10 is a structural diagram of a data information acquisition device provided in an embodiment;

[0070] Fig.11 is a structural diagram of a data information acquisition device provided in an embodiment;

[0071] Fig.12 is a structural diagram of a data information acquisition device provided in an embodiment;

[0072] Fig.13 is a structural diagram of a data information acquisition device provided in an embodiment;

[0073] Fig.14 is a structural schematic diagram of a computer device provided in an embodiment of the present application;

[0074] Fig.15 It is a structural diagram of a data information acquisition system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0076] For further information, see Figure 1 , Figure 1 : is a schematic diagram of a network architecture of a communication system provided in an embodiment of the present application. The communication system may include but is not limited to a 5G communication system, which will not be limited here. Figure 1 The network architecture shown may include a network open function device cluster A, a first function network element cluster B located in a non-trusted domain, and a second function network element cluster C located in a trusted domain.

[0077] The network open function device cluster A may include one or more network open function devices, and the number of network open function devices is not limited. Figure 1 The network exposure function device 1 and the network exposure function device 2 are shown. It can be understood that in the network architecture, the network exposure function device 1 and the network exposure function device 2 can be collectively referred to as a network exposure function (ie, Network Exposure Function, NEF).

[0078] The first functional network element cluster B may specifically include one or more functional network elements (for example, application functional network elements), and the number of application functional network elements in the first functional network element cluster B is not limited. For example, the multiple application functional network elements may specifically include Figure 1 The application function network element 100a, the application function network element 100b and the application function network element 100c are shown. It can be understood that in the network architecture, the application function network element 100a, the application function network element 100b and the application function network element 100c can be collectively referred to as an application function (ie, Application Function, AF).

[0079] The second functional network element cluster C here may specifically include one or more functional network elements (for example, network functional network elements) in the 5G core network, and the number of network functional network elements in the second functional network element cluster is not limited here. For example, the multiple network functional network elements here may specifically include Figure 1The network function network element 200a, network function network element 200b, ..., network function network element 200n are shown. It can be understood that in the network architecture, the network function network element 200a, network function network element 200b, ..., network function network element 200n can be collectively referred to as a network function (i.e., Network Function, NF). It can be understood that the NF here can include but is not limited to PCF, AMF (Access and Mobility Management Function, access and mobility management function), SMF (Session Management Function, session management function), etc. In a broad sense, UPF (i.e., User plane Function, user plane function) can also be a network function.

[0080] It can be understood that in the 5G communication system, NEF: Network Exposure Function, network open function, is located between the 5G core network and the external third-party application function body (there may also be some internal AF, that is, AF deployed and trusted by the operator). The NEF here can be used to manage network data open to the outside world. Figure 1 As shown in the figure, all external applications that want to access the internal data of the 5G core network must go through NEF. NEF can provide corresponding security guarantees to ensure the security and topological isolation of external applications to the 3GPP network, and can also provide external application QoS customization capability exposure, mobility status event subscription, location information, and AF-affected routing and other functions.

[0081] AF: Application Function, refers to various services at the application layer, which can be an application within the operator, such as VoLTE AF (similar to VoLTE AS in 4G), or an AF of a third party (i.e., a third-party service provider) (such as an AF deployed on edge servers such as video servers, game servers, and vehicle servers). If the AF here is an AF deployed and trusted by the operator (for example, Figure 1 The application function network element 100a shown in the figure can be in the same trusted domain with other NFs, so that it can directly interact with other NFs without going through NEF. For example, the application function network element 100a can interact with the policy control function (i.e., Policy Control Function PCF) to directly call the service provided by the PCF for policy control.

[0082] However, if the AF here is the AF of a third party (i.e., a third-party service provider), then Figure 1In the trusted domain shown, at this time, the AFs of these third parties (for example, Figure 1 The application function network element 100b and the application function network element 100c shown in the figure must access other NFs through NEF, which means that at this time, the external application function network elements 100b cannot directly interact with each other. Figure 1 The network architecture provides a method for obtaining data information, which can solve the problem that these AFs (for example, application function network 100b, application function network 100b, application function network element 100c and other network elements) cannot directly interact with each other.

[0083] For further understanding, please refer to Figure 2 , Figure 2 Schematic diagram of the network architecture based on the 5G communication system provided in the embodiment of the present application. It can be understood that the network architecture diagram is in the above Figure 1 A 3GPP system (i.e., a 5G communication system) may at least include a 5G access network, a 5G core network, and user terminals. Figure 2 The user terminal (UE) shown in FIG. Figure 2 The base station shown (e.g., a 5G base station) is connected to a 5G core network.

[0084] For example, before the UE performs service communication, it can obtain the IP address configured by the 5G core network. For example, it can obtain the IP address configured for the UE by the SMF (session management function) in the 5G core network, that is, Figure 2 The SMF (i.e., session management function) shown in FIG. 1 may carry the IP address assigned to the UE in the PDU session establishment accept (NAS) message sent to the UE, which means that the message may be sent by Figure 2 The AMF (Access and Mobility Management Function) shown in the figure is transparently transmitted to Figure 2 The base station shown in FIG. Figure 2 The base station shown transparently transmits the data to the UE. Figure 2 In the 3GPP network shown, the UE can access multiple data networks in parallel through one PDU session, for example, Figure 2 Shown are network 300a, network 300b and network 300c.

[0085] Among them, UPF: User plane Function, user plane function, can include an intermediate user plane function (for example, I-UPF) for performing service offloading function, an anchor user plane function 1 (for example, PSA-UPF1) for interacting with the data network of the central server, and an anchor user plane function 2 (for example, PSA-UPF2) for interacting with the multi-access edge computing (i.e., Multi-access Edge Computing, MEC) network of the edge server. Among them, UPF: User plane Function, user plane function, can specifically include routing and forwarding of user data packets, data interaction with the external data network DN, QoS processing of the user plane, implementation of flow control rules (such as gating, redirection, and traffic steering), etc.

[0086] Among them, DN: Data Network (DN), such as operator services, Internet or third-party services.

[0087] Among them, MEC network can include but is not limited to Figure 2 The network 300a and the network 300b are shown. In this embodiment of the application, the edge server 1 in the network 300a can be collectively referred to as the first device. Figure 2 The application function 1 (i.e., AF1) shown may be an application function entity in the first device, and AF1 may be deployed on the first device (e.g., edge server 1 located in the MEC platform 1). Similarly, in order to distinguish it from edge server 1, the embodiment of the present application may collectively refer to edge server 2 in network 300b as a second device. Figure 2 The application function 2 (i.e., AF2) shown in the figure may be an application function entity in the second device, and AF2 may be deployed on the second device (e.g., an edge server 2 located in the MEC platform 2). Figure 2 The application function 3 (i.e., AF3) shown may be located in the data network of the central server (i.e., another second device). It is understandable that both the MEC platform 1 and the MEC platform 2 here may include at least one edge server, and the number of edge servers included therein will not be limited here.

[0088] Among them, Figure 2 In the 3GPP network architecture shown, AF1 is located in MEC platform 1 and can obtain low-latency network capability exposure information. It is understandable that Figure 2The I-UPF (i.e., intermediate user plane function) shown can allow PSA-UPF2 (i.e., anchor user plane function 2) to send user plane data from the N6 interface to the edge server 1 located in the MEC platform 1 through a routing protocol or a tunnel after performing service diversion. At this time, if the AF1 in the MEC platform 1 is an entity of other edge servers located in the network 300a, the AF1 can interact with the edge server (e.g., edge server 1) deployed in the MEC platform 1 to send the capability exposure information of the network exposure to the edge server 1. Optionally, the AF1 here can also be integrated and deployed on the edge server 1, so that the edge server 1 can have the capability exposure information of the AF1, and the specific deployment method of the AF1 will not be limited here.

[0089] Among them, traffic steering in the MEC platform refers to the ability of the MEC system to route traffic to target applications in the distributed cloud. For example, in 5G integrated deployment, UPF plays a central role in directing traffic to the required applications and network functions. In addition to UPF, 3GPP also specifies some related processes to support flexible and efficient routing of traffic to applications. One of the processes is the influence of application functions (for example, AF1) on traffic routing. It allows AF1 to influence the selection and reselection of local UPF and request service configuration rules to allow traffic to be diverted and turned to the data network where it is located (for example, Figure 2 Network 200a shown).

[0090] For example, in a cloud data analysis scenario (i.e., a business scenario that requires big data analysis), AF1 can collect a large amount of data from the UE (e.g., mobile phone video information, sensor information (e.g., AR sensor information or VR sensor information), etc.), and through processing and analysis, extract meaningful data information before sending it to the central server, thereby aggregating some new services for operators or third-party suppliers. Here, AF1 may be running in a single location (i.e., on a single host (e.g., Figure 2 The edge server 1 shown in the figure) may be distributed in a given area (such as campus coverage) or even in the entire network. The specific deployment method and location will not be limited here. It is understandable that when AF1 extracts meaningful data information from a large amount of data to provide service events, it can allow Figure 2 As shown, application function 3 (ie, AF3) or application function 2 (ie, AF2) directly obtains the capability exposure information of AF1.

[0091] It can be understood that AF3 located in network 300c or AF2 located in network 300b can obtain the capability exposure information of AF1 located in network 300a through any one of the following schemes (for example, Scheme 1, Scheme 2 or Scheme 3). The embodiment of the present application will not limit the scheme for directly obtaining the capability exposure information of AF1 (i.e., the first functional network element).

[0092] For ease of understanding, the second functional network element AF2 is taken as an example to illustrate the specific process of AF2 directly obtaining the capability exposure information of AF1 from the network 300a through the above solution.

[0093] The data interaction rule corresponding to solution 1 may be the first data interaction rule. For example, Figure 2 The network open function shown (i.e., the above-mentioned NEF) can authenticate the capability call request sent by the functional network element (e.g., AF2) located on the MEC platform 2 according to a specific configuration policy (e.g., the contract signing rules between AF2 and NEF), and then return the capability call response information to AF2 when the authentication is successful, so that AF2 can directly send the capability call signing request to the AF providing the capability (e.g., the above-mentioned AF1) based on the received capability call response information. In this way, when AF1 determines that it has received the capability call signing request, it can directly return the capability call signing response information for the capability call signing request to AF2. In this way, when AF1 detects that an event corresponding to the event type contracted with AF2 has occurred, it can quickly send the event response information of the event directly to AF2.

[0094] It should be understood that the capability call response information here may carry the following authentication response parameter information. For example, when the NEF confirms receipt of the capability call request, the authentication response parameter information here may include indication information of receiving the capability call request. Furthermore, the authentication response parameter information may also include identification information of the AF determined by the NEF that can provide services to the AF2 (for example, the identification information of the above-mentioned AF1), and / or the IP (Internet Protocol) address information of AF1, and / or the endpoint address (Endpoint Address) of AF1, etc. Optionally, the authentication response parameter information may also include the access token information or access key information configured by the NEF for the AF2 to access the AF1. The specific content of the authentication response parameter information returned by the NEF and received by AF2 will not be limited here.

[0095] Among them, the data interaction rule corresponding to scheme 2 can be a second data interaction rule, and the second data interaction rule specifically means that the present application can also transfer the capability call request of AF2 to AF1 through the NEF. For example, the functional network element (for example, AF1) located on the MEC platform 1 can also receive the corresponding request sent by AF2 through the NEF (for example, a capability call request for requesting to call the capability exposure information of AF1), so that the AF1 can authenticate the capability call request transferred by the NEF to determine whether to receive the capability call request sent by the AF2 through the NEF. For example, when AF1 determines to receive the capability call request, the contract processing of the target event type requested by AF2 can be completed in AF1, and then when the target event type is successfully signed, the request response parameter information that needs to be returned to AF2 can be further transferred through the NEF. In this way, when AF1 detects the occurrence of an event corresponding to the contract event type (that is, the target event type signed by itself), the event response information of the event can be quickly sent directly to AF2.

[0096] It is understood that the contract event type here can be a target event type associated with AF1 determined in the request event type (e.g., one or more event types) sent by AF2, which means that the target event type is the same as the event type supported by AF1. It is understood that in the embodiment of the present application, one or more event types sent by AF2 can be collectively referred to as request event types. The number of request event types involved is not limited here.

[0097] Among them, it can be understood that the request response parameter information here can specifically include prompt information for indicating AF1 to receive the capability call request, the above-mentioned signing event type (that is, the signing event type can be a target event type with a signed status), and the first functional network element (for example, AF1) identification information, and / or the IP (Internet Protocol) address information of the first functional network element, and / or the endpoint address (EndpointAddress) information of the first functional network element.

[0098] Among them, the data interaction rule corresponding to scheme three can be a third data interaction rule, and the third data interaction rule specifically means that NEF can actively decide which of the above-mentioned capability call authentication methods to adopt (i.e., actively decide whether to adopt scheme one or scheme two) according to actual business needs (for example, according to the policy information of the network operator or the network topology information, etc.). For example, the functional network element closest to the functional network element (for example, AF2) that initiates the capability call request can be found according to the policy information or network topology information of the network operator. If the functional network element closest to AF2 (for example, AF1) can support the event type requested by AF2, then NEF can adopt the second data interaction rule corresponding to scheme two to directly forward the capability call request to AF1 so that AF1 can authenticate the capability call request. Optionally, if the policy information of the network operator requires NEF to authenticate the capability call request, then NEF can adopt the first data interaction rule corresponding to scheme one to directly authenticate the capability call request in the NEF based on the above-mentioned specific configuration policy, so that the NEF can determine which NF or which AF provides the capability call request service for AF2.

[0099] Among them, it can be understood that, as mentioned above Figure 2 As shown, in the embodiment of the present application, AF (for example, the second application function 2) can communicate with PCF (ie Figure 2 The policy control function shown in the figure) is contacted to request a time window (for example, to request valid time period information) and related conditions (for example, delay requirements, maximum number of calls information, and time interval information for event response, etc.) for future background data transmission.

[0100] It is understandable that the edge servers deployed on the MEC platform 1 can be effectively used for applications that require a lot of computing, such as applications that require a lot of graphics rendering (high-speed browsers, augmented reality (AR), virtual reality (VR), and 3D games, etc.), applications that require a lot of data preprocessing (sensor data cleaning, video analysis, etc.), and applications that need to provide value-added services (language translation, log analysis, etc.). AF1 deployed on the MEC platform can provide these edge servers with information on network capability exposure. Among them, it is understandable that edge computing, as an evolution of cloud computing, migrates applications from centralized data centers to edge networks, which can be closer to consumers and data sources.

[0101] For further information, see Figure 3 , Figure 3The method can be executed by a computer device, where the computer device can be a first device, for example, the first device can be the above-mentioned Figure 2 In the edge computing device 1 in the corresponding embodiment, it can be understood that a first functional network element is running in the first device, and the first functional network element can be the above-mentioned Figure 2 The corresponding application function 1 in the embodiment, that is, the application function 1 may be AF1. The method for obtaining data information may at least include the following steps S101 to S103:

[0102] Step S101, obtaining a capability invocation subscription request sent by a second functional network element based on subscription request parameter information;

[0103] The contract signing request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device authenticates the capability call request; and the capability call request is sent by the second functional network element.

[0104] It can be understood that the first functional network element here may be a first application functional entity, and the first application functional entity may be an application function deployed on the first platform (for example, the above Figure 2 Similarly, the second functional network element is a second application function entity, which may be an application function deployed on a second platform (for example, the above-mentioned Figure 2 The application function 2) in the corresponding embodiment.

[0105] Among them, it can be understood that the first platform here may be different from the second platform, that is, through the embodiments of the present application, data interaction between network elements can be realized on two cross-platforms; optionally, the first platform here can also be the same platform as the second platform, that is, through the embodiments of the present application, data interaction between network elements can be realized on the same platform.

[0106] For ease of understanding, please refer to Figure 4 , Figure 4 is a schematic diagram of a scenario for data interaction provided by an embodiment of the present application. Figure 4 The network open function device shown can be the above Figure 2 The NEF in the corresponding embodiment. Figure 4 The first functional network element shown may be the above Figure 2 AF1 in the corresponding embodiment. Figure 4 The second functional network element shown can be the above Figure 2 The corresponding embodiment of AF2. Based on the above Figure 2For the 5G communication system in the corresponding embodiment, both AF1 and AF2 can communicate with PCF (i.e., the above-mentioned Figure 2 The policy control function shown in the figure) is contacted to request the corresponding time window and related conditions for future background data transmission.

[0107] like Figure 4 As shown, it can be understood that when AF2 (i.e., the second functional network element) needs to call a certain capability (e.g., a certain service) from AF1 (i.e., the first functional network element), AF2 (i.e., the second functional network element) can pre-execute Figure 4 Step S11 shown in FIG. Figure 4 The capability call request 1 shown is sent to Figure 4 The NEF (i.e., network open function device) shown. It can be understood that there is a contract rule between AF2 and the NEF that meets the 5G communication requirements and the network operator requirements. Similarly, there is another contract rule between AF1 and the NEF that meets the 5G communication requirements and the network operator requirements. For ease of understanding, the embodiment of the present application may collectively refer to the contract rule between NEF and AF2 as the first contract rule, and may collectively refer to another contract rule between NEF and AF1 as the second contract rule. Based on this, the above-mentioned authentication response parameter information may be obtained by the network open function device after authenticating the capability call request based on the first contract rule; the capability call request may be sent by the second functional network element based on the first contract rule.

[0108] It is understandable that when NEF (ie, network open function device) receives a capability call request (ie, Figure 4 When the capability call request 1 is made, the NEF (ie, the network open function device) can execute Figure 2 Step S12 shown is to authenticate the capability call request 1 according to the corresponding contract rules (i.e., the aforementioned first contract rules). Among them, it can be understood that the capability call request 1 can carry the request parameter data information that the AF2 needs to request. For example, the request parameter data information here can specifically include information such as the identification information of AF2, the authentication information of AF2, and one or more event types that AF2 needs to request. It can be understood that the embodiment of the present application can collectively refer to the one or more event types requested by the AF2 as the above-mentioned request event types. It can be understood that these request event types can include target event types associated with AF1, and the AF1 here can be a functional network element that can provide services to the AF2. In an embodiment of the present application, when the NEF receives the above-mentioned capability call request 1, the NEF can directly use the above-mentioned first data interaction rule to execute the above-mentioned scheme one. Specifically, if Figure 4 As shown, at this point, NEF can execute Figure 4 Step S12 shown is to directly authenticate the received capability call request according to a specific configuration strategy (for example, configuration strategy 1, which can specifically be a first signing rule in accordance with the above-mentioned 5G communication requirements and network operator requirements).

[0109] Among them, optionally, the request parameter data information may further include: a delay indicator for responding to events (i.e., delay requirement), an effective time for capability calling (i.e., effective time period information), a call number threshold for capability calling (i.e., maximum call number information), and an interval duration for responding to events (i.e., time interval information for event response), etc. The specific parameters of the request parameter data information will not be limited here.

[0110] It can be understood that the latency indicator here can be, but is not limited to, used to indicate that the network open function device determines the identifier of the first application function entity (e.g., AF1) that can meet the request of the second application function entity (e.g., AF2). For example, optionally, the latency indicator can also be used to indicate that AF1 provides a low-latency capability call service for AF2. The specific role of the latency indicator will not be limited here.

[0111] Among them, Figure 4 As shown, the specific process when NEF authenticates the capability call request 1 may at least include an authentication process and an authorization process. The authentication process means that when NEF obtains the call request 1 sent by AF2, it can obtain the authentication information of AF2 (for example, the certificate information of AF2) from the call request 1, and then authenticate the legitimacy of the obtained authentication information. The authorization process specifically means that when the NEF succeeds in authentication, it can further authorize the capability call request 1 sent by AF2, for example, it can be determined that the capability call request 1 is a legal request.

[0112] Among them, Figure 4 As shown, it can be understood that when NEF obtains the authentication information sent by AF2 (for example, the certificate information of AF2), it can query the contract verification information (for example, the contract certificate information) used to verify the certificate information according to the obtained identification information of AF2, and then can authenticate the authentication information (for example, the certificate information of AF2) sent by AF2 according to the contract verification information (for example, the contract certificate information) of AF2 found to obtain the authentication result. If the authentication result indicates that the contract verification information is consistent with the authentication information, it can be determined that the authentication information (for example, the certificate information of AF2) sent by AF2 is legal authentication information, that is, the above authentication process has been successfully completed.

[0113] Further, it can be understood that when the authentication is successful, the NEF can determine that the AF2 used to send the request parameter data information is legitimate, and further determine that the capability call request 1 sent by AF2 is a legitimate request. This means that the NEF can determine that the request parameter data information sent by the legitimate AF2 is also legitimate parameter information according to the above-mentioned first contract rule. The present invention does not limit the authentication process of the NEF.

[0114] It is understood that when the NEF performs authentication processing (e.g., authentication and authorization) on the capability call request according to the first contract rule, the NEF can also determine the AF or NF that can provide services to the AF2. For example, the NEF can check which AFs or NFs can provide services to the AF2 (i.e. Figure 4 The second functional network element shown in FIG. 1 provides a capability call request service. Specifically, NEF can view AF1 (i.e. Figure 4 The NEF determines whether the first functional network element shown in the figure can provide the service of the event type indicated by the capability call request 1 to the AF2. In other words, when the authentication is successful, the NEF can further determine which AF or which NF in the subscription list can provide the service of the requested event type to the AF2. Optionally, the NEF here can also be used to determine the identification information of the AF (for example, the above-mentioned AF1) that provides the capability to the AF2 based on the delay indicator (for example, the delay requirement) parsed from the request parameter data information or the policy information or network topology information of the network operator.

[0115] Among them, for ease of understanding, the embodiment of the present application takes the first data interaction rule used as the above-mentioned direct interaction method as an example. After obtaining the above-mentioned capability call request 1, NEF also needs to judge other parameters (for example, the above-mentioned one or more event types) in the request parameter data information to determine whether the event type of AF1 conforms to the event type requested by AF2. If the two are consistent, the event types in the one or more event types requested by AF2 that are the same as the event type of AF1 can be collectively referred to as target event types. For ease of understanding, here, the event type requested by AF2 is taken as an example, so that the capability call request can be authenticated in NEF based on AF2's identification information (i.e., the first identification information), AF2's authentication information and the target event type, to determine whether the target event type requested by AF2 is the same as the event type indicated by AF1, and then the capability call response information for the capability call request 1 can be further generated (for example, Figure 4 At this time, the NEF (ie, the network open function device) may execute step S13 to return the capability call response information 1 to the Figure 4The second functional network element (e.g., AF2) shown in FIG. Figure 4 The second functional network element shown can perform Figure 4 It can be understood that, in step S14 here, that is, at this time, the second functional network element (for example, AF2) can send a capability invocation subscription request (ie, Figure 4 The capability shown invokes a contract request 2).

[0116] The capability call response information 1 received by the second functional network element (e.g., AF2) may carry authentication response parameter information, where the authentication response parameter information may at least include authentication success indication information; the authentication success indication information is obtained when the network open function device confirms the reception of the capability call request after successful authentication processing. It can be understood that the embodiment of the present application may also collectively refer to the authentication success indication information as a method for indicating NEF (i.e., Figure 4 The network open function device shown in FIG. 1 receives a prompt message of a capability call request (for example, the capability call request 1 described above). It can be understood that if the NEF accepts the capability call request 1, it can further send a prompt message to the AF2 (ie, Figure 4 The second functional network element shown in the figure returns the identification information (i.e., the second identification information) of the first functional network element (e.g., AF1), and / or the IP (Internet Protocol) address information of the first functional network element, and / or the endpoint address (EndpointAddress) information of the first functional network element and the access parameter information; wherein the access parameter information can be the access token information or target key information configured by the network open function device for the second functional network element (e.g., AF2) for accessing the first functional network element (e.g., AF1).

[0117] It can be seen that the authentication response parameter information of the capability call response information 1 returned by the NEF when the authentication is successful may at least include: prompt information for indicating the reception of the capability call request, the second identification information of the first functional network element, the IP (Internet Protocol) address information of the first functional network element, the endpoint address (Endpoint Address) information of the first functional network element and the access parameter information; wherein the access parameter information is the access token information or target key information configured by the network open function device for the second functional network element for accessing the first functional network element.

[0118] Optionally, when the NEF fails in authentication, the capability call response parameter information 1 here may also carry another prompt information for indicating the rejection of the capability call request (for example, the capability call request 1 mentioned above). For example, if the NEF refuses to accept the capability call request, it may further return the reason value for refusing to accept the capability call request. For example, if the NEF determines that the AF2 cannot request a certain event type, it may return the rejection reason value (for example, 1) for rejecting the capability call request 1 mentioned above. The rejection reason values ​​for rejecting the capability call request 1 will not be listed one by one here.

[0119] Step S102, obtaining access parameter information for requesting access to the first function network element from the contract request parameter information carried by the capability call contract request, and performing contract verification on the capability call contract request based on the access parameter information;

[0120] Specifically, it can be understood that the first functional network element receives the capability call signing request (i.e., the above-mentioned Figure 4 When the capability call contract request 2 is shown, the capability call request (i.e., the above Figure 4 The capability call contract request 2 shown in the figure obtains the contract request parameter information carried. The contract request parameter information here may include: the identification information of the second functional network element (that is, the above-mentioned first identification information), the target event type determined by the above-mentioned NEF to be associated with the first functional network element, the access parameter information configured by the above-mentioned NEF, the delay indicator for responding to the event, the effective time for capability call, the call number threshold for capability call, and the interval time for responding to the event. It can be understood that when the first functional network element obtains the contract request parameter information, it can further extract the above-mentioned access parameter information (for example, the above-mentioned access token information or target key information for requesting access to the first functional network element) from the contract request parameter information. At this time, the first functional network element can perform contract verification on the capability call contract request based on the access parameter information, and then execute the following step S103 when the contract verification is successful.

[0121] For example, as mentioned above Figure 4 As shown, the first functional network element (for example, AF1) can extract access token information or target key information from the capability call contract request 2 when obtaining the capability call contract request 2, and then perform contract verification on the access token information or the target key information. If the verification passes (that is, the contract verification succeeds), the capability call contract request 2 can be received to execute the above Figure 4In step S14 shown, the first functional network element may return capability call contract response information 2 for the capability call contract request 2 to the second functional network element to notify the second functional network element that the first functional network element has currently completed the contract for the target event type. It can be understood that the capability call contract response information 2 here can be the capability call contract response information in the following step S103.

[0122] Among them, it can be understood that when the contract verification is successful, the capability call contract response information 2 may include indication information for indicating the reception of the capability call contract request 2. Optionally, when the contract verification fails, the capability call contract response information 2 may also include another indication information for indicating the refusal to receive the capability call contract request 2, that is, the other indication information for indicating the refusal to receive the capability call contract request 2 may carry a corresponding rejection reason value. For example, the rejection reason value here, for example, the rejection reason value 2 can be used to represent that AF1 has counted that the event corresponding to the event type called by AF2 within the effective time has reached the maximum number of call times (that is, reaching the above-mentioned authorized call number threshold for capability call).

[0123] Step S103, generating capability call contract response information for the capability call contract request when the contract verification succeeds, and returning the capability call contract response information to the second function network element;

[0124] Among them, the capability call contract response information can be used to instruct the second functional network element to access the first functional network element. In addition, it can be understood that the first functional network element (for example, the above-mentioned AF1) can determine the target event type of the contract request sent by AF2 as the contract event type that has been signed when the contract verification is successful, and then store the contract event type in AF1. In this way, when AF1 detects that the event corresponding to the contract event type (i.e., the contracted event) occurs, the event response information of the contracted event can be directly returned to the second functional network element, thereby helping the second functional network element to improve the efficiency of obtaining information.

[0125] It can be seen from this that it can be understood that after the second functional network element successfully signs a contract for the target event of the first functional network element, the first functional network element can further return event response information for the signed event to the second functional network element when detecting that the event corresponding to the currently signed target event type (i.e., the above-mentioned signed event type) occurs. For example, AF1 (i.e., the first functional network element) can return the event response information to AF2 (i.e., the second functional network element) within the above-mentioned interval duration for responding to the signed event.

[0126] In an embodiment of the present application, a first functional network element located on a first platform can receive a capability call contract request sent by a second functional network element located on a second platform. The capability call contract request is sent by the second functional network element based on the contract request parameter information; it can be understood that the contract request parameter information here is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information here is obtained by the network open function device after the capability call request is authenticated based on the first contract rule; it can be understood that the capability call request here is sent by the second functional network element based on the first contract rule between the second functional network element and the network open function device in advance. It can be seen that before the second functional network element sends the capability call contract request to the first functional network element, the second functional network element can send the capability call request to the network open function device in advance, so that the network open function device can directly authenticate the received capability call request, and then return the authentication response parameter information to the second functional network element when the authentication is successful. Furthermore, the first functional network element can obtain access parameter information used to request access to the first functional network element from the contract request parameter information carried by the capability call contract request, and then can perform contract verification on the capability call contract request based on the access parameter information (for example: the above-mentioned access token information, etc.); further, the first functional network element can generate capability call contract response information for the capability call contract request when the contract verification is successful, and can return the capability call contract response information to the second functional network element; it can be understood that the capability call contract response information here can be used to instruct the second functional network element to access the first functional network element. At this time, the first functional network element and the second functional network element can directly interact with each other, thereby improving the efficiency of information acquisition between the network elements of the two platforms.

[0127] For further information, see Figure 5 , Figure 5 The method can be executed by a computer device, where the computer device can be a first device, and the first device is the above-mentioned Figure 2 In the edge computing device 1 in the corresponding embodiment, it can be understood that a first functional network element is running in the first device, and the first functional network element can be the above-mentioned Figure 2 The application function 1 in the corresponding embodiment, that is, the application function 1 may be AF1. It can be understood that the first functional network element may be used to execute the above Figure 3 In the method in the corresponding embodiment, optionally, the first functional network element may further perform the following steps S201 to S203:

[0128] Step S201, receiving a capability invocation request forwarded by a network open function device associated with a first functional network element;

[0129] Among them, the capability call request is sent by the second functional network element associated with the network open function device, and the capability call request can carry request parameter data information, for example, the request parameter data information can at least include the authentication information of the second functional network element; it can be understood that in an embodiment of the present application, there can be a first signing rule between the network open function device and the second functional network element that meets the above-mentioned operator requirements, and similarly, there can be a second signing rule between the first functional network element and the network open function device that meets the above-mentioned operator requirements.

[0130] Among them, it can be understood that in the embodiment of the present application, when the network open function device (for example, NEF) receives the capability call request sent from the second functional network element, it can directly adopt the above-mentioned second data interaction rule to execute the above-mentioned scheme 2. For example, NEF can directly forward the received capability call request to the first functional network element based on another configuration policy (for example, configuration policy 2). For example, specifically, NEF can receive the capability call request according to the first contract rule between it and the second functional network element, and further determine the first functional network element that serves the request, and then directly forward the received capability call request to the first functional network element.

[0131] Optionally, it is understandable that in some feasible implementations, NEF may also determine, based on the operator's policy information or network topology information, that NEF may directly forward the capability call request sent by AF2 to AF1, so that AF1 can authenticate the acquired capability call request.

[0132] Optionally, NEF can also authenticate the capability call request sent by AF2 directly in the NEF according to the operator's requirements. For example, it can be understood that in some achievable implementations, NEF can execute the above solution 1 according to specific information (for example, the above configuration policy 1), that is, NEF can authenticate the received capability call request according to the above first contract rule. The specific implementation method of NEF authenticating the capability call request can be found in the above Figure 4 The description of obtaining the capability call response information 1 in the corresponding embodiment will not be repeated here.

[0133] For ease of understanding, we take the above solution 2 as an example. For further information, please refer to Figure 6 , Figure 6 1 is a schematic diagram of a scenario in which data interaction between network elements is realized through a network open function device transfer provided by an embodiment of the present application. Figure 6 The first functional network element shown can be deployed on a first platform, and the first platform can be the above-mentioned MEC platform 1; wherein, Figure 6 The second functional network element shown can be deployed on a second platform; the second platform can be the above-mentioned MEC platform 2. The first platform here can be different from the second platform, for example, one platform can be an operator platform, and the other platform can be a platform of a third-party service provider (referred to as a third-party platform). Optionally, the second functional network element and the first functional network element here can also be deployed on the same platform, for example, both are deployed on a third-party platform in a certain geographical location area.

[0134] It can be understood that the capability call request sent by the second functional network element (for example, Figure 6 The capability call request 3) shown in the figure may carry request parameter data information. The request parameter data information here may specifically include: the request parameter data information at least includes: the identification information of the second functional network element (for example, the second functional network element may be the second application function entity deployed in the above-mentioned second device), the target event type and the authentication information of the second functional network element. Optionally, in some feasible implementations, the request parameter data information may also include: a delay indicator for responding to events, an effective duration for performing capability calls, a call count threshold for performing capability calls, and an interval duration for responding to events.

[0135] It is understandable that if Figure 6 As shown, the second functional network element (for example, AF2) executes Figure 6 After step S21 shown, Figure 6 The network open function device (e.g., NEF) shown in the figure can receive the capability call request 3 and can determine a functional network element that can match the target event type requested in the capability call request 3. For example, the functional network element determined by the NEF that can provide services for the second functional network element can be Figure 6 The first functional network element shown, for example, the delay indicator here can be used to instruct the network open function device (ie, NEF) to determine the first application function entity that matches the capability call request sent by the second application function entity. It can be understood that when the network open function device (eg, NEF) receives the capability call request 3, it can further execute according to the above solution 2. Figure 6 Step S22 shown in FIG. 3 may directly forward the capability call request 3 to Figure 6 The first functional network element shown.

[0136] Further, such as Figure 6 As shown, after the first functional network element (for example, AF1) receives the capability call request 3 forwarded by the network open function device (for example, NEF), the first functional network element may further execute Figure 6The step S23 shown here may be the following step S202 in the embodiment of the present application.

[0137] Step S202, obtaining request parameter data information from the capability call request, and performing authentication processing on the capability call request based on the request parameter data information;

[0138] Specifically, after executing the above step S201, the first functional network element can further obtain authentication information from the received capability call request, for example, the authentication information here can be the certificate information of the above AF2. In this way, the first functional network element can search and obtain the contract verification information of the second functional network element (for example, the contract certificate information of AF2) according to the identification information of the second functional network element. The acquisition source of the contract verification information (for example, the contract certificate information of AF2) will not be limited here. It can be understood that when the first functional network element finds the contract verification information (for example, the contract certificate information of AF2) that matches the identification information of the second functional network element, the authentication information (that is, the certificate information of AF2) can be authenticated according to the contract verification information (for example, the contract certificate information of AF2). If the authentication is successful, the capability call request 3 can be authorized. Specifically, the first functional network element (for example, AF1) can perform contract processing on other parameter information in the request parameter data information (for example, the request event type sent by AF2, such as the above target event type), for example, AF1 can obtain the authentication success result when the contract for the target event type is successfully completed. For example, the target event type for requesting a contract can be used as the contract event type in AF1, and the contract event type can be stored and processed in AF1 so that the following step S203 can be performed later.

[0139] The request parameter data information may carry identification information of the second functional network element for which the subscription is requested, and authentication information of the second functional network element (for example, the certificate information of AF2 mentioned above).

[0140] It can be understood that the first functional network element here can be a first application functional entity, that is, the first application functional entity can be an application function deployed on the first platform (for example, the above Figure 2 Similarly, the second functional network element is a second application function entity, that is, the second application function entity can be an application function deployed on the second platform (for example, the above Figure 2 The application function 2) in the corresponding embodiment.

[0141] It can be understood that the first platform here may be different from the second platform, that is, through the embodiments of the present application, data interaction between network elements can be realized on two cross-platforms; Figure 6 As shown, when AF2 (i.e., the second functional network element) needs to call a certain capability (e.g., a certain service) from AF1 (i.e., the first functional network element), AF2 (i.e., the second functional network element) can pre-execute Figure 6 Step S21 shown in FIG. Figure 6 The capability call request 3 shown is sent to Figure 6 The NEF (i.e., network open function device) shown in FIG. 1 is a network open function device. It is understandable that there is a contract rule between AF2 and the NEF that meets the 5G communication requirements and the network operator's requirements. Similarly, there is another contract rule between AF1 and the NEF that meets the 5G communication requirements and the network operator's requirements. For ease of understanding, the embodiment of the present application may collectively refer to the contract rule between NEF and AF2 as the first contract rule, and may collectively refer to another contract rule between NEF and AF1 as the second contract rule.

[0142] It is understandable that when AF1 (i.e., the first functional network element) receives a capability call request (i.e., Figure 6 When the capability call request 3) is shown, the AF1 can execute Figure 6 Step S23 shown is to perform the above-mentioned authentication processing on the capability call request 3. It can be understood that the capability call request 3 can carry the request parameter data information required by the AF2. For example, the request parameter data information here can specifically include the identification information of AF2 (i.e., the first identification information mentioned above), one or more event types required by AF2, the delay index for responding to the event (i.e., the delay requirement), the effective time for capability call (i.e., the effective time period information), the call number threshold for capability call (i.e., the maximum call number information), and the interval time for responding to the event (i.e., the time interval information of the event response), etc.

[0143] The specific process of AF1 performing authentication processing on the capability call request 3 may at least include an authentication process and an authorization process. The authentication process means that AF1 can obtain the authentication information in the aforementioned request parameter data information from the capability call request 3 when obtaining the capability call request 3 sent by the AF2 transferred by the NEF. It can be understood that the authentication information here can be the certificate information of the second functional network element (for example, AF2). At this time, the AF1 (i.e., the first functional network element) can further authenticate the authentication information according to the obtained contract verification information of the AF1 (for example, the contract certificate information of AF2), and then authorize the capability call request 3 when the authentication is successful. For example, AF1 can determine whether the call number threshold for the capability call is reasonable. If it is reasonable, AF1 can determine that the request parameter data information sent by the legitimate AF2 belongs to the legitimate parameter information, and then the contract process in the following step S203 can be further performed in AF1 to contract the target event type requested to be contracted in the request parameter data information. At this time, AF1 can check in the acquired contract list whether it can provide the service of the event type indicated by the capability call request 3 to the AF2. For example, AF2 can check within the effective period whether it can provide the service of the target event type indicated by the capability call request 3 to the AF2. If so, the contracted target event type can be used as the contracted event type, and the target event type contracted by AF2 can be saved (that is, the aforementioned contracted event type can be saved), and detection can be started to determine whether the event corresponding to the target event type occurs. In other words, AF1 can receive the capability call request 3 and generate request response parameter information for the capability call request 3 when the authentication is successful and it is determined that it can provide the service of the target event type requested to be contracted to the AF2, and then can execute Figure 6 Steps S24-S25 are shown.

[0144] Step S203, when the authentication is successful, receiving the capability call request, generating request response parameter information for the capability call request, and forwarding the request response parameter information to the second functional network element through the network open function device;

[0145] Specifically, the first functional network element can determine that the currently received capability call request is a legal request when authentication is successful, and then generate a signing instruction for the legal request when receiving the legal request; further, the first functional network element can determine the target event type as a signing event type based on the signing instruction, and generate request response parameter information for the signing event type, and then send the request response parameter information to the network open function device, so that the network open function device forwards the request response parameter information to the second functional network element.

[0146] Optionally, the first functional network element can also determine the target signing rule between the first functional network element and the second functional network element based on the signing instruction, and then determine the target event type as the signing event type based on the target signing rule, and generate request response parameter information for the signing event type; further, the first functional network element can send the request response parameter information to the network open function device based on the second signing rule, so that the network open function device forwards the request response parameter information to the second functional network element based on the first signing rule.

[0147] The request response parameter information may be used to instruct the second functional network element to access the first functional network element. Figure 6 The request response parameter information 4) shown may specifically include prompt information for indicating the reception of a capability call request (for example, the capability call request 3 mentioned above), the above-mentioned contract event type (i.e., the contracted target event type), and the identification information of the first functional network element (for example, AF1), and / or the IP (Internet Protocol) address information of the first functional network element, and / or the endpoint address (Endpoint Address) information of the first functional network element. For ease of understanding, the embodiment of the present application may collectively refer to the contracted target event types as the above-mentioned contract event types. It is understandable that at this time, AF1 may be connected to the NEF (i.e., Figure 6 The network open function device shown in FIG. 1 returns to the second function network element Figure 6 The request response parameter information 4 shown. It can be understood that the request response parameter information 4 can be used to instruct the second functional network element to access the first functional network element, which means that when the first functional network element detects that the event corresponding to the target event type currently signed by itself (i.e., the above-mentioned signed event) occurs, the event response information of the event (i.e., the above-mentioned signed event) can be directly returned to the second functional network element, thereby improving the efficiency of the second functional network element in obtaining information.

[0148] It can be seen that in the embodiment of the present application, the request response parameter information (for example, the above-mentioned Figure 6 The parameter content of the request response parameter information 4) shown in the figure will be different from the above Figure 3 The request response parameter information (for example, the above-mentioned Figure 4This is because in the embodiment of the present application, after the first functional network element (for example, the above-mentioned AF1) performs the authentication process, if the authentication is successful, it can receive the capability call request (for example, Figure 6 The capability call request 4 shown in the figure can then directly generate a signing instruction in the first functional network element, and the signing instruction can be used to help the first functional network element determine the target signing rule between the first functional network element and the second functional network element. It can be understood that the target signing rule here can be used to characterize that the first functional network element has currently completed the signing for the above-mentioned target event type, and then the generated request response parameter information for the target event type can be forwarded to the second functional network element through the network open function device. It can be understood that at this time, the request response parameter information can be used to indicate that the second functional network element can currently be directly connected to the first functional network element. In this way, when the event that the first functional network element is signed by the second functional network element occurs, the first functional network element can directly return the event as event response information to the second functional network element, thereby improving the efficiency of the second functional network element in obtaining information.

[0149] For further information, see Figure 7 , Figure 7 The method can be executed by a computer device, where the computer device can be a second device, and the second device can be the above-mentioned Figure 2 The edge computing device 2 or the above-mentioned Figure 2 The central server in the corresponding embodiment will not be limited here. For ease of understanding, the second device is taken as the above-mentioned edge computing device 2 as an example to illustrate the specific process of data interaction between the second functional network element running in the second device and the first functional network element running in other devices (i.e., the first device, such as the above-mentioned edge computing device 1). Among them, the second functional network element can be used to execute the following steps S301-S303:

[0150] Step S301, receiving authentication response parameter information returned by the network open function device, and determining contract request parameter information based on the authentication response parameter information;

[0151] The authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second function network element. Specifically, the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request based on the first contract rule; the capability call request is sent by the second function network element based on the first contract rule.

[0152] Among them, the authentication response parameter information may include at least one of the following: prompt information for indicating the reception of the capability call request, the second identification information of the first functional network element, the IP (Internet Protocol) address information of the first functional network element, the endpoint address (Endpoint Address) information of the first functional network element and the access parameter information; wherein the access parameter information is the access token information or target key information configured by the network open function device for the second functional network element for accessing the first functional network element.

[0153] Among them, the contract request parameter information may include at least: the first identification information of the second functional network element, the target event type, the access parameter information, the effective time for capability calling, the call number threshold for capability calling, and the interval time for responding to the event.

[0154] It can be understood that the first functional network element running in the first device can be the above Figure 2 The application function 1 in the corresponding embodiment, that is, the application function 1 may be AF1 deployed on the first platform; the second function network element running in the second device may be the above-mentioned Figure 2 The application function 2 in the corresponding embodiment, that is, the application function 2 may be AF2 deployed on the above-mentioned second platform.

[0155] It can be understood that in an embodiment of the present application, before executing the above-mentioned step S301, the second functional network element may also perform the following steps: the second functional network element may obtain the first identification information of the second functional network element, the authentication information of the second functional network element, and the target event type requested by the second functional network element; further, the second functional network element may determine the request parameter data information based on the first identification information, the authentication information and the target event type; further, the second functional network element may add the request parameter data information to the capability call request; wherein, the capability call request may be used to instruct the network open function device to authenticate the authentication information based on the contract verification information matching the first identification information, and when the authentication is successful and it is determined that the target event type is associated with the first functional network element, generate authentication response parameter information for the capability call request.

[0156] Among them, the specific implementation method of the second functional network element obtaining the authentication response parameter information can be referred to above Figure 3 The description of the specific process of performing authentication processing on the network open function device in the corresponding embodiment will not be repeated here.

[0157] Step S302, adding the contract request parameter information to the capability call contract request, and sending the capability call contract request to the first functional network element, so that the first functional network element performs contract verification on the capability call contract request according to the access parameter information in the contract request parameter information;

[0158] Step S303: receiving capability call contract response information returned by the first functional network element when the contract verification is successful, and accessing the first functional network element based on the capability call contract response information.

[0159] The specific implementation of step S301-step S302 can be found in the above Figure 3 The description of the second functional network element in the corresponding embodiment will not be repeated here.

[0160] In an embodiment of the present application, for the second functional network element, after receiving the authentication response parameter information returned by the network open function device after authentication, the above-mentioned contract request parameter information (for example, the identification information of AF2, the target event type determined by the above-mentioned NEF, and the above-mentioned access parameter information) can be determined according to the authentication response parameter information (for example, the prompt information for indicating the reception of the capability call request, the identification information of the above-mentioned AF1, and the above-mentioned access parameter information), and then the contract request parameter information can be added to the capability call contract request (for example, the above-mentioned Figure 4 The capability call contract request 2) in the corresponding embodiment enables the first functional network element to perform contract verification on the received capability call contract request. In this way, the second functional network element can receive capability call contract response information for accessing the first functional network element when the contract verification of the first functional network element succeeds, thereby improving the efficiency of information acquisition between different network elements.

[0161] For further information, see Figure 8 , Figure 8 The method can be executed by a computer device, where the computer device can be a second device, and the second device can be the above-mentioned Figure 2 The edge computing device 2 or the above-mentioned Figure 2 The central server in the corresponding embodiment. For ease of understanding, here we take the second device as the above-mentioned edge computing device 2 as an example to illustrate the specific process of data interaction between the second functional network element running in the second device and the first functional network element running in other devices (i.e., the first device, such as the above-mentioned edge computing device 1). Among them, the second functional network element can be used to execute the above Figure 7 The steps in the corresponding embodiment; Optionally, the second functional network element can also be used to perform the following steps S401-S402:

[0162] Step S401, sending a capability call request to a network open function device associated with a second function network element;

[0163] Among them, it can be understood that after the second functional network element executes step S401, the network open function device can directly execute the above-mentioned scheme 2, that is, the network open function device can forward the capability call request to the first functional network element based on the second contract rule, so that the first functional network element can authenticate the capability call request based on the request parameter data information carried in the capability call request; it can be understood that there can be a second contract rule between the first functional network element and the network open function device.

[0164] Step S402, receiving request response parameter information for the capability call request returned by the first functional network element through the network open function device when the authentication is successful;

[0165] The request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0166] The specific implementation of steps S401 to S402 can be found in the above Figure 6 The description of the second functional network element in the corresponding embodiment will be further repeated here.

[0167] Optional, for ease of understanding, further see Fig. 9 , Fig. 9 This is an interactive timing diagram of a data information acquisition method provided in an embodiment of the present application. Fig. 9 As shown, if the second functional network element needs to directly obtain capability exposure information from the first functional network element, the embodiment of the present application can adopt the third data interaction rule to implement solution 3. For example, the network exposure function device here can actively decide whether to forward the received capability call request to the first functional network element. For example, the network exposure function device can determine whether to execute the above solution 1 or solution 2 according to the conditions in solution 3.

[0168] For example, Fig. 9 The second functional network element shown can execute step S31 to send the capability call request to Fig. 9 The network open function device shown. Fig. 9 As shown, the network open function device can adopt the third data interaction rule (for example, the policy information of the network operator or the network topology information, etc.) to implement the third solution, that is, the network open function device can Fig. 9In step S32 shown in the figure, it is determined whether the capability call request satisfies the conditions in the data interaction rule (for example, the third data interaction rule mentioned above). If not, the above solution 1 can be executed; otherwise, if it is satisfied, the above solution 2 can be executed. For example, if the network open function device (i.e., the above NEF) determines, based on the policy information of the network operator, that the first function network element running in the first device can provide the service of the event type requested by the second function network element running in the second device, the above solution 2 can be executed by the network open function device (i.e., the above NEF) to further jump to execution. Fig. 9 Step S40 is shown.

[0169] Optionally, if the network open function device (ie, the NEF) determines that the NEF is to perform the authentication of the capability call request according to the policy information of the network operator, the above-mentioned solution 1 can be executed by the network open function device (ie, the NEF) so that the NEF can directly execute the authentication request. Fig. 9 Step S32 is shown so that a functional network element that can provide a capability call request for the second functional network element (eg, AF2) can be determined in the NEF, thereby helping AF2 to obtain capability exposure information from the determined functional network element.

[0170] For example, specifically, Fig. 9 As shown, if it is not satisfied, the network open function device (for example, NEF) can further perform step S33, that is, the capability call request can be authenticated in the network open function device, and then after the authentication process is completed, step S34 can be performed to return the capability call response information obtained for the capability call request to the second functional network element. It can be understood that the capability call response information may include Fig. 9 The authentication response parameter information shown. The specific implementation method of the network open function device for the authentication processing of the capability call request can be referred to the above Figure 4 The description of the specific process of obtaining the capability call response information 1 in the corresponding embodiment will not be repeated here.

[0171] like Fig. 9 As shown, further, the second functional network element may perform step S35 to determine the subscription request parameter information based on the authentication response parameter information. It is understandable that at this time, the second functional network element needs to add the subscription request parameter information to the capability call subscription request in advance to perform Fig. 9 In step S36, the capability call signing request can be directly sent to Fig. 9 The first functional network element shown.

[0172] Further, the first functional network element may execute upon receiving the capability call signing request Fig. 9In step S37, the access parameter information for requesting access to the first functional network element is obtained from the contract request parameter information carried by the capability call contract request, and then the contract verification of the capability call contract request can be performed based on the access parameter information. It can be understood that the first functional network element can execute when the contract verification is successful. Fig. 9 Steps S38-S39 shown in the figure return the capability call contract response information to Fig. 9 The second functional network element shown. At this time, the capability call contract information may carry indication information for indicating the reception of the capability call contract request. It is understandable that, optionally, the first functional network element may also return a rejection reason value for indicating the rejection of the capability call contract request to the second functional network element when the contract verification fails.

[0173] It can be understood that after the first functional network element executes step S39, the second functional network element can be allowed to access the first functional network element based on the capability call contract response information. In this way, when the first functional network element detects that the event corresponding to the target event type currently contracted with the second functional network element (i.e., the above-mentioned contracted event) occurs, it can further jump to execute Fig. 9 As shown in step S45, the efficiency of information acquisition can be improved between network elements through the above-mentioned solution 1.

[0174] Optional, specific, such as Fig. 9 As shown, after executing the above step S32, the network open function device can also jump to execute based on the above solution 2. Fig. 9 That is, at this time, when the network open function device determines that the capability call request sent by AF2 meets the above transfer condition, it can further forward the capability call request to the first functional network element so that the first functional network element can execute Fig. 9 For example, the first functional network element may authenticate the capability call request based on the authentication information of the request parameter data information carried in the capability call request; and then, when the authentication is successful, the following steps S42 and S43 may be further executed to pass the request response parameter information obtained when the authentication is successful to the first functional network element. Fig. 9 The network open function device shown returns to the second functional network element. In this way, when the first functional network element detects that the event corresponding to the target event type currently contracted with the second functional network element (i.e. the above-mentioned contracted event) occurs, it can further jump to execute Fig. 9 As shown in step S45, the efficiency of information acquisition can be improved between network elements through the above-mentioned solution 2.

[0175] For further information, see Fig.10 , Fig.10It is a structural diagram of a data information acquisition device provided in an embodiment. In one embodiment, the device 11 may be a computer program (including program code) running in a computer device. For example, the device 11 may be a first functional network element running in a computer device; optionally, the device 11 may also be deployed on the first functional network element, and the first functional network element may run in the computer device. Optionally, the computer device here may also be a device independent of the first functional network element, and the computer device may be deployed on the same MEC platform (for example, the above-mentioned MEC platform 1) as the first functional network element. For ease of understanding, the embodiment of the present application takes the device 11 as an example of the first functional network element running in the above-mentioned computer device. The first functional network element can be used to execute the above-mentioned Figure 3 For further information, please refer to Fig.10 , the device 11 may include: a contract request acquisition module 111, a contract verification module 112, and a contract response return module 113. Further, the device 11 may also include: an event response return module 114;

[0176] The contract request acquisition module 111 is used to acquire the capability call contract request sent by the second functional network element based on the contract request parameter information; the contract request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second functional network element;

[0177] The contract verification module 112 is used to obtain access parameter information for requesting access to the first function network element from the contract request parameter information carried by the capability call contract request, and perform contract verification on the capability call contract request based on the access parameter information;

[0178] The contract signing response returning module 113 is used to generate capability calling contract signing response information for the capability calling contract signing request when the contract signing verification is successful, and return the capability calling contract signing response information to the second functional network element; the capability calling contract signing response information is used to instruct the second functional network element to access the first functional network element.

[0179] Optionally, the authentication response parameter information at least includes authentication success indication information; the authentication success indication information is obtained by the network open function device when confirming the reception of the capability call request after successful authentication processing; the capability call request is generated by the second function network element based on the request parameter data information; the requested event type in the request parameter data information at least includes: the target event type associated with the first function network element in the authentication response parameter information; the target event type is the same as the event type of the signed event in the capability call signing response information;

[0180] The event response returning module 114 is used to return event response information corresponding to the signed event to the second functional network element within the interval length of the signing request parameter information when it is detected that the signed event corresponding to the target event type occurs.

[0181] Among them, the first functional network element is the first application functional entity, and the second functional network element is the second application functional entity; the request parameter data information includes at least: identification information of the second application functional entity, target event type, delay index for responding to events, effective time for capability call, call number threshold for capability call, and interval time for responding to events; among them, the delay index can be but is not limited to being used to instruct the network open function device to determine the first application functional entity that matches the capability call request sent by the second application functional entity.

[0182] The specific implementation methods of the contract request acquisition module 111, the contract verification module 112, the contract response return module 113, and the event response return module 114 can be found in the above Figure 3 The description of the first functional network element in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated.

[0183] For further information, see Fig.11 , Fig.11 It is a structural diagram of a data information acquisition device provided in an embodiment. In one embodiment, the device 12 may be a computer program (including program code) running in a computer device. For example, the device 12 may be a first functional network element running in a computer device; optionally, the device 12 may also be deployed on the first functional network element, and the first functional network element may run in the computer device. Optionally, the computer device here may also be a device independent of the first functional network element, and the computer device may be deployed on the same MEC platform (for example, the above-mentioned MEC platform 1) as the first functional network element. For ease of understanding, the embodiment of the present application takes the device 12 as an example of the first functional network element running in the above-mentioned computer device. The first functional network element can be used to execute the above-mentioned Figure 5 For further information, please refer to Fig.11 The device 12 may include: a call request receiving module 121, an authentication processing module 122, and a request response returning module 123.

[0184] The call request receiving module 121 is used to receive a capability call request forwarded by a network open function device associated with a first function network element; the capability call request is sent by a second function network element associated with the network open function device, and the capability call request carries request parameter data information;

[0185] The authentication processing module 122 is used to obtain the request parameter data information from the capability call request and perform authentication processing on the capability call request based on the request parameter data information;

[0186] The authentication processing module 122 includes: an authentication information acquisition unit 1221, a search unit 1222, and an authentication processing unit 1223;

[0187] The authentication information acquisition unit 1221 is used to obtain authentication information from the capability call request;

[0188] A searching unit 1222 is configured to search for the contract verification information matching the identification information of the second functional network element;

[0189] The authentication processing unit 1223 authenticates the authentication information based on the contract verification information if the contract verification information is found, and performs authorization processing on the capability call request when the authentication is successful.

[0190] The specific implementation of the authentication information acquisition unit 1221, the search unit 1222, and the authentication processing unit 1223 can be found in the above Figure 5 The description of the specific process of using the first functional network element to perform authentication processing in the corresponding embodiment will not be repeated here.

[0191] The request response returning module 123 is used to receive the capability call request when the authentication is successful, and generate request response parameter information for the capability call request, and forward the request response parameter information to the second functional network element through the network open function device; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0192] The request parameter data information carries the target event type for which the contract is requested; the request response returning module 123 includes: a legal request receiving unit 1231, an event type contracting unit 1232 and a request response sending unit 1233;

[0193] The legal request receiving unit 1231 is used to determine that the capability invocation request is a legal request when the authentication is successful, receive the legal request, and generate a signing instruction for the legal request;

[0194] The event type signing unit 1232 is used to determine the target event type as a signing event type based on the signing instruction, and generate request response parameter information for the signing event type;

[0195] The request response sending unit 1233 is configured to send the request response parameter information to the network open function device, so that the network open function device forwards the request response parameter information to the second function network element.

[0196] The specific implementation of the legal request receiving unit 1231, the event type signing unit 1232 and the request response sending unit 1233 can be found in the above Figure 5 The description of the specific process of generating request response parameter information in the corresponding embodiment will not be repeated here.

[0197] Among them, the first functional network element is deployed on the first platform; the second functional network element is deployed on the second platform; the first platform is different from the second platform, or the first platform and the second platform are the same platform.

[0198] The specific implementation of the call request receiving module 121, the authentication processing module 122, and the request response returning module 123 can be found in the above Figure 5 The description of steps S201 to S203 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here either.

[0199] For further information, see Fig.12 , Fig.12 It is a structural diagram of a data information acquisition device provided in an embodiment. In one embodiment, the device 21 may be a computer program (including program code) running in a computer device. For example, the device 21 may be a second functional network element running in a computer device; optionally, the device 21 may also be deployed on a second functional network element, and the second functional network element may run in a computer device. Optionally, the computer device here may also be a device independent of the second functional network element, and the computer device may be deployed on the same MEC platform (for example, the above-mentioned MEC platform 2) as the second functional network element. For ease of understanding, the embodiment of the present application takes the device 21 as an example of a second functional network element running in the above-mentioned computer device. The second functional network element may correspondingly execute the above-mentioned Figure 7 For further information, please refer to Fig.12 The device 21 may include: an authentication response receiving module 211, a contract signing request sending module 212, and a contract signing response receiving module 213. Further, the device 21 also includes: an identification obtaining module 214, a request parameter determining module 215, and a call request generating module 216;

[0200] The authentication response receiving module 211 is used to receive the authentication response parameter information returned by the network open function device, and determine the contract request parameter information based on the authentication response parameter information; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second function network element;

[0201] The contract request sending module 212 is used to add the contract request parameter information to the capability call contract request, and send the capability call contract request to the first functional network element, so that the first functional network element performs contract verification on the capability call contract request according to the access parameter information in the contract request parameter information;

[0202] The contract signing response receiving module 213 is used to receive capability call contract signing response information returned by the first functional network element when the contract signing verification is successful, and access the first functional network element based on the capability call contract signing response information.

[0203] Optionally, the identification acquisition module 214 is used to obtain the first identification information of the second function network element, the authentication information of the second function network element, and the target event type requested by the second function network element;

[0204] A request parameter determination module 215, configured to determine request parameter data information based on the first identification information, the authentication information and the target event type;

[0205] The call request generation module 216 is used to add request parameter data information to the capability call request; the capability call request is used to instruct the network open function device to authenticate the authentication information based on the contract verification information matching the first identification information, and when the authentication is successful and it is determined that the target event type is associated with the first functional network element, generate authentication response parameter information for the capability call request.

[0206] Among them, the authentication response parameter information includes at least one of the following: prompt information for indicating the reception of the capability call request, the second identification information of the first functional network element, the IP (Internet Protocol) address information of the first functional network element, the endpoint address (Endpoint Address) information of the first functional network element and the access parameter information; wherein the access parameter information is the access token information or target key information configured by the network open function device for the second functional network element for accessing the first functional network element.

[0207] Among them, the contract request parameter information includes at least: the first identification information of the second functional network element, the target event type, the access parameter information, the delay indicator for responding to the event, the effective time for capability calling, the call number threshold for capability calling, and the interval time for responding to the event.

[0208] Among them, the authentication response receiving module 211, the contract signing request sending module 212, and the contract signing response receiving module 213. Further, the device 21 also includes: an identification acquisition module 214, a request parameter determination module 215, and a call request generation module 216. For specific implementation methods, please refer to the above Figure 3 or Figure 7The description of the second functional network element in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated.

[0209] For further information, see Fig.13 , Fig.13 It is a structural diagram of a data information acquisition device provided in an embodiment. In one embodiment, the device 22 may be a computer program (including program code) running in a computer device. For example, the device 22 may be a second functional network element running in a computer device. Optionally, the device 22 may also be deployed on a second functional network element, and the second functional network element may run in a computer device. Optionally, the computer device here may also be a device independent of the second functional network element, and the computer device may be deployed on the same MEC platform (for example, the above-mentioned MEC platform 2) as the second functional network element. For ease of understanding, the embodiment of the present application takes the device 22 as an example of a second functional network element running in the above-mentioned computer device. The second functional network element may correspondingly execute the above-mentioned Figure 8 For further information, please refer to Fig.13 , the device 22 may include: a call request sending module 221 and a request response receiving module 222;

[0210] The call request sending module 221 is used to send a capability call request to the network open function device associated with the second function network element, so that the network open function device forwards the capability call request to the first function network element; wherein the first function network element is used to authenticate the capability call request based on the request parameter data information carried in the capability call request;

[0211] The request response receiving module 222 is used to receive the request response parameter information for the capability call request returned by the first functional network element through the network open function device when the authentication is successful; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

[0212] The specific implementation of the call request sending module 221 and the request response receiving module 222 can be found in the above Figure 5 or Figure 8 The description of the second functional network element in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated.

[0213] For further information, see Fig.14 , Fig.14 Schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.14As shown, the computer device may at least include a processor 1201, an input device 1202, an output device 1203, and a computer storage medium 1204. The processor 1201, the input device 1202, the output device 1203, and the computer storage medium 1204 may be connected via a bus or other means. The computer storage medium 1204 may be stored in the memory of the computer device, the computer storage medium 1204 is used to store a computer program, the computer program includes program instructions, and the processor 1201 is used to execute the program instructions stored in the computer storage medium 1204. The processor 1201 (or CPU (Central Processing Unit)) is the computing core and control core of the computer device, which is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more instructions to implement the corresponding method flow or corresponding function.

[0214] The embodiment of the present invention also provides a computer storage medium (Memory) 1204, which is a memory device of a computer device for storing programs and data. The computer storage medium provides a storage space, in which one or more instructions suitable for being loaded and executed by the processor 1201 are also stored. These instructions can be one or more computer programs (including program codes). It should be noted that the computer storage medium here can be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk storage; optionally, it can also be at least one computer storage medium located away from the aforementioned processor.

[0215] In one embodiment, the processor 1201 loads and executes one or more instructions stored in the computer storage medium, so that the computer device having the processor 1201 can implement Figure 3-Figure 9 In one embodiment, the computer device may execute the method in the above embodiment. Figure 3 , Figure 5 , Figure 7 or Figure 8 The description of the data information acquisition method in the corresponding embodiment can also be performed as described above. Fig.10 The description of the data information acquisition device 11 in the corresponding embodiment or the execution of the above Fig.11 The description of the data information acquisition device 12 in the corresponding embodiment can also be performed as described above. Fig.12 The description of the data information acquisition device 21 in the corresponding embodiment or the execution of the above Fig.13 The description of the data information acquisition device 22 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here either.

[0216] For further information, see Fig.15 , Fig.15 31 is a structural diagram of a data information acquisition system provided in an embodiment of the present application. The data information acquisition system 31 may at least include a data information acquisition device 311, a data information acquisition device 312 and a network open function device 313. The data information acquisition device 311 may be the above Fig.10 The data information acquisition device 11 in the corresponding embodiment or the above Fig.11 The data information acquisition device 12 in the corresponding embodiment will not be described in detail here. Figure 2 In the edge server 1 of the corresponding embodiment. In addition, the network open function device 313 can be the above Figure 2 In addition, it can be understood that the data information acquisition device 312 can be the above-mentioned Fig.12 The data information acquisition device 21 in the corresponding embodiment or the above Fig.13 The data information acquisition device 22 in the corresponding embodiment will not be described in detail here. Figure 2 In the edge server 2 of the corresponding embodiment. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the data information acquisition system embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0217] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0218] The above disclosure is only the preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims

1. A method for acquiring data information, characterized in that: The method is performed by a first functional network element, and includes: Obtaining a capability invocation contract request sent by the second functional network element based on contract request parameter information; the contract request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability invocation request; the capability invocation request is sent by the second functional network element; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; Acquire access parameter information for requesting access to the first function network element from the contract request parameter information carried by the capability call contract request, and perform contract verification on the capability call contract request based on the access parameter information; When the contract verification is successful, capability call contract response information is generated for the capability call contract request, and the capability call contract response information is returned to the second functional network element; the capability call contract response information is used to instruct the second functional network element to access the first functional network element.

2. The method according to claim 1, characterized in that The authentication response parameter information at least includes authentication success indication information; the authentication success indication information is obtained by the network open function device when confirming receipt of the capability call request after successful authentication processing; the capability call request is generated by the second function network element based on the request parameter data information; the request event type in the request parameter data information at least includes: the target event type associated with the first function network element in the authentication response parameter information; The target event type is the same as the event type of the signed event in the capability call signing response information; The method further comprises: When the occurrence of a signed event corresponding to the target event type is detected, event response information of the signed event is returned to the second functional network element within the interval duration of the signing request parameter information.

3. The method according to claim 2, characterized in that The first functional network element is a first application functional entity, and the second functional network element is a second application functional entity; The request parameter data information includes at least: identification information of the second application function entity, the target event type, a delay indicator for responding to the event, an effective duration for capability calling, a call count threshold for capability calling, and an interval duration for responding to the event.

4. A method for acquiring data information, characterized in that: The method is performed by a first functional network element; the method comprises: receiving a capability invocation request forwarded by a network open function device associated with the first function network element; the capability invocation request is sent by a second function network element associated with the network open function device, and the capability invocation request carries request parameter data information; Acquire the request parameter data information from the capability call request, and perform authentication processing on the capability call request based on the request parameter data information; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; When authentication is successful, the capability call request is received, and request response parameter information for the capability call request is generated, and the request response parameter information is forwarded to the second functional network element through the network open function device; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

5. The method according to claim 4, characterized in that The request parameter data information carries identification information of the second function network element for which subscription is requested, and authentication information of the second function network element; The obtaining the request parameter data information from the capability call request, and performing authentication processing on the capability call request based on the request parameter data information, includes: Acquire the authentication information from the capability call request; Searching for contract verification information that matches the identification information of the second function network element; If the contract verification information is found, the authentication information is authenticated based on the contract verification information, and authorization processing is performed on the capability call request when the authentication is successful.

6. The method according to claim 5, characterized in that The request parameter data information carries the target event type for the contract signing request; When the authentication is successful, receiving the capability call request, generating request response parameter information for the capability call request, and forwarding the request response parameter information to the second function network element through the network open function device, includes: When the authentication is successful, determining that the capability invocation request is a legitimate request, receiving the legitimate request, and generating a signing instruction for the legitimate request; Determining the target event type as a contract signing event type based on the contract signing instruction, and generating request response parameter information for the contract signing event type; The request response parameter information is sent to the network open function device, so that the network open function device forwards the request response parameter information to the second function network element.

7. The method according to claim 4, characterized in that The first functional network element is deployed on a first platform; the second functional network element is deployed on a second platform; the first platform is different from the second platform, or the first platform and the second platform are the same platform.

8. A method for acquiring data information, characterized in that: The method is performed by a second functional network element, and includes: receiving authentication response parameter information returned by the network open function device, and determining the contract request parameter information based on the authentication response parameter information; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second function network element; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; Adding the contract request parameter information to the capability call contract request, and sending the capability call contract request to the first functional network element, so that the first functional network element performs contract verification on the capability call contract request according to the access parameter information in the contract request parameter information; Receive capability call contract response information returned by the first functional network element when the contract verification is successful, and access the first functional network element based on the capability call contract response information.

9. The method according to claim 8, characterized in that The method further comprises: Acquire the first identification information of the second function network element, the authentication information of the second function network element, and the target event type requested by the second function network element; Determining the request parameter data information based on the first identification information, the authentication information and the target event type; Add the request parameter data information to the capability call request; the capability call request is used to instruct the network open function device to authenticate the authentication information based on the contract verification information matching the first identification information, and when the authentication is successful and it is determined that the target event type is associated with the first functional network element, generate authentication response parameter information for the capability call request.

10. The method according to claim 9, characterized in that The authentication response parameter information includes at least one of the following: prompt information for indicating receiving the capability call request, second identification information of the first functional network element, IP (Internet Protocol) address information of the first functional network element, endpoint address (Endpoint Address) information of the first functional network element, and the access parameter information; wherein the access parameter information is the access token information or target key information configured by the network open function device for the second functional network element for accessing the first functional network element.

11. The method according to claim 10, characterized in that The contract request parameter information includes at least: the first identification information of the second functional network element, the target event type, the access parameter information, the effective duration for capability calling, the call number threshold for capability calling, and the interval duration for responding to events.

12. A method for acquiring data information, characterized in that: The method is performed by a second functional network element; the method includes: Sending a capability call request to a network open function device associated with the second function network element, so that the network open function device forwards the capability call request to the first function network element, the first function network element is used to perform authentication processing on the capability call request based on the request parameter data information carried in the capability call request; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; Receive request response parameter information for the capability call request returned by the first functional network element through the network open function device when authentication is successful; the request response parameter information is used to instruct the second functional network element to access the first functional network element.

13. A data information acquisition device, characterized in that: include: A contract signing request acquisition module, used to acquire a capability call contract signing request sent by the second function network element based on contract signing request parameter information; The contract request parameter information is determined by the authentication response parameter information received by the second functional network element; the authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; the capability call request is sent by the second functional network element; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; A contract verification module, configured to obtain access parameter information for requesting access to a first functional network element from the contract request parameter information carried by the capability call contract request, and perform contract verification on the capability call contract request based on the access parameter information; A contract signing response returning module, configured to generate capability calling contract signing response information for the capability calling contract signing request when the contract signing verification succeeds, and return the capability calling contract signing response information to the second function network element; The capability invocation contract response information is used to instruct the second function network element to access the first function network element.

14. A data information acquisition device, characterized in that: include: A call request receiving module, configured to receive a capability call request forwarded by a network open function device associated with a first function network element; The capability invocation request is sent by a second functional network element associated with the network open function device, and the capability invocation request carries request parameter data information; an authentication processing module, used to obtain the request parameter data information from the capability call request, and perform authentication processing on the capability call request based on the request parameter data information; the authentication processing is actively decided by the network open function device according to the policy information of the network operator or the network topology information; The request response returning module is used to receive the capability call request when the authentication is successful, and generate request response parameter information for the capability call request, and forward the request response parameter information to the second function network element through the network open function device; the request response parameter information is used to instruct the second function network element to access the first function network element.

15. A data information acquisition device, characterized in that: include: An authentication response receiving module, used to receive the authentication response parameter information returned by the network open function device, and determine the contract signing request parameter information based on the authentication response parameter information; The authentication response parameter information is obtained after the network open function device performs authentication processing on the capability call request; The capability call request is sent by the second functional network element; the authentication process is actively decided by the network open function device according to the policy information of the network operator or the network topology information; A contract signing request sending module, configured to add the contract signing request parameter information to the capability call contract signing request, and send the capability call contract signing request to the first functional network element, so that the first functional network element performs contract signing verification on the capability call contract signing request according to the access parameter information in the contract signing request parameter information; The contract signing response receiving module is used to receive the capability call contract signing response information returned by the first functional network element when the contract signing verification is successful, and access the first functional network element based on the capability call contract signing response information.

16. A data information acquisition device, characterized in that: include: A call request sending module, used to send a capability call request to a network open function device associated with a second function network element, so that the network open function device forwards the capability call request to the first function network element, and the first function network element is used to authenticate the capability call request based on the request parameter data information carried in the capability call request; The authentication process is actively decided by the network open function device according to the policy information of the network operator or the network topology information; A request response receiving module, used to receive the request response parameter information for the capability call request returned by the first functional network element through the network open function device when the authentication is successful; The request response parameter information is used to instruct the second function network element to access the first function network element.

17. A computer device, characterized in that: include: Processor and memory; The processor is connected to a memory, wherein the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method according to any one of claims 1 to 12.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 12.

Images