Business Object Update Sequencing via Reconciliation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large software applications with multiple business objects face performance issues due to locking mechanisms that suspend operations until one business object completes its action, and sequencing errors in update transmissions lead to data inconsistencies and errors.
Innovation Solution
A system and method that reconciles business object updates by using reconciliation messages to ensure correct sequencing and handling of disruptions in transmission, allowing for independent processing of updates and maintaining data consistency across application components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If business objects are implemented as collections of logically related functions and data to simplify design, then design complexity is reduced, but system performance deteriorates due to locking mechanisms that suspend operations until one business object completes its action
Solution Approach 1:
The patent segments the business object update process into independent update transmissions, each with its own sequencing number. This allows multiple updates to be processed concurrently rather than requiring sequential locking, thus improving system performance while maintaining the logical grouping of functions and data that simplifies design.
Solution Approach 2:
The patent introduces an intermediary mechanism (the sequencing number and reconciliation process) that mediates between multiple concurrent update transmissions. This intermediary allows the system to handle concurrent operations without requiring locking mechanisms, resolving the contradiction between design simplicity and performance.
2Reliability
If updates are transmitted between application components to maintain data consistency, then data integrity is improved, but sequencing errors occur when updates are received out of order leading to data inconsistencies
Solution Approach 1:
The patent applies preliminary action by assigning sequencing numbers to update transmissions before they are sent. This pre-numbering allows the receiving component to identify and correct out-of-order arrivals, ensuring that updates are applied in the correct sequence even when transmission disruptions occur, thus maintaining both data consistency and sequencing accuracy.
Solution Approach 2:
The patent implements a feedback mechanism where the receiving application component checks the sequencing number of each incoming update against the expected sequence. When discrepancies are detected (out-of-order or duplicate updates), the system requests retransmission or adjusts processing accordingly, ensuring accurate sequencing while maintaining data consistency across distributed components.
3Adaptability or versatility
If multiple updates to a business object are allowed to improve functionality, then system versatility is improved, but data integrity deteriorates when transmission disruptions cause updates to be overwritten or lost
Solution Approach 1:
The patent uses feedback through sequencing number verification to detect when transmission disruptions occur. When an update with an unexpected sequencing number is received (indicating a disruption), the system requests retransmission of the correct update rather than applying it, thus maintaining data integrity while allowing multiple updates to be processed.
Solution Approach 2:
The patent applies preliminary anti-action by checking the sequencing number before applying an update. This preliminary check prevents harmful actions (applying incorrect or out-of-order updates) before they can occur, ensuring data integrity is maintained even when multiple updates are transmitted concurrently or experience transmission disruptions.
Data Source
AI summary
A system and method for compensating for disruptions to update transmissions is disclosed. A first application component stores an instance of a business object. The first application component reconciles the instance with data stored on a second application component. The first application component receives a business object update from the second application component. The first application component checks a reconciliation value associated with the business object update. If the first reconciliation value indicates the first business object update was sent after the reconciliation, the first application component applies the business object update to the instance.