Gateway Protocol Mapping for Resource-Weak Device Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for enabling communication between devices with limited processing and storage capabilities, such as embedded systems, assume the presence of server-like capabilities, which is not feasible due to resource constraints.
Innovation Solution
A method that maps data streams from a low-level data format to a high-level data format using a mapping function on the computer client, allowing the client to display data from resource weak devices, thereby utilizing the client's resources to implement web server-like functionality with minimal storage requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web server functionality is implemented in resource weak devices, then communication capability is improved, but processing and storage resource consumption increases significantly
Solution Approach 1:
A gateway device is introduced as an intermediary between resource weak devices and computer clients. The gateway performs protocol mapping and data format conversion, allowing resource weak devices to communicate without implementing full web server functionality. This mediator handles the complex processing tasks, freeing resources on the embedded devices while enabling HTTP/HTTPS communication capabilities.
Solution Approach 2:
The solution enables resource weak devices to communicate using their native simple protocols without requiring them to serve full HTTP/HTTPS requests. The devices serve themselves by maintaining their resource-efficient architecture while the gateway translates their communications into web-compatible formats, allowing them to 'serve' web functionality without implementing web server software.
2Adaptability or versatility
If protocol mapping is performed on the server side, then communication compatibility is improved, but server processing load increases
Solution Approach 1:
The protocol mapping function is segmented from the main server application and implemented as a separate gateway component. This modular approach allows the gateway to handle protocol conversion independently, distributing the processing load and enabling the mapping functionality to be optimized separately from core server operations. The segmentation also allows caching of mapping rules to reduce real-time processing requirements.
3Adaptability or versatility
If resource weak devices implement full web server functionality, then communication versatility is improved, but device complexity increases
Solution Approach 1:
The gateway device provides universal protocol conversion capabilities, serving multiple resource weak devices with different native protocols through a single multi-functional platform. Rather than each device implementing multiple protocols, the gateway handles protocol translation universally, allowing resource weak devices to maintain simple single-protocol implementations while achieving multi-protocol communication versatility through the gateway's universal mapping capabilities.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A method and a system for providing data from a resource weak device to a computer client (103) connected to the resource weak device, allowing the computer client (103) to receive and send information from and to the resource weak device (101), and a data stream between the resource weak device (101) and the computer client (103) is mapped from a low level data format to a high level data format by a mapping function in the computer client (101), the mapping function comprises static data (206) relating to the resource weak device (101) and the high level data format link to the static data (206), the second high level data format is used for displaying the data from the resource weak device at the computer client.