Data Transformation Re-Execution for Detailed Exception Status

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing computing environments face challenges in handling exception conditions during compression/decompression operations, particularly due to the limitations of asynchronous execution modes which lack detailed error reporting, leading to incomplete status information and potential operational failures.

Innovation Solution

A bi-modal execution environment is introduced, allowing instructions to be executed both asynchronously and synchronously, where unsatisfactory data transformation operations are re-executed synchronously to obtain detailed status information, ensuring robust error handling and exception reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data transformation operation is performed asynchronously using another processor, then processing throughput is improved, but error status information becomes incomplete

Engineering Contradiction:

Improveprocessing throughputVSAvoiderror status information

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The system dynamically switches between asynchronous and synchronous execution modes based on operation success. Successful operations continue to execute asynchronously for high throughput, while failed operations are re-executed synchronously to capture complete error status information, thus adapting the execution mode to the specific needs of each operation.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements a feedback mechanism where the completion status of asynchronous operations is monitored. When an operation completes unsatisfactorily, the system detects this through polling or interrupt mechanisms and triggers a re-execution in synchronous mode, using the feedback from the asynchronous execution result to determine the appropriate corrective action.

Inventive Principle:

Principle #23Feedback

2Reliability

If data transformation operation is performed synchronously, then error status information is complete, but processing throughput decreases

Engineering Contradiction:

Improveerror status information completenessVSAvoidprocessing throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Instead of executing all operations synchronously, the system applies synchronous execution only partially - specifically to failed operations that require detailed error information. Successful operations are handled asynchronously, thus applying the more resource-intensive synchronous mode only when necessary rather than universally.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system changes the execution mode parameter from asynchronous to synchronous based on the completion status of the operation. This parameter change allows the system to optimize between throughput and information completeness dynamically, switching execution modes according to the specific needs revealed by the initial asynchronous execution result.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If asynchronous execution mode is used, then processing efficiency is maintained, but exception handling capability is reduced

Engineering Contradiction:

Improveprocessing efficiencyVSAvoidexception handling capability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The exception handling process is segmented into two phases: initial asynchronous execution for maintaining processing efficiency, followed by conditional synchronous re-execution for detailed exception analysis. This segmentation allows the system to handle the majority of operations efficiently while providing comprehensive exception handling only when needed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs a preliminary asynchronous execution to determine if an operation succeeded or failed before committing to detailed error handling. This preliminary action allows the system to filter out successful operations that don't require detailed exception information, reserving synchronous re-execution only for cases where exceptions actually occurred.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11314555B2Synchronous re-execution of a data transformation operation to obtain further details regarding an exception

Publication Date: 2022.04.26 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A processor requests that a data transformation operation be performed using another processor, in which the data transformation operation is performed asynchronously. A determination is made that the data transformation operation performed using the other processor has completed unsatisfactorily, and based on the unsatisfactory completion, status relating to performance of the data transformation operation is incomplete. The data transformation operation is then re-executed synchronously using the one processor, and the re-executing provides status information unavailable in performing the data transformation operation asynchronously.