Batch UI Calls and Response Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web applications face performance issues and user experience problems when processing large amounts of data in complex technical formats, leading to timeout errors and prolonged wait times due to sequential data processing.

Innovation Solution

Implementing optimized batch user interface calls and response processing using web workers, which allow parallel processing of data in separate threads, enabling incremental data presentation and avoiding timeouts by batching requests based on the hierarchy structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential calls are used to process and present information from hierarchical data sections, then data processing is completed thoroughly, but user wait time increases and timeout errors occur

Engineering Contradiction:
Improvedata processing completenessVSAvoiduser wait time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the hierarchical data processing into multiple independent batches, where each batch processes a specific section or subsection. This allows parallel processing of different data sections simultaneously, reducing overall wait time while maintaining complete data processing through systematic batch management.

Inventive Principle:
Principle #1Segmentation

2Reliability

If sequential calls are used to access and present hierarchical data, then all data sections are processed, but timeout errors occur during data reading

Engineering Contradiction:
Improvedata processing completenessVSAvoidtimeout errors
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent divides the data processing into smaller batches with manageable data volumes, preventing timeout errors that occur with large sequential data loads. Each batch is processed independently within timeout thresholds, ensuring reliable data reading without overwhelming the system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent processes data in partial batches rather than attempting to load all data at once. This partial action approach processes sufficient data segments to meet user needs while staying within system timeout limitations, avoiding harmful timeout errors.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If sequential processing is used for hierarchical data sections, then complete data is presented, but frontend browser processing timeout occurs

Engineering Contradiction:
Improvedata presentation completenessVSAvoidfrontend timeout errors
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the frontend processing into multiple parallel batch operations, where each batch processes a specific data section independently. This segmentation prevents the frontend browser from timing out by distributing processing load across multiple smaller, concurrent operations rather than one large sequential process.

Inventive Principle:
Principle #1Segmentation

4Reliability

If all data sections are processed before presentation, then complete information is available, but user experience deteriorates due to long wait times

Engineering Contradiction:
Improveinformation completenessVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent performs preliminary processing of data into organized batches before user interaction. This preliminary action prepares data segments in advance, allowing rapid presentation when users request specific sections, thereby improving user experience while maintaining information completeness through systematic batch management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments data processing and presentation into independent batches that can be retrieved and displayed independently. This allows the system to present complete information when needed while providing faster initial response times for specific sections, significantly improving user experience.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12038985B2Batch user interface calls and response processing
Publication Date: 2024.07.16 SAP SE
  • US12038985B2 patent drawing
  • US12038985B2 patent drawing
  • US12038985B2 patent drawing

AI summary

User interface responsiveness is improved using batch interface calls and response processing. To do this, a selection, via a user interface, is obtained of nodes of a hierarchy corresponding to a hierarchical data structure containing information to be presented in the user interface based on the selection. A separate request is sent to a database to obtain information corresponding to each of the nodes. Responses corresponding to a particular request are received from the database. Each response is processed to obtain parsed data in separate threads such that the responses are executable in parallel. The processing of the responses outputs parsed data for the corresponding response. The parsed data is obtained and the parsed data for a particular response is incrementally presented in the user interface as it is obtained.