Controller Database Interface for Asynchronous Configuration Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 standardizes communication between controllers, allowing them to retrieve necessary data without interrupting each other's operations, and storing holistic state data for self-configuration and diagnostics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If controllers directly request data from each other to obtain operational parameters, then data can be accessed by controllers, but controller operations are interrupted and system efficiency is reduced

Engineering Contradiction:
Improvedata accessVSAvoidcontroller efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent introduces a database as an intermediary component that stores operational parameters and search results. Instead of controllers directly requesting data from each other (which causes interruptions), controllers asynchronously read data from the database. This mediator approach eliminates direct controller-to-controller communication interruptions while ensuring data availability, resolving the contradiction between data access and controller efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If controllers operate independently without standardized communication, then each controller can function autonomously, but data communication becomes cumbersome and inefficient

Engineering Contradiction:
Improvecontroller independenceVSAvoiddata communication architecture
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a universal database interface that all controllers access through standardized methods. The database serves multiple functions: storing operational parameters, storing search results, providing data to multiple controllers simultaneously, and enabling asynchronous access. This universal interface maintains controller independence while simplifying data communication architecture, as controllers don't need individual communication protocols with each other.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of manufacture

If data is only accessed at the beginning of the decision cycle, then data access is simple, but data needed over time cannot be efficiently retrieved

Engineering Contradiction:
Improvedata access simplicityVSAvoiddata retrieval timing
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having controllers read necessary data from the database at the beginning of the control cycle, before the optimization process starts. Operational parameters and search results are pre-loaded into the database during previous cycles, making them immediately available when needed. This eliminates the need for time-consuming data requests during critical control periods, addressing both data access simplicity and retrieval timing needs.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2871585B1Control system database systems and methods
Publication Date: 2023.05.31 ROCKWELL AUTOMATION TECH INC
  • EP2871585B1 patent drawingFigure 1~2
  • EP2871585B1 patent drawingFigure 3~4B
  • EP2871585B1 patent drawingFigure 5~6

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.