CAPIF Node Endpoint Health Checking and Stale Record Cleanup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In 5G telecommunications networks, there is a lack of effective methods for health checking and resource cleanup of service endpoints, leading to issues with unavailable API invokers and service API endpoints being registered indefinitely, which can cause network inefficiencies and congestion.

Innovation Solution

A Common Application Programming Interface (API) Framework (CAPIF) node is configured to receive health check information, including a URI and an acceptable response value, to periodically or aperiodically determine the health status of endpoints, and perform resource cleanup by deleting or compressing stale data records of inactive endpoints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If health check procedures are implemented to monitor endpoint status, then network efficiency is improved by removing inactive endpoints, but system complexity increases due to additional monitoring mechanisms

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a CAPIF node as an intermediary between the NRF and consumer NFs. This mediator performs health check procedures by sending requests to endpoints and evaluating responses, thereby managing endpoint status without requiring complex health monitoring logic in the NRF or consumer NFs themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the CAPIF node periodically sends health check requests to endpoints and evaluates the responses. Based on whether endpoints return acceptable responses within timeout periods, the system dynamically updates endpoint status information in the NRF, enabling automatic removal of inactive endpoints from service registries.

Inventive Principle:
Principle #23Feedback

2Reliability

If endpoint health monitoring is performed periodically, then service reliability is improved by preventing use of inactive endpoints, but energy consumption increases due to continuous monitoring activities

Engineering Contradiction:
Improveservice reliabilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic health check actions where the CAPIF node monitors endpoint status at scheduled intervals rather than continuously. This periodic monitoring approach maintains service reliability by detecting inactive endpoints while reducing energy consumption compared to continuous monitoring. The system can adjust monitoring frequency based on service requirements and endpoint criticality.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11709725B1Methods, systems, and computer readable media for health checking involving common application programming interface framework
Publication Date: 2023.07.25 ORACLE INT CORP
  • US11709725B1 patent drawing
  • US11709725B1 patent drawing
  • US11709725B1 patent drawing

AI summary

Methods, systems, and computer readable media for health checking involving common application programming interface (API) framework (CAPIF) are disclosed. One example method for health checking using CAPIF comprises: at a CAPIF node including at least one processor: receiving, from a sender, a CAPIF request message including health check information usable in checking the health of an endpoint associated with the sender, wherein the health check information includes a uniform resource identifier (URI) associated with the endpoint and an acceptable response value for indicating that the endpoint is active; and determining, periodically or aperiodically, a health status of the endpoint by performing a health check procedure using the URI and the acceptable response value.