Dynamic Time-Delay Adjustment for Reconciliation Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional reconciliation software in computing environments, such as Kubernetes, employs static time delays between successive executions, which reduces flexibility and responsiveness, and limits scalability and portability due to preprogrammed delays that do not adapt to varying failure reasons or framework differences.

Innovation Solution

The introduction of delay-management software (DMS) that dynamically determines time-delay values based on the results of previous executions, selecting algorithms from a group and considering prior time-delay values to inform future decisions, decoupling the reconciliation software from static delay implementation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static time delays are used in reconciliation software, then the system structure is simple and easy to implement, but the flexibility and responsiveness are reduced

Engineering Contradiction:
ImproveflexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the time delay control into two independent parts: (1) reconciliation software that executes state reconciliation tasks, and (2) delay-management software that independently manages time delay values. This segmentation allows the reconciliation software to remain simple while the delay management becomes adaptive and flexible.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces delay-management software as an intermediary component between the reconciliation software and the execution loop. This intermediary dynamically determines time delay values based on previous execution results, providing flexibility without complicating the core reconciliation logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If preprogrammed static delays are used, then the software is easy to deploy, but scalability and portability across different frameworks are limited

Engineering Contradiction:
ImproveportabilityVSAvoidease of deployment
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent extracts the time delay determination logic from the reconciliation software into a separate delay-management software component. This extraction makes the reconciliation software framework-agnostic and portable, while the delay management can be independently configured and deployed.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The delay-management software serves as a universal component that can work with different reconciliation software frameworks (e.g., Kubernetes Ansible Operator framework, Kubernetes Go Operator framework). It provides adaptive delay management functionality that is framework- independent, enhancing portability.

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

3Reliability

If the same time delay is used regardless of failure reasons, then the control logic is simple, but the responsiveness to different failure scenarios is reduced

Engineering Contradiction:
ImproveresponsivenessVSAvoidcontrol logic complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the delay-management software receives information about previous execution results (including failure reasons) and uses this feedback to dynamically adjust time delay values. This allows the system to respond appropriately to different failure scenarios without complex control logic in the reconciliation software itself.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent transforms the static time delay into a dynamic parameter that changes based on execution history and failure reasons. The delay-management software continuously adjusts the time delay values, making the system responsive to different scenarios while keeping the reconciliation logic simple.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11288092B2Dynamically adjusting reconciliation time-delays
Publication Date: 2022.03.29 RED HAT INC
  • US11288092B2 patent drawing
  • US11288092B2 patent drawing
  • US11288092B2 patent drawing

AI summary

Time delays used in a reconciliation process can be dynamically adjusted. For example, a system can receive a request from a client for a time delay value. The time delay value can be a timespan in which to wait between a first execution and a second execution of reconciliation software. The request can indicate a result of the first execution. In response to receiving the request, the system can select an algorithm from among a group of algorithms based on the result of the first execution. The system can then determine the time delay value by executing the algorithm. The system can transmit the time delay value to the client, which can wait for the timespan prior to initiating the second execution of the reconciliation software.