Markup Language Database Query Refresh Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for database queries and user interface screens in wireless communication devices are inefficient as they often require frequent database query re-execution, leading to excessive data transmission and processing, especially when the database is not frequently updated.

Innovation Solution

The implementation of markup language-based object-oriented code that allows for the definition, execution, and refreshing of database queries and user interface screens independently, enabling mutual exclusive instantiation based on user specifications, thereby reducing unnecessary query refreshes and data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the database query is re-executed every time the GUI screen is presented to ensure data currency, then the data freshness is improved, but the data transmission volume and processing overhead increase excessively

Engineering Contradiction:
Improvedata freshnessVSAvoiddata transmission overhead
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system dynamically determines whether to refresh the database query based on the current state of the database and the requirements of the GUI screen. Instead of always refreshing the query when the screen is presented, the system evaluates whether the database has been modified since the last query execution. This dynamic approach allows the system to maintain data freshness when necessary while avoiding unnecessary data transmission and processing overhead when the database remains unchanged.

Inventive Principle:
Principle #15Dynamics

2Measurement precision

If the database query is re-executed frequently to maintain data currency, then the data accuracy is improved, but the processing time increases

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing a mechanism to track database modifications before the GUI screen is presented. The system monitors whether the database has been updated since the last query execution and only re-executes the query when necessary. This preliminary checking approach ensures data accuracy is maintained while avoiding the time penalty of frequent unnecessary query re-executions.

Inventive Principle:
Principle #10Preliminary action

3Loss of energy

If the application downloads minimal data to reduce transmission cost, then the data transmission cost is reduced, but the functionality and adaptability of the application are limited

Engineering Contradiction:
Improvedata transmission costVSAvoidapplication functionality
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The application is segmented into core functionality components that are downloaded with minimal data, and optional or context-dependent components that are downloaded only when needed. The system identifies and downloads only the essential application code and data structures required for basic operation, while deferring the download of additional functionality to later stages when specific features are activated or when the user's needs are determined. This segmentation approach reduces initial transmission cost while preserving full adaptability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP1865423B1Software and Device for refreshing Markup Language-Based Database Queries Independently from User Interface Screens
Publication Date: 2008.11.19 NEXTAIR CORP
  • EP1865423B1 patent drawingFigure 1
  • EP1865423B1 patent drawingFigure 2
  • EP1865423B1 patent drawingFigure 3

AI summary

To effect database queries and user interface screens that are independently refreshable and markup language-based, a machine-readable medium contains object-oriented code for defining a database query, including instructions for storing the result of the database query, based on a markup language element representation of the query, and object-oriented code for displaying a user interface screen based on a markup language element representations of the screen which has a display element that is based at least in part upon the result of the database query. The machine-readable medium also contains object-oriented code for refreshing the database query and object-oriented code for refreshing the screen that are capable of mutually exclusive instantiation based upon a user specification of one of a markup language element representing a refreshing of the database query and a markup language element representing a screen refresh. The markup language may be Extensible Markup Language (XML).