# US 2021/0279119 A1 · Method and apparatus for providing network-based northbound application programming interface in a wireless communication system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0279119 A1
- Document ID: US20210279119A1
- Status: Published application
- Kind: A1
- Application number: 17/195,041
- Filed: 2021-03-08
- Published: 2021-09-09
- Earliest claimed: 2017-05-02
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Basavaraj Jayawant PATTAN; Suresh CHITTURI
- Web page: https://patentgrep.com/patent/US20210279119A1

## CPC

- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- H04L 12/1403: {Architecture for metering, charging or billing}
- H04L 12/1482: {involving use of telephony infrastructure for billing for the transport of data, e.g. call detail record [CDR] or intelligent network infrastructure}
- H04L 41/0866: Checking the configuration
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04W 80/12: Application layer protocols, e.g. WAP [Wireless Application Protocol]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A pre-5th-Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4th-Generation (4G) communication system such as Long Term Evolution (LTE). Embodiments herein achieve a method and system for providing a network-based northbound application programming interface. The method includes receiving, by an API provider, a request for invoking one or more service APIs from one or more API invoker clients. The method includes utilizing, by the API provider, a CAPIF core function residing at a first domain to provide the one or more service APIs. The method includes providing, by the API provider, the one or more service APIs to the one or more API invoker clients through the CAPIF core function, wherein the API provider comprises one or more service APIs, an API exposing function, an API publishing function and an API management function.

## Claims

### Claim 1

A method performed by an application programming interface (API) provider in a wireless communication system, the method comprising:
receiving a request for invoking one or more service APIs from one or more API invoker clients;
communicating with a common API framework (CAPIF) core function for performing access control of the one or more service APIs based on the request; and
providing the one or more service APIs to the one or more API invoker clients,
wherein the API provider comprises an API exposing function, an API publishing function and an API management function.

### Claim 2 (depends on 1)

The method of claim 1, wherein the one or more service APIs are discoverable at the CAPIF core function through one of a CAPIF-1 interface and a CAPIF-1e interface to the one or more API invoker clients.

### Claim 3 (depends on 1)

The method of claim 1, wherein the request for the invoking of the one or more service APIs is received through one of a common API framework 2 (CAPIF-2) interface and a CAPIF-2e interface.

### Claim 4 (depends on 1)

The method of claim 1, wherein the API exposing function performs at least one of authentication or authorization of the one or more API invoker clients using the request received through a CAPIF-2 interface and a CAPIF-2e interface from the one or more API invoker clients.

### Claim 5 (depends on 1)

The method of claim 1, wherein the API exposing function associated with a third party domain communicates with the CAPIF core function for performing at least one of data logging, charging, authentication or authorization through a CAPIF-3e interface.

### Claim 6 (depends on 1)

The method of claim 1, wherein the API publishing function associated with a third party domain publishes the one or more service APIs to the CAPIF core function through a CAPIF-4e message.

### Claim 7 (depends on 1)

The method of claim 1, wherein the API management function associated with a third party domain communicates with the CAPIF core function to perform at least one of access monitoring, checking policy configurations or provisioning of an API invoker client through a CAPIF-5e interface.

### Claim 8 (depends on 1)

The method of claim 1, wherein the API exposing function associated with a public land mobile network (PLMN) domain communicates with the CAPIF core function for performing at least one of data logging, charging, authentication or authorization through a CAPIF-3 interface.

### Claim 9 (depends on 1)

The method of claim 1, wherein the API publishing function associated with a PLMN domain publishes the one or more service APIs to the CAPIF core function through a CAPIF-4 message.

### Claim 10 (depends on 1)

The method of claim 1, wherein the API management function associated with a PLMN domain communicates with the CAPIF core function to perform at least one of access monitoring, checking policy configurations or provisioning of an API invoker client through a CAPIF-5 interface.

### Claim 11

An apparatus for an application programming interface (API) provider in a wireless communication system, the apparatus comprising:
a transceiver; and
at least one processor;
wherein the at least one processor is configured to:
receive a request for invoking one or more service APIs from one or more API invoker clients;
communicate with a common API framework (CAPIF) core function for performing access control of the one or more service APIs based on the request; and
provide the one or more service APIs to the one or more API invoker clients,
wherein the API provider comprises an API exposing function, an API publishing function and an API management function.

### Claim 12 (depends on 11)

The method of claim 11, wherein the one or more service APIs are discoverable at the CAPIF core function through one of a CAPIF-1 interface and a CAPIF-1e interface to the one or more API invoker clients.

### Claim 13 (depends on 11)

The apparatus of claim 11, wherein the request for the invoking of the one or more service APIs is received through one of a common API framework 2 (CAPIF-2) interface and a CAPIF-2e interface.

### Claim 14 (depends on 11)

The apparatus of claim 11, wherein the API exposing function performs at least one of authentication or authorization of the one or more API invoker clients using the request received through a CAPIF-2 interface and a CAPIF-2e interface from the one or more API invoker clients.

### Claim 15 (depends on 11)

The apparatus of claim 11, wherein the API exposing function associated with a third party domain communicates with the CAPIF core function for performing at least one of data logging, charging, authentication or authorization through a CAPIF-3e interface.

### Claim 16 (depends on 11)

The apparatus of claim 11, wherein the API publishing function associated with the third party domain publishes the one or more service APIs to the CAPIF core function through a CAPIF-4e message.

### Claim 17 (depends on 11)

The apparatus of claim 11, wherein the API management function associated with a third party domain communicates with the CAPIF core function to perform at least one of access monitoring, checking policy configurations or provisioning of an API invoker client through a CAPIF-5e interface.

### Claim 18 (depends on 11)

The apparatus of claim 11, wherein the API exposing function associated with a public land mobile network (PLMN) domain communicates with the CAPIF core function for performing at least one of data logging, charging, authentication or authorization through a CAPIF-3 interface.

### Claim 19 (depends on 1)

The method of claim 1, wherein the API publishing function associated with a PLMN domain publishes the one or more service APIs to the CAPIF core function through a CAPIF-4 message.

### Claim 20 (depends on 1)

The method of claim 1, wherein the API management function associated with a PLMN domain communicates with the CAPIF core function to perform at least one of access monitoring, checking policy configurations or provisioning of an API invoker client through a CAPIF-5 interface.
