System and method for implementing data-compatibility-based version scheme

• US 8,555,272 B2
• Filed: 03/16/2010
• Issued: 10/08/2013
• Est. Priority Date: 04/18/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Wetherly, Curtis, Goring, Bryan R., Shenfield, Michael, Cacenco, Michael
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Rampuria, Satish
• Application Number:
  US12/725,028
• Publication Number:
  US 20100175059A1
• Time in Patent Office: 1,302 Days
• Field of Search: 717168-178, 455418-421, 455/422.1, 455/426, 709/202, 709/203, 707/638, 707/695, 707/806
• US Class Current: 717/170
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

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. The versioning schema includes a respective field for each one of a plurality of aspects of the application and defines an initial value of each field when an initial application load is released. For each successive software update affecting the application, the method involves identifying each aspect of the application affected by the software update and incrementing a value of the respective field of each identified aspect. The version number can be in the form D.M.F where D, M and F are incremented in response to changes in the application relating to data components, message components and features.

Claims

1. A method of enabling controlled distribution of software updates affecting an application installed on a plurality of terminal devices of a wireless network, the method comprising steps of:

defining a single version number for said application, said version number comprising a respective field for each one of a plurality of aspects of the application, said plurality of fields being separated from one another within said version number by a separator symbol;

defining an initial value of each field when an initial application load is released; and

for each successive software update affecting the application;

identifying each aspect of the application affected by the software update; and

incrementing a value of the respective field of each identified aspect.

2. The method as claimed in claim 1, wherein the version number comprises at least one “

Data”

field corresponding to data components of the application, and wherein said incrementing increments the numerical value of the “

Data”

field if the software update modifies any existing data components of the application.

3. The method as claimed in claim 1, wherein the version number comprises at least one “

Messages”

field corresponding to messages used by the application, and wherein said incrementing increments the numerical value of the “

Messages”

field if the software update modifies any existing messages used by the application.

4. The method as claimed in claim 1, wherein the version number comprises at least one “

Features”

field corresponding to functional features of the application, and wherein said incrementing increments the numerical value of the “

Features”

field if the software update adds any one or more of new data components, new messages, and new application logic to the application.

5. The method of claim 1 wherein said incrementing comprises incrementing a value of a given one of said respective fields of said single version number independently of any incrementing of a value of any other one of said respective fields of said single version number.

6. The method of claim 1 wherein the value of at least one of said fields is a letter.

7. The method of claim 1 wherein said separator symbol is a colon, slash or hyphen.

8. The method of claim 1 wherein said incrementing comprises, for a single one of said successive software updates, incrementing each field of said plurality of fields of said version number.

9. A system for enabling controlled distribution of software updates affecting an application installed on a plurality of terminal devices 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 (ADE) running on the computing device for enabling the application to be updated, the ADE including a versioning module for generating a single version number for said application, said version number defined by a plurality of fields representing different aspects of the application, said plurality of fields being separated from one another within said version number by a separator symbol, the versioning module causing said computing device to;

compare an updated version of the application with a previous version of the application to determine what changes have been made to the different aspects of the application;

increment the fields of the version number in response to the changes to the different aspects of the application; and

communicate the version number of the updated application to the application gateway.

10. The system as claimed in claim 9 wherein the version number is defined to include fields representing changes to Data, Messages and Features.

11. The system as claimed in claim 9 wherein the version number is defined in the form D.M.F where D represents changes to aspects of the application relating to data, M represents changes to aspects of the application relating to messages, and F represents changes to aspects of the application relating to features.

12. The system of claim 10 wherein said incrementing increments:

a given value of D independently of the respective values of M and F;

a given value of M independently of the respective values of D and F; and

a given value of F independently of the respective values of D and M.

13. The system as claimed in claim 9 wherein the versioning module defines an initial version number for an initial version of the application and then increments the first digit by 1 when a change is detected in an aspect of the application relating to data, increments the second digit by 1 when a change is detected in an aspect of the application relating to messages, and increments the third digit by 1 when a change is detected in an aspect of the application relating to application features.

14. The system as claimed in claim 9 wherein the versioning module defines an initial version number for an initial version of the application and then increments the first digit by 1 when a change is detected in an aspect of the application relating to existing data components, increments the second digit by 1 when a change is detected in an aspect of the application relating to existing messages, and increments the third digit by 1 when a change is detected in an aspect of the application relating to existing or new application logic, new data components, or new message components.

15. The system as claimed in claim 9 wherein the comparing of the updated version of the application with the previous version of the application is performed using a revisions log for tracking changes made to the application within the application development environment.

16. A method of implementing a versioning scheme for updates to a software application to be distributed to a plurality of wireless devices in a wireless network through an application gateway mediating the wireless network and a data network, the method comprising the steps of:

defining an initial single version number corresponding to an initial version of the application, the version number having at least three fields defining a data components field, a message components field and a features field;

incrementing the data components field in response to an update in an aspect of the application relating to data components;

incrementing the message components field in response to an update in an aspect of the application relating to message components; and

incrementing the features field in response to an update to an aspect of the application relating to features, whereby an updated version number is generated that is indicative of the compatibility of the update with previous versions of the application.

17. The method as claimed in claim 16 further comprising the step of notifying the updated version number to the application gateway.

18. The method as claimed in claim 17 further comprising the step of notifying the updated version number to the terminal device to enable the terminal device to check compatibility with the updated application and, where an incompatibility is detected, to install the update by downloading and executing a script that accesses and downloads update files.

19. The method as claimed in claim 16 wherein the initial version number is initialized to an initial version number and wherein the data components, message components and feature fields are respectively incremented by 1 in response to changes in aspects of the application relating, respectively, to existing data components, to existing message components and to features, whereby aspects relating to features include additions of new data components, additions of new message components, additions of new logic and changes to existing logic that are compatible with the previous versions.

20. The method as claimed in claim 16 wherein the version number further comprises a fourth field occupied by a fourth digit that is incremented in response to changes to a fourth aspect of the application.

21. The method as claimed in claim 16 wherein the step of incrementing the features field in response to an update in an aspect of the application relating to features comprises incrementing the features field in response to additions of new logic, new data components, new message components or changes to existing logic which are compatible with the previous version of the application.