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

• US 7,698,702 B2
• Filed: 09/06/2005
• Issued: 04/13/2010
• Est. Priority Date: 04/18/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Cacenco, Michael, Wetherly, Curtis, Shenfield, Michael, Goring, Bryan R.
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): Rampuria; Satish
• Application Number:
  US11/218,432
• Publication Number:
  US 20060236317A1
• Time in Patent Office: 1,680 Days
• Field of Search: 717168-178, 707/203, 455/550.1, 455/552.1, 455/418
• 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 updates to a software application, the method comprising:

defining a single version number for said software application, said single version number comprising the form “

A.B”

, wherein each of “

A” and

“

B”

is a field representing a respective one of a plurality of aspects of the application;

defining an initial numerical value of each of said fields “

A” and

“

B”

when an initial application load is released; and

for each successive software update affecting the application;

identifying each aspect of said plurality of aspects of the application affected by the software update, said identifying resulting in at least one identified aspect; and

for each said identified aspect, incrementing the numerical value of the respective field of said single version number independently of any incrementing of the numerical value of any other field of said single version number.

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, for a single one of said successive software updates, incrementing each field of said plurality of fields of said version number.

6. A method of enabling software updates to a software application, the method comprising:

defining a single version number for said software application,

said single version number comprising the form “

D.M.F”

, wherein “

D”

is a data field corresponding to data components of the application, “

M”

is a messages field corresponding to messages used by the application, and “

F”

is a features field corresponding to functional features of said application;

defining an initial numerical value of each of said fields “

D”

, “

M” and

“

F”

when an initial application load is released; and

for each successive software update affecting said application;

identifying each one of said data components, said messages and said functional features of said application affected by the software update, said identifying resulting in at least one identified aspect; and

for each said identified aspect, incrementing the value of the respective field of said single version number independently of any incrementing of the numerical value of any other field of said single version number.

7. A system for enabling controlled distribution of software updates affecting a software application installed on a plurality of terminal devices of a wireless network, the system comprising a computing device operable to:

define a single version number for said software application, said single version number comprising the form “

A.B”

, wherein each of “

A” and

“

B”

is a field representing a respective one of a plurality of aspects of the application;

define an initial numerical value of each of said fields “

A” and

“

B”

when an initial application load is released; and

for each successive software update affecting the application;

identify each aspect of said plurality of aspects of the application affected by the software update, said identifying resulting in at least one identified aspect; and

for each said identified aspect, increment the numerical value of the respective field of said single version number independently of any incrementing of the numerical value of any other field of said single version number.

8. A system for enabling controlled distribution of software updates affecting a software application installed on a plurality of terminal devices of a wireless network, the system comprising a computing device operable to:

define a single version number for said software application, said single version number comprising the form “

D.M.F”

, wherein “

D”

is a data field corresponding to data components of the application, “

M”

is a messages field corresponding to messages used by the application, and “

F”

is a features field corresponding to functional features of said application;

define an initial numerical value of each of said fields “

D”

, “

M” and

“

F”

when an initial application load is released; and

for each successive software update affecting said application;

identify each one of said data components, said messages and said functional features of said application affected by the software update, said identifying resulting in at least one identified aspect; and

for each said identified aspect, increment the value of the respective field of said single version number independently of any incrementing of the numerical value of any other field of said single version number.