Patent US5905896A successfully refreshed from Google Patents.
US5905896A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method of changing software version in a computer system comprising a plurality of stations, and a computer system for implementing the method
Assignee: Alcatel Lucent SAS
•
Filing: 1997-04-28
•
Granted: 1999-05-18
•
Expires: 2017-04-28
Abstract
Abstract A method for automatically changing software version in a computer system comprising a plurality of stations that are to execute in parallel a plurality of replicas of the same software. A series of successively messages, communication protocol, between a master station and each slave station required for initializing and making necessary preparations at each of the slave stations prior to the version-change actual issued. In this way, without human intervention, all of the stations ensure that do restart after receiving the version-change order do indeed all restart actually executing the new version.
Inventors
- 👤 Olivier Delannoy
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-08 03:26
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/60; G06F8/65
Claims Analysis
Total Claims: 4
Claim 1
Independent Claim
284 words
A method of changing software version in a computer system comprising a plurality of stations, the method being characterized in that it consists in: selecting one station (MA) as a master station, with the other stations (S1, S2) being called slave stations; providing each slave station with a flag (P1, P2); installing the new version (n+1) in each station, while continuing to execute the current version; and in that it consists in the following successively and in this order: the master station sending a first message (M11, M12) to all of the slave stations; on a slave station receiving this first message, it gives its flag an initial value (0) indicating that the new version is not enabled; a second message (M21, M22) is sent by the master station to each slave station; in each slave station that receives the second message, the new version is enabled by performing the preparations necessary for using it next time the slave station is started; the flag of the slave station is given a new value (1) specifying, where appropriate, that preparations have succeeded; and the value of the flag is stored in a non-volatile memory; the master station sends a third message (M31, M32) to all of the slave stations to cause the slave stations to restart; after which the master station restarts; in each slave station that restarts, the value stored in the flag is tested (3) and: if the value indicates that the preparations were successful, the new version is executed (4,5); if the value indicates that the preparations did not succeed, neither the current version nor the new version is executed, and the slave station waits (8) for orders from the master station.
Claim 2
Independent Claim
284 words
A method of changing software version in a computer system comprising a plurality of stations, the method being characterized in that it consists in: selecting one station (MA) as a master station, with the other stations (S1, S2) being called slave stations; providing each slave station with a flag (P1, P2); installing the new version (n+1) in each station, while continuing to execute the current version; and in that it consists in the following successively and in this order: the master station sending a first message (M11, M12) to all of the slave stations; on a slave station receiving this first message, it gives its flag an initial value (0) indicating that the new version is not enabled; a second message (M21, M22) is sent by the master station to each slave station; in each slave station that receives the second message, the new version is enabled by performing the preparations necessary for using it next time the slave station is started; the flag of the slave station is given a new value (1) specifying, where appropriate, that preparations have succeeded; and the value of the flag is stored in a non-volatile memory; the master station sends a third message (M31, M32) to all of the slave stations to cause the slave stations to restart; after which the master station restarts; in each slave station that restarts, the value stored in the flag is tested (3) and: if the value indicates that the preparations were successful, the new version is executed (4,5); if the value indicates that the preparations did not succeed, neither the current version nor the new version is executed, and the slave station waits (8) for orders from the master station.
Claim 3
Dependent Claim
300 words
Apparatus for changing software version in a computer system comprising a plurality of stations, one station (MA) being a master station, and the other stations (S1, S2) being called slave stations; the apparatus being characterized in that it comprises: means for storing a flag (P1, P2) in each slave station; means for installing the new version (n+1) in each station, while continuing to execute the current version; means for issuing a first message (M11, M12) from the master station (MA) to all the slave stations; means in each slave station for responding to reception of the first message by giving the flag of said slave station an initial value (0) indicating that the new version has not been enabled; means for subsequently issuing a second message (M21, M22) from the master station to each slave station; in each slave station, means for enabling the new version by making the preparations necessary for using it next time the slave station is started, the new version being enabled when the slave station receives said second message; and means for giving the flag of said slave station a new value (1) indicating, where appropriate, that the preparations were successful, and for saving said value of the flag in non-volatile memory; means for issuing a third message (M31, M32) from the master station to all of the slave stations to cause said slave stations to restart; means for subsequently causing the master station to restart; and in each slave station, means for testing (3) the stored value of the flag; and if the value indicates that the preparations were successful, executing (4,5) the new version; and if the value indicates that the preparations were not successful, executing neither the current version nor the new version, and waiting (8) for orders from the master station.
Claim 4
Dependent Claim
300 words
Apparatus for changing software version in a computer system comprising a plurality of stations, one station (MA) being a master station, and the other stations (S1, S2) being called slave stations; the apparatus being characterized in that it comprises: means for storing a flag (P1, P2) in each slave station; means for installing the new version (n+1) in each station, while continuing to execute the current version; means for issuing a first message (M11, M12) from the master station (MA) to all the slave stations; means in each slave station for responding to reception of the first message by giving the flag of said slave station an initial value (0) indicating that the new version has not been enabled; means for subsequently issuing a second message (M21, M22) from the master station to each slave station; in each slave station, means for enabling the new version by making the preparations necessary for using it next time the slave station is started, the new version being enabled when the slave station receives said second message; and means for giving the flag of said slave station a new value (1) indicating, where appropriate, that the preparations were successful, and for saving said value of the flag in non-volatile memory; means for issuing a third message (M31, M32) from the master station to all of the slave stations to cause said slave stations to restart; means for subsequently causing the master station to restart; and in each slave station, means for testing (3) the stored value of the flag; and if the value indicates that the preparations were successful, executing (4,5) the new version; and if the value indicates that the preparations were not successful, executing neither the current version nor the new version, and waiting (8) for orders from the master station.
References Cited (Backward Citations)
US4785397A
Cited
US5495610A
Cited
US5410703A
Cited
US5421009A
Cited
US5742829A
Cited
US5784563A
Cited
US5752042A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-05-17 | 2002-11-16 | 2003-05-18 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-05-17 | 2006-11-16 | 2007-05-18 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-05-17 | 2010-11-16 | 2011-05-18 | $7700.00 | Window Closed / Lapsed |