Network performance monitor

• US 8,195,478 B2
• Filed: 03/07/2007
• Issued: 06/05/2012
• Est. Priority Date: 03/07/2007
• Status: Expired due to Fees

• Current Assignee: Welch Allyn Incorporated
• Original Assignee: Welch Allyn Incorporated
• Inventors: Petersen, Eric G., Baker, Steven D., Marcaccini, Steven J., Heritage, Mark A.
• Primary Examiner(s): O'Connor, Gerald J.
• Assistant Examiner(s): Patel, Neha
• Application Number:
  US11/683,252
• Publication Number:
  US 20080221918A1
• Time in Patent Office: 1,917 Days
• Field of Search: 705/2, 705/3, 370/241, 370/245
• US Class Current: 705/2
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information

Abstract

Disclosed in this specification is a method for monitoring a network, such as the central monitoring station of a medical facility. Performance data from each of the network components of interest is monitored for compliance with certain component-specific criteria. Responses are generated if the performance data satisfies, or fails to satisfy, such criteria.

Claims

1. A network monitoring system for monitoring a medical network to determine if connected network components are adequately performing without otherwise burdening said network by performing the method comprising the steps of:

a. connecting said system to said network, said medical network comprising a plurality of connected network components, said network components including network devices comprising patient monitoring devices and at least one of wireless infusion pumps, PCs, telephones, PDAs, monitoring stations and servers for obtaining and transmitting life critical data, including waveform data, on said network, network appliances comprising at least one of routers, switches, and hubs for controlling data flow along said network and network-capable applications comprising software run on said network devices and network appliances on said network, wherein said connecting step includes the step of installing said system on a central monitoring system of a medical facility,

b. measuring the actual network performance of data typically traversing the network,

c. receiving network performance data from applications running on at least one connected network component over said network, said performance data relating solely to said first network component'"'"'s connectivity with said network, with at least one other connected network component,

d. selecting a component-specific criteria, wherein the component-specific criteria is selected from a plurality of component-specific criteria based upon the unique identity of the first network component and relating to operational aspects of said network component on the network, such that the selected component-specific criteria corresponds to the first network component,

e. comparing the network performance data from the first network component to the selected component-specific criteria,

f. determining if the network performance data from the first network component satisfies the selected component-specific criteria,

g. generating a first response if the network performance data satisfies the selected component-specific criteria and generating a second response if the performance data does not satisfy the selected component-specific criteria and wherein said network performance data includes end-to-end latency across all connected network components, said end to end latency being directly measured by said measuring step along the actual data path taken between any connected network components over said network and without requiring intermediate or remote monitoring devices or endpoints, and

h. displaying an alarm response selected from the group consisting of the first response and the second response, wherein the alarm response is displayed on a monitor of the central monitoring station and the affected patient monitor, based on a determination that the waveform data is adversely affected, wherein other connected network components are not affected.

2. The system as recited in claim 1, further comprising the step of displaying a second alarm on the first network component, wherein the second alarm corresponds to the alarm response.

3. The system as recited in claim 2, further comprising an access point disposed between the central monitoring station and the first network component.

4. The system as recited in claim 1, wherein the selected component-specific criteria includes a hold-off delay period such that the performance data must satisfy the selected component-specific criteria for the hold-off delay period for the alarm condition to change state.

5. The system as recited in claim 1, wherein the selected component-specific criteria includes hysteresis.

6. The system as recited in claim 1, further comprising the step of recording the performance data, thus producing recorded performance data.

7. The system as recited in claim 6, wherein the recorded performance data is extracted and analyzed.

8. The system as recited in claim 7, further comprising the step of monitoring a trend in the stored performance data for the first network component as a function of time.

9. The system as recited in claim 1, wherein the performance data is selected from the group consisting of number of retries, signal strength data, packet loss data, latency data and combinations thereof.

10. The system as recited in claim 1, further comprising the step of determining a degree to which each of the network components from the plurality of network components deviates from their corresponding component-specific criteria.

11. The system as recited in claim 10, further comprising the step of displaying a list that includes network components ordered by the degree to which the network components deviate from their corresponding component-specific criteria.

12. The system as recited in claim 11, wherein only those network components which fail to satisfy their corresponding component-specific criteria are listed.

13. The system as recited in claim 1, further comprising the step of requesting the performance data from the first network component.

14. The system as recited in claim 1, further comprising the step of evaluating the performance data for the first network component and determining baseline values for the performance data.

15. The system as recited in claim 1, wherein the performance data is selected from the group consisting of jitter, bandwidth, quality of service tags, number of clients, packets transmission and reception counts, byte transmission and reception counts, errors, and combinations thereof.