IoT Gateway Deployment via Edge Server Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT deployment systems require pre-installing all function nodes on gateways, leading to resource wastage and inefficient updates, as each gateway must be updated individually, and lack a unified interface for data collection and display.
Innovation Solution
A deployment system utilizing a single edge server with a database and agent modules to configure and manage multiple gateways, allowing for the deployment of specific function nodes based on edited flows, reducing the need for pre-installed nodes and enabling centralized management and data collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the entire IoT tool program is pre-installed to every gateway, then all gateways can support all possible IoT functions, but hardware resources of the gateways are wasted
Solution Approach 1:
The patent segments the IoT tool program into multiple independent function node scripts (e.g., modbus node, computation node, transmission node, receiving node, HTTP node). Instead of installing the complete program on each gateway, only the specific function node scripts required by each gateway are deployed. This segmentation allows gateways to run only the necessary functions, reducing resource consumption while maintaining adaptability.
Solution Approach 2:
The patent implements local quality by customizing the software configuration of each gateway according to its specific function requirements. Each gateway receives a tailored set of function node scripts that match its actual usage scenario, rather than a universal complete program. This ensures that each gateway has the exact capabilities it needs without carrying unnecessary software components.
2Manufacturing precision
If each gateway is updated individually, then each gateway can be precisely configured, but a huge time is consumed for updating multiple gateways in a factory
Solution Approach 1:
The patent merges the deployment operations for multiple gateways into a single centralized deployment action. The edge server manages the deployment of function node scripts to multiple gateways simultaneously through a unified interface, allowing administrators to update all gateways in one operation rather than individually. This combining approach maintains precise configuration control while dramatically reducing the time required for fleet-wide updates.
Solution Approach 2:
The edge server acts as an intermediary between the central management system and multiple gateways. It receives deployment instructions and manages the distribution of function node scripts to relevant gateways, automating the update process. This intermediary role enables centralized control and coordination of updates across multiple gateways, eliminating the need for manual individual updates while preserving configuration precision.
3Ease of operation
If a unified interface for data collection and display is implemented, then data monitoring becomes convenient, but system complexity increases
Solution Approach 1:
The edge server serves as an intermediary that consolidates data collection and display functions. Instead of requiring direct connections to multiple gateways, the edge server aggregates data from all gateways and provides a unified interface for data monitoring. This intermediary approach simplifies the user experience while managing the underlying system complexity on the server side.
Solution Approach 2:
The system creates a virtual representation of gateway data through the edge server's unified interface. Rather than requiring users to interact with multiple physical gateway interfaces, the edge server provides a consolidated view that copies and presents data from all gateways in a single location, making monitoring convenient without exposing users to the underlying complexity.
Data Source
AI summary
A deployment system for IoT including an edge server, multiple gateways, and multiple agent modules is disclosed. Each gateway is respectively connected with different peripheral devices to support different function. The edge server includes a flow editor used to edit a flow for a target gateway. The edge server performs a deploying procedure to the target gateway in accordance with the flow, wherein the deploying procedure is to first read a script and a parameter of one or more function nodes included in the flow, then encapsulate the script and the parameter into a packet, and then transmit the packet to the target gateway through one of the agent modules. The target gateway receives the packet through one of the agent modules and sequentially executes the function nodes according to the content of the flow, so as to implement a corresponding IoT function.