CAPIF Core Function Northbound API Framework for 5G Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 5G communication systems lack a unified, coordinated framework for northbound application programming interfaces (APIs), leading to inefficiencies in integrating third-party services with 3GPP networks, which hinders the integration of vertical industries and wireless networks.

Innovation Solution

A method and system providing a network-based northbound API framework using the CAPIF core function, allowing service APIs to be exposed, published, and managed across domains, enabling API invokers to access and utilize these APIs through standardized interfaces like CAPIF-2 and CAPIF-2e, with authentication, authorization, and access control mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent service APIs are developed without coordination, then each API can be implemented independently, but the system lacks a unified framework for integrating third-party services with 3GPP networks

Engineering Contradiction:
Improveintegration capabilityVSAvoidframework complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The CAPIF core function serves as a universal framework that can accommodate multiple different service APIs (SCEF, xMB, and custom APIs) through a single standardized interface. This allows the system to integrate various third-party services with 3GPP networks using one unified mechanism rather than requiring separate integration approaches for each API type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The CAPIF core function acts as an intermediary layer between API invoker clients and the actual service implementation. It receives API invocation requests from clients, routes them to the appropriate service providers, and manages the interaction flow, thereby simplifying the integration process for both third-party services and 3GPP networks.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a unified API framework is implemented to coordinate all service APIs, then integration of vertical industries and wireless networks is improved, but the system complexity and implementation difficulty increase

Engineering Contradiction:
Improveintegration capabilityVSAvoidimplementation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The framework is segmented into distinct functional components: the CAPIF core function for centralized management, API provider functions for service implementation, and API invoker clients for service consumption. This segmentation allows each component to be developed, deployed, and maintained independently while still working together through standardized interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The CAPIF core function performs preliminary actions by pre-establishing the framework structure, registration mechanisms, and invocation protocols before actual service integration. This preliminary setup simplifies subsequent implementation efforts as new services can be integrated by following the pre-defined framework patterns rather than creating integration logic from scratch.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If service APIs are exposed across multiple domains (PLMN and third-party trust domains), then service accessibility is improved, but authentication and authorization complexity increases

Engineering Contradiction:
Improveservice accessibilityVSAvoidauthentication complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The CAPIF core function serves as an intermediary authentication and authorization mediator between API invoker clients and service providers across different domains. It manages credential verification, access rights validation, and secure communication establishment, thereby providing unified security management that simplifies cross-domain service access while maintaining robust authentication and authorization controls.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10942794B2Method and apparatus for providing network-based northbound application programming interface in a wireless communication system
Publication Date: 2021.03.09 SAMSUNG ELECTRONICS CO LTD
  • US10942794B2 patent drawing
  • US10942794B2 patent drawing
  • US10942794B2 patent drawing

AI summary

The present disclosure relates to 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.