Multiplex communications – Wide area network – Packet switching
Patent
1997-06-02
2000-08-08
Hafiz, Tariq R.
Multiplex communications
Wide area network
Packet switching
370469, G06F 9445
Patent
active
061013277
DESCRIPTION:
BRIEF SUMMARY
TECHNICAL FIELD OF THE INVENTION
The present invention relates to the replacement of software in an operating computer system, and in particular, to the synchronization of state transfer between processes within an old software to processes within a new software.
BACKGROUND
One aspect of computer software is that it must be periodically updated with revisions, additions and/or deletions in order to continue to provide adequate functionality to the user, to optimize the software and to correct errors and discrepancies that arise throughout the life of the software. As new features are added to software, it is desirable to replace the old software with the new versions as early as possible in order to provide the user with the features of the new software.
In certain types of computing systems, such as stand-alone or batch processing systems, changing software from one version to another presents few obstacles. Typically, the computer system is merely shut down during a period of day when there is little activity and the maintenance personnel are readily available. The old software is then simply removed and replaced by the newer version of the software. Thereafter, the computing system is restarted and all future data processing is done with the new version of the software. This procedure, of course, assumes that the new software has been adequately tested and debugged on an off-line system to the point that the software personnel and the operational management are confident that it will adequately perform the functions for which it is intended without undue interruptions that require halting and then re-starting the entire computing system.
In other types of computing systems, such as modern stored program control (SPC) telecommunications exchange systems (commonly referred to in the industry simply as "switches"), neither the testing of new versions of software nor the changing of software in the system is as easy as in stand-alone or batch processing systems. For example, new versions of software cannot be effectively tested without being placed into actual operation processing calls. The software must be tested while in operation in order to determine whether the software will adequately function under live operating conditions and whether the new portions will properly interface with all of the other software blocks that form a part of an operational SPC switching system. In addition, telecommunications switching systems are virtually never out of operation. Ideally; these systems would run perpetually, without interruption because of the continuous need for communications services within a community. That is, there is a continuous flow of telecommunications traffic being processed through the system even at off hours of the day or night and any interruption in the operation of the switch results in a non desired disruption of the telecommunications traffic. Such a disruption could be extremely damaging to the system's operation and its effectiveness, as well as its acceptance among users or costumers of the system.
These real-time requirements of telecommunications exchange systems place severe constraints on both the testing of enhanced versions of the software, or portions thereof, containing new or improved functionality, as well as the substitution of software containing error corrections or "bug fixes" in the switch without disrupting existing telecommunications traffic being processed by the switch. Therefore, integrating new versions of software components or units into the system using the traditional "edit-compile-link-load-run" approach is not desirable.
Another problem associated with the replacement of software in a operating computer system, such as telecommunications switches, is the state transfer between processes within the old software to processes within the new software, and especially the synchronization thereof. A process uses or comprises resource objects, which are object types that handle information on a hardware resource or an internal data structure. In context of the p
REFERENCES:
patent: 5155837 (1992-10-01), Liu et al.
patent: 5155847 (1992-10-01), Kirouac et al.
patent: 5175828 (1992-12-01), Hall et al.
patent: 5185742 (1993-02-01), Bales et al.
patent: 5212787 (1993-05-01), Baker et al.
patent: 5339430 (1994-08-01), Lundin et al.
patent: 5410703 (1995-04-01), Nilsson et al.
patent: 5606659 (1997-02-01), M.ang.loy
patent: 5654901 (1997-08-01), Boman
Co-Pending Application Nos. 08/849,335, 07/907,294, 08/836,814 Mar. 15, 2000.
Co-Pending Application Nos. 08/765,160 (Not Available) Mar. 15, 2000.
Fuchs Robert
Holte-Rost Anna
Markstrom Ulf
Hafiz Tariq R.
Nguyen-Ba Antony
Telefonaktiebolaget LM Ericsson
LandOfFree
Method of synchronization allowing state transfer does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method of synchronization allowing state transfer, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method of synchronization allowing state transfer will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-1158434