Method and system for performing SW upgrade in a real-time system

• US 7,089,550 B2
• Filed: 02/19/2003
• Issued: 08/08/2006
• Est. Priority Date: 03/13/2002
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Bakke, Knut, Johansen, Odd Oyvind, Mohagheghi, Parastoo
• Primary Examiner(s): INGBERG, TODD D
• Application Number:
  US10/369,870
• Publication Number:
  US 20030177486A1
• Time in Patent Office: 1,266 Days
• Field of Search: 717/173, 717/178, 713/188, 713/187, 713/118, 713/200, 713/220, 713/201, 455/418, 455/414.1, 455/412.1, 455/410, 455/575.1, 455/550.1, 455/186.1, 709/206, 709/207, 709/219, 370/270, 380/270
• US Class Current: 717/173
• CPC Class Codes: G06F 8/656 while running

Abstract

A new method is disclosed, for upgrading the software in a real-time distributed software system comprising several processes running in parallell. The method involves a preparatory procedure in which the new software is installed. Then, the software is activated, the components ordered to save configuration data and transaction data in a database, whereupon the components are stopped. When the preparatory procedure is completed, a restart procedure is invoked. This involves selecting start level (full upgrade involving all components, or a partial upgrade concerning just one or a few components). The modules concerned are started from the new software version. On each start level a number of start phases are defined. These are sequential steps performed during the restart operation. Each module subscribes to a number of these phases. Some of the phases are defined as synchronisation points, here called service levels, which all modules have to arrive at before the process is allowed to commence. During this process, each module is given the responsibility of converting any configuration data or transaction data belonging to it, if needed. The conversion is done by reading the old data from the database mentioned above and converting said data to the format required by the new software.

Claims

1. A method for upgrading software in a system comprising several application modules running in parallel, one or more of the modules holding configuration data and transaction data which must survive the upgrade operation, comprising the steps of:

a) installing and activating new software on the system,

b) ordering all modules to save their configuration and transaction data to a database,

c) stopping all modules

d) restarting all modules from the new software version,

e) any module which need to convert the configuration and transaction data in order to comply with the new software version, loading said data from the database and defining an upgrade module, and

f) said upgrade module will read said data, convert the data into the required format, and save the converted data by writing the converted data back into said database.

2. The method as claimed in claim 1, wherein said step c) further comprises the steps of:

c1) selecting a start level defining the number of application modules that are concerned by the upgrade, each start level comprising a number of start phases defining activities;

c2) allocating a number of start phases to each application module; and

c3) executing the start phases seguentially for each application module.

3. The method as claimed in claim 2, wherein some of the start phases are defined as synchronization points, and on arriving on such a phase, each application module being arranged to temporarily stop the execution of the phase until all application modules have reached the same phase.

4. A system for processing data tangibly embodied on a computer readable medium comprising a number of application modules running in parallel, the system comprising:

a number of start levels each defining the extent of a start or restart procedure,

each start level including a number of start phases each defining an activity,

each application module subscribing to a number of start phases of each start level,

a database holding configuration and transaction data for one or more of the application modules, and

an upgrade module associated with each application module, said upgrade module being adapted to read configuration and transaction data from said database, convert the data and write the data back into the database.

5. The system as claimed in claim 4, wherein some of said start phases are defined as synchronization points, and on arriving on such a phase, each application module being arranged to temporarily stop the execution of the phase until all application modules have reached the same phase.

6. The system as claimed in claim 4, further comprising:

means for selecting a start level defining the number of application modules that are concerned by the upgrade, each start level comprising a number of start phases defining activities;

means for allocating a number of start phases to each application module; and

means for executing the start phases sequentially for each application module.