Multi-Computer API Stability With Encrypted Provider Logs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for identifying failed application programming interfaces (APIs) in systems with shared computing infrastructure are inefficient, particularly when rapid mitigation is critical, leading to system slowdowns and crashes.
Innovation Solution
Implementing a system that captures and analyzes API call logs, splits them into provider-specific sub-logs, encrypts them with provider-specific keys, and writes them to a blockchain for secure access by providers to facilitate rapid identification and correction of failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual identification of API call failures is used, then system complexity is reduced, but identification speed and productivity deteriorate
Solution Approach 1:
The system performs preliminary actions by automatically capturing, analyzing, and encrypting API call logs in real-time before failures propagate through the system. Call log data is pre-processed and stored in blockchain, enabling immediate failure detection without manual intervention when issues occur.
Solution Approach 2:
The patent introduces an intermediary automated system comprising blockchain technology and encryption mechanisms that mediate between API call operations and failure identification. This intermediary layer automatically processes call logs, encrypts sensitive data, and stores it immutably, eliminating the need for manual log review while maintaining system security.
2Loss of time
If API call logs are manually reviewed to identify failures, then data security requirements are simplified, but mitigation time increases
Solution Approach 1:
Call log data is pre-encrypted using provider-specific encryption keys and stored in blockchain before any failure analysis is needed. This preliminary encryption and immutable storage enable immediate failure identification and mitigation without compromising data security, as the encrypted data is already prepared and securely stored.
Solution Approach 2:
The patent replaces the mechanical process of manual log review with an automated digital system that uses blockchain technology and cryptographic encryption. This substitution eliminates time-consuming manual processes while implementing robust data security measures through automated encryption and immutable storage mechanisms.
3Reliability
If provider-specific encryption is implemented, then data security is improved, but processing complexity increases
Solution Approach 1:
The system segments call log data by provider and applies provider-specific encryption keys to each segment. This segmentation approach enhances security by ensuring that each provider's data is encrypted with their own unique key, while the modular segmentation makes the overall encryption process more manageable and scalable across multiple providers.
Solution Approach 2:
The patent changes the encryption parameter by using different encryption keys for different providers based on their specific requirements. This parameter customization allows each provider to have tailored security levels while maintaining a standardized encryption framework, balancing security needs with processing efficiency.
4Productivity
If automated API failure detection is implemented, then productivity is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal automated detection system that handles multiple providers' API call logs through a single blockchain infrastructure. This multi-functional system can process, encrypt, and store data from various providers simultaneously, improving productivity across the entire ecosystem while avoiding the need for separate manual processes for each provider.
Solution Approach 2:
The automated detection system serves as an intermediary layer between diverse API providers and the failure analysis process. It standardizes data collection, applies appropriate encryption, and stores everything in a unified blockchain structure, enabling efficient automated detection without requiring complex point-to-point integration with each provider's system.
Data Source
AI summary
Arrangements for providing API stability functions are provided. In some aspects, call logs may be received and analyzed to identify a provider associated with each API call. Based on the provider, the call logs may be split into one or more provider-specific sub-logs. The provider-specific sub-logs may be analyzed to identify failed API calls and the sub-logs having failed API calls may be encrypted using a provider-specific encryption key. The encrypted data may be written to a blockchain where the provider may decrypt the data using the provider-specific key and identify and execute one or more corrective actions. Once a cause of the API call failure has been addressed, an indication of the correction may be received and displayed.