Controller Database Architecture for Asynchronous State Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing control systems face inefficiencies in data communication and access, particularly in large-scale distributed systems, where controllers often interrupt each other to retrieve operational parameters, leading to reduced efficiency and cumbersome data access.
Innovation Solution
Implementing a database that facilitates communication between controllers by storing and transmitting holistic state data, allowing controllers to retrieve necessary information without interrupting each other's operations, thereby standardizing data transfer and improving communication efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If controllers directly request and retrieve operational parameters from each other, then data can be accessed, but controller operations are interrupted and system efficiency is reduced
Solution Approach 1:
The patent introduces a database as an intermediary component that stores operational parameters and configuration data. Controllers access data through this database rather than directly requesting from each other, eliminating interruptions to controller operations while maintaining data accessibility. The database serves as a centralized repository that decouples data storage from data access operations.
2Device complexity
If controllers operate independently without centralized data management, then system complexity is reduced, but data communication efficiency deteriorates
Solution Approach 1:
The database acts as a mediator that improves data communication efficiency without significantly increasing system complexity. It provides a standardized interface for data access and enables asynchronous data transfer between controllers, allowing independent controllers to communicate efficiently through a centralized data repository.
Solution Approach 2:
The database pre-stores operational parameters and configuration data that controllers will need, allowing controllers to access data asynchronously without real-time interruptions. Data is prepared and available in advance in the database, eliminating the need for synchronous requests and responses between controllers.
3Reliability
If data is stored in logs or shared databases with traditional access patterns, then data is preserved, but access is limited to the beginning of decision cycles and is slow
Solution Approach 1:
The database stores data in a structured format accessible throughout the control cycle, not just at the beginning. Controllers can retrieve data at any point during their decision-making process, enabling faster access without compromising data reliability or integrity.
Data Source
AI summary
The embodiments described herein include one embodiment that provides a control method that includes connecting a first controller to a control system; receiving control system configuration data from a database, in which the configuration data comprises holistic state data of a second controller in the control system; and configuring operation of the first controller based at least in part on the configuration data received.