Method and system for controlling software version updates

• US 20060236083A1
• Filed: 04/11/2006
• Published: 10/19/2006
• Est. Priority Date: 04/18/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Shenfield, Michael, Vitanov, Kamen B., Goring, Bryan R., Bibr, Viera, Fritsch, Brindusa L., Blagojevic, Vladimir
• Granted Patent: US 7,747,995 B2
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

Methods and systems are provided for controlling asynchronous distribution and installation of software updates affecting applications installed on terminal devices of a wireless network. A versioning schema enforced by the application development environment enables the runtime environment of a terminal device to evaluate a software update to identify potential compatibility issues and control installation of the update.

Claims

1. A method of controlling asynchronous installation of a software update on a terminal device of a wireless network, the method comprising steps of:

receiving an update notification message in respect of the software update, the update notification message comprising;

a software identifier uniquely identifying an application affected by the update;

a version number associated with the software update; and

an address of an update script on a data network accessible by the terminal device, the update script being adapted to install the software update on the terminal device;

logging the update notification message in an updates registry; and

forwarding a notification message to the terminal device, the notification message including the software identifier, the version number and the address of the update script.

2. A method as claimed in claim 1, wherein the data network is an Internet Protocol (IP) network, and the address of an update script comprises a Uniform Resource Locator (URL) address of the update script on the IP network.

3. A method as claimed in claim 1, wherein the step of logging the update notification message in a registry comprises a step of storing at least the software identifier, the version number and the address of the update script in the updates registry.

4. A method as claimed in claim 1, wherein the step of forwarding the notification message comprises steps of:

searching a profiles registry containing information identifying each application installed on each one of a plurality of terminal devices, to identify each terminal device which is affected by the software update; and

sending the notification message to each identified terminal device.

5. A method as claimed in claim 4, wherein the profiles registry comprises a plurality of profiles, each profile being associated with a respective terminal device and containing, for each application installed on the respective terminal device, the respective software identifier of the application, and a current version number indicative of a version of the installed application, and wherein the step of searching the profiles registry comprises a step of identifying each terminal device for which the software identifier of the update matches that of an application installed on the terminal device.

6. A method as claimed in claim 5, further comprising a step of identifying each terminal device for which at least one field of the version number associated with the software update is greater than a corresponding field of the current version number.

7. A method as claimed in claim 1, wherein the step of forwarding the notification message comprises steps of:

receiving a message from the terminal device;

accessing a profile associated with the device, the profile containing information identifying software installed on the terminal device;

searching the updates registry using the profile to identify any software updates affecting software installed on the terminal device; and

sending a notification message to the terminal device in respect of each identified software update.

8. A method as claimed in claim 7, wherein the profile contains, for each software application installed on the terminal device, the respective software identifier, and a current version number indicative of a version of the software application, and wherein the step of searching the updates registry further comprises steps of:

comparing the version number associated with the software update with the current version number; and

identifying each software update for which at least one field of the associated version number is greater than a corresponding field of the current version number.

9. A method as claimed in claim 1 wherein the script is further adapted to perform a data transformation on an incompatible update.

10. A method of controlling installation of a software update on a terminal device of a wireless network, the method comprising steps of:

receiving an update-notification message comprising information respecting an available software update, the update notification message comprising;

a software identifier uniquely identifying an application affected by the update;

a version number associated with the software update; and

an address of an update script on a data network accessible by the terminal device, the update script being adapted to install the software update on the terminal device;

determining a compatibility of the software update using the update version number;

accessing the update script using the address; and

executing the update script.

11. A method as claimed in claim 10, wherein the step of determining a compatibility of the software update comprises a step of comparing the update version number to a current version number of the affected application.

12. A method as claimed in claim 11, wherein the update and current version numbers are defined in accordance with a version schema comprising a respective field for each one of a plurality of aspects of the application, and wherein the step of comparing the update version number to the current version number comprises a step of subtracting a value of each field of the current version number from the value of the corresponding field of the update version number.

13. A method as claimed in claim 12, further comprising, if a numerical value of any field of the subtraction result is greater than 1, a step of determining that at least one other software update must be installed prior to installation of the software update.

14. A method as claimed in claim 12, wherein the version schema comprises at least one “

Data”

field corresponding to data components of the application, and wherein the step of determining a compatibility of the software update comprises, if the numerical value of the “

Data”

field of the subtraction result is greater than “

0”

, determining that the software update may require conversion of user data stored on the terminal device.

15. A method as claimed in claim 12, wherein the version schema comprises at least one “

Messages”

field corresponding to message components of the application, and wherein the step of determining a compatibility of the software update comprises, if the numerical value of the “

Messages”

field of the subtraction result is greater than “

0”

, determining that the software update may require conversion of user messages stored on the terminal device.

16. A method as claimed in claim 12, wherein the version schema comprises at least one “

RE”

field corresponding to a runtime environment of the application, and wherein the step of determining a compatibility of the software update comprises, if the numerical value of the “

RE”

field of the subtraction result is greater than “

0”

, determining that a runtime environment of the application must be updated before the software update.

17. A method as claimed in claim 10 wherein the script is further adapted to perform a data transformation on an incompatible update.

18. A system for controlling asynchronous installation of a software update on a terminal device of a wireless network, the system comprising:

a computing device connected to a data network for communicating with an application gateway mediating the data network and the wireless network;

an application development environment running on the computing device for enabling the application to be updated and for further enabling update scripts and update files to be uploaded to an application developer registry that is accessible through the data network for subsequent downloading by the terminal device via the application gateway.

19. The system as claimed in claim 18 further comprising an online registry including:

a profiles registry containing, for each terminal device, a listing of information identifying software applications stored on the terminal device; and

an updates registry containing information identifying any available application updates.

20. The system as claimed in claim 18 wherein the terminal device comprises a memory for storing a terminal device registry identifying software applications loaded on the terminal devices and a version number corresponding to each of the software applications loaded on the terminal device.

21. The system as claimed in claim 18 wherein the application development environment comprises a versioning module for assigning a version number based on changes made to the software application.

22. The system as claimed in claim 19 wherein the online registry is co-resident with the application gateway.