Segmented Screen Update System for Web Application Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current screen updating methods for Web applications either reload unnecessary data, transfer non-updated data, or risk data inconsistency due to inadequate handling of dependent data blocks during updates.

Innovation Solution

An information processing apparatus that stores segment information about associated display units and instructs the client terminal to update data in associated segments when an update occurs, ensuring only relevant data is refreshed and maintaining data consistency across dependent blocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entirety of the screen is periodically reloaded (scheme 1), then data consistency is maintained, but unnecessary data is transferred and I/O load increases

Engineering Contradiction:
Improvedata consistencyVSAvoidI/O load
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The screen is divided into multiple blocks, and the system tracks which blocks contain updated data. Only the necessary blocks are reloaded and transferred to the client terminal, rather than reloading the entire screen. This segmentation approach maintains data consistency for updated blocks while avoiding unnecessary transfers of non-updated blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different update strategies to different blocks based on their update status. Blocks with updated data are reloaded and transferred, while blocks without updates are left unchanged. This localized approach ensures data consistency where needed while minimizing I/O load in areas where data hasn't changed.

Inventive Principle:
Principle #3Local quality

2Loss of energy

If only updated blocks are reloaded (scheme 2), then I/O load is reduced, but data inconsistency may occur between dependent blocks

Engineering Contradiction:
ImproveI/O loadVSAvoiddata consistency
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system maintains an update notification list that tracks which blocks contain updated data. When determining which blocks to reload, the system references this feedback information to identify not only the updated block itself but also any dependent blocks that require updates to maintain consistency. This feedback mechanism prevents data inconsistency while minimizing unnecessary transfers.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system pre-identifies dependent blocks that need to be updated alongside the primary updated block by checking the update notification list before initiating the reload process. This preliminary identification ensures that all blocks requiring updates are prepared in advance, preventing data inconsistency issues.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If updated blocks are reloaded using push scheme (scheme 3), then unnecessary data transfer is reduced, but I/O load increases due to frequent transmissions

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidI/O load
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system performs partial action by reloading only the specific blocks that contain updated data and their dependent blocks, rather than reloading the entire screen. This selective approach reduces I/O load compared to full screen reloads while ensuring that all necessary updates are transmitted to maintain data consistency.

Inventive Principle:
Principle #16Partial or excessive action

4Loss of information

If only the updated block is reloaded (scheme 3), then data transfer efficiency is improved, but data inconsistency occurs between dependent blocks

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoiddata consistency
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The system uses the update notification list as feedback to identify not only the directly updated block but also any dependent blocks that require updates. This feedback-driven approach ensures that all blocks needing updates are identified and reloaded together, maintaining data consistency while avoiding unnecessary transfers of blocks that don't depend on the updated data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10719569B2Information processing apparatus, screen displaying system, and non-transitory recording medium having storing therein program
Publication Date: 2020.07.21 FSAS TECH INC
  • US10719569B2 patent drawing
  • US10719569B2 patent drawing
  • US10719569B2 patent drawing

AI summary

An information processing apparatus includes a storing device and a processor. The storing device stores associated segment information indicative of two or more display unit segments having common data forming display contents among a plurality of display unit segments included in a screen of the client terminal. The processor instructs, when an update occurs on the data forming the display contents on a first display unit segment among the plurality of display unit segments, the client terminal to update data forming the display contents to be displayed on a second display unit segment associated with the first display unit segment among the plurality of display unit segments by referring to the associated segment information stored in the storing device.