System and Method for Context Sensitive Mobile Data and Software Update

• US 20100251230A1
• Filed: 06/08/2010
• Published: 09/30/2010
• Est. Priority Date: 04/07/2003
• Status: Abandoned Application

• Current Assignee: Antenna Dexterra Incorporated
• Original Assignee: Antenna Dexterra Incorporated
• Inventors: O'Farrell, Robert, Kirstein, Mark D.
• Application Number:
  US12/796,277
• Publication Number:
  US 20100251230A1
• Time in Patent Office: Days
• US Class Current: 717/173
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 8/61 Installation

Abstract

Change management for a mobile data system having a mobile client device that shares data with multiple enterprise data sources involves receiving a communication from the mobile client device, wherein the client request is received at an application server and includes metadata that identifies one or more to applications installed at the mobile client device, determining if an update package is available for the installed application, and updating the mobile client device and downloading the update package to the mobile client device.

Claims

1. A method of change management for a mobile data system having a mobile client device that shares data with multiple enterprise data sources, the method comprising:

receiving a communication request from the mobile client device to establish communications with a server of the mobile data system, wherein the communication request includes data that identifies one or more applications installed at the mobile client device;

determining if an update package is available for the identified application at the client device; and

downloading the update package to the mobile client device and updating the identified application at the mobile client device.

2. A method as defined in claim 1, further including a subscription process for initial installation of the identified application.

3. A method as defined in claim 2, wherein the subscription process comprises:

identifying a user at the mobile client device;

downloading a Client Framework to the mobile client device; and

receiving data comprising at least one from the group of Metadata, Customer Data Definition, Customer Business Data, and runtime files for the identified application, wherein the received data is overwritten to any prior corresponding application files previously installed at the mobile client device.

4. A method as defined in claim 1, wherein determining if an update package is available comprises:

determining a version number for the identified application installed at the mobile client device;

identifying an update package for the identified application; and

installing the update package at the mobile client device to replace the previous version of the identified application.

5. A method as defined in claim 4, wherein determining a version number comprises receiving data from the mobile client in a predetermined format for the identified application and determining the version number in accordance with the data format.

6. A method as defined in claim 1, wherein the communication request identifies all installed applications at the mobile client device.

7. A method of operating a mobile client device in a mobile data system in which the client device shares data with multiple enterprise data sources, the method comprising:

transmitting a communication request from the mobile client device to a server of the mobile data system to establish communication, wherein the communication request includes data that identifies one or more applications installed at the mobile client device, wherein the communication request includes information that determines a version number for the identified application installed at the mobile client device;

receiving an update package from the server that replaces the version of the identified application with an updated version of the identified application.

8. A method as defined in claim 7, wherein the communication request includes data from the mobile client in a predetermined data format for the identified application and thereby determines the version number of the identified application.

9. A method as defined in claim 7, wherein the communication request identifies all installed applications at the mobile client device.

10. A method as defined in claim 7, further including performing a subscription process at the mobile client device for initial installation of the identified application at the mobile client device.

11. A method as defined in claim 10, wherein the subscription process comprises:

sending user identifying information to a network location;

selecting the identified application for installation;

downloading a Client Framework for the identified application; and

receiving data comprising at least one from the group of Metadata, Customer Data Definition, Customer Business Data, and runtime files for the identified application, wherein the received data is overwritten to any prior corresponding application files previously installed at the mobile client device.

12. A server for use in a mobile data system in which a mobile client device shares data with multiple enterprise data sources through communications with the server, the server comprising:

a wireless communication interface that enables communication with the mobile client device;

a processor that operates so as to receive a communication request from the mobile client device to establish communications with the server, wherein the communication request includes data that identifies one or more applications installed at the mobile client device, and the processor further operates to determine if an update package is available for the identified application at the client device and, if so, sends the update package to the mobile client device for updating the identified application at the mobile client device.

13. A server as defined in claim 12, wherein the server performs a subscription process for initial installation of the identified application at the mobile client device.

14. A server as defined in claim 13, wherein the server performs the subscription process by identifying a user at the mobile client device, sending a Client Framework to the mobile client device, and sending data comprising at least one from the group of Metadata, Customer Data Definition, Customer Business Data, and runtime files for the identified application to the mobile client device, such that the mobile client device will overwrite any prior corresponding application files previously installed at the mobile client device.

15. A server as defined in claim 12, wherein the server determines if an update package is available by determining a version number for the identified application installed at the mobile client device, identifying an update package for the identified application, and sending the update package to the mobile client device to replace the previous version of the identified application.

16. A server as defined in claim 15, wherein the server determines a version number by receiving data from the mobile client in a predetermined format for the identified application and determines the version number in accordance with the data format.

17. A server as defined in claim 12, wherein the received communication request identifies all installed applications at the mobile client device.