CA2316355C - Traffic monitoring tool for bandwidth management - Google Patents
Traffic monitoring tool for bandwidth management Download PDFInfo
- Publication number
- CA2316355C CA2316355C CA002316355A CA2316355A CA2316355C CA 2316355 C CA2316355 C CA 2316355C CA 002316355 A CA002316355 A CA 002316355A CA 2316355 A CA2316355 A CA 2316355A CA 2316355 C CA2316355 C CA 2316355C
- Authority
- CA
- Canada
- Prior art keywords
- bandwidth
- computer
- flows
- traffic
- information
- 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.)
- Expired - Lifetime
Links
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/0876—Network utilisation, e.g. volume of load or congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- 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/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- 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/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- 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
- 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/5019—Ensuring fulfilment of SLA
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/11—Identifying congestion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/19—Flow control; Congestion control at layers above the network layer
- H04L47/193—Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/28—Flow control; Congestion control in relation to timing considerations
- H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
- H04L47/323—Discarding or blocking control packets, e.g. ACK packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
-
- 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/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- 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/04—Processing captured monitoring data, e.g. for logfile generation
- H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
-
- 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/06—Generation of reports
-
- 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/06—Generation of reports
- H04L43/067—Generation of reports using time frame reporting
-
- 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
-
- 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/0852—Delays
- H04L43/087—Jitter
-
- 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/0894—Packet rate
-
- 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/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
-
- 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/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
Abstract
A method and system (100) for monitoring or profiling quality of service within a network of computers. The method includes a step of providing a network of computers, each being coupled to each other to form a local area network. The network of computers has a firewall server (110) coupled to the network of computers and a traffic management tool coupled to the firewall server. The method also includes implementing traffic monitoring or profiling of incoming and outgoing information.
Description
TRAFFIC MONITORING TOOL FOR BANDWIDT]H MANAGEMENT.
BACKGROUND OF THE INVENTION The present invention relates to communication or telecommunication.
More particularly, -the present invention provides a techniqiue, including a method and system, for monitoring and allocating bandwidth on a telecommunication network at, for example, a firewall access point. As merely an example, the present invention is implemented on a wide area network of computers or workstations such as the Internct.
But it would be recognized that the present invention has .t much broader range of applicability including local area networks, a combination of wide and local area networks, and the like.
Telecommunication techniques havi been aroiund for numerous years. In the eariy days, people such as the American Indians communicated to each other over long distances using "smoke signals." Smoke signals were generally used to transfer visual information from one geographical location to be observed at another geographical location. Since smoke signals could only be so:n over a limited range of geographical distances, they were soon replaced by a consmuinication technique known as telegraph. Telegraph generally transferred information from one geographical location to another geographical location using electrical sig;nals in the form of "dots"
and "dashes" over transmission lines. An example of commonly used electrical signals is Morse code. Telegraph has been, for the most part, replaceci by telephone. The telephone was invented by Alexander Graham Bell in the 1800s to transniit and send voice information using electrical analog signals over a telephone line, or more commonly a single twisted pair copper line. Most industrialized countries today rely heavily upon telephone to facilitate communication between businesses and people, in general.
In the 1990s, another significant development in the telecommunication industry occurred. People began communicating to each other by way of computers, which are coupled to the telephone lines or telephone network. These computers or workstations coupled to each other can transmit many types of information from one geographical location to another geographical location. This information can be in the form of voice, video, and data, which have been commonly termed as "multimedia."
Information transmitted over the Internet or Internet "traffic" has increased dramatically in recent years. In fact, the increased traffic has caused congestion, which leads to problems in responsiveness and throughput. This congestion is similar to the congestion of automobiles on a freeway, such as those in Silicon Valley from the recent "boom" in high technology companies, including companies specializing in telecommunication. As a result, individual users, businesses, and others have been spending more time waiting for information, and less time on productive activities. For example, a typical user of the Internet may spend a great deal of time attempting to view selected sites, which are commonly referred to as "Websites," on the Internet.
Additionally, information being sent from one site to another through electronic mail, which is termed "e-mail," may not reach its destination in a timely or adequate manner.
In effect, quality of service or Quality of Service ("QoS") of the Internet has decreased to the point where some messages are being read at some time significantly beyond the time the messages were sent.
Quality of Service is often measured by responsiveness, including the amount of time spent waiting for images, texts, and other data to be transferred, and by throughput of data across the Internet, and the like. Other aspects may be application specific, for example, jitter, quality of playback, quality of data transferred across the Internet, and the like. Three main sources of data latency include: the lack of bandwidth at the user (or receiving) end, the general congestion of Internet, and the lack of bandwidth at the source (or sending) end.
A solution to decreasing data latency includes increasing the bandwidth of the user. This is typically accomplished by upgrading the network link, for example by upgrading a modem or network connection. For example, the network link may be SUBSTITUTE SHEET (RULE 26) upgraded to X2 modems, 56K modems, ADSL or DMT modems, ISDN service and modems, cable TV service and modems, and the like. Drawbacks to these solutions include that they typically require additional network service; they also require additional hardware and/or software, and further they require both the sender and receiver to both agree on using the same hardware and/or software. Although one user may have a much faster line or faster modem, another user may still rely on the same 1,200 kbaud modem. So, the speed at which information moves from one location to another location is often determined by the slowest information which is being transferred over the network. Accordingly, users of faster technology are basically going nowhere, or "running" nowhere fast, as is commonly stated in the network industry.
From the above, it is seen that a technique for improving the use of a wide area network is highly desirable.
SUMMARY OF THE INVENTION
The present invention relates to a technique, including a method and system, for providing more quality to telecommunication services. More particularly, the present invention relates to quality of service management using a novel traffic monitoring technique. The present monitoring technique is predominantly software based, but is not limited to such software in some embodiments.
In a specific embodiment, the present invention provides a system with a novel graphical user interface for monitoring a flow of information coupled to a network of computers. The user interface is provided on a display. The display has at least a first portion and a second portion, where the first portion displays a graphical chart representing the flow of information. The second portion displays text information describing aspects of the flow of information. The combination of the first portion and the second portion describe the information being profiled.
In an alternative specific embodiment, the present invention provides a novel computer network system having a real-time bandwidth profiling tool. The real-time bandwidth profiling tool has a graphical user interface on a monitor. The graphical user interface includes at least a first portion and a second portion. The first SUBSTITUTE SHEET (RULE 26) portion displays a graphical chart representing the flow of information. The second portion displays text information describing the flow of information. The combination of the first portion and the second portion describe the information being profiled.
In still an alternative embodiment, the present invention provides a novel bandwidth profiling tool. The present bandwidth profiling tool includes a variety of computer codes to form computer software or a computer program, which is stored in computer memory.
The program includes a first code that is directed to measuring a data rate for a flow of information from an incoming source, which is coupled to a network of computers. The program also has a second code that is directed to categorizing the data rate from the flow of information based upon at least one of a plurality of traffic classes and a third code that is directed to outputting a visual representation of the data rate in graphical form on a display. A
fourth code is used to direct the outputting of a text representation of the one of the plurality of traffic classes on the display. The present invention has a variety of other codes to perform the methods described herein, and outside the present specification.
Numerous advantages are achieved by way of the present invention over pre-existing or conventional techniques. In a specific embodiment, the present invention provides a single point or a single region to manage telecommunication traffic including directory services and bandwidth management. Additionally, in some, if not all embodiments, the present invention can be implemented at a single point of access such as a computer terminal or firewall, for example. Furthermore, the present invention can be predominately software based and can be implemented into a pre-existing system by way of a relatively simple installation process. Moreover, the present invention provides more valued applications and users with a more reliable and faster service. Less critical applications and users are provided with a service level that is appropriate for them in some embodiments. In most embodiments, available bandwidth in a system is fairly shared between equally prioritized users (e.g., no user can monopolize or "hog" the system). Still further, link efficiency improves due to overall congestion avoidance in most cases. Moreover, the present invention implements its traffic management technique using a simple and easy to use "rule" based technique. These and other advantages are described throughout the present specification, and more particularly below.
Further understanding of the nature and advantages of the invention may be SUBSTITUTE SHEET (RULE 26) realized by reference to the remaining portions of the specification, drawings, and attached documents.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a simplified diagram of a system according to an embodiment of the present invention;
Fig. 2 is a simplified block diagram of system architecture according to an embodiment of the present invention;
Fig. 3 is a simplified diagram of a traffic management cycle according to an embodiment of the present invention;
Figs. 4-7 are simplified diagrams of systems according to various embodiments of the present invention;
Fig. 8 is a simplified flow diagram of a rule-based control method according to the present invention; and Figs. 9-15 are simplified representations of graphical user interfaces for monitoring traffic according to the present invention.
DESCRIPTION OF SPECIFIC EMBODIMENTS
An embodiment of the present provides integrated network service policies for firewall platforms, as well as other platforms or gateways.
Specifically, the present invention provides network or firewall administrators with the ability to implement policy-based schema for security and resource management on firewall platforms. In a specific embodiment, resource management includes Network Quality of Service (QoS) or "bandwidth" management techniques. In an exemplary embodiment, the present invention provides tools for monitoring traffic for bandwidth management, as well as other functions.
Network QoS occurs by managing the resources that serve network application traffic, for example. This typically includes the following resources: link bandwidth, application server bandwidth (CPU), and buffer space on generally all nodes (end-points, routers and gateways). Typically, data through-put is limited by the speed of Internet access links and by the server CPU capacity, and response time is SU8STITUTE SHEET (RULE 26) determined by the number of hops in a route, physical length of the route, and extent of congestion in the route. There are various other factors that may affect QoS, such as the behavior of TCP/IP, severe congestion anywhere in the route, prioritization of traffic along the route, etc. To a network administrator, embodiments of the present invention provide discrimination of different traffic types and provide methods for enforcement of traffic flow by management to the above resources.
DEFINITIONS
In the present invention, it may assist the reader to understand some of the terms described herein. These terms have been briefly described below.
These terms are merely examples and should not unduly limit the scope of the claims herein.
1. Traffic Management: A set of techniques or mechanisms including policies that can be applied in a network to manage limited network resources such as bandwidth and the like. These techniques are intended to improve overall network performance and efficiency. They are also intended to provide for more predictability and orderliness in the event of network congestion. The techniques should also isolate faults and provide visibility into performance problems. Additionally, they should meet the diverse user and application requirements as per an organization's business goals.
Furthermore, traffic management is intended to increase the "goodput" traffic, based on the economic value and prevent the abuse of network resources.
2. Quality Of Service (QoS): The concept of Quality of Service (QoS) has been analyzed and discussed for a number of years in the networking industry, and was previously associated mostly with ATM technology. In a more generic sense, QoS
describes the performance specifications that an application requires from the underlying infrastructure.
Otherwise, the application will not run satisfactorily. Some applications are designed to run in a best-effort mode and can adapt to available bandwidth. Others are extremely sensitive to delays. Still others can produce large bursts in traffic which affects other applications while providing little perceptible improvements to the end-user. QoS specifications are closely SUBSTITUTE SHEET (RULE 26) associated with the expectations and perceptions of end-users and the organization they are part of.
3. Bandwidth: Bandwidth usually refers to maximum available bit rate for a specific application. In a specific embodiment, synchronous, interactive, and real-time applications, which are bandwidth-sensitive, can require minimum bandwidth guarantees, and can require sustained and burst-scale bit-rates. On the other hand, network administrators may want to limit bandwidth taken by non-productive traffic such as push technologies like PointCast and others. Even though bandwidth may be allocated for specified applications, it does not mean that these applications may be using that bandwidth. Therefore, a good policy should be to enforce when there is competition and demand.
4. Latency: Latency generally refers to the delay experienced by a packet from the source to destination. Latency requirements are typically specified as mean-delay and worst case delay in some cases. Real-time audio/video applications such as, for example, DNS, HTTP, and TELNET are delay sensitive. Delay is a result of propagation delay, due to physical medium and queuing at intermediate nodes such as routers, gateways, or even servers. A certain portion of the delay can be controlled by how the queues are serviced at the intermediate nodes, and by controlling congestion at bottleneck points.
Some examples of delay measures are packet round-trip delay and connection response time.
BACKGROUND OF THE INVENTION The present invention relates to communication or telecommunication.
More particularly, -the present invention provides a techniqiue, including a method and system, for monitoring and allocating bandwidth on a telecommunication network at, for example, a firewall access point. As merely an example, the present invention is implemented on a wide area network of computers or workstations such as the Internct.
But it would be recognized that the present invention has .t much broader range of applicability including local area networks, a combination of wide and local area networks, and the like.
Telecommunication techniques havi been aroiund for numerous years. In the eariy days, people such as the American Indians communicated to each other over long distances using "smoke signals." Smoke signals were generally used to transfer visual information from one geographical location to be observed at another geographical location. Since smoke signals could only be so:n over a limited range of geographical distances, they were soon replaced by a consmuinication technique known as telegraph. Telegraph generally transferred information from one geographical location to another geographical location using electrical sig;nals in the form of "dots"
and "dashes" over transmission lines. An example of commonly used electrical signals is Morse code. Telegraph has been, for the most part, replaceci by telephone. The telephone was invented by Alexander Graham Bell in the 1800s to transniit and send voice information using electrical analog signals over a telephone line, or more commonly a single twisted pair copper line. Most industrialized countries today rely heavily upon telephone to facilitate communication between businesses and people, in general.
In the 1990s, another significant development in the telecommunication industry occurred. People began communicating to each other by way of computers, which are coupled to the telephone lines or telephone network. These computers or workstations coupled to each other can transmit many types of information from one geographical location to another geographical location. This information can be in the form of voice, video, and data, which have been commonly termed as "multimedia."
Information transmitted over the Internet or Internet "traffic" has increased dramatically in recent years. In fact, the increased traffic has caused congestion, which leads to problems in responsiveness and throughput. This congestion is similar to the congestion of automobiles on a freeway, such as those in Silicon Valley from the recent "boom" in high technology companies, including companies specializing in telecommunication. As a result, individual users, businesses, and others have been spending more time waiting for information, and less time on productive activities. For example, a typical user of the Internet may spend a great deal of time attempting to view selected sites, which are commonly referred to as "Websites," on the Internet.
Additionally, information being sent from one site to another through electronic mail, which is termed "e-mail," may not reach its destination in a timely or adequate manner.
In effect, quality of service or Quality of Service ("QoS") of the Internet has decreased to the point where some messages are being read at some time significantly beyond the time the messages were sent.
Quality of Service is often measured by responsiveness, including the amount of time spent waiting for images, texts, and other data to be transferred, and by throughput of data across the Internet, and the like. Other aspects may be application specific, for example, jitter, quality of playback, quality of data transferred across the Internet, and the like. Three main sources of data latency include: the lack of bandwidth at the user (or receiving) end, the general congestion of Internet, and the lack of bandwidth at the source (or sending) end.
A solution to decreasing data latency includes increasing the bandwidth of the user. This is typically accomplished by upgrading the network link, for example by upgrading a modem or network connection. For example, the network link may be SUBSTITUTE SHEET (RULE 26) upgraded to X2 modems, 56K modems, ADSL or DMT modems, ISDN service and modems, cable TV service and modems, and the like. Drawbacks to these solutions include that they typically require additional network service; they also require additional hardware and/or software, and further they require both the sender and receiver to both agree on using the same hardware and/or software. Although one user may have a much faster line or faster modem, another user may still rely on the same 1,200 kbaud modem. So, the speed at which information moves from one location to another location is often determined by the slowest information which is being transferred over the network. Accordingly, users of faster technology are basically going nowhere, or "running" nowhere fast, as is commonly stated in the network industry.
From the above, it is seen that a technique for improving the use of a wide area network is highly desirable.
SUMMARY OF THE INVENTION
The present invention relates to a technique, including a method and system, for providing more quality to telecommunication services. More particularly, the present invention relates to quality of service management using a novel traffic monitoring technique. The present monitoring technique is predominantly software based, but is not limited to such software in some embodiments.
In a specific embodiment, the present invention provides a system with a novel graphical user interface for monitoring a flow of information coupled to a network of computers. The user interface is provided on a display. The display has at least a first portion and a second portion, where the first portion displays a graphical chart representing the flow of information. The second portion displays text information describing aspects of the flow of information. The combination of the first portion and the second portion describe the information being profiled.
In an alternative specific embodiment, the present invention provides a novel computer network system having a real-time bandwidth profiling tool. The real-time bandwidth profiling tool has a graphical user interface on a monitor. The graphical user interface includes at least a first portion and a second portion. The first SUBSTITUTE SHEET (RULE 26) portion displays a graphical chart representing the flow of information. The second portion displays text information describing the flow of information. The combination of the first portion and the second portion describe the information being profiled.
In still an alternative embodiment, the present invention provides a novel bandwidth profiling tool. The present bandwidth profiling tool includes a variety of computer codes to form computer software or a computer program, which is stored in computer memory.
The program includes a first code that is directed to measuring a data rate for a flow of information from an incoming source, which is coupled to a network of computers. The program also has a second code that is directed to categorizing the data rate from the flow of information based upon at least one of a plurality of traffic classes and a third code that is directed to outputting a visual representation of the data rate in graphical form on a display. A
fourth code is used to direct the outputting of a text representation of the one of the plurality of traffic classes on the display. The present invention has a variety of other codes to perform the methods described herein, and outside the present specification.
Numerous advantages are achieved by way of the present invention over pre-existing or conventional techniques. In a specific embodiment, the present invention provides a single point or a single region to manage telecommunication traffic including directory services and bandwidth management. Additionally, in some, if not all embodiments, the present invention can be implemented at a single point of access such as a computer terminal or firewall, for example. Furthermore, the present invention can be predominately software based and can be implemented into a pre-existing system by way of a relatively simple installation process. Moreover, the present invention provides more valued applications and users with a more reliable and faster service. Less critical applications and users are provided with a service level that is appropriate for them in some embodiments. In most embodiments, available bandwidth in a system is fairly shared between equally prioritized users (e.g., no user can monopolize or "hog" the system). Still further, link efficiency improves due to overall congestion avoidance in most cases. Moreover, the present invention implements its traffic management technique using a simple and easy to use "rule" based technique. These and other advantages are described throughout the present specification, and more particularly below.
Further understanding of the nature and advantages of the invention may be SUBSTITUTE SHEET (RULE 26) realized by reference to the remaining portions of the specification, drawings, and attached documents.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a simplified diagram of a system according to an embodiment of the present invention;
Fig. 2 is a simplified block diagram of system architecture according to an embodiment of the present invention;
Fig. 3 is a simplified diagram of a traffic management cycle according to an embodiment of the present invention;
Figs. 4-7 are simplified diagrams of systems according to various embodiments of the present invention;
Fig. 8 is a simplified flow diagram of a rule-based control method according to the present invention; and Figs. 9-15 are simplified representations of graphical user interfaces for monitoring traffic according to the present invention.
DESCRIPTION OF SPECIFIC EMBODIMENTS
An embodiment of the present provides integrated network service policies for firewall platforms, as well as other platforms or gateways.
Specifically, the present invention provides network or firewall administrators with the ability to implement policy-based schema for security and resource management on firewall platforms. In a specific embodiment, resource management includes Network Quality of Service (QoS) or "bandwidth" management techniques. In an exemplary embodiment, the present invention provides tools for monitoring traffic for bandwidth management, as well as other functions.
Network QoS occurs by managing the resources that serve network application traffic, for example. This typically includes the following resources: link bandwidth, application server bandwidth (CPU), and buffer space on generally all nodes (end-points, routers and gateways). Typically, data through-put is limited by the speed of Internet access links and by the server CPU capacity, and response time is SU8STITUTE SHEET (RULE 26) determined by the number of hops in a route, physical length of the route, and extent of congestion in the route. There are various other factors that may affect QoS, such as the behavior of TCP/IP, severe congestion anywhere in the route, prioritization of traffic along the route, etc. To a network administrator, embodiments of the present invention provide discrimination of different traffic types and provide methods for enforcement of traffic flow by management to the above resources.
DEFINITIONS
In the present invention, it may assist the reader to understand some of the terms described herein. These terms have been briefly described below.
These terms are merely examples and should not unduly limit the scope of the claims herein.
1. Traffic Management: A set of techniques or mechanisms including policies that can be applied in a network to manage limited network resources such as bandwidth and the like. These techniques are intended to improve overall network performance and efficiency. They are also intended to provide for more predictability and orderliness in the event of network congestion. The techniques should also isolate faults and provide visibility into performance problems. Additionally, they should meet the diverse user and application requirements as per an organization's business goals.
Furthermore, traffic management is intended to increase the "goodput" traffic, based on the economic value and prevent the abuse of network resources.
2. Quality Of Service (QoS): The concept of Quality of Service (QoS) has been analyzed and discussed for a number of years in the networking industry, and was previously associated mostly with ATM technology. In a more generic sense, QoS
describes the performance specifications that an application requires from the underlying infrastructure.
Otherwise, the application will not run satisfactorily. Some applications are designed to run in a best-effort mode and can adapt to available bandwidth. Others are extremely sensitive to delays. Still others can produce large bursts in traffic which affects other applications while providing little perceptible improvements to the end-user. QoS specifications are closely SUBSTITUTE SHEET (RULE 26) associated with the expectations and perceptions of end-users and the organization they are part of.
3. Bandwidth: Bandwidth usually refers to maximum available bit rate for a specific application. In a specific embodiment, synchronous, interactive, and real-time applications, which are bandwidth-sensitive, can require minimum bandwidth guarantees, and can require sustained and burst-scale bit-rates. On the other hand, network administrators may want to limit bandwidth taken by non-productive traffic such as push technologies like PointCast and others. Even though bandwidth may be allocated for specified applications, it does not mean that these applications may be using that bandwidth. Therefore, a good policy should be to enforce when there is competition and demand.
4. Latency: Latency generally refers to the delay experienced by a packet from the source to destination. Latency requirements are typically specified as mean-delay and worst case delay in some cases. Real-time audio/video applications such as, for example, DNS, HTTP, and TELNET are delay sensitive. Delay is a result of propagation delay, due to physical medium and queuing at intermediate nodes such as routers, gateways, or even servers. A certain portion of the delay can be controlled by how the queues are serviced at the intermediate nodes, and by controlling congestion at bottleneck points.
Some examples of delay measures are packet round-trip delay and connection response time.
5. Jitter: Jitter generally refers to variation in delay (e.g., that is, the delay is not constant for all packets of a given flow) for a particular application. Real-time applications require a worst case jitter. Applications such as real-audio and video do some advanced buffering to overcome any variation in packet delays - the amount of buffering is determined by the expected jitter.
6. Packet Loss: Packet loss is a loss in a packet or a portion of packets that is generally caused by failure of network elements (e.g., routers, servers) to forward or deliver packets. Packet loss is usually an indication of severe congestion, overload of an element, or element failure (e.g., if a server is down). Even if the packet was not dropped SUBSTiTUTE SHEET (RULE 26) but just delayed, protocols and applications can assume it was lost. Packet loss can cause application timeouts, loss of quality or retransmitted packets. Packet loss is usually specified as a rate (e.g., a real-time video application cannot tolerate loss of more than one packet for every 10 packets sent). Indirect results of packet loss may also be measured (e.g., connection retries or data retransmits).
7. Guarantees: An extreme example of a guarantee is to partition bandwidth so that it is not available to other entities. Guarantee also means a share of the resource, e.g., minimum bandwidth or maximum latency.
7. Guarantees: An extreme example of a guarantee is to partition bandwidth so that it is not available to other entities. Guarantee also means a share of the resource, e.g., minimum bandwidth or maximum latency.
8. Best-effort: Best-efforts describes a service on best-effort basis but makes no guarantees.
9. Limits: Specific physical or theoretical limitation on a resource such as bandwidth. Resource utilization or admission is limited under certain conditions.
10. Priority: Level of importance for a specific user, application, or data.
Create a priority scheme among different entities so that contention is resolved or service is provided.
Create a priority scheme among different entities so that contention is resolved or service is provided.
11. Traffic Profiling: Profiling is intended to be defined as cumulative details of traffic flows for each active client, server, or application without application of any rules. This includes bandwidth, response time, and failure related statistics.
Profiling is intended to provide long term cumulative snapshots of traffic for capacity planning or setting traffic rules.
The above defmitions are merely intended to assist the reader in understanding some of the terms described herein. They are not intended, in any manner, to limit the scope of the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.
SUBSTtTUTE SHEET (RULE 26) SYSTEM OVERVIEW
Fig. 1 illustrates a simplified system 100 according to an embodiment of the present invention. The system 100 is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The present invention can be embodied as a TrafficWareTM
firewall server 110 from Ukiah Software, Inc, but can be others. System 100 typically includes a file server 120, and a plurality of computers 130-150, coupled to a local area network (LAN) 160, and other elements. Firewall server 110 includes a typical connection to a wide area network (WAN) 170 and to a remote LAN 180 (such as an Intranet) and a typical network connection 190 to the Internet 200. Attached to Internet 200 are Web servers 210 and other computers 220.
As illustrated, computers such as computer 130, 140, and 210 communicate using any one or multiple application layer protocols such as Telnet, file transfer protocol (FTP), Hypertext transmission protocol (HTTP), and the like. Further, communication across WAN 170 and across network connection 190 implements transport layer protocols such as transmission control protocol (TCP), universal data protocol (UDP), and the like.
LAN 160 and LAN 180 are preferably based upon network protocols such as Internet protocol (IP), IPX from Novell, AppleTalk, and the like. As shown in Fig. 1, network connection 190 may be accomplished using T1, ISDN, Dial-up, and other hardware connections. Computers 120-150 and 210-220 may be any suitable make or model of computer that can be coupled to a network. The system can also include a variety of other elements such as bridges, routers, and the like.
In an alternative specific embodiment, the present invention may be applied to a system with various links accessed in servicing a browser request at a remote web server.
In this embodiment, a client could be dialing in via a 28.8kbit dial up modem to a local Internet service provider (ISP), where the ISP may be connected to the Internet by a T1 link.
A web server may be on a 10 Mbs Ethernet LAN, which is connected to another ISP via a 56 K frame relay. The web server's ISP may be connected to its carrier via a T3 line. The client ISP carrier and the server ISP carrier may both be connected by an ATM
backbone or the like. Because of this asymmetry in this embodiment, any traffic management solution should take into account these variations including traffic speed and data format described SUBSTITUTE SHEET (RULE 26) above. Moreover, simply upgrading the capacity of a link, in the access path, may not offer a viable solution. This present embodiment may have the bandwidth requirements shown by way of Table 1, for example.
Table 1: Bandwidth R uirements Users Bandwidth Service Offered Internet developers, individuals, 28.8 to 56 Kbps Dial-up services, ISDN
international locations where bandwidth is expensive Small to medium-sized organizations with 56 Kbps to 1.5 Mbps Fractional TI, frame relay moderate Internet usage Medium sized organizations with many 1.5 Mbps Dedicated TI circuit moderate users, smaller organizations re uirin huge amounts of bandwidth Standard bandwidth for Ethernet-based 10 Mbps Ethernet, token ring (4 Mbps LANS or 16 Mbps) Bandwidth usage for large organizations or 45 Mbps Dedicated T3 circuit Internet backbones Huge bandwidth LAN backbone usage for 100 to 1.000 Mbps Fast Ethernet, gigabit medium to large organizations (hundreds or Ethernet thousands of users) As shown above, there exist a large number of diverse applications and protocols that are widely used and have their own performance requirements. For example, applications such as mail (e.g., SMTP) and news (e.g., NNTP) are not interactive and are therefore not sensitive to delay. On the other hand, applications such as real-time conferencing are extremely sensitive to delay but not to packet loss. Applications such as TELNET and DNS
do not utilize significant bandwidth, but are sensitive to delay and loss.
Conversely, applications such as FTP consume a great deal of bandwidth but are not that sensitive to delay. Generally, network applications can be categorized as:
1. Interactive (e.g., delay sensitive) versus non-interactive (e.g., delay tolerant);
2. Bandwidth intensive (bulk data) versus non-bandwidth intensive; and SUBSTtTUTE SHEET (RULE 26) 3. Bursty versus non-bursty.
These categories are merely illustrative and should not limit the scope of the claims herein.
Additionally, some application requirements are dependent on the context of use and the nature of data being accessed. Such applications can be described as being nominally interactive or nominally bandwidth intense. This means the description applies to many but not all the situations in which they are used.
As merely an example, Table 2 provides some illustrations for these categories.
Application Class Examples Low-bandwidth, delay DNS. PING, TELNET, CHAT, sensitive, highly interactive COLLABORATION
High bandwidth, delay sensitive Real-time audio and video High Bandwidth, nominally interactive Web service requests, file downloads Non-interactive Mail and news Table 2: Application Spectrum As shown in Table 2, low-bandwidth, delay sensitive, and highly interactive applications include, among others, DNS. PING, TELNET, CHAT, COLLABORATION. High bandwidth and delay sensitive applications including at least real-time audio and video.
Additional applications for high bandwidth and nominally interactive, or non-interactive have also been shown. Again, these applications are merely provided for illustration and should not limit the scope of the claims herein.
The present invention can also be used with a number of various files. For example, a number of common applications, such as FTP and HTTP, can handle a wide variety of files. The file types being transferred and downloaded place different demands on the underlying infrastructure. Index and HTML files take up limited bandwidth but have very mundane contents. On the other hand, GIF, JPEG and MPEG, RA and AVI files take up a lot more bandwidth but provide a rich multimedia experience to the end-user.
In fact, push SU6STITUTE SHEET (RULE 26) technologies such as PointCast basically download rich-multimedia bandwidth-intensive files.
The present invention can also be used with a variety of user requirements.
For example, networks are facing an explosion in the number of (inter) networked applications and data accessible through them. Network resources are increasingly being used for a wide variety of purposes, ranging from business critical to personal. This means that policies must ensure that scarce resources (e.g., Internet bandwidth) are utilized with the goal of maximizing the returns to the organization. These benefits can come from direct revenue generating activities or from improved productivity (or reduced loss of productivity).
As shown in Table 3, for example, at a mythical company called "Shebang Software Inc. "
the highest bandwidth priority has been allocated to technical support.
However, there is no hard and fast rule. As with security policies, decisions should be consistent with the needs of the organization.
Table 3: Shebang Software User Priorities Users Application Class Reasons Technical support Mission critical Needs most bandwidth to deal with customers who need assistance Sales and marketing Critical Needs bandwidth to deal with potential customers. Answer inquires, make quotes, transmit multimedia presentations Upper management and middle Casual Needs bandwidth to perform tasks management, administrative necessary to run the business Development and manufacturing Personal Needs bandwidth to send e-mail, subscribe to Push technologies The present invention takes into account, in one or more embodiments, the factors which are described specifically above. Although the above has been generally SUBSTITUTE SHEET (RULE 26) described in terms of a specific type of information, other types of information on a network can also be used with the present invention. Additionally, the present invention has been described in general to a specific system. For instance, the present bandwidth management tool can be applied at a network's Internet access link. Alternatively, the present tool can be applied to a private WAN link to a remote corporate site or an access to a server farm (e.g., a group of servers located in a special part of the network close to an access link, e.g., in a web hosting environment), Alternatively, the present invention can be applied to key servers (e.g., database/web server) within an organization servicing internal and/or external users.
Furthermore, the present bandwidth management tool can be applied to any combination of the above or the like.
Fig. 2 is a simplified block diagram 200 of details of system architecture according to an embodiment of the present invention. The block diagram is merely an illustration and should not limit the scope of the claims herein. The architecture includes a variety of layers that each interface to each_other as depicted by, the layers. The system includes a network layer 211, which interfaces to incoming and outgoing information to the network. The network can be one of a variety including; among others, Ethernet and Token R.ing: A physical layer 209 is disposed above the network layeir 211. The physical layer can be personal computers, which are commonly called PCs, or network interface computers, which are commonly called NCs, or alternatively workstations. As merely an example, a personal computer can be an IBM PC compatible computer having a'586-class, based microprocessor, such a Pentium''m from Intel Corporation, but iis not lirnited to such a computer or processor. An operating system ("OS") is used on. the computer such as WindowsNTTM from Microsoft Corporation, but can also be ottier OSs. The system.is also coupled to a graphical user interface ("GUI") 201 and is coupled to directory services such as, for example, LDAP, but can be others. A detailed discussion of directoq services is described in U.S. Paterits 6,212,558 and 6,047,322.
Directory services 224 and GUI 201 couple to an application programming interface ("API") 223. The API is coupled to a traffic n-anageinent or bandwidth management tool with at least three modules, including a policy engine module 231, a FAST module 229, and a FAIR module 227, which will be discussed in more detail below, but is not limited to these modules. The bandwidth management tool 208 can be predominantly software based and is substantially free from any significant hardware or software changes in the network. In a preferred embodiment, the bandwidth management tool 208 can be loaded onto a server without any changes to hardware. In an alternative preferred embodiment, the tool can install, configure, and operate on a conventional IBM
compatible PC running and operating system such as, for example, Windows NT, but can be others. The tool can be deployed at any appropriate point in the network data path. The tool can also be stand-alone at the WAN access point (e.g., behind the Internet access router or behind a firewall), with a conventional firewall or with an NT based proxy/caching server or application server (e.g., a Web server).
Tool 208 performs incoming and/or outgoing management of information over the network of computers. In a specific embodiment, traffic management tool 208 performs inbound and outbound monitoring arid control of flows by application, source address, destination address, URL, time of day, day of week, day of month, and other variations. In a specific embodiment, tool 208 also monitors, controls, and produces reports and alarms, which can enhance a whole spectrum of traffic monitoring and control activities ranging from bandwidth/latency control to capacity planning.
In a specific embodiment, the bandwidth management tool adapts to "real"
changes on any pre-existing networking system. For example, network infrastructure management involves a continuous process of monitoring, reporting, and deploying changes to match network growth or changing needs in a growing office, for example.
These changes exist at various levels and time scales. As merely examples, the network changes can be to enforce a QoS Policy for a critical service, add WAN bandwidth, segment the network, upgrade a router, choose a guaranteed service level for a web site (e.g., user's own wet site), or notify "Mr. Hog" (i.e., a user occupying too much bandwidth) that he should schedule his large personal downloads at more prudent times such as late at night, for example.
BANDWIDTH MANAGEMENT PROCESS
The bandwidth management tool can employ these changes using, for example, the process shown in Fig. 3. This process is merely and illustration and should not limit the SUBSTITUTE SHEET (RULE 26) scope of the claims herein. As shown, Fig. 3 is a simplified diagram 300 of a traffic management cycle according to an embodiment of the present invention. The traffic management cycle is depicted as a continuous cycle, which includes a monitoring phase 301, a creating/applying policy phase 303, and a reporting/alarming phase 305, but is not limited to these cycles. That is, these cycles can be separated or combined depending upon the application. By way of this cycle, the tool can adapt to any changes to the networking system according to the present invention.
In an aspect of the present invention, the present tool can monitor and control activities at various times, e.g., seconds, days, weeks, months, years. Some details with regard to these control activities are shown below under the headings.
1. Second to second The tool provides second to second time scale monitoring and control of incoming and outgoing traffic over the network. As merely an example, the tool ensures that critical or more important traffic gets a right of way during traffic bursts and provides bandwidth enforcement. Multiple users of the network at a specific time can cause the traffic burst. Alternatively, multiple sessions on the network at a specific time can cause the traffic burst. Once the traffic burst is detected, the tool has a control device, which provides bandwidth enforcement to ensure that the more important traffic gets through the network.
2. Day to day The tool provides day to day time scale monitoring and control of incoming and outgoing traffic over the network. As merely an example, the tool manages time of day congestion, and responds to intermittent problems or perceived problems. The tool generally deals with problems or limitations that are very specific and isolated to particular users or particular services at particular times that need to be tracked down quickly.
3. Week to week The tool provides week to week time scale monitoring and control of incoming and outgoing traffic over the network. The tool analyzes traffic usage performance patterns, what services or hosts are active on the network, and troubleshoots chronic problems. In SUBSTITUTE SHEET (RULE 26) particular, the tool looks at aggregates, such as a particular segment of the network, and compares Websites or compares groups of users for usage of bandwidth and frequency of usage.
4. Longer term activities The tool provides long term time scale monitoring and control of incoming and outgoing traffic over the network. The tool implements changes in organizational priorities, in billing. The tool also provides service for new applications as they are introduced, and provides for capacity planning for network resources. The present tool can also be used with network stress testing tools to obtain detailed analysis of flows and traffic behavior with/without policy enforcement before a new application is deployed to change the network infrastructure.
Based upon the above description, the present tool can be used to monitor and control incoming and outgoing traffic over a variety of time frequencies. The time frequencies include second by second, day to day, or long term, and combinations thereof, depending upon the application. Of course, the time frequency used depends upon the particular network and applications.
Figs. 4-7 are simplified diagrams of systems according to various embodiments of the present invention. These diagrams are merely illustrations and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, alternatives, and modifications. These systems show various deployment scenarios according to the present invention.
1. Internet Service Provider (ISP) Fig. 4 is a sirnplified diagram 400 of the present tool in an ISP environment according to the present invention. The diagram 400 includes a variety of elements such as an ISP LAN 401, which is coupled to network elements including a remote access concentrator 403, a web server 417, an FTP server 415, a router 413, a news server 411, and others. The too1405 is coupled between the ISP LAN and router 407, which is connected to the Internet 409. In this embodiment, the ISP is providing a number of services to its SUBSTtTUTE SHEET (RULE 26) customers and the present tool sits by the Internet link and manages inbound and outbound traffic.
2. Web Hosting Deployment Fig. 5 is a simplified diagram 500 of the present tool in a web hosting environment according to the present invention. The diagram 500 includes a variety of elements such as a LAN BackBone 501, which is coupled to network elements including web servers 503, 511, 513, and others. The present tool 505 is coupled between LAN
501 and router 507, which is connected to the Internet 509. In the present embodiment, the tool is being used to manage inbound and outbound traffic between some Websites and the Internet.
In a specific embodiment, most of the data being transmitted is multimedia-based, but is not limited as such data.
3. End-User Deployment Fig. 6 is a simplified diagram 600 of the present tool in a campus environment according to the present invention. The diagram 600 includes a variety of features such as a campus network 601, which is coupled to network elements such as a desktop PC
603, a UNIX computer 617, an NT Server 615, a web server 613, directory services 611, and others. A bandwidth management tool 605 is coupled between campus network 601 and router 607, which is coupled to Internet 609. In this embodiment, a LAN or WAN
supports a number of different setups and configurations, which are compete for bandwidth to access the Internet. The present tool acts as an arbitrator for implementing rules, enforcing policies, and setting admissions for classes, as well as perform other acts.
4. Private WAN
Fig. 7 is a simplified diagram 700 of the present tool deployed for a large corporation that has an Intranet as well as an Internet. The diagram 700 includes a variety of elements or "children" such as a connection to Frankfurt 715, a connection to London 713, a connection to Hong Kong 717, and a connection to Paris 719. Each connection or child includes a router 705A, E, D, C, and the present tool 703A, E, D, C, which is coupled between the router and the hub ("HQ"). In a WAN-based environment, for example, HQ 701 SUBSTITUTE SHEET (RULE 26) is the hub that handles a number of independent systems (e.g., Frankfurt, London, Hong Kong, Paris), which can be LAN-based. In this embodiment, the present too1703B
also sits by the Internet 711 and is used to allocate bandwidth between the competing children, e.g., Frankfurt, London, Hong Kong, Paris. Router 705B is coupled between tool 703B
and Internet 711.
Although the above descriptions have been made in terms of deploying the present tool in selected environments, the present tool can also be deployed in other environments. For example, the present tool can be deployed in any combination of the above. Alternatively, the present tool can be deployed in any portion of the above environments. Of course, the type of environment used by the present tool depends highly upon the application.
In a specific embodiment, the tool provides an easy to use interface or graphical user interface ("GUI") for performance monitoring and profiling (e.g., accounting).
Profiling can be based on active services, clients and servers, among other parameters.
Additionally, profiling of the network can be started as soon as the tool is installed into the server of the network. Accordingly, the tool provides immediate accounting and service measurement on a variety of QoS measures.
In a specific embodiment, the present tool generally uses two mechanisms to implement efficient traffic monitoring and traffic control. These mechanisms include processes performed by the FAST module and the FAIR module, which are shown in Fig. 2, for example. Additionally, the present tool uses a policy engine module 231, which oversees the FAST module 229 and the FAIR module 227. Some details of these modules are described as follows.
1. FAST Module (Flow Analysis and Session Tagging) The FAST module generally provides for monitoring of incoming and outgoing information to and from the network or link. Flow Analysis and Session Tagging ("FAST") implements rich, application level traffic classification, and measurement.
This operation is accomplished without introducing slow data paths to minimize latency and maximize overall throughout of traffic through the tool management engine. As shown in the Fig., the FAST
module provides for classification 203 of information such as parameters 213 including SUBSTITUTE SHEET (RULE 26) application, presentation, session, transport, and network. The FAST module also provides for measurement 219 of various parameters. The FAST module is coupled to the API.
2. FAIR Module (Flow Analysis and Intelligent Regulation) The FAIR module generally implements traffic control and manages bandwidth of incoming and outgoing information to and from the network or link. Flow Analysis and Intelligent Regulation ("FAIR") implements traffic control based on a combination of flow control and queuing algorithms. FAIR's objective provides inbound and outbound traffic management for meaningful time intervals, reducing the load on packet classifiers and packet schedulers. The FAIR module controls 205 incoming and outgoing information to and from the network. Additionally, the FAIR module controls 205 by parameters 215 such as class, session, burst, packet, and others. The FAIR module also controls time 217 of allocating bandwidth for these parameters. The FAIR module is coupled to the API.
3. Policy Engine Module The policy engine module 231 oversees the FAST and FAIR modules. The engine module also interfaces with the API. In an embodiment, the policy engine module includes a security policy 201, a traffic policy 202, and other policies 221.
The security policy provides parameters for securing the present tool. The traffic policy defmes specific limitations or parameters for the traffic.
Some defmitions about the various modules have been described above. These defmitions are not intended to be limiting. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. Additionally, the modules described are generally provided in terms of computer software. Computer software can be used to program and implement these modules, as well as others. The modules can be combined or even separated, depending upon the applications. Functionality of the modules can also be combined with hardware or the like. In a specific embodiment, the present modules are implemented on an WindowsNTTM operating system, which has been developed by Microsoft Corporation. Of course, other operating systems can also be used. Accordingly, the present modules are not intended to be limiting in any manner.
In an embodiment, the present tool can be configured based upon at least the SUBSTRUTE SHEET (RULE 26) following components - traffic classes, traffic policies, traffic rules, and traffic entities. Some information about these components are described below.
1. Traffic Classes The present tool identifies data flows at a network site based on traffic classes.
A traffic class is any combination of the following, but is not limited to these:
IP address, subnet, network, netgroup, or range of source or destination;
URL of the sender or group of URLs;
Service (e.g., HTTP, FTP) or groups of services;
FTP and HTTP, file types can be selected as well;
Time of day, day of week/month; and Inbound and outbound information.
As shown above, traffic classes are directional. Traffic classes configured for inbound traffic are managed separately from traffic classes configured for outbound traffic.
For example, the present tool may decide to guarantee a minimum bandwidth to critical traffic so that it is not affected by congestion from large downloads. Additionally, the present tool may want to monitor Push traffic for a while and then choose to limit it if it is perceived as a problem.
Traffic classes can also be for measurement only or for control and measurement in some embodiments. These are merely examples and should not limit the scope of the claims herein.
2. Traffic Policies Traffic policies are generally mechanisms used to control the traffic behavior of specific classes. In an embodiment, the present tool can configure policy properties which provide, for example:
Bandwidth guarantees - granting classes a minimum bandwidth in the presence of congestion or competition;
Bandwidth limits - establishing a limit on the total bandwidth used by the class;
SUBSTITUTE SHEET (RULE 26) Setting priorities - establishing a priority order foir bandwidth limiting or servicing traffic from a class. (That is, high priority classes are serviced first and are affected the least during contention for baindwidth. Lower priority classes are serviced in order of priority and may be more affected by congestion or contention);
Admission control- establishing conditions under which a new network session or service request is admitted or not admitted. (This kind of policy establishes.
a broad bandwidth control or service quality for sessions already admitted).
As shown, the present invention provides policies such as bandwidth guarantees, bandwidth limits, setting priorities, admission control, and others. It may assist the reader in understanding some of the terms used in the policies by drawing an analogy with a geographical highway for automobiles. For example, bandwidth relates to how fast one can go (e.g., fast or slow lane) once a user has entered the stream of'traffic on the highway. That is, the physical limit for speed in the specific lane chosen. Priority is analogous to how quickly the user is able to enter the highway and move into a de<.,ignated lane, and how often the user may have to temporarily give way to other vehicles during the drive.
Admission control is analogous to the metered lights at the entrance of the freeway where one is made to wait under certain conditions. . Of course, depending upon the applications other analogies can be used to explain the policies. Additionally, the policies are merely examples and should not limit the scope of the claims herein.
3. Traffic Rules .
A rule generally includes a traffic class and a policy associated with the class.
A class can have several policies that apply at different time intervals. -'Rule' is also used to refer to the, policy or to a specific row in the present tool user initerface.
4. Traffic Entities The present tool refers to entities in at least two different contexts:
defining traffic classes and viewing traffic profiles. For example, a network entity generally refers to an IP address, host, subnet, IP net, IP range, URL or a group of other network entities. A
service entity refers to a single service or a group of services. A native entity is referred to in viewing traffic profiles. No rule setting or configuration is required to monitor these entities.
When the present tool is installed, it begins to profile traffic based upon detected services, clients, or servers, all of which are called native entities.
5. Guidelines for Developing Traffic Policies The present invention provides some guidelines for developing traffic policies.
For example, to develop meaningful and effective traffic policies, the present tool may need to understand and take into account one or more of the following:
= The kind of business being performed by the user over the Internet. If the user is an ISP, the user may need to develop a business/pricing model that leverages the features of the present tool. If the user is managing corporate access to the Internet, the user may want to identify any business critical services being provided over the Internet = The priority of clients, servers and URLs hosted in the user's network or servers access over the Internet. This can be organized as business critical, casual and personal.
= The properties of different applications being used, whether they utilize lots of bandwidth or not. The user may also need to account for the type of files commonly download by users or from the Web site.
= Measure and analyze traffic using the present tool's profiles.
SUBSTITUTE SHEET (RULE 26) Additionally, monitoring of selected entities (e.g., users, services) may also be useful.
In a further embodiment, the present tool provides some general guidelines of some commonly used applications. These guidelines should be used in conjunction with business driven priorities, traffic profiling, and selective real-time monitoring to establish an effective traffic policy. Selected guidelines are defined as follows, but are not limited to these.
= Delay-sensitive low bandwidth applications, such as TELNET
and DNS, are controlled best by setting a high priority policy.
The present tool can give the highest priority to all network control traffic, such as QoS signaling, session establishment, domain lookup and routing protocols.
= Streaming multimedia applications, such as Real Audio/Video and Vxtreme, can hog allot of bandwidth but are also delay and bandwidth sensitive. If they are not critical, they are controlled best by setting a high priority and a policy to limit admission of sessions so that bandwidth use is capped but admitted sessions have a reasonable quality.
= Push technologies, such as PointCast and Marimba, download large files, are not delay or bandwidth sensitive and usually not business critical. They are best controlled by a limiting bandwidth policy and a low priority.
= Bulk-data non-interactive applications, such as SMTP and NNTP, should be guaranteed a small bandwidth minimum so that they are not totally squeezed out by congestion or control policies.
SUBSTITUTE SHEET (RULE 26) = Bulk-download, nominally interactive applications, such as FTP
or some HTTP downloads, are commonly used in a variety of situations, ranging from critical to casual. Differentiating various types of usage in this case can usually be made only on the basis of file types and/or source or destination addresses. In this case, a small minimum can be guaranteed for more important use.
= In bulk-download applications (e.g., file size> 20 K Bytes), overall congestion and burstiness can be controlled by slightly limiting this traffic, even if it is just a little below the total available bandwidth (e.g., 90 b). The present tool can provide smoothing controls on this traffic without impacting overall perceptible performance for these downloads. This is particularly useful at lower link speeds (128 K and below).
= Mission critical applications, such as Lotus Notes, Oracle SQLNet, and LDAP, are controlled best by setting a high priority with a guaranteed bandwidth minimum.
The above provides some guidelines for commonly used applications according to the present invention. Using the above guidelines, the present tool can effectively allocate bandwidth on a network, for example. Again, the above guidelines are merely examples and should not limit the scope of the claims herein.
In a specific embodiment, the present tool provides a comprehensive, flexible, rule-based paradigm for implementing traffic control, as illustrated by a simplified flow diagram 800 of Fig. 8. This flow diagram 800 is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. Before explaining the flow diagram, it may assist the reader by reviewing some general terms used herein.
SUBSTITUTE SHEET (RULE 26) These terms include, among others, "rules" and "classes" and "policies. "
Rules can be created for very specific groups of flows or more general groups of flows, which are commonly all the stuff that transmits to and from a link to a gateway point.
Groups of flows are also referred to as traffic classes, but are not limited to such classes.
Classes also can be defined by source, destination, application, file types, URLs, and other features. Policies can be specified to control traffic flows in terms of overall bandwidth guarantees, bandwidth limits, priority of service, how individual sessions within a class are serviced or admitted, and other aspects. The present tool also has intelligent policy validation that prevents users from defming any contradictory or ambiguous rules. Policy validation is generally a higher level check used by way of the present method.
The present method occurs at start, which is step 801, for example. In general, a flow of information or data or packets of information enter a gateway point, where the present tool sits. The present method classifies (step 803) the flow of information.
Groups of flows can be referred to as traffic classes, but are not limited to such classes.
Classes also can be defmed by source, destination, application, file types, URLs, and other features. Other examples of classes were previously noted, but are not limited to these classes. In general, step 803 classifies the flow of information received into one of a plurality of predetermined classes.
The present tool measures parameters for each of the classes in step 805, which were received, for example. These parameters are based upon the policy or rule, which may be applied in a later step. As merely an example, parameters include the class itself, file sizes, and other information, which can be used by the policy or rule to apply the policy or rule to improve the quality of service for the network. After measuring. the parameters, the present method applies a tiune stamp (step 807) on the parameters to correlate the class of information received to a time, for example.
A step of determining whether to apply a policy occurs in the next step 809.
For example, if the class and the time (and the link state in some embodiments) meet predetermined settings, the policy is applied to the class in step 811 through branch 810.
Alternatively, if one of the elements including the class, the time, or the link state do not meet the predetermined settings, the policy does not apply and the process continues to measure parameters through branch 808. Alternatively, the process continues to measure parameters SUBSTITUTE SHEET (RULE 26) through branch 821 after the policy is applied to the flow of information for the class.
Depending upon the application, the policy is used to improve the quality of service of the network by performing at least one of a number of functions for the class of information from the flow. These functions include, among others, bandwidth guarantees, bandwidth limits, setting priorities, admission control. The present process can also halt or ' stop as shown in step 815. The steps occur, in part, by way of the modules, which were previously described, but can also occur using other techniques including a combination of hardware and software, for example. These sequence of steps are merely illustrative and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other modifications, alternatives, and variations.
In a preferred embodiment, the present invention uses a variety of graphical user interfaces for profiling and monitoring traffic. Figs. 9A-15 are simplified representations of graphical user interfaces for monitoring traffic according to the present invention. These representations are merely illustrative and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.
Fig. 9A is a simplified flow diagram 950 of a profiling method according to the present invention. Profiling or monitoring traffic can occur using one of a plurality of user interfaces or graphical user interfaces. The present invention provides a profiles tab 953, which can be selected using a mouse or keyboard interface. The present method begins with a start step, which is step 951. Upon selecting a profiles tab 953, one of a plurality of tabs is prompted. These tabs represent services 957, server 959, and client 961. These tabs display relevant traffic statistics by every active service, server and client, respectively. By selecting one of the tabs, the present tool sorts data or information in ascending order by clicking on any header (e.g., Kb Transferred), as illustrated by Fig. 9 for a service tab 900.
Other functions that can be performed using one of the profiles and the graphical user interface include:
= Click the Refresh button, all data is updated from the profiling engine.
= Click the Reset button 907, clears all the respective data from the profiling SUBSTITUTE SHEET (RULE 26) engine.
= Click the Save As 909 button to save the respective data to a log file. The data is saved as tab-separated text.
Each of the present user interfaces also includes function keys 901 and a tool bar 903. Upon selecting the profiles tab, a profiles light or display indication illuminates 911. As shown, the main profiles tab also includes tabs for services 913, server 915, and client 917. Additional features of the various tabs including the services tab, the server tab, and the client tab are described below and refer to Figs. 9, 10, and 11, respectively, but are not limited to these descriptions.
1. Services Tab Fig. 9 is a simplified diagram 900 of a representation of a graphical user interface for a services tab according to the present invention. In particular, the dialog box displays cumulative traffic statistics for selected applications. The services tab, which can be selected by default, provides the following information:
Service Name This field 919 shows what servicts (e.g., All Services, FTP, HTTP, SMTP, POP3, SSL) the network uses. Summary statistics for all services (e.g., inbound or outbound) are also shown. Traffic from services that are not recognized by the present tool are indicated as ' Others' .
Direction This field 919 indicates whether the service is inbound or outbound.
Note: Inbound and Outbound refer to the direction of data flow, not the request.
Kb Transferred SUBSTITUTE SHEET (RULE 26) WO 99/34544 PCr/US98/27396 This field 923 shows the amount of data transferred in inbound or outbound direction. As shown, the amount of data can be in kilobits transferred.
Additionally, the amount of data can be referred to as a percentage of all services.
Connect Response Time This field 925 indicates an average time to establish a session. The connect response time is in milliseconds, but is not limited to this time. The minimum and maximum connect response time is also shown in parenthesis.
Request Response Time This field 927 indicates an average response time for an application request.
The request response time is in milliseconds, but is not limited to this time.
The minimum and maximum request response time is also shown in parenthesis.
Note: This measure is application specific and does not apply to all services.
For example, for HTTP, it is the time taken by a URL to start sending data after a request for a file was made by a Web browser.
Total Sessions This field (not shown) indicates the total number of sessions established for this service.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the SUBSTITUTE SHEET (RULE 26) server.
Tune This field (not shown) indicates the last time the service was active.
2. Server Tab Fig. 10 is a simplified diagram 1000 of a representation of a graphical user interface for a server tab according to the present invention. Upon selecting or clicking the server tab 915, screen 1000 appears. The dialog box displays cumulative traffic statistics for every active server. The server tab provides the following information, but is not limited to such information:
Server This field 1001 shows the server host name, URL or IP address. Summary statistics for all servers are also shown.
Note:
= In one aspect of the invention, the present tool can profile up to 256 servers. Subsequent traffic from new servers are indicated as 'Others'.
= Host names can also be displayed in some embodiments.
Kb Transferred This field 1003 shows the amount of data transferred from the server. As shown, the amount of data can be in kilobits transferred. Additionally, the amount of data can be referred to as a percentage of all services.
Round Trip Time This field 1005 indicates an average round trip delay for packets sent to the server. The round trip time is in milliseconds, but is not limited to this time.
The minimum and maximum round trip time is also shown in parenthesis.
SUBSTITUTE SHEET (RULE 26) Connect Response Time This field 1007 indicates an average time to establish a session with the server.
The connect response time is in milliseconds, but is not limited to this time.
The minirnum and maximum connect response time is also shown in parenthesis.
Total Sessions This field 1009 indicates the total number of sessions established to the server.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the server.
Access Speed This field (not shown) indicates the bottleneck speed for the route between the present tool as a host and a server.
Data Retransmits This field (not shown) indicates the percentage of data packets that were retransmitted by the server.
Time This field (not shown) indicates the last time data was received from the server.
SUBSTITUTE SHEET (RULE 26) 3. Client Tab Fig. 11 is a simplified diagram 1100 of a representation of a graphical user interface for a client tab according to the present invention. When the client tab 917 is selected or is clicked using a user interface, screen 1100 appears. The dialog box displays the cumulative traffic statistics for the clients. The client tab provides the following information, but is not limited to such information:
CGent This field 1101 shows the client host name or IP address. Summary statistics for all clients are also shown.
Note: The present tool can profile up to 256 clients in some embodiments.
Subsequent traffic from the clients are indicated as ' Others' .
Kb Transferred This field 1103 shows the amount of data transferred to the client. As shown, the amount of data can be in kilobits transferred. Additionally, the amount of data can be referred to as a percentage of all services.
Round Trip Time This field 1105 indicates an average round trip delay for packets from this client. The round trip time is in milliseconds, but is not limited to this time.
The minimum and maximum round trip time is also shown in parenthesis.
Connect Response Time This field 1105 indicates the average time to establish a session from the client.
The connect response time is in milliseconds, but is not limited to this time.
The minimum and maximum connect response time is also shown in parenthesis.
SUBSTITUTE SHEET (RULE 26) Total Sessions This field 1109 indicates the total number of sessions established from the client.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the server.
Time This field (not shown) indicates the last time the client received data through the link used by the present tool.
The present invention provides the aforementioned tool for profiling a variety of information from a flow of information at a communication link. The tool has an easy to use graphical user interface, which can sort information by at least services, client, or server, depending upon the application. The illustrations shown are merely used as examples and should not limit the scope of the claims herein.
In a specific embodiment, the present invention with graphical user interface begins profiling upon installation. In particular, the present tool is installed onto a server to automatically start profiling traffic in inbound and outbound directions without any further configuration. The present tool can be stopped and restarted manually from a user interface.
While the present tool is stopped, profiling is interrupted temporarily.
The present invention provides additional easy to use graphical tools to monitor and profile traffic. In one aspect, the present invention takes advantage of a Windows NTTM
Performance Monitor to monitor traffic for any measurement or control rule that is created.
In another aspect, the present invention can launch the Performance Monitor from the SUBSTITUTE SHEET (RULE 26) 'Administrative Tools' Program group and select counters for monitoring incoming and outgoing traffic from a link.
Fig. 12 is a simplified graphical user interface 1200 to launch a performance monitoring tool according to the present invention. This interface is merely an illustration and should not limit the scope of the claims herein. A method for launching the present tool occurs, in part, by selecting or clicking on the performance monitor tab 1201.
The display shows available traffic classes 1201 (e.g., FTP, HTTP, PointCast), which have been defined in the traffic policy. Note that a traffic class is not a rule. There may be more than one rule that belongs to the same traffic class. Traffic classes are created when rules are edited. A
traffic class is defmed by at least a source, destination, and service properties. The display includes a group of option buttons 1207 titled monitor, which allows a user to specify whether the user wants to monitor bandwidth consumption 1209, connect time 1211, or connect retries 1213 for the selected classes. A prompt box 1215 above the option buttons 1207 provides a brief explanation of the selected option. A Launch button 1205 launches the performance monitor too. To launch the present performance monitor tool:
1. Select one or more traffic classes 1203 in the list.
2. Choose monitor by clicking on an appropriate option button (e. g. , bandwidth consumption, response time, failures) 1207 in the monitor group.
3. Push launch button 1205.
As merely an example, Fig. 13 is a simplified graphical user display 1300 for bandwidth consumption according to the present invention. As shown, the Fig.
is an example of Class Bandwidth 1305 monitoring for a few services 1307 such as FTP, HTTP, etc. over a 56 Kbit Internet link. The vertical axis 1302 illustrates a bandwidth scale from "0" to "56.0"
kbits and the horizontal axis represents time 1306. The plurality of line plots 1304 each represent one of the services 1307, which are each color coded 1301 for easy reading by the user. The display also includes an object 1309 and a computer 1311, which is being used to SUBSTITUTE SHEET (RULE 26) monitor the traffic. Accordingly, the present display includes a graphical portion 1310 and a text portion 1320. The graphical portion includes the plurality of plots representing the services for bandwidth consumption as functions of time. The text portion is in the form of a legend, but can also include other information.
The illustration in the above Fig. is merely an example and should not limit the scope of the claims. Although the present example has been described in terms of bandwidth consumption, the present performance monitor tool can also be used to monitor a variety of other parameters, as discussed above. These other parameters include, among others, connect time, or connect retries for the selected classes.
Furthermore, the present tool has other types of charts such as a bar chart, a pie chart, and the like. Of course, the parameter being profiled and monitored depends upon the application.
In an alternative embodiment, the present invention provides a user interface for modifying the plots or charts, such as the one previously described, as well as others.
Fig. 14 is a simplified interface tool 1400 used to modify chart styles, scales, charting intervals etc. This tool is merely an example and should not limit the scope of the claims herein. The present tool has an "OK" button for saving or storing selected chart options. A
"cancel" button 1403 is also shown to delete or remove selected chart options.
A help button 1405 is shown to identify features of any of the chart options. Numerous chart options 1407 exist. For example, opiions include, among others, a legend, a value bar, a vertical grid, a horizontal grid, and vertical labels. To select any one of these options, the user clicks onto the box located next to the option or enters the underlined key designating the option. Chart options also include a gallery 1409, either in graph or histogram form.
Additionally, the chart can have a maximum vertical scale 1411 such as the 56 for 56 kbits/second.
Furthermore, the chart can have a refreshing or updating cycle time 1413. In one aspect, the cycle time can be manually updated. Alternatively, the cycle time can be periodically updated. When using the periodically updating feature, a time interval (e.g., seconds) needs to be specified and entered into a field, as shown.
Fig. 15 is a simplified graphical user interface 1500 for adding or specifying an additional chart according to the present invention. This interface or tool is merely an example and should not limit the scope of the claims herein. This interface allows the user to select the parameters to be monitored on the chart. These parameters include, among others, SUBSTITUTE SHEET (RULE 26) the computer to be monitored 1507, the object 1509, the counter 1511, and the instance 1514.
Depending on the types of parameters being monitored or profiled, specific visual details of the plots or charts are also selected. These details include the plot color 1513, the plot width 1519, the plot style 1517, and others. A counter definition 1515 is also made or selected.
Once all the changes have been made or selected, the user can add the changes to be monitored by the tool by pressing or selecting the add button 1501.
Alternatively, the user may start over by selecting the cancel button 1503. If the user would like an explanation on any one of the features described in the tool, the user may selected either the explain button 1505 or the help button 1506. Of course, this user interface is merely an example and should not be limiting any manner outside the spirit and scope of the claims.
In yet an alternative aspect, the present monitoring or profiling tool has a save feature for storing the chart or plot. In particular, the present tool can save snapshots of measurements to a disk file or the like. As merely an example, the present tool saves snapshots using the following sequence of steps, which should not be construed as limiting:
Go to view/log in the tool to configure a log file;
Add measurements to the file and start and/or stop logging.
Furthermore, the present tool provides congestion, utilization, and performance degradation reports, which make day to day troubleshooting much simpler and serve to justify or validate policy setting decisions. For example, a chronic problem affecting a service through a day period (i.e., 24 hour) can be monitored by a combination of real-time monitoring, which will be described in more detail below, and congestion reports. By monitoring and using the reports, it may be determined that the affected service is not getting its due share of bandwidth, or a limitation exists with the server or in the Internet backbone.
Conclusion In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. Many changes or modifications are readily envisioned. For example, the present invention can be applied to manage a variety of TCP/IP network traffic types for the Internet and Intranet. Further, the techniques SUBSTITUTE SHEET (RULE 26) can also be applied to Novell SPX, Xerox XNS or any protocol with a similar 'flow-control' design that utilizes windows and acknowledgment signals (similar to ACK).
Alternative embodiments of the present invention can also be applied to a 'legacy' private WAN running IP as well as native Novell protocols if there is a need.
(e.g., file server and client/server traffic). Further, embodiments of the present invention can include monitoring, billing, and reporting features, thus allowing for enhanced client billing and internal cost accounting of network usage.
These techniques are preferably implemented within a firewall platform to solve the provide the following benefits: bidirectional bandwidth management of network links carrying TCP traffic; reactive (short-time scale) and proactive (long time scale) control mechanisms; and gateway (local) and end-end (global) techniques for bandwidth control.
This solution reduces their contribution to congestion in the Internet; and operation in a present day heterogeneous wide area networks, such as the Internet, without requiring any client, server or router changes.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.
SUBSTITUTE SHEET (RULE 26)
Profiling is intended to provide long term cumulative snapshots of traffic for capacity planning or setting traffic rules.
The above defmitions are merely intended to assist the reader in understanding some of the terms described herein. They are not intended, in any manner, to limit the scope of the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.
SUBSTtTUTE SHEET (RULE 26) SYSTEM OVERVIEW
Fig. 1 illustrates a simplified system 100 according to an embodiment of the present invention. The system 100 is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The present invention can be embodied as a TrafficWareTM
firewall server 110 from Ukiah Software, Inc, but can be others. System 100 typically includes a file server 120, and a plurality of computers 130-150, coupled to a local area network (LAN) 160, and other elements. Firewall server 110 includes a typical connection to a wide area network (WAN) 170 and to a remote LAN 180 (such as an Intranet) and a typical network connection 190 to the Internet 200. Attached to Internet 200 are Web servers 210 and other computers 220.
As illustrated, computers such as computer 130, 140, and 210 communicate using any one or multiple application layer protocols such as Telnet, file transfer protocol (FTP), Hypertext transmission protocol (HTTP), and the like. Further, communication across WAN 170 and across network connection 190 implements transport layer protocols such as transmission control protocol (TCP), universal data protocol (UDP), and the like.
LAN 160 and LAN 180 are preferably based upon network protocols such as Internet protocol (IP), IPX from Novell, AppleTalk, and the like. As shown in Fig. 1, network connection 190 may be accomplished using T1, ISDN, Dial-up, and other hardware connections. Computers 120-150 and 210-220 may be any suitable make or model of computer that can be coupled to a network. The system can also include a variety of other elements such as bridges, routers, and the like.
In an alternative specific embodiment, the present invention may be applied to a system with various links accessed in servicing a browser request at a remote web server.
In this embodiment, a client could be dialing in via a 28.8kbit dial up modem to a local Internet service provider (ISP), where the ISP may be connected to the Internet by a T1 link.
A web server may be on a 10 Mbs Ethernet LAN, which is connected to another ISP via a 56 K frame relay. The web server's ISP may be connected to its carrier via a T3 line. The client ISP carrier and the server ISP carrier may both be connected by an ATM
backbone or the like. Because of this asymmetry in this embodiment, any traffic management solution should take into account these variations including traffic speed and data format described SUBSTITUTE SHEET (RULE 26) above. Moreover, simply upgrading the capacity of a link, in the access path, may not offer a viable solution. This present embodiment may have the bandwidth requirements shown by way of Table 1, for example.
Table 1: Bandwidth R uirements Users Bandwidth Service Offered Internet developers, individuals, 28.8 to 56 Kbps Dial-up services, ISDN
international locations where bandwidth is expensive Small to medium-sized organizations with 56 Kbps to 1.5 Mbps Fractional TI, frame relay moderate Internet usage Medium sized organizations with many 1.5 Mbps Dedicated TI circuit moderate users, smaller organizations re uirin huge amounts of bandwidth Standard bandwidth for Ethernet-based 10 Mbps Ethernet, token ring (4 Mbps LANS or 16 Mbps) Bandwidth usage for large organizations or 45 Mbps Dedicated T3 circuit Internet backbones Huge bandwidth LAN backbone usage for 100 to 1.000 Mbps Fast Ethernet, gigabit medium to large organizations (hundreds or Ethernet thousands of users) As shown above, there exist a large number of diverse applications and protocols that are widely used and have their own performance requirements. For example, applications such as mail (e.g., SMTP) and news (e.g., NNTP) are not interactive and are therefore not sensitive to delay. On the other hand, applications such as real-time conferencing are extremely sensitive to delay but not to packet loss. Applications such as TELNET and DNS
do not utilize significant bandwidth, but are sensitive to delay and loss.
Conversely, applications such as FTP consume a great deal of bandwidth but are not that sensitive to delay. Generally, network applications can be categorized as:
1. Interactive (e.g., delay sensitive) versus non-interactive (e.g., delay tolerant);
2. Bandwidth intensive (bulk data) versus non-bandwidth intensive; and SUBSTtTUTE SHEET (RULE 26) 3. Bursty versus non-bursty.
These categories are merely illustrative and should not limit the scope of the claims herein.
Additionally, some application requirements are dependent on the context of use and the nature of data being accessed. Such applications can be described as being nominally interactive or nominally bandwidth intense. This means the description applies to many but not all the situations in which they are used.
As merely an example, Table 2 provides some illustrations for these categories.
Application Class Examples Low-bandwidth, delay DNS. PING, TELNET, CHAT, sensitive, highly interactive COLLABORATION
High bandwidth, delay sensitive Real-time audio and video High Bandwidth, nominally interactive Web service requests, file downloads Non-interactive Mail and news Table 2: Application Spectrum As shown in Table 2, low-bandwidth, delay sensitive, and highly interactive applications include, among others, DNS. PING, TELNET, CHAT, COLLABORATION. High bandwidth and delay sensitive applications including at least real-time audio and video.
Additional applications for high bandwidth and nominally interactive, or non-interactive have also been shown. Again, these applications are merely provided for illustration and should not limit the scope of the claims herein.
The present invention can also be used with a number of various files. For example, a number of common applications, such as FTP and HTTP, can handle a wide variety of files. The file types being transferred and downloaded place different demands on the underlying infrastructure. Index and HTML files take up limited bandwidth but have very mundane contents. On the other hand, GIF, JPEG and MPEG, RA and AVI files take up a lot more bandwidth but provide a rich multimedia experience to the end-user.
In fact, push SU6STITUTE SHEET (RULE 26) technologies such as PointCast basically download rich-multimedia bandwidth-intensive files.
The present invention can also be used with a variety of user requirements.
For example, networks are facing an explosion in the number of (inter) networked applications and data accessible through them. Network resources are increasingly being used for a wide variety of purposes, ranging from business critical to personal. This means that policies must ensure that scarce resources (e.g., Internet bandwidth) are utilized with the goal of maximizing the returns to the organization. These benefits can come from direct revenue generating activities or from improved productivity (or reduced loss of productivity).
As shown in Table 3, for example, at a mythical company called "Shebang Software Inc. "
the highest bandwidth priority has been allocated to technical support.
However, there is no hard and fast rule. As with security policies, decisions should be consistent with the needs of the organization.
Table 3: Shebang Software User Priorities Users Application Class Reasons Technical support Mission critical Needs most bandwidth to deal with customers who need assistance Sales and marketing Critical Needs bandwidth to deal with potential customers. Answer inquires, make quotes, transmit multimedia presentations Upper management and middle Casual Needs bandwidth to perform tasks management, administrative necessary to run the business Development and manufacturing Personal Needs bandwidth to send e-mail, subscribe to Push technologies The present invention takes into account, in one or more embodiments, the factors which are described specifically above. Although the above has been generally SUBSTITUTE SHEET (RULE 26) described in terms of a specific type of information, other types of information on a network can also be used with the present invention. Additionally, the present invention has been described in general to a specific system. For instance, the present bandwidth management tool can be applied at a network's Internet access link. Alternatively, the present tool can be applied to a private WAN link to a remote corporate site or an access to a server farm (e.g., a group of servers located in a special part of the network close to an access link, e.g., in a web hosting environment), Alternatively, the present invention can be applied to key servers (e.g., database/web server) within an organization servicing internal and/or external users.
Furthermore, the present bandwidth management tool can be applied to any combination of the above or the like.
Fig. 2 is a simplified block diagram 200 of details of system architecture according to an embodiment of the present invention. The block diagram is merely an illustration and should not limit the scope of the claims herein. The architecture includes a variety of layers that each interface to each_other as depicted by, the layers. The system includes a network layer 211, which interfaces to incoming and outgoing information to the network. The network can be one of a variety including; among others, Ethernet and Token R.ing: A physical layer 209 is disposed above the network layeir 211. The physical layer can be personal computers, which are commonly called PCs, or network interface computers, which are commonly called NCs, or alternatively workstations. As merely an example, a personal computer can be an IBM PC compatible computer having a'586-class, based microprocessor, such a Pentium''m from Intel Corporation, but iis not lirnited to such a computer or processor. An operating system ("OS") is used on. the computer such as WindowsNTTM from Microsoft Corporation, but can also be ottier OSs. The system.is also coupled to a graphical user interface ("GUI") 201 and is coupled to directory services such as, for example, LDAP, but can be others. A detailed discussion of directoq services is described in U.S. Paterits 6,212,558 and 6,047,322.
Directory services 224 and GUI 201 couple to an application programming interface ("API") 223. The API is coupled to a traffic n-anageinent or bandwidth management tool with at least three modules, including a policy engine module 231, a FAST module 229, and a FAIR module 227, which will be discussed in more detail below, but is not limited to these modules. The bandwidth management tool 208 can be predominantly software based and is substantially free from any significant hardware or software changes in the network. In a preferred embodiment, the bandwidth management tool 208 can be loaded onto a server without any changes to hardware. In an alternative preferred embodiment, the tool can install, configure, and operate on a conventional IBM
compatible PC running and operating system such as, for example, Windows NT, but can be others. The tool can be deployed at any appropriate point in the network data path. The tool can also be stand-alone at the WAN access point (e.g., behind the Internet access router or behind a firewall), with a conventional firewall or with an NT based proxy/caching server or application server (e.g., a Web server).
Tool 208 performs incoming and/or outgoing management of information over the network of computers. In a specific embodiment, traffic management tool 208 performs inbound and outbound monitoring arid control of flows by application, source address, destination address, URL, time of day, day of week, day of month, and other variations. In a specific embodiment, tool 208 also monitors, controls, and produces reports and alarms, which can enhance a whole spectrum of traffic monitoring and control activities ranging from bandwidth/latency control to capacity planning.
In a specific embodiment, the bandwidth management tool adapts to "real"
changes on any pre-existing networking system. For example, network infrastructure management involves a continuous process of monitoring, reporting, and deploying changes to match network growth or changing needs in a growing office, for example.
These changes exist at various levels and time scales. As merely examples, the network changes can be to enforce a QoS Policy for a critical service, add WAN bandwidth, segment the network, upgrade a router, choose a guaranteed service level for a web site (e.g., user's own wet site), or notify "Mr. Hog" (i.e., a user occupying too much bandwidth) that he should schedule his large personal downloads at more prudent times such as late at night, for example.
BANDWIDTH MANAGEMENT PROCESS
The bandwidth management tool can employ these changes using, for example, the process shown in Fig. 3. This process is merely and illustration and should not limit the SUBSTITUTE SHEET (RULE 26) scope of the claims herein. As shown, Fig. 3 is a simplified diagram 300 of a traffic management cycle according to an embodiment of the present invention. The traffic management cycle is depicted as a continuous cycle, which includes a monitoring phase 301, a creating/applying policy phase 303, and a reporting/alarming phase 305, but is not limited to these cycles. That is, these cycles can be separated or combined depending upon the application. By way of this cycle, the tool can adapt to any changes to the networking system according to the present invention.
In an aspect of the present invention, the present tool can monitor and control activities at various times, e.g., seconds, days, weeks, months, years. Some details with regard to these control activities are shown below under the headings.
1. Second to second The tool provides second to second time scale monitoring and control of incoming and outgoing traffic over the network. As merely an example, the tool ensures that critical or more important traffic gets a right of way during traffic bursts and provides bandwidth enforcement. Multiple users of the network at a specific time can cause the traffic burst. Alternatively, multiple sessions on the network at a specific time can cause the traffic burst. Once the traffic burst is detected, the tool has a control device, which provides bandwidth enforcement to ensure that the more important traffic gets through the network.
2. Day to day The tool provides day to day time scale monitoring and control of incoming and outgoing traffic over the network. As merely an example, the tool manages time of day congestion, and responds to intermittent problems or perceived problems. The tool generally deals with problems or limitations that are very specific and isolated to particular users or particular services at particular times that need to be tracked down quickly.
3. Week to week The tool provides week to week time scale monitoring and control of incoming and outgoing traffic over the network. The tool analyzes traffic usage performance patterns, what services or hosts are active on the network, and troubleshoots chronic problems. In SUBSTITUTE SHEET (RULE 26) particular, the tool looks at aggregates, such as a particular segment of the network, and compares Websites or compares groups of users for usage of bandwidth and frequency of usage.
4. Longer term activities The tool provides long term time scale monitoring and control of incoming and outgoing traffic over the network. The tool implements changes in organizational priorities, in billing. The tool also provides service for new applications as they are introduced, and provides for capacity planning for network resources. The present tool can also be used with network stress testing tools to obtain detailed analysis of flows and traffic behavior with/without policy enforcement before a new application is deployed to change the network infrastructure.
Based upon the above description, the present tool can be used to monitor and control incoming and outgoing traffic over a variety of time frequencies. The time frequencies include second by second, day to day, or long term, and combinations thereof, depending upon the application. Of course, the time frequency used depends upon the particular network and applications.
Figs. 4-7 are simplified diagrams of systems according to various embodiments of the present invention. These diagrams are merely illustrations and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, alternatives, and modifications. These systems show various deployment scenarios according to the present invention.
1. Internet Service Provider (ISP) Fig. 4 is a sirnplified diagram 400 of the present tool in an ISP environment according to the present invention. The diagram 400 includes a variety of elements such as an ISP LAN 401, which is coupled to network elements including a remote access concentrator 403, a web server 417, an FTP server 415, a router 413, a news server 411, and others. The too1405 is coupled between the ISP LAN and router 407, which is connected to the Internet 409. In this embodiment, the ISP is providing a number of services to its SUBSTtTUTE SHEET (RULE 26) customers and the present tool sits by the Internet link and manages inbound and outbound traffic.
2. Web Hosting Deployment Fig. 5 is a simplified diagram 500 of the present tool in a web hosting environment according to the present invention. The diagram 500 includes a variety of elements such as a LAN BackBone 501, which is coupled to network elements including web servers 503, 511, 513, and others. The present tool 505 is coupled between LAN
501 and router 507, which is connected to the Internet 509. In the present embodiment, the tool is being used to manage inbound and outbound traffic between some Websites and the Internet.
In a specific embodiment, most of the data being transmitted is multimedia-based, but is not limited as such data.
3. End-User Deployment Fig. 6 is a simplified diagram 600 of the present tool in a campus environment according to the present invention. The diagram 600 includes a variety of features such as a campus network 601, which is coupled to network elements such as a desktop PC
603, a UNIX computer 617, an NT Server 615, a web server 613, directory services 611, and others. A bandwidth management tool 605 is coupled between campus network 601 and router 607, which is coupled to Internet 609. In this embodiment, a LAN or WAN
supports a number of different setups and configurations, which are compete for bandwidth to access the Internet. The present tool acts as an arbitrator for implementing rules, enforcing policies, and setting admissions for classes, as well as perform other acts.
4. Private WAN
Fig. 7 is a simplified diagram 700 of the present tool deployed for a large corporation that has an Intranet as well as an Internet. The diagram 700 includes a variety of elements or "children" such as a connection to Frankfurt 715, a connection to London 713, a connection to Hong Kong 717, and a connection to Paris 719. Each connection or child includes a router 705A, E, D, C, and the present tool 703A, E, D, C, which is coupled between the router and the hub ("HQ"). In a WAN-based environment, for example, HQ 701 SUBSTITUTE SHEET (RULE 26) is the hub that handles a number of independent systems (e.g., Frankfurt, London, Hong Kong, Paris), which can be LAN-based. In this embodiment, the present too1703B
also sits by the Internet 711 and is used to allocate bandwidth between the competing children, e.g., Frankfurt, London, Hong Kong, Paris. Router 705B is coupled between tool 703B
and Internet 711.
Although the above descriptions have been made in terms of deploying the present tool in selected environments, the present tool can also be deployed in other environments. For example, the present tool can be deployed in any combination of the above. Alternatively, the present tool can be deployed in any portion of the above environments. Of course, the type of environment used by the present tool depends highly upon the application.
In a specific embodiment, the tool provides an easy to use interface or graphical user interface ("GUI") for performance monitoring and profiling (e.g., accounting).
Profiling can be based on active services, clients and servers, among other parameters.
Additionally, profiling of the network can be started as soon as the tool is installed into the server of the network. Accordingly, the tool provides immediate accounting and service measurement on a variety of QoS measures.
In a specific embodiment, the present tool generally uses two mechanisms to implement efficient traffic monitoring and traffic control. These mechanisms include processes performed by the FAST module and the FAIR module, which are shown in Fig. 2, for example. Additionally, the present tool uses a policy engine module 231, which oversees the FAST module 229 and the FAIR module 227. Some details of these modules are described as follows.
1. FAST Module (Flow Analysis and Session Tagging) The FAST module generally provides for monitoring of incoming and outgoing information to and from the network or link. Flow Analysis and Session Tagging ("FAST") implements rich, application level traffic classification, and measurement.
This operation is accomplished without introducing slow data paths to minimize latency and maximize overall throughout of traffic through the tool management engine. As shown in the Fig., the FAST
module provides for classification 203 of information such as parameters 213 including SUBSTITUTE SHEET (RULE 26) application, presentation, session, transport, and network. The FAST module also provides for measurement 219 of various parameters. The FAST module is coupled to the API.
2. FAIR Module (Flow Analysis and Intelligent Regulation) The FAIR module generally implements traffic control and manages bandwidth of incoming and outgoing information to and from the network or link. Flow Analysis and Intelligent Regulation ("FAIR") implements traffic control based on a combination of flow control and queuing algorithms. FAIR's objective provides inbound and outbound traffic management for meaningful time intervals, reducing the load on packet classifiers and packet schedulers. The FAIR module controls 205 incoming and outgoing information to and from the network. Additionally, the FAIR module controls 205 by parameters 215 such as class, session, burst, packet, and others. The FAIR module also controls time 217 of allocating bandwidth for these parameters. The FAIR module is coupled to the API.
3. Policy Engine Module The policy engine module 231 oversees the FAST and FAIR modules. The engine module also interfaces with the API. In an embodiment, the policy engine module includes a security policy 201, a traffic policy 202, and other policies 221.
The security policy provides parameters for securing the present tool. The traffic policy defmes specific limitations or parameters for the traffic.
Some defmitions about the various modules have been described above. These defmitions are not intended to be limiting. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. Additionally, the modules described are generally provided in terms of computer software. Computer software can be used to program and implement these modules, as well as others. The modules can be combined or even separated, depending upon the applications. Functionality of the modules can also be combined with hardware or the like. In a specific embodiment, the present modules are implemented on an WindowsNTTM operating system, which has been developed by Microsoft Corporation. Of course, other operating systems can also be used. Accordingly, the present modules are not intended to be limiting in any manner.
In an embodiment, the present tool can be configured based upon at least the SUBSTRUTE SHEET (RULE 26) following components - traffic classes, traffic policies, traffic rules, and traffic entities. Some information about these components are described below.
1. Traffic Classes The present tool identifies data flows at a network site based on traffic classes.
A traffic class is any combination of the following, but is not limited to these:
IP address, subnet, network, netgroup, or range of source or destination;
URL of the sender or group of URLs;
Service (e.g., HTTP, FTP) or groups of services;
FTP and HTTP, file types can be selected as well;
Time of day, day of week/month; and Inbound and outbound information.
As shown above, traffic classes are directional. Traffic classes configured for inbound traffic are managed separately from traffic classes configured for outbound traffic.
For example, the present tool may decide to guarantee a minimum bandwidth to critical traffic so that it is not affected by congestion from large downloads. Additionally, the present tool may want to monitor Push traffic for a while and then choose to limit it if it is perceived as a problem.
Traffic classes can also be for measurement only or for control and measurement in some embodiments. These are merely examples and should not limit the scope of the claims herein.
2. Traffic Policies Traffic policies are generally mechanisms used to control the traffic behavior of specific classes. In an embodiment, the present tool can configure policy properties which provide, for example:
Bandwidth guarantees - granting classes a minimum bandwidth in the presence of congestion or competition;
Bandwidth limits - establishing a limit on the total bandwidth used by the class;
SUBSTITUTE SHEET (RULE 26) Setting priorities - establishing a priority order foir bandwidth limiting or servicing traffic from a class. (That is, high priority classes are serviced first and are affected the least during contention for baindwidth. Lower priority classes are serviced in order of priority and may be more affected by congestion or contention);
Admission control- establishing conditions under which a new network session or service request is admitted or not admitted. (This kind of policy establishes.
a broad bandwidth control or service quality for sessions already admitted).
As shown, the present invention provides policies such as bandwidth guarantees, bandwidth limits, setting priorities, admission control, and others. It may assist the reader in understanding some of the terms used in the policies by drawing an analogy with a geographical highway for automobiles. For example, bandwidth relates to how fast one can go (e.g., fast or slow lane) once a user has entered the stream of'traffic on the highway. That is, the physical limit for speed in the specific lane chosen. Priority is analogous to how quickly the user is able to enter the highway and move into a de<.,ignated lane, and how often the user may have to temporarily give way to other vehicles during the drive.
Admission control is analogous to the metered lights at the entrance of the freeway where one is made to wait under certain conditions. . Of course, depending upon the applications other analogies can be used to explain the policies. Additionally, the policies are merely examples and should not limit the scope of the claims herein.
3. Traffic Rules .
A rule generally includes a traffic class and a policy associated with the class.
A class can have several policies that apply at different time intervals. -'Rule' is also used to refer to the, policy or to a specific row in the present tool user initerface.
4. Traffic Entities The present tool refers to entities in at least two different contexts:
defining traffic classes and viewing traffic profiles. For example, a network entity generally refers to an IP address, host, subnet, IP net, IP range, URL or a group of other network entities. A
service entity refers to a single service or a group of services. A native entity is referred to in viewing traffic profiles. No rule setting or configuration is required to monitor these entities.
When the present tool is installed, it begins to profile traffic based upon detected services, clients, or servers, all of which are called native entities.
5. Guidelines for Developing Traffic Policies The present invention provides some guidelines for developing traffic policies.
For example, to develop meaningful and effective traffic policies, the present tool may need to understand and take into account one or more of the following:
= The kind of business being performed by the user over the Internet. If the user is an ISP, the user may need to develop a business/pricing model that leverages the features of the present tool. If the user is managing corporate access to the Internet, the user may want to identify any business critical services being provided over the Internet = The priority of clients, servers and URLs hosted in the user's network or servers access over the Internet. This can be organized as business critical, casual and personal.
= The properties of different applications being used, whether they utilize lots of bandwidth or not. The user may also need to account for the type of files commonly download by users or from the Web site.
= Measure and analyze traffic using the present tool's profiles.
SUBSTITUTE SHEET (RULE 26) Additionally, monitoring of selected entities (e.g., users, services) may also be useful.
In a further embodiment, the present tool provides some general guidelines of some commonly used applications. These guidelines should be used in conjunction with business driven priorities, traffic profiling, and selective real-time monitoring to establish an effective traffic policy. Selected guidelines are defined as follows, but are not limited to these.
= Delay-sensitive low bandwidth applications, such as TELNET
and DNS, are controlled best by setting a high priority policy.
The present tool can give the highest priority to all network control traffic, such as QoS signaling, session establishment, domain lookup and routing protocols.
= Streaming multimedia applications, such as Real Audio/Video and Vxtreme, can hog allot of bandwidth but are also delay and bandwidth sensitive. If they are not critical, they are controlled best by setting a high priority and a policy to limit admission of sessions so that bandwidth use is capped but admitted sessions have a reasonable quality.
= Push technologies, such as PointCast and Marimba, download large files, are not delay or bandwidth sensitive and usually not business critical. They are best controlled by a limiting bandwidth policy and a low priority.
= Bulk-data non-interactive applications, such as SMTP and NNTP, should be guaranteed a small bandwidth minimum so that they are not totally squeezed out by congestion or control policies.
SUBSTITUTE SHEET (RULE 26) = Bulk-download, nominally interactive applications, such as FTP
or some HTTP downloads, are commonly used in a variety of situations, ranging from critical to casual. Differentiating various types of usage in this case can usually be made only on the basis of file types and/or source or destination addresses. In this case, a small minimum can be guaranteed for more important use.
= In bulk-download applications (e.g., file size> 20 K Bytes), overall congestion and burstiness can be controlled by slightly limiting this traffic, even if it is just a little below the total available bandwidth (e.g., 90 b). The present tool can provide smoothing controls on this traffic without impacting overall perceptible performance for these downloads. This is particularly useful at lower link speeds (128 K and below).
= Mission critical applications, such as Lotus Notes, Oracle SQLNet, and LDAP, are controlled best by setting a high priority with a guaranteed bandwidth minimum.
The above provides some guidelines for commonly used applications according to the present invention. Using the above guidelines, the present tool can effectively allocate bandwidth on a network, for example. Again, the above guidelines are merely examples and should not limit the scope of the claims herein.
In a specific embodiment, the present tool provides a comprehensive, flexible, rule-based paradigm for implementing traffic control, as illustrated by a simplified flow diagram 800 of Fig. 8. This flow diagram 800 is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. Before explaining the flow diagram, it may assist the reader by reviewing some general terms used herein.
SUBSTITUTE SHEET (RULE 26) These terms include, among others, "rules" and "classes" and "policies. "
Rules can be created for very specific groups of flows or more general groups of flows, which are commonly all the stuff that transmits to and from a link to a gateway point.
Groups of flows are also referred to as traffic classes, but are not limited to such classes.
Classes also can be defined by source, destination, application, file types, URLs, and other features. Policies can be specified to control traffic flows in terms of overall bandwidth guarantees, bandwidth limits, priority of service, how individual sessions within a class are serviced or admitted, and other aspects. The present tool also has intelligent policy validation that prevents users from defming any contradictory or ambiguous rules. Policy validation is generally a higher level check used by way of the present method.
The present method occurs at start, which is step 801, for example. In general, a flow of information or data or packets of information enter a gateway point, where the present tool sits. The present method classifies (step 803) the flow of information.
Groups of flows can be referred to as traffic classes, but are not limited to such classes.
Classes also can be defmed by source, destination, application, file types, URLs, and other features. Other examples of classes were previously noted, but are not limited to these classes. In general, step 803 classifies the flow of information received into one of a plurality of predetermined classes.
The present tool measures parameters for each of the classes in step 805, which were received, for example. These parameters are based upon the policy or rule, which may be applied in a later step. As merely an example, parameters include the class itself, file sizes, and other information, which can be used by the policy or rule to apply the policy or rule to improve the quality of service for the network. After measuring. the parameters, the present method applies a tiune stamp (step 807) on the parameters to correlate the class of information received to a time, for example.
A step of determining whether to apply a policy occurs in the next step 809.
For example, if the class and the time (and the link state in some embodiments) meet predetermined settings, the policy is applied to the class in step 811 through branch 810.
Alternatively, if one of the elements including the class, the time, or the link state do not meet the predetermined settings, the policy does not apply and the process continues to measure parameters through branch 808. Alternatively, the process continues to measure parameters SUBSTITUTE SHEET (RULE 26) through branch 821 after the policy is applied to the flow of information for the class.
Depending upon the application, the policy is used to improve the quality of service of the network by performing at least one of a number of functions for the class of information from the flow. These functions include, among others, bandwidth guarantees, bandwidth limits, setting priorities, admission control. The present process can also halt or ' stop as shown in step 815. The steps occur, in part, by way of the modules, which were previously described, but can also occur using other techniques including a combination of hardware and software, for example. These sequence of steps are merely illustrative and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other modifications, alternatives, and variations.
In a preferred embodiment, the present invention uses a variety of graphical user interfaces for profiling and monitoring traffic. Figs. 9A-15 are simplified representations of graphical user interfaces for monitoring traffic according to the present invention. These representations are merely illustrative and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.
Fig. 9A is a simplified flow diagram 950 of a profiling method according to the present invention. Profiling or monitoring traffic can occur using one of a plurality of user interfaces or graphical user interfaces. The present invention provides a profiles tab 953, which can be selected using a mouse or keyboard interface. The present method begins with a start step, which is step 951. Upon selecting a profiles tab 953, one of a plurality of tabs is prompted. These tabs represent services 957, server 959, and client 961. These tabs display relevant traffic statistics by every active service, server and client, respectively. By selecting one of the tabs, the present tool sorts data or information in ascending order by clicking on any header (e.g., Kb Transferred), as illustrated by Fig. 9 for a service tab 900.
Other functions that can be performed using one of the profiles and the graphical user interface include:
= Click the Refresh button, all data is updated from the profiling engine.
= Click the Reset button 907, clears all the respective data from the profiling SUBSTITUTE SHEET (RULE 26) engine.
= Click the Save As 909 button to save the respective data to a log file. The data is saved as tab-separated text.
Each of the present user interfaces also includes function keys 901 and a tool bar 903. Upon selecting the profiles tab, a profiles light or display indication illuminates 911. As shown, the main profiles tab also includes tabs for services 913, server 915, and client 917. Additional features of the various tabs including the services tab, the server tab, and the client tab are described below and refer to Figs. 9, 10, and 11, respectively, but are not limited to these descriptions.
1. Services Tab Fig. 9 is a simplified diagram 900 of a representation of a graphical user interface for a services tab according to the present invention. In particular, the dialog box displays cumulative traffic statistics for selected applications. The services tab, which can be selected by default, provides the following information:
Service Name This field 919 shows what servicts (e.g., All Services, FTP, HTTP, SMTP, POP3, SSL) the network uses. Summary statistics for all services (e.g., inbound or outbound) are also shown. Traffic from services that are not recognized by the present tool are indicated as ' Others' .
Direction This field 919 indicates whether the service is inbound or outbound.
Note: Inbound and Outbound refer to the direction of data flow, not the request.
Kb Transferred SUBSTITUTE SHEET (RULE 26) WO 99/34544 PCr/US98/27396 This field 923 shows the amount of data transferred in inbound or outbound direction. As shown, the amount of data can be in kilobits transferred.
Additionally, the amount of data can be referred to as a percentage of all services.
Connect Response Time This field 925 indicates an average time to establish a session. The connect response time is in milliseconds, but is not limited to this time. The minimum and maximum connect response time is also shown in parenthesis.
Request Response Time This field 927 indicates an average response time for an application request.
The request response time is in milliseconds, but is not limited to this time.
The minimum and maximum request response time is also shown in parenthesis.
Note: This measure is application specific and does not apply to all services.
For example, for HTTP, it is the time taken by a URL to start sending data after a request for a file was made by a Web browser.
Total Sessions This field (not shown) indicates the total number of sessions established for this service.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the SUBSTITUTE SHEET (RULE 26) server.
Tune This field (not shown) indicates the last time the service was active.
2. Server Tab Fig. 10 is a simplified diagram 1000 of a representation of a graphical user interface for a server tab according to the present invention. Upon selecting or clicking the server tab 915, screen 1000 appears. The dialog box displays cumulative traffic statistics for every active server. The server tab provides the following information, but is not limited to such information:
Server This field 1001 shows the server host name, URL or IP address. Summary statistics for all servers are also shown.
Note:
= In one aspect of the invention, the present tool can profile up to 256 servers. Subsequent traffic from new servers are indicated as 'Others'.
= Host names can also be displayed in some embodiments.
Kb Transferred This field 1003 shows the amount of data transferred from the server. As shown, the amount of data can be in kilobits transferred. Additionally, the amount of data can be referred to as a percentage of all services.
Round Trip Time This field 1005 indicates an average round trip delay for packets sent to the server. The round trip time is in milliseconds, but is not limited to this time.
The minimum and maximum round trip time is also shown in parenthesis.
SUBSTITUTE SHEET (RULE 26) Connect Response Time This field 1007 indicates an average time to establish a session with the server.
The connect response time is in milliseconds, but is not limited to this time.
The minirnum and maximum connect response time is also shown in parenthesis.
Total Sessions This field 1009 indicates the total number of sessions established to the server.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the server.
Access Speed This field (not shown) indicates the bottleneck speed for the route between the present tool as a host and a server.
Data Retransmits This field (not shown) indicates the percentage of data packets that were retransmitted by the server.
Time This field (not shown) indicates the last time data was received from the server.
SUBSTITUTE SHEET (RULE 26) 3. Client Tab Fig. 11 is a simplified diagram 1100 of a representation of a graphical user interface for a client tab according to the present invention. When the client tab 917 is selected or is clicked using a user interface, screen 1100 appears. The dialog box displays the cumulative traffic statistics for the clients. The client tab provides the following information, but is not limited to such information:
CGent This field 1101 shows the client host name or IP address. Summary statistics for all clients are also shown.
Note: The present tool can profile up to 256 clients in some embodiments.
Subsequent traffic from the clients are indicated as ' Others' .
Kb Transferred This field 1103 shows the amount of data transferred to the client. As shown, the amount of data can be in kilobits transferred. Additionally, the amount of data can be referred to as a percentage of all services.
Round Trip Time This field 1105 indicates an average round trip delay for packets from this client. The round trip time is in milliseconds, but is not limited to this time.
The minimum and maximum round trip time is also shown in parenthesis.
Connect Response Time This field 1105 indicates the average time to establish a session from the client.
The connect response time is in milliseconds, but is not limited to this time.
The minimum and maximum connect response time is also shown in parenthesis.
SUBSTITUTE SHEET (RULE 26) Total Sessions This field 1109 indicates the total number of sessions established from the client.
Retries This field (not shown) indicates the percentage of connect requests that needed to be retried. Retries can result from network congestion, packets dropped in the network or server congestion.
Server Aborts This field (not shown) indicates the percentage of sessions aborted by the server.
Time This field (not shown) indicates the last time the client received data through the link used by the present tool.
The present invention provides the aforementioned tool for profiling a variety of information from a flow of information at a communication link. The tool has an easy to use graphical user interface, which can sort information by at least services, client, or server, depending upon the application. The illustrations shown are merely used as examples and should not limit the scope of the claims herein.
In a specific embodiment, the present invention with graphical user interface begins profiling upon installation. In particular, the present tool is installed onto a server to automatically start profiling traffic in inbound and outbound directions without any further configuration. The present tool can be stopped and restarted manually from a user interface.
While the present tool is stopped, profiling is interrupted temporarily.
The present invention provides additional easy to use graphical tools to monitor and profile traffic. In one aspect, the present invention takes advantage of a Windows NTTM
Performance Monitor to monitor traffic for any measurement or control rule that is created.
In another aspect, the present invention can launch the Performance Monitor from the SUBSTITUTE SHEET (RULE 26) 'Administrative Tools' Program group and select counters for monitoring incoming and outgoing traffic from a link.
Fig. 12 is a simplified graphical user interface 1200 to launch a performance monitoring tool according to the present invention. This interface is merely an illustration and should not limit the scope of the claims herein. A method for launching the present tool occurs, in part, by selecting or clicking on the performance monitor tab 1201.
The display shows available traffic classes 1201 (e.g., FTP, HTTP, PointCast), which have been defined in the traffic policy. Note that a traffic class is not a rule. There may be more than one rule that belongs to the same traffic class. Traffic classes are created when rules are edited. A
traffic class is defmed by at least a source, destination, and service properties. The display includes a group of option buttons 1207 titled monitor, which allows a user to specify whether the user wants to monitor bandwidth consumption 1209, connect time 1211, or connect retries 1213 for the selected classes. A prompt box 1215 above the option buttons 1207 provides a brief explanation of the selected option. A Launch button 1205 launches the performance monitor too. To launch the present performance monitor tool:
1. Select one or more traffic classes 1203 in the list.
2. Choose monitor by clicking on an appropriate option button (e. g. , bandwidth consumption, response time, failures) 1207 in the monitor group.
3. Push launch button 1205.
As merely an example, Fig. 13 is a simplified graphical user display 1300 for bandwidth consumption according to the present invention. As shown, the Fig.
is an example of Class Bandwidth 1305 monitoring for a few services 1307 such as FTP, HTTP, etc. over a 56 Kbit Internet link. The vertical axis 1302 illustrates a bandwidth scale from "0" to "56.0"
kbits and the horizontal axis represents time 1306. The plurality of line plots 1304 each represent one of the services 1307, which are each color coded 1301 for easy reading by the user. The display also includes an object 1309 and a computer 1311, which is being used to SUBSTITUTE SHEET (RULE 26) monitor the traffic. Accordingly, the present display includes a graphical portion 1310 and a text portion 1320. The graphical portion includes the plurality of plots representing the services for bandwidth consumption as functions of time. The text portion is in the form of a legend, but can also include other information.
The illustration in the above Fig. is merely an example and should not limit the scope of the claims. Although the present example has been described in terms of bandwidth consumption, the present performance monitor tool can also be used to monitor a variety of other parameters, as discussed above. These other parameters include, among others, connect time, or connect retries for the selected classes.
Furthermore, the present tool has other types of charts such as a bar chart, a pie chart, and the like. Of course, the parameter being profiled and monitored depends upon the application.
In an alternative embodiment, the present invention provides a user interface for modifying the plots or charts, such as the one previously described, as well as others.
Fig. 14 is a simplified interface tool 1400 used to modify chart styles, scales, charting intervals etc. This tool is merely an example and should not limit the scope of the claims herein. The present tool has an "OK" button for saving or storing selected chart options. A
"cancel" button 1403 is also shown to delete or remove selected chart options.
A help button 1405 is shown to identify features of any of the chart options. Numerous chart options 1407 exist. For example, opiions include, among others, a legend, a value bar, a vertical grid, a horizontal grid, and vertical labels. To select any one of these options, the user clicks onto the box located next to the option or enters the underlined key designating the option. Chart options also include a gallery 1409, either in graph or histogram form.
Additionally, the chart can have a maximum vertical scale 1411 such as the 56 for 56 kbits/second.
Furthermore, the chart can have a refreshing or updating cycle time 1413. In one aspect, the cycle time can be manually updated. Alternatively, the cycle time can be periodically updated. When using the periodically updating feature, a time interval (e.g., seconds) needs to be specified and entered into a field, as shown.
Fig. 15 is a simplified graphical user interface 1500 for adding or specifying an additional chart according to the present invention. This interface or tool is merely an example and should not limit the scope of the claims herein. This interface allows the user to select the parameters to be monitored on the chart. These parameters include, among others, SUBSTITUTE SHEET (RULE 26) the computer to be monitored 1507, the object 1509, the counter 1511, and the instance 1514.
Depending on the types of parameters being monitored or profiled, specific visual details of the plots or charts are also selected. These details include the plot color 1513, the plot width 1519, the plot style 1517, and others. A counter definition 1515 is also made or selected.
Once all the changes have been made or selected, the user can add the changes to be monitored by the tool by pressing or selecting the add button 1501.
Alternatively, the user may start over by selecting the cancel button 1503. If the user would like an explanation on any one of the features described in the tool, the user may selected either the explain button 1505 or the help button 1506. Of course, this user interface is merely an example and should not be limiting any manner outside the spirit and scope of the claims.
In yet an alternative aspect, the present monitoring or profiling tool has a save feature for storing the chart or plot. In particular, the present tool can save snapshots of measurements to a disk file or the like. As merely an example, the present tool saves snapshots using the following sequence of steps, which should not be construed as limiting:
Go to view/log in the tool to configure a log file;
Add measurements to the file and start and/or stop logging.
Furthermore, the present tool provides congestion, utilization, and performance degradation reports, which make day to day troubleshooting much simpler and serve to justify or validate policy setting decisions. For example, a chronic problem affecting a service through a day period (i.e., 24 hour) can be monitored by a combination of real-time monitoring, which will be described in more detail below, and congestion reports. By monitoring and using the reports, it may be determined that the affected service is not getting its due share of bandwidth, or a limitation exists with the server or in the Internet backbone.
Conclusion In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. Many changes or modifications are readily envisioned. For example, the present invention can be applied to manage a variety of TCP/IP network traffic types for the Internet and Intranet. Further, the techniques SUBSTITUTE SHEET (RULE 26) can also be applied to Novell SPX, Xerox XNS or any protocol with a similar 'flow-control' design that utilizes windows and acknowledgment signals (similar to ACK).
Alternative embodiments of the present invention can also be applied to a 'legacy' private WAN running IP as well as native Novell protocols if there is a need.
(e.g., file server and client/server traffic). Further, embodiments of the present invention can include monitoring, billing, and reporting features, thus allowing for enhanced client billing and internal cost accounting of network usage.
These techniques are preferably implemented within a firewall platform to solve the provide the following benefits: bidirectional bandwidth management of network links carrying TCP traffic; reactive (short-time scale) and proactive (long time scale) control mechanisms; and gateway (local) and end-end (global) techniques for bandwidth control.
This solution reduces their contribution to congestion in the Internet; and operation in a present day heterogeneous wide area networks, such as the Internet, without requiring any client, server or router changes.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.
SUBSTITUTE SHEET (RULE 26)
Claims (52)
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A computer system coupled to a network of computers, said computer system for monitoring and managing a plurality of flows of information, said computer system comprising:
a graphical user interface component that generates a display, said display comprising at least a first portion and a second portion, said first portion comprising a graphical chart representing said flows of information, said second portion comprising text information describing each of said flows of information;
an application programming interface (API) component coupled to said graphical user interface component; and a traffic control and management component, coupled to said application programming interface component, that controls an amount of bandwidth allocated to said plurality of flows of information, said traffic control and management component comprising:
a first application, coupled to said API component, that classifies said plurality of flows of information into parameters and measures said parameters;
a second application, coupled to said API
component, that controls said plurality of flows of information into and out of the network of computers and allocates said bandwidth allocated to said plurality of flows of information; and a third application, coupled to said API component, that applies a traffic policy associated with one or more traffic rules in said first and second applications, and wherein the one or more traffic rules can be manually edited or created.
a graphical user interface component that generates a display, said display comprising at least a first portion and a second portion, said first portion comprising a graphical chart representing said flows of information, said second portion comprising text information describing each of said flows of information;
an application programming interface (API) component coupled to said graphical user interface component; and a traffic control and management component, coupled to said application programming interface component, that controls an amount of bandwidth allocated to said plurality of flows of information, said traffic control and management component comprising:
a first application, coupled to said API component, that classifies said plurality of flows of information into parameters and measures said parameters;
a second application, coupled to said API
component, that controls said plurality of flows of information into and out of the network of computers and allocates said bandwidth allocated to said plurality of flows of information; and a third application, coupled to said API component, that applies a traffic policy associated with one or more traffic rules in said first and second applications, and wherein the one or more traffic rules can be manually edited or created.
2. The computer system of claim 1 wherein said graphical chart representing said flows of information is a plot of bandwidth consumed against time.
3. The computer system of claim 1 wherein said graphical chart representing said flows of information is a plurality of plots, each of said plots representing consumed bandwidth against time.
4. The computer of claim 1 wherein each of said flows of information comprises one of a plurality of traffic classes.
5. The computer of claim 4 wherein said plurality of traffic classes comprise HTTP, FTP and SMTP.
6. The computer system of claim 1 wherein said graphical chart comprises a plot of failure rates against time.
7. The computer system of claim 1 wherein said graphical chart comprises a plot of delay rates against time.
8. The computer system of claim 1 wherein said display is outputted on a computer monitor.
9. The computer system of claim 1 wherein said display is a real-time display of a portion of said plurality of flows of information.
10. The computer system of claim 1 wherein said graphical chart is selected from a graph, a histogram, a bar chart, and a pie chart.
11. The computer of claim 1 wherein said graphical chart comprises a plot of bandwidth consumption.
12. A computer system connected to a network of computers, said computer system for monitoring and managing in real time a plurality of flows of information, each of said plurality of flows of information being of one of a plurality of traffic classes, said computer system comprising:
a graphical user interface component that generates a display on a monitor, said display comprising at least a first portion and a second portion, said first portion comprising a graphical chart representing said traffic classes and said second portion comprising text information describing each of said traffic classes, wherein said graphical chart comprises a bandwidth consumption plot for each of said traffic classes; and a traffic control and management component, coupled to said graphical user interface component, said traffic control and management component comprising:
a first module that monitors said plurality of flows of information to and from said network of computers by classifying information into a first set of parameters and measuring said first set of parameters;
a second module that implements traffic control and manages bandwidth allocation by controlling said plurality of flows of information to and from said network of computers using a second set of parameters and allocating bandwidth based in part on said second set of parameters;
and a third module that applies a traffic policy associated with one or more traffic rules in said first and second modules, and wherein the one or more traffic rules can be edited or created.
a graphical user interface component that generates a display on a monitor, said display comprising at least a first portion and a second portion, said first portion comprising a graphical chart representing said traffic classes and said second portion comprising text information describing each of said traffic classes, wherein said graphical chart comprises a bandwidth consumption plot for each of said traffic classes; and a traffic control and management component, coupled to said graphical user interface component, said traffic control and management component comprising:
a first module that monitors said plurality of flows of information to and from said network of computers by classifying information into a first set of parameters and measuring said first set of parameters;
a second module that implements traffic control and manages bandwidth allocation by controlling said plurality of flows of information to and from said network of computers using a second set of parameters and allocating bandwidth based in part on said second set of parameters;
and a third module that applies a traffic policy associated with one or more traffic rules in said first and second modules, and wherein the one or more traffic rules can be edited or created.
13. The computer system of claim 12 wherein said bandwidth consumption is a plot of bandwidth consumed against time.
14. The computer system of claim 12 wherein said bandwidth consumption is a plurality of plots, each of said plots representing consumed bandwidth against time for each of said traffic classes.
15. The computer system of claim 12 wherein said plurality of traffic classes comprise FTP, HTTP, and SMTP.
16. The computer system of claim 12 wherein said graphical chart further comprises a plot of failure rates against time or a plot of delay rates against time.
17. The computer system of claim 12 wherein said graphical chart is selected from a graph, a histogram, a bar chart, and a pie chart.
18. A method in a computer system for managing and monitoring a plurality of flows of information, said method comprising the steps of:
allocating bandwidth to a plurality of flows of information between one or more sources coupled to a network of computers;
measuring a data rate for each of said flows of information, each of said flows of information being of one of a plurality traffic classes;
applying a traffic policy associated with one or more traffic rules for each one of said flows of information, wherein the one or more traffic rules can be edited or created;
categorizing each one of said flows of information into one of said plurality of traffic classes;
measuring a parameter for said each one of said flows of information associated with said one of said plurality of traffic classes;
applying a time stamp to said parameter to correlate said one of said plurality of traffic classes with a time;
determining a data rate for each one of said plurality of traffic classes;
outputting a visual representation of the data rate of at least one of said plurality of traffic classes in graphical form on a display; and outputting a text representation of said at least one of said plurality of traffic classes on said display.
allocating bandwidth to a plurality of flows of information between one or more sources coupled to a network of computers;
measuring a data rate for each of said flows of information, each of said flows of information being of one of a plurality traffic classes;
applying a traffic policy associated with one or more traffic rules for each one of said flows of information, wherein the one or more traffic rules can be edited or created;
categorizing each one of said flows of information into one of said plurality of traffic classes;
measuring a parameter for said each one of said flows of information associated with said one of said plurality of traffic classes;
applying a time stamp to said parameter to correlate said one of said plurality of traffic classes with a time;
determining a data rate for each one of said plurality of traffic classes;
outputting a visual representation of the data rate of at least one of said plurality of traffic classes in graphical form on a display; and outputting a text representation of said at least one of said plurality of traffic classes on said display.
19. The method of claim 18 wherein said data rate is a baud rate.
20. The method of claim 18 wherein said visual representation is a real time histogram of said data rate.
21. The method of claim 18 wherein said plurality of traffic classes comprise HTTP, FTP, and SMTP.
22. A computer system comprising a bandwidth profiling and management tool for monitoring and managing a plurality of flows of information between one or more sources coupled to a network of computers, each of said plurality of flows of information comprising one of a plurality of traffic classes, said bandwidth profiling and management tool being stored in computer memory, said computer memory comprising:
a first code that is directed to allocating bandwidth to said plurality of flows of information;
a second code that is directed to measuring a data rate for each one of said flows of information;
a third code that is directed to categorizing each of said plurality of flows of information into one of a plurality of traffic classes;
a fourth code that is directed to measuring a parameter for each of said flows of information associated with said one of said plurality of traffic classes;
a fifth code that is directed to applying a time stamp to said parameter to correlate said one of said plurality of traffic classes with a time;
a sixth code that is directed to determining a data rate for each one of said plurality of traffic classes;
a seventh code that is directed to outputting a visual representation of said data rate of at least one of said plurality of traffic classes in graphical form on a display; and an eighth code that is directed to outputting a text representation of said at least one of said plurality of traffic classes on said display; and a ninth code that is directed to applying a traffic policy associated with one or more traffic rules for each of said flows of information, wherein the one or more traffic rules can be edited or created.
a first code that is directed to allocating bandwidth to said plurality of flows of information;
a second code that is directed to measuring a data rate for each one of said flows of information;
a third code that is directed to categorizing each of said plurality of flows of information into one of a plurality of traffic classes;
a fourth code that is directed to measuring a parameter for each of said flows of information associated with said one of said plurality of traffic classes;
a fifth code that is directed to applying a time stamp to said parameter to correlate said one of said plurality of traffic classes with a time;
a sixth code that is directed to determining a data rate for each one of said plurality of traffic classes;
a seventh code that is directed to outputting a visual representation of said data rate of at least one of said plurality of traffic classes in graphical form on a display; and an eighth code that is directed to outputting a text representation of said at least one of said plurality of traffic classes on said display; and a ninth code that is directed to applying a traffic policy associated with one or more traffic rules for each of said flows of information, wherein the one or more traffic rules can be edited or created.
23. A method of operating a computer, comprising:
connecting said computer to a wide area network;
connecting said computer to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
controlling an amount of bandwidth allocated to said flows of information, by said computer based on one or more traffic rules that can be edited or created; and generating a display by said computer, said display having a chart representing said flows of information passing through said computer, and representing said amount of bandwidth allocated to said flows.
connecting said computer to a wide area network;
connecting said computer to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
controlling an amount of bandwidth allocated to said flows of information, by said computer based on one or more traffic rules that can be edited or created; and generating a display by said computer, said display having a chart representing said flows of information passing through said computer, and representing said amount of bandwidth allocated to said flows.
24. A computer-readable medium comprising: instructions and data written thereon, said instructions and data containing information for the practice of the method of claim 23.
25. A computer comprising:
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
software executing on said computer, said software having:
a graphical user interface component that generates a display, said display having a chart representing said flows of information passing through said computer, and a traffic control and management component that controls and applies an amount of bandwidth allocated to said flows of information, and wherein the traffic control and management component is based on one or more traffic rules that can be edited or created.
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
software executing on said computer, said software having:
a graphical user interface component that generates a display, said display having a chart representing said flows of information passing through said computer, and a traffic control and management component that controls and applies an amount of bandwidth allocated to said flows of information, and wherein the traffic control and management component is based on one or more traffic rules that can be edited or created.
26. The computer of claim 25 wherein said software has a component that classifies said plurality of flows of information into parameters, and measures said parameters.
27. The computer of claim 25 wherein said software has a component that allocates bandwidth to said plurality of flows as they pass between said wide area network and said local area network.
28. The computer of claim 25 wherein said software has a component that enforces a traffic policy by allocating bandwidth to said plurality of flows.
29. The computer of claim 25 wherein said software has an application programming interface (API) component coupled to said graphical user interface and to other components of said software.
30. The computer of claim 25 wherein said graphical user interface displays text as well as said chart.
31. A communication network comprising at least one computer as claimed in claim 25.
32. A computer comprising:
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
means for controlling and applying an amount of bandwidth allocated to said flows of information, said means effectuated by said computer, and wherein the means for controlling and applying is based on one or more traffic rules that can be edited or created; and means for generating a display by said computer, said display having a chart representing said flows of information passing through said computer, and representing said amount of bandwidth allocated to each of said flows.
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
means for controlling and applying an amount of bandwidth allocated to said flows of information, said means effectuated by said computer, and wherein the means for controlling and applying is based on one or more traffic rules that can be edited or created; and means for generating a display by said computer, said display having a chart representing said flows of information passing through said computer, and representing said amount of bandwidth allocated to each of said flows.
33. A computer comprising:
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
software executing on said computer, said software having a traffic-monitoring and management component to control an amount of bandwidth allocated to said flows of information, wherein the traffic-monitoring and management component uses one or more traffic rules that can be edited or created; and a graphical user interface component of said software that generates a display, said display having a chart representing said flows of information passing through said computer.
a first connection to a wide area network;
a second connection to a local area network, said computer serving as a firewall computer for a plurality of flows of information passing between said wide area network and said local area network;
software executing on said computer, said software having a traffic-monitoring and management component to control an amount of bandwidth allocated to said flows of information, wherein the traffic-monitoring and management component uses one or more traffic rules that can be edited or created; and a graphical user interface component of said software that generates a display, said display having a chart representing said flows of information passing through said computer.
34. The computer of claim 33 wherein said graphical user interface displays text as well as said chart.
35. The computer of claim 33 wherein said software comprises a component that classifies said plurality of flows of information into parameters, and measures said parameters.
36. The computer of claim 33 wherein said software comprises a component that allocates bandwidth to said plurality of flows as they pass between said wide area network and said local area network.
37. The computer of claim 33 wherein said software comprises a component that effectuates a traffic policy by allocating bandwidth to said plurality of flows.
38. The computer of claim 33 wherein said software comprises an application programming interface (API) component coupled to a graphical user interface and to other components of said software.
39. An apparatus to control traffic flow into a first network of computers from a second network of computers, comprising:
a computer receiving traffic directed to said first network from said second network;
a first application, in response to receiving a packet from said second network for forwarding into said first network, to classify said packet as belonging to a flow, and to measure a current bandwidth used by said flow, referred to as a measured flow bandwidth;
a second application, in response to said measured flow bandwidth, to determine a difference between said measured flow bandwidth and an allocated value of bandwidth for said flow;
a third application, in response to said difference, to manage and apply bandwidth allocation to said flow based on one or more traffic rules that can be edited or created;
and a graphical user interface to permit a person to monitor activity of said computer.
a computer receiving traffic directed to said first network from said second network;
a first application, in response to receiving a packet from said second network for forwarding into said first network, to classify said packet as belonging to a flow, and to measure a current bandwidth used by said flow, referred to as a measured flow bandwidth;
a second application, in response to said measured flow bandwidth, to determine a difference between said measured flow bandwidth and an allocated value of bandwidth for said flow;
a third application, in response to said difference, to manage and apply bandwidth allocation to said flow based on one or more traffic rules that can be edited or created;
and a graphical user interface to permit a person to monitor activity of said computer.
40. The apparatus as in claim 39, further comprising:
a process for managing bandwidth of said flow in response to a type of flow.
a process for managing bandwidth of said flow in response to a type of flow.
41. The apparatus as in claim 39, further comprising:
a process for applying an admissions policy to said flow.
a process for applying an admissions policy to said flow.
42. The apparatus as in claim 39, further comprising:
means for increasing allocated bandwidth if said flow has a high priority.
means for increasing allocated bandwidth if said flow has a high priority.
43. The apparatus as in claim 39, further comprising:
means for decreasing allocated bandwidth if said flow has a low priority.
means for decreasing allocated bandwidth if said flow has a low priority.
44. The apparatus as in claim 39, wherein said first network is a local network and said second network is a remote network.
45. The apparatus as in claim 39, wherein said first network is a remote network and said second network is a local network.
46. The apparatus as in claim 39, wherein:
said graphical user interface further permits a person to control operation of said computer.
said graphical user interface further permits a person to control operation of said computer.
47. A method for controlling traffic flow into a first network of computers from a second network of computers, comprising:
receiving, by a computer, a packet directed to said first network from said second network, said packet addressed for forwarding into said first network;
classifying, in response to receiving said packet, said packet as belonging to a flow, and to measure a current bandwidth used by said flow, referred to as a measured flow bandwidth;
providing a second application responsive to said measured flow bandwidth, to determine a difference between said measured flow bandwidth and an allocated value of bandwidth for said flow;
providing a third application responsive to said difference, to manage and apply bandwidth allocation to said flow based on one or more traffic rules that can be edited or created;
and displaying on a graphical user interface data for monitoring operation of said computer.
receiving, by a computer, a packet directed to said first network from said second network, said packet addressed for forwarding into said first network;
classifying, in response to receiving said packet, said packet as belonging to a flow, and to measure a current bandwidth used by said flow, referred to as a measured flow bandwidth;
providing a second application responsive to said measured flow bandwidth, to determine a difference between said measured flow bandwidth and an allocated value of bandwidth for said flow;
providing a third application responsive to said difference, to manage and apply bandwidth allocation to said flow based on one or more traffic rules that can be edited or created;
and displaying on a graphical user interface data for monitoring operation of said computer.
48. The method as in claim 47, further comprising:
adjusting said bandwidth allocation so that said allocation depends upon a type of said flow.
adjusting said bandwidth allocation so that said allocation depends upon a type of said flow.
49. The method as in claim 47, further comprising:
applying an admissions policy to incoming flows by adjustment of allocated bandwidth.
applying an admissions policy to incoming flows by adjustment of allocated bandwidth.
50. The method as in claim 47, further comprising:
increasing allocated bandwidth if said flow has a high priority.
increasing allocated bandwidth if said flow has a high priority.
51. The method as in claim 47, further comprising:
reducing allocated bandwidth if said flow has a low priority.
reducing allocated bandwidth if said flow has a low priority.
52. The method as in claim 47, further comprising:
controlling operation of said computer by use of said graphical user interface.
controlling operation of said computer by use of said graphical user interface.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/999,517 | 1997-12-29 | ||
US08/999,517 US6578077B1 (en) | 1997-05-27 | 1997-12-29 | Traffic monitoring tool for bandwidth management |
PCT/US1998/027396 WO1999034544A1 (en) | 1997-12-29 | 1998-12-23 | Traffic monitoring tool for bandwidth management |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2316355A1 CA2316355A1 (en) | 1999-07-08 |
CA2316355C true CA2316355C (en) | 2008-12-02 |
Family
ID=25546441
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002316355A Expired - Lifetime CA2316355C (en) | 1997-12-29 | 1998-12-23 | Traffic monitoring tool for bandwidth management |
Country Status (6)
Country | Link |
---|---|
US (2) | US6578077B1 (en) |
EP (1) | EP1050128A4 (en) |
JP (1) | JP2002500469A (en) |
AU (1) | AU2307699A (en) |
CA (1) | CA2316355C (en) |
WO (1) | WO1999034544A1 (en) |
Families Citing this family (712)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6473793B1 (en) * | 1994-06-08 | 2002-10-29 | Hughes Electronics Corporation | Method and apparatus for selectively allocating and enforcing bandwidth usage requirements on network users |
US5867153A (en) | 1996-10-30 | 1999-02-02 | Transaction Technology, Inc. | Method and system for automatically harmonizing access to a software application program via different access devices |
US7249344B1 (en) | 1996-10-31 | 2007-07-24 | Citicorp Development Center, Inc. | Delivery of financial services to remote devices |
US8112330B1 (en) | 1997-08-07 | 2012-02-07 | Citibank Development Center, Inc. | System and method for delivering financial services |
US7668781B2 (en) | 1996-10-31 | 2010-02-23 | Citicorp Development Center, Inc. | Global method and system for providing enhanced transactional functionality through a customer terminal |
US7821926B2 (en) | 1997-03-10 | 2010-10-26 | Sonicwall, Inc. | Generalized policy server |
US7580919B1 (en) | 1997-03-10 | 2009-08-25 | Sonicwall, Inc. | Query interface to policy server |
US7272625B1 (en) * | 1997-03-10 | 2007-09-18 | Sonicwall, Inc. | Generalized policy server |
US8914410B2 (en) | 1999-02-16 | 2014-12-16 | Sonicwall, Inc. | Query interface to policy server |
US6408336B1 (en) | 1997-03-10 | 2002-06-18 | David S. Schneider | Distributed administration of access to information |
ATE367701T1 (en) | 1997-03-12 | 2007-08-15 | Nomadix Inc | NOMADIC TRANSLATOR OR PATH FINDER |
US5898801A (en) | 1998-01-29 | 1999-04-27 | Lockheed Martin Corporation | Optical transport system |
US6968379B2 (en) * | 1997-05-30 | 2005-11-22 | Sun Microsystems, Inc. | Latency-reducing bandwidth-prioritization for network servers and clients |
US6760746B1 (en) | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US7283561B1 (en) * | 1997-12-12 | 2007-10-16 | Level 3 Communications, Llc | Secure network architecture with quality of service |
US8631093B2 (en) | 1998-03-19 | 2014-01-14 | Crane Merchandising Systems, Inc. | Remote data acquisition, transmission and analysis system including handheld wireless equipment |
US6330598B1 (en) * | 1998-06-23 | 2001-12-11 | Ameritech Corporation | Global service management system for an advanced intelligent network |
US6735701B1 (en) * | 1998-06-25 | 2004-05-11 | Macarthur Investments, Llc | Network policy management and effectiveness system |
SG141212A1 (en) * | 1998-11-24 | 2008-04-28 | Niksun Inc | Apparatus and method for collecting and analyzing communications data |
US8713641B1 (en) | 1998-12-08 | 2014-04-29 | Nomadix, Inc. | Systems and methods for authorizing, authenticating and accounting users having transparent computer access to a network using a gateway device |
US7194554B1 (en) * | 1998-12-08 | 2007-03-20 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization authentication and accounting |
US8266266B2 (en) | 1998-12-08 | 2012-09-11 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization, authentication and accounting |
US6917617B2 (en) * | 1998-12-16 | 2005-07-12 | Cisco Technology, Inc. | Use of precedence bits for quality of service |
US6542508B1 (en) * | 1998-12-17 | 2003-04-01 | Watchguard Technologies, Inc. | Policy engine using stream classifier and policy binding database to associate data packet with appropriate action processor for processing without involvement of a host processor |
US6779282B2 (en) * | 1998-12-23 | 2004-08-24 | Groehninger Frank Friedrich | Insole |
JP3486125B2 (en) * | 1999-01-14 | 2004-01-13 | 富士通株式会社 | Network device control system and device |
US6789118B1 (en) * | 1999-02-23 | 2004-09-07 | Alcatel | Multi-service network switch with policy based routing |
US7076476B2 (en) * | 1999-03-02 | 2006-07-11 | Microsoft Corporation | Method and system for integrated service administration via a directory service |
US6711137B1 (en) * | 1999-03-12 | 2004-03-23 | International Business Machines Corporation | System and method for analyzing and tuning a communications network |
US7174452B2 (en) * | 2001-01-24 | 2007-02-06 | Broadcom Corporation | Method for processing multiple security policies applied to a data packet structure |
US9141717B2 (en) | 1999-03-22 | 2015-09-22 | Esdr Network Solutions Llc | Methods, systems, products, and devices for processing DNS friendly identifiers |
US7188138B1 (en) | 1999-03-22 | 2007-03-06 | Eric Schneider | Method, product, and apparatus for resource identifier registration and aftermarket services |
US8037168B2 (en) * | 1999-07-15 | 2011-10-11 | Esdr Network Solutions Llc | Method, product, and apparatus for enhancing resolution services, registration services, and search services |
USRE43690E1 (en) | 1999-03-22 | 2012-09-25 | Esdr Network Solutions Llc | Search engine request method, product, and apparatus |
US6338082B1 (en) | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
US6687750B1 (en) * | 1999-04-14 | 2004-02-03 | Cisco Technology, Inc. | Network traffic visualization |
US6804714B1 (en) * | 1999-04-16 | 2004-10-12 | Oracle International Corporation | Multidimensional repositories for problem discovery and capacity planning of database applications |
US6704284B1 (en) * | 1999-05-10 | 2004-03-09 | 3Com Corporation | Management system and method for monitoring stress in a network |
US7275113B1 (en) * | 1999-05-27 | 2007-09-25 | 3 Com Corporation | Dynamic network address configuration system and method |
US7127506B1 (en) | 1999-05-28 | 2006-10-24 | Teradyne, Inc. | PC configuration fault analysis |
US7032022B1 (en) * | 1999-06-10 | 2006-04-18 | Alcatel | Statistics aggregation for policy-based network |
US6944183B1 (en) | 1999-06-10 | 2005-09-13 | Alcatel | Object model for network policy management |
US7010801B1 (en) | 1999-06-11 | 2006-03-07 | Scientific-Atlanta, Inc. | Video on demand system with parameter-controlled bandwidth deallocation |
US7992163B1 (en) | 1999-06-11 | 2011-08-02 | Jerding Dean F | Video-on-demand navigational system |
US6817028B1 (en) | 1999-06-11 | 2004-11-09 | Scientific-Atlanta, Inc. | Reduced screen control system for interactive program guide |
US6751191B1 (en) | 1999-06-29 | 2004-06-15 | Cisco Technology, Inc. | Load sharing and redundancy scheme |
US6959006B1 (en) * | 1999-06-29 | 2005-10-25 | Adc Telecommunications, Inc. | Service delivery unit for an enterprise network |
US6681243B1 (en) * | 1999-07-27 | 2004-01-20 | Intel Corporation | Network environment supporting mobile agents with permissioned access to resources |
USRE44207E1 (en) | 1999-09-01 | 2013-05-07 | Esdr Network Solutions Llc | Network resource access method, product, and apparatus |
US6832341B1 (en) * | 1999-09-23 | 2004-12-14 | International Business Machines Corporation | Fault event management using fault monitoring points |
US6674760B1 (en) * | 1999-09-28 | 2004-01-06 | Extreme Networks, Inc. | Method and system for implementing end-to-end QoS in packet-switched networks |
US6801939B1 (en) * | 1999-10-08 | 2004-10-05 | Board Of Trustees Of The Leland Stanford Junior University | Method for evaluating quality of service of a digital network connection |
US6788646B1 (en) | 1999-10-14 | 2004-09-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Link capacity sharing for throughput-blocking optimality |
US7213068B1 (en) * | 1999-11-12 | 2007-05-01 | Lucent Technologies Inc. | Policy management system |
US6901051B1 (en) * | 1999-11-15 | 2005-05-31 | Fujitsu Limited | Server-based network performance metrics generation system and method |
US6668275B1 (en) * | 1999-12-17 | 2003-12-23 | Honeywell International Inc. | System and method for multiprocessor management |
US6779120B1 (en) * | 2000-01-07 | 2004-08-17 | Securify, Inc. | Declarative language for specifying a security policy |
US6684244B1 (en) * | 2000-01-07 | 2004-01-27 | Hewlett-Packard Development Company, Lp. | Aggregated policy deployment and status propagation in network management systems |
US8074256B2 (en) * | 2000-01-07 | 2011-12-06 | Mcafee, Inc. | Pdstudio design system and method |
US7587041B2 (en) | 2000-01-13 | 2009-09-08 | Verint Americas Inc. | System and method for analysing communications streams |
GB0000735D0 (en) | 2000-01-13 | 2000-03-08 | Eyretel Ltd | System and method for analysing communication streams |
US6839766B1 (en) * | 2000-01-14 | 2005-01-04 | Cisco Technology, Inc. | Method and apparatus for communicating cops protocol policies to non-cops-enabled network devices |
EP1117265A1 (en) * | 2000-01-15 | 2001-07-18 | Telefonaktiebolaget Lm Ericsson | Method and apparatus for global roaming |
US7058007B1 (en) | 2000-01-18 | 2006-06-06 | Cisco Technology, Inc. | Method for a cable modem to rapidly switch to a backup CMTS |
US6839829B1 (en) | 2000-01-18 | 2005-01-04 | Cisco Technology, Inc. | Routing protocol based redundancy design for shared-access networks |
JP2001203691A (en) * | 2000-01-19 | 2001-07-27 | Nec Corp | Network traffic monitor system and monitor method to be used for it |
US6823479B1 (en) | 2000-02-14 | 2004-11-23 | Teradyne, Inc. | Network fault analysis tool |
JP2001237886A (en) * | 2000-02-18 | 2001-08-31 | Sony Corp | Data transmission system and method, data transmission management system and method |
US6842783B1 (en) * | 2000-02-18 | 2005-01-11 | International Business Machines Corporation | System and method for enforcing communications bandwidth based service level agreements to plurality of customers hosted on a clustered web server |
US20010055274A1 (en) * | 2000-02-22 | 2001-12-27 | Doug Hegge | System and method for flow mirroring in a network switch |
US6983317B1 (en) | 2000-02-28 | 2006-01-03 | Microsoft Corporation | Enterprise management system |
US7260635B2 (en) * | 2000-03-21 | 2007-08-21 | Centrisoft Corporation | Software, systems and methods for managing a distributed network |
US6671724B1 (en) * | 2000-03-21 | 2003-12-30 | Centrisoft Corporation | Software, systems and methods for managing a distributed network |
US7975277B1 (en) | 2000-04-03 | 2011-07-05 | Jerding Dean F | System for providing alternative services |
US7200857B1 (en) | 2000-06-09 | 2007-04-03 | Scientific-Atlanta, Inc. | Synchronized video-on-demand supplemental commentary |
US8516525B1 (en) | 2000-06-09 | 2013-08-20 | Dean F. Jerding | Integrated searching system for interactive media guide |
US6857025B1 (en) * | 2000-04-05 | 2005-02-15 | International Business Machines Corporation | Highly scalable system and method of regulating internet traffic to server farm to support (min,max) bandwidth usage-based service level agreements |
US6865150B1 (en) * | 2000-04-06 | 2005-03-08 | Cisco Technology, Inc. | System and method for controlling admission of voice communications in a packet network |
US7277384B1 (en) | 2000-04-06 | 2007-10-02 | Cisco Technology, Inc. | Program and method for preventing overload in a packet telephony gateway |
US20050091378A1 (en) * | 2000-04-10 | 2005-04-28 | Jorg Nonnenmacher | Method and system for using mobile code to measure quality of service over a network |
US6941551B1 (en) * | 2000-04-11 | 2005-09-06 | Microsoft Corporation | Method and system for creating a quality of service message |
US7013394B1 (en) * | 2000-04-18 | 2006-03-14 | International Business Machines Corporation | Data flow pattern recognition and manipulation |
JP2001309036A (en) * | 2000-04-20 | 2001-11-02 | Fujitsu Ltd | Communication equipment and congestion regulation control method |
US6591298B1 (en) * | 2000-04-24 | 2003-07-08 | Keynote Systems, Inc. | Method and system for scheduling measurement of site performance over the internet |
US6904458B1 (en) * | 2000-04-26 | 2005-06-07 | Microsoft Corporation | System and method for remote management |
US6654804B1 (en) * | 2000-04-27 | 2003-11-25 | Micron Electronics, Inc. | Method and apparatus for automatic dial-up dial-down web hosting |
US7054943B1 (en) * | 2000-04-28 | 2006-05-30 | International Business Machines Corporation | Method and apparatus for dynamically adjusting resources assigned to plurality of customers, for meeting service level agreements (slas) with minimal resources, and allowing common pools of resources to be used across plural customers on a demand basis |
US6775699B1 (en) * | 2000-04-28 | 2004-08-10 | Microsoft Corporation | System and method for implementing integrated polling functions in a client management tool |
US7523180B1 (en) * | 2000-04-28 | 2009-04-21 | Microsoft Corporation | System and method for service chain management in a client management tool |
US7934232B1 (en) | 2000-05-04 | 2011-04-26 | Jerding Dean F | Navigation paradigm for access to television services |
US6742044B1 (en) * | 2000-05-10 | 2004-05-25 | Cisco Technology, Inc. | Distributed network traffic load balancing technique implemented without gateway router |
US6941371B2 (en) * | 2000-05-18 | 2005-09-06 | International Business Machines Corporation | System and method for enabling graphic applications in an interactive programming model |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7251688B2 (en) * | 2000-05-26 | 2007-07-31 | Akamai Technologies, Inc. | Method for generating a network map |
US7010594B2 (en) * | 2000-05-26 | 2006-03-07 | Isochron, Llc | System using environmental sensor and intelligent management and control transceiver for monitoring and controlling remote computing resources |
US6584504B1 (en) * | 2000-05-26 | 2003-06-24 | Networks Associates Technology, Inc. | Method and apparatus for monitoring internet traffic on an internet web page |
US7096263B2 (en) * | 2000-05-26 | 2006-08-22 | Akamai Technologies, Inc. | Method for predicting file download time from mirrored data centers in a global computer network |
JP4690628B2 (en) * | 2000-05-26 | 2011-06-01 | アカマイ テクノロジーズ インコーポレイテッド | How to determine which mirror site should receive end-user content requests |
US6963575B1 (en) | 2000-06-07 | 2005-11-08 | Yipes Enterprise Services, Inc. | Enhanced data switching/routing for multi-regional IP over fiber network |
US7418489B2 (en) | 2000-06-07 | 2008-08-26 | Microsoft Corporation | Method and apparatus for applying policies |
US7444395B2 (en) * | 2000-06-07 | 2008-10-28 | Microsoft Corporation | Method and apparatus for event handling in an enterprise |
US8069259B2 (en) | 2000-06-09 | 2011-11-29 | Rodriguez Arturo A | Managing removal of media titles from a list |
US6754843B1 (en) * | 2000-06-13 | 2004-06-22 | At&T Corp. | IP backbone network reliability and performance analysis method and apparatus |
US20020093527A1 (en) * | 2000-06-16 | 2002-07-18 | Sherlock Kieran G. | User interface for a security policy system and method |
US20030061506A1 (en) * | 2001-04-05 | 2003-03-27 | Geoffrey Cooper | System and method for security policy |
US7917647B2 (en) | 2000-06-16 | 2011-03-29 | Mcafee, Inc. | Method and apparatus for rate limiting |
US6975594B1 (en) * | 2000-06-27 | 2005-12-13 | Lucent Technologies Inc. | System and method for providing controlled broadband access bandwidth |
US7962370B2 (en) | 2000-06-29 | 2011-06-14 | Rodriguez Arturo A | Methods in a media service system for transaction processing |
US6763372B1 (en) * | 2000-07-06 | 2004-07-13 | Nishant V. Dani | Load balancing of chat servers based on gradients |
US7111163B1 (en) | 2000-07-10 | 2006-09-19 | Alterwan, Inc. | Wide area network using internet with quality of service |
US20020059418A1 (en) * | 2000-07-17 | 2002-05-16 | Alan Bird | Method of and system for recording and displaying electronic mail statistics |
US7467193B2 (en) * | 2000-08-01 | 2008-12-16 | Qwest Communications International Inc | Management of virtual and physical network inventories |
US7058707B1 (en) | 2000-08-01 | 2006-06-06 | Qwest Communications International, Inc. | Performance modeling in a VDSL network |
US6996132B1 (en) * | 2000-08-08 | 2006-02-07 | Verizon Laboratories Inc. | Method, apparatus and program for determining available bandwidth between multiple points in a communication system |
US6973491B1 (en) * | 2000-08-09 | 2005-12-06 | Sun Microsystems, Inc. | System and method for monitoring and managing system assets and asset configurations |
US7089301B1 (en) * | 2000-08-11 | 2006-08-08 | Napster, Inc. | System and method for searching peer-to-peer computer networks by selecting a computer based on at least a number of files shared by the computer |
US7412514B2 (en) * | 2000-08-17 | 2008-08-12 | Hoshiko Llc | Method and apparatus for improving bandwidth efficiency in a computer network |
US20020039352A1 (en) * | 2000-08-17 | 2002-04-04 | Ramzi El-Fekih | Methods, systems, and computer program products for managing a service provided by a network |
US7660869B1 (en) | 2000-08-21 | 2010-02-09 | Vignette Software, LLC | Network real estate analysis |
US7278105B1 (en) * | 2000-08-21 | 2007-10-02 | Vignette Corporation | Visualization and analysis of user clickpaths |
KR20030061794A (en) * | 2000-09-01 | 2003-07-22 | 터트 시스템즈 인코포레이티드 | A method and system to implement policy-based network traffic management |
US7024476B1 (en) * | 2000-09-13 | 2006-04-04 | Canon Kabushiki Kaisha | Directory-enabled device management |
US7340406B1 (en) * | 2000-09-21 | 2008-03-04 | Netscape Communications Corporation | Business rules system |
US9130954B2 (en) | 2000-09-26 | 2015-09-08 | Brocade Communications Systems, Inc. | Distributed health check for global server load balancing |
US7657629B1 (en) | 2000-09-26 | 2010-02-02 | Foundry Networks, Inc. | Global server load balancing |
US7454500B1 (en) | 2000-09-26 | 2008-11-18 | Foundry Networks, Inc. | Global server load balancing |
US7096260B1 (en) * | 2000-09-29 | 2006-08-22 | Cisco Technology, Inc. | Marking network data packets with differentiated services codepoints based on network load |
US7325190B1 (en) | 2000-10-02 | 2008-01-29 | Boehmer Tiffany D | Interface system and method of building rules and constraints for a resource scheduling system |
US7796524B1 (en) * | 2000-10-06 | 2010-09-14 | O'connell David | Monitoring quality of service in packet-based communications |
US7606898B1 (en) | 2000-10-24 | 2009-10-20 | Microsoft Corporation | System and method for distributed management of shared computers |
US7562134B1 (en) * | 2000-10-25 | 2009-07-14 | At&T Intellectual Property I, L.P. | Network traffic analyzer |
US7054930B1 (en) | 2000-10-26 | 2006-05-30 | Cisco Technology, Inc. | System and method for propagating filters |
US8250570B2 (en) | 2000-10-31 | 2012-08-21 | Hewlett-Packard Development Company, L.P. | Automated provisioning framework for internet site servers |
US20020082821A1 (en) | 2000-10-31 | 2002-06-27 | Glenn Ferguson | Data model for automated server configuration |
US6750882B1 (en) * | 2000-10-31 | 2004-06-15 | Verizon Laboratories, Inc. | Automated association of operations with objects in a graphical window |
WO2002037301A1 (en) * | 2000-11-02 | 2002-05-10 | Polycom, Inc. | Conferencing network resource management for call connectivity |
US7340759B1 (en) | 2000-11-10 | 2008-03-04 | Scientific-Atlanta, Inc. | Systems and methods for adaptive pricing in a digital broadband delivery system |
US8225361B2 (en) * | 2000-11-27 | 2012-07-17 | Cox Communications, Inc. | Remote monitoring and control method and apparatus for an information distribution system |
AU3054102A (en) * | 2000-11-30 | 2002-06-11 | Lancope Inc | Flow-based detection of network intrusions |
US20030105887A1 (en) * | 2001-12-03 | 2003-06-05 | Cox Burke David | Method and system for integration of software applications |
US6978301B2 (en) * | 2000-12-06 | 2005-12-20 | Intelliden | System and method for configuring a network device |
US7254638B2 (en) * | 2000-12-15 | 2007-08-07 | International Business Machines Corporation | Method and apparatus for identifying slow links and for providing application-based responses to slow links in a distributed computer network |
US7051070B2 (en) | 2000-12-18 | 2006-05-23 | Timothy Tuttle | Asynchronous messaging using a node specialization architecture in the dynamic routing network |
US8505024B2 (en) | 2000-12-18 | 2013-08-06 | Shaw Parsing Llc | Storing state in a dynamic content routing network |
GB0031157D0 (en) * | 2000-12-20 | 2001-01-31 | Ncr Int Inc | Streaming of data |
US7168044B1 (en) * | 2000-12-22 | 2007-01-23 | Turin Networks | Apparatus and method for automatic network connection provisioning |
US20020087722A1 (en) * | 2000-12-29 | 2002-07-04 | Ragula Systems D/B/A/ Fatpipe Networks | Domain name resolution making IP address selections in response to connection status when multiple connections are present |
NO20010069L (en) * | 2001-01-05 | 2002-07-08 | Ericsson Telefon Ab L M | Multi-user applications in multimedia networks |
US7143154B2 (en) * | 2001-01-26 | 2006-11-28 | Lucent Technologies Inc. | Internet protocol security framework utilizing predictive security association re-negotiation |
US7290283B2 (en) * | 2001-01-31 | 2007-10-30 | Lancope, Inc. | Network port profiling |
AU2002242043B2 (en) * | 2001-01-31 | 2006-12-14 | Cisco Technology, Inc. | Network port profiling |
GB0103381D0 (en) | 2001-02-12 | 2001-03-28 | Eyretel Ltd | Packet data recording method and system |
GB2372673B (en) * | 2001-02-27 | 2003-05-28 | 3Com Corp | Apparatus and method for processing data relating to events on a network |
JP4273669B2 (en) * | 2001-02-28 | 2009-06-03 | 沖電気工業株式会社 | Node information management system and node |
US7720958B2 (en) * | 2001-03-09 | 2010-05-18 | International Business Machines Corporation | Method and system for embedding correlated performance measurements for distributed application performance decomposition |
US8402129B2 (en) * | 2001-03-21 | 2013-03-19 | Alcatel Lucent | Method and apparatus for efficient reactive monitoring |
US7689711B2 (en) | 2001-03-26 | 2010-03-30 | Salesforce.Com, Inc. | System and method for routing messages between applications |
US7788399B2 (en) | 2001-03-26 | 2010-08-31 | Salesforce.Com, Inc. | System and method for mapping of services |
US9948644B2 (en) | 2001-03-26 | 2018-04-17 | Salesforce.Com, Inc. | Routing messages between applications |
US20020143914A1 (en) * | 2001-03-29 | 2002-10-03 | Cihula Joseph F. | Network-aware policy deployment |
US7065566B2 (en) * | 2001-03-30 | 2006-06-20 | Tonic Software, Inc. | System and method for business systems transactions and infrastructure management |
US20020143911A1 (en) * | 2001-03-30 | 2002-10-03 | John Vicente | Host-based network traffic control system |
US8015042B2 (en) | 2001-04-02 | 2011-09-06 | Verint Americas Inc. | Methods for long-range contact center staff planning utilizing discrete event simulation |
US7058687B2 (en) * | 2001-04-03 | 2006-06-06 | Sendmail, Inc. | E-mail system with methodology for accelerating mass mailings |
US6952732B2 (en) | 2001-04-30 | 2005-10-04 | Blue Pumpkin Software, Inc. | Method and apparatus for multi-contact scheduling |
US7107339B1 (en) * | 2001-04-07 | 2006-09-12 | Webmethods, Inc. | Predictive monitoring and problem identification in an information technology (IT) infrastructure |
US6959405B2 (en) | 2001-04-18 | 2005-10-25 | Blue Pumpkin Software, Inc. | Method and system for concurrent error identification in resource scheduling |
WO2002087157A1 (en) * | 2001-04-20 | 2002-10-31 | General Instrument Corporation | Graphical user interface for a transport multiplexer |
US7743147B2 (en) | 2001-04-20 | 2010-06-22 | Hewlett-Packard Development Company, L.P. | Automated provisioning of computing networks using a network database data model |
US7551560B1 (en) * | 2001-04-30 | 2009-06-23 | Opnet Technologies, Inc. | Method of reducing packet loss by resonance identification in communication networks |
US20020161922A1 (en) * | 2001-04-30 | 2002-10-31 | Scott Frank F. | Method for adapting a characteristic of a call server |
US20030018696A1 (en) * | 2001-05-10 | 2003-01-23 | Sanchez Humberto A. | Method for executing multi-system aware applications |
US7505936B2 (en) * | 2001-05-11 | 2009-03-17 | Accenture Global Services Gmbh | Digital content subscription conditioning system |
US7065482B2 (en) * | 2001-05-17 | 2006-06-20 | International Business Machines Corporation | Internet traffic analysis tool |
US7024628B2 (en) * | 2001-05-29 | 2006-04-04 | General Instrument Corporation | Broad band test point element management system |
US7000006B1 (en) * | 2001-05-31 | 2006-02-14 | Cisco Technology, Inc. | Implementing network management policies using topology reduction |
US7895123B1 (en) | 2001-06-12 | 2011-02-22 | Accenture Global Services Limited | Digital content publication |
US20040015579A1 (en) * | 2001-06-14 | 2004-01-22 | Geoffrey Cooper | Method and apparatus for enterprise management |
US7881208B1 (en) | 2001-06-18 | 2011-02-01 | Cisco Technology, Inc. | Gateway load balancing protocol |
US6970432B1 (en) * | 2001-06-18 | 2005-11-29 | Packeteer, Inc. | System and method for dynamically identifying internal hosts in a heterogeneous computing environment with multiple subnetworks |
US7720980B1 (en) * | 2001-06-19 | 2010-05-18 | Packeteer, Inc. | System and method for dynamically controlling a rogue application through incremental bandwidth restrictions |
US6934745B2 (en) * | 2001-06-28 | 2005-08-23 | Packeteer, Inc. | Methods, apparatuses and systems enabling a network services provider to deliver application performance management services |
US8782254B2 (en) * | 2001-06-28 | 2014-07-15 | Oracle America, Inc. | Differentiated quality of service context assignment and propagation |
US20030005091A1 (en) * | 2001-06-29 | 2003-01-02 | International Business Machines Corporation | Method and apparatus for improved monitoring in a distributed computing system |
US8006262B2 (en) | 2001-06-29 | 2011-08-23 | Rodriguez Arturo A | Graphic user interfaces for purchasable and recordable media (PRM) downloads |
US7778600B2 (en) | 2001-06-29 | 2010-08-17 | Crane Merchandising Systems, Inc. | Apparatus and method to provide multiple wireless communication paths to and from remotely located equipment |
US7526788B2 (en) | 2001-06-29 | 2009-04-28 | Scientific-Atlanta, Inc. | Graphic user interface alternate download options for unavailable PRM content |
US7496945B2 (en) | 2001-06-29 | 2009-02-24 | Cisco Technology, Inc. | Interactive program guide for bidirectional services |
US7512964B2 (en) | 2001-06-29 | 2009-03-31 | Cisco Technology | System and method for archiving multiple downloaded recordable media content |
US7164884B2 (en) | 2001-06-29 | 2007-01-16 | Isochron, Llc | Method and system for interfacing a machine controller and a wireless network |
US6925335B2 (en) * | 2001-07-05 | 2005-08-02 | Isochron, Llc | Real-time alert mechanism for monitoring and controlling field assets via wireless and internet technologies |
US7305492B2 (en) * | 2001-07-06 | 2007-12-04 | Juniper Networks, Inc. | Content service aggregation system |
US7200662B2 (en) | 2001-07-06 | 2007-04-03 | Juniper Networks, Inc. | Integrated rule network management system |
US7249139B2 (en) | 2001-07-13 | 2007-07-24 | Accenture Global Services Gmbh | Secure virtual marketplace for virtual objects and services |
EP1407406A1 (en) * | 2001-07-17 | 2004-04-14 | BRITISH TELECOMMUNICATIONS public limited company | Communications network |
US6981029B1 (en) * | 2001-07-17 | 2005-12-27 | Cisco Technology, Inc. | System and method for processing a request for information in a network |
US20030208527A1 (en) * | 2001-07-20 | 2003-11-06 | Lino Lglesais | Method for smart device network application infrastructure (SDNA) |
US20030023681A1 (en) * | 2001-07-26 | 2003-01-30 | International Business Machines Corporation | Sharing messaging device information among network users |
US7424526B1 (en) | 2001-07-31 | 2008-09-09 | Sprint Communications Company L.P. | Internet service node incorporating a bandwidth measurement device and associated methods for evaluating data transfers |
US20030033467A1 (en) * | 2001-08-08 | 2003-02-13 | Satoshi Yoshizawa | Method and apparatus for resource allocation in network router and switch |
US8332502B1 (en) | 2001-08-15 | 2012-12-11 | Metavante Corporation | Business to business network management event detection and response system and method |
US8560709B1 (en) * | 2004-02-25 | 2013-10-15 | F5 Networks, Inc. | System and method for dynamic policy based access over a virtual private network |
US7408961B2 (en) * | 2001-09-13 | 2008-08-05 | General Instrument Corporation | High speed serial data transport between communications hardware modules |
US20030055920A1 (en) * | 2001-09-17 | 2003-03-20 | Deepak Kakadia | Method and apparatus for automatic quality of service configuration based on traffic flow and other network parameters |
US20030059026A1 (en) * | 2001-09-21 | 2003-03-27 | Brugman David L. | Method and apparatus for telecommunications link capacity determination |
US7039916B2 (en) * | 2001-09-24 | 2006-05-02 | Intel Corporation | Data delivery system for adjusting assignment of connection requests to nodes based upon the tracked duration |
US7457862B2 (en) * | 2001-10-22 | 2008-11-25 | Avaya, Inc. | Real time control protocol session matching |
US20030084144A1 (en) * | 2001-10-30 | 2003-05-01 | Lipinski Greg J. | Network bandwidth optimization method and system |
JP2003143218A (en) * | 2001-10-31 | 2003-05-16 | Fujitsu Ltd | Communication band control system |
US20030107590A1 (en) * | 2001-11-07 | 2003-06-12 | Phillippe Levillain | Policy rule management for QoS provisioning |
GB0126908D0 (en) | 2001-11-09 | 2002-01-02 | Ibm | Method and system for display of activity of users |
US7082531B1 (en) | 2001-11-30 | 2006-07-25 | Cisco Technology, Inc. | Method and apparatus for determining enforcement security devices in a network topology |
US7895326B2 (en) * | 2002-03-25 | 2011-02-22 | Lancope, Inc. | Network service zone locking |
US7475426B2 (en) * | 2001-11-30 | 2009-01-06 | Lancope, Inc. | Flow-based detection of network intrusions |
US7418484B2 (en) * | 2001-11-30 | 2008-08-26 | Oracle International Corporation | System and method for actively managing an enterprise of configurable components |
US7437450B1 (en) * | 2001-11-30 | 2008-10-14 | Cisco Technology Inc. | End-to-end performance tool and method for monitoring electronic-commerce transactions |
US7644151B2 (en) * | 2002-01-31 | 2010-01-05 | Lancope, Inc. | Network service zone locking |
US7512980B2 (en) * | 2001-11-30 | 2009-03-31 | Lancope, Inc. | Packet sampling flow-based detection of network intrusions |
US7222269B2 (en) * | 2001-12-06 | 2007-05-22 | Ns Solutions Corporation | Performance evaluation device, performance evaluation information managing device, performance evaluation method, performance evaluation information managing method, performance evaluation system |
US7197558B1 (en) * | 2001-12-17 | 2007-03-27 | Bellsouth Intellectual Property Corp. | Methods and systems for network element fault information processing |
US7203169B1 (en) * | 2001-12-20 | 2007-04-10 | Packeteer, Inc. | Interface facilitating configuration of network resource utilization |
US7167917B2 (en) * | 2002-01-03 | 2007-01-23 | International Business Machines Corporation | Visual tool for developing service components for use in advanced intelligent networks |
US7636937B1 (en) | 2002-01-11 | 2009-12-22 | Cisco Technology, Inc. | Method and apparatus for comparing access control lists for configuring a security policy on a network |
US7640335B1 (en) * | 2002-01-11 | 2009-12-29 | Mcafee, Inc. | User-configurable network analysis digest system and method |
US7016952B2 (en) * | 2002-01-24 | 2006-03-21 | Ge Medical Technology Services, Inc. | System and method for universal remote access and display of diagnostic images for service delivery |
US20050060365A1 (en) * | 2002-01-24 | 2005-03-17 | Robinson Scott L. | Context-based information processing |
US7047296B1 (en) * | 2002-01-28 | 2006-05-16 | Witness Systems, Inc. | Method and system for selectively dedicating resources for recording data exchanged between entities attached to a network |
US9008300B2 (en) | 2002-01-28 | 2015-04-14 | Verint Americas Inc | Complex recording trigger |
US7424715B1 (en) | 2002-01-28 | 2008-09-09 | Verint Americas Inc. | Method and system for presenting events associated with recorded data exchanged between a server and a user |
US7882212B1 (en) | 2002-01-28 | 2011-02-01 | Verint Systems Inc. | Methods and devices for archiving recorded interactions and retrieving stored recorded interactions |
US7219138B2 (en) | 2002-01-31 | 2007-05-15 | Witness Systems, Inc. | Method, apparatus, and system for capturing data exchanged between a server and a user |
US7334251B2 (en) | 2002-02-11 | 2008-02-19 | Scientific-Atlanta, Inc. | Management of television advertising |
US20030163558A1 (en) * | 2002-02-25 | 2003-08-28 | Docomo Communications Laboratories Usa, Inc. | System and method for Hyper Operator controlled network probing across overlaid heterogeneous access networks |
US7068610B2 (en) | 2002-02-26 | 2006-06-27 | Unruh Lincoln J | System and method for reliable communications over multiple packet RF networks |
DE10210707A1 (en) * | 2002-03-12 | 2003-10-02 | Deutsche Telekom Ag | Process for the output of status data |
GB2386501B (en) * | 2002-03-14 | 2005-03-16 | Manuel Oliveira | Network performance indicators |
US7489687B2 (en) * | 2002-04-11 | 2009-02-10 | Avaya. Inc. | Emergency bandwidth allocation with an RSVP-like protocol |
JP2003319009A (en) * | 2002-04-24 | 2003-11-07 | Communication Research Laboratory | Data communication control method, data communication control system, data sending mechanism, data communication control program, and data communication control program recording medium |
US7552205B2 (en) * | 2002-05-21 | 2009-06-23 | Accenture Global Services Gmbh | Distributed transaction event matching |
US7039715B2 (en) * | 2002-05-21 | 2006-05-02 | Microsoft Corporation | Methods and systems for a receiver to allocate bandwidth among incoming communications flows |
US8447963B2 (en) | 2002-06-12 | 2013-05-21 | Bladelogic Inc. | Method and system for simplifying distributed server management |
AUPS339102A0 (en) * | 2002-07-04 | 2002-08-01 | Three Happy Guys Pty Ltd | Method of monitoring volumes of data between multiple terminals and an external communication network |
US7469338B2 (en) * | 2002-07-29 | 2008-12-23 | Broadcom Corporation | System and method for cryptographic control of system configurations |
US7086061B1 (en) | 2002-08-01 | 2006-08-01 | Foundry Networks, Inc. | Statistical tracking of global server load balancing for selecting the best network address from ordered list of network addresses based on a set of performance metrics |
US7676576B1 (en) | 2002-08-01 | 2010-03-09 | Foundry Networks, Inc. | Method and system to clear counters used for statistical tracking for global server load balancing |
US7574508B1 (en) | 2002-08-07 | 2009-08-11 | Foundry Networks, Inc. | Canonical name (CNAME) handling for global server load balancing |
EP1552412A4 (en) * | 2002-08-14 | 2007-05-23 | Drs Technical Services Inc | Method and apparatus for monitoring and controlling the allocation of network bandwidth |
GB0219493D0 (en) | 2002-08-21 | 2002-10-02 | Eyretel Plc | Method and system for communications monitoring |
EP1315358A1 (en) * | 2002-09-12 | 2003-05-28 | Agilent Technologies Inc. a Delaware Corporation | Data-transparent management system for controlling measurement instruments |
US7324447B1 (en) * | 2002-09-30 | 2008-01-29 | Packeteer, Inc. | Methods, apparatuses and systems facilitating concurrent classification and control of tunneled and non-tunneled network traffic |
US8176154B2 (en) * | 2002-09-30 | 2012-05-08 | Avaya Inc. | Instantaneous user initiation voice quality feedback |
US7359979B2 (en) | 2002-09-30 | 2008-04-15 | Avaya Technology Corp. | Packet prioritization and associated bandwidth and buffer management techniques for audio over IP |
US20040073690A1 (en) * | 2002-09-30 | 2004-04-15 | Neil Hepworth | Voice over IP endpoint call admission |
US6975963B2 (en) * | 2002-09-30 | 2005-12-13 | Mcdata Corporation | Method and system for storing and reporting network performance metrics using histograms |
WO2004034229A2 (en) * | 2002-10-10 | 2004-04-22 | Rocksteady Networks, Inc. | System and method for providing access control |
WO2004036371A2 (en) * | 2002-10-16 | 2004-04-29 | Rocksteady Networks, Inc. | System and method for dynamic bandwidth provisioning |
US20040088314A1 (en) * | 2002-10-31 | 2004-05-06 | Simes Scott T. | Method and system for reporting performance data for a network |
US7100091B2 (en) * | 2002-11-05 | 2006-08-29 | Spirent Communications | Method and system for testing networks |
US7283480B1 (en) * | 2002-11-12 | 2007-10-16 | Lockheed Martin Corporation | Network system health monitoring using cantor set signals |
US7359930B2 (en) * | 2002-11-21 | 2008-04-15 | Arbor Networks | System and method for managing computer networks |
JP3789425B2 (en) * | 2002-11-27 | 2006-06-21 | リンナイ株式会社 | Hot air heater |
JP2004178472A (en) * | 2002-11-29 | 2004-06-24 | Sanyo Electric Co Ltd | Program acquisition method and packet transfer device capable of using its method |
KR100457538B1 (en) * | 2002-12-02 | 2004-11-17 | 삼성전자주식회사 | Multimedia data transmission methods in wireless LAN and point coordinator device in wireless LAN |
US7949765B2 (en) * | 2002-12-02 | 2011-05-24 | Sap Aktiengesellschaft | Data structure for analyzing user sessions |
US20040111513A1 (en) * | 2002-12-04 | 2004-06-10 | Shen Simon S. | Automatic employment of resource load information with one or more policies to automatically determine whether to decrease one or more loads |
US7386611B2 (en) * | 2002-12-10 | 2008-06-10 | International Business Machines Corporation | Apparatus and methods for co-location and offloading of web site traffic based on traffic pattern recognition |
US7792951B2 (en) * | 2002-12-10 | 2010-09-07 | International Business Machines Corporation | Apparatus and methods for classification of web sites |
KR100523486B1 (en) * | 2002-12-13 | 2005-10-24 | 한국전자통신연구원 | Traffic measurement system and traffic analysis method thereof |
US7301909B2 (en) * | 2002-12-20 | 2007-11-27 | Compucom Systems, Inc. | Trouble-ticket generation in network management environment |
US20040122940A1 (en) * | 2002-12-20 | 2004-06-24 | Gibson Edward S. | Method for monitoring applications in a network which does not natively support monitoring |
US7219131B2 (en) * | 2003-01-16 | 2007-05-15 | Ironport Systems, Inc. | Electronic message delivery using an alternate source approach |
US7478151B1 (en) * | 2003-01-23 | 2009-01-13 | Gomez, Inc. | System and method for monitoring global network performance |
US20040148386A1 (en) * | 2003-01-24 | 2004-07-29 | Dennis Bushmitch | Dynamic CC/PP-based profile generation framework for network conditions assessment |
US7437675B2 (en) * | 2003-02-03 | 2008-10-14 | Hewlett-Packard Development Company, L.P. | System and method for monitoring event based systems |
US7689676B2 (en) * | 2003-03-06 | 2010-03-30 | Microsoft Corporation | Model-based policy application |
US7890543B2 (en) | 2003-03-06 | 2011-02-15 | Microsoft Corporation | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
US8122106B2 (en) | 2003-03-06 | 2012-02-21 | Microsoft Corporation | Integrating design, deployment, and management phases for systems |
WO2004081730A2 (en) * | 2003-03-07 | 2004-09-23 | Netnostics, Inc. | Network architecture |
US7076562B2 (en) * | 2003-03-17 | 2006-07-11 | July Systems, Inc. | Application intermediation gateway |
US20050021683A1 (en) * | 2003-03-27 | 2005-01-27 | Chris Newton | Method and apparatus for correlating network activity through visualizing network data |
US7373416B2 (en) * | 2003-04-24 | 2008-05-13 | Akamai Technologies, Inc. | Method and system for constraining server usage in a distributed network |
US7519916B1 (en) * | 2003-06-16 | 2009-04-14 | Microsoft Corporation | Methods for tailoring a bandwidth profile for an operating environment |
US7392311B2 (en) * | 2003-06-19 | 2008-06-24 | International Business Machines Corporation | System and method for throttling events in an information technology system |
US7676559B2 (en) * | 2003-06-24 | 2010-03-09 | Alcatel Lucent | Real-time policy evaluation mechanism |
US8805966B2 (en) | 2003-07-28 | 2014-08-12 | Limelight Networks, Inc. | Rich content download |
US7703029B2 (en) * | 2003-07-28 | 2010-04-20 | Sap Ag | Grid browser component |
US7631069B2 (en) | 2003-07-28 | 2009-12-08 | Sap Ag | Maintainable grid managers |
US7594015B2 (en) * | 2003-07-28 | 2009-09-22 | Sap Ag | Grid organization |
US7568199B2 (en) * | 2003-07-28 | 2009-07-28 | Sap Ag. | System for matching resource request that freeing the reserved first resource and forwarding the request to second resource if predetermined time period expired |
US7673054B2 (en) | 2003-07-28 | 2010-03-02 | Sap Ag. | Grid manageable application process management scheme |
US7574707B2 (en) * | 2003-07-28 | 2009-08-11 | Sap Ag | Install-run-remove mechanism |
US7546553B2 (en) * | 2003-07-28 | 2009-06-09 | Sap Ag | Grid landscape component |
US20100011090A1 (en) * | 2008-07-14 | 2010-01-14 | Limelight Networks, Inc. | Network-aware download manager |
US7526541B2 (en) * | 2003-07-29 | 2009-04-28 | Enterasys Networks, Inc. | System and method for dynamic network policy management |
US7688733B1 (en) * | 2003-08-04 | 2010-03-30 | Sprint Communications Company L.P. | System and method for bandwidth selection in a communication network |
US7593936B2 (en) | 2003-08-11 | 2009-09-22 | Triumfant, Inc. | Systems and methods for automated computer support |
FR2858900B1 (en) * | 2003-08-12 | 2006-01-06 | Cit Alcatel | PROVIDING RESOURCE RESERVATION SERVICES WITHIN A RESOURCE MANAGEMENT COMMUNICATIONS NETWORK THROUGH POLICY RULES |
US7624438B2 (en) | 2003-08-20 | 2009-11-24 | Eric White | System and method for providing a secure connection between networked computers |
US20050078606A1 (en) * | 2003-09-11 | 2005-04-14 | Bernstein David R. | Pattern-based correlation of non-translative network segments |
US20050060403A1 (en) * | 2003-09-11 | 2005-03-17 | Bernstein David R. | Time-based correlation of non-translative network segments |
US9584360B2 (en) | 2003-09-29 | 2017-02-28 | Foundry Networks, Llc | Global server load balancing support for private VIP addresses |
US20050076339A1 (en) * | 2003-10-03 | 2005-04-07 | Nortel Networks Limited | Method and apparatus for automated negotiation for resources on a switched underlay network |
US7810090B2 (en) | 2003-12-17 | 2010-10-05 | Sap Ag | Grid compute node software application deployment |
US7546355B2 (en) * | 2004-01-16 | 2009-06-09 | Bloomberg Finance L.P. | Network architecture for data transmission |
US8161388B2 (en) | 2004-01-21 | 2012-04-17 | Rodriguez Arturo A | Interactive discovery of display device characteristics |
US8316128B2 (en) * | 2004-01-26 | 2012-11-20 | Forte Internet Software, Inc. | Methods and system for creating and managing identity oriented networked communication |
CA2554915C (en) | 2004-02-17 | 2013-05-28 | Ironport Systems, Inc. | Collecting, aggregating, and managing information relating to electronic messages |
US7778422B2 (en) | 2004-02-27 | 2010-08-17 | Microsoft Corporation | Security associations for devices |
US7610621B2 (en) | 2004-03-10 | 2009-10-27 | Eric White | System and method for behavior-based firewall modeling |
US7665130B2 (en) | 2004-03-10 | 2010-02-16 | Eric White | System and method for double-capture/double-redirect to a different location |
US7509625B2 (en) | 2004-03-10 | 2009-03-24 | Eric White | System and method for comprehensive code generation for system management |
US8543710B2 (en) | 2004-03-10 | 2013-09-24 | Rpx Corporation | Method and system for controlling network access |
US7590728B2 (en) | 2004-03-10 | 2009-09-15 | Eric White | System and method for detection of aberrant network behavior by clients of a network access gateway |
US7698730B2 (en) * | 2004-03-16 | 2010-04-13 | Riverbed Technology, Inc. | Service detection |
FR2867932A1 (en) * | 2004-03-18 | 2005-09-23 | France Telecom | RECEIVING FLOW MEASUREMENT FOR A TERMINAL |
WO2005093576A1 (en) * | 2004-03-28 | 2005-10-06 | Robert Iakobashvili | Visualization of packet network performance, analysis and optimization for design |
US20050235364A1 (en) * | 2004-04-15 | 2005-10-20 | Wilson Christopher S | Authentication mechanism permitting access to data stored in a data processing device |
US20050235336A1 (en) * | 2004-04-15 | 2005-10-20 | Kenneth Ma | Data storage system and method that supports personal video recorder functionality |
US20050231849A1 (en) * | 2004-04-15 | 2005-10-20 | Viresh Rustagi | Graphical user interface for hard disk drive management in a data storage system |
US7681007B2 (en) | 2004-04-15 | 2010-03-16 | Broadcom Corporation | Automatic expansion of hard disk drive capacity in a storage device |
US7555613B2 (en) * | 2004-05-11 | 2009-06-30 | Broadcom Corporation | Storage access prioritization using a data storage device |
US20050262322A1 (en) * | 2004-05-21 | 2005-11-24 | Kenneth Ma | System and method of replacing a data storage drive |
US20050235283A1 (en) * | 2004-04-15 | 2005-10-20 | Wilson Christopher S | Automatic setup of parameters in networked devices |
US20050267958A1 (en) * | 2004-04-28 | 2005-12-01 | International Business Machines Corporation | Facilitating management of resources by tracking connection usage of the resources |
US7679612B2 (en) * | 2004-04-30 | 2010-03-16 | Microsoft Corporation | Configuration goals via video presenting network |
US20050246529A1 (en) | 2004-04-30 | 2005-11-03 | Microsoft Corporation | Isolated persistent identity storage for authentication of computing devies |
US7584301B1 (en) | 2004-05-06 | 2009-09-01 | Foundry Networks, Inc. | Host-level policies for global server load balancing |
US7496651B1 (en) * | 2004-05-06 | 2009-02-24 | Foundry Networks, Inc. | Configurable geographic prefixes for global server load balancing |
US8073819B2 (en) * | 2004-05-11 | 2011-12-06 | At&T Intellectual Property I, L.P. | System and method for storing element information |
US7756930B2 (en) | 2004-05-28 | 2010-07-13 | Ironport Systems, Inc. | Techniques for determining the reputation of a message sender |
US7870200B2 (en) * | 2004-05-29 | 2011-01-11 | Ironport Systems, Inc. | Monitoring the flow of messages received at a server |
US7873695B2 (en) | 2004-05-29 | 2011-01-18 | Ironport Systems, Inc. | Managing connections and messages at a server by associating different actions for both different senders and different recipients |
US7917588B2 (en) | 2004-05-29 | 2011-03-29 | Ironport Systems, Inc. | Managing delivery of electronic messages using bounce profiles |
US7849142B2 (en) | 2004-05-29 | 2010-12-07 | Ironport Systems, Inc. | Managing connections, messages, and directory harvest attacks at a server |
US8166310B2 (en) | 2004-05-29 | 2012-04-24 | Ironport Systems, Inc. | Method and apparatus for providing temporary access to a network device |
US7748038B2 (en) | 2004-06-16 | 2010-06-29 | Ironport Systems, Inc. | Method and apparatus for managing computer virus outbreaks |
US10284571B2 (en) * | 2004-06-28 | 2019-05-07 | Riverbed Technology, Inc. | Rule based alerting in anomaly detection |
US7978827B1 (en) | 2004-06-30 | 2011-07-12 | Avaya Inc. | Automatic configuration of call handling based on end-user needs and characteristics |
US20060020699A1 (en) * | 2004-07-23 | 2006-01-26 | D Esposito John J | Method and computer program for web site performance monitoring and testing by variable simultaneous angulation |
US7778194B1 (en) * | 2004-08-13 | 2010-08-17 | Packeteer, Inc. | Examination of connection handshake to enhance classification of encrypted network traffic |
EP1628443A1 (en) * | 2004-08-16 | 2006-02-22 | Universite Pierre Et Marie Curie | Method for making a network equipment proactive |
JP2008510259A (en) * | 2004-08-17 | 2008-04-03 | ショー パーシング リミティド ライアビリティ カンパニー | Modular event-driven processing |
JP4668271B2 (en) | 2004-08-17 | 2011-04-13 | ショー パーシング リミティド ライアビリティ カンパニー | Upstream failure detection and recovery methods |
WO2006023459A1 (en) | 2004-08-17 | 2006-03-02 | Shaw Parsing Llc | Techniques for delivering personalized content with a real-time routing network |
US7423977B1 (en) * | 2004-08-23 | 2008-09-09 | Foundry Networks Inc. | Smoothing algorithm for round trip time (RTT) measurements |
US8659996B2 (en) * | 2004-09-17 | 2014-02-25 | At&T Intellectual Property I, L.P. | Network capacity management system and method |
US7805515B2 (en) * | 2004-09-20 | 2010-09-28 | Camiant, Inc. | Method for dynamic rate adaptation based on selective passive network monitoring |
US8613048B2 (en) | 2004-09-30 | 2013-12-17 | Citrix Systems, Inc. | Method and apparatus for providing authorized remote access to application sessions |
US7711835B2 (en) | 2004-09-30 | 2010-05-04 | Citrix Systems, Inc. | Method and apparatus for reducing disclosure of proprietary data in a networked environment |
US7748032B2 (en) | 2004-09-30 | 2010-06-29 | Citrix Systems, Inc. | Method and apparatus for associating tickets in a ticket hierarchy |
US8499337B1 (en) | 2004-10-06 | 2013-07-30 | Mcafee, Inc. | Systems and methods for delegation and notification of administration of internet access |
US20070086352A1 (en) * | 2004-10-20 | 2007-04-19 | France Telecom | Method of monitoring multimedia stream exchange session initialization messages and a server and an installation for carrying out said method |
US7555549B1 (en) * | 2004-11-07 | 2009-06-30 | Qlogic, Corporation | Clustered computing model and display |
US7565383B2 (en) * | 2004-12-20 | 2009-07-21 | Sap Ag. | Application recovery |
US7793290B2 (en) | 2004-12-20 | 2010-09-07 | Sap Ag | Grip application acceleration by executing grid application based on application usage history prior to user request for application execution |
TWI268074B (en) * | 2005-01-07 | 2006-12-01 | Netklass Technology Inc | Method and system of bandwidth management for Internet communication |
US20060159432A1 (en) | 2005-01-14 | 2006-07-20 | Citrix Systems, Inc. | System and methods for automatic time-warped playback in rendering a recorded computer session |
US8935316B2 (en) | 2005-01-14 | 2015-01-13 | Citrix Systems, Inc. | Methods and systems for in-session playback on a local machine of remotely-stored and real time presentation layer protocol data |
US8200828B2 (en) | 2005-01-14 | 2012-06-12 | Citrix Systems, Inc. | Systems and methods for single stack shadowing |
US8145777B2 (en) | 2005-01-14 | 2012-03-27 | Citrix Systems, Inc. | Method and system for real-time seeking during playback of remote presentation protocols |
US7831728B2 (en) | 2005-01-14 | 2010-11-09 | Citrix Systems, Inc. | Methods and systems for real-time seeking during real-time playback of a presentation layer protocol data stream |
US8296441B2 (en) | 2005-01-14 | 2012-10-23 | Citrix Systems, Inc. | Methods and systems for joining a real-time session of presentation layer protocol data |
US7529185B2 (en) * | 2005-01-26 | 2009-05-05 | International Business Machines Corporation | Method, system and program product for determining bandwidth consumption across a multi-tiered computer environment |
US8108510B2 (en) * | 2005-01-28 | 2012-01-31 | Jds Uniphase Corporation | Method for implementing TopN measurements in operations support systems |
US8024568B2 (en) | 2005-01-28 | 2011-09-20 | Citrix Systems, Inc. | Method and system for verification of an endpoint security scan |
US7843938B1 (en) | 2005-02-25 | 2010-11-30 | Citrix Systems, Inc. | QoS optimization with compression |
US20060212422A1 (en) * | 2005-03-21 | 2006-09-21 | Anil Khilani | Efficiently executing commands against a large set of servers with near real time feedback of execution and presentation of the output of the commands |
US7685270B1 (en) * | 2005-03-31 | 2010-03-23 | Amazon Technologies, Inc. | Method and apparatus for measuring latency in web services |
US20060230136A1 (en) * | 2005-04-12 | 2006-10-12 | Kenneth Ma | Intelligent auto-archiving |
US7802144B2 (en) | 2005-04-15 | 2010-09-21 | Microsoft Corporation | Model-based system monitoring |
US8489728B2 (en) | 2005-04-15 | 2013-07-16 | Microsoft Corporation | Model-based system monitoring |
US7797147B2 (en) | 2005-04-15 | 2010-09-14 | Microsoft Corporation | Model-based system monitoring |
US7924732B2 (en) * | 2005-04-19 | 2011-04-12 | Hewlett-Packard Development Company, L.P. | Quality of service in IT infrastructures |
US20060288296A1 (en) * | 2005-05-12 | 2006-12-21 | David Rosenbluth | Receptor array for managing network traffic data |
US20060271857A1 (en) * | 2005-05-12 | 2006-11-30 | David Rosenbluth | Imaging system for network traffic data |
US20060268852A1 (en) * | 2005-05-12 | 2006-11-30 | David Rosenbluth | Lens-based apparatus and method for filtering network traffic data |
US7546368B2 (en) * | 2005-06-01 | 2009-06-09 | Neustar, Inc. | Systems and methods for isolating local performance variation in website monitoring |
GB2428533B (en) * | 2005-06-24 | 2007-08-22 | Hewlett Packard Development Co | Determining data flows in a network |
US8549513B2 (en) | 2005-06-29 | 2013-10-01 | Microsoft Corporation | Model-based virtual system provisioning |
JP2007053465A (en) * | 2005-08-16 | 2007-03-01 | Kddi Corp | Traffic control system, traffic control method, communications apparatus and computer program |
US7434041B2 (en) * | 2005-08-22 | 2008-10-07 | Oracle International Corporation | Infrastructure for verifying configuration and health of a multi-node computer system |
US8189472B2 (en) | 2005-09-07 | 2012-05-29 | Mcdonald James F | Optimizing bandwidth utilization to a subscriber premises |
US8676974B2 (en) * | 2005-09-29 | 2014-03-18 | International Business Machines Corporation | Quality of service (QoS) based planning in web services aggregation |
US8191008B2 (en) | 2005-10-03 | 2012-05-29 | Citrix Systems, Inc. | Simulating multi-monitor functionality in a single monitor environment |
US8171127B2 (en) * | 2005-10-07 | 2012-05-01 | Citrix Systems, Inc. | Systems and methods for response monitoring |
US8615578B2 (en) * | 2005-10-07 | 2013-12-24 | Oracle International Corporation | Using a standby data storage system to detect the health of a cluster of data storage servers |
US7890752B2 (en) | 2005-10-31 | 2011-02-15 | Scenera Technologies, Llc | Methods, systems, and computer program products for associating an originator of a network packet with the network packet using biometric information |
US7941309B2 (en) | 2005-11-02 | 2011-05-10 | Microsoft Corporation | Modeling IT operations/policies |
US20070106784A1 (en) * | 2005-11-08 | 2007-05-10 | Dickman David T | Systems, methods and apparatus to identify network maintenance zones |
US20070112951A1 (en) * | 2005-11-14 | 2007-05-17 | Fung Joseph B K | Automatic website workload management |
US8484068B2 (en) | 2005-12-14 | 2013-07-09 | Crane Merchandising Systems, Inc. | Method and system for evaluating consumer demand for multiple products and services at remotely located equipment |
CA2633966C (en) * | 2005-12-15 | 2014-04-15 | Lehman Brothers Inc. | System and method for secure remote desktop access |
US20070150581A1 (en) * | 2005-12-22 | 2007-06-28 | American Express Travel Services, Co., Inc. a New York Corporation | System and method for monitoring system performance levels across a network |
US8112298B2 (en) | 2006-02-22 | 2012-02-07 | Verint Americas, Inc. | Systems and methods for workforce optimization |
US8112306B2 (en) | 2006-02-22 | 2012-02-07 | Verint Americas, Inc. | System and method for facilitating triggers and workflows in workforce optimization |
US8108237B2 (en) | 2006-02-22 | 2012-01-31 | Verint Americas, Inc. | Systems for integrating contact center monitoring, training and scheduling |
US7864946B1 (en) | 2006-02-22 | 2011-01-04 | Verint Americas Inc. | Systems and methods for scheduling call center agents using quality data and correlation-based discovery |
US7853006B1 (en) | 2006-02-22 | 2010-12-14 | Verint Americas Inc. | Systems and methods for scheduling call center agents using quality data and correlation-based discovery |
US8160233B2 (en) | 2006-02-22 | 2012-04-17 | Verint Americas Inc. | System and method for detecting and displaying business transactions |
US8117064B2 (en) | 2006-02-22 | 2012-02-14 | Verint Americas, Inc. | Systems and methods for workforce optimization and analytics |
US8670552B2 (en) | 2006-02-22 | 2014-03-11 | Verint Systems, Inc. | System and method for integrated display of multiple types of call agent data |
US7663626B2 (en) * | 2006-02-28 | 2010-02-16 | At&T Corp. | Method and apparatus for providing a network traffic composite graph |
US8447802B2 (en) | 2006-03-08 | 2013-05-21 | Riverbed Technology, Inc. | Address manipulation to provide for the use of network tools even when transaction acceleration is in use over a network |
US7734783B1 (en) | 2006-03-21 | 2010-06-08 | Verint Americas Inc. | Systems and methods for determining allocations for distributed multi-site contact centers |
US8126134B1 (en) | 2006-03-30 | 2012-02-28 | Verint Americas, Inc. | Systems and methods for scheduling of outbound agents |
US7995612B2 (en) | 2006-03-31 | 2011-08-09 | Verint Americas, Inc. | Systems and methods for capturing communication signals [32-bit or 128-bit addresses] |
US7672746B1 (en) | 2006-03-31 | 2010-03-02 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US8000465B2 (en) | 2006-03-31 | 2011-08-16 | Verint Americas, Inc. | Systems and methods for endpoint recording using gateways |
US7701972B1 (en) | 2006-03-31 | 2010-04-20 | Verint Americas Inc. | Internet protocol analyzing |
US7792278B2 (en) | 2006-03-31 | 2010-09-07 | Verint Americas Inc. | Integration of contact center surveys |
US8204056B2 (en) | 2006-03-31 | 2012-06-19 | Verint Americas, Inc. | Systems and methods for endpoint recording using a media application server |
US7826608B1 (en) | 2006-03-31 | 2010-11-02 | Verint Americas Inc. | Systems and methods for calculating workforce staffing statistics |
US7852994B1 (en) | 2006-03-31 | 2010-12-14 | Verint Americas Inc. | Systems and methods for recording audio |
US8130938B2 (en) | 2006-03-31 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for endpoint recording using recorders |
US8254262B1 (en) | 2006-03-31 | 2012-08-28 | Verint Americas, Inc. | Passive recording and load balancing |
US8442033B2 (en) * | 2006-03-31 | 2013-05-14 | Verint Americas, Inc. | Distributed voice over internet protocol recording |
US8594313B2 (en) | 2006-03-31 | 2013-11-26 | Verint Systems, Inc. | Systems and methods for endpoint recording using phones |
US7822018B2 (en) | 2006-03-31 | 2010-10-26 | Verint Americas Inc. | Duplicate media stream |
US7680264B2 (en) | 2006-03-31 | 2010-03-16 | Verint Americas Inc. | Systems and methods for endpoint recording using a conference bridge |
US7774854B1 (en) | 2006-03-31 | 2010-08-10 | Verint Americas Inc. | Systems and methods for protecting information |
US8155275B1 (en) | 2006-04-03 | 2012-04-10 | Verint Americas, Inc. | Systems and methods for managing alarms from recorders |
US8331549B2 (en) | 2006-05-01 | 2012-12-11 | Verint Americas Inc. | System and method for integrated workforce and quality management |
US8396732B1 (en) | 2006-05-08 | 2013-03-12 | Verint Americas Inc. | System and method for integrated workforce and analytics |
US7817795B2 (en) | 2006-05-10 | 2010-10-19 | Verint Americas, Inc. | Systems and methods for data synchronization in a customer center |
US8051163B2 (en) | 2006-05-11 | 2011-11-01 | Computer Associates Think, Inc. | Synthetic transactions based on system history and load |
US7738377B1 (en) * | 2006-05-22 | 2010-06-15 | At&T Intellectual Property Ii, L.P. | Method and apparatus for volumetric thresholding and alarming on internet protocol traffic |
JP4899633B2 (en) * | 2006-05-22 | 2012-03-21 | 富士通株式会社 | Communication performance analysis program, communication performance analysis device, and communication performance analysis method |
US20080037427A1 (en) * | 2006-05-24 | 2008-02-14 | Kist Alexander A | Estimating bandwidth |
US7660406B2 (en) | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for integrating outsourcers |
US7660407B2 (en) | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for scheduling contact center agents |
US7617367B2 (en) * | 2006-06-27 | 2009-11-10 | International Business Machines Corporation | Memory system including a two-on-one link memory subsystem interconnection |
US7660307B2 (en) | 2006-06-29 | 2010-02-09 | Verint Americas Inc. | Systems and methods for providing recording as a network service |
US7903568B2 (en) | 2006-06-29 | 2011-03-08 | Verint Americas Inc. | Systems and methods for providing recording as a network service |
US7853800B2 (en) | 2006-06-30 | 2010-12-14 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US7948909B2 (en) | 2006-06-30 | 2011-05-24 | Embarq Holdings Company, Llc | System and method for resetting counters counting network performance information at network communications devices on a packet network |
US8194643B2 (en) | 2006-10-19 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for monitoring the connection of an end-user to a remote network |
US7966397B2 (en) | 2006-06-30 | 2011-06-21 | Verint Americas Inc. | Distributive data capture |
US7769176B2 (en) | 2006-06-30 | 2010-08-03 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US8289965B2 (en) | 2006-10-19 | 2012-10-16 | Embarq Holdings Company, Llc | System and method for establishing a communications session with an end-user based on the state of a network connection |
US8131578B2 (en) | 2006-06-30 | 2012-03-06 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US8000318B2 (en) | 2006-06-30 | 2011-08-16 | Embarq Holdings Company, Llc | System and method for call routing based on transmission performance of a packet network |
US9094257B2 (en) | 2006-06-30 | 2015-07-28 | Centurylink Intellectual Property Llc | System and method for selecting a content delivery network |
US8477614B2 (en) | 2006-06-30 | 2013-07-02 | Centurylink Intellectual Property Llc | System and method for routing calls if potential call paths are impaired or congested |
US20080052535A1 (en) * | 2006-06-30 | 2008-02-28 | Witness Systems, Inc. | Systems and Methods for Recording Encrypted Interactions |
US8488447B2 (en) | 2006-06-30 | 2013-07-16 | Centurylink Intellectual Property Llc | System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance |
US7848524B2 (en) | 2006-06-30 | 2010-12-07 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US7953621B2 (en) | 2006-06-30 | 2011-05-31 | Verint Americas Inc. | Systems and methods for displaying agent activity exceptions |
US7881471B2 (en) | 2006-06-30 | 2011-02-01 | Verint Systems Inc. | Systems and methods for recording an encrypted interaction |
US8717911B2 (en) | 2006-06-30 | 2014-05-06 | Centurylink Intellectual Property Llc | System and method for collecting network performance information |
US7853685B1 (en) * | 2006-07-10 | 2010-12-14 | Network General Technology | Identifying critical network and application entities |
US7720954B2 (en) * | 2006-08-03 | 2010-05-18 | Citrix Systems, Inc. | Method and appliance for using a dynamic response time to determine responsiveness of network services |
US8531954B2 (en) | 2006-08-22 | 2013-09-10 | Centurylink Intellectual Property Llc | System and method for handling reservation requests with a connection admission control engine |
US8125897B2 (en) * | 2006-08-22 | 2012-02-28 | Embarq Holdings Company Lp | System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets |
US8537695B2 (en) | 2006-08-22 | 2013-09-17 | Centurylink Intellectual Property Llc | System and method for establishing a call being received by a trunk on a packet network |
US9479341B2 (en) | 2006-08-22 | 2016-10-25 | Centurylink Intellectual Property Llc | System and method for initiating diagnostics on a packet network node |
US8312120B2 (en) | 2006-08-22 | 2012-11-13 | Citrix Systems, Inc. | Systems and methods for providing dynamic spillover of virtual servers based on bandwidth |
US8015294B2 (en) | 2006-08-22 | 2011-09-06 | Embarq Holdings Company, LP | Pin-hole firewall for communicating data packets on a packet network |
US7808918B2 (en) | 2006-08-22 | 2010-10-05 | Embarq Holdings Company, Llc | System and method for dynamically shaping network traffic |
US8064391B2 (en) | 2006-08-22 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for monitoring and optimizing network performance to a wireless device |
US8224255B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for managing radio frequency windows |
US8493858B2 (en) | 2006-08-22 | 2013-07-23 | Citrix Systems, Inc | Systems and methods for providing dynamic connection spillover among virtual servers |
US7684332B2 (en) | 2006-08-22 | 2010-03-23 | Embarq Holdings Company, Llc | System and method for adjusting the window size of a TCP packet through network elements |
US8144586B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for controlling network bandwidth with a connection admission control engine |
US8194555B2 (en) | 2006-08-22 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for using distributed network performance information tables to manage network communications |
US8040811B2 (en) | 2006-08-22 | 2011-10-18 | Embarq Holdings Company, Llc | System and method for collecting and managing network performance information |
US8549405B2 (en) | 2006-08-22 | 2013-10-01 | Centurylink Intellectual Property Llc | System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally |
US8238253B2 (en) | 2006-08-22 | 2012-08-07 | Embarq Holdings Company, Llc | System and method for monitoring interlayer devices and optimizing network performance |
US8743703B2 (en) | 2006-08-22 | 2014-06-03 | Centurylink Intellectual Property Llc | System and method for tracking application resource usage |
US8189468B2 (en) | 2006-10-25 | 2012-05-29 | Embarq Holdings, Company, LLC | System and method for regulating messages between networks |
US7940735B2 (en) | 2006-08-22 | 2011-05-10 | Embarq Holdings Company, Llc | System and method for selecting an access point |
US8576722B2 (en) | 2006-08-22 | 2013-11-05 | Centurylink Intellectual Property Llc | System and method for modifying connectivity fault management packets |
US8307065B2 (en) | 2006-08-22 | 2012-11-06 | Centurylink Intellectual Property Llc | System and method for remotely controlling network operators |
US8223655B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for provisioning resources of a packet network based on collected network performance information |
US8619600B2 (en) | 2006-08-22 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for establishing calls over a call path having best path metrics |
US8199653B2 (en) | 2006-08-22 | 2012-06-12 | Embarq Holdings Company, Llc | System and method for communicating network performance information over a packet network |
US8750158B2 (en) | 2006-08-22 | 2014-06-10 | Centurylink Intellectual Property Llc | System and method for differentiated billing |
US8098579B2 (en) | 2006-08-22 | 2012-01-17 | Embarq Holdings Company, LP | System and method for adjusting the window size of a TCP packet through remote network elements |
US8274905B2 (en) | 2006-08-22 | 2012-09-25 | Embarq Holdings Company, Llc | System and method for displaying a graph representative of network performance over a time period |
US8107366B2 (en) | 2006-08-22 | 2012-01-31 | Embarq Holdings Company, LP | System and method for using centralized network performance tables to manage network communications |
US8407765B2 (en) | 2006-08-22 | 2013-03-26 | Centurylink Intellectual Property Llc | System and method for restricting access to network performance information tables |
US8130793B2 (en) | 2006-08-22 | 2012-03-06 | Embarq Holdings Company, Llc | System and method for enabling reciprocal billing for different types of communications over a packet network |
US8228791B2 (en) | 2006-08-22 | 2012-07-24 | Embarq Holdings Company, Llc | System and method for routing communications between packet networks based on intercarrier agreements |
US8144587B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for load balancing network resources using a connection admission control engine |
US7843831B2 (en) | 2006-08-22 | 2010-11-30 | Embarq Holdings Company Llc | System and method for routing data on a packet network |
US8223654B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | Application-specific integrated circuit for monitoring and optimizing interlayer network performance |
US7889660B2 (en) | 2006-08-22 | 2011-02-15 | Embarq Holdings Company, Llc | System and method for synchronizing counters on an asynchronous packet communications network |
GB2443229B (en) * | 2006-08-23 | 2009-10-14 | Cramer Systems Ltd | Capacity management for data networks |
US7997484B2 (en) | 2006-09-13 | 2011-08-16 | Crane Merchandising Systems, Inc. | Rich content management and display for use in remote field assets |
US7953750B1 (en) | 2006-09-28 | 2011-05-31 | Verint Americas, Inc. | Systems and methods for storing and searching data in a customer center environment |
US7930314B2 (en) | 2006-09-28 | 2011-04-19 | Verint Americas Inc. | Systems and methods for storing and searching data in a customer center environment |
US7991613B2 (en) | 2006-09-29 | 2011-08-02 | Verint Americas Inc. | Analyzing audio components and generating text with integrated additional session information |
US8645179B2 (en) | 2006-09-29 | 2014-02-04 | Verint Americas Inc. | Systems and methods of partial shift swapping |
US8005676B2 (en) | 2006-09-29 | 2011-08-23 | Verint Americas, Inc. | Speech analysis using statistical learning |
US8068602B1 (en) | 2006-09-29 | 2011-11-29 | Verint Americas, Inc. | Systems and methods for recording using virtual machines |
US7873156B1 (en) | 2006-09-29 | 2011-01-18 | Verint Americas Inc. | Systems and methods for analyzing contact center interactions |
US7752043B2 (en) | 2006-09-29 | 2010-07-06 | Verint Americas Inc. | Multi-pass speech analytics |
US7920482B2 (en) | 2006-09-29 | 2011-04-05 | Verint Americas Inc. | Systems and methods for monitoring information corresponding to communication sessions |
US8837697B2 (en) | 2006-09-29 | 2014-09-16 | Verint Americas Inc. | Call control presence and recording |
US20080082654A1 (en) * | 2006-09-29 | 2008-04-03 | Rockwell Automation Technologies, Inc. | Interrogating controllers for alarms and events |
US7570755B2 (en) | 2006-09-29 | 2009-08-04 | Verint Americas Inc. | Routine communication sessions for recording |
US7881216B2 (en) | 2006-09-29 | 2011-02-01 | Verint Systems Inc. | Systems and methods for analyzing communication sessions using fragments |
US7965828B2 (en) | 2006-09-29 | 2011-06-21 | Verint Americas Inc. | Call control presence |
US7899176B1 (en) | 2006-09-29 | 2011-03-01 | Verint Americas Inc. | Systems and methods for discovering customer center information |
US8199886B2 (en) | 2006-09-29 | 2012-06-12 | Verint Americas, Inc. | Call control recording |
US7899178B2 (en) | 2006-09-29 | 2011-03-01 | Verint Americas Inc. | Recording invocation of communication sessions |
US7885813B2 (en) | 2006-09-29 | 2011-02-08 | Verint Systems Inc. | Systems and methods for analyzing communication sessions |
JP4874049B2 (en) * | 2006-10-19 | 2012-02-08 | 株式会社日立製作所 | Mail management method, mail system, and display method in mail system |
US8130925B2 (en) | 2006-12-08 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for recording |
US8280011B2 (en) | 2006-12-08 | 2012-10-02 | Verint Americas, Inc. | Recording in a distributed environment |
US8130926B2 (en) | 2006-12-08 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for recording data |
US8533846B2 (en) | 2006-11-08 | 2013-09-10 | Citrix Systems, Inc. | Method and system for dynamically associating access rights with a resource |
EP2090022B1 (en) * | 2006-11-14 | 2014-01-15 | Telefonaktiebolaget LM Ericsson (publ) | A system and a method relating to network management |
US20090252070A1 (en) * | 2007-01-12 | 2009-10-08 | Connors Dennis P | Airlink management in a wireless broadcast system |
US7912057B2 (en) | 2007-01-12 | 2011-03-22 | Wi-Lan Inc. | Convergence sublayer for use in a wireless broadcasting system |
US8774229B2 (en) | 2007-01-12 | 2014-07-08 | Wi-Lan, Inc. | Multidiversity handoff in a wireless broadcast system |
US8064444B2 (en) * | 2007-01-12 | 2011-11-22 | Wi-Lan Inc. | Wireless broadcasting system |
US7944919B2 (en) * | 2007-01-12 | 2011-05-17 | Wi-Lan, Inc. | Connection identifier for wireless broadcast system |
US7911974B1 (en) | 2007-01-25 | 2011-03-22 | Sprint Communications Company L.P. | Service layer availability |
US8548520B2 (en) | 2007-01-26 | 2013-10-01 | Wi-Lan Inc. | Multiple network access system and method |
US8856326B2 (en) * | 2007-02-01 | 2014-10-07 | Telefonaktiebolaget L M Ericsson (Publ) | Enhanced media control |
US7617337B1 (en) | 2007-02-06 | 2009-11-10 | Avaya Inc. | VoIP quality tradeoff system |
US7796510B2 (en) | 2007-03-12 | 2010-09-14 | Citrix Systems, Inc. | Systems and methods for providing virtual fair queueing of network traffic |
US8631147B2 (en) | 2007-03-12 | 2014-01-14 | Citrix Systems, Inc. | Systems and methods for configuring policy bank invocations |
US9021140B2 (en) * | 2007-03-12 | 2015-04-28 | Citrix Systems, Inc. | Systems and methods for error detection |
US7870277B2 (en) | 2007-03-12 | 2011-01-11 | Citrix Systems, Inc. | Systems and methods for using object oriented expressions to configure application security policies |
US7760642B2 (en) | 2007-03-12 | 2010-07-20 | Citrix Systems, Inc. | Systems and methods for providing quality of service precedence in TCP congestion control |
US7853678B2 (en) | 2007-03-12 | 2010-12-14 | Citrix Systems, Inc. | Systems and methods for configuring flow control of policy expressions |
US8490148B2 (en) | 2007-03-12 | 2013-07-16 | Citrix Systems, Inc | Systems and methods for managing application security profiles |
US8572160B2 (en) * | 2007-03-12 | 2013-10-29 | Citrix Systems, Inc. | Systems and methods for script injection |
US7853679B2 (en) | 2007-03-12 | 2010-12-14 | Citrix Systems, Inc. | Systems and methods for configuring handling of undefined policy events |
US7865589B2 (en) | 2007-03-12 | 2011-01-04 | Citrix Systems, Inc. | Systems and methods for providing structured policy expressions to represent unstructured data in a network appliance |
US8743730B2 (en) | 2007-03-30 | 2014-06-03 | Verint Americas Inc. | Systems and methods for recording resource association for a communications environment |
US8437465B1 (en) | 2007-03-30 | 2013-05-07 | Verint Americas, Inc. | Systems and methods for capturing communications data |
US9106737B2 (en) | 2007-03-30 | 2015-08-11 | Verint Americas, Inc. | Systems and methods for recording resource association for recording |
US8170184B2 (en) | 2007-03-30 | 2012-05-01 | Verint Americas, Inc. | Systems and methods for recording resource association in a recording environment |
US7903604B2 (en) | 2007-04-18 | 2011-03-08 | Wi-Lan Inc. | Method and apparatus for a scheduler for a macro-diversity portion of a transmission |
US8711833B2 (en) | 2007-04-18 | 2014-04-29 | Wi-Lan, Inc. | Base station synchronization for a single frequency network |
US20080263188A1 (en) * | 2007-04-20 | 2008-10-23 | Verizon Business Network Services Inc. | Method and system for monitoring and analyzing of routing in ip networks |
US8315901B2 (en) | 2007-05-30 | 2012-11-20 | Verint Systems Inc. | Systems and methods of automatically scheduling a workforce |
US8111692B2 (en) | 2007-05-31 | 2012-02-07 | Embarq Holdings Company Llc | System and method for modifying network traffic |
US8069251B2 (en) | 2007-06-01 | 2011-11-29 | Adobe Systems Incorporated | System and/or method for client-driven server load distribution |
US8559446B2 (en) * | 2007-06-27 | 2013-10-15 | Blackberry Limited | Signaling architecture for decomposed service network elements operable with IMS |
US8874721B1 (en) * | 2007-06-27 | 2014-10-28 | Sprint Communications Company L.P. | Service layer selection and display in a service network monitoring system |
US8019820B2 (en) * | 2007-06-27 | 2011-09-13 | Research In Motion Limited | Service gateway decomposition in a network environment including IMS |
US8706075B2 (en) * | 2007-06-27 | 2014-04-22 | Blackberry Limited | Architecture for service delivery in a network environment including IMS |
US8959028B2 (en) | 2007-07-02 | 2015-02-17 | Crane Merchandising Systems, Inc. | Apparatus and method for monitoring and control of remotely located equipment |
WO2009007985A2 (en) * | 2007-07-06 | 2009-01-15 | Elitecore Technologies Limited | Identity and policy-based network security and management system and method |
US7969872B2 (en) * | 2007-07-23 | 2011-06-28 | Mitel Networks Corporation | Distributed network management |
US8988995B2 (en) * | 2007-07-23 | 2015-03-24 | Mitel Network Corporation | Network traffic management |
US9591086B2 (en) | 2007-07-25 | 2017-03-07 | Yahoo! Inc. | Display of information in electronic communications |
US8656449B1 (en) * | 2007-07-30 | 2014-02-18 | Sprint Communications Company L.P. | Applying policy attributes to events |
US8559310B2 (en) * | 2007-09-04 | 2013-10-15 | Ca, Inc. | System and method for bandwidth control |
US7856574B2 (en) * | 2007-09-27 | 2010-12-21 | Microsoft Corporation | Internet connectivity evaluation |
US8284664B1 (en) | 2007-09-28 | 2012-10-09 | Juniper Networks, Inc. | Redirecting data units to service modules based on service tags and a redirection table |
US8150820B1 (en) | 2007-10-04 | 2012-04-03 | Adobe Systems Incorporated | Mechanism for visible users and groups |
US8533315B2 (en) | 2007-10-25 | 2013-09-10 | Crane Merchandising Systems, Inc. | Systems and methods for monitoring performance of field assets |
US7778165B2 (en) * | 2007-11-08 | 2010-08-17 | University Of Washington | Information plane for determining performance metrics of paths between arbitrary end-hosts on the internet |
US7738492B2 (en) * | 2007-11-19 | 2010-06-15 | Avistar Communications Corporation | Network communication bandwidth management |
EP2223538B1 (en) | 2007-12-17 | 2016-03-23 | Telefonaktiebolaget LM Ericsson (publ) | Method and arrangement for network qos |
US8104087B2 (en) * | 2008-01-08 | 2012-01-24 | Triumfant, Inc. | Systems and methods for automated data anomaly correction in a computer network |
US8767541B2 (en) * | 2008-02-14 | 2014-07-01 | Qualcomm Incorporated | Scheduling policy-based traffic management |
US8964651B2 (en) * | 2008-02-14 | 2015-02-24 | Qualcomm Incorporated | Traffic management employing interference management messages |
US8737314B2 (en) | 2008-02-14 | 2014-05-27 | Qualcomm Incorporated | Traffic management for multi-hop wireless communication |
US8667175B2 (en) * | 2008-03-13 | 2014-03-04 | Cisco Technology, Inc. | Server selection for routing content to a client using application layer redirection |
US8255536B2 (en) * | 2008-03-21 | 2012-08-28 | Microsoft Corporation | Bandwidth and latency controller |
US8068425B2 (en) | 2008-04-09 | 2011-11-29 | Embarq Holdings Company, Llc | System and method for using network performance information to determine improved measures of path states |
EP2291949B1 (en) * | 2008-04-21 | 2011-10-12 | Telefonaktiebolaget L M Ericsson (PUBL) | Method and system for network fault management |
EP2324615B1 (en) * | 2008-05-21 | 2014-04-02 | McAfee, Inc. | System and method for discovery of network entities |
US8059541B2 (en) * | 2008-05-22 | 2011-11-15 | Microsoft Corporation | End-host based network management system |
US8401155B1 (en) | 2008-05-23 | 2013-03-19 | Verint Americas, Inc. | Systems and methods for secure recording in a customer center environment |
US8898293B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8402111B2 (en) | 2009-01-28 | 2013-03-19 | Headwater Partners I, Llc | Device assisted services install |
US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8548428B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8924469B2 (en) | 2008-06-05 | 2014-12-30 | Headwater Partners I Llc | Enterprise access control and accounting allocation for access networks |
US8340634B2 (en) | 2009-01-28 | 2012-12-25 | Headwater Partners I, Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8346225B2 (en) | 2009-01-28 | 2013-01-01 | Headwater Partners I, Llc | Quality of service for device assisted services |
US8275830B2 (en) | 2009-01-28 | 2012-09-25 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
US8725123B2 (en) | 2008-06-05 | 2014-05-13 | Headwater Partners I Llc | Communications device with secure data path processing agents |
US8406748B2 (en) | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
US8391834B2 (en) | 2009-01-28 | 2013-03-05 | Headwater Partners I Llc | Security techniques for device assisted services |
US8924543B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Service design center for device assisted services |
US8023425B2 (en) | 2009-01-28 | 2011-09-20 | Headwater Partners I | Verifiable service billing for intermediate networking devices |
US8199671B2 (en) * | 2008-06-09 | 2012-06-12 | Hewlett-Packard Development Company, L.P. | Throttling network traffic generated by a network discovery tool during a discovery scan |
US20100064251A1 (en) * | 2008-09-05 | 2010-03-11 | International Business Machines Corporation | Toggling window display state by screen in a multi-screened desktop environment |
US8218751B2 (en) | 2008-09-29 | 2012-07-10 | Avaya Inc. | Method and apparatus for identifying and eliminating the source of background noise in multi-party teleconferences |
WO2010042580A1 (en) * | 2008-10-08 | 2010-04-15 | Citrix Systems, Inc. | Systems and methods for allocating bandwidth by an intermediary for flow control |
US9300532B2 (en) * | 2008-10-24 | 2016-03-29 | Microsoft Technology Licensing, Llc | Automating deployment of service applications by exposing hosting environment constraints |
WO2010056839A1 (en) * | 2008-11-12 | 2010-05-20 | Citrix Systems, Inc. | Tool for visualizing configuration and status of a network appliance |
US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US9858559B2 (en) | 2009-01-28 | 2018-01-02 | Headwater Research Llc | Network service plan design |
US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US10064055B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US10841839B2 (en) | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
US9270559B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
US8606911B2 (en) | 2009-03-02 | 2013-12-10 | Headwater Partners I Llc | Flow tagging for service policy implementation |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
US10484858B2 (en) | 2009-01-28 | 2019-11-19 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8893009B2 (en) | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
US8745191B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
US8793758B2 (en) | 2009-01-28 | 2014-07-29 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
US9253663B2 (en) | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
US8351898B2 (en) | 2009-01-28 | 2013-01-08 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US9755842B2 (en) | 2009-01-28 | 2017-09-05 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
US9647918B2 (en) | 2009-01-28 | 2017-05-09 | Headwater Research Llc | Mobile device and method attributing media services network usage to requesting application |
US9351193B2 (en) | 2009-01-28 | 2016-05-24 | Headwater Partners I Llc | Intermediate networking devices |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US9571559B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners I Llc | Enhanced curfew and protection associated with a device group |
US9578182B2 (en) | 2009-01-28 | 2017-02-21 | Headwater Partners I Llc | Mobile device and service management |
WO2010111667A2 (en) * | 2009-03-27 | 2010-09-30 | Chaz Immendorf | Reducing congestion in a wireless network |
US8719016B1 (en) | 2009-04-07 | 2014-05-06 | Verint Americas Inc. | Speech analytics system and system and method for determining structured speech |
US7957319B2 (en) | 2009-05-08 | 2011-06-07 | Blue Coat Systems, Inc. | Classification techniques for encrypted network traffic |
EP2262173A1 (en) * | 2009-06-10 | 2010-12-15 | Alcatel Lucent | Network management method and agent |
US8654654B2 (en) * | 2009-09-22 | 2014-02-18 | Ixia | Traffic distribution control |
US8369225B2 (en) * | 2009-09-23 | 2013-02-05 | Ixia | Network testing providing for concurrent real-time ingress and egress viewing of network traffic data |
US10115065B1 (en) | 2009-10-30 | 2018-10-30 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US9760866B2 (en) * | 2009-12-15 | 2017-09-12 | Yahoo Holdings, Inc. | Systems and methods to provide server side profile information |
US8239374B2 (en) * | 2010-01-18 | 2012-08-07 | Microsoft Corporation | Collection of performance information for search queries executed in a tiered architecture |
US9020938B2 (en) | 2010-02-03 | 2015-04-28 | Yahoo! Inc. | Providing profile information using servers |
US8448221B2 (en) * | 2010-03-12 | 2013-05-21 | Mcafee, Inc. | System, method, and computer program product for displaying network events in terms of objects managed by a security appliance and/or a routing device |
US8230061B2 (en) * | 2010-03-17 | 2012-07-24 | Microsoft Corporation | Network resource management with prediction |
US9449301B2 (en) * | 2010-05-07 | 2016-09-20 | Alcatel Lucent | Managed object support |
US20120041945A1 (en) * | 2010-08-16 | 2012-02-16 | Salesforce.Com, Inc. | Mechanism for facilitating efficient collection and presentation of business activity monitoring data |
US8904511B1 (en) * | 2010-08-23 | 2014-12-02 | Amazon Technologies, Inc. | Virtual firewalls for multi-tenant distributed services |
US8744367B2 (en) | 2010-08-31 | 2014-06-03 | At&T Intellectual Property I, L.P. | Tail optimization protocol for cellular radio resource allocation |
US8549148B2 (en) | 2010-10-15 | 2013-10-01 | Brocade Communications Systems, Inc. | Domain name system security extensions (DNSSEC) for global server load balancing |
US8726103B2 (en) | 2010-12-07 | 2014-05-13 | At & T Intellectual Property I, Lp | Visual outage management tool |
US8527627B2 (en) * | 2010-12-14 | 2013-09-03 | At&T Intellectual Property I, L.P. | Intelligent mobility application profiling with respect to identified communication bursts |
US8863256B1 (en) | 2011-01-14 | 2014-10-14 | Cisco Technology, Inc. | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US20120191724A1 (en) * | 2011-01-26 | 2012-07-26 | Tucek Joseph A | Storage of data objects based on a time of creation |
US20120215957A1 (en) * | 2011-02-17 | 2012-08-23 | Byungcheol Cho | Semiconductor storage device-based cache storage system |
US8751184B2 (en) * | 2011-03-31 | 2014-06-10 | Infosys Limited | Transaction based workload modeling for effective performance test strategies |
US9154826B2 (en) | 2011-04-06 | 2015-10-06 | Headwater Partners Ii Llc | Distributing content and service launch objects to mobile devices |
WO2012144257A1 (en) * | 2011-04-22 | 2012-10-26 | 日本電気株式会社 | Policy description assistance system and policy description assistance method |
WO2012166927A1 (en) * | 2011-06-02 | 2012-12-06 | Numerex Corp. | Wireless snmp agent gateway |
EP2533152A1 (en) * | 2011-06-08 | 2012-12-12 | Astrium Ltd. | Command and control system integrated with network management |
US9220018B1 (en) | 2011-06-16 | 2015-12-22 | The Boeing Company | Communications quality analysis |
US9264872B2 (en) | 2011-06-20 | 2016-02-16 | At&T Intellectual Property I, L.P. | Controlling traffic transmissions to manage cellular radio resource utilization |
US9220066B2 (en) | 2011-06-20 | 2015-12-22 | At&T Intellectual Property I, L.P. | Bundling data transfers and employing tail optimization protocol to manage cellular radio resource utilization |
US9747583B2 (en) | 2011-06-30 | 2017-08-29 | Yahoo Holdings, Inc. | Presenting entity profile information to a user of a computing device |
US8972569B1 (en) * | 2011-08-23 | 2015-03-03 | John J. D'Esposito | Remote and real-time network and HTTP monitoring with real-time predictive end user satisfaction indicator |
CN102957718B (en) * | 2011-08-23 | 2018-04-03 | 中兴通讯股份有限公司 | The method of User Agreement message synchronization between a kind of service node and service node |
US9130842B2 (en) * | 2011-08-30 | 2015-09-08 | Qatar Foundation | System and method for latency monitoring |
US9094290B2 (en) | 2011-09-09 | 2015-07-28 | Ixia | Measuring and displaying bandwidth contention |
US8615159B2 (en) | 2011-09-20 | 2013-12-24 | Citrix Systems, Inc. | Methods and systems for cataloging text in a recorded session |
EP2772020B1 (en) | 2011-10-25 | 2020-06-10 | Fourth Wall Media, Inc. | Network bandwidth regulation using traffic scheduling |
US8850008B2 (en) * | 2011-11-22 | 2014-09-30 | Verizon Patent And Licensing Inc. | User device application monitoring and control |
US8732291B2 (en) | 2012-01-13 | 2014-05-20 | Accenture Global Services Limited | Performance interference model for managing consolidated workloads in QOS-aware clouds |
US9762634B2 (en) * | 2012-04-06 | 2017-09-12 | At&T Intellectual Property I, L.P. | System and method to transmit digital broadcast grade video via a cellular data network |
US9407443B2 (en) | 2012-06-05 | 2016-08-02 | Lookout, Inc. | Component analysis of software applications on computing devices |
US9003023B2 (en) * | 2012-06-13 | 2015-04-07 | Zscaler, Inc. | Systems and methods for interactive analytics of internet traffic |
US11469914B2 (en) * | 2012-08-10 | 2022-10-11 | Viasat, Inc. | System, method and apparatus for subscriber user interfaces |
US10637760B2 (en) * | 2012-08-20 | 2020-04-28 | Sandvine Corporation | System and method for network capacity planning |
JP2015524237A (en) * | 2012-10-05 | 2015-08-20 | エヌイーシー ラボラトリーズ アメリカ インクNEC Laboratories America, Inc. | Network management |
US8495221B1 (en) * | 2012-10-17 | 2013-07-23 | Limelight Networks, Inc. | Targeted and dynamic content-object storage based on inter-network performance metrics |
US10192200B2 (en) | 2012-12-04 | 2019-01-29 | Oath Inc. | Classifying a portion of user contact data into local contacts |
US9208215B2 (en) * | 2012-12-27 | 2015-12-08 | Lookout, Inc. | User classification based on data gathered from a computing device |
US9258234B1 (en) | 2012-12-28 | 2016-02-09 | Juniper Networks, Inc. | Dynamically adjusting liveliness detection intervals for periodic network communications |
US8953460B1 (en) | 2012-12-31 | 2015-02-10 | Juniper Networks, Inc. | Network liveliness detection using session-external communications |
US20140222997A1 (en) * | 2013-02-05 | 2014-08-07 | Cisco Technology, Inc. | Hidden markov model based architecture to monitor network node activities and predict relevant periods |
WO2014159862A1 (en) | 2013-03-14 | 2014-10-02 | Headwater Partners I Llc | Automated credential porting for mobile devices |
US9584633B2 (en) | 2013-03-15 | 2017-02-28 | Tria Network Systems, LLC | Method and system for managing network communications |
WO2014209900A1 (en) | 2013-06-23 | 2014-12-31 | Intel Corporation | Selective sharing of user information based on contextual relationship information, such as to crowd-source gifts of interest to a recipient |
US9961096B1 (en) | 2013-09-17 | 2018-05-01 | Cisco Technology, Inc. | Distributed behavior based anomaly detection |
US10412007B1 (en) * | 2013-12-13 | 2019-09-10 | Jpmorgan Chase Bank, N.A. | Method and system for determining balanced traffic flows for network capacity planning |
US9379998B2 (en) | 2014-02-07 | 2016-06-28 | International Business Machines Corporation | Symmetric coherent request/response policy enforcement |
US9219658B2 (en) * | 2014-04-14 | 2015-12-22 | Verizon Patent And Licensing Inc. | Quality of service optimization management tool |
US9769017B1 (en) | 2014-09-26 | 2017-09-19 | Juniper Networks, Inc. | Impending control plane disruption indication using forwarding plane liveliness detection protocols |
US9769186B2 (en) * | 2014-12-23 | 2017-09-19 | Mcafee, Inc. | Determining a reputation through network characteristics |
WO2016138400A1 (en) | 2015-02-27 | 2016-09-01 | Cisco Technology, Inc. | System and methods for computer network security involving user confirmation of network connections |
USD794676S1 (en) * | 2015-04-24 | 2017-08-15 | Isaac S. Daniel | Computer screen with icon |
AU2016258533B2 (en) | 2015-05-01 | 2017-11-30 | Lookout, Inc. | Determining source of side-loaded software |
US9940739B2 (en) | 2015-08-28 | 2018-04-10 | Accenture Global Services Limited | Generating interactively mapped data visualizations |
US9578351B1 (en) | 2015-08-28 | 2017-02-21 | Accenture Global Services Limited | Generating visualizations for display along with video content |
US9444703B1 (en) | 2015-11-30 | 2016-09-13 | International Business Machines Corporation | Interconnecting electronic devices for reporting device status |
US10374936B2 (en) | 2015-12-30 | 2019-08-06 | Juniper Networks, Inc. | Reducing false alarms when using network keep-alive messages |
US10447828B2 (en) * | 2016-03-01 | 2019-10-15 | Microsoft Technology Licensing, Llc | Cross-application service-driven contextual messages |
EP3430834B1 (en) | 2016-03-15 | 2021-10-06 | Telefonaktiebolaget LM Ericsson (publ) | Systems and methods for quality of service differentiation for non-ip bearers |
US10397085B1 (en) | 2016-06-30 | 2019-08-27 | Juniper Networks, Inc. | Offloading heartbeat responses message processing to a kernel of a network device |
JP6432947B2 (en) * | 2016-09-12 | 2018-12-05 | ▲ホア▼▲ウェイ▼技術有限公司Huawei Technologies Co.,Ltd. | Data packet processing method, system, and device |
US10594576B2 (en) * | 2017-01-31 | 2020-03-17 | Splunk Inc. | Visualizing network activity involving networked computing devices distributed across network address spaces |
US10462061B1 (en) * | 2017-03-28 | 2019-10-29 | Veritas Technologies Llc | Systems and methods for managing quality of service |
US10218697B2 (en) | 2017-06-09 | 2019-02-26 | Lookout, Inc. | Use of device risk evaluation to manage access to services |
US10949319B2 (en) * | 2018-07-25 | 2021-03-16 | EMC IP Holding Company LLC | Performance monitoring and enhancement |
US11258877B2 (en) | 2018-07-26 | 2022-02-22 | Netapp, Inc. | Methods for managing workloads in a storage system and devices thereof |
US11750441B1 (en) | 2018-09-07 | 2023-09-05 | Juniper Networks, Inc. | Propagating node failure errors to TCP sockets |
US10644954B1 (en) * | 2019-05-10 | 2020-05-05 | Capital One Services, Llc | Techniques for dynamic network management |
US10587457B1 (en) | 2019-05-10 | 2020-03-10 | Capital One Services, Llc | Techniques for dynamic network resiliency |
US10756971B1 (en) | 2019-05-29 | 2020-08-25 | Capital One Services, Llc | Techniques for dynamic network strengthening |
US10574978B1 (en) * | 2019-08-21 | 2020-02-25 | Agora Lab, Inc. | System and method for diagnosing QOE in real time communication |
US11456917B2 (en) * | 2020-06-01 | 2022-09-27 | Cisco Technology, Inc. | Analyzing deployed networks with respect to network solutions |
US20220200924A1 (en) * | 2020-12-21 | 2022-06-23 | Hewlett Packard Enterprise Development Lp | Methods and systems to dynamically prioritize applications over 802.11 wireless lan |
US11451460B1 (en) * | 2021-03-19 | 2022-09-20 | At&T Intellectual Property I, L.P. | Condition-based management of shared mobile edge computing for 5G or other next generation network |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5049873A (en) * | 1988-01-29 | 1991-09-17 | Network Equipment Technologies, Inc. | Communications network state and topology monitor |
US5270919A (en) | 1990-06-04 | 1993-12-14 | At&T Bell Laboratories | Network planning tool |
US5365514A (en) | 1993-03-01 | 1994-11-15 | International Business Machines Corporation | Event driven interface for a system for monitoring and controlling a data communications network |
US5493689A (en) | 1993-03-01 | 1996-02-20 | International Business Machines Corporation | System for configuring an event driven interface including control blocks defining good loop locations in a memory which represent detection of a characteristic pattern |
KR100293920B1 (en) * | 1993-06-12 | 2001-09-17 | 윤종용 | Apparatus and method for controlling traffic of atm user network interface |
US5446874A (en) * | 1993-12-23 | 1995-08-29 | International Business Machines Corp. | Automated benchmarking with self customization |
US5583792A (en) * | 1994-05-27 | 1996-12-10 | San-Qi Li | Method and apparatus for integration of traffic measurement and queueing performance evaluation in a network system |
US5664105A (en) * | 1994-10-04 | 1997-09-02 | Fluke Corporation | Method and apparatus for network analysis |
US5615323A (en) * | 1994-11-04 | 1997-03-25 | Concord Communications, Inc. | Displaying resource performance and utilization information |
US5521907A (en) * | 1995-04-25 | 1996-05-28 | Visual Networks, Inc. | Method and apparatus for non-intrusive measurement of round trip delay in communications networks |
US5867483A (en) * | 1996-11-12 | 1999-02-02 | Visual Networks, Inc. | Method and apparatus for measurement of peak throughput in packetized data networks |
US6097722A (en) * | 1996-12-13 | 2000-08-01 | Nortel Networks Corporation | Bandwidth management processes and systems for asynchronous transfer mode networks using variable virtual paths |
-
1997
- 1997-12-29 US US08/999,517 patent/US6578077B1/en not_active Expired - Lifetime
-
1998
- 1998-12-04 US US09/205,063 patent/US6502131B1/en not_active Expired - Lifetime
- 1998-12-23 WO PCT/US1998/027396 patent/WO1999034544A1/en not_active Application Discontinuation
- 1998-12-23 JP JP2000527050A patent/JP2002500469A/en active Pending
- 1998-12-23 EP EP98966473A patent/EP1050128A4/en not_active Withdrawn
- 1998-12-23 CA CA002316355A patent/CA2316355C/en not_active Expired - Lifetime
- 1998-12-23 AU AU23076/99A patent/AU2307699A/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
EP1050128A4 (en) | 2001-12-19 |
EP1050128A1 (en) | 2000-11-08 |
US6502131B1 (en) | 2002-12-31 |
WO1999034544A1 (en) | 1999-07-08 |
CA2316355A1 (en) | 1999-07-08 |
JP2002500469A (en) | 2002-01-08 |
AU2307699A (en) | 1999-07-19 |
US6578077B1 (en) | 2003-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2316355C (en) | Traffic monitoring tool for bandwidth management | |
US6816903B1 (en) | Directory enabled policy management tool for intelligent traffic management | |
US6137777A (en) | Control tool for bandwidth management | |
US6078953A (en) | System and method for monitoring quality of service over network | |
US6292465B1 (en) | Linear rule based method for bandwidth management | |
US6047322A (en) | Method and apparatus for quality of service management | |
US6119235A (en) | Method and apparatus for quality of service management | |
US6934745B2 (en) | Methods, apparatuses and systems enabling a network services provider to deliver application performance management services | |
US6341309B1 (en) | Firewall system for quality of service management | |
US6459682B1 (en) | Architecture for supporting service level agreements in an IP network | |
WO2000035130A1 (en) | Directory enabled policy management tool for intelligent traffic management | |
US6681232B1 (en) | Operations and provisioning systems for service level management in an extended-area data communications network | |
US8595787B2 (en) | Dynamic service delivery platform for communication networks | |
US6466984B1 (en) | Method and apparatus for policy-based management of quality of service treatments of network data traffic flows by integrating policies with application programs | |
Räisänen | Implementing service quality in IP networks | |
Menth | Efficient admission control and routing for resilient communication networks | |
Xiao et al. | A practical approach for providing QoS in the Internet backbone | |
Joseph et al. | Deploying QoS for Cisco IP and next generation networks: the definitive guide | |
Wang et al. | Experimental QoS performances of multimedia applications | |
Borella et al. | Pricing framework for a differential services Internet | |
Rayes et al. | Integrated management architecture for IP-based networks | |
Wang | USD: Scalable bandwidth allocation for the Internet | |
Guirguis et al. | Providing soft bandwidth guarantees using elastic TCP-based tunnels | |
Gunantara et al. | Improving Internet Network Performance through Bandwidth Management | |
Jena et al. | Resource Engineering for Internet Applications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKEX | Expiry |
Effective date: 20181224 |