API Protocol Standardization for Reliable Multi-Provider Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing APIs for communication between remote computer systems are often verbose and complex, leading to slowed and unreliable data communication due to the need for multiple API calls, which can result in increased failure risks.
Innovation Solution
A system that uses a single API protocol for communication between multiple service provider computer systems, where a user application obtains registry data to map API endpoints with resource types and initiates communication using context values, allowing for efficient and reliable data exchange through HTTP POST or GET requests, with options for asynchronous or synchronous operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a comprehensive API is designed to support all potential functionality requirements, then the API becomes powerful and versatile, but it becomes verbose and complex, slowing down communication and increasing failure risk
Solution Approach 1:
The patent segments the comprehensive API into multiple specialized API instances, each designed for specific communication scenarios. Instead of one monolithic API supporting all functionality, multiple focused APIs handle different service types (data transfer, device control, media streaming), reducing the complexity each instance must manage while maintaining overall system versatility.
Solution Approach 2:
The patent creates a universal API framework where a standardized set of core functions can be applied across multiple specialized API instances. The registry system and standardized data structures enable a single API design pattern to serve multiple communication needs, achieving versatility without requiring each API to be comprehensive.
2Adaptability or versatility
If multiple API calls are performed to achieve desired functionality, then comprehensive functionality is achieved, but communication speed decreases and reliability decreases due to increased failure risk
Solution Approach 1:
The patent merges multiple separate API calls into single consolidated operations where possible. The registry system allows the client to obtain all necessary endpoint information and configuration in one lookup, and the standardized API structures enable complex operations to be performed through single unified calls rather than multiple sequential calls.
Solution Approach 2:
The registry system performs preliminary action by pre-configuring and storing all API endpoint mappings, service descriptions, and communication parameters before actual data exchange occurs. This upfront preparation eliminates the need for multiple exploratory API calls during runtime, improving both speed and reliability.
3Adaptability or versatility
If multiple API calls are performed to achieve desired functionality, then comprehensive functionality is achieved, but communication speed is slowed
Solution Approach 1:
The registry system performs preliminary action by pre-configuring and storing all API endpoint mappings, service descriptions, and communication parameters before actual data exchange occurs. This upfront preparation eliminates the need for multiple exploratory API calls during runtime, improving both speed and reliability.
Solution Approach 2:
The patent segments the comprehensive API into multiple specialized API instances, each designed for specific communication scenarios. Instead of one monolithic API supporting all functionality, multiple focused APIs handle different service types (data transfer, device control, media streaming), reducing the complexity each instance must manage while maintaining overall system versatility.
Data Source
AI summary
Embodiments of the present invention provide a system, comprising a first computer associated with a first service provider, a second computer associated with a second service provider, and a third computer executing a user application, wherein the third computer is arranged to obtain first registry data identifying a first endpoint associated with the first computer and second registry data identifying a second endpoint associated with the second computer; obtain, from the first endpoint, a first service resource indicative of a mapping between one or more API endpoints associated with the first computer and one or more resource types associated with the user application of the third computer, and, from the second endpoint, a second service resource indicative of a mapping between one or more API endpoints associated with the second computer and one or more resource types associated with the user application of the third computer; initiate communication with the first computer via a first API instance according to a predetermined API protocol to exchange data with the first computer in dependence on the first service resource, wherein the third computer provides a context value indicative of an identity of the user application to the first computer; initiate communication with the second computer via a second API instance according to the predetermined API protocol to exchange data with the second computer in dependence on the second service resource, wherein the third computer provides the context value indicative of the identity of the user application to the second computer.