API Billing System with Flexible Charging Conditions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing API charging systems lack flexibility in determining charges based on the type of user application, charging the same amount regardless of usage type, which does not meet the demand for varying charging amounts according to the user's application usage.
Innovation Solution
An API charging system that includes an API management device and a charging management device, allowing for flexible charging by receiving and storing charging conditions, acquiring usage history, and determining charge values based on these conditions for each application, enabling different charge values for applications with the same usage history.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the fee for API use is determined according to the number of times of use, then the charging method is simple and easy to implement, but the charging amount cannot be flexibly adjusted according to the type of user application
Solution Approach 1:
The charging system is segmented into multiple independent components: an API management device that handles API requests and responses, a charging management device that calculates fees, a charging condition storage that stores different charging rules, and a history storage that records usage patterns. This segmentation allows each component to perform its specific function independently, enabling flexible charging strategies without overwhelming system complexity.
Solution Approach 2:
The charging management device acts as an intermediary between the API management device and the billing system. It receives usage information from the API management device, applies appropriate charging conditions from the charging condition storage, and determines the final fee. This intermediary layer enables flexible charging without requiring the API management device itself to be complex.
2Adaptability or versatility
If the same fee is charged for all applications with the same usage count, then the charging system is easy to operate, but it does not meet the demand for varying charges based on application type
Solution Approach 1:
Different charging conditions are applied to different applications based on their specific characteristics. The charging condition storage contains multiple charging rules that can be selectively applied to different applications, allowing each application to have its own customized charging strategy while using the same underlying system.
Solution Approach 2:
The system allows charging parameters to be changed based on application type, usage patterns, and business requirements. The charging management device can adjust fee structures, pricing models, and charging conditions without changing the fundamental system architecture, enabling flexible adaptation to different operational scenarios.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
[Problems] An API charging system for flexibly changing a charging amount depending on a user even for the same API is provided. [Means for Solving the Problem(s)] An API management device includes: a reception unit configured to receive selection of a charging condition when using an API from the application; a receiver configured to receive a request for the API from the application; a transmitter configured to transmit a response according to the request to the application; and a history storage configured to store a history of the request for the API and the response for each of the applications that use the API. A charging management device includes: a charging condition storage configured to store the charging condition received by the reception unit for each of the applications that use the API when using the API; an acquisition unit configured to acquire information on the history from the history storage; and a determination unit configured to determine a charge value for the application that uses the API based on the charging condition and the information on the history. The determination unit determines a different charge value according to the charging condition for at least two of the applications that use the API and have the same history.