Machine-to-Machine Configuration Through Gateway Asset Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity and challenge of managing diverse and dynamic Internet of Things (IoT) systems, particularly in configuring and deploying ad-hoc networks of IoT devices, is hindered by the need for manual device-specific configurations and the lack of portability and scalability of IoT applications.
Innovation Solution
Implementing asset abstraction and automated asset binding within IoT management systems, allowing devices to be configured and managed through abstracted classes or taxonomies, eliminating the need for specific device identifiers and enabling automatic deployment and redeployment of IoT systems with minimal human intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual device-specific configurations are used, then device control precision is improved, but system complexity and deployment time increase
Solution Approach 1:
The patent introduces an intermediary configuration management system that sits between the deployment platform and IoT devices. This intermediary automatically handles device discovery, identification, and configuration by using device identifiers and metadata to bind configuration templates to specific devices, eliminating manual configuration while maintaining precise device control through automated policy application
Solution Approach 2:
The system changes the configuration approach from manual device-specific parameters to automated template-based parameters. Configuration templates define device parameters in a standardized format, and the system automatically binds these templates to devices based on their identifiers and metadata, transforming the configuration process from manual precision to automated parameter application
2Manufacturing precision
If manual configuration processes are used, then configuration accuracy is improved, but deployment time and labor requirements increase
Solution Approach 1:
The patent implements preliminary action by pre-defining configuration templates and policies before device deployment. These templates contain pre-configured device parameters and settings that can be automatically applied to devices upon discovery, eliminating the need for manual configuration during deployment while ensuring accuracy through template validation
Solution Approach 2:
The system enables self-service configuration where devices automatically provide their identifiers and metadata during discovery, and the configuration management system autonomously binds appropriate templates and applies configurations without human intervention. This self-service approach maintains configuration accuracy through automated validation while dramatically reducing deployment time
3Reliability
If device-specific configurations are implemented, then system reliability is improved, but scalability and portability of IoT applications decrease
Solution Approach 1:
The patent applies universality by creating a universal configuration management framework that can handle multiple device types and deployment scenarios through a single system. The framework uses standardized device identifiers and metadata to bind configuration templates to any device, making the system scalable across different IoT applications while maintaining reliability through consistent automated configuration processes
Solution Approach 2:
The system introduces dynamics by making device identification and configuration binding adaptive rather than static. Devices dynamically provide their identifiers and metadata upon discovery, and the system dynamically binds appropriate configuration templates based on this information. This dynamic approach enables scalability across varying device combinations while maintaining reliability through automated adaptation
4Productivity
If automated configuration is implemented, then deployment speed is improved, but configuration management complexity increases
Solution Approach 1:
The patent applies segmentation by dividing configuration management into discrete, manageable components: device discovery, device identification, template binding, and configuration application. Each component is handled as a separate automated step in the deployment pipeline, increasing deployment speed while keeping individual management tasks simple and modular
Data Source
AI summary
A gateway is provided with configuration management logic to identify a set of configurations corresponding to a deployment of a particular application, and automatically send corresponding configuration data to a set of devices in range of the gateway. Service management logic of the gateway determines that assets on the set of devices correspond to one or more asset abstractions defined for the particular application, where the configuration data is sent to the set of devices based on the assets corresponding to the asset abstractions. Sensor data is received during the deployment as generated by a sensor asset of one of the devices, the sensor data is processed according to service logic of the particular application to generate a result, and actuating data is generated and sent during the deployment to an actuator asset on the set of devices based on the result.