Edge Orchestrator NAT Mapping for Agile Building Device Onboarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current building management systems (BMS) face challenges in efficiently managing and configuring various computing systems and equipment within a building, particularly in dynamically adapting to new devices and optimizing communication between on-premises and off-premises platforms.
Innovation Solution
The implementation of an edge platform with a software service that facilitates communication between a cloud platform and local building subsystems, utilizing a container network with an edge device manager to identify and manage containers, assign IP addresses, and apply policies, enabling plug-and-play capabilities and auto-configuration of new devices based on digital twin data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If manual configuration methods are used for new devices, then setup accuracy is maintained, but device integration time increases significantly
Solution Approach 1:
The system performs preliminary actions by pre-configuring device templates with default settings and policies before devices are actually deployed. When a new device joins the network, the edge device orchestrator automatically matches it against predefined device templates and applies the pre-configured settings, eliminating the need for manual configuration during deployment.
Solution Approach 2:
The system enables self-service through automated device onboarding where new devices automatically register themselves with the edge device orchestrator. The orchestrator then autonomously performs device identification, IP address assignment, policy application, and integration without requiring manual intervention, allowing devices to configure themselves upon network entry.
2Adaptability or versatility
If static IP address assignment is used, then network stability is maintained, but adaptability to dynamic container networks deteriorates
Solution Approach 1:
The edge device manager continuously monitors the container network for IP address changes and other dynamic conditions. When changes are detected, the system receives feedback about the new state and automatically updates device configurations and network routing tables to maintain stable communication despite the dynamic IP environment.
Solution Approach 2:
The system introduces an intermediary layer (the edge device orchestrator and manager) that sits between the dynamic container network and the application layer. This intermediary handles IP address translation, maintains mapping tables between container identifiers and IP addresses, and manages network routing, thereby shielding applications from IP volatility while maintaining network adaptability.
3Extent of automation
If comprehensive device policies are enforced, then device management control is improved, but system complexity increases
Solution Approach 1:
The system segments device policies into hierarchical categories (device-level, network-level, application-level policies) and applies them at different stages of device onboarding. This segmentation allows complex policy requirements to be broken down into manageable, independently configurable components that can be applied systematically without overwhelming system complexity.
Solution Approach 2:
The edge device orchestrator implements a universal policy engine that handles multiple device types, network configurations, and security requirements through a single unified framework. This multi-functional policy management system can enforce diverse policies across different device categories while maintaining consistent management procedures, reducing overall system complexity despite comprehensive policy enforcement.
Data Source
AI summary
Systems and methods for device agility may include an edge device manager configured to identify a container on a local network, determine a local internet protocol (IP) address for the container, and transmit an identifier of the container to an edge device orchestrator. The edge device manager may receive a network address translation (NAT) address assigned by the edge device orchestrator for the container, and manage, using the identifier, changes to the local IP address for the container on the local network according to the NAT address assigned by the edge device orchestrator.