Container-Based Gateway for IoT Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network-connected devices often rely on proprietary communication protocols that limit access and require pre-batching commands, restricting user interaction and flexibility in managing these devices over popular communication networks like the Internet.
Innovation Solution
The use of container instances to establish a communications channel between a network-connected device service and a network-connected device, allowing users to interact with devices over the Internet through a software container instance that can handle proprietary protocols and execute commands dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary communication protocols are used by network-connected devices, then device-specific functionality is maintained, but user access and interaction flexibility are restricted
Solution Approach 1:
A gateway device is introduced as an intermediary between the user's controlling device and the network-connected device using proprietary protocols. The gateway translates standard internet communication protocols into proprietary device protocols, enabling users to access and control devices without being constrained by proprietary protocol limitations. The gateway maintains reliable device-specific communication while providing flexible user access through standard internet protocols.
2Reliability
If commands are pre-batched for execution on network-connected devices, then protocol compatibility is maintained, but user interaction real-time capability is lost
Solution Approach 1:
The gateway acts as a real-time intermediary that receives commands from users over the internet and immediately translates and forwards them to the network-connected device. This eliminates the need for pre-batching commands, as the gateway handles protocol translation on-demand in real-time, maintaining both protocol compatibility and immediate user interaction capability.
Solution Approach 2:
The system transitions from static pre-batched command execution to dynamic real-time command processing. The gateway dynamically adapts protocol translations based on incoming commands, enabling flexible real-time interaction while maintaining compatibility with the device's proprietary protocol requirements.
3Reliability
If proprietary protocols are used for device communication, then device functionality is preserved, but access to devices over popular communication networks is inhibited
Solution Approach 1:
The gateway serves as a protocol translation intermediary that enables access to proprietary protocol devices over standard internet networks. It receives standard internet protocols (HTTP, TCP/IP) from users and translates them into the device's proprietary protocols, preserving device functionality while enabling easy access over popular communication networks like the internet.
Solution Approach 2:
The gateway provides universal access to multiple types of network-connected devices with different proprietary protocols through a single interface. It supports multiple communication protocols simultaneously, allowing users to access diverse devices over the internet using standard protocols while each device maintains its proprietary protocol requirements.
Data Source
AI summary
A network-connected device service receives a request to establish a communications session with a network-connected device. In response to the request, the service transmits a second request to a container service to invoke a software container instance that can be used to establish the communications session with the network-connected device. The network-connected device service receives a notification from the container instance indicating whether the communications session has been established. If so, the service provides an indication to a controlling device that the session has been established. This enables the controlling device to submit commands executable by the network-connected device to the service, which provides the commands to the container instance and, hence, to the network-connected device.