CAPIF Authorization Revocation for Resource Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Common API Framework (CAPIF) systems lack efficient mechanisms for revoking API invocation authorization, leading to resource waste when API invocation entities continue to use expired or invalidated authorizations, causing processing resources to be wasted as service logic is executed unnecessarily.
Innovation Solution
An authorization revocation method is introduced where a first entity, such as the Common API Framework Core Function (CCF), receives a revocation request message from an API Exposing Function (AEF), sends a revocation response, and notifies other AEFs to reject API invocations from the affected entity, allowing for timely revocation of API invocation authorization, thereby preventing resource waste.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If API invocation authorization is not revoked timely, then the API invocation entity can continue to invoke APIs using original authorization, but processing resources are wasted when authorization has expired or been invalidated
Solution Approach 1:
The system performs preliminary actions by establishing notification mechanisms before authorization expiration occurs. The CCF sends notifications to AEFs in advance when authorization is about to expire or has been invalidated, enabling AEFs to prepare for and promptly reject subsequent API invocation requests, thus preventing resource waste without causing service disruption.
2Loss of energy
If notification messages are sent to all AEFs upon authorization revocation, then resource waste is prevented across the system, but system complexity and communication overhead increase
Solution Approach 1:
Each AEF independently manages its own authorization validation by receiving notification messages from the CCF. When an AEF receives a notification that an API invocation entity's authorization has been revoked, it autonomously updates its local records and rejects subsequent invocation requests without needing to query other AEFs or the CCF, thereby reducing system-wide communication overhead while preventing resource waste.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
This application discloses an authorization revocation method and an apparatus, and relates to the communications field. The method includes: receiving, by a first entity, an authorization revocation request message from a second entity, where the authorization revocation request message carries an identifier of an API invocation entity; and sending, by the first entity, an authorization revocation response message to the second entity based on the authorization revocation request message. In the method, API invocation authorization management is improved, so that API invocation authorization can be revoked in a timely manner, thereby avoiding resource waste caused by invoking an API by an API invocation entity that already has no API invocation authorization. For example, the API invocation entity invokes the API with original authorization, and an AEF executes service logic for the API invocation, but the API invocation finally fails. Consequently, processing resources of the AEF are wasted. In addition, the AEF is prevented from executing the service logic for the API invocation of the API invocation entity that already has no API invocation authorization, thereby improving working efficiency of a CAPIF system.