API Invoker Security Method Update for Seamless Invocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods fail to successfully invoke a service API when the security method is updated, leading to a mismatch that prevents the API from being invoked.
Innovation Solution
The proposed method involves updating the security method applied to the API exposing function entity and using the new security method for communication between the API exposing function entity and the invoker, by obtaining the new security method from either the CAPIF core function entity or the API exposing function entity, and sending a first invoking request using the new security method to invoke the service API.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the security method is updated in the CAPIF core function entity and API exposing function entity, then the security level is improved, but the API invoker cannot successfully invoke the service API because it still uses the original security method
Solution Approach 1:
The patent implements a feedback mechanism where the API invoker detects invocation failure, receives notification about the security method update from the CAPIF core function entity, and automatically retrieves and applies the new security method. This closed-loop feedback ensures the invoker adapts to security updates without manual intervention.
Solution Approach 2:
The patent performs preliminary action by having the CAPIF core function entity proactively notify the API invoker about security method updates before the invoker attempts to invoke the service API with the old method. This allows the invoker to update its security method in advance, preventing invocation failures.
2Ease of operation
If the API invoker continuously checks for security method updates, then the API invocation success is maintained, but the system complexity increases
Solution Approach 1:
The patent implements periodic action by having the API invoker check for security method updates at regular intervals or before each service API invocation attempt. This periodic checking mechanism maintains invocation success while keeping the system complexity manageable through structured, scheduled updates rather than continuous monitoring.
Data Source
AI summary
A service application programming interface (API) invoking method where a security method applied to an API exposing function entity is updated from an original security method to a new security method, and where the security method of the API exposing function entity is used for communication between the API exposing function entity and an invoker. The method includes: obtaining, by the invoker, a new security method of the API exposing function entity; and sending, by the invoker, a first invoking request to the API exposing function entity using the new security method, where the first invoking request includes a name of a service API, and where the first invoking request is used to invoke the service API.