US20090059807A1 - Systems and Methods to Monitor a Network - Google Patents
Systems and Methods to Monitor a Network Download PDFInfo
- Publication number
- US20090059807A1 US20090059807A1 US12/201,178 US20117808A US2009059807A1 US 20090059807 A1 US20090059807 A1 US 20090059807A1 US 20117808 A US20117808 A US 20117808A US 2009059807 A1 US2009059807 A1 US 2009059807A1
- Authority
- US
- United States
- Prior art keywords
- network
- data packets
- edge switch
- reflected
- processor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/087—Jitter
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
- H04L41/5067—Customer-centric QoS measurements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
- H04L43/0829—Packet loss
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/0864—Round trip delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0888—Throughput
Definitions
- the present disclosure relates generally to the monitoring of networks.
- Ethernet is a local-area network architecture that was developed in the late 1970s for use in offices, e.g., to interconnect computers to each other and to a common printer.
- companies have begun to develop ways to expand Ethernet principles to wide area networks, e.g., using Internet routers that are interconnected in various ways. The result has been the creation of switched metro Ethernet data networks.
- a service can be considered a high level service and may be offered at a premium price if it has certain characteristics that are beneficial to customers.
- a service provider may offer a service in which data is delivered at a relatively high packet delivery rate.
- a service level agreement between a service provider and a customer may state that the data will be delivered at or above a particular packet delivery rate and the customer will pay a particular fee for that promised packet delivery rate.
- FIG. 1 is a diagram of a switched metro Ethernet system
- FIG. 2 is a flow chart to illustrate a method for collecting one or more metrics related to a switched metro Ethernet system and presenting those metrics to a user;
- FIG. 3 is a general diagram representative of an embodiment of a graphical user interface that can be used to present one or more metrics related to a switched metro Ethernet system
- FIG. 4 is a general diagram representative of another embodiment of a graphical user interface that can be used to present one or more metrics related to a switched metro Ethernet system.
- a method for monitoring a network includes injecting a plurality of data packets into the network.
- the data packets are transmitted between a source device and a destination device.
- a plurality of reflected data packets is collected.
- the plurality of reflected data packets are reflected from the destination device to the source device.
- the plurality of reflected data packets includes at least a portion of the data packets that are injected into the network.
- the method further includes determining a total number of the reflected data packets.
- a packet delivery rate, a latency value, and a jitter value can be calculated based at least partially on the total number of reflected data packets. Further, the packet delivery rate, the latency value, and the jitter value can be reported to a user.
- the network is a switched metro Ethernet network and the plurality of data packets are created at a server and injected into an edge switch of the switched metro Ethernet network. Particularly, the plurality of data packets is created by a service assurance agent (SAA) within the server.
- SAA service assurance agent
- the source device is a first edge switch of a switched metro Ethernet network
- the destination device is a second edge switch of the switched metro Ethernet network
- the first edge switch is coupled to the second edge switch via a core system of the switched metro Ethernet network.
- a server in another embodiment, includes a processor and a memory device that is coupled to the processor.
- a service assurance agent (SAA) is embedded within the memory device and the SAA is executable by the processor.
- the SAA includes instructions to inject a plurality of data packets into a switched metro Ethernet network from a source device to a destination device.
- the SAA includes instructions to collect a plurality of data packets that are reflected from the destination device back to the source device.
- a switched metro Ethernet network includes a core system.
- a first edge switch and a second edge switch are coupled to the core system.
- a computer program is embedded within the server.
- the computer program includes instructions to calculate a data packet delivery rate between the first edge switch and the second edge switch.
- a switched metro Ethernet network is shown and is generally designated 100 .
- the switched metro Ethernet network 100 includes a core system 102 .
- the core system 102 includes a plurality of switches and routers that can be used to route network traffic through the core system 102 .
- the switches and routers are optical equipment.
- a first edge switch 104 is coupled to the core system 102 .
- a first customer premises equipment (CPE) 106 is coupled to the edge switch 104 .
- FIG. 1 further shows a first user computer 108 coupled to the first CPE 106 .
- the CPE 106 can be a modem, a gateway, or a router.
- the first user computer 108 can be a desktop computer, a laptop computer, a handheld computer, or any other computer device.
- the first user computer 108 includes a processor 110 and a display 112 that is coupled to the processor 110 .
- a graphical user interface (GUI) 114 can be presented to a user at the first user computer 108 via the display 112 .
- information regarding the switched metro Ethernet network 100 including one or more metrics concerning the operation of the switched metro Ethernet network 100 can be presented to a user via the GUI 114 .
- FIG. 1 further shows a memory device 116 that is coupled to the processor 110 within the first user computer 108 .
- a server 118 can be coupled to the first edge switch 104 .
- the server 118 includes a processor 120 and a memory device 122 .
- a service assurance agent (SAA) 124 is stored within the server 118 , e.g., within the memory device 122 .
- the SAA 124 is a computer program that can have one or more instructions that can be executed by the processor 120 in order to collect and calculate one or more metrics concerning the operation of the switched metro Ethernet network 100 . Further, the SAA 124 can present the metrics or any data derived from the metrics to the user computer 108 via the GUI 114 .
- FIG. 1 further shows that a second edge switch 126 is coupled to the core system 102 . Moreover, a second CPE 128 is connected to the second edge switch 126 . As illustrated in FIG. 1 , a second user computer 130 is also coupled to the second CPE 128 . In a particular embodiment, the second user computer 130 includes a processor 132 and a display 134 coupled thereto. Moreover, as illustrated in FIG. 1 , a GUI 136 can be presented to a user at the second user computer 130 . Particularly, information regarding the switched metro Ethernet network 100 including one or more metrics concerning the operation of the switched metro Ethernet network 100 can be presented to a user via the GUI 136 . FIG. 1 also shows a memory device 138 that is coupled to the processor 132 .
- the first user computer 108 can be networked to the second user computer 130 by the first CPE 106 , the first edge switch 104 , the core system 102 , the second edge switch 126 and the second CPE 128 .
- multiple offices of a single company at different locations can be networked via the switched metro Ethernet network 100 .
- the method includes periodically creating a predetermined number of artificial data packets.
- the artificial data packets are injected into the network from a source Internet protocol (IP) address toward a destination IP address, e.g., from the first edge switch 104 ( FIG. 1 ) to the second edge switch 126 ( FIG. 1 ).
- IP Internet protocol
- the artificial data packets can be created and injected into the network every fifteen minutes or less.
- the packets are reflected, or otherwise returned, from the destination IP address back to the source IP address, e.g., from the second edge switch 126 ( FIG. 1 ) back to the first edge switch 104 ( FIG. 1 ).
- the artificial data packets that have been reflected back to the source IP address are collected, e.g., by the SAA 124 ( FIG. 1 ) within the server 118 ( FIG. 1 ) coupled to the first edge switch 104 ( FIG. 1 ).
- a total number of packets that are reflected, or otherwise returned, to the source IP address is determined.
- a packet delivery rate is calculated based on the total number of returned packets.
- the packet delivery rate is a measure of the percentage of packets that reach the destination IP address and that are reflected back to the source IP address. Packet delivery rate can be determined using the following formula:
- the SAA 124 in order to determine a more reliable value for packet delivery rate, several metrics can be used by the SAA 124 ( FIG. 1 ).
- Table 1 shows several exemplary, non-limiting metrics that can be used by the SAA 124 ( FIG. 1 ) in order to determine the packet delivery rate.
- C rttMonLatestJitterStatsPacketLossDS The number of packets lost when sent from destination to source
- D RttMonLatestJitterStatsPacketOutOfSequence
- E rttMonLatestJitterStatsPacketMIA
- F RttMonLatestJitterStatsPacketLateArrival The number of packets that arrived after the timeout
- the metrics shown in Table 1 can be used to determine a packet delivery rate using the following formula:
- a latency value is calculated based on the total number of returned packets.
- latency is the delay that the packets experience as they flow through the network, e.g., from the first edge switch 104 to the second edge switch 126 and back.
- latency can include the time that packets spend in buffers and the propagation delay.
- several metrics can be used by the SAA 124 ( FIG. 1 ) in order to determine latency.
- Table 2 shows several exemplary, non-limiting metrics that can be used by the SAA 124 ( FIG. 1 ) in order to determine the latency value.
- rttMonLatestJitterStatsNumOfRTT The number of RTTs that are successfully measured rttMonLatestJitterStatsRTTSum
- the sum of RTTs that are successfully measured rttMonLatestJitterStatsRTTMin The minimum of RTTs that were successfully measured rttMonLatestJitterStatsRTTMax
- the maximum of RTTs that were successfully measured rttMonLatestJitterStatsRTTSum2Low The sum of squares of RTTs that are successfully measured rttMonLatestJitterStatsRTTSum2High (low/high order 32 bits)
- rttMonJitterStatsOWSumSD The sum of one way times from source to destination rttMonJitterStatsOWMinSD The minimum of all one way times from source to destination.
- rttMonJitterStatsOWMaxSD The maximum of all one way times from source to destination.
- rttMonJitterStatsOWSumDS The sum of one way times from destination to source.
- rttMonJitterStatsOWMinDS The minimum of all one way times from destination to source.
- rttMonJitterStatsOWMaxDS The maximum of all one way times from destination to source.
- rttMonJitterStatsNumOfOW The number of one way times that are successfully measured.
- the RTT numbers can be divided by two. Further, rttMonLatestJitterStatsRTTSum2 Low and rttMonLatestJitterStatsRTTSum2High are optional metrics and can be collected if a calculation of a standard deviation is desired.
- a jitter value is calculated based on the total number of returned packets.
- jitter is defined as the variance in the inter-packet arrival rate at the destination.
- several metrics can be used by the SAA 124 ( FIG. 1 ) in order to determine latency.
- Table 3 shows several exemplary, non-limiting metrics that can be used by the SAA 124 ( FIG. 1 ) in order to determine the Jitter value.
- rttMonJitterStatsMinOfPositivesSD The minimum of absolute values of all positive jitter values from packets sent from source to destination.
- rttMonJitterStatsMaxOfPositivesSD The maximum of absolute values of all positive jitter values from packets sent from source to destination.
- rttMonJitterStatsNumOfPositivesSD The sum of number of all positive jitter values from packets sent from source to destination.
- rttMonJitterStatsSumOfPositivesSD The sum of all positive jitter values from packets sent from source to destination.
- rttMonJitterStatsSum2PositivesSDLow The sum of square of RTT's of all positive jitter values from packets sent from source to destination (low order 32 bits).
- rttMonJitterStatsMinOfNegativesSD The minimum of all negative jitter values from packets sent from source to destination.
- rttMonJitterStatsMaxOfNegativesSD The maximum of all negative jitter values from packets sent from source to destination.
- rttMonJitterStatsNumOfNegativesSD The sum of number of all negative jitter values from packets sent from source to destination.
- rttMonJitterStatsSumOfNegativesSD The sum of RTT's of all negative jitter values from packets sent from source to destination.
- rttMonJitterStatsSum2NegativesSDLow The sum of square of RTT's of all negative jitter values from packets sent from source to destination (low order 32 bits).
- rttMonJitterStatsSum2NegativesSDHigh The sum of square of RTT's of all negative jitter values from packets sent from source to destination (high order 32 bits).
- rttMonJitterStatsMinOfPositivesDS The minimum of absolute values of all positive jitter values from packets sent from destination to source.
- rttMonJitterStatsMaxOfPositivesDS The maximum of absolute values of all positive jitter values from packets sent from destination to source.
- rttMonJitterStatsNumOfPositivesDS The sum of number of all positive jitter values from packets sent from destination to source.
- rttMonJitterStatsSumOfPositivesDS The sum of all positive jitter values from packets sent from destination to source.
- rttMonJitterStatsSum2PositivesDSLow The sum of square of RTT's of all positive jitter values from packets sent from destination to source (low order 32 bits).
- rttMonJitterStatsSum2PositivesDSHigh sum of square of RTT's of all positive jitter values from packets sent from destination to source (high order 32 bits).
- rttMonJitterStatsMinOfNegativesDS The minimum of all negative jitter values from packets sent from destination to source.
- rttMonJitterStatsMaxOfNegativesDS The maximum of all negative jitter values from packets sent from destination to source.
- rttMonJitterStatsNumOfNegativesDS The sum of number of all negative jitter values from packets sent from destination to source.
- rttMonJitterStatsSumOfNegativesDS The sum of RTT's of all negative jitter values from packets sent from destination to source.
- rttMonJitterStatsSum2NegativesDSLow The sum of square of RTT's of all negative jitter values from packets sent from destination to source (low order 32 bits).
- rttMonJitterStatsSum2NegativesDSHigh The sum of square of RTT's of all negative jitter values from packets sent from destination to source (high order 32 bits).
- a maximum jitter value from a source to a destination is defined as the maximum between these values: rttMonJitterStatsNumOfNegativesSD and rttMonJitterStatsNumOfPositivesSD.
- the metrics described herein are simple network management protocol management information base (SNMP MIB) objects that can be collected using an SNMP collection mechanism.
- SNMP MIB simple network management protocol management information base
- the packet delivery rate, the latency value, and the jitter value are reported to a user.
- the packet delivery rate, the latency value, and the jitter value are reported to the user via a GUI 114 , 136 ( FIG. 1 ) presented at one of the user computers 108 , 130 ( FIG. 1 ) and the method ends at state 218 .
- the metrics described above and collected by the SAA 124 can be used to enhance or optimize the switched metro Ethernet network ( FIG. 1 ). For example, if a user notices that a packet delivery rate between two locations is not at or above a stated value in a service level agreement, the user can contact the service provider who can verify the packet delivery rate and then, determine the cause of the problem and correct the problem, if possible.
- GUI 300 an exemplary, non-limiting embodiment of a graphical user interface (GUI) is shown and is generally designated 300 .
- the GUI 300 includes a graphical representation of a user's network 302 showing a core network 304 and different CPE 306 and their locations.
- the GUI 300 includes an information window 308 that provides information relevant to the CPE 306 when each is selected by a user.
- FIG. 3 also shows that the GUI 300 includes an information table 310 that provides network trouble information, e.g., device type, problem severity, reason, and date/time.
- FIG. 4 shows another exemplary, non-limiting embodiment of a GUI, designated 400 .
- the GUI 400 shown in FIG. 4 includes a matrix 402 of information blocks 404 .
- a user can use the GUI 400 to determine a jitter value, a latency value, and a packet delivery rate between two CPEs within a switched metro Ethernet network.
- the GUI 400 can indicate a level of service provided for in a service level agreement.
- the GUI 400 can indicate the level of service by providing a certain color within the information blocks 404 , e.g., bronze, silver, or gold.
- the system and method for collecting and presenting service level agreement metrics disclosed herein provides the capability for determining jitter, latency, and packet delivery rate between two edge switches within a switched metro Ethernet.
- Each edge switch is coupled to a CPE and each edge switch represents the outer boundary of the portion of a switched metro Ethernet that is under the control of a service provider.
- the system and method can provide a close approximation of the jitter, latency, and packet delivery rate between the two CPEs coupled to the edge switches.
- a GUI is provided for presenting the jitter, latency, and packet delivery rate information to a user via a computer. Using the information presented via the GUI, a user can verify that the terms of a service level agreement are being met.
Abstract
Systems and methods to monitor a network are provided. A particular method includes determining a data packet delivery rate between a first edge switch and a second edge switch coupled to a network. The method also includes sending the data packet delivery rate to a user device, operably coupled to a customer equipment side of the first edge switch, as graphical user interface display data.
Description
- The present application claims priority from and is a continuation of patent application Ser. No. 10/975,022 filed on Oct. 27, 2004 and entitled “System and Method for Collection and Presenting Service Level Agreement Metrics in a Switched Metro Ethernet Network,” the contents of which are expressly incorporated herein by reference in their entirety.
- The present disclosure relates generally to the monitoring of networks.
- Ethernet is a local-area network architecture that was developed in the late 1970s for use in offices, e.g., to interconnect computers to each other and to a common printer. In recent years, companies have begun to develop ways to expand Ethernet principles to wide area networks, e.g., using Internet routers that are interconnected in various ways. The result has been the creation of switched metro Ethernet data networks.
- In an effort to market switched metro Ethernet services, service providers can offer varying levels of service for different prices. Moreover, a service can be considered a high level service and may be offered at a premium price if it has certain characteristics that are beneficial to customers. For example, a service provider may offer a service in which data is delivered at a relatively high packet delivery rate. Further, a service level agreement between a service provider and a customer may state that the data will be delivered at or above a particular packet delivery rate and the customer will pay a particular fee for that promised packet delivery rate. However, it can be difficult to provide an indication to a customer that the service they are receiving is meeting the level agreed to in the service level agreement.
- Accordingly, there is a need for a system and method for collecting and presenting service level agreement metrics in a switched metro Ethernet network.
-
FIG. 1 is a diagram of a switched metro Ethernet system; -
FIG. 2 is a flow chart to illustrate a method for collecting one or more metrics related to a switched metro Ethernet system and presenting those metrics to a user; -
FIG. 3 is a general diagram representative of an embodiment of a graphical user interface that can be used to present one or more metrics related to a switched metro Ethernet system; and -
FIG. 4 is a general diagram representative of another embodiment of a graphical user interface that can be used to present one or more metrics related to a switched metro Ethernet system. - A method for monitoring a network includes injecting a plurality of data packets into the network. The data packets are transmitted between a source device and a destination device. A plurality of reflected data packets is collected. In a particular embodiment, the plurality of reflected data packets are reflected from the destination device to the source device. Also, the plurality of reflected data packets includes at least a portion of the data packets that are injected into the network.
- In a particular embodiment, the method further includes determining a total number of the reflected data packets. A packet delivery rate, a latency value, and a jitter value can be calculated based at least partially on the total number of reflected data packets. Further, the packet delivery rate, the latency value, and the jitter value can be reported to a user. Also, in a particular embodiment, the network is a switched metro Ethernet network and the plurality of data packets are created at a server and injected into an edge switch of the switched metro Ethernet network. Particularly, the plurality of data packets is created by a service assurance agent (SAA) within the server. Further, in a particular embodiment, the source device is a first edge switch of a switched metro Ethernet network, the destination device is a second edge switch of the switched metro Ethernet network, and the first edge switch is coupled to the second edge switch via a core system of the switched metro Ethernet network.
- In another embodiment, a server includes a processor and a memory device that is coupled to the processor. A service assurance agent (SAA) is embedded within the memory device and the SAA is executable by the processor. In a particular embodiment, the SAA includes instructions to inject a plurality of data packets into a switched metro Ethernet network from a source device to a destination device. Moreover, the SAA includes instructions to collect a plurality of data packets that are reflected from the destination device back to the source device.
- In yet another embodiment, a switched metro Ethernet network includes a core system. A first edge switch and a second edge switch are coupled to the core system. Further, a computer program is embedded within the server. In a particular embodiment, the computer program includes instructions to calculate a data packet delivery rate between the first edge switch and the second edge switch.
- Referring to
FIG. 1 , a switched metro Ethernet network is shown and is generally designated 100. As shown, the switched metro Ethernetnetwork 100 includes acore system 102. Particularly, thecore system 102 includes a plurality of switches and routers that can be used to route network traffic through thecore system 102. In a particular embodiment, the switches and routers are optical equipment. As illustrated inFIG. 1 , afirst edge switch 104 is coupled to thecore system 102. Also, a first customer premises equipment (CPE) 106 is coupled to theedge switch 104.FIG. 1 further shows afirst user computer 108 coupled to thefirst CPE 106. In a particular embodiment, the CPE 106 can be a modem, a gateway, or a router. Further, thefirst user computer 108 can be a desktop computer, a laptop computer, a handheld computer, or any other computer device. - In a particular embodiment, the
first user computer 108 includes aprocessor 110 and adisplay 112 that is coupled to theprocessor 110. Moreover, as illustrated inFIG. 1 , a graphical user interface (GUI) 114 can be presented to a user at thefirst user computer 108 via thedisplay 112. In a particular embodiment, information regarding the switched metro Ethernetnetwork 100 including one or more metrics concerning the operation of the switched metro Ethernetnetwork 100 can be presented to a user via theGUI 114.FIG. 1 further shows amemory device 116 that is coupled to theprocessor 110 within thefirst user computer 108. - As shown in
FIG. 1 , aserver 118 can be coupled to thefirst edge switch 104. In a particular embodiment, theserver 118 includes aprocessor 120 and amemory device 122. Further, in a particular embodiment, a service assurance agent (SAA) 124 is stored within theserver 118, e.g., within thememory device 122. In a particular embodiment, the SAA 124 is a computer program that can have one or more instructions that can be executed by theprocessor 120 in order to collect and calculate one or more metrics concerning the operation of the switched metro Ethernetnetwork 100. Further, the SAA 124 can present the metrics or any data derived from the metrics to theuser computer 108 via theGUI 114. -
FIG. 1 further shows that asecond edge switch 126 is coupled to thecore system 102. Moreover, asecond CPE 128 is connected to thesecond edge switch 126. As illustrated inFIG. 1 , asecond user computer 130 is also coupled to thesecond CPE 128. In a particular embodiment, thesecond user computer 130 includes aprocessor 132 and adisplay 134 coupled thereto. Moreover, as illustrated inFIG. 1 , aGUI 136 can be presented to a user at thesecond user computer 130. Particularly, information regarding the switched metro Ethernetnetwork 100 including one or more metrics concerning the operation of the switched metro Ethernetnetwork 100 can be presented to a user via theGUI 136.FIG. 1 also shows amemory device 138 that is coupled to theprocessor 132. - With this configuration of structure, the
first user computer 108 can be networked to thesecond user computer 130 by thefirst CPE 106, thefirst edge switch 104, thecore system 102, thesecond edge switch 126 and thesecond CPE 128. In a particular example, multiple offices of a single company at different locations can be networked via the switchedmetro Ethernet network 100. - Referring to
FIG. 2 , a method for collecting one or more metrics related to a switched metro Ethernet system and for presenting those metrics to a user is disclosed. Commencing atblock 200, the method includes periodically creating a predetermined number of artificial data packets. Atblock 202, the artificial data packets are injected into the network from a source Internet protocol (IP) address toward a destination IP address, e.g., from the first edge switch 104 (FIG. 1 ) to the second edge switch 126 (FIG. 1 ). In an illustrative embodiment, the artificial data packets can be created and injected into the network every fifteen minutes or less. Moving to block 204, the packets are reflected, or otherwise returned, from the destination IP address back to the source IP address, e.g., from the second edge switch 126 (FIG. 1 ) back to the first edge switch 104 (FIG. 1 ). Next, atblock 206, the artificial data packets that have been reflected back to the source IP address are collected, e.g., by the SAA 124 (FIG. 1 ) within the server 118 (FIG. 1 ) coupled to the first edge switch 104 (FIG. 1 ). - Moving to block 208, a total number of packets that are reflected, or otherwise returned, to the source IP address is determined. At
block 210, a packet delivery rate is calculated based on the total number of returned packets. In a particular embodiment, the packet delivery rate is a measure of the percentage of packets that reach the destination IP address and that are reflected back to the source IP address. Packet delivery rate can be determined using the following formula: -
PDR=(packets delivered to destination)/(packets offered at source) - In a particular embodiment, in order to determine a more reliable value for packet delivery rate, several metrics can be used by the SAA 124 (
FIG. 1 ). Table 1 shows several exemplary, non-limiting metrics that can be used by the SAA 124 (FIG. 1 ) in order to determine the packet delivery rate. -
TABLE 1 Exemplary, non-limiting metrics used by the SAA in order to determine a Packet Delivery Rate. Variable Measurement Description A rttMonLatestJitterStatsNumOfRTT The number of round trip times (RTTs) that are successfully measured B rttMonLatestJitterStatsPacketLossSD The number of packets lost when sent from source to destination. C rttMonLatestJitterStatsPacketLossDS The number of packets lost when sent from destination to source D RttMonLatestJitterStatsPacketOutOfSequence The number of packets arrived out of sequence E rttMonLatestJitterStatsPacketMIA The number of packets that are lost for which we cannot determine the direction. F RttMonLatestJitterStatsPacketLateArrival The number of packets that arrived after the timeout - Moreover, in a particular embodiment, the metrics shown in Table 1 can be used to determine a packet delivery rate using the following formula:
-
PDR=(ΣA*100)/(ΣA+ΣB+ΣC+ΣD+ΣE+ΣF) - Returning to the description of
FIG. 2 , atblock 212, a latency value is calculated based on the total number of returned packets. In an illustrative embodiment, latency is the delay that the packets experience as they flow through the network, e.g., from thefirst edge switch 104 to thesecond edge switch 126 and back. Particularly, latency can include the time that packets spend in buffers and the propagation delay. In a particular embodiment, several metrics can be used by the SAA 124 (FIG. 1 ) in order to determine latency. Table 2 shows several exemplary, non-limiting metrics that can be used by the SAA 124 (FIG. 1 ) in order to determine the latency value. -
TABLE 2 Exemplary, non-limiting metrics used by the SAA in order to determine a latency value. Measurement Description rttMonLatestJitterStatsNumOfRTT The number of RTTs that are successfully measured rttMonLatestJitterStatsRTTSum The sum of RTTs that are successfully measured rttMonLatestJitterStatsRTTMin The minimum of RTTs that were successfully measured rttMonLatestJitterStatsRTTMax The maximum of RTTs that were successfully measured rttMonLatestJitterStatsRTTSum2Low The sum of squares of RTTs that are successfully measured rttMonLatestJitterStatsRTTSum2High (low/high order 32 bits) rttMonJitterStatsOWSumSD The sum of one way times from source to destination rttMonJitterStatsOWMinSD The minimum of all one way times from source to destination. rttMonJitterStatsOWMaxSD The maximum of all one way times from source to destination. rttMonJitterStatsOWSumDS The sum of one way times from destination to source. rttMonJitterStatsOWMinDS The minimum of all one way times from destination to source. rttMonJitterStatsOWMaxDS The maximum of all one way times from destination to source. rttMonJitterStatsNumOfOW The number of one way times that are successfully measured. - In a particular embodiment, in order to calculate latency in one direction, e.g., from the first edge switch 104 (
FIG. 1 ) to the second edge switch 126 (FIG. 1 ), the RTT numbers can be divided by two. Further, rttMonLatestJitterStatsRTTSum2 Low and rttMonLatestJitterStatsRTTSum2High are optional metrics and can be collected if a calculation of a standard deviation is desired. - Continuing the description of
FIG. 2 , atblock 214, a jitter value is calculated based on the total number of returned packets. In a particular embodiment, jitter is defined as the variance in the inter-packet arrival rate at the destination. In a particular embodiment, several metrics can be used by the SAA 124 (FIG. 1 ) in order to determine latency. Table 3 shows several exemplary, non-limiting metrics that can be used by the SAA 124 (FIG. 1 ) in order to determine the Jitter value. -
TABLE 3 Exemplary, non-limiting metrics used by the SAA in order to determine a jitter value. Measurement Description rttMonJitterStatsMinOfPositivesSD The minimum of absolute values of all positive jitter values from packets sent from source to destination. rttMonJitterStatsMaxOfPositivesSD The maximum of absolute values of all positive jitter values from packets sent from source to destination. rttMonJitterStatsNumOfPositivesSD The sum of number of all positive jitter values from packets sent from source to destination. rttMonJitterStatsSumOfPositivesSD The sum of all positive jitter values from packets sent from source to destination. rttMonJitterStatsSum2PositivesSDLow The sum of square of RTT's of all positive jitter values from packets sent from source to destination (low order 32 bits). rttMonJitterStatsSum2PositivesSDHigh The sum of square of RTT's of all positive jitter values from packets sent from source to destination (high order 32 bits). rttMonJitterStatsMinOfNegativesSD The minimum of all negative jitter values from packets sent from source to destination. rttMonJitterStatsMaxOfNegativesSD The maximum of all negative jitter values from packets sent from source to destination. rttMonJitterStatsNumOfNegativesSD The sum of number of all negative jitter values from packets sent from source to destination. rttMonJitterStatsSumOfNegativesSD The sum of RTT's of all negative jitter values from packets sent from source to destination. rttMonJitterStatsSum2NegativesSDLow The sum of square of RTT's of all negative jitter values from packets sent from source to destination (low order 32 bits). rttMonJitterStatsSum2NegativesSDHigh The sum of square of RTT's of all negative jitter values from packets sent from source to destination (high order 32 bits). rttMonJitterStatsMinOfPositivesDS The minimum of absolute values of all positive jitter values from packets sent from destination to source. rttMonJitterStatsMaxOfPositivesDS The maximum of absolute values of all positive jitter values from packets sent from destination to source. rttMonJitterStatsNumOfPositivesDS The sum of number of all positive jitter values from packets sent from destination to source. rttMonJitterStatsSumOfPositivesDS The sum of all positive jitter values from packets sent from destination to source. rttMonJitterStatsSum2PositivesDSLow The sum of square of RTT's of all positive jitter values from packets sent from destination to source (low order 32 bits). rttMonJitterStatsSum2PositivesDSHigh The sum of square of RTT's of all positive jitter values from packets sent from destination to source (high order 32 bits). rttMonJitterStatsMinOfNegativesDS The minimum of all negative jitter values from packets sent from destination to source. rttMonJitterStatsMaxOfNegativesDS The maximum of all negative jitter values from packets sent from destination to source. rttMonJitterStatsNumOfNegativesDS The sum of number of all negative jitter values from packets sent from destination to source. rttMonJitterStatsSumOfNegativesDS The sum of RTT's of all negative jitter values from packets sent from destination to source. rttMonJitterStatsSum2NegativesDSLow The sum of square of RTT's of all negative jitter values from packets sent from destination to source (low order 32 bits). rttMonJitterStatsSum2NegativesDSHigh The sum of square of RTT's of all negative jitter values from packets sent from destination to source (high order 32 bits). - In a particular embodiment, to calculate an average jitter value from a source to destination the following equation can be used:
-
(rttMonJitterStatsSumOfPositivesSD+rttMonJitterStatsSumOfNegativesSD)/(rttMonJitterStatsNumOfPositivesSD+rttMonJitterStatsNumOfNegativesSD) - Further, to calculate an average jitter value from a destination to a source, the following equation can be used:
-
(rttMonJitterStatsSumOfPositivesDS+rttMonJitterStatsSumOfNegativesDS)/(rttMonJitterStatsNumOfPositivesDS+rttMonJifterStatsNumOfNegativesDS) - Additionally, a maximum jitter value from a source to a destination is defined as the maximum between these values: rttMonJitterStatsNumOfNegativesSD and rttMonJitterStatsNumOfPositivesSD.
- In an illustrative embodiment, the metrics described herein are simple network management protocol management information base (SNMP MIB) objects that can be collected using an SNMP collection mechanism.
- Returning to
FIG. 2 , atblock 216, the packet delivery rate, the latency value, and the jitter value are reported to a user. In a particular embodiment, the packet delivery rate, the latency value, and the jitter value are reported to the user via aGUI 114, 136 (FIG. 1 ) presented at one of theuser computers 108, 130 (FIG. 1 ) and the method ends atstate 218. - In a particular embodiment, the metrics described above and collected by the SAA 124 (
FIG. 1 ) can be used to enhance or optimize the switched metro Ethernet network (FIG. 1 ). For example, if a user notices that a packet delivery rate between two locations is not at or above a stated value in a service level agreement, the user can contact the service provider who can verify the packet delivery rate and then, determine the cause of the problem and correct the problem, if possible. - Referring now to
FIG. 3 , an exemplary, non-limiting embodiment of a graphical user interface (GUI) is shown and is generally designated 300. As shown, theGUI 300 includes a graphical representation of a user'snetwork 302 showing acore network 304 anddifferent CPE 306 and their locations. Further, theGUI 300 includes aninformation window 308 that provides information relevant to theCPE 306 when each is selected by a user.FIG. 3 also shows that theGUI 300 includes an information table 310 that provides network trouble information, e.g., device type, problem severity, reason, and date/time. -
FIG. 4 shows another exemplary, non-limiting embodiment of a GUI, designated 400. TheGUI 400 shown inFIG. 4 includes amatrix 402 of information blocks 404. A user can use theGUI 400 to determine a jitter value, a latency value, and a packet delivery rate between two CPEs within a switched metro Ethernet network. Further, theGUI 400 can indicate a level of service provided for in a service level agreement. In a particular embodiment, theGUI 400 can indicate the level of service by providing a certain color within the information blocks 404, e.g., bronze, silver, or gold. - With the configuration of structure described above, the system and method for collecting and presenting service level agreement metrics disclosed herein provides the capability for determining jitter, latency, and packet delivery rate between two edge switches within a switched metro Ethernet. Each edge switch is coupled to a CPE and each edge switch represents the outer boundary of the portion of a switched metro Ethernet that is under the control of a service provider. As such, the system and method can provide a close approximation of the jitter, latency, and packet delivery rate between the two CPEs coupled to the edge switches. Further, a GUI is provided for presenting the jitter, latency, and packet delivery rate information to a user via a computer. Using the information presented via the GUI, a user can verify that the terms of a service level agreement are being met.
- The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
Claims (20)
1. A method, comprising:
determining a data packet delivery rate between a first edge switch coupled to a network and a second edge switch coupled to the network; and
sending the data packet delivery rate to a user device, operably coupled to a customer equipment side of the first edge switch, as graphical user interface display data.
2. The method of claim 1 , wherein the data packet delivery rate is determined by collecting a plurality of data packets, wherein the plurality of data packets are reflected from the second edge switch to the first edge switch.
3. The method of claim 2 , wherein the plurality of data packets are injected into the network at the first edge switch.
4. The method of claim 2 , further comprising:
determining a latency value based at least partially on the plurality of data packets; and
sending the latency value to the user device.
5. The method of claim 2 , further comprising:
determining a jitter value based at least partially on the plurality of data packets; and
sending the jitter value to the user device.
6. The method of claim 1 , wherein the graphical user interface display data comprises configuration data related to the network.
7. The method of claim 6 , wherein the configuration data includes a graphical representation of the network.
8. The method of claim 1 , wherein the graphical user interface display data comprises service level information indicated by color.
9. The method of claim 1 , wherein the graphical user interface display data comprises information regarding a service level agreement.
10. The method of claim 1 , wherein the graphical user interface display data comprises trouble information related to the network.
11. A memory device, comprising
instructions that are executable by a processor to cause the processor to collect a plurality of reflected data packets, wherein the plurality of reflected data packets are reflected from a destination device to a source device of a network; and
instructions that are executable by the processor to cause the processor to report results from the collecting of the plurality of reflected data packets to a user device operably coupled to a customer equipment side of the source device.
12. The memory of claim 11 , when a plurality of data packets are injected into the network, and wherein the plurality of reflected data packets include at least a portion of the plurality of data packets injected into the network.
13. The memory of claim 11 , wherein reporting the results from the collecting of the plurality of reflected data packets to the user device comprises generating a graphical user interface including service level information related to the network.
14. The memory of claim 13 , wherein the graphical user interface comprises a matrix including service level information related to a portion of the network.
15. The memory of claim 11 , wherein the results from the collecting of the plurality of reflected data packets include an average jitter value.
16. The memory of claim 11 , wherein the results from the collecting of the plurality of reflected data packets include a packet delivery rate.
17. The memory of claim 11 , wherein the results from the collecting of the plurality of reflected data packets include a total number of data packets reflected from the destination device.
18. A memory device, comprising
instructions that are executable by a processor to cause the processor to determine a data packet delivery rate between a first edge switch coupled to a network and a second edge switch coupled to the network; and
instructions that are executable by the processor to cause the processor to send the data packet delivery rate to a user device as graphical user interface display data, wherein the user device is operably coupled to a customer equipment side of the first edge switch.
19. The memory device of claim 18 , further comprising instructions that are executable by the processor to cause the processor to determine a total number of data packet reflected from the second edge switch to the first edge switch, wherein the data packet delivery rate is determined based on the total number of the data packets reflected.
20. The memory device of claim 18 , wherein the network comprises a switched metro Ethernet network.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/201,178 US20090059807A1 (en) | 2004-10-27 | 2008-08-29 | Systems and Methods to Monitor a Network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/975,022 US7433319B2 (en) | 2004-10-27 | 2004-10-27 | System and method for collecting and presenting service level agreement metrics in a switched metro ethernet network |
US12/201,178 US20090059807A1 (en) | 2004-10-27 | 2008-08-29 | Systems and Methods to Monitor a Network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/975,022 Continuation US7433319B2 (en) | 2004-10-27 | 2004-10-27 | System and method for collecting and presenting service level agreement metrics in a switched metro ethernet network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090059807A1 true US20090059807A1 (en) | 2009-03-05 |
Family
ID=36206077
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/975,022 Active 2026-11-11 US7433319B2 (en) | 2004-10-27 | 2004-10-27 | System and method for collecting and presenting service level agreement metrics in a switched metro ethernet network |
US12/201,178 Abandoned US20090059807A1 (en) | 2004-10-27 | 2008-08-29 | Systems and Methods to Monitor a Network |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/975,022 Active 2026-11-11 US7433319B2 (en) | 2004-10-27 | 2004-10-27 | System and method for collecting and presenting service level agreement metrics in a switched metro ethernet network |
Country Status (1)
Country | Link |
---|---|
US (2) | US7433319B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9992073B2 (en) | 2015-10-02 | 2018-06-05 | Axis Ab | Network status measuring system and a method for measuring status of a network |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7701934B2 (en) * | 2004-11-02 | 2010-04-20 | At&T Intellectual Property I, L.P. | System and method for managing devices within a private network via a public network |
US8015064B2 (en) | 2005-04-20 | 2011-09-06 | At&T Intellectual Property I, Lp | System and method of providing advertisements to cellular devices |
US7778873B2 (en) * | 2005-04-20 | 2010-08-17 | At&T Intellectual Property I, L.P. | System and method of providing advertisements to Wi-Fi devices |
US7930211B2 (en) | 2005-04-20 | 2011-04-19 | At&T Intellectual Property I, L.P. | System and method of providing advertisements to portable communication devices |
US8027877B2 (en) | 2005-04-20 | 2011-09-27 | At&T Intellectual Property I, L.P. | System and method of providing advertisements to mobile devices |
KR100636284B1 (en) * | 2005-08-19 | 2006-10-18 | 삼성전자주식회사 | Voip terminal provided function of qos monitoring and qos monitoring method |
US9311611B2 (en) | 2006-06-16 | 2016-04-12 | Hewlett Packard Enterprise Development Lp | Automated service level management system |
US7940677B2 (en) * | 2007-06-05 | 2011-05-10 | At&T Intellectual Property I, Lp | Architecture for optical metro ethernet service level agreement (SLA) management |
CN107769988B (en) * | 2016-08-19 | 2021-05-04 | 华为技术有限公司 | Method, device and network equipment for sending information and detecting message loss |
US11228340B1 (en) * | 2019-08-28 | 2022-01-18 | Marvell Asia Pte, Ltd. | Ethernet link transmit power method based on network provided alien crosstalk feedback |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5926649A (en) * | 1996-10-23 | 1999-07-20 | Industrial Technology Research Institute | Media server for storage and retrieval of voluminous multimedia data |
US6075773A (en) * | 1998-03-17 | 2000-06-13 | 3Com Corporation | Multi-user LAN packet generator |
US6279039B1 (en) * | 1996-04-03 | 2001-08-21 | Ncr Corporation | Resource management method and apparatus for maximizing multimedia performance of open systems |
US6363056B1 (en) * | 1998-07-15 | 2002-03-26 | International Business Machines Corporation | Low overhead continuous monitoring of network performance |
US20020080750A1 (en) * | 2000-11-08 | 2002-06-27 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20020099854A1 (en) * | 1998-07-10 | 2002-07-25 | Jacob W. Jorgensen | Transmission control protocol/internet protocol (tcp/ip) packet-centric wireless point to multi-point (ptmp) transmission system architecture |
US6452915B1 (en) * | 1998-07-10 | 2002-09-17 | Malibu Networks, Inc. | IP-flow classification in a wireless point to multi-point (PTMP) transmission system |
US6590885B1 (en) * | 1998-07-10 | 2003-07-08 | Malibu Networks, Inc. | IP-flow characterization in a wireless point to multi-point (PTMP) transmission system |
US6594246B1 (en) * | 1998-07-10 | 2003-07-15 | Malibu Networks, Inc. | IP-flow identification in a wireless point to multi-point transmission system |
US6628629B1 (en) * | 1998-07-10 | 2003-09-30 | Malibu Networks | Reservation based prioritization method for wireless transmission of latency and jitter sensitive IP-flows in a wireless point to multi-point transmission system |
US20030200548A1 (en) * | 2001-12-27 | 2003-10-23 | Paul Baran | Method and apparatus for viewer control of digital TV program start time |
US6640248B1 (en) * | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
US20030225549A1 (en) * | 2002-03-29 | 2003-12-04 | Shay A. David | Systems and methods for end-to-end quality of service measurements in a distributed network environment |
US20030223466A1 (en) * | 2002-05-31 | 2003-12-04 | Noronha Ciro Aloisio | Apparatus for redundant multiplexing and remultiplexing of program streams and best effort data |
US20040008736A1 (en) * | 2002-07-10 | 2004-01-15 | Byungjun Bae | Apparatus and method for inserting null packet in digital broadcasting transmission system |
US6680922B1 (en) * | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US20040017780A1 (en) * | 2002-07-26 | 2004-01-29 | Tazebay Mehmet V. | Physical layer device with diagnostic loopback capability |
US20040073718A1 (en) * | 2000-12-28 | 2004-04-15 | Svein Johannessen | Time synchronization in computer network |
US20040196852A1 (en) * | 2003-02-13 | 2004-10-07 | Nokia Corporation | Method for signaling client rate capacity in multimedia streaming |
US20040228302A1 (en) * | 2003-04-29 | 2004-11-18 | Seol Jee Woong | Method for determining packet data rate in wireless communication system |
US6901604B1 (en) * | 1999-02-19 | 2005-05-31 | Chaincast, Inc. | Method and system for ensuring continuous data flow between re-transmitters within a chaincast communication system |
US20050281392A1 (en) * | 2004-06-18 | 2005-12-22 | Covaro Networks, Inc. | System and method for connection performance analysis |
US7185232B1 (en) * | 2001-02-28 | 2007-02-27 | Cenzic, Inc. | Fault injection methods and apparatus |
-
2004
- 2004-10-27 US US10/975,022 patent/US7433319B2/en active Active
-
2008
- 2008-08-29 US US12/201,178 patent/US20090059807A1/en not_active Abandoned
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6279039B1 (en) * | 1996-04-03 | 2001-08-21 | Ncr Corporation | Resource management method and apparatus for maximizing multimedia performance of open systems |
US5926649A (en) * | 1996-10-23 | 1999-07-20 | Industrial Technology Research Institute | Media server for storage and retrieval of voluminous multimedia data |
US6075773A (en) * | 1998-03-17 | 2000-06-13 | 3Com Corporation | Multi-user LAN packet generator |
US6628629B1 (en) * | 1998-07-10 | 2003-09-30 | Malibu Networks | Reservation based prioritization method for wireless transmission of latency and jitter sensitive IP-flows in a wireless point to multi-point transmission system |
US6680922B1 (en) * | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US6640248B1 (en) * | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
US20020099854A1 (en) * | 1998-07-10 | 2002-07-25 | Jacob W. Jorgensen | Transmission control protocol/internet protocol (tcp/ip) packet-centric wireless point to multi-point (ptmp) transmission system architecture |
US6452915B1 (en) * | 1998-07-10 | 2002-09-17 | Malibu Networks, Inc. | IP-flow classification in a wireless point to multi-point (PTMP) transmission system |
US20030067903A1 (en) * | 1998-07-10 | 2003-04-10 | Jorgensen Jacob W. | Method and computer program product for internet protocol (IP)-flow classification in a wireless point to multi-point (PTMP) |
US6590885B1 (en) * | 1998-07-10 | 2003-07-08 | Malibu Networks, Inc. | IP-flow characterization in a wireless point to multi-point (PTMP) transmission system |
US6594246B1 (en) * | 1998-07-10 | 2003-07-15 | Malibu Networks, Inc. | IP-flow identification in a wireless point to multi-point transmission system |
US6363056B1 (en) * | 1998-07-15 | 2002-03-26 | International Business Machines Corporation | Low overhead continuous monitoring of network performance |
US6901604B1 (en) * | 1999-02-19 | 2005-05-31 | Chaincast, Inc. | Method and system for ensuring continuous data flow between re-transmitters within a chaincast communication system |
US20030142638A1 (en) * | 2000-11-08 | 2003-07-31 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20020085526A1 (en) * | 2000-11-08 | 2002-07-04 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20020150075A1 (en) * | 2000-11-08 | 2002-10-17 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20030185166A1 (en) * | 2000-11-08 | 2003-10-02 | Belcea John M. | Time division protocol for an AD-HOC, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20020080750A1 (en) * | 2000-11-08 | 2002-06-27 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20020089945A1 (en) * | 2000-11-08 | 2002-07-11 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20030142645A1 (en) * | 2000-11-08 | 2003-07-31 | Belcea John M. | Time division protocol for an ad-hoc, peer-to-peer radio network having coordinating channel access to shared parallel data channels with separate reservation channel |
US20040073718A1 (en) * | 2000-12-28 | 2004-04-15 | Svein Johannessen | Time synchronization in computer network |
US7185232B1 (en) * | 2001-02-28 | 2007-02-27 | Cenzic, Inc. | Fault injection methods and apparatus |
US20030200548A1 (en) * | 2001-12-27 | 2003-10-23 | Paul Baran | Method and apparatus for viewer control of digital TV program start time |
US20030225549A1 (en) * | 2002-03-29 | 2003-12-04 | Shay A. David | Systems and methods for end-to-end quality of service measurements in a distributed network environment |
US20030223466A1 (en) * | 2002-05-31 | 2003-12-04 | Noronha Ciro Aloisio | Apparatus for redundant multiplexing and remultiplexing of program streams and best effort data |
US20040008736A1 (en) * | 2002-07-10 | 2004-01-15 | Byungjun Bae | Apparatus and method for inserting null packet in digital broadcasting transmission system |
US20040017780A1 (en) * | 2002-07-26 | 2004-01-29 | Tazebay Mehmet V. | Physical layer device with diagnostic loopback capability |
US20040196852A1 (en) * | 2003-02-13 | 2004-10-07 | Nokia Corporation | Method for signaling client rate capacity in multimedia streaming |
US20040228302A1 (en) * | 2003-04-29 | 2004-11-18 | Seol Jee Woong | Method for determining packet data rate in wireless communication system |
US20050281392A1 (en) * | 2004-06-18 | 2005-12-22 | Covaro Networks, Inc. | System and method for connection performance analysis |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9992073B2 (en) | 2015-10-02 | 2018-06-05 | Axis Ab | Network status measuring system and a method for measuring status of a network |
Also Published As
Publication number | Publication date |
---|---|
US7433319B2 (en) | 2008-10-07 |
US20060087979A1 (en) | 2006-04-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20090059807A1 (en) | Systems and Methods to Monitor a Network | |
US20070041329A1 (en) | System and method for monitoring a switched metro ethernet network | |
EP1206085B1 (en) | Method and apparatus for automated service level agreements | |
Prasad et al. | Bandwidth estimation: metrics, measurement techniques, and tools | |
US7245584B2 (en) | Method and apparatus for auditing service level agreements by test packet insertion | |
US7668966B2 (en) | Data network controller | |
US20080046266A1 (en) | Service level agreement management | |
EP1610496A1 (en) | Rapid fault detection and recovery for internet protocol telephony | |
US20030133443A1 (en) | Passive route control of data networks | |
US7610327B2 (en) | Method of automatically baselining business bandwidth | |
Sundaresan et al. | TCP congestion signatures | |
Pras et al. | Dimensioning network links: a new look at equivalent bandwidth | |
Collange et al. | User impatience and network performance | |
Beckers et al. | Generalized processor sharing performance models for Internet access lines | |
Ishibashi et al. | Active/passive combination-type performance measurement method using change-of-measure framework | |
US8713160B1 (en) | Automated top-down multi-abstraction infrastructure performance analytics -network infrastructure-as-a-service perspective | |
Cisco | Planning the IP Telephony Network | |
Sprenkels et al. | Service level agreements | |
Ugochukwu et al. | Diagnosing Salem University Lokoja Network for Better Network Performance | |
Hongjie et al. | A distributed architecture for network performance measurement and evaluation system | |
Davy et al. | An efficient process for estimation of network demand for QoS-aware IP network planning | |
DUMAN et al. | Performance Metrics and Monitoring Tools for Sustainable Network Management | |
Claffy et al. | First amended report of at&t independent measurement expert: Reporting requirements and measurement methods | |
Vasudevan et al. | MIDAS: An impact scale for DDoS attacks | |
Smith | Network performance in managed networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AT&T INTELLECTUAL PROPERTY I, L.P. (FORMERLY KNOWN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SCHINE, BRUCE ALDEN;TOMALENAS, PAUL A.;REEL/FRAME:021461/0203;SIGNING DATES FROM 20041123 TO 20041202 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |