Grid Network Control Application Synchronization via Patch Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current grid network infrastructure management systems face challenges in efficiently updating infrastructure information across control applications, particularly where slave applications need more frequent updates than master applications, leading to increased computational and storage costs and complexity.
Innovation Solution
A system and method for creating and implementing patches in slave applications to update infrastructure information independently of the master application, allowing slave applications to receive and apply updates before the master application is updated, with the ability to visually distinguish patched information and synchronize with the master application later.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If slave applications wait for master application updates before updating infrastructure information, then data consistency is maintained, but update timeliness deteriorates
Solution Approach 1:
The patent segments the update process into two independent parts: master application updates and slave application updates. Slave applications can independently receive and apply infrastructure updates from their respective infrastructure update sources without waiting for master application updates, while still maintaining data consistency through the synchronization mechanism.
Solution Approach 2:
Slave applications perform preliminary updates by receiving and applying infrastructure updates before the master application is updated. This preliminary action allows slave applications to operate with current data, and the synchronization mechanism later ensures consistency when the master application updates.
2Productivity
If slave applications receive frequent infrastructure updates independently, then operational efficiency improves, but system complexity increases
Solution Approach 1:
The patent introduces a synchronization mechanism as an intermediary that manages the relationship between master and slave applications. This mechanism receives infrastructure updates, determines which slave applications should receive them, and coordinates the updates, thereby simplifying the overall system architecture while enabling efficient independent updates.
3Speed
If master application updates are delayed to allow slave applications to update first, then slave application performance improves, but master application update timing deteriorates
Solution Approach 1:
The patent implements a dynamic update mechanism where the timing and sequence of updates are flexible rather than fixed. Slave applications can update at their optimal times based on their operational needs, while the master application updates independently when ready. The synchronization mechanism dynamically coordinates these updates without imposing a rigid sequence, allowing both to operate at optimal speeds.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A non-transitory, computer-readable medium storing instructions is presented. The instructions may cause a control system to receive 72 a proposed update to a grid system. The instructions may also cause the control system to create 74 a patch based on the proposed update to amend infrastructure information relating to the grid system upon receipt of the proposed update. Additionally, the instructions may cause the control system to implement 70 a the patch by storing the amended infrastructure information in memory. Furthermore, the instructions may cause the control system to send 80 a patch update related to the patch to a master application.