CN111435924A - Method and device for calling application program interface - Google Patents

Abstract

The application provides a method and a device for calling an Application Program Interface (API), which can determine a target open function network element for calling the API. The method comprises the following steps: the first network element acquires routing information of an API (application program interface), wherein the routing information is used for indicating a route for calling the API, and the API is provided by a first open function network element and a second open function network element; the first network element acquires calling parameter information of the API, wherein the calling parameter information is used for operating the API; and the first network element determines a target open function network element from the first open function network element and the second open function network element according to the routing information and the calling parameter information.

Description

Method and apparatus for calling application program interface

technical field

The present application relates to the field of communications, and in particular, to a method and apparatus for calling an application program interface (application programmers interface API, API) in the field of communications.

Background technique

The common API framework (CAPIF) generally includes an API invoker (API invoker), a CAPIF core function (CCF) network element, an API exposing function (AEF) network element, and an API publishing function. (API publishing function, APF) network element and API management function (API management function, APIMF) network element. Among them, the API calling entity is generally a third-party application that has signed a service agreement with the operator, and has the ability to call the API. AEF provides APIs, and also serves as the entry point for API calling entities to call APIs. APF provides the function of publishing API and publishes the API in CCF. The CCF saves the APIs published by the APF, so that the API calling entity can discover the API and call the API. APIMF provides functionality to manage APIs.

When deploying CAPIF, the CCF can determine to use a topology hiding strategy for the API, that is, select a topology hiding entry point AEF (generally referred to as a boundary AEF) for the API. Then, when the API calling entity calls the API, the boundary AEF can determine the AEF that actually provides the API, and send an API calling request to the AEF. For a scenario in which an API is provided by only one AEF, the boundary AEF can determine the AEF that actually provides the API according to the identifier of the API, and directly sends an API call request to the AEF that actually provides the API. For a scenario where an API can be provided by multiple AEFs, when the API is provided to the API calling entity, the CCF applies a topology hiding strategy to it, and the boundary AEF cannot determine which of the multiple AEFs that should provide the API. AEF sends an API call request, which causes the API call to fail.

SUMMARY OF THE INVENTION

The present application provides a method and apparatus for calling an application program interface, which can determine a target open function network element for calling the API in a scenario where an API is provided by multiple open function network elements, thereby successfully calling the API.

In a first aspect, a method for invoking an application program interface is provided, including: a first network element obtains routing information of an API, where the routing information is used to indicate a route for invoking the API, and the API is provided by the first open function network element and a second open function network element; the first network element obtains the calling parameter information of the API, and the calling parameter information is used to operate the API; the first network element The invocation parameter information is used, and the target open function network element is determined from the first open function network element and the second open function network element.

In the method for invoking an application program interface according to the embodiment of the present application, in a scenario where an API is provided by multiple open function network elements, by combining the routing information of the API and the invocation parameter information of the API, the method for invoking the API can be determined. The target open function network element, so that the border open function network element forwards the API call request to the target open function network element, so that the API call is successful.

In this embodiment, the first network element may be a core function network element, a publishing function network element, or an open function network element (ie, a border open function network element that can receive an API call request from an API calling entity).

With reference to the first aspect, in some implementations of the first aspect, the invocation parameter information includes identification information of a terminal device and/or location information of the terminal device; and/or the routing information includes the first Information of an open function network element, information of the second open function network element, and information of the first service area and information of the second service area corresponding to the API, wherein the first open function network element provides The API provided by the second open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

With reference to the first aspect, in some implementations of the first aspect, the first network element is a core function network element, and the first network element obtains the calling parameter information of the API, including: the first network element The element receives the calling parameter information of the API from the boundary opening function network element; the method further includes: the first network element sends the information of the target opening function network element to the boundary opening function network element.

Specifically, the above-mentioned first network element is a core function network element, and the core function network element can receive the calling parameter information of the API from the border opening function network element. Further, after determining the target open function network element according to the routing information and calling parameter information of the API, the core function network element can send the information of the target open function network element to the border open function network element, so that the target open function network element can be The element sends the API calling request from the API calling entity to the target open function network element.

With reference to the first aspect, in some implementations of the first aspect, the first network element is a core function network element, and the first network element obtains the routing information of the API, including: the first network element is published from The functional network element receives the routing information of the API.

As an optional embodiment, the first network element is a core function network element, and the first network element obtains the routing information of the API, which may be determined by the first network element from locally preconfigured AEF information. routing information.

With reference to the first aspect, in some implementations of the first aspect, the above-mentioned first network element is a publishing function network element, and the publishing function network element can obtain the API information locally.

With reference to the first aspect, in some implementations of the first aspect, the first network element is a core function network element, and the method further includes: the first network element receives the first network element from a publishing function network element The information of the open function network element and the information of the second open function network element, and the information of the first service area and the information of the second service area, wherein all the information provided by the first open function network element The API corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area; the first network element obtains the routing information of the API, including: the first network element The element generates the routing information of the API according to the information of the first open function network element and the information of the second open function network element, as well as the information of the first service area and the information of the second service area .

Specifically, the above-mentioned first network element is a core function network element, and the first network element can be based on the received information of the first open function network element, information of the second open function network element, information of the first service area, and The information of the second service area is used to generate the routing information of the above-mentioned API. Optionally, the routing information may indicate the correspondence between the first service area and the first open function network element, and the correspondence between the second service area and the second open function network element.

With reference to the first aspect, in some implementations of the first aspect, the first network element is a border opening function network element, and the first network element obtains the routing information of the API, including: the first network element from the The core function network element or the publishing function network element receives the routing information of the API.

Specifically, if the first network element is a border opening function network element, the border opening function network element may receive the routing information of the API from the core function network element or the publishing function network element. Exemplarily, if there is an interface between the border opening function network element and the publishing function network element, the publishing function network element can directly send the routing information of the API to the border opening function network element through the interface. Exemplarily, if there is no interface between the border opening function network element and the publishing function network element, the publishing function network element can send the API routing information to the core function network element, and the core function network element sends the API information to the core function network element. Border opening function network element.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the first network element sends a request message, where the request message is used to request routing information of the API, and the request message Including the identification information of the API.

Specifically, the first network element is a border opening function network element, and the border opening function network element may also send a request message to the core function network element or the publishing function network element for requesting the routing information of the API. Since the routing information is for a specific API, the request message may also include identification information of the requested API. In general, after receiving the API call request from the API calling entity, the network element with the open border function sends the above request message to the core function network element or the publishing function network element. The API corresponding to the routing information requested by the request message is the The API that was requested to be called for this API call request.

In the embodiment of the present application, only when the border opening function network element receives the API call request, the border opening function network element requests routing information from the core function network element, instead of the core function network element actively requesting the border opening function network element Sending the routing information avoids that the network element with the border opening function obtains the routing information but does not use it, resulting in waste of push signaling and related information.

In a second aspect, another method for invoking an application program interface is provided, including: a second network element obtains routing information of an API, where the routing information is used to indicate a route for invoking the API, and the API is opened by the first open function provided by the network element and the second open function network element; the second network element sends the routing information to the border open function network element, where the routing information is used for the border open function network element to determine the target open function network element , the target open function network element is determined from the first open function network element and the second open function network element.

With reference to the second aspect, in some implementations of the second aspect, the routing information includes information of a first open function network element that provides the API, information of a second open function network element, and information corresponding to the API. The information of the first service area and the information of the second service area, wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponding to the second service area.

With reference to the second aspect, in some implementations of the second aspect, the second network element is a core function network element, and the method further includes: the second network element receives the first network element from a publishing function network element The information of the open function network element and the information of the second open function network element, and the information of the first service area and the second service area corresponding to the API, wherein the first open function network element The provided API corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area; the second network element obtains the routing information of the API, including: the The second network element generates the API according to the information of the first open function network element and the information of the second open function network element, as well as the information of the first service area and the information of the second service area routing information.

With reference to the second aspect, in some implementations of the second aspect, before the second network element sends the routing information to the border opening function network element, the method further includes: the second network element Receive a request message from the border opening function network element, where the request message is used to request the routing information, and the request message includes the identification information of the API; the second network element reports to the border opening function network element Sending the routing information includes: the second network element sending the routing information to the border opening function network element according to the request message.

A third aspect provides a method for invoking an application program interface, including: a first network element acquiring API information, the API information including information of a first open function network element that provides the API and a second open function network element information, and the information of the first service area and the information of the second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, the second service area The API provided by the open function network element corresponds to the second service area; the first network element obtains call parameter information of the API, where the call parameter information includes the identification information of the terminal device and/or the terminal device location information; the first network element determines a target open function network element from the first open function network element and the second open function network element according to the API information and the invocation parameter information.

In the method for invoking an application program interface according to the embodiment of the present application, in a scenario where an API is provided by multiple open function network elements, by combining the information of the service area corresponding to the API, the multiple open function network elements that provide the API, and the API The call parameter information can determine the target open function network element used to call the API, so that the border open function network element forwards the API call request to the target open function network element, so that the API call is successful.

In this embodiment, the first network element may be a core function network element, a publishing function network element, or an open function network element (ie, a border open function network element that can receive an API call request from an API calling entity).

With reference to the third aspect, in some implementations of the third aspect, the first network element is a core function network element, and the first network element obtains the calling parameter information of the API, including: the first network element The element receives the calling parameter information of the API from the boundary opening function network element; the method further includes: the first network element sends the information of the target opening function network element to the boundary opening function network element.

Specifically, the above-mentioned first network element is a core function network element, and the core function network element can receive the calling parameter information of the API from the border opening function network element. Further, after determining the target open function network element according to the API information and the calling parameter information, the core function network element may send the information of the target open function network element to the border open function network element, so that the target open function network element will The API call request from the API call entity is sent to the target open function network element.

With reference to the third aspect, in some implementations of the third aspect, the first network element is a core function network element, and the first network element acquiring the API information includes: the first network element obtains API information from the publishing function network element. Meta receives the API information.

With reference to the third aspect, in some implementations of the third aspect, the above-mentioned first network element is a publishing function network element, and the publishing function network element can obtain the API information locally. This embodiment of the present application does not limit this.

With reference to the third aspect, in some implementations of the third aspect, the first network element is a border opening function network element, and the first network element obtains API information, including: the first network element obtains the API information from the core function The network element or the publishing function network element receives the API information.

Specifically, if the above-mentioned first network element is a boundary opening function network element, the boundary opening function network element may receive the above-mentioned API information from the core function network element or the publishing function network element. Exemplarily, if there is an interface between the border opening function network element and the publishing function network element, the publishing function network element can directly send the API information to the border opening function network element through the interface. Exemplarily, if there is no interface between the border opening function network element and the publishing function network element, the publishing function network element can send the API information to the core function network element, and then the core function network element sends the API information to the border opening function network element. functional network element.

With reference to the third aspect, in some implementations of the third aspect, the method further includes: the first network element generates, according to the API information, a routing rule for calling the API, where the routing rule for calling is used to indicate A route for calling the API; the first network element determines a target open function network element from the at least two open function network elements according to the API information and the calling parameter information, including: the first network element The element determines a target open function network element from the first open function network element and the second open function network element according to the calling routing rule and the called parameter information.

It should be understood that the invocation routing rule here may be included in the routing information in the first aspect and the second aspect, but this application does not limit it. Specifically, the above-mentioned first network element (core function network element, or border opening function network element, or publishing function network element, etc.) can generate a routing rule for calling the API according to the API information. In this case, the first network element The network element may determine the target open function network element according to the generated call routing rule and call parameter information. Optionally, the invocation routing rule may represent the correspondence between the first service area and the first open function network element, and the correspondence between the second service area and the second open function network element.

With reference to the third aspect, in some implementations of the third aspect, the first network element is a border opening function network element, and the method further includes: the first network element sends a request message, and the request message uses In order to request the call routing rule of the API, the request message includes the identification information of the API.

Specifically, the above-mentioned first network element is a border opening function network element, and the border opening function network element may also send a request message to the core function network element or the publishing function network element for requesting the calling routing rule of the API. Since the calling routing rule is for a specific API, the request message may also include identification information of the requested API. In general, after receiving the API call request from the API calling entity, the network element of the border opening function sends the above-mentioned request message to the core function network element or the publishing function network element. The request message requests the API corresponding to the routing rule. That is, the API requested to be called by the API call request.

In the embodiment of the present application, only when the border opening function network element receives the API call request, the border opening function network element requests the routing call rule from the core function network element, rather than the core function network element actively opening the border function network element to the border function network element. The element sends the call routing rule, which avoids that the border opening function network element obtains the call routing rule, but does not use it, resulting in waste of push signaling and related information.

In a fourth aspect, another method for invoking an application program interface is provided, including: acquiring API information by a second network element, where the API information includes information of a first open function network element that provides the API and a second open function network element element information, and the information of the first service area and the second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, and the first open function network element corresponds to the first service area. The API provided by the second open function network element corresponds to the second service area; the second network element sends the API information to the border open function network element, and the API information is used for the border open function network element to pair Determination of a target open function network element, the target open function network element is determined from the first open function network element and the second open function network element.

With reference to the fourth aspect, in some implementations of the fourth aspect, the method further includes: the second network element generates, according to the API information, a routing rule for calling the API, where the routing rule for calling is used to indicate The route for invoking the API; the second network element sends the invocation routing rule to the border opening function network element.

With reference to the fourth aspect, in some implementations of the fourth aspect, before the second network element sends the call routing rule to the border opening function network element, the method further includes: the second network element element receives a request message from the border opening function network element, the request message is used to request the call routing rule, and the request message includes the identification information of the API; the second network element reports to the border opening function The network element sending the calling routing rule includes: the second network element sending the calling routing rule to the border opening function network element according to the request message.

In a fifth aspect, an apparatus is provided for performing the method in each of the above aspects or any possible implementation manner of each aspect. Specifically, the apparatus includes a unit for performing the method in each of the above-mentioned aspects or any possible implementation manner of the various aspects.

In a sixth aspect, an apparatus is provided, the apparatus comprising: a transceiver, a memory, and a processor. The transceiver, the memory and the processor communicate with each other through an internal connection path, the memory is used for storing instructions, and the processor is used for executing the instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals , and when the processor executes the instructions stored in the memory, the execution causes the processor to perform the above-described various aspects or the methods in any possible implementation manner of the various aspects.

In a seventh aspect, there is provided a computer program product, the computer program product comprising: computer program code, when the computer program code is executed by a computing device, the computing device is made to perform each of the above aspects or any one of the various aspects method in one possible implementation.

In an eighth aspect, a computer-readable medium is provided for storing a computer program, the computer program comprising instructions for performing the method in each of the above-mentioned aspects or any possible implementation manner of the various aspects.

In a ninth aspect, a chip is provided, including: a processor for invoking and running a computer program from a memory, so that a device installed with the chip executes each of the above aspects or any of the possible implementations of the various aspects Methods.

Description of drawings

FIG. 1 shows a schematic diagram of a system architecture of an embodiment of the present application.

FIG. 2 shows a schematic diagram of another system architecture of an embodiment of the present application.

FIG. 3 shows a schematic flowchart of a method for invoking an application program interface according to an embodiment of the present application.

FIG. 4 shows a schematic flowchart of another method for invoking an application program interface according to an embodiment of the present application.

FIG. 5 shows a schematic flowchart of another method for invoking an application program interface according to an embodiment of the present application.

FIG. 6 shows a schematic flowchart of another method for invoking an application program interface according to an embodiment of the present application.

FIG. 7 shows a schematic flowchart of another method for invoking an application program interface according to an embodiment of the present application.

FIG. 8 shows a schematic block diagram of an apparatus for invoking an application program interface according to an embodiment of the present application.

FIG. 9 shows a schematic block diagram of another apparatus for invoking an application program interface according to an embodiment of the present application.

FIG. 10 shows a schematic block diagram of another apparatus for invoking an application program interface according to an embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a global system for mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (wideband) system code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (long termevolution, LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, future fifth generation (5th generation, 5G) system or new Wireless (new radio, NR) and so on.

The terminal device in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication function handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminals in future evolved public land mobile networks (PLMN) equipment, etc., which are not limited in this embodiment of the present application.

The network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a global system for mobile communications (GSM) system or code division multiple access (CDMA) The base transceiver station (BTS) in the LTE system can also be the base station (NodeB, NB) in the wideband code division multiple access (WCDMA) system, or the evolved base station (evolved) in the LTE system. NodeB, eNB or eNodeB), it can also be a wireless controller in the cloud radio access network (cloud radio access network, CRAN) scenario, or the network device can be a relay station, an access point, an in-vehicle device, a wearable device, and future The network equipment in the 5G network or the network equipment in the future evolved PLMN network, etc., are not limited in the embodiments of the present application.

In this embodiment of the present application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiments of the present application do not specifically limit the specific structure of the execution body of the methods provided by the embodiments of the present application, as long as the program that records the codes of the methods provided by the embodiments of the present application can be executed to provide the methods provided by the embodiments of the present application. For example, the execution subject of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

Additionally, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer readable device, carrier or medium. For example, computer-readable media may include, but are not limited to, magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), cards, stick or key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

In this embodiment of the present application, the service API or API refers to the API provided by the AEF entity, which can be discovered and called by the API calling entity. APIs mainly include APIs of some specific service types, which can be used by API calling entities to use resources and services provided by operators, such as APIs for quality of service (QoS) control, APIs for broadcast, and Internet of Things (Internet of Things) of things, IoT) type API, etc.

FIG. 1 shows a schematic diagram of a system architecture 100 to which an embodiment of the present application is applied. As shown in FIG. 1 , the system architecture 100 includes: an API calling entity 110 and an open function network element 120 . Among them, the API calling entity 110 has the ability to call the API, and the open function network element 120 provides the API and also serves as the entry for the API calling entity to call the API.

Optionally, the foregoing system architecture 100 may further include at least one of a core function network element 130 , a management function network element 140 , and a publishing function network element 150 . Exemplarily, the publishing function network element 150 provides the function of publishing an API, and the API is published in the core function network element 130 . The core function network element 130 saves the API published by the publishing function network element 150, so that the API calling entity 110 can discover the API and call the API. The management function network element 140 provides functions of the management API.

Optionally, each network element in the foregoing system architecture 100 may be implemented by one device, or may be implemented jointly by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application. It can be understood that the above functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).

FIG. 2 is another system architecture 200 according to an embodiment of the present application. As shown in FIG. 2, the system architecture 200 may specifically include the following network elements:

1. API invoker

The API calling entity, also known as the API caller, is generally a third-party application that has signed a service agreement with the operator, such as machine to machine (M2M) applications, Internet of things (IoT) applications , vehicle to everything (V2X) applications, etc., and can also be operators' own applications. These applications can run on both terminal equipment and network equipment.

In addition, the API calling entity may also be a device in the PLMN network, for example, a mobile management entity (MME), a radio access network (RAN), a policy and a charging rule function in an LTE communication system (policy and charging rules function, PCRF), application network element (Application Function, AF), home subscriber server (home subscriber server, HSS) and the like. For another example, the authentication management function (APIMF) network element, the session management function (SMF) network element, the user plane function (UPF) network element, and user data management in the 5G communication system (unified data management, UDM), policy control function (Policy Control Function, PCF) network element, network element repository function (network repository function, NRF), network capability exposure function (network exposure function, NEF), application network element (Application Function) , AF) etc. The API calling entity may be in the same trust domain as the PLMN operator, or may not be in the same trust domain as the PLMN operator, which is not limited in this embodiment of the present application.

2. CAPIF core function (CAPIF core function, CCF) network element

CCF mainly includes the following functions: (1) Authenticate the API calling entity based on the identity and other information of the API calling entity; (2) Support mutual authentication between the CCF and the API calling entity; (3) Before the API calling entity calls the API The API calling entity provides authorization; (4) supports API publishing, API storage and API discovery; (5) is responsible for API access control based on the PLMN operator's policy; (6) stores API call logs and provides them to the authorized entity; (7) Billing based on API logs; (8) Monitoring API calls; (9) Registration of API calling entities; (10) Storage configuration policies; (11) Support for auditing calls and logs.

In an LTE communication system, the CCF may be deployed independently in a physical device, or may be deployed together with other entities, for example, in a service capability exposure function (service capability exposure function, SCEF). In the 5G communication system, CCF can be deployed independently in a physical device, or it can be deployed together with other entities, trying to be deployed in the NEF.

3. API exposing function (AEF) network element

AEF provides APIs and is also the entry point for API calling entities to call APIs. AEF mainly includes the following functions: (1) authenticate the API calling entity based on the identity of the API calling entity and other information provided by the CCF; (2) confirm the authorization provided by the CCF; (3) synchronize the API log to the CCF.

AEF can be deployed in NEF, or AEF can also be APIMF, SMF, UDM, PCF, NRF, NEF, etc. AEF can also be deployed in SCEF, or AEF can also be MME, PCRF, etc., used for PLMN internal network capabilities open.

4. API publishing function (API publishing function, APF)

APF provides API publishing functionality so that API calling entities can discover the API.

5. API management function network element (API management function, APIMF).

APIMF provides management of APIs, mainly including the following functions: (1) perform auditing of API call logs provided by CCF; (2) monitor events reported by CCF; (3) configure API provider policies to the API; (4) monitor The status of the API; (5) Register the API calling entity.

It should be understood that, in the above system architecture 100, the API calling entity 110 may specifically correspond to the API calling entity in FIG. 2 , the open function network element 120 may specifically correspond to the AEF in FIG. 2 , and the core function network element 130 may specifically correspond to the FIG. 2 In the CCF, the management function network element 140 may specifically correspond to the APIMF in FIG. 2 , and the publishing function network element 150 may specifically correspond to the APF in FIG. 2 .

It should be understood that the above-mentioned application scenario 200 applied to the embodiments of the present application is only an example of a network architecture described from the perspective of a service-oriented architecture, and the network architecture applicable to the embodiments of the present application is not limited thereto. The network architectures of the functions of the elements are all applicable to the embodiments of the present application.

It should be noted that the name of the interface between each network element in FIG. 2 is just an example, and the name of the interface in specific implementation may be other names, which are not specifically limited in this embodiment of the present application. For example, the API calling entity and the CCF network element are connected through the CAPIF-1 or CAPIF-1e interface. The API calling entity and the AEF network element are connected through the CAPIF-2 or CAPIF-2e interface. The CCF network element and the AEF network element are connected through the CAPIF-3 interface. The CCF network element and the APF network element are connected through the CAPIF-4 interface. The CCF network element and the APIMF network element are connected through the CAPIF-5 interface. Wherein, AEF network elements can be connected through CAPIF-2 or CAPIF-2i interfaces (“i” here represents the meaning of internal), which is not shown in FIG. 2 .

It should be noted that the name of each network element (such as CCF, APF, AEF, etc.) included in FIG. 2 is only an example, and does not limit the function of the network element itself. In the 5G network and other future networks, the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, and may also use other names, etc., which will be uniformly described here, and will not be repeated below. In addition, it should be understood that the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.

In the following, three processes related to calling an API are first introduced in conjunction with the above-mentioned system architecture 200 .

1. API release process

Step 1: APF sends an API release request message to CCF, and the API release request message includes API information, which may specifically include API name, AEF information that provides the API (such as AEF ID, version number, protocol used by the API, data Format, interface description (IP address, port number, security method), API description information, features supported by the API, etc.

Step 2: The CCF receives the API publishing request message from the APF, and checks whether the APF is authorized to publish the API. If the check passes, the CCF saves the above API information received from the APF.

Step 3: The CCF returns an API publishing response message to the APF, where the API publishing response message is used to indicate that the API publishing is successful or that the API publishing fails. In addition, the CCF can also send a notification message to the subscribed API calling entity to notify the API calling entity that there is a new API or an API that the API calling entity is interested in.

2. API discovery process

When the API calling entity has logged in and has the identity of the API calling entity, and the CCF has configured the discovery policy of the API calling entity, the following steps can be performed:

Step 1: The API calling entity sends an API discovery request message to the CCF, where the API discovery request message includes the identifier of the API calling entity and the discovery filter condition.

Step 2: The CCF receives the API discovery request message from the API calling entity, and authenticates the identity of the API calling entity according to the identity of the API calling entity. If the API calling entity passes the authentication, the CCF retrieves the published API information according to the above-mentioned discovery filter conditions and the policy information of the API calling entity.

Step 3: The CCF sends an API discovery response message to the API calling entity, where the API response message includes information about the API that the API calling entity is allowed to use. It should be understood that the information of the API may be information of one API, or information of multiple APIs.

3. API call process

Step 1: The API calling entity sends an API calling request message to the AEF, where the API calling request message includes the identifier of the API calling entity and the information of the API (for example, the identifier of the API).

Step 2: The AEF receives the API calling request message from the API calling entity, and authenticates the identity of the API calling entity according to the identity of the API calling entity. If the API calling entity passes the authentication, AEF executes the corresponding API logic.

Step 3: AEF sends an API call response message to the API call entity.

It should be understood that if the above-mentioned AEF is the AEF that actually provides the above-mentioned API (which can be understood as the destination AEF for handling the above-mentioned API), then the logic of the above-mentioned AEF for the above-mentioned API call is: the AEF is the API call Entity provides this API. If the above-mentioned AEF is not an AEF that actually provides the above-mentioned API, the logic of the above-mentioned AEF for the above-mentioned API call is: the AEF sends an API call request message to the AEF that actually provides the above-mentioned API. This is because when CAPIF is deployed, the CCF can determine to use a topology hiding strategy for the API, that is, select a topology hiding entry point AEF (generally referred to as a boundary AEF) for the API. Then, when the API calling entity calls the API, the boundary AEF can determine the AEF that actually provides the API, and send an API calling request to the AEF.

Specifically, in the above API publishing process, the APF sends an API publishing request message to the CCF, and the CCF stores the API information included in the API publishing request message, and decides to apply the topology hiding policy to the API requested by the APF to publish. In this case, the CCF may select an AEF as the boundary AEF for this API. The CCF sends an API topology hiding notification message to the border AEF, where the API topology hiding notification message is used for forwarding the API call request that may exist later. The API topology hiding notification message includes the information of the API and the information of the AEF that provides the API. The border AEF receives the above topology concealment notification message from the CCF, and saves the information therein. The CCF sends an API publish response message to the APF. It should be understood that the topology hiding strategy may be applying topology hiding to all API calling entities, or applying topology hiding to some API calling entities.

Due to the application of the topology hiding strategy, the CCF should change the information of the AEF that actually provides the API to the information of the boundary AEF, and correspondingly modify its interface information, and provide it to the API calling entity in the API discovery process. At this point, what the API calling entity gets is the boundary AEF and its interface information. The API calling entity can only send API calling requests to the boundary AEF. For a scenario in which an API is provided by only one AEF, the boundary AEF can determine the AEF that actually provides the API according to the identifier of the API, and directly sends an API call request to the AEF that actually provides the API.

For a scenario where an API can be provided by multiple AEFs (that is, multiple AEFs can provide the same API), the boundary AEF can obtain the information of multiple AEFs that provide the API after the API publishing process. It should be understood that an API or the same API referred to in this application refers to an API with the same API name and /API function. If the CCF does not apply the topology hiding policy to the above API, the API calling entity can obtain the information of multiple AEFs that provide the API, and the API calling entity can decide which AEF to use and its interface information. If the CCF applies the topology hiding policy to the above API, the API calling entity can only send the API call request to the border AEF, but the border AEF cannot determine which AEF should send the API call to among the multiple AEFs that provide the API. request, causing the API call to fail.

In view of this, an embodiment of the present application proposes a new method for invoking an API. In a scenario where an API is provided by multiple open function network elements, by combining the routing information of the API and the invocation parameter information of the API (for example, The identification and/or location of the terminal device) can determine the target AEF for calling the API, so that the border AEF forwards the API call request to the target AEF to implement the API call.

FIG. 3 shows a schematic flowchart of a method 300 for invoking an application program interface according to an embodiment of the present application. The method 300 may be applied to the communication system 100 shown in FIG. 1 and may also be applied to the communication system 200 shown in FIG. 2 , but the embodiment of the present application is not limited thereto.

S310: The first network element obtains routing information of the API, where the routing information is used to indicate a route for calling the API, and the API is provided by the first open function network element and the second open function network element.

For example, the API is provided by multiple open function network elements. The multiple open function network elements include a first open function network element and a second open function network element.

Optionally, the routing information of the API includes the information of the first open function network element and the information of the second open function network element that provide the API, and the information of the first service area and the second service corresponding to the API. area information, wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

S320, the first network element acquires call parameter information (application user or application client) of the API, where the call parameter information is used to operate the API.

The above-mentioned operation (handle) API can be understood as performing an operation (operation) on a resource (resource) corresponding to the API according to the detailed information of the API call request. The following description takes a protocol data unit (protocol data unit, PDU) session service API as an example for description. The operations allowed by this API include create, update, release, etc. The API contains a resource, which is identified by a uniform resource locator, such as {cmcc.smfapi. com}/{PDU Session}/{v1}. The calling parameter information may include the object corresponding to the resource, which may be used as a required input parameter of the API, such as the identifier of the terminal equipment, indicating that the terminal equipment identified above provides PDU session services. An example of operating the API, such as creating a PDU session for user 1, can understand that the AEF that provides the API creates a new session for user 1 under the resource directory of the API, and the resource directory after the operation is updated, which can be {cmcc. smfapi.com}/{PDU Session}/{v1}/{User 1}.

Optionally, the invocation parameter information includes identification information of the terminal device and/or location information of the terminal device.

S330, the first network element determines a target open function network element from the first open function network element and the second open function network element according to the routing information and the invocation parameter information.

In the method for calling an application program interface according to the embodiment of the present application, in a scenario where an API is provided by multiple open function network elements, by combining the routing information of the API and the calling parameter information of the API, the multiple open function network elements can be accessed from the multiple open function network elements. A target open function network element for invoking the API is determined in the process, so that the border open function network element forwards the API call request to the target open function network element, so that the API call is successful.

In this embodiment, the first network element may be a core function network element, a publishing function network element, or an open function network element (that is, a border open function network element that can receive an API call request from an API calling entity). The embodiment does not limit this.

The above determination of the target open function network element from the first open function network element and the second open function network element means that the determined target open function network element is one of the first open function network element and the second open function network element . In other words, the target open function network element is the first open function network element or the second open function network element.

Specifically, one API is provided by multiple open function network elements, and among the multiple open function network elements, APIs provided by different open function network elements may correspond to different service areas. In other words, there is a correspondence between the multiple service areas corresponding to the API and the multiple open function network elements. For ease of understanding and description, in this embodiment, the multiple open function network elements that provide the API include a first open function network element and a second open function network element, and the multiple service areas corresponding to the API include the first service area and the second open function network element. The service area is used as an example. It can be understood that the APIs mentioned in this application all refer to the same API, which will not be repeated in the following. The API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

The service area represents the service scope of the API provided on the open function network. Exemplarily, if the service area is represented by a domain name, such as cmcc.beijing.com, it means that the API can provide services for users (terminal devices or application clients) within the area. Exemplarily, if the service area is represented by an IP address segment, such as 10.11.1.0 to 10.11.1.255, it means that the API can provide services for users (terminal devices or application clients) whose IP addresses are within this address range. Exemplarily, if the service area is represented by an IP address prefix, it means that the API can provide services for users (terminal devices or application clients) with the IP address prefix. Exemplarily, if the service area is represented by location area (area) information, it means that the API can provide services for users (terminal devices or application clients) whose current location is in the area.

In addition, the provision of the API by the open function network element can be understood as the open function network element handling the API, for example, the open function network element can specifically create, modify, delete, query, etc. The information of the open function network element that provides the API can be the interface information of the API, and the interface information of the API has the IP address and/or port number information of the open function network element, and the uniform resource identifier of the API resource. identifier (unified resource identifier, URI), etc.

Then, the first network element can obtain the information of the open function network element that provides the API and the information about the service area of the corresponding API, and then combine the call parameter information of the API (for example, terminal equipment (subscriber, application user, application client) identification information and/or location information), you can determine from the first open function network element and the second open function network element the target openness that can truly provide the API in the area corresponding to the terminal device functional network element.

Exemplarily, taking a terminal device as an example, the identification information of the terminal device may be the ID of the terminal device, such as a 3GPP subscriber identification or device identification, or the IP address of the terminal device; the location information of the terminal device may be The IP address of the terminal device, or the area information where the terminal device is located, or the current location information of the terminal device. It should be understood that the above-mentioned terminal device is the terminal device corresponding to the API, that is, the API calling entity calls the API to serve the terminal device, or the API is called by the API calling entity for the terminal device, or the terminal device It is the object of the operation of the API call, for example, the API calling entity calls the API to obtain the information of the terminal device.

As an optional embodiment, the first network element is a core function network element, and acquiring the calling parameter information of the API by the first network element includes: the first network element receives from the border opening function network element Call parameter information of the API; and the method further includes: the first network element sending the information of the target open function network element to the border open function network element.

Specifically, the above-mentioned first network element is a core function network element, and the core function network element can receive the calling parameter information of the API from the border opening function network element. Further, after determining the target open function network element according to the routing information and calling parameter information of the API, the core function network element can send the information of the target open function network element to the border open function network element, so that the target open function network element can be The element sends the API calling request from the API calling entity to the target open function network element.

Exemplarily, the above-mentioned border opening function network element may call a routing request message (service API invocation routing request) through an API, or obtain a topology hiding policy request message (obtain topology hiding policy request), or other messages sent by the border AEF to the CCF. The calling parameter information is sent to the core function network element, and the specific message name is not limited in this embodiment of the present application. Exemplarily, the above-mentioned core function network element may call a routing response message (service API invocation routing response), or obtain a topology hiding policy response message (obtain topology hiding policy response), or an API topology hiding notification message (APItopology hiding notify) through an API. , or other messages sent by the CCF to the border AEF, to feed back the information of the above-mentioned target open function network element to the border open function network element, and the specific message name is not limited in this embodiment of the present application.

As an optional embodiment, the first network element is a core function network element, and the first network element acquiring the routing information of the API includes: the first network element receiving the API's routing information from the publishing function network element routing information. That is, the core function network element may receive the routing information of the above API from the publishing function network element.

As an optional embodiment, the first network element is a core function network element, and the first network element obtains the routing information of the API, which may be determined by the first network element from locally preconfigured AEF information. routing information.

As another optional embodiment, the above-mentioned first network element is a publishing function network element, and the publishing function network element can locally obtain the routing information of the API from the publishing function network element. This embodiment of the present application does not limit this.

As an optional embodiment, the first network element is a core function network element, and the method further includes: receiving, by the first network element, the information of the first open function network element and the information of the first open function network element from the publishing function network element. the information of the second open function network element, the information of the first service area corresponding to the API, and the information of the second service area, wherein the API provided by the first open function network element corresponds to the The first service area, the API provided by the second open function network element corresponds to the second service area; the first network element acquiring the routing information of the API includes: the first network element according to the first network element. The routing information of the API is generated by the information of an open function network element and the information of the second open function network element, as well as the information of the first service area and the information of the second service area.

Specifically, the above-mentioned first network element is a core function network element, and the first network element can be based on the received information of the first open function network element, information of the second open function network element, information of the first service area, and The information of the second service area (herein collectively referred to as API information) generates the routing information of the above-mentioned API.

Optionally, the routing information may indicate the correspondence between the first service area and the first open function network element, and the correspondence between the second service area and the second open function network element.

The routing information of the above API may also be referred to as "API calling routing rules" in this embodiment of the present application, and the present application does not limit its name. It should be understood that the invocation routing rule can be specifically embodied in the form of a table or a formula, and the specific expression form thereof is not limited in this application.

As an optional embodiment, the first network element is a border opening function network element, and the first network element obtains the routing information of the API, including: the first network element obtains the API from the core function network element or the publishing function network element. Meta receives routing information for the API.

Specifically, if the first network element is a border opening function network element, the border opening function network element may receive the routing information of the API from the core function network element or the publishing function network element. Exemplarily, if there is an interface between the border opening function network element and the publishing function network element, the publishing function network element can directly send the routing information of the API to the border opening function network element through the interface. Exemplarily, if there is no interface between the border opening function network element and the publishing function network element, the publishing function network element can send the API routing information to the core function network element, and then the core function network element sends the API routing information. It is sent to the network element of the border opening function.

As an optional embodiment, the first network element is a border opening function network element, and the method further includes: sending, by the first network element, a request message, where the request message is used to request routing information of the API , the request message includes the identification information of the API.

Specifically, the first network element is a border opening function network element, and the border opening function network element may also send a request message to the core function network element or the publishing function network element for requesting the routing information of the API. Since the routing information is for a specific API, the request message may also include identification information of the requested API. For example, after receiving the API call request from the API calling entity, the border opening function network element sends the above request message to the core function network element or the publishing function network element, and the API corresponding to the routing information requested by the request message is the API. The API call requests the API to be called. Wherein, the request message may be an API invocation routing request message (service API invocation routing request), or an obtain topology hiding policy request message (obtain topology hiding policy request), or other messages sent by the border AEF to the CCF, which is not done in the embodiment of the present application. limited.

In the embodiment of the present application, the network element with the open border function receives the API call request, and requests routing information from the network element with the core function, which prevents the network element with the open border function from actively sending the routing information to the border when the network element with the open border function does not need to use the routing information. The open-function network element sends the routing information, thereby saving signaling.

FIG. 4 shows a schematic flowchart of a method 400 for invoking an application program interface according to an embodiment of the present application. The method 400 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the application scenario 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto.

S410: The second network element obtains routing information of the API, where the routing information is used to indicate a route for calling the API, and the API is provided by the first open function network element and the second open function network element.

For example, the API is provided by multiple open function network elements. The multiple open function network elements include a first open function network element and a second open function network element.

Optionally, the routing information includes information of the first open function network element and information of the second open function network element, and information of the first service area and information of the second service area corresponding to the API , wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

S420, the second network element sends the routing information to the border opening function network element, where the routing information is used by the border opening function network element to determine a target open function network element, and the target open function network element is obtained from the determined from the first open function network element and the second open function network element.

Correspondingly, the border open function network element receives the routing information of the API from the second network element, and determines the target open function network element from the first open function network element and the second open function network element according to the routing information and the calling parameter information. .

S430, the network element of the border opening function acquires the calling parameter information of the API, where the calling parameter information is used to operate the API.

The above-mentioned operation (handle) API can be understood as performing an operation (operation) on a resource (resource) corresponding to the API according to the detailed information of the API call request. The following description takes a protocol data unit (protocol data unit, PDU) session service API as an example for description. The operations allowed by this API include create, update, release, etc. The API contains a resource, which is identified by a uniform resource locator, such as {cmcc.smfapi. com}/{PDU Session}/{v1}. The calling parameter information may include the object corresponding to the resource, which may be used as a required input parameter of the API, such as the identification of the terminal equipment, indicating that the terminal equipment with the above identification provides a PDU session service. An example of operating the API, such as creating a PDU session for user 1, can understand that the AEF that provides the API creates a new session for user 1 under the resource directory of the API, and the resource directory after the operation is updated, which can be {cmcc. smfapi.com}/{PDU Session}/{v1}/{User 1}.

Optionally, the invocation parameter information includes identification information of the terminal device (or subscriber, or application user, or application client) and/or the terminal device (or subscriber, or application user, or application client) location information.

S440, the border opening function network element determines a target open function network element from the first open function network element and the second open function network element according to the routing information and the invocation parameter information.

In the method for invoking an application program interface according to the embodiment of the present application, in a scenario where an API is provided by multiple open function network elements, by sending the routing information of the API to the border open function network element, the border open function network element can combine the API The calling parameter information, the target AEF for calling the API is determined from the above-mentioned multiple open function network elements, so that the border AEF forwards the API calling request to the target AEF to implement the API calling.

In this embodiment, the second network element may be a core function network element or a release function network element.

The above determination of the target open function network element from the first open function network element and the second open function network element means that the determined target open function network element is one of the first open function network element and the second open function network element . In other words, the target open function network element is the first open function network element or the second open function network element.

Specifically, one API is provided by multiple open function network elements, and among the multiple open function network elements, APIs provided by different open function network elements correspond to different service areas. In other words, there is a correspondence between the multiple service areas corresponding to the API and the multiple open function network elements. For ease of understanding and description, the multiple open function network elements that provide the API in this embodiment include a first open function network element and a second open function network element, and the multiple service areas corresponding to the API include a first service area and a second open function network element. The service area is used as an example. It can be understood that the APIs mentioned in this application all refer to the same API, which will not be repeated in the following. The API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

The service area represents the service scope of the API provided on the open function network. Exemplarily, if the service area is represented by a domain name, such as cmcc.beijing.com, it means that the API can provide services for users (terminal devices or application clients) within the area. Exemplarily, if the service area is represented by an IP address segment, such as 10.11.1.0 to 10.11.1.255, it means that the API can provide services for users (terminal devices or application clients) whose IP addresses are within this address range. Exemplarily, if the service area is represented by an IP address prefix, it means that the API can provide services for users (terminal devices or application clients) with the IP address prefix. Exemplarily, if the service area is represented by location area (area) information, it means that the API can provide services for users (terminal devices or application clients) whose current location is in the area.

In addition, the provision of the API by the open function network element can be understood as the open function network element handling the API, for example, the open function network element can specifically create, modify, delete, query, etc. The information of the open function network element that provides the API can be the interface information of the API, and the interface information of the API has the IP address and/or port number information of the open function network element, and the uniform resource identifier of the API resource. identifier (unified resource identifier, URI), etc.

Then, the second network element may obtain the routing information of the API, for example, the routing information may include the information of the network element providing the open function of the API and the information of the corresponding service area of the API. The second network element sends the API's routing information to the border opening function network element, and the border opening function network element combines the API's routing information and the API's calling parameter information (for example, terminal equipment (subscriber, application) according to the API's routing information. User, application client) identification information and/or location information), determine from the first border opening function network element and the second border opening function network element the target that can actually provide the API in the area corresponding to the terminal device Open functional network elements. For a specific method for determining the target open function network element by the border opening function network element, reference may be made to the method 300, which will not be repeated here.

Exemplarily, taking a terminal device as an example, the identification information of the terminal device may be the ID of the terminal device, or the IP address of the terminal device; the location information of the terminal device may be the IP address of the terminal device, or the terminal device. Information about the area where the terminal device is located, or the current location information of the terminal device. It should be understood that the above-mentioned terminal device is the terminal device corresponding to the API, that is, the API calling entity calls the API to serve the terminal device, or in other words, the API is called by the API calling entity for the terminal device, for example, the API calling entity calls This API obtains the information of the terminal device.

As an optional embodiment, the second network element is a core function network element, and the method further includes: the second network element receiving the information of the first open function network element and the information of the first open function network element from the publishing function network element. information of the second open function network element, information of the first service area and information of the second service area, wherein the API provided by the first open function network element corresponds to the first service area, the API provided by the second open function network element corresponds to the second service area; the second network element obtaining the routing information of the API includes: the second network element according to the first open function The routing information of the API is generated from the information of the network element and the information of the second open function network element, as well as the information of the first service area and the information of the second service area.

Optionally, the routing information may specifically represent the correspondence between the first service area and the first open function network element, and the relationship between the second service area and the second open function network element. corresponding relationship.

Specifically, the above-mentioned second network element (core function network element) may be based on the received information of the first open function network element, information of the second open function network element, information of the first service area, and information of the second service area. information (herein collectively referred to as API information) to generate routing information for the API. In this case, the second network element can send the API routing information to the border opening function network element, so that the border opening function network element can determine the target open function network element according to the API routing information and calling parameter information.

As an optional embodiment, before the second network element sends the routing information to the border opening function network element, the method further includes: the second network element opens the border opening function network element from the border opening function network element. Receive a request message, where the request message is used to request the routing information, and the request message includes the identification information of the API; the second network element sends the routing information to the border opening function network element, including: The second network element sends the routing information to the border opening function network element according to the request message.

Specifically, the above-mentioned boundary opening function network element may also send a request message to the second network element (ie, the core function network element or the publishing function network element), for requesting the routing information of the above-mentioned API. Since the routing information is for a specific API, the request message may also include identification information of the requested API. In general, after receiving the API call request from the API calling entity, the network element with the open border function sends the above request message to the core function network element or the publishing function network element. The API corresponding to the routing information requested by the request message is the The API that was requested to be called for this API call request. Wherein, the request message may be an API invocation routing request message (service API invocation routing request), or an obtain topology hiding policy request message (obtain topology hiding policy request), or other messages sent by the border AEF to the CCF, which is not done in the embodiment of the present application. limited.

For specific embodiments of the above method, reference may be made to FIG. 5 to FIG. 10 and the corresponding text descriptions, which will not be repeated here.

For ease of understanding, the embodiments of the present application are described in detail below with reference to FIGS. 5 to 10 , taking the core function network element as the CCF, the publishing function network element as the APF, and the open function network element as the AEF as an example.

FIG. 5 shows a schematic flowchart of a method 500 for invoking an application program interface according to an embodiment of the present application. The method 500 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the application scenario 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto. In this embodiment, the API information is equivalent to the routing information of the above-mentioned API.

In S501, the APF and the CCF execute the API publishing process.

Specifically, the APF sends an API release request to the CCF, where the API release request includes API information. The API information includes the API name and the AEF information that provides the API. The AEF information includes interface information of the API, such as IP address, port number, or uniform resource identifier (URI), etc. The AEF information also includes Including the API serving area (API serving area) information corresponding to the API, the serving area information may be information such as an IP address segment, an IP address prefix, a geographic or administrative area, or a domain name. The CCF receives the API release request sent by the APF, and according to the received API information, determines the API application topology hiding policy corresponding to the API information. It should be understood that the topology hiding strategy may be applying topology hiding to all API calling entities, or applying topology hiding to some API calling entities. The CCF determines the boundary AEF.

In S502, the CCF determines the calling routing rule of the API, where the API is an API to which the above topology hiding policy is applied.

Specifically, the CCF may generate a call routing rule for the border AEF to determine the target AEF according to the API information. For example, the CCF may determine the calling routing rule of the API according to the corresponding service area information (such as IP address segment, geographic or administrative area, or domain name) in the API information. Further, the call routing rule may represent the mapping relationship between multiple service areas and multiple AEFs, or may directly represent the mapping relationship between multiple IP address segments or domain names and multiple AEFs.

In S503, the CCF sends the call routing rule of the API to the border AEF; correspondingly, the border AEF receives the call routing rule of the API from the CCF.

In S504, the API calling entity and the CCF execute the API discovery process.

In S505, the API calling entity sends an API calling request to the border AEF, and the API calling request may include API information (such as the address (URI) of the resource (resource) corresponding to the API, or the identification information of the API) and calling parameters information. The invocation parameter information may specifically be terminal device IP, area information, location information, and the like. Wherein, the terminal device IP represents the IP address of the terminal device, which can be IPv4 or IPv6; the area information represents the area information of the API application, and the area information can be network area description information, such as cell identification, tracking area (TA) The identifier, the area of interest identifier, etc., may also be physical area description information. The location information may indicate location information of the API application, and specifically may be location information of the terminal device.

In S506, the border AEF determines the target AEF according to the call routing rules and call parameter information of the API received from the CCF.

Exemplarily, the multiple AEFs that provide the above API include a first AEF and a second AEF, and a service area corresponding to the above API includes a first service area and a second service area. The above-mentioned invocation routing rule may represent the correspondence between the first service area and the first AEF, and the correspondence between the second service area and the second AEF. The above-mentioned invocation parameter information may include identification information and/or location information of the terminal device (subscriber, application user, application client), and further indicates the service area where the terminal device is located. For example, the invocation parameter information indicates that the terminal device is located in the second service area. area. Then, the border AEF can select the second service area corresponding to the second service area from the first AEF and the second AEF according to the second service area indicated by the invocation parameter information and the corresponding relationship indicated by the above invocation routing rule. The AEF is identified as the target AEF.

In S507, the boundary AEF sends an API call request to the target AEF, where the API call request includes API information (such as the address (URI) of the resource (resource) corresponding to the API, or the identification information of the API).

In S508, the target AEF sends an API call response to the boundary AEF.

In S509, the border AEF sends the API call response to the API call entity.

In the method for invoking an application program interface according to the embodiment of the present application, after receiving the API publishing request from the APF, the CCF obtains the API information and applies the topology hiding policy to the API, and sends the calling routing rule of the API to the border AEF, so that The boundary AEF determines the target AEF according to the call routing rules of the API, and realizes the forwarding of the API call request, thereby realizing the completion of the API call. In this embodiment, the CCF pushes the call routing rules to the border AEF before the call, which can reduce the call delay caused by the border AEF acquiring the call routing rules in the API call process, which is beneficial to improve the API call efficiency.

In another possible implementation manner of the present application, the CCF may determine the above-mentioned invocation routing rule according to locally pre-configured AEF information. In this case, the service scope of the API provided by the AEF is the service area of the AEF.

FIG. 6 shows a schematic flowchart of another method 600 for invoking an application program interface according to an embodiment of the present application. The method 600 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the application scenario 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto. In this embodiment, the API information is equivalent to the routing information of the above-mentioned API.

In S601, the APF and the CCF execute the API publishing process.

Specifically, the APF sends an API release request to the CCF, where the API release request includes API information. The API information includes the API name and the AEF information that provides the API. The AEF information includes interface information of the API, such as IP address, port number, or uniform resource identifier (URI), etc. The AEF information also includes Including the API serving area (API serving area) information corresponding to the API, the serving area information may be information such as an IP address segment, an IP address prefix, a geographic or administrative area, or a domain name. The CCF receives the API release request sent by the APF, and according to the received API information, determines the API application topology hiding policy corresponding to the API information. It should be understood that the topology hiding strategy may be applying topology hiding to all API calling entities, or applying topology hiding to some API calling entities. The CCF determines the boundary AEF.

In S602, the API calling entity and the CCF perform an API discovery process.

In S603, the API calling entity sends an API calling request to the border AEF, where the API calling request includes API information (such as the address (URI) of the resource (resource) corresponding to the API, or the identification information of the API) and calling parameter information . The invocation parameter information may specifically be terminal device IP, area information, location information, and the like. Wherein, the terminal device IP represents the IP address of the terminal device, which can be IPv4 or IPv6; the area information represents the area information of the API application, and the area information can be network area description information, such as cell identification, tracking area (TA) The identifier, the area of interest identifier, etc., may also be physical area description information. The location information may indicate location information of the API application, and specifically may be location information of the terminal device.

In S604, the border AEF receives the API call request from the API call entity, and sends the API call routing request to the CCF.

In S605, the CCF receives the API call routing request sent by the border AEF, and determines the call routing rule of the API, where the API is an API to which the above topology hiding policy is applied.

Specifically, the CCF may generate a call routing rule for the border AEF to determine the target AEF according to the API information. For example, the CCF may determine the calling routing rule of the API according to the corresponding IP address segment, service area, or domain name in the API information. Further, the call routing rule may represent the mapping relationship between multiple service areas and multiple AEFs, or may directly represent the mapping relationship between multiple IP address segments or domain names and multiple AEFs.

It should be understood that the above-mentioned CCF determines that the API call routing rule can also be executed in S602, that is, in the API discovery process, the CCF can first generate the API call routing rule and save it, and after receiving the API call routing request from the border AEF, Then, the calling routing rule of the API is sent to the border AEF, which is not limited in this embodiment of the present application.

In S606, the CCF sends an API call routing response to the border AEF, where the API call routing response includes the above-mentioned API call routing rules.

In S607, the boundary AEF determines the target AEF according to the call routing rule of the API received from the CCF and the call parameter information included in the API call request.

For example, for the boundary AEF to determine the target AEF, reference may be made to the description of step S506 in FIG. 5 , which will not be repeated here.

In S608, the border AEF sends an API call request to the target AEF, where the API call request includes API information (such as an address (URI) of a resource (resource) corresponding to the API, or API identification information).

In S609, the target AEF sends an API call response to the boundary AEF.

In S610, the border AEF sends the API call response to the API call entity.

In the method for invoking an application program interface according to the embodiment of the present application, after receiving the API invocation request, the border AEF requests the CCF for the invocation routing rules of the API, so as to determine the target AEF according to the received invocation routing rules and invocation parameter information of the API, Realize the forwarding of the API call request, so as to realize the completion of the API call. Further, in this embodiment of the present application, the border AEF receives the API call request, and requests the CCF for a routing call rule, which prevents the CCF from actively sending the call route to the border AEF when the border open function network element does not need to use the routing information. rules, thus saving signaling.

FIG. 7 shows a schematic flowchart of another method 700 for invoking an application program interface according to an embodiment of the present application. The method 700 may be applied to the system architecture 100 shown in FIG. 1 , and may also be applied to the application scenario 200 shown in FIG. 2 , and the embodiments of the present application are not limited thereto. In this embodiment, the API information is equivalent to the routing information of the above-mentioned API.

S701-S703 are the same as S601-S603, and are not repeated in this embodiment.

In S704, the border AEF receives the API call request from the API call entity, and sends the API call routing request to the CCF. Different from the above method 600, the API call routing request includes the call parameter information obtained by the border AEF from the API call entity. The invocation parameter information may specifically be terminal device IP, area information, location information, and the like. Wherein, the terminal device IP represents the IP address of the terminal device, which can be IPv4 or IPv6; the area information represents the area information of the API application, and the area information can be network area description information, such as cell identification, tracking area (TA) The identifier, the area of interest identifier, etc., may also be physical area description information. The location information may indicate location information of the API application, and specifically may be location information of the terminal device.

In S705, the CCF receives the API call routing request sent by the border AEF, and determines the target AEF according to the API information and the call parameter information.

Exemplarily, the multiple AEFs that provide the above API include a first AEF and a second AEF, and a service area corresponding to the above API includes a first service area and a second service area. The above-mentioned invocation routing rule may represent the correspondence between the first service area and the first AEF, and the correspondence between the second service area and the second AEF. The above-mentioned invocation parameter information may include identification information and/or location information of the terminal device (subscriber, application user, application client), and further indicates the service area where the terminal device is located. For example, the invocation parameter information indicates that the terminal device is located in the second service area. area. Then, the CCF can, according to the second service area indicated by the invocation parameter information, combined with the corresponding relationship indicated by the above invocation routing rule, select the second AEF corresponding to the second service area from the first AEF and the second AEF. identified as the target AEF.

In S706, the CCF sends an API call routing response to the border AEF, where the API call routing response includes the information of the target AEF, for example, the identifier of the target AEF.

S707-S709 are the same as S608-S610, and are not repeated in this embodiment.

In the method for invoking an application program interface in the embodiment of the present application, after receiving the API invocation request, the boundary AEF requests the CCF for the target AEF, so as to realize the forwarding of the API invocation request, thereby realizing the completion of the API invocation. Further, in the embodiment of the present application, the CCF determines the target AEF, and the border AEF only forwards the message according to the instruction of the CCF, which can reduce the burden of the border AEF.

It should be understood that the size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

The method for invoking an application program interface according to an embodiment of the present application is described in detail above with reference to FIGS. 1 to 7 , and the apparatus for invoking an application program interface according to an embodiment of the present application will be described in detail below with reference to FIGS. 8 to 10 .

FIG. 8 shows an apparatus 800 for invoking an application program interface provided by an embodiment of the present application. The apparatus 800 includes: an acquisition unit 810 and a processing unit 820 . Specifically, the apparatus 800 is configured to execute each process and step corresponding to the first network element in the foregoing method 200 .

The obtaining unit 810 is configured to: obtain routing information of an API, where the routing information is used to indicate a route for calling the API, the API is provided by the first open function network element and the second open function network element; and obtain Call parameter information of the API, where the call parameter information is used to operate the API;

The processing unit 820 is configured to: determine a target open function network element from the first open function network element and the second open function network element according to the routing information and the invocation parameter information.

Optionally, the invocation parameter information includes the identification information of the terminal device and/or the location information of the terminal device; and/or the routing information includes the information of the first open function network element and the second open function network element. the information of the open function network element, and the information of the first service area and the second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, The API provided by the second open function network element corresponds to the second service area.

Optionally, the apparatus is a core function network element, and the apparatus further includes: a first receiving unit, configured to receive call parameter information of the API from the border opening function network element; a first sending unit, configured to send the The border opening function network element sends the information of the target open function network element.

Optionally, the apparatus is a core function network element, and the apparatus further includes: a second receiving unit configured to receive the routing information of the API from the publishing function network element.

Optionally, the apparatus is a core function network element, and the apparatus further includes: a third receiving unit, configured to receive the information of the first open function network element and the second open function network element from the publishing function network element. element information, and the information of the first service area and the second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, so The API provided by the second open function network element corresponds to the second service area; the processing unit is further configured to: according to the information of the first open function network element and the information of the second open function network element , and the information of the first service area and the information of the second service area, to generate routing information of the API.

Optionally, the apparatus is a border opening function network element, and the apparatus further includes: a fourth receiving unit, configured for the first network element to receive the routing information of the API from a core function network element or a publishing function network element .

Optionally, the apparatus further includes: a second sending unit, configured to send a request message, where the request message is used to request routing information of the API, and the request message includes identification information of the API.

It should be understood that the apparatus 800 here is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group of processors, etc.) and memory, merge logic, and/or other suitable components to support the described functions. In an optional example, those skilled in the art can understand that the apparatus 800 may be specifically the first network element in the foregoing embodiment, and the apparatus 800 may be configured to execute various processes and processes corresponding to the first network element in the foregoing method embodiments. /or steps, in order to avoid repetition, details are not repeated here.

FIG. 9 shows another apparatus 900 for invoking an application program interface provided by an embodiment of the present application. The apparatus 900 includes: an obtaining unit 910 and a sending unit 920 . Specifically, the apparatus 900 is configured to execute each process and step corresponding to the second network element in the foregoing method 300 .

The obtaining unit 910 is configured to: obtain routing information of an API, where the routing information is used to indicate a route for calling the API, and the API is provided by the first open function network element and the second open function network element;

The sending unit 920 is configured to: send the routing information to the border opening function network element, where the routing information is used for the border opening function network element to determine the target opening function network element, the target opening function network element is from It is determined from the first open function network element and the second open function network element.

Optionally, the routing information includes information of the first open function network element and information of the second open function network element, and information of the first service area and information of the second service area corresponding to the API , wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

Optionally, the apparatus is a core function network element, and the apparatus further includes: a first receiving unit configured to receive the information of the first open function network element and the second open function network element from the publishing function network element. element information, and the information of the first service area and the second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, so The API provided by the second open function network element corresponds to the second service area; the apparatus further includes: a processing unit configured to, according to the information of the first open function network element and the second open function network element Meta information, as well as information about the first service area and information about the second service area, generate routing information for the API.

Optionally, the apparatus further includes: a second receiving unit, configured to receive a request message from the border opening function network element before sending the routing information to the border opening function network element, the request message using For requesting the routing information, the request message includes the identification information of the API; the sending unit 920 is specifically configured to: send the routing information to the border opening function network element according to the request message.

It should be understood that the apparatus 900 here is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group of processors, etc.) and memory, merge logic, and/or other suitable components to support the described functions. In an optional example, those skilled in the art can understand that the apparatus 900 may be specifically the second network element in the foregoing embodiment, and the apparatus 900 may be configured to execute various processes and processes corresponding to the second network element in the foregoing method embodiments. /or steps, in order to avoid repetition, details are not repeated here.

The apparatuses 800 and 900 of the above solutions have the function of implementing the corresponding steps performed by the first network element or the second network element in the above method; the functions may be implemented by hardware or by executing corresponding software in hardware. The hardware or software includes one or more modules corresponding to the above functions; for example, the sending unit can be replaced by a transmitter, the receiving unit can be replaced by a receiver, and other units, such as the determining unit, can be replaced by a processor, which can be executed separately. Transceiver operations and related processing operations in each method embodiment.

In the embodiments of the present application, the devices in FIG. 8 and FIG. 9 may also be a chip or a system of chips, such as a system on chip (system on chip, SoC). Correspondingly, the receiving unit and the transmitting unit may be the transceiver circuits of the chip, which are not limited herein.

FIG. 10 shows another apparatus 1000 for invoking an application program interface provided by an embodiment of the present application. The apparatus 1000 includes a processor 1010 , a transceiver 1020 and a memory 1030 . The processor 1010, the transceiver 1020 and the memory 1030 communicate with each other through an internal connection path, the memory 1030 is used to store instructions, and the processor 1010 is used to execute the instructions stored in the memory 1030 to control the transceiver 1020 to send signals and / or receive signals.

In a possible implementation manner, the apparatus 1000 is configured to execute each process and step corresponding to the first network element in the foregoing method 200 .

The processor 1010 is configured to: acquire routing information of an API, where the routing information is used to indicate a route for calling the API, the API is provided by the first open function network element and the second open function network element; and obtain Call parameter information of the API, the call parameter information is used to operate the API; according to the routing information and the call parameter information, from the first open function network element and the second open function network element Determine the target open function network element.

In a possible implementation manner, the apparatus 1000 is configured to execute each process and step corresponding to the second network element in the foregoing method 300 .

The processor 1010 is configured to: obtain routing information of an API, where the routing information is used to indicate a route for calling the API, and the API is provided by the first open function network element and the second open function network element; The transceiver 1020 sends the routing information to the border opening function network element, where the routing information is used for the border opening function network element to determine the target opening function network element, and the target opening function network element is obtained from the first network element. The open function network element and the second open function network element are determined.

It should be understood that the apparatus 1000 may be specifically the first network element or the second network element in the foregoing embodiments, and may be configured to perform various steps and/or steps corresponding to the first network element or the second network element in the foregoing method embodiments process. Optionally, the memory 1030 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1010 can be configured to execute the instructions stored in the memory, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is configured to execute the above method corresponding to the first network element or the second network element Various steps and/or processes of an embodiment.

It should be understood that, in this embodiment of the present application, the processor of the above device may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits ( ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software units in the processor. The software unit may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor executes the instructions in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.

In this application, "at least one" means one or more, and "plurality" means two or more. "And/or", which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) of a, b or c may represent: a, b, c, a-b, a-c, b-c or a-b-c, where a, b, c may be single or multiple.

Those of ordinary skill in the art can realize that, in combination with the method steps and units described in the embodiments disclosed herein, they can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the steps and components of the various embodiments have been generally described in terms of functions in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Persons of ordinary skill in the art may use different methods of implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalents within the technical scope disclosed in the present application. Modifications or substitutions shall be covered by the protection scope of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (26)

1. A method of calling an application program interface, API, comprising:

the method comprises the steps that a first network element obtains routing information of an API (application program interface), wherein the routing information is used for indicating a route for calling the API, and the API is provided by a first open function network element and a second open function network element;

the first network element acquires calling parameter information of the API, wherein the calling parameter information is used for operating the API;

and the first network element determines a target open function network element from the first open function network element and the second open function network element according to the routing information and the calling parameter information.

2. The method according to claim 1, wherein the calling parameter information comprises identification information of a terminal device and/or location information of the terminal device; and/or

The routing information includes information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

3. The method according to claim 1 or 2, wherein the first network element is a core function network element, and the obtaining, by the first network element, the calling parameter information of the API includes:

the first network element receives calling parameter information of the API from a boundary open function network element;

the method further comprises the following steps:

and the first network element sends the information of the target open function network element to the boundary open function network element.

4. The method according to any one of claims 1 to 3, wherein the first network element is a core function network element, and the obtaining, by the first network element, the routing information of the API includes:

and the first network element receives the routing information of the API from a network element with a publishing function.

5. The method according to any of claims 1 to 3, wherein the first network element is a core function network element, the method further comprising:

the first network element receives, from a distribution function network element, information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area;

the obtaining, by the first network element, the routing information of the API includes:

and the first network element generates the routing information of the API according to the information of the first open-function network element, the information of the second open-function network element, the information of the first service area and the information of the second service area.

6. The method according to claim 1 or 2, wherein the first network element is a border open function network element, and the obtaining, by the first network element, the routing information of the API includes:

and the first network element receives the routing information of the API from a core function network element or a release function network element.

7. The method of claim 6, further comprising:

and the first network element sends a request message, wherein the request message is used for requesting the routing information of the API, and the request message comprises the identification information of the API.

8. A method of calling an application program interface, API, comprising:

the second network element acquires routing information of an API (application program interface), wherein the routing information is used for indicating a route for calling the API, and the API is provided by a first open function network element and a second open function network element;

the second network element sends the routing information to a border open function network element, where the routing information is used for determining a target open function network element by the border open function network element, and the target open function network element is determined from the first open function network element and the second open function network element.

9. The method of claim 8, wherein the routing information includes information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

10. The method according to claim 8 or 9, wherein the second network element is a core function network element, the method further comprising:

the second network element receives, from a distribution function network element, information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area;

the second network element obtaining the routing information of the API, including:

and the second network element generates the routing information of the API according to the information of the first open-function network element, the information of the second open-function network element, the information of the first service area and the information of the second service area.

11. The method according to any of claims 8 to 10, wherein before the second network element sends the routing information to the border open function network element, the method further comprises:

the second network element receives a request message from the border open function network element, where the request message is used to request the routing information, and the request message includes the identification information of the API;

the sending, by the second network element, the routing information to the border open function network element includes:

and the second network element sends the routing information to the boundary open function network element according to the request message.

12. An apparatus for calling an Application Program Interface (API), comprising:

an obtaining unit, configured to obtain routing information of an API, where the routing information is used to indicate a route for calling the API, and the API is provided by a first open function network element and a second open function network element; acquiring calling parameter information of the API, wherein the calling parameter information is used for operating the API;

and the processing unit is used for determining a target open function network element from the first open function network element and the second open function network element according to the routing information and the calling parameter information.

13. The apparatus according to claim 12, wherein the invoking parameter information comprises identification information of a terminal device and/or location information of the terminal device; and/or

The routing information includes information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

14. The apparatus according to claim 12 or 13, wherein the apparatus is a core function network element, the apparatus further comprising:

a first receiving unit, configured to receive, from a border open function network element, call parameter information of the API;

a first sending unit, configured to send the information of the target open function network element to the border open function network element.

15. The apparatus according to any of claims 12 to 14, wherein the apparatus is a core function network element, the apparatus further comprising:

and the second receiving unit is used for receiving the routing information of the API from the network element with the issuing function.

16. The apparatus according to any of claims 12 to 14, wherein the apparatus is a core function network element, the apparatus further comprising:

a third receiving unit, configured to receive, from a distribution function network element, information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area;

the processing unit is further to:

and generating the routing information of the API according to the information of the first open function network element, the information of the second open function network element, the information of the first service area and the information of the second service area.

17. The apparatus according to claim 12 or 13, wherein the apparatus is a border open function network element, the apparatus further comprising:

a fourth receiving unit, configured to receive, by the first network element, the routing information of the API from a core function network element or a distribution function network element.

18. The apparatus of claim 17, further comprising:

a second sending unit, configured to send a request message, where the request message is used to request routing information of the API, and the request message includes identification information of the API.

19. An apparatus for calling an Application Program Interface (API), comprising:

an obtaining unit, configured to obtain routing information of an API, where the routing information is used to indicate a route for calling the API, and the API is provided by a first open function network element and a second open function network element;

a sending unit, configured to send the routing information to a border open function network element, where the routing information is used for determining, by the border open function network element, a target open function network element, and the target open function network element is determined from the first open function network element and the second open function network element.

20. The apparatus of claim 19, wherein the routing information comprises information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, wherein the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area.

21. The apparatus according to claim 19 or 20, wherein the apparatus is a core function network element, the apparatus further comprising:

a first receiving unit, configured to receive, from a distribution function network element, information of the first open function network element and information of the second open function network element, and information of a first service area and information of a second service area corresponding to the API, where the API provided by the first open function network element corresponds to the first service area, and the API provided by the second open function network element corresponds to the second service area;

the device further comprises:

a processing unit, configured to generate routing information of the API according to the information of the first open-function network element and the information of the second open-function network element, and the information of the first service area and the information of the second service area.

22. The apparatus of any one of claims 19 to 21, further comprising:

a second receiving unit, configured to receive a request message from the border open function network element before sending the routing information to the border open function network element, where the request message is used to request the routing information, and the request message includes identification information of the API;

the sending unit is specifically configured to:

and sending the routing information to the boundary open function network element according to the request message.

23. An apparatus, comprising: a processor coupled with a memory, the memory to store a program that, when executed by the processor, causes the apparatus to perform the apparatus of any of claims 1-1.

24. A computer-readable medium for storing a computer program, characterized in that the computer program comprises instructions for implementing the apparatus of any of the preceding claims 1-11.

25. A computer program product comprising computer program code, which, when run on a computer, causes the computer to implement the apparatus of any of the preceding claims 1-11.

26. A chip, comprising: a processor for reading instructions stored in a memory, which when executed by the processor, cause the chip to implement the apparatus of any of claims 1-11.

Images