System for exchanging software processes during execution...

Data processing: software development – installation – and managem – Software upgrading or updating

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C717S170000, C717S172000, C717S173000, C717S174000, C717S178000

Reexamination Certificate

active

06634025

ABSTRACT:

BACKGROUND OF THE INVENTION
The invention relates to a communication system comprising a control circuit, which control circuit
includes a message-based operating system, application software and means for exchanging application software, and
when application software is exchanged, causes an old software component to be replaced to carry out a state transfer and stop at a certain point to direct the available messages to a new software component.
Communication systems comprise computer systems or control circuits whose software is to be available for a long time and practically uninterruptedly. In the case of errors in the software, or also because of new requirements, certain software components are to be renewed. In that case the down time of the communication system is to be minimized.
A communication system which has practically no down time when a software component of a switching system is exchanged is known from U.S. Pat. No. 5,155,837. Before the exchange, first the contents and states of all the registers, processes and memory units are saved in a specific memory, while the old software is in operation (column
7
, rows
30
to
36
). The old version of the software is then loaded in a first partition. The new software is consecutively loaded in a second partition. Once the new software has been loaded and tested, the contents and states of all the registers, processes and memory units are transferred from the memory to the new software. This new software is then taken into operation. Then the new software, however, does not start to operate at the process point at which the old software was stopped, but at a defined program point. Besides, not individual software modules or software components are exchanged, but closed software is.
Furthermore, the document “Elektrisches Nachrichtenwesen, Vol. 64, no. 4, 1990, pages 327 to 333” has disclosed an exchange of software components during the operation of, for example, a switching center. In the case of an exchange, the system then causes an old software component to carry out a necessary state transfer. When predefined synchronization points are reached, the old software component is stopped and messages are redirected from the old to the new software component. The new software component is started and the old software component is stopped and removed. Details about the structure of the program provided for the exchange cannot be learnt from the document.
SUMMARY OF THE INVENTION
Therefore, it is an object of the invention to provide a realizable exchange procedure of software components in which procedure the operation is not restricted except during a brief delay period.
The object is achieved by a communication system of the type defined in the opening paragraph, in that the application software includes at least a process with at least an application thread and an exchange thread, in that an old process to be exchanged is at least provided for gathering its states after the application threads of the old process have stopped at an exchange point, and in that the exchange thread of the old process is used at least for transferring the states to a new process through exchange ports.
The exchange procedure according to the invention relates to processes which include, for example, a plurality of threads (sequentially running program partitions) among which there is an exchange thread for controlling the exchange. Due to the invention, a new process is started at the respective program point (exchange point) at which the old process has been stopped. In addition, all the states of the old process are transferred to the new process via an exchange thread of the old process. However, this may only apply to such systems that comprise an operating system that makes it possible to exchange messages between software components (for example CHORUS). Messages are then exchanged between various processes via software interfaces which are referenced ports in the following. The states are then exchanged via exchange ports of the old and the new process.
A process is exchanged so that no other process is affected thereby. The messages arriving from another client (another process) are transmitted to the new process and further processed after the exchange. The exchange is effected in that there is only a brief delay during the processing. Practical investigations have shown that the delay lies in the range of a few milliseconds.
A communication system may be a computer system, a switching center, a computer network or also server systems such as, for example, a video-on-demand server. A computer system comprises at least a computer in which a software component is to be exchanged.
An application thread has a first partition for gathering at least the states of the application thread of an old process to be exchanged, and is used for delivering the gathered states to the exchange thread of the old process. An application thread of a new process has a second partition for taking over the states from the exchange thread of the old process and for reconstructing objects related to the states.
The exchange of a process is introduced by a replacement server. This server is included in the control circuit as a further software component and is used for loading and starting a process and for identifying whether a newly started process is to replace an old process. A maintenance device delivers a new process to the replacement server via a transmission medium.
When a plurality of processes are to be exchanged, they are exchanged consecutively. Thus first a first process is exchanged and then the following processes in succession. When a plurality of processes are to be exchanged, the control can be taken over by the replacement server.
Once a new process has been loaded and started, which process is used for exchanging an old process, first a jump is made to an exchange point that corresponds to the exchange point of the old process in that normal program routines are skipped.
The invention likewise relates to a computer system comprising at least a computer and a method of exchanging software components.
These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.


REFERENCES:
patent: 4954941 (1990-09-01), Redman
patent: 5155837 (1992-10-01), Liu et al.
patent: 5210854 (1993-05-01), Beaverton et al.
patent: 5274808 (1993-12-01), Miyao et al.
patent: 5295263 (1994-03-01), Kojima et al.
patent: 5359730 (1994-10-01), Marron
patent: 5410703 (1995-04-01), Nilsson et al.
patent: 5511194 (1996-04-01), Shirakata et al.
patent: 5555418 (1996-09-01), Nilsson et al.
patent: 5613133 (1997-03-01), Bell et al.
patent: 5619698 (1997-04-01), Lillich et al.
patent: 5682533 (1997-10-01), Siljestroemer
patent: 5761504 (1998-06-01), Corrigan et al.
patent: 5764992 (1998-06-01), Kullick et al.
patent: 5797016 (1998-08-01), Chen et al.
patent: 5845077 (1998-12-01), Fawcett
patent: 6049671 (2000-04-01), Slivka et al.
patent: 6073214 (2000-06-01), Fawcett
patent: 6101327 (2000-08-01), Holte-Rost et al.
patent: 6161218 (2000-12-01), Taylor
patent: 6202205 (2001-03-01), Saboff et al.
patent: 6327617 (2001-12-01), Fawcett
Paindaveine et al., “Process vs. Task Migration” Proceedings of the 29th Annual Hawaii International Conference on System Sciences, IEEE, 1996.*
Barak et al.., “Performance of PVM with Preemptive Process Migration Scheme”, Proceedings of ICCSSE, IEEE, 1996.*
Gupta, D.; Jalote, P.; Baura, G.; “A Formal Framework for On-line Software Version Change”; IEEE Transactions on Software Engineering; vol. 22, No. 2, pp. 120-131, Feb. 1996.*
Gupta, D.; Jalote, P.; “Increasing System Availability through On-line Software Version Change”; The Twenty-Third International Symposium on Fault-Tolerant Computing; pp. 30-35, Jun. 1993.*
Fujita, K.; Kanemaki, K.; Ishimoto, H.; Oda, N.; “Dynamic Program Updating Method for Packet Switching Systems”; NTT R & D, vol. 42, No. 8, pp. 1027-1036. (abstract) INSPEC [online]. Retrieved from Dialog Information Services. Accession No. 4551244

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

System for exchanging software processes during execution... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with System for exchanging software processes during execution..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and System for exchanging software processes during execution... will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-3174934

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.