Coordinator-Governed Environment Model Updates for Shared Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In shared automated environments, coordinating modifications among multiple users and devices to maintain a consistent environment model is challenging due to the need for synchronized updates across various controller devices, while allowing for concurrent modifications and ensuring data integrity.
Innovation Solution
Designating a coordinator device to manage updates to the environment model, allowing other devices to make modifications locally while ensuring they do not propagate until accepted by the coordinator, and enabling devices to roll back changes if rejected, thus maintaining consistency across all users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple users are allowed to modify the environment model concurrently, then user productivity and system adaptability are improved, but data consistency and model integrity deteriorate due to potential conflicts between simultaneous modifications
Solution Approach 1:
The patent introduces a coordinator device as an intermediary between multiple user devices and the environment model. The coordinator receives modification requests from multiple users, processes them sequentially, and manages the updates to maintain consistency. This mediator architecture allows concurrent user interactions while ensuring only one modification is applied at a time, preventing data conflicts and maintaining model integrity.
2Reliability
If a coordinator device is introduced to manage updates, then data consistency is improved, but system complexity increases due to the additional coordination layer
Solution Approach 1:
The patent combines the coordinator functionality with existing controller devices in the environment. Rather than introducing a completely separate coordination system, the coordinator role is integrated into devices that are already part of the automated environment, such as central controllers or gateway devices. This merging approach reduces overall system complexity while still providing the necessary coordination functions.
3Speed
If local modifications are allowed before coordinator approval, then user operation speed is improved, but data integrity risks increase until coordination is complete
Solution Approach 1:
The patent implements a two-phase modification process: first, user devices can prepare and submit modification requests to the coordinator without immediately applying changes; second, the coordinator reviews and approves requests before they are committed to the environment model. This preliminary action phase allows users to initiate changes quickly while maintaining data integrity until the coordinator's approval is obtained.
Solution Approach 2:
The system implements feedback mechanisms where the coordinator communicates with user devices throughout the modification process. The coordinator provides status updates, approval notifications, and conflict resolution information back to the initiating device. This feedback loop ensures that users are informed of the coordination status while maintaining data consistency through controlled update propagation.
Data Source
AI summary
Modifications made by multiple controller devices to an environment model describing a shared automated environment can be coordinated. One of the controller devices can be designated as a coordinator, and any controller device other than the coordinator can send an update request to the coordinator. The coordinator can determine whether to accept or reject the requested modification and can report its determination to the requesting controller device. If the coordinator accepts the request, the coordinator can instigate operations to update the environment model across all controller devices of all users. If the coordinator rejects the request, the environment model is not updated. The controller device that made the request can update its local copy of the environment model and roll back the update if the request is rejected.


