Search

US-20260127052-A1 - APPLICATION PROGRAMMING INTERFACE (API) ACCESS FOR INTERCONNECTED API FRAMEWORK CORE FUNCTIONS

US20260127052A1US 20260127052 A1US20260127052 A1US 20260127052A1US-20260127052-A1

Abstract

Various aspects of the present disclosure relate to application programming interface (API) access for interconnected API framework core functions (CCFs) for wireless communication. A device implements a first CCF that is interconnected with a second CCF. The device obtains an indication that one or more service APIs are associated with the second CCF and receives a request to onboard an API invoker to access at least one service API of one or more service APIs associated with the first CCF or the service APIs associated with the second CCF. The service APIs associated with the first CCF and the second CCF correspond to respective CCF addresses or respective CCF identifiers (IDs). The device transmits a response to the request that indicates one or more of the respective CCF addresses or the respective CCF IDs corresponding to the service APIs associated with the first CCF and the second CCF.

Inventors

  • Sheeba Backia Mary BASKARAN
  • Andreas Kunz

Assignees

  • LENOVO (UNITED STATES) INC.

Dates

Publication Date
20260507
Application Date
20241101

Claims (20)

  1. 1 . A device to implement a first common application programming interface framework core function (CCF) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the device to: obtain, based at least in part on a connection between the first CCF and a second CCF, an indication that one or more service application programming interfaces (APIs) are associated with the second CCF; receive a request to onboard an API invoker to access at least one service API of one or more service APIs associated with the first CCF or the one or more service APIs associated with the second CCF, wherein the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF correspond to respective CCF addresses or respective CCF identifiers; and transmit a response to the request that indicates one or more of the respective CCF addresses or the respective CCF identifiers corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF.
  2. 2 . The device of claim 1 , wherein the at least one processor is further configured to cause the device to store, at the first CCF, one or more of: the respective CCF addresses or the respective CCF identifiers corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF; one or more additional respective CCF addresses or one or more additional respective CCF identifiers corresponding to one or more application exposure functions (AEFs) associated with the second CCF; service API information corresponding to the one or more service APIs associated with the first CCF; service API information corresponding to the one or more service APIs associated with the second CCF; AEF information corresponding to the AEFs associated with the first CCF; or AEF information corresponding to the AEFs associated with the second CCF.
  3. 3 . The device of claim 1 , wherein to transmit the response to the request, the at least one processor is configured to generate a profile associated with the API invoker, wherein the profile indicates a method for the API invoker to authenticate and authorize one or more application exposure functions (AEFs).
  4. 4 . The device of claim 3 , wherein the one or more AEFs are associated with the second CCF, and wherein the response comprises one or more of AEF information associated with the one or more AEFs, additional respective CCF addresses or additional respective CCF identifiers corresponding to the one or more AEFs, respective security methods corresponding to the one or more AEFs, or additional respective security methods corresponding to the one or more service APIs associated with the second CCF.
  5. 5 . The device of claim 3 , wherein the profile comprises a certificate associated with the API invoker for subsequent authentication procedures with the first CCF and for establishing a connection with the one or more AEFs.
  6. 6 . The device of claim 1 , wherein the response comprises one or more of an identifier assigned to the API invoker by the first CCF, additional respective CCF addresses or additional respective CCF identifiers corresponding to one or more application exposure functions (AEFs) associated with at least one of the first CCF or the second CCF, a root certificate to validate one or more server certificates corresponding to the one or more AEFs, a certificate associated with the API invoker, and an onboard secret associated with the API invoker.
  7. 7 . A device to implement an application programming interface (API) invoker for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the device to: establish a connection between the API invoker and a first common application programming interface framework core function (CCF); transmit a request to onboard the API invoker to access at least one of one or more service APIs associated with the first CCF or one or more service APIs associated with a second CCF, wherein the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF correspond to respective CCF addresses or respective CCF identifiers; and receive a response to the request that indicates one or more of the respective CCF addresses or the respective CCF identifiers corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF.
  8. 8 . The device of claim 7 , wherein the at least one processor is further configured to cause the device to store, at the API invoker, the respective CCF addresses or the respective CCF identifiers corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF.
  9. 9 . The device of claim 7 , wherein the response to the request comprises a profile associated with the API invoker, and wherein the profile indicates a method for the API invoker to authenticate and authorize one or more application exposure functions (AEFs).
  10. 10 . The device of claim 9 , wherein the one or more AEFs are associated with the second CCF, and wherein the response comprises one or more of AEF information associated with the one or more AEFs, additional respective CCF addresses or additional respective CCF identifiers corresponding to the one or more AEFs, respective security methods corresponding to the one or more AEFs, or additional respective security methods corresponding to the one or more service APIs associated with the second CCF.
  11. 11 . The device of claim 9 , wherein the profile comprises a certificate associated with the API invoker for subsequent authentication procedures with the first CCF and for establishing a connection with the one or more AEFs.
  12. 12 . The device of claim 7 , wherein the response comprises one or more of an identifier assigned to the API invoker by the first CCF, additional respective CCF addresses or additional respective CCF identifiers corresponding to one or more application exposure functions (AEFs) associated with at least one of the first CCF or the second CCF, a root certificate to validate one or more server certificates corresponding to the one or more AEFs, a certificate associated with the API invoker, and an onboard secret associated with the API invoker.
  13. 13 . A device to implement a first common application programming interface framework core function (CCF) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the device to: receive, from an application programming interface (API) invoker, first signaling requesting a security method associated with one or more application exposure functions (AEFs) for accessing one or more service APIs, wherein the first signaling comprises one or more of respective CCF addresses corresponding to the one or more AEFs, respective CCF identifiers corresponding to the one or more AEFs, or a uniform resource identifier (URI) associated with the API invoker; transmit, to a second CCF, second signaling requesting respective security methods corresponding to at least a portion of AEFs of the one or more AEFs based at least in part on the respective CCF addresses indicating that the portion of the AEFs is associated with the second CCF; receive, from the second CCF, third signaling that indicates the respective security methods corresponding to the portion of the AEFs and respective security data sharing criterion corresponding to the portion of the AEFs; and transmit, to the API invoker, fourth signaling that indicates the respective security methods corresponding to the portion of the AEFs, the respective security data sharing criterion corresponding to the portion of the AEFs, and the respective CCF addresses or the respective CCF identifiers corresponding to the portion of the AEFs.
  14. 14 . The device of claim 13 , wherein the at least one processor is further configured to: obtain, based at least in part on a connection between the first CCF and the second CCF, the respective CCF addresses or the respective CCF identifiers corresponding to the AEFs and additional respective CCF addresses or additional respective CCF identifiers corresponding to the one or more service APIs; and store, at the first CCF, one or more of: the respective CCF addresses or the respective CCF identifiers corresponding to the one or more AEFs; the additional respective CCF addresses or the additional respective CCF identifiers corresponding to the one or more service APIs; service API information corresponding to the one or more service APIs; and AEF information corresponding to the one or more AEFs.
  15. 15 . The device of claim 13 , wherein the at least one processor is further configured to cause the device to select, based at least in part on security capability information associated with the API invoker, additional respective security methods corresponding to an additional portion of the one or more AEFs associated with the first CCF, wherein the first signaling indicates the security capability information associated with the API invoker, and wherein the fourth signaling indicates the additional respective security methods corresponding to the additional portion of the one or more AEFs, respective security data sharing criterion corresponding to the additional portion of the AEFs, and the respective CCF addresses or the respective CCF identifiers corresponding to the additional portion of the AEFs.
  16. 16 . The device of claim 13 , wherein the at least one processor is further configured to cause the device to: transmit, to the second CCF, fifth signaling that comprises information, wherein the information comprises at least one of an identifier associated with the API invoker, the URI associated with the API invoker, security information to secure respective connections between the API invoker and the portion of the AEFs based at least in part on the respective security methods; and receive, from the second CCF, sixth signaling that indicates the second CCF successfully stores the information.
  17. 17 . The device of claim 13 , wherein the second signaling comprises an identifier associated with the API invoker, an identifier associated with the first CCF, an indication of at least a portion of service APIs associated with the second CCF of the one or more service APIs, one or more access scenarios, the respective CCF addresses or the respective CCF identifiers corresponding to the portion of the AEFs, and one or more security methods.
  18. 18 . A device to implement a first common application programming interface framework core function (CCF) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the device to: receive, from a second CCF, first signaling requesting respective security methods associated with one or more application exposure functions (AEFs) for an application programming interface (API) invoker to access one or more service APIs, wherein respective CCF addresses or respective CCF identifiers corresponding to the one or more AEFs indicate that the one or more AEFs are associated with the first CCF; select, based at least in part on the second CCF being authorized to access the respective security methods, the respective security methods and respective security data sharing criterion corresponding to the AEFs; and transmit, to the second CCF, second signaling that indicates the respective security methods corresponding to the one or more AEFs and the respective security data sharing criterion corresponding to the AEFs.
  19. 19 . The device of claim 18 , wherein the first signaling comprises an identifier associated with the API invoker, an identifier associated with the second CCF, an indication that the one or more service APIs are associated with the first CCF, one or more access scenarios, the respective CCF addresses or the respective CCF identifiers corresponding to the one or more AEFs, and one or more security methods, and wherein the respective security methods are selected from the one or more security methods based at least in part on one or more of the indication of one or more service APIs associated with the first CCF, the one or more access scenarios, or respective capabilities of the one or more AEFs.
  20. 20 . The device of claim 18 , wherein the at least one processor is further configured to cause the device to: receive, from the second CCF, third signaling that comprises information, wherein the information comprises at least one of an identifier associated with the API invoker, a uniform resource identifier (URI) associated with the API invoker, security information to secure respective connections between the API invoker and the one or more AEFs based at least in part on the respective security methods; store, at the first CCF, the information; and transmit, to the second CCF, fourth signaling that indicates the first CCF successfully stores the security information.

Description

TECHNICAL FIELD The present disclosure relates to wireless communications, and more specifically to application programming interface (API) exposure and access. BACKGROUND A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). The wireless communications system may support wireless communications, and may include one or more devices, such as UEs, base stations (e.g., gNBs), network entities, satellites, and/or network equipment (NE), among other devices, that transmit and/or receive signaling. SUMMARY An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements. Some implementations of the method and apparatuses described herein may include a device to implement a first common application programming interface framework core function (CCF) for wireless communication to obtain, based on a connection between the first CCF and a second CCF, an indication that one or more service application programming interfaces (APIs) are associated with the second CCF, receive a request to onboard an API invoker to access at least one service API of one or more service APIs associated with the first CCF or the one or more service APIs associated with the second CCF, where the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF correspond to respective CCF addresses or respective CCF identifiers (IDs), and transmit a response to the request that indicates one or more of the respective CCF addresses or the respective CCF IDs corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF. In some implementations of the method and apparatuses described herein, the device stores, at the first CCF, one or more of the respective CCF addresses or the respective CCF IDs corresponding to the one or more service APIs associated with the first CCF and the one or more service APIs associated with the second CCF, one or more additional respective CCF addresses or one or more additional respective CCF IDs corresponding to one or more application exposure functions (AEFs) associated with the second CCF, service API information corresponding to the one or more service APIs associated with the first CCF, service API information corresponding to the one or more service APIs associated with the second CCF, AEF information corresponding to the AEFs associated with the first CCF, or AEF information corresponding to the AEFs associated with the second CCF. Additionally, or alternatively, to transmit the response to the request, the device generates a profile associated with the API invoker, where the profile indicates a method for the API invoker to authenticate and authorize one or more AEFs. Additionally, or alternatively, the one or more AEFs are associated with the second CCF, and where the response includes one or more of AEF information associated with the one or more AEFs, additional respective CCF addresses or additional respective CCF IDs corresponding to the