System and method for creating and managing survivable, service hosting networks
Patent 7194543 Issued on March 20, 2007. Estimated Expiration Date: 
November 12, 2022. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.
November 12, 2022. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesActive server management Fault monitor for restarting failed instances of the fault monitor Patent #: 6718486 InventorsAssigneeApplicationNo. 10292256 filed on 11/12/2002US Classes:709/226, Network resource allocating709/223, COMPUTER NETWORK MANAGING709/224, Computer network monitoring709/230, COMPUTER-TO-COMPUTER PROTOCOL IMPLEMENTING714/4, Of network714/13, Prepared backup processor (e.g., initializing cold backup) or updating backup processor (e.g., by checkpoint message)714/39, Monitor recognizes sequence of events (e.g., protocol or logic state analyzer)714/41, For reliability enhancing component (e.g., testing backup spare, or fault injection)714/47Performance monitoring for fault avoidanceExaminersPrimary: Dalencourt, YvesInternational ClassG06F 15/173AbstractThe present invention is directed to a system, method and software product for balancing resource services are always available to match the desired work to be done through the use of “sticky services.”. Sticky services are defined as services that you know you want to have available as resources and as such they need to be present in the environment of cooperative applications; it may be that you want these always present or it may be that you want them present whenever certain conditions occur (see NewWave policy service). The general assumption of distributed systems is to not count on the environment you want being present, or put another way assume failure will occur. Therefore distributed environments like Jini assume all services are transient and will be garbage collected when not in active use. For the inside out approach to work, a mechanism should exist that, when desired, counters the transit design assumptions. This implies that two things are needed: (1) a mechanism for providing services as needed; (2) a mechanism for insuring the correct balance of resource services are always available to match the desired work to be done.Field of SearchNetwork resource allocatingCOMPUTER NETWORK MANAGING Computer network monitoring COMPUTER-TO-COMPUTER PROTOCOL IMPLEMENTING Of network For reliability enhancing component (e.g., testing backup spare, or fault injection) Performance monitoring for fault avoidance Prepared backup processor (e.g., initializing cold backup) or updating backup processor (e.g., by checkpoint message) Monitor recognizes sequence of events (e.g., protocol or logic state analyzer) | |
