Method and apparatus for application programming interface management
By integrating location information into API discovery processes, the API frameworks address the lack of provider location and invoker interface details, optimizing service API discovery and communication efficiency.
Patent Information
- Application Number
- JP2023518296
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-09-30
- Filing Date
- 2021-09-28
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-09-28
AI Technical Summary
Existing API frameworks like CAPIF lack location information of service API providers and API invoker interface information, leading to suboptimal service API discovery when multiple providers offer the same service with similar coverage, hindering efficient selection and communication.
Incorporating location information, such as GPS coordinates and data center identifiers, into API discovery requests and responses to enhance the service API discovery process, ensuring that API invokers can select providers that are geographically or topologically closer, thereby optimizing communication and service delivery.
Enhances the service API discovery process by enabling more granular location-based selection of service providers, improving communication efficiency and optimizing service delivery by selecting topologically closer API providers.
Smart Images

Figure 0007577844000010 
Figure 0007577844000011 
Figure 0007577844000012
Abstract
Description
[Technical field]
[0001] Non-limiting, exemplary embodiments of the present disclosure relate generally to the field of communications technology, and more particularly, to a method and apparatus for application programming interface (API) management. [Background technology]
[0002] This section introduces aspects that may be helpful in improving the understanding of the disclosure. Accordingly, the statements in this section should be read in this light and not understood as admissions about what is in the prior art or what is not in the prior art.
[0003] For example, in a communication network defined by the 3rd Generation Partnership Project (3GPP), there may be multiple APIs, such as northbound service APIs. For example, APIs for the Service Capability Exposure Function (SCEF) function are defined in 3GPP TS23.682 V16.8.0. APIs for the interface between a service provider of a multimedia broadcast and multicast service (MBMS) and a broadcast multicast service center (BM-SC) are defined in 3GPP TR26.981 V16.0.0. 3GPP TS23.222 V17.1.0, the entire disclosure of which is incorporated herein by reference, introduced a Common API Framework (CAPIF) that includes common aspects applicable to all northbound service APIs. CAPIF may enable consistent development of northbound APIs, for example, where the northbound APIs are defined to abstract or expose underlying 3GPP network functions to third-party applications. CAPIF may provide a common framework for northbound APIs with respect to API registration, authentication, discovery, logging, and charging. Apart from northbound APIs, the common aspects defined in CAPIF can also be used for other APIs. Summary of the Invention [Problem to be solved by the invention]
[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. It is understood that this Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be limiting of the scope of the claims.
[0005] There are several problems with existing API frameworks such as CAPIF. The first problem is that existing API frameworks such as CAPIF lack finer-grained API Exposing Function (AEF) location, such as AEF location. In CAPIF, service area information may be used to indicate information of a location where a service API is provided. The service area information may be included in some API-related messages, such as a service API issue request, an onboard API invoker response, a service API acquisition response, a service API update request, a service API discovery request, etc. The service area information may support an application (such as an edge application) of a service API (e.g., provided by an edge application server or an edge enabler server) that is consumed by an application server available in a particular service area of a network, such as an edge data network. When two or more service API providers with the same service area information are available in a network, such as an edge data network, the location of the service API provider (e.g., finer-grained location, such as the location of a site or data center where a server providing the service is hosted) may help a service consumer select a service API provider. For example, a service consumer may select a service API provider in the same location (such as the same site or data center). However, existing API frameworks such as CAPIF do not provide location information for service API providers. For example, existing API-related messages in CAPIF do not support the location of AEFs (such as addresses, Global Positioning System (GPS) coordinates, or data center identifiers where the AEFs providing the service APIs are located).
[0006] The second problem is that there is no API invoker interface information in the service API discovery request. The API invoker interface information, such as the IP (Internet Protocol) address of the API invoker, can help the CCF (CAPIF Core Function) to make a decision in the service API discovery procedure. For example, the API invoker interface information can be used to provide candidate AEFs that are topologically close to the API invoker. However, there is no API invoker interface information in the service API discovery request.
[0007] Therefore, when two or more service API providers provide the same service API and have the same service area information in different locations, there is no way to optimize service API discovery. For example, a first service API provider may be located in a first data center and a second service API provider may be located in a second data center, and the first and second service API providers may provide the same service API and have the same service area information. In this case, when an API invoker is located in one of the two data centers, there is no way to optimize service API discovery in existing API frameworks such as CAPIF.
[0008] To overcome or mitigate at least one of the above-referenced problems or other problems, an improved API management solution would be desirable. [Means for solving the problem]
[0009] According to a first aspect of the disclosure, there is provided a method performed by a first network function. The method includes sending a first service application programming interface (API) discovery request to a second network function. The method further includes receiving a first service API discovery response from the second network function. The first service API discovery response includes location information of at least one API exposing function that provides the discovered service API.
[0010] In one embodiment, the first network function may be an API invoker and the second network function may be a first Common API Framework (CAPIF) core function.
[0011] In one embodiment, if the first service API discovery response includes information about a second CAPIF core function, the method may further include sending a second service API discovery request to the second CAPIF core function. The method may further include receiving a second service API discovery response from the second CAPIF core function. The second service API discovery response includes location information of at least one API publishing function that provides the discovered service API.
[0012] In one embodiment, the method may further include sending an onboard API invoker request to a third CAPIF core function. The method may further include receiving an onboard API invoker response from the third CAPIF core function. The onboard API invoker request and the onboard API invoker response include location information of the at least one API exposing function.
[0013] In one embodiment, the first network function may be a first Common API Framework (CAPIF) core function and the second network function may be a second CAPIF core function.
[0014] In one embodiment, the first service API discovery request may be an interconnect service API discovery request, and the first service API discovery response may be an interconnect service API discovery response.
[0015] In one embodiment, the method may further include receiving a third service API discovery request from the fifth network function. The method may further include processing the third service API discovery request. The method may further include sending a third service API discovery response to the fifth network function. The third service API discovery response may include location information of at least one API exposing function providing the discovered service API.
[0016] In one embodiment, the fifth network function may be an API invoker or a CAPIF core function.
[0017] In one embodiment, processing the third service API discovery request may include determining that a second network function is used to service the third service API discovery request. In response to the determination, the first service API discovery request may be sent to the second network function.
[0018] In one embodiment, the service API discovery request may include API invoker interface information and / or location information of at least one target API exposing function. The location information of the at least one target API exposing function is used to discover at least one first service API, and at least one API exposing function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposing function. The API invoker interface information is used to discover at least one second service API, and at least one API exposing function providing the discovered at least one second service API is topologically close to the API invoker.
[0019] In one embodiment, the API invoker interface information includes an Internet Protocol (IP) address of the API invoker.
[0020] In one embodiment, the location information of the at least one target API exposed function includes at least one of an address, a coordinate, or a data center identifier.
[0021] According to a second aspect of the disclosure, there is provided a method performed by a second network function. The method includes receiving a first service application programming interface (API) discovery request from the first network function. The method further includes processing the first service API discovery request. The method further includes sending a first service API discovery response to the first network function. The first service API discovery response includes location information of at least one API exposing function providing the discovered service API.
[0022] In one embodiment, when the first service API discovery request includes API invoker interface information and / or location information of the at least one target API exposing function, processing the first service API discovery request includes discovering at least one first service API based on the location information of the at least one target API exposing function, where the at least one API exposing function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposing function, and / or discovering at least one second service API based on the API invoker interface information, where the at least one API exposing function providing the discovered at least one second service API is topologically close to the API invoker.
[0023] In one embodiment, processing the first service API discovery request includes determining that a second CAPIF core function is to be used to service the first service API discovery request. The first service API discovery response includes information about the second CAPIF core function.
[0024] In one embodiment, the method further includes receiving an onboard API invoker request from the API invoker. The method further includes processing the onboard API invoker request. The method further includes sending an onboard API invoker response to the API invoker. The onboard API invoker request and the onboard API invoker response include location information of the at least one API exposed function.
[0025] According to a third aspect of the disclosure, there is provided a method performed by a third network function. The method includes sending a service Application Programming Interface (API) publishing request to a fourth network function. The service API publishing request includes location information of the at least one API publishing function. The method further includes receiving a service API publishing response from the fourth network function.
[0026] In one embodiment, the method further includes sending a service API acquisition request to a fourth network function. The method further includes receiving a service API acquisition response from the fourth network function. The service API acquisition response includes location information of the at least one API exposing function.
[0027] In one embodiment, the method further includes sending a service API update request to a fourth network function, the service API update request including location information of the at least one API publishing function, and receiving a service API update response from the fourth network function.
[0028] In one embodiment, the third network function is an API publishing function and the fourth network function is a Common API Framework (CAPIF) core function.
[0029] In one embodiment, the third network function is a first Common API Framework (CAPIF) core function and the fourth network function is a second CAPIF core function.
[0030] In one embodiment, the service API publication request may be an interconnection API publication request, and the service API publication response may be an interconnection API publication response.
[0031] In one embodiment, the method further includes obtaining, from the API publishing function or another CAPIF core function, information regarding the at least one service API shared with the second CAPIF core function, the information regarding the at least one service API including location information of the at least one API publishing function.
[0032] In one embodiment, the location information of the API publishing function is included in the service API information.
[0033] In one embodiment, the location information of the at least one API exposed function includes at least one of an address, a coordinate, or a data center identifier.
[0034] According to a fourth aspect of the disclosure, a method is provided that is performed by a fourth network function. The method includes receiving a service Application Programming Interface (API) publishing request from a third network function. The service API publishing request includes location information of the at least one API publishing function. The method further includes processing the API publishing request. The method further includes sending a service API publishing response to the third network function.
[0035] In one embodiment, the method further includes receiving a service API acquisition request from the third network function. The method further includes processing the service API acquisition request. The method further includes sending a service API acquisition response to the third network function. The service API acquisition response includes location information of the at least one API exposing function.
[0036] In one embodiment, the method further includes receiving a service API update request from a third network function. The service API update request includes location information of the at least one API publishing function. The method further includes processing the service API update request. The method further includes sending a service API update response to the third network function.
[0037] According to a fifth aspect of the disclosure, a first network function is provided. The first network function includes a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The first network function is operative to send a first service Application Programming Interface (API) discovery request to a second network function. The first network function is further operative to receive a first service API discovery response from the second network function. The first service API discovery response includes location information of at least one API exposing function providing the discovered service API.
[0038] According to a sixth aspect of the disclosure, a second network function is provided. The second network function includes a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The second network function is operative to receive a first service Application Programming Interface (API) discovery request from the first network function. The second network function is further operative to process the first API discovery request. The second network function is further operative to send a first service API discovery response to the first network function. The first service API discovery response includes location information of at least one API exposing function providing the discovered service API.
[0039] According to a seventh aspect of the disclosure, a third network function is provided. The third network function includes a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The third network function is operative to send a service Application Programming Interface (API) discovery request to a fourth network function. The service API publishing request includes location information of the at least one API publishing function. The third network function is further operative to receive a service API discovery response from the fourth network function.
[0040] According to an eighth aspect of the disclosure, a fourth network function is provided. The fourth network function includes a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The fourth network function is operative to receive a service Application Programming Interface (API) publishing request from the third network function. The service API publishing request includes location information of the at least one API publishing function. The fourth network function is further operative to process the service API publishing request. The fourth network function is further operative to send a service API publishing response to the third network function.
[0041] In a ninth aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform a method according to any of the first, second, third and fourth aspects.
[0042] In a tenth aspect of the present disclosure, there is provided a computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform a method according to any of the first, second, third and fourth aspects.
[0043] The embodiments herein provide many advantages, a non-exhaustive list of examples of which is given below: Some embodiments herein may add an AEF location and / or an API invoker interface address to a service API discovery request, which can optimize communication between an API invoker and an API publishing function. Some embodiments herein suggest a finer-grained location of a service API provider (e.g., the location of the site or data center where the server providing the service is hosted) to help a service consumer (i.e., an API invoker) select a service API provider. The embodiments herein are not limited to the preferred features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description.
[0044] The above and other aspects, features and advantages of various embodiments of the present disclosure will become more fully apparent from the following detailed description, which refers, by way of example, to the accompanying drawings in which like or equivalent elements are designated with like reference numerals or characters, and in which: The drawings are presented to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale. [Brief description of the drawings]
[0045] [Figure 1a] Schematic diagram of the system architecture of a 4G network. [Figure 1b] Schematic diagram of the system architecture of a 5G network. [Figure 1c] Schematic diagram of system architecture for service exposure of EPC-5GC interworking. [Diagram 2] FIG. 1 illustrates a functional model of CAPIF for supporting third-party API providers, according to one embodiment of the present disclosure. [Diagram 3] FIG. 1 illustrates a high-level functional architecture for CAPIF interconnection with multiple CAPIF provider domains, according to one embodiment of the present disclosure. [Figure 4]FIG. 2 illustrates a high-level functional architecture for CAPIF interconnection within a CAPIF provider domain, according to one embodiment of the present disclosure. [Diagram 5] 1 is a flowchart of a method according to an embodiment of the present disclosure. [Figure 6] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 7] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 8] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 9] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 10] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 11] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 12] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 13] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 14] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 15] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 16] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 17] 4 is a flow chart of a method according to another embodiment of the present disclosure. [Figure 18] 4 is a flowchart of service API publishing according to an embodiment of the present disclosure. [Figure 19] 5 is a flowchart of a service API call according to an embodiment of the present disclosure. [Figure 20] 4 is a flowchart of a service API update according to an embodiment of the present disclosure. [Figure 21] 4 is a flowchart of service API discovery according to an embodiment of the present disclosure. [Figure 22] 4 is a flowchart of interconnection API issuance according to an embodiment of the present disclosure. [Figure 23] 1 is a flowchart of service API discovery involving multiple CCFs according to an embodiment of the present disclosure. [Figure 24] 13 is a flowchart of service API discovery for CAPIF interconnection according to an embodiment of the present disclosure. [Diagram 25] FIG. 1 is a block diagram of an apparatus suitable for some embodiments of the present disclosure. [Figure 26] FIG. 2 is a block diagram of a first network function according to one embodiment of the present disclosure. [Figure 27] FIG. 2 is a block diagram of a second network function according to one embodiment of the present disclosure. [Figure 28] FIG. 4 is a block diagram of a third network function according to one embodiment of the present disclosure. [Figure 29] FIG. 13 is a block diagram of a fourth network function according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0046] The embodiments of the present disclosure will be described in detail below with reference to the drawings. It should be understood that these embodiments are described only for the purpose of enabling those skilled in the art to better understand and therefore practice the present disclosure, rather than implying limitations on the scope of the present disclosure. Throughout this specification, references to features, advantages, or similar language do not imply that all features and advantages that may be realized in the present disclosure should or are in any single embodiment of the present disclosure. Rather, language referring to features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the present disclosure can be combined in any suitable manner in one or more embodiments. A person skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in a particular embodiment that are not present in all embodiments of the present disclosure.
[0047] As used herein, the term "network" refers to a network conforming to any suitable communications standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a wireless technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" may be used interchangeably. Furthermore, communication between two devices in a network may be performed according to any suitable communication protocol, including, but not limited to, communication protocols defined by a standards organization such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and / or other protocols now known or developed in the future.
[0048] The term "Network Function (NF)" refers to any suitable function that may be implemented in a network entity (physical or virtual) of a communication network. For example, a network function may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, such as a cloud infrastructure. For example, a 5G system (5GS) may comprise multiple NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Publishing Function), UPF (User Plane Function), and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Proxy), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function), etc. For example, a 4G system (such as LTE) may include MME (Mobility Management Entity), HSS (Home Subscriber Server), Service Capability Publishing Function (SCEF), etc. In other embodiments, the network functions may include different types of NFs, depending on, for example, the particular network.
[0049] References herein to "one embodiment," "embodiment," "example embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, implementing such feature, structure, or characteristic in connection with other embodiments is presented as being within the knowledge of one of ordinary skill in the art, whether or not explicitly stated.
[0050] As used herein, terms such as "first" and "second" may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.
[0051] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean "A only, B only, or both A and B." The phrase "A and / or B" should be understood to mean "A only, B only, or both A and B."
[0052] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. The singular forms are intended to include the plural forms unless the context clearly indicates otherwise. As used herein, the terms "including," "having," "comprising," and the like specify the presence of stated features, elements, and / or components, but do not exclude the presence of one or more other features, elements, components, and / or combinations thereof.
[0053] Please note that these terms used in this document are only used for ease of description and to distinguish between nodes, devices, or networks, etc. As technology develops, other terms with similar / same meanings may also be used.
[0054] In the following description and claims, unless defined otherwise, all technical and scientific terms used have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0055] It should be noted that some embodiments of the present disclosure are described primarily in relation to cellular networks as defined by 3GPP, which are used as non-limiting examples of specific exemplary network configurations and system deployments. Thus, the description of the exemplary embodiments provided herein specifically references terms directly related thereto. Such terms are used only in the context of the presented non-limiting examples and embodiments, and of course do not limit the present disclosure in any way. Rather, any other system configuration or wireless technology, such as wireless sensor networks, may equally be utilized, so long as the exemplary embodiments described herein are applicable.
[0056] 1a-1c show schematic systems in which some embodiments of the present disclosure may be implemented. For simplicity, the system architectures of FIGS. 1a-1c show only some example elements. In practice, the communication system may further include any additional elements suitable for supporting communication between terminal devices, or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal device's access to and / or use of services provided by or via the communication system.
[0057] FIG. 1a illustrates a schematic diagram of a system architecture in a 4G network, which is the same as FIG. 4.2-1a in 3GPP TS23.682 V16.7.0, the disclosure of which is incorporated herein by reference in its entirety. The system architecture of Figure 1a may include several exemplary elements, such as a Service Capability Server (SCS), an Application Server (AS), an SCEF, an HSS, a UE, a RAN (Radio Access Network), a Serving GPRS (General Packet Radio Service) Support Node (SGSN), an MME, an MSC (Mobile Switching Center), an S-GW (Serving Gateway), a GGSN / P-GW (Gateway GPRS Support Node / Packet Data Network (PDN) Gateway), an MTC-IWF (Machine Type Communications Interworking) Function), a CDF / CGF (Charging Data Function / Charging Gateway Function), an MTC-AAA (Machine Type Communications-Authentication, Authorization and Accounting), an SMS-SC / GMSC / IWMSC (Short Message Service-Service Center / Gateway MSC / Interworking MSC), an IP-SM-GW (Internet Protocol Short Message Gateway), etc. The network elements and interfaces illustrated in Figure 1a may be the same as the corresponding network elements and interfaces described in 3GPP TS23.682 V16.7.0.
[0058] Figure 1b illustrates a system architecture in a 5G network, which is the same as Figure 4.2.3-1 of 3GPP TS23.501 V16.5.1, the disclosure of which is incorporated herein by reference in its entirety. The system architecture in Figure 1b may include several exemplary elements, such as AMF, SMF, AUSF, UDM, PCF, AF, NEF, UPF and NRF, (R)AN, SCP, NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function). The network elements, reference points and interfaces illustrated in Figure 1b may be the same as the corresponding network elements, reference points and interfaces described in 3GPP TS23.501 V16.5.1.
[0059] FIG. 1c shows a schematic system architecture for service exposure of EPC (Evolved Packet Core)-5GC (5G Core Network) interworking, which is the same as FIG. 4.3.5.1-1 of 3GPP TS 23.501 V16.5.1. For example, if a UE can move between EPS (Evolved Packet Core System) and 5GS (5G System), the network (such as EPC or 5GC) is expected to associate the UE with a combination of SCEF and NEF (also called SCEF+NEF node) for service capability exposure. The system architecture of FIG. 1c may include several exemplary elements, such as AF / AS, SCEF+NEF, EPC node, NF, etc. The network elements and interfaces shown in FIG. 1c may be the same as the corresponding network elements and interfaces described in 3GPP TS 23.501 V16.5.1.
[0060] An exposing functional entity, such as a SCEF, NEF, or SCEF+NEF, may provide a means to securely expose services and capabilities offered by various network interfaces. The exposing functional entity may provide a means to discover exposed services and capabilities. The exposing functional entity may provide access to network capabilities through a network application programming interface (e.g., a network API (Application Programming Interface)). The exposing functional entity may abstract services from the underlying network interfaces and protocols.
[0061] 3GPP has several northbound API related specifications. To avoid duplication and inconsistency in approaches between different API specifications, 3GPP introduced CAPIF, which contains common aspects applicable to all northbound service APIs. Apart from northbound APIs, the common aspects defined in CAPIF can also be used for other APIs. The common API framework applies to both EPS and 5GS and is independent of the underlying 3GPP access (E-UTRA, NR, etc.).
[0062] The CAPIF functional model may be organized into functional entities that describe the functional architecture that enables an API invoker to access and invoke service APIs. The CAPIF functional model may be adopted by any 3GPP function that provides a service API.
[0063] 2 shows a functional model of a CAPIF for supporting third-party API providers according to an embodiment of the present disclosure, in which an embodiment of the present disclosure may be implemented. FIG. 2 is the same as FIG. 6.2.1-1 of 3GPP TS23.222 V17.1.0.
[0064] 3 illustrates a high-level functional architecture of CAPIF interconnection of multiple CAPIF provider domains according to an embodiment of the present disclosure, in which an embodiment of the present disclosure may be implemented. FIG. 3 is the same as FIG. 6.2.1-1 of 3GPP TS23.222 V17.1.0. The architecture model for CAPIF interconnection illustrated in FIG. 3 may enable an API invoker of a CAPIF provider to utilize service APIs from a third-party CAPIF provider.
[0065] 4 illustrates a high-level functional architecture of CAPIF interconnection within a CAPIF provider domain according to an embodiment of the present disclosure, in which an embodiment of the present disclosure may be implemented. FIG. 4 is the same as FIG. 6.2.2-2 of 3GPP TS23.222 V17.1.0. The architecture model of CAPIF interconnection within the same CAPIF provider domain allows an API invoker of CAPIF Core Function 1 to utilize a service API from CAPIF Core Function 2, where both CAPIF Core Function 1 and CAPIF Core Function 2 are hosted within the trust domain of CAPIF Provider A.
[0066] The functional model, functional entities and reference points shown in Figures 2 to 4 are described in Section 6 of 3GPP TS 23.222 V17.1.0. In other embodiments, any other suitable functional model of CAPIF may be present. Application of the functional model for deployment is described in Section 7 of 3GPP TS 23.222 V17.1.0.
[0067] Some terms used herein are defined in 3GPP TS23.222 V17.1.0.
[0068] API: How an API invoker can access a service API invoker: the entity that invokes a CAPIF or service API API Invoker Profile: A set of information associated with an API Invoker that enables the API Invoker to utilize CAPIF APIs and Service APIs.
[0069] API Exposing Function: An entity that provides a service communication entry point for a service API.
[0070] APIF Administrator: An authorized user with special privileges for the operation of CAPIF. Common API Framework: A framework consisting of common API aspects required to support a service API.
[0071] Designated CAPIF Core Function: A CAPIF Core Function that is configured as the Serving CAPIF Core Function for an Interconnection.
[0072] Northbound API: Service API exposed to upper layer API invokers Onboarding: A one-time registration process that enables an API invoker to subsequently access CAPIF and Service APIs.
[0073] Resource: The object or component of the API on which operations are performed.
[0074] Service API: An interface by which components of a system expose their services to API invokers, by abstracting the services from the underlying mechanisms.
[0075] Service area information: Location information where the service API is provided.
[0076] PLMN: (Public Land Mobile Network) Trust Domain: An entity protected by appropriate security and controlled by the PLMN operator or a trusted third party of the PLMN.
[0077] Third-Party Trust Domain: An entity that is protected by appropriate security and controlled by a third party.
[0078] 5 is a flow chart of a method according to one embodiment of the present disclosure, which may be performed in an apparatus implemented in, or at, or communicatively connected to the first network function. Thus, the apparatus may provide means or modules for accomplishing various parts of the method 500 and means or modules for accomplishing other processes together with other components. The first network function may be any suitable network function, such as an API invoker or a CAPIF core function as described in 3GPP TS23.222 V17.1.0.
[0079] At block 502, a first network function may send a first service API discovery request to a second network function. The second network function may be any suitable network function, such as a CAPIF core function as described in 3GPP TS23.222 V17.1.0.
[0080] The first service API discovery request may include any suitable information. For example, the first service API discovery request may include first network function identification information and query information. The query information may include criteria for discovering a matching service API (e.g., service API type, service area information (optional), interface, protocol).
[0081] In one embodiment, the first service API discovery request may be a service API discovery request as described in 3GPP TS23.222 V17.1.0. In another embodiment, the first service API discovery request may be an interconnection service API discovery request as described in 3GPP TS23.222 V17.1.0.
[0082] In one embodiment, a service API discovery request (e.g., a first service API discovery request and / or a second service API discovery request described below) may include API invoker interface information and / or location information of at least one target API exposing function. The API invoker interface information and / or location information of the at least one target API exposing function may be used as query information to discover at least one matching service API. The matching service API may be an exact match service API or a fuzzy matching service API. For example, some matching service APIs may be exact match service APIs and some matching service APIs may be fuzzy matching service APIs. The location information of the at least one target API exposing function is used to discover at least one first service API, and at least one API exposing function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposing function. The API invoker interface information is used to discover at least one second service API, and at least one API exposing function providing the discovered at least one second service API is topologically close (or closest) to the API invoker.
[0083] The API invoker interface information may include any suitable interface information capable of identifying a location of the API invoker. For example, the API invoker interface information may be an interface network address, such as an Internet Protocol (IP) address, an interface network coordinate, etc. In one embodiment, the API invoker interface information may include an IP address of the API invoker. For example, the IP address of the API invoker may be one that is used to trigger a service API call.
[0084] The location information of the at least one target API exposure function may be any suitable location information capable of identifying the location of the at least one target API exposure function, such as a geographic location, a topological location, etc. In one embodiment, the location information of the at least one target API exposure function may include at least one of an address, a coordinate, or a data center identifier. The coordinate may be the coordinate of any suitable positioning system, such as a GPS (Global Positioning System), a BDS (BeiDou Navigation Satellite System), etc.
[0085] In one embodiment, the geographic location of the discovered API publishing function providing the at least one first service API may be the same as the geographic location of the at least one target API publishing function. In one embodiment, a difference between the geographic location of the discovered API publishing function providing the at least one first service API and the geographic location of the at least one target API publishing function may be within a predefined threshold. In one embodiment, the discovered at least one API publishing function providing the at least one first service API is geographically closest to the geographic location of the at least one target API publishing function.
[0086] In one embodiment, a topological location of the discovered API exposing function providing the at least one first service API may be the same as a topological location of the at least one target API exposing function. In one embodiment, a difference between a topological location of the discovered API exposing function providing the at least one first service API and a topological location of the at least one target API exposing function may be within a predefined threshold. In one embodiment, the discovered at least one API exposing function providing the at least one first service API is topologically closest to a topological location of the at least one target API exposing function.
[0087] The API invoker interface information and the location information of the at least one target API exposing function may be used together to discover at least one service API. Additionally, the API invoker interface information and / or the location information of the at least one target API exposing function may be used together with any other query information of the service API discovery request to discover at least one service API.
[0088] At block 504, the first network function may receive a first service API discovery response from the second network function. The first service API discovery response may include a list of service API information for which the API invoker has the required authorization. The first service API discovery response may further include location information of at least one API publishing function providing the discovered service API. The location information of the at least one API publishing function providing the discovered service API may be any suitable location information, such as a geographic location, a topological location, etc. In one embodiment, the location information of the at least one API publishing function providing the discovered service API may include at least one of API publishing function interface information, an address, a coordinate, or a data center identifier. For example, upon receiving the first service API discovery request, the second network function, such as a CAPIF core function, may obtain stored service API information from a CAPIF core function (API registry) according to the inquiry information of the first service API discovery request. Furthermore, the second network function, such as a CAPIF core function, applies a discovery policy and performs filtering of the service API information obtained from the CAPIF core function. The stored service API information may include location information of the API publishing function providing the service API.
[0089] In one embodiment, the first service API discovery response is a service API discovery response as described in 3GPP TS23.222 V17.1.0, but may further include location information of at least one API exposing function providing the discovered service API. In another embodiment, the first service API discovery response is an interconnection service API discovery response as described in 3GPP TS23.222 V17.1.0, but may further include location information of at least one API exposing function providing the discovered service API.
[0090] In one embodiment, when the first service API discovery request includes API invoker interface information and / or location information of at least one target API exposing function, the at least one API exposing function providing the discovered at least one first service API may be geographically or topologically close (or closest) to the location information of the at least one target API exposing function, and / or the at least one API exposing function providing the discovered at least one second service API may be topologically close (or closest) to the API invoker.
[0091] In one embodiment, if the first service API discovery request does not include API invoker interface information and location information of the at least one target API exposing function, the first network function may determine a topologically and / or geographically nearby (or closest) one of the at least one API exposing function providing the discovered at least one first service API based on the location information of the at least one API exposing function providing the discovered service API and at least one of the API invoker interface information and the API invoker location information.
[0092] FIG. 6 shows a flowchart of a method 600 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the first network function, or in the first network function, or by an apparatus communicatively connected to the first network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 600 and means or modules for achieving other processes together with other components. For some parts described in the above embodiment, detailed descriptions thereof are omitted here for brevity. In this embodiment, the first network function may be an API invoker, and the second network function may be a first CAPIF Core Function (CCF).
[0093] In block 602, a first network function may send a first service application programming interface (API) discovery request to a second network function. Block 602 is the same as block 502 of FIG.
[0094] At block 604, the first network function may receive a first service API discovery response from the second network function. The first service API discovery response includes information about the second CAPIF core functionality. The first CCF, e.g., CCF-A, validates the API invoker's identifier and retrieves stored service API information and service API categories. The second CCF, e.g., CCF-B's information of service API categories that match the discovery criteria may be returned to the API invoker in the service API discovery response.
[0095] In block 606, the first network function may send a second service API discovery request to the second CAPIF core function. An identifier of the API invoker is included. Query information is also provided. Block 606 is similar to block 502 of FIG. 5.
[0096] In block 608, the first network function may receive a second service API discovery response from the second CAPIF core function. The second service API discovery response may include location information of at least one API publishing function that provides the discovered service API. Block 608 is similar to block 504 of FIG. 5.
[0097] FIG. 7 shows a flowchart of a method 700 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the first network function, or in the first network function, or by an apparatus communicatively connected to the first network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 700 and means or modules for achieving other processes together with other components. For some parts described in the above embodiment, detailed descriptions thereof are omitted here for brevity. In this embodiment, the first network function may be an API invoker, and the second network function may be a first CAPIF Core Function (CCF).
[0098] Method 700 can onboard an API invoker into CAPIF, which allows for a one-time onboarding process to register the API invoker as a recognized user of CAPIF, which can be based on triggering the API invoker via CAPIF-1 or CAPIF-1e, or provisioning.
[0099] At block 702, the first network function may send an onboard API invoker request to the third CAPIF core function. The onboard API invoker request may include location information of at least one API exposing function. The onboard API invoker request may further include any other suitable information, such as information of the API invoker, including registration details required for onboarding, a list of APIs to be registered, etc. In one embodiment, the onboard API invoker request is the same as the onboard API invoker request described in 3GPP TS23.222 V17.1.0, but may further include location information of the at least one API exposing function.
[0100] At block 704, the first network function may receive an on-board API invoker response from the third CAPIF core function. The on-board API invoker response may include location information of the at least one API exposing function. In one embodiment, the on-board API invoker response is an on-board API invoker response as described in 3GPP TS23.222 V17.1.0, but may further include location information of the at least one API exposing function.
[0101] 8 shows a flowchart of a method 800 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the first network function, or in the first network function, or by an apparatus communicatively connected to the first network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 800, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0102] In this embodiment, the first network function may be a first Common API Framework (CAPIF) core function, and the second network function may be a second CAPIF core function.
[0103] In this embodiment, the first service API discovery request may be an interconnection service API discovery request, and the first service API discovery response may be an interconnection service API discovery response.
[0104] The first network function may receive a third service API discovery request from a fifth network function at block 802. In one embodiment, the fifth network function may be an API invoker or a CAPIF core function.
[0105] In block 804, the first network function may process the third service API discovery request. For example, upon receiving the third service API discovery request, the CAPIF core function verifies the identity (through authentication) of the API invoker. The CAPIF core function retrieves the stored service API information from the CAPIF core function (API registry) according to the inquiry information of the service API discovery request. Furthermore, the CAPIF core function applies discovery policies and performs filtering of the service API information obtained from the CAPIF core function.
[0106] In one embodiment, processing the third service API discovery request may include determining that a second network function is used to process (serve) the third service API discovery request. The first service API discovery request is sent to the second network function according to the determination. In this case, blocks 806 and 808 may be performed.
[0107] For example, a first network function, such as CCF-A, validates the API invoker's identifier and retrieves the stored service API information and service API categories. The second network function's information, such as CCF-B, of service API categories that match the discovery criteria can be returned to the API invoker in a service API discovery response.
[0108] Blocks 806 and 808 are the same as blocks 502 and 504 in FIG.
[0109] The first network function may send a third service API discovery response to the fifth network function at block 810. The third service API discovery response includes location information of at least one API publishing function that provides the discovered service API.
[0110] 9 shows a flowchart of a method 900 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the second network function, or in the second network function, or by an apparatus communicatively connected to the second network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 900, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0111] The second network function may receive a first service application programming interface (API) discovery request from the first network function in block 902. For example, the first network function may send the first service API discovery request to the second network function in block 502 of FIG. 5, while the second network function may receive the first service API discovery request.
[0112] In block 904, the second network function may process the first service API discovery request. For example, upon receiving the first service API discovery request, the second network function, such as a CAPIF core function, verifies the identity (via authentication) of the API invoker. The second network function retrieves the stored service API information from the CAPIF core function (API registry) according to the inquiry information of the service API discovery request. Furthermore, the second network function applies a discovery policy and performs filtering of the service API information obtained from the CAPIF core function.
[0113] In one embodiment, when the first service API discovery request includes API invoker interface information and / or location information of the at least one target API exposing function, processing the first service API discovery request includes discovering at least one first service API based on the location information of the at least one target API exposing function, where the at least one API exposing function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposing function, and / or discovering at least one second service API based on the API invoker interface information, where the at least one API exposing function providing the discovered at least one second service API is topologically close to the API invoker.
[0114] In one embodiment, processing the first service API discovery request may include determining that a second CAPIF core function is to be used to process (provide services for) the first service API discovery request, in which case the first service API discovery response sent in block 906 may include information about the second CAPIF core function.
[0115] At block 906, the second network function may send a first service API discovery response to the first network function. The first service API discovery response includes location information of at least one API exposing function that provides the discovered service API.
[0116] In one embodiment, the first network function may be an API invoker and the second network function may be a first Common API Framework (CAPIF) core function.
[0117] 10 shows a flowchart of a method 1000 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the second network function, or in the second network function, or by an apparatus communicatively connected to the second network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1000, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0118] At block 1002, a second network function may receive an on-board API invoker request from an API invoker. For example, the first network function may send an on-board API invoker request to the second network function at block 702 of Figure 7, where the second network function may receive the on-board API invoker request. In one embodiment, the on-board API invoker request may include location information of at least one API exposing function.
[0119] In block 1004, the second network function may process the onboard API invoker request. For example, the second network function, such as a CAPIF core function, may start the onboarding process by verifying whether all information required for onboarding the API invoker is provided and may also start the authorization process. Successful onboarding may result in the provisioning of an API invoker profile that includes the API invoker's identifier. A list of credentials and APIs and API types that the API invoker can access following successful onboarding may be created. Completion of the onboarding process may require an explicit grant by the CAPIF administrator or API management. CAPIF may handle the grant process internally without requiring an explicit grant by the CAPIF administrator. The API invoker profile includes at least the API invoker's identity, the information required for authentication and authorization by CAPIF, and the CAPIF identity.
[0120] At block 1006, the second network function may send an onboard API invoker response to the API invoker. In one embodiment, the onboard API invoker response may include location information of at least one API exposing function. For example, if the API invoker triggers an onboard API invoker request and authorization is granted, the onboard API invoker response may provide a success indication, including information from the provisioned API invoker profile that authenticates the API invoker and enables it to obtain authorization for the service API. As a result of a successful onboarding process, the CAPIFl core function may authenticate and authorize the API invoker.
[0121] 11 shows a flowchart of a method 1100 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in a third network function, or in the third network function, or by an apparatus communicatively connected to the third network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1100, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0122] In block 1102, the third network function may send a service application programming interface (API) publishing request to the fourth network function. The service API publishing request includes location information of at least one API publishing function. The service application programming interface (API) publishing request may be the same as an interconnection API publishing request or a service API publishing request described in 3GPP TS23.222 V17.1.0, but may further include location information of at least one API publishing function.
[0123] In block 1104, the third network function may receive a service API publication response from the fourth network function. The service application programming interface (API) publication response may be the same as an interconnection API publication response or a service API publication response described in 3GPP TS23.222 V17.1.0.
[0124] 12 shows a flowchart of a method 1200 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in, or communicatively connected to, the third network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1100, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0125] In block 1202, the third network function may send a service API acquisition request to the fourth network function. The service API acquisition request may be the same as the service API acquisition request described in 3GPP TS23.222 V17.1.0.
[0126] At block 1204, the third network function may receive a service API acquisition response from the fourth network function. The service API acquisition response may include location information of the at least one API exposing function. The service API acquisition response may be the same as the service API acquisition response described in 3GPP TS23.222 V17.1.0, but may further include location information of the at least one API exposing function.
[0127] 13 shows a flowchart of a method 1300 according to another embodiment of the present disclosure, in which the method 1200 may be performed in an apparatus implemented in the third network function, or in the third network function, or by an apparatus communicatively connected to the third network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1300, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0128] In block 1302, the third network function may send a service API update request to the fourth network function. The service API update request may include location information of at least one API publishing function. The service API update request may be the same as the service API update request described in 3GPP TS23.222 V17.1.0, but may further include location information of at least one API publishing function.
[0129] In block 1304, the third network function may receive a service API update response from the fourth network function. The service API update response may be the same as the service API update response described in 3GPP TS23.222 V17.1.0.
[0130] In one embodiment, the third network function may be an API publishing function and the fourth network function may be a Common API Framework (CAPIF) core function.
[0131] In one embodiment, the third network function may be a first Common API Framework (CAPIF) core function and the fourth network function may be a second CAPIF core function.
[0132] 14 shows a flowchart of a method 1400 according to another embodiment of the present disclosure, in which the method 1200 may be performed in an apparatus implemented in the third network function, or in the third network function, or by an apparatus communicatively connected to the third network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1400, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0133] In this embodiment, the service API publishing request may be an interconnection API publishing request, and the service API publishing response may be an interconnection API publishing response.
[0134] In block 1402, the third network function may obtain, from the API publishing function or another CAPIF core function, information regarding at least one service API shared with the second CAPIF core function, The information regarding the at least one service API includes location information of the at least one API publishing function.
[0135] Based on the sharable information of the service API or the service API category information, the third network function may decide to publish the service API or the service API category information to the fourth network function. At block 1404, the third network function may send an interconnection API publishing request to the fourth network function. The interconnection API publishing request includes location information of the at least one API publishing function.
[0136] The third network function may receive an interconnect API publication response from the fourth network function at block 1406. The interconnect API publication response may indicate a success or failure outcome and may trigger notifications to subscribed API invokers.
[0137] In one embodiment, the location information of the API publishing function may be included in the service API information.
[0138] 15 shows a flowchart of a method 1500 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the fourth network function, or in the fourth network function, or by an apparatus communicatively connected to the fourth network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1500, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0139] At block 1502, the fourth network function may receive a service application programming interface (API) publishing request from the third network function. The service API publishing request includes location information of the at least one API publishing function.
[0140] In block 1504, the fourth network function may process the service API issuance request. For example, upon receiving the service API issuance request, the fourth network function, such as a CAPIF core function, checks whether the third network function, such as an API publishing function, has the authority to issue the service API. If the check is successful, the service API information provided by the API publishing function is stored in the CAPIF core function (API registry). As another example, if the service API issuance request is an interconnection API issuance request, the fourth network function, such as a CCF-B, may store the service API information or service API category provided by the third network function, such as a CCF-A.
[0141] At block 1506, the fourth network function may send a service API publication response to the third network function.
[0142] 16 shows a flowchart of a method 1600 according to another embodiment of the present disclosure, which may be performed in an apparatus implemented in the fourth network function, or in the fourth network function, or by an apparatus communicatively connected to the fourth network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1600, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0143] At block 1602, the fourth network function may receive a service API obtainment request from the third network function.
[0144] In block 1604, the fourth network function may process the service API acquisition request. For example, upon receiving the service API acquisition request, the CAPIF core function checks whether the API issuing function is authorized to obtain the issued service API information. If the check is successful, the corresponding service API information is retrieved from the CAPIF core function (API registry).
[0145] In block 1606, the fourth network function may send a service API acquisition response to the third network function. The service API acquisition response includes location information of the at least one API exposing function.
[0146] 17 shows a flowchart of a method 1700 according to another embodiment of the present disclosure, in which the method 1500 may be performed in an apparatus implemented in the fourth network function, or in the fourth network function, or by an apparatus communicatively connected to the fourth network function. Thus, the apparatus may provide means or modules for achieving various parts of the method 1600, and means or modules for achieving other processes together with other components. For some parts described in the above embodiments, detailed descriptions thereof are omitted here for brevity.
[0147] At block 1702, the fourth network function may receive a service API update request from the third network function. The service API update request includes location information of the at least one API publishing function.
[0148] In block 1704, the fourth network function may process the service API update request. For example, upon receiving the service API update request, the fourth network function, such as a CAPIF core function, checks whether the API publishing function is authorized to update the published service API information. If the check is successful, the service API information provided by the third network function, such as an API publishing function, is updated in the CAPIF core function (API registry).
[0149] At block 1706, the fourth network function may send a service API update response to the third network function.
[0150] FIG. 18 is a flowchart of service API issuance according to an embodiment of the present disclosure.
[0151] In step 1801, the API Publishing Function (APF) sends a service API publishing request to the CAPIF core function with details of the service API. If the service API is shared with other CAPIF core functions, the shareable information and CAPIF provider domain information are included. The service API publishing request may include location information of at least one API Publishing Function (AEF).
[0152] In block 1802, upon receiving the service API issuing request, the CAPIF core function checks whether the API issuing function is authorized to issue the service API. If the check is successful, the service API information provided by the API issuing function is stored in the CAPIF core function (API registry).
[0153] In step 1803, the CAPIF core function provides a service API publication response to the API publishing function indicating the success or failure outcome and triggers notifications to subscribed API invokers.
[0154] FIG. 19 is a flowchart of a service API call according to an embodiment of the present disclosure.
[0155] In step 1901, the API issuing function sends a service API get request to the CAPIF core function along with the service API issuing information reference provided by the CAPIF core function when the service API was issued.
[0156] In step 1902, upon receiving the service API acquisition request, the CAPIF core function checks whether the API issuing function is authorized to obtain the issued service API information. If the check is successful, the corresponding service API information is read from the CAPIF core function (API registry).
[0157] At 1903, the CAPIF core function provides a service API acquisition response including the service API information to the API publishing function. The service API acquisition response may include location information of at least one API publishing function.
[0158] FIG. 20 is a flowchart of a service API update according to an embodiment of the present disclosure.
[0159] In step 2001, the API publishing function sends a service API update request to the CAPIF core function, the service API update request including the service API publishing information reference provided by the CAPIF core function when the service API was published and the new service API information to be updated. The service API update request may include location information of at least one API publishing function.
[0160] In step 2002, upon receiving the service API update request, the CAPIF core function checks whether the API issuing function is authorized to update the issued service API information. If the check is successful, the service API information provided by the API issuing function is updated in the CAPIF core function (API registry).
[0161] At step 2003, the service API update response is provided to the API publishing function to trigger notifications to subscribing API invokers.
[0162] FIG. 21 is a flowchart of service API discovery according to an embodiment of the present disclosure.
[0163] In step 2101, the API invoker sends a service API discovery request to the CAPIF core function, which includes an API invoker identifier and may include query information, which may further include API invoker interface information and / or location information of at least one target API exposed function.
[0164] In step 2102, upon receiving the service API discovery request, the CAPIF core function verifies the identity (through authentication) of the API invoker. The CAPIF core function retrieves the stored service API information from the CAPIF core function (API registry) according to the inquiry information of the service API discovery request. Furthermore, the CAPIF core function applies discovery policies and performs filtering of the service API information obtained from the CAPIF core function. For example, the API invoker may include a desired AEF location in the discovery request, and when such a desired AEF location is received at the CCF, the CCF may match it with the service API information and return the service API information including the matched AEF location. If the AEF location is not received, the CCF may perform the legacy matching logic of the legacy query parameters described in 3GPP TS23.222 V17.1.0 and return the service API information including the AEF location.
[0165] In step 2103, the CAPIF core function sends a service API discovery response to the API invoker with a list of service API information for which the API invoker has the required permissions. The service API discovery response may include location information of at least one API publishing function that provides the discovered service API.
[0166] FIG. 22 is a flowchart of interconnection API issuance according to an embodiment of the present disclosure.
[0167] In step 2201, CCF-A obtains service APIs to be shared with CCF-B from an API publishing function in the same CAPIF provider domain as CCF-A or from another CCF described in this flowchart. The information about the service APIs includes location information of at least one API publishing function.
[0168] In step 2202, based on the sharable information or service API category information of the service API, CCF-A decides to publish the service API or service API category information to CCF-B. If sharing is allowed, CCF-A sends an interconnection API publishing request to CCF-B, including at least one of the details of the service API and the category information of the service API, together with the identification information of CCF-A, the sharable information and the CAPIF provider domain information. API topology hiding may be enabled. The interconnection API publishing request may include location information of at least one API publishing function.
[0169] In step 2203, CCF-B stores the service API information or service API category provided by CCF-A.
[0170] In step 2204, CCF-B provides an interconnection API issue response to CC-A indicating the success or failure result, triggering notifications to subscribed API invokers.
[0171] FIG. 23 is a flowchart of service API discovery involving multiple CCFs according to an embodiment of the present disclosure.
[0172] In step 2301, the API invoker sends a service API discovery request to the CCF-A, which includes the identification information of the API invoker and may include query information, which may further include API invoker interface information and / or location information of at least one target API exposed function.
[0173] In step 2302, CCF-A validates the API invoker's identifier and retrieves the stored service API information and service API category. The service API category and CCF-B's information that matches the discovery criteria can be returned to the API invoker in a service API discovery response.
[0174] The remaining steps 2303, 2304 and 2305 are only applied if a service API category is included in the interconnection API issuance request, as described in section 8.25.2.1 of 3GPP TS23.222 V17.1.0.
[0175] In step 2303, the API invoker sends a service API discovery request to the CCF-B. The API invoker's identifier is included. Query information (such as API invoker interface information and / or location information of at least one target API exposed function) is also provided.
[0176] In step 2304, upon receiving the service API discovery request, the CCF-B verifies the identifier of the API invoker. The CCF-B retrieves the stored service API information according to the query information of the service API discovery request. Furthermore, the CCF-B applies the discovery policy and performs filtering of the service API information that matches the discovery criteria.
[0177] In step 2305, the CCF-B sends a service API discovery response to the API invoker with a list of service API information for which the API invoker has the required permissions. The service API discovery response may include location information of at least one API publishing function that provides the discovered service API.
[0178] In this embodiment, the API invoker may include the desired AEF location in the discovery request. Following conventional procedures, CCF-A returns the CCF-B address to the API invoker since it has only limited information of the service API. The API invoker repeats the discovery to CCF-B using the desired AEF location. Then, if such a desired AEF location is received at CCF-B, CCF-B may match it with the service API information and return the service API information including the matched AEF location. If the AEF location is not received, CCF-B may execute the legacy matching logic of the legacy query parameters and return the service API information including the AEF location.
[0179] FIG. 24 is a flowchart of service API discovery of CAPIF interconnection according to an embodiment of the present disclosure.
[0180] In step 2401, CCF-A sends an interconnection service API discovery request to CCF-B. The request includes an identifier of CCF-A and query information. As the query information, it may include API invoker interface information and / or location information of at least one target API exposure function. For example, CCF-A may be triggered to perform service API discovery on CCF-B (API invoker service API discovery, periodic service API discovery, etc.).
[0181] In step 2402, when CCF-B receives the interconnection service API discovery request, it verifies the identifier of CCF-A. CCF-B obtains stored service API or CCF information according to the inquiry information of the interconnection service API discovery request. Furthermore, CCF-B applies a discovery policy and performs filtering of the service API or CCF information. A topology hiding policy can be applied to the obtained list of service API information.
[0182] In step 2403, CCF-B sends an interconnection service API discovery response to CCF-A with a list of service API information for which CCF-A has the required permissions or CCF information that matches the discovery criteria. The service API discovery response may include location information of at least one API publishing function that provides the discovered service API.
[0183] In this embodiment, the API invoker may include the desired AEF location in the discovery request. Upon receiving the discovery request, CCF-A may further query CCF-B for the desired AEF location. Then, if such desired AEF location is received at CCF-B, CCF-B may match it with the service API information and return the service API information including the matched AEF location. If the AEF location is not received, CCF-B may execute the legacy matching logic of the legacy query parameters and return the service API information including the AEF location.
[0184] According to various embodiments, the messages shown in Figures 2-24 are the same as the corresponding messages described in 3GPP TS23.222 V17.1.0, except that some messages include location information of at least one API exposed function, and some messages may include API invoker interface information and / or location information of at least one target API exposed function.
[0185] The various blocks / steps illustrated in Figures 2 through 24 may be viewed as method steps and / or as operations resulting from the operation of computer program code and / or as a number of coupled logic circuit elements configured to perform the associated functions. The schematic flow chart diagrams described above are generally illustrated as logical flow chart diagrams. As such, the illustrated order and labeled steps are indicative of particular embodiments of the presented method. Other steps and methods may be conceived that are equivalent in function, logic or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the order in which a particular method occurs may or may not strictly follow the order of the corresponding steps shown.
[0186] The embodiments herein provide many advantages, a non-exhaustive list of examples of which is given below: Some embodiments herein can add AEF location and / or API invoker interface address to the service API discovery request, which can optimize communication between the API invoker and the API publishing function. Some embodiments herein suggest finer-grained location of the service API provider (e.g., the location of the site or data center where the server providing the service is hosted) to help the service consumer (i.e., API invoker) select the service API provider. The embodiments herein are not limited to the preferred features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description.
[0187] 25 is a block diagram of an apparatus suitable for some embodiments of the present disclosure. For example, any one of the first network function, the second network function, the third network function, and the fourth network function described above may be implemented as or via the apparatus 2500.
[0188] The apparatus 2500 comprises at least one processor 2521, such as a digital processor (DP), and at least one memory (MEM) 2522 coupled to the processor 2521. The apparatus 2520 may further comprise a transmitter TX and a receiver RX 2523 coupled to the processor 2521. The MEM 2522 stores a program (PROG) 2524. The PROG 2524 may include instructions that, when executed by the associated processor 2521, enable the apparatus 2520 to operate according to embodiments of the present disclosure. The combination of the at least one processor 2521 and the at least one MEM 2522 may form a processing means 2525 adapted to perform various embodiments of the present disclosure.
[0189] Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processor 2521, software, firmware, hardware, or combinations thereof.
[0190] MEM2522 may be of any type suitable for the local technology environment and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed and removable memory.
[0191] The processor 2521 may be of any type suitable for the local technology environment and may include, by way of non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.
[0192] In an embodiment in which the device is implemented as or in a first network function, memory 2522 includes instructions executable by processor 2521 to cause the first network function to operate according to any of the steps of the methods associated with the first network function described above.
[0193] In an embodiment in which the device is implemented as or in a second network function, memory 2522 includes instructions executable by processor 2521 to cause the second network function to operate according to any of the steps of the methods relating to the second network function described above.
[0194] In an embodiment in which the device is implemented as or in a third network function, memory 2522 includes instructions executable by processor 2521 to cause the third network function to operate according to any of the steps of the methods relating to the third network function described above.
[0195] In an embodiment in which the device is implemented as or in a fourth network function, memory 2522 includes instructions executable by processor 2521 to cause the fourth network function to operate according to any of the steps of the methods associated with the fourth network function described above.
[0196] 26 is a block diagram of a first network function according to an embodiment of the present disclosure. As shown, the first network function 2600 includes a transmitting module 2602 and a receiving module 2604. The transmitting module 2602 may be configured to send a first service application programming interface (API) discovery request to a second network function. The receiving module 2604 may be configured to receive a first service API discovery response from the second network function. The first service API discovery response includes location information of at least one API exposing function that provides the discovered service API.
[0197] 27 is a block diagram of a second network function according to one embodiment of the present disclosure. As shown, the second network function 2700 includes a receiving module 2702, a processing module 2704, and a transmitting module 2706. The receiving module 2702 may be configured to receive a first service application programming interface (API) discovery request from the first network function. The processing module 2704 may be configured to process the first service API discovery request. The transmitting module 2706 may be configured to send a first service API discovery response to the first network function. The first service API discovery response includes location information of at least one API exposing function that provides the discovered service API.
[0198] 28 is a block diagram of a third network function according to an embodiment of the present disclosure. As shown, the third network function 2800 includes a sending module 2802 and a receiving module 2804. The sending module 2802 may be configured to send a service application programming interface (API) publishing request to the fourth network function. The service API publishing request includes location information of at least one API publishing function. The receiving module 2904 may be configured to receive a service API publishing response from the fourth network function.
[0199] 29 is a block diagram of a fourth network function according to one embodiment of the present disclosure. As shown, the fourth network function 2900 includes a receiving module 2902, a processing module 2904, and a sending module 2906. The receiving module 2902 may be configured to receive a service application programming interface (API) publishing request from the third network function. The service API publishing request includes location information of at least one API publishing function. The processing module 2904 may be configured to process the service API publishing request. The sending module 2906 may be configured to send a service API publishing response to the third network function.
[0200] The term unit has its conventional meaning in the art of electrical, electrical, and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid state and / or discrete devices, computer programs or instructions described herein for performing respective tasks, procedures, computations, output, and / or display functions, etc.
[0201] By using the functional units, the first network function, the second network function, the third network function, and the fourth network function do not require fixed processors or memories, and any computing resource and storage resource can be allocated from the first network function, the second network function, the third network function, and the fourth network function in the communication system. By introducing virtualization technology and network computing technology, the utilization efficiency of network resources and the flexibility of the network can be improved.
[0202] According to one aspect of the present disclosure, there is provided a computer program product comprising instructions tangibly stored on a computer-readable storage medium and that, when executed on at least one processor, cause the at least one processor to perform any of the methods set forth above.
[0203] According to one aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any of the methods set forth above.
[0204] The present disclosure further provides a carrier comprising the above-mentioned computer program, the carrier being one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium, which may be, for example, an optical compact disc, an electronic memory device such as a RAM (random access memory), a ROM (read only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.
[0205] The techniques described herein may be implemented by various means, and an apparatus implementing one or more functions of the corresponding apparatus described in the embodiments may have not only conventional means, but also means for implementing one or more functions of the corresponding apparatus described in the embodiments, which may include separate means for each separate function, or means that may be configured to perform one or more functions. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. In the case of firmware or software, the implementation may be performed by modules (e.g., procedures, functions, etc.) that perform the functions described herein.
[0206] Exemplary embodiments herein have been described above with reference to block diagrams and flowcharts of methods and apparatus. It will be understood that each block of the block diagrams and flowchart diagrams, and combinations of blocks in each of the block diagrams and flowchart diagrams, can be implemented by various means including computer program instructions. These computer program instructions can be loaded into a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, executed on the computer or other programmable data processing apparatus, create means for implementing the function specified in the flowchart block or block.
[0207] Additionally, although acts have been described in a particular order, there is no requirement that they be performed in the particular order shown or in a sequential order, and all described acts may be performed to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the above description includes certain implementation details, they are not intended to limit the scope of the disclosure, and the description of features may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.
[0208] Although this specification contains many specific implementation details, these should not be construed as limitations on the scope of the implementation or claimed subject matter, but rather as descriptions of features specific to particular embodiments of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in a particular combination, and may even be initially claimed as such, one or more features from a claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to subcombinations or variations of the subcombination.
[0209] It will be obvious to those skilled in the art that as technology advances, the concept of the present invention can be implemented in various ways. The above-mentioned embodiments are given to illustrate, not to limit, the present disclosure, and it should be understood that modifications and variations can be resorted to without departing from the spirit and scope of the present disclosure, as easily understood by those skilled in the art. Such modifications and variations are deemed to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.
[0210] In one embodiment, 3GPP TS23.222 V17.1.0 may be modified as follows: 3.1 Definition For the purposes of this document, the terms and definitions found in 3GPP TR21.905[1] and the following apply. Terms defined in the present document take precedence over definitions of the same terms defined in 3GPP TR21.905[1].
[0211] API: The means by which an API invoker can access a service.
[0212] API Invoker: An entity that invokes a CAPIF or service API.
[0213] API Invoker Profile: A set of information associated with an API Invoker that enables the API Invoker to utilize CAPIFAPIs and Service APIs.
[0214] API Exposing Function: An entity that provides a service communication entry point for a service API.
[0215] API publishing function location: Information about the location where the API publishing function that provides the service API is located (address, GPS coordinates, data center ID, etc.).
[0216] CAPIF Administrator: An authorized user with special privileges for CAPIF operations.
[0217] Common API Framework: A framework consisting of common API aspects required to support a service API.
[0218] Designated CAPIF Core Function: A CAPIF Core Function that is configured as the Serving CAPIF Core Function for an Interconnection.
[0219] Northbound API: Service API exposed to upper layer API invokers Onboarding: A one-time registration process that enables an API invoker to subsequently access CAPIF and Service APIs.
[0220] Resource: The object or component of the API on which operations are performed.
[0221] Service API: An interface by which components of a system expose their services to API invokers, by abstracting the services from the underlying mechanisms.
[0222] Service area information: Location information where the service API is provided.
[0223] PLMB Trust Domain: An entity protected by appropriate security and controlled by the PLMN operator or a trusted third party of the PLMN.
[0224] Third-Party Trust Domain: An entity that is protected by appropriate security and controlled by a third party.
[0225] For the purposes of this document, the following terms and definitions are given in 3GPP TS 32.240[6].
[0226] Offline billing Online billing 4.2.2 Request [AR-4.2.2-a] CAPIF provides a mechanism to publish service API information that is used by API invokers to discover and subsequently invoke service APIs. [AR-4.2.2-b] CAPIF provides a mechanism for an API invoker to discover published service API information according to the API invoker's interests, as specified in [AR-4.2.2-a]. [AR-4.2.2-c] CAPIF provides a mechanism to restrict the discovery of exposed service API information by API invokers based on configured policies. [AR-4.2.2-d] CAPIF provides a mechanism to configure policies that restrict the discovery of exposed service API information. [AR-4.2.2-e] CAPIF provides a mechanism to support service area information related to service APIs. [AR-4.2.2-e] CAPIF provides a mechanism to support AEF location relative to the service API. 8.1.2.2 Onboard API Invoker Response Table 8.1.2.2-1 shows the information flow of the On-Board API Invoker response from the CAPIF Core Function to the API Invoker.
[0227] [Table 1]
[0228] 8.3.2.1 Service API issuance request Table 8.3.2.1-1 shows the information flow of a service API issuance request from the API issuing function to the CAPIF core function.
[0229] [Table 2]
[0230] 8.5.2.2 Service API Get Response Table 8.5.2.2-1 shows the information flow of the service API acquisition response from the CAPIF core function to the API issuing function.
[0231] [Table 3]
[0232] 8.6.2.1 Service API Update Request Table 8.6.2.1-1 shows the information flow of the Service API Update request from the API Publishing Function to the CAPIF Core Function.
[0233] [Table 4]
[0234] 8.7.2.1 Service API Discovery Request Table 8.7.2.1-1 shows the information flow of a service API discovery request from an API invoker to a CAPIF core function.
[0235] [Table 5]
[0236] 8.7.2.2 Service API Discovery Response Table 8.7.2.2-1 shows the information flow of the Service API discovery response from the CAPIF Core Function to the API Invoker.
[0237] [Table 6]
[0238] 8.25.2.1 Interconnection API Issuance Request Table 8.25.2.1-1 shows the information flow of an Interconnection API issuance request from a CAPIF core function to a CAPIF core function.
[0239] [Table 7]
[0240] 8.25.2.3 Interconnect Service API Discovery Request Table 8.25.2.3-1 shows the information flow of an Interconnection Service API discovery request from one CAPIF Core Function to another.
[0241] [Table 8]
[0242] 8.25.2.4 Interconnect Service API Discovery Response Table 8.25.2.4-1 shows the information flow of an Interconnection Services API discovery response from one CAPIF Core Function to another.
[0243] [Table 9]
Claims
1. A method (500) performed by a first network function, comprising: Sending 502 a first service application programming interface (API) discovery request to a second network function; receiving (504) a first service API discovery response from the second network function; Including, The method of claim 1, wherein the first service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
2. 2. The method of claim 1 , the first network function is an API invoker; The method, wherein the second network function is a first Common API Framework (CAPIF) core function.
3. 3. The method of claim 2, The first service API discovery response includes information regarding a second CAPIF core function; The method further comprises: sending (606) a second service API discovery request to the second CAPIF core function; receiving (608) a second service API discovery response from the second CAPIF core function; Including, The method of claim 1, wherein the second service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
4. The method according to claim 2 or 3, further comprising: Sending (702) an on-board API invoker request to a third CAPIF core function; receiving (704) an on-board API invoker response from the third CAPIF core function; Including, The method, wherein the on-board API invoker request and the on-board API invoker response include location information indicating a location of at least one API exposed function.
5. 2. The method of claim 1 , the first network function is a first Common API Framework (CAPIF) core function; The method, wherein the second network function is a second CAPIF core function.
6. 6. The method of claim 5, The first service API discovery request is an interconnection service API discovery request; The method, wherein the first service API discovery response is an interconnect service API discovery response.
7. The method according to claim 5 or 6, further comprising: receiving (802) a third service API discovery request from a fifth network function; Processing (804) the third service API discovery request; sending (810) a third service API discovery response to the fifth network function; Including, The method of claim 1, wherein the third service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
8. 8. The method of claim 7, The method, wherein the fifth network function is an API invoker or a CAPIF core function.
9. 9. The method according to claim 7 or 8, Processing the third service API discovery request includes determining that the second network function is to be used to provide a service for the third service API discovery request; In response to the determining, the first service API discovery request is sent to the second network function.
10. 10. The method according to any one of claims 1 to 9, the service API discovery request includes API invoker interface information and / or location information indicating the location of at least one target API exposed function; The location information of the at least one target API exposing function is used to discover at least one first service API; At least one API exposure function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposure function; The API invoker interface information is used to discover at least one second service API; At least one API exposing function providing the discovered at least one second service API is topologically close to the API invoker.
11. 11. The method of claim 10, The method, wherein the API invoker interface information includes an Internet Protocol (IP) address of the API invoker.
12. 12. The method according to claim 10 or 11, 20. The method of claim 1 , wherein the location information of at least one target API exposed function includes at least one of an address, a coordinate, or a data center identifier.
13. A method (900) performed by a second network function, comprising: Receiving 902 a first service application programming interface (API) discovery request from a first network function; Processing (904) the first service API discovery request; sending (906) a first service API discovery response to the first network function; Including, The method of claim 1, wherein the first service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
14. 14. The method of claim 13, When the first service API discovery request includes API invoker interface information and / or location information indicating a location of at least one target API exposed function, processing the first service API discovery request includes: Discovering at least one first service API based on the location information of at least one target API exposure function, wherein at least one API exposure function providing the discovered at least one first service API is geographically or topologically close to the location information of the at least one target API exposure function; and / or The method includes discovering at least one second service API based on the API invoker interface information, wherein at least one API exposing function providing the discovered at least one second service API is topologically close to the API invoker.
15. 15. The method of claim 14, The API invoker interface information includes an Internet Protocol (IP) address of the API invoker; and / or 20. The method of claim 1 , wherein the location information of at least one target API exposed function includes at least one of an address, a coordinate, or a data center identifier.
16. 16. The method according to any one of claims 13 to 15, the first network function is an API invoker; The method, wherein the second network function is a first Common API Framework (CAPIF) core function.
17. 17. The method according to any one of claims 13 to 16, comprising: Processing the first service API discovery request includes determining that a second CAPIF core function is to be used to provide a service for the first service API discovery request; The first service API discovery response includes information about the second CAPIF core functionality.
18. 18. The method of claim 16 or 17, further comprising: receiving (1002) an on-board API invoker request from the API invoker; Processing (1004) the on-board API invoker request; sending 1006 an on-board API invoker response to the API invoker; Including, The method, wherein the on-board API invoker request and the on-board API invoker response include location information indicating a location of at least one API exposed function.
19. A first network function (2500), A processor (2521); A memory (2522) coupled to the processor (2521); Equipped with The memory (2522) includes instructions executable by the processor (2521) such that the first network function (2500) Sending a first service application programming interface (API) discovery request to a second network function; receiving a first service API discovery response from the second network function; It operates as if The first network function, wherein the first service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
20. 20. A first network function according to claim 19, comprising: The first network function further operates to perform a method according to any one of claims 2 to 12.
21. A second network function (2500), A processor (2521); A memory (2522) coupled to the processor (2521); Equipped with The memory (2522) includes instructions executable by the processor (2521) such that the second network function (2500) Receiving a first service application programming interface (API) discovery request from a first network function; Processing the first API discovery request; sending a first service API discovery response to the first network function; It operates as if A second network function, wherein the first service API discovery response includes location information indicating a location of at least one API exposing function that provides the discovered service API.
22. 22. A second network function according to claim 21, comprising: The second network function further operates to perform a method according to any one of claims 14 to 18.
Citation Information
Patent Citations
Authorization withdrawing method and device
CN110046001A
Security procedures for common API framework in next generation networks
WO2019194242A1
