Intermediation Server API Compatibility Timestamp Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems between multi-function devices and cloud servers face challenges in efficiently managing data communication due to compatibility issues with different APIs, leading to inefficiencies in data transfer and potential errors from timestamp discrepancies.
Innovation Solution
An intermediation server is introduced to prepare and supply demand-creation data with appropriate timing information, enabling multi-function devices to communicate effectively with cloud servers by converting requests into compatible formats for various APIs and managing timestamp validity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If an intermediation server prepares multiple demand-creation data simultaneously, then data transfer efficiency improves, but timestamp errors occur causing communication failures
Solution Approach 1:
The intermediation server performs preliminary actions by preparing demand-creation data sequentially rather than simultaneously. Each demand-creation data is prepared only after the previous one has been successfully transmitted, ensuring that timing information remains valid while maintaining efficient data transfer through continuous processing.
2Measurement precision
If the intermediation server waits for communication completion before preparing next demand-creation data, then timestamp accuracy improves, but data transfer speed decreases
Solution Approach 1:
The intermediation server maintains continuous useful action by preparing the next demand-creation data immediately after the current one is transmitted, rather than waiting for full communication completion. This continuous preparation process ensures timing accuracy is maintained while maximizing data transfer speed through uninterrupted processing.
3Adaptability or versatility
If the system supports multiple APIs with different formats, then compatibility improves, but system complexity increases
Solution Approach 1:
The intermediation server acts as an intermediary between communication devices and cloud servers, handling the complexity of multiple API formats. It receives notifications, converts them into appropriate demand-creation data formats based on the target API requirements, and manages the communication protocol differences, thereby providing compatibility without requiring changes to the endpoint devices.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An intermediation server (50) may receive one notification from a communication device (10). The one notification may include a plurality of identification information for identifying a plurality of target data to be communicated between the communication device (10) and a specific server (100). The intermediation server (50) may prepare a plurality of demand-creation data corresponding to the plurality of target data, and supply the plurality of demand-creation data to the communication device (10). Each of the plurality of demand-creation data may be necessary for the communication device (10) to create one communication demand, and include timing information related to a timing at which the demand-creation data has been prepared. The intermediation server (50) may prepare first demand-creation data, and then prepare second demand-creation data under a condition that the communication device (10) has created a first communication demand by using the first demand-creation data and has sent the first communication demand to the specific server (100).