Linear rule based method for bandwidth management

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

BACKGROUND OF THE INVENTION

The present invention relates to communication or telecommunication. More particularly, the present invention provides a technique, 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 Internet. But it would be recognized that the present invention has a much broader range of applicability including local area networks, a combination of wide and local area networks, and the like.

Telecommunication techniques have been around for numerous years. In the early 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 seen over a limited range of geographical distances, they were soon replaced by a communication technique known as telegraph. Telegraph generally transferred information from one geographical location to another geographical location using electrical signals 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, replaced by telephone. The telephone was invented by Alexander Graham Bell in the 1800s to transmit 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 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 a novel traffic control technique using, for example, a linear rule-based process. The present control technique is predominantly software based, but is not limited to such software in some embodiments.

In a specific embodiment, the present invention provides a novel method of setting a quality of service (“QoS”) policy for a bandwidth management tool. The present method uses steps of providing a flow of information to a gateway from an incoming source from a network of computers. The flow of information has at least a first group of information and a second group of information. At least one of a plurality of policies is applied to the first group of information to manage flow of the first group through the gateway. A further step of allowing the second flow to traverse through the gateway substantially free from any application of any one of the plurality of policies also is included. By way of classifying and managing the information in this manner, the present method is more efficient than conventional techniques.

In an alternative embodiment, the present invention provides yet an alternative novel method of managing information in a network of computers. The present method includes a step of providing a flow of information to a gateway, where the flow of information has a plurality of information packets. The packets include at least a first portion to be managed and a second portion to be unmanaged. In most cases, the flow of information originates or is derived from an incoming source. The flow of information is classified into at least the first portion and the second portion. The present method applies a policy to the first portion to control the first portion before transferring the first portion to a link, and transfers the second portion substantially free from any application of any policy to the link.

In still a further embodiment, the present invention provides a system for managing information in a network of computers. The system has computer memory using a variety of computer codes to form software or a computer program. The program has at least a first code directed to separating a flow of information from a gateway into a first portion and a second portion. A second code is directed to applying a policy to the first portion to manage or control the first portion before transferring the first portion to a link. The memory also has a third code directed to transferring the second portion substantially free from any application of any policy to the link. The memory also includes a variety of other codes to perform the methods or processes described herein and others.

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 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;

FIG. 9 is a simplified tree diagram of a rule-based control method based upon hierarchy according to the present invention; and

FIGS. 10-13 are simplified diagram of a linear rule-based control method 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 controlling traffic for bandwidth management, as well as other functions, using a rule based technique, for example.

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 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 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 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.

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.

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 definitions 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.

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 TrafficWare™ 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.8 kbit 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 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 Requirements
Users	Bandwidth	Service Offered
Internet developers, individuals,	28.8 to	Dial-up services,
international locations where	56 Kbps	ISDN
bandwidth is expensive
Small to medium-sized organizations	56 Kbps to	Fractiona TI,
with moderate Internet usage	1.5 Mbps	frame relay
Medium sized organizations with	1.5 Mbps	Dedicated TI circuit
many moderate users, smaller
organizations requiring huge
amounts of bandwidth
Standard bandwidth for	10 Mbps	Ethernet, token ring
Ethernet-based LANS		(4 Mbps or
		16 Mbps)
Bandwidth usage for large	45 Mbps	Dedicated T3
organizations or Internet		circuit
backbones
Huge bandwidth LAN backbone	100 to	Fast Ethernet,
usage for medium to large	1.000 Mbps	gigabit Ethernet
organizations (hundreds or
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

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.

TABLE 2
Application Spectrum
Application Class                Examples
Low-bandwidth, delay             DNS, PING, TELNET,
sensitive, highly interactive    CHAT, COLLABORATION
High bandwidth, delay sensitive  Real-time audio and video
High Bandwidth, nominally interactive Web service requests, file
                                 downloads
Non-interactive                  Mail and news

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 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	Mission critical	Needs most bandwidth to deal
support		with customers who need
		assistance
Sales and	Critical	Needs bandwidth to deal with
marketing		potential customers. Answer
		inquires, make quotes, transmit
		multimedia presentations
Upper management	Casual	Needs bandwidth to perform
and middle manage-		tasks necessary to run the
ment, administrative		business
Development and	Personal	Needs bandwidth to send e-mail,
manufacturing		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 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 Ring. A physical layer 209 is disposed above the network layer 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™ from Intel Corporation, but is not limited to such a computer or processor. An operating system (“OS”) is used on the computer such as WindowsNT™ from Microsoft Corporation, but can also be other 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 directory services is described in U.S. application Ser. Nos. 08/998,100 and 08/998,313, both of which were filed on Dec. 24, 1997, and both of which are commonly assigned, and hereby incorporated by reference for all purposes.

Directory services 224 and GUI 201 couple to an application programming interface (“API”) 223 . The API is coupled to a traffic management or bandwidth management tool 208 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 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 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 simplified 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 tool 405 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 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 705 A, E, D, C, and the present tool 703 A, E, D, C, which is coupled between the router and the hub (“HQ”). In a WAN-based environment, for example, HQ 701 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 tool 703 B also sits by the Internet 711 and is used to allocate bandwidth between the competing children, e.g., Frankfurt, London, Hong Kong, Paris. Router 705 B is coupled between tool 703 B 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 FMR 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 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 defines specific limitations or parameters for the traffic.

Some definitions about the various modules have been described above. These definitions 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 WindowsNT™ 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 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;

Setting priorities—establishing a priority order for bandwidth limiting or servicing traffic from a class. (That is, high priority classes are serviced first and are affected the least during contention for bandwidth. 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 designated 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 interface. The present tool user interface is described in, for example, U.S. Application No. 60/067,857 filed Dec. 5, 1997 (Attorney Docket No. 18430-000300, commonly assigned, which is hereby incorporated by reference for all purposes.

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. 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.

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%). 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.

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 defining 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 defined 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 time 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 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.

FIG. 9 is a simplified tree diagram 900 of a rule-based control method based upon hierarchy according to the present invention. This tree diagram is merely an illustration and should not limit the scope of the claims. A hierarchical model is represented as the tree diagram 900 , with the “root” representing the total available bandwidth (i.e., 100%) 901 , each “branch” node representing aggregated traffic (e.g., meta-traffic classes), which can include a marketing subnet 903 and other subnets 905 . “Leaves” represent individual connections (or traffic classes), which can include HTTP 907 , FTP 909 , e-mail 911 , and others 913 . Each of the nodes has a number that represents the total bandwidth allocated for the node. For example, the total available bandwidth at node 901 is 100%. The marketing subnet 903 is allocated 60% of the bandwidth and the other subnets 905 are allocated 40% of the bandwidth. Within the marketing subnet 903 , HTTP 907 is allocated 25% and FTP is allocated 35% of the total available bandwidth. Other subnets 905 allocate 30% of available bandwidth to e-mail 911 , and others 913 is allocated 10% of available bandwidth. Each of the traffic classes coupled to connection 915 , which transfers the information to a link or user location.

This model gives the user flexibility in defining and implementing a service policy or multiple service policies. For example, the network traffic can be divided in different ways and then the specific policy refined from a top down approach or amalgamated from a bottom up approach. This model also provides the user with different methods for different traffic classes since it abstracts the policy definition from the enforcement or implementation.

In the present embodiment, the user typically has competing factors to consider when determining a network QoS policy, including at least bandwidth “guarantees”, latency “guarantees”, and exception control. It should be understood “guarantees” refer to best efforts of the system to provide service, and does not in any way imply an absolute guarantee of service. For example, obviously no service can be provided or guaranteed if the network connection is inoperative, if the Internet Service Provider (ISP) has hardware or software glitches, or there is a general Internet crash.

One factor is bandwidth guarantee, or data throughput guarantee, and how excess bandwidth is shared. For traffic classes that have data intensive requirements this is an important criteria. Typically, the user initially determines what are the minimum bandwidth guarantees that are given for different traffic classes or for connections relying on data from the different traffic classes, before determining a policy. As result of the policy, the system monitors the actual bandwidth provided to different classes, and preferably if bandwidth is critically low, the system attempts to provide at least the minimum bandwidth to the different traffic classes. Typically, the user also initially determines how excess bandwidth is allocated. In a hierarchical model, the user provides bandwidth sharing by classes ‘passing up’ or ‘receiving’ unused bandwidth via their ‘parents’. As a result, closer siblings (traffic classes) typically are able to share more bandwidth than distant traffic classes. Alternatively, the user may decide that all leaf classes are allowed to utilize excess bandwidth simply based on their priority.

Another factor is latency guarantees, or response time guarantees. For traffic classes that are sensitive to delays this is an important criteria. Typically latency is determined by the end-end route rather than the local network or any single gateway. The user typically first determines what are the maximum latency guarantees that are given for different traffic classes, before determining a policy. In response to the policy, the system monitors the bandwidth provided to different classes and if a particular traffic class requires a quicker response, the system attempts to provide more bandwidth for that traffic class. This monitoring occurs preferably when the network is idle or when the network is congested.

Still a further factor is exception control. The system preferably implements exception control when the bandwidth link capacity is being exceeded (e.g., congestion) or when a traffic class is attempting to exceed it's allotted capacity. Initially, the user typically determines what actions to perform when there are exceptions, some actions include: admission control (e.g., deny new requests), service degradation (e.g., dropping packets), sources throttling, traffic redirection (load sharing), and the like. Exception control is preferably a function of traffic type and policy. For example, the user may determine that real-time video requires a steady bit-rate and thus requires admission control as an exception policy when the bandwidth is low, and the user may determine that bulk file download services (which are weakly interactive) may accommodate some new requests thus instruct the system to throttle the download sources when the bandwidth is low.

The user is preferably provided with at least three properties: bandwidth intensive, real-time and/or interactive, which are useful in describing meaningful policies for the different traffic classes. Bandwidth-intense traffic classes typically require relatively large transmission rates (e.g., >50 kbps) for each connection over short or long intervals to maintain reasonable quality. Interactive classes typically require a low latency for all packets to maintain a good response time. Real-time classes typically require a very steady rate of data delivery (high or low) and generally also low latency. These three properties or combinations of them can also be thought of as describing generic (i.e., base) classes of traffic.

The present embodiment uses hierarchy in allocating bandwidth for a class of traffic. In some embodiments, the present method is quite useful in ensuring that the most important or critical traffic gets through the network. This embodiment, however, often relies upon a recurring process that attempts to ensure that the amount of bandwidth being allocated to a class falls within the bandwidth limits or percentages. This process can take additional time in some cases. Accordingly, the present invention also provides a substantially linear process based upon exclusionary rules to set a policy for managing a class of traffic over the network.

In a specific embodiment, FIGS. 10-13 shows simplified diagrams of a linear rule-based control methods according to the present invention. These diagram are merely examples and should not limit the scope of the claims herein. Additionally, the present control methods can occur by way of a control software tool, for example, using a software module or the like. Before proceeding to the examples, however, it may assist the reader to revisit terms used to describe the present control process. For instance, “rules” are used for setting up traffic classes and traffic policies that apply to them. A traffic rule or the rule includes at least a specified class and policy applied to the class. “Traffic Classes” are specific combinations of hosts, applications or files that the user may want to measure or control. Classes can be as general (e.g., all services for all servers) or specific, e.g., a type of HTTP file from a given URL sent to a particular workstation. “Policies” specify at least bandwidth controls, priorities, and session admittance conditions. A policy can be defined to either a measure or control at a specified time period such as time of day, day of week, date of month, and others.

According to an embodiment of the present invention, flow control of information occurs in a linear manner 1000 , such as the linear processes illustrated by FIG. 10 , for example. As shown, the information including a traffic class enters a process at a gateway, for example, and goes through one or more linear processes A, B, C, and D, which are illustrated by functional blocks 1001 , 1003 , 1005 , and 1007 , for example. These functional blocks perform an operation or operations on the class of traffic depending upon a variety of factors such as the specific type of traffic class, the time of day, available bandwidth, competing traffic classes, and other factors. Rather than allocating bandwidth depending upon a hierarchy model, such as the one previously noted, the present control tool performs a process in a linear or non-recursive manner.

As merely an example, FIG. 11 shows a simplified flow diagram 1100 of a process for controlling or managing a flow of information according to the present invention. The process begins at step 1101 . Step 1101 provides a system including a network of computers, such as the ones previously noted, but are not limited to such network of computers. A flow (step 1103 ) of information is provided at, for example, a gateway such as a firewall server or the like. The present process or tool can sit at the gateway including the firewall server. The information can include, among others, data or packets. The present method classifies (step 1105 ) 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 defined 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 1105 classifies the flow of information received into one of a plurality of predetermined classes.

In the present embodiment, the predetermined classes separate or divide into at least two classes. The flow of information separates into a class to be managed 1107 and a class that is not managed 1109 , which is substantially free from any application of a policy. The present method or tool applies a predetermined policy 1111 to the information to be managed. The policy is based, in part, upon predetermined policy settings. As merely an example, the policy can specify bandwidth controls or allocate bandwidth, priorities, and session admittance conditions. The policy also can be applied to the information to be managed at a specified time period such as time of day, day of week, date of month, and others. The managed flow of information goes to a link 1115 or a user site.

Information to be unmanaged also goes to link 1115 or the user site. The unmanaged information goes through decision block 1113 and branch 1117 to link 1115 . In some embodiments, the information to be unmanaged is managed, as shown by branch 1119 , which applies policy 1111 to the information to be unmanaged. In these embodiments, the information to be unmanaged takes the managed route if the unmanaged information begins to influence the flow of managed information or flow of information to be managed, as shown by decision block 1113 . If the information to be unmanaged goes to step 1111 through branch 1119 , it transfers to link 1115 in similar fashion as the managed information.

By way of allowing information to be unmanaged, the present method only applies policy to a class of information to be managed. This method simplifies programming and control of the class of information. As merely an example, FIG. 12 illustrates some simplified examples 1200 of high level language used to control the flow of information in an exclusionary manner, which is non-recursive. Control is generally provided in a manner that goes from more specific to more general 1201 to ease information flow. For example, control is given by the representation “ALL SUBNET EXCEPT HTTP, FTP, AND E-MAIL” 1203 . This allows all information for the subnet to flow through the node except information classified as HTTP, FTP, and E-MAIL. The logic of the representation is easy to understand by the user and allows for an efficient control of the flow of information. Other expressions 1203 are also shown in the Fig.

In an alternative embodiment, the present tool also provides a method for creating rules according to the present invention, as shown by the simplified flow diagram 1300 of FIG. 13 . This flow diagram is merely an illustration and should not limit the scope of the claims herein. The method begins at step 1301 . A rule is created 1303 using an interface tool, such as the one described in U.S. Application Serial No. 60/067,857 filed Dec. 5, 1997. The rule generally specifies at least the class of traffic and at least a policy. The rule takes into account the class of traffic, time of day, and other factors, which were previously described, as well as others. The rule is verified (step 1305 ) according to defined policies to be consistent in terms of bandwidth allocated, classes defined, and time slots. Additionally, the method validates (step 1307 ) the created traffic rule in context to previously existing rules so that conflicting or ambiguous rules are not created. Once the rule has been verified according to policies and validated according to other rules, the rule is saved, step 1309 . Other rules for other classes of traffic are made in a similar fashion. These rules are used in, for example, the flow diagrams shown above, but can also be others.

Additional examples of creating policies and implementing rules are described in U.S. Application Serial No. 60/067,857 (Attorney Docket No. 18430-000300), which is hereby incorporated by reference of all purposes. These examples are implemented in an easy to use graphical user interface, which is on a computer monitor or display. Of course, the type of interface used depends upon the application.

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 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.

Claims

1. A method for managing a flow of information in a computer system, said method comprising:providing a flow of information to a gateway from one or more sources from a network of computers, said flow of information comprising a first group of information being of a first one of a plurality of traffic classes and a second group of information being of a second one of a plurality of traffic classes; applying one of a plurality of policies to said first group of information to manage flow of said first group of information through said gateway; and allowing said second group of information to traverse through said gateway substantially free from any application of any one of said plurality of policies.

2. The method of claim 1 wherein said step of allowing occurs in a normal mode.

3. The method of claim 1 wherein said gateway comprises a firewall, said firewall further comprising directory services.

4. The method of claim 1 wherein said gateway is a firewall.

5. The method of claim 1 wherein said steps of applying and allowing are linear.

6. The method of claim 1 wherein said step of applying further comprises the step of prohibiting said first group of information to flow through said gateway.

7. A method of managing information in a network of computers, said method comprising:providing a flow of information to a gateway, said flow of information comprising a plurality of packets, said packets being of a first traffic class to be managed or a second traffic class to be unmanaged, said packets coming from one or more incoming sources; classifying said packets into said first traffic class creating a first set of packets and into said second traffic class creating a second set of packets; applying a policy to said first set of packets to control said first set of packets before transferring said first set of packets to a link; and transferring said second set of packets substantially free from any application of any policy to said link.

8. A system for managing a flow of information in a network of computers, said system having a computer memory comprising:a first code directed to separating a flow of information to a gateway into a first group of information being of a first one of a plurality of traffic classes and a second group of information being of a second one of a plurality of traffic classes; a second code directed to applying a policy to said first group of information to manage said first group of information before transferring said first group of information to a link; and a third code directed to transferring said second group of information substantially free from any application of any policy to said link.