Ledger-Based Software Gateways for Building Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Building management systems face challenges in configuring gateways, leading to resource imbalances and network security issues, with conventional gateways being difficult to set up and prone to failures that disrupt data collection and security.
Innovation Solution
A method using software gateways with a ledger file that manages point assignments across multiple computing systems, allowing for automatic load balancing and failover, and enhancing security through distributed ledger technology to detect and isolate vulnerabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration of gateway points is used, then flexibility in point assignment is improved, but device complexity and ease of operation deteriorate due to difficult setup and resource imbalance
Solution Approach 1:
The system enables self-service through automated point assignment. The ledger server automatically assigns points to gateways based on their capabilities and current load, eliminating manual configuration. The gateway autonomously receives and implements point assignments from the ledger file, and automatically detects and responds to peer gateway failures by reassigning their points.
Solution Approach 2:
The ledger server performs preliminary actions by pre-configuring point assignments in the ledger file before gateways need them. When a gateway joins the network or when points become available (due to gateway failure), the ledger server has already prepared the assignment information, allowing immediate automated allocation without manual intervention.
2Adaptability or versatility
If manual gateway configuration is used, then customization is improved, but reliability deteriorates due to gateway failures causing data collection cessation
Solution Approach 1:
The system implements feedback mechanisms where gateways continuously monitor each other's status by reading peer gateway information from the ledger file. When a gateway failure is detected through this feedback, the system automatically triggers point reassignment to maintain data collection continuity, ensuring reliability while preserving customization capabilities.
Solution Approach 2:
The ledger file serves as a preparatory cushion containing pre-configured point assignment information for all gateways. When a gateway failure occurs, the reassignment process can immediately draw from this pre-prepared information, cushioning against service interruption and maintaining reliability without sacrificing customization flexibility.
3Ease of operation
If centralized gateway management is used, then ease of operation is improved, but security deteriorates due to network security vulnerabilities
Solution Approach 1:
The system segments gateway management by giving each gateway independent ability to read the ledger file and autonomously determine its own point assignments and peer gateway status. This distributed segmentation reduces centralized security vulnerabilities while maintaining operational simplicity, as each gateway operates independently based on shared ledger information.
Solution Approach 2:
The ledger file acts as an intermediary that securely distributes configuration and status information among gateways. Rather than requiring direct peer-to-peer communication or centralized control, the ledger file mediates all gateway interactions, simplifying management while enhancing security through this trusted intermediate data structure.
Data Source
AI summary
A method of software gateways of a building, the method including generating a ledger file including a description of a first software gateway, wherein the ledger file further includes first point assignments for the first software gateway and second point assignments for a second software gateway, wherein a first computing system implements the first software gateway and a second computing system implements the second software gateway and communicating the ledger file to the first software gateway and the second software gateway. The method further including managing, by the first software gateway, first points of the first point assignments based on the ledger file and managing, by the second software gateway, second points of the second point assignments based on the ledger file and determining, by the second software gateway, a status of the first software gateway based on the description of the first software gateway of the ledger file.