Browse Prior Art Database

SYSTEM AND METHOD FOR DYNAMIC VERSION MANAGEMENT OF WIRELESS APPLICATIONS

IP.com Disclosure Number: IPCOM000126843D
Publication Date: 2005-Aug-15
Document File: 4 page(s) / 96K

Publishing Venue

The IP.com Prior Art Database

Abstract

The idea is for a wireless application framework which manages migration between different versions of an XML application. The key feature of this system is the ability to maintain the bulk of the application (XML Content) and allow code potions of the application to update as required. The added feature of this idea is that application data may be preserved, and code portions are separated. This idea applies to any range of XML-defined applications to be used in conjunction with terminals that are limited in terms of connectivity, memory, and storage space. A wireless application is partitioned by the designer into several non-overlapping Logical Modules, which may be Code Modules that drive the application behavior, or Data Modules that define how data is represented. All modules are uniquely addressable via an Addressing Scheme. Code Modules are considered to export a set of executable methods. To facilitate the management of a partial update to an application, the following facilities are required: Migration Script, Addressing Map, and Inter-module Addressing Scheme. Data Modules generally represent the content of the XML-defined application. This XML Content typically makes up the bulk of the XML application. Further, XML Content makes reference to Code Modules that may drive the application, affect presentation of the content, etc. It is advantageous to allow this content to remain unaffected when various Code Modules update. This is the essence of version indifference from the perspective of the XML Content. Due to the limited processing capabilities of the device and the medium through which XML Applications are transferred, the resources dedicated to performing an upgrade are at a premium. In the scheme described in this proposal, the transfer and install time for an upgraded application can be considerably reduced. Utilization of the Addressing Map allows the potential to have multiple different versions of the same application resident on the same device, sharing modules rather than duplicating common code, and operating on the same internal representation of data. Figure 1: Sample Code Module public vs private addressing Table 1:Sample Code Module Addressing Public Address Private Address APP_METHOD A CMX_1 APP_METHOD B CMX_2 APP_METHOD C CMX_3 Figure 2: Sample Processing Framework partitioning Figure 2: Sample Processing Framework partitioning Figure 3: Sample XML Application and execution paths Table 2:Addressing Map for sample app prior to upgrade Public Address Private Address Module Port APP_METHOD A CM4 CM4_1 APP_METHOD B CM3 CM3_1 APP_METHOD C CM3 CM3_2 APP_METHOD D CM2 CM2_1 APP_METHOD E CM1 CM1_1 APP_METHOD F CM3 CM3_3 During upgrade, the Migration Script instructs the Upgrade Manager to remove Code Modules CM3 and CM4. The resulting application and revised Address Map are installed as depicted in Figure 4 and Table 3. Figure 4:Sample application after upgrade showing defunct, revised paths and modules Table 3:Updated Addressing Map for revised application Public Address Private Address Module Port APP_METHOD A CM5 CM5_1 APP_METHOD C CM5 CM3_2 APP_METHOD C CM2 CM2_1 APP_METHOD E CM1 CM1_1 APP_METHOD F CM5 CM5_3

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

SYSTEM AND METHOD FOR DYNAMIC VERSION MANAGEMENT OF WIRELESS APPLICATIONS

Disclosed Anonymously

The idea is for a wireless application framework which manages migration between different versions of an XML application.  The key feature of this system is the ability to maintain the bulk of the application (XML Content) and allow code potions of the application to update as required.  The added feature of this idea is that application data may be preserved, and code portions are separated. 

This idea applies to any range of XML-defined applications to be used in conjunction with terminals that are limited in terms of connectivity, memory, and storage space.

A wireless application is partitioned by the designer into several non-overlapping Logical Modules, which may be Code Modules that drive the application behavior, or Data Modules that define how data is represented.  All modules are uniquely addressable via an Addressing Scheme.  Code Modules are considered to export a set of executable methods. 

To facilitate the management of a partial update to an application, the following facilities are required: Migration Script, Addressing Map, and Inter-module Addressing Scheme.

Data Modules generally represent the content of the XML-defined application.  This XML Content typically makes up the bulk of the XML application.  Further, XML Content makes reference to Code Modules that may drive the application, affect presentation of the content, etc.  It is advantageous to allow this content to remain unaffected when various Code Modules update.  This is the essence of version indifference from the perspective of the XML Content.

Due to the limited processing capabilities of the device and the medium through which XML Applications are transferred, the resources dedicated to performing an upgrade are at a premium.  In the scheme described in this proposal, the transfer and install time for an upgraded application can be considerably reduced.

Utilization of the Addressing Map allows the potential to have multiple different versions of the same application resident on the same devic...