XML-Based Database Upgrade for Mobile Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database upgrade methods lack an efficient, markup language-based solution for managing schema changes and incremental migrations across different versions, particularly in mobile devices where resource constraints and wireless network costs are significant.

Innovation Solution

A method utilizing Extensible Markup Language (XML) documents to describe database changes, which are executed by database upgrade software to perform actions such as adding, dropping, or renaming tables and fields, enabling incremental upgrades from one database version to another, leveraging a hierarchy of objects instantiated from XML elements to manage the upgrade process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If markup language documents (XML) are used to describe database changes, then the database upgrade process becomes more adaptable and easier to manage across different versions, but the complexity of the upgrade software increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces markup language documents (XML) as an intermediary between the database upgrade software and the actual database schema changes. These documents serve as a standardized interface that describes all modifications (table additions, field deletions, renamings, etc.) in a platform-independent format, allowing the software to interpret and execute changes without being tightly coupled to specific database management systems or operating platforms

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The database upgrade process is segmented into distinct components: the markup language document containing structured change descriptions, the upgrade software that parses and interprets these documents, and the database management system that executes the changes. This segmentation allows each component to be developed and maintained independently, improving adaptability while managing complexity through clear separation of concerns

Inventive Principle:
Principle #1Segmentation

2Loss of energy

If database upgrades are performed locally on mobile devices, then wireless data transmission costs are reduced, but the device must handle more processing and storage responsibilities

Engineering Contradiction:
Improvetransmission costVSAvoidcomplexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent enables mobile devices to perform database upgrades autonomously by executing markup language documents locally. The upgrade software on the device parses the change descriptions and applies modifications without requiring continuous communication with external servers, allowing the device to serve itself during the upgrade process and minimizing wireless data transmission

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The complete database upgrade instructions are provided in advance through the markup language documents, which contain all necessary change information (additions, deletions, renamings) before execution. This preliminary preparation allows the device to perform all upgrade operations locally without needing to fetch additional instructions during the process, reducing transmission requirements

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP1881420B1Mark Up Language Based Database Upgrades
Publication Date: 2008.11.12 NEXTAIR CORP
  • EP1881420B1 patent drawingFigure 1
  • EP1881420B1 patent drawingFigure 2
  • EP1881420B1 patent drawingFigure 3

AI summary

Software, methods and devices for performing a markup language based database upgrade are disclosed. One or more markup language documents contain markup language portions. Each markup language portion, which may be a hierarchy of markup language elements, describes a set of changes to be made to the database in order to effect an upgrade of the database from a starting version to a subsequent version. Based on a determined current version of a database, one of the markup language portions is selected for implementation. The set of changes to the database that is described by the selected markup language portion is implemented. Implementation may be effected through instantiation of object oriented classes corresponding to markup language elements. Selection and implementation of other markup language portions may be performed until a final database version is attained. The markup language may be Extensible Markup Language (XML).