Title of Invention: Method and apparatus for quality of service management
Abstract: A novel method for a network of computers to improve quality of services using a combination of a bandwidth management tool in a firewall. The method includes the steps of providing a network directory services server providing network directory services to a plurality of network servers, each of the plurality of network servers coupled to one of the plurality of network quality of service devices, implementing a quality of service policy for the plurality of network quality of service devices on the network directory services server, and using the network directory services to provide configuration information for the plurality of network quality of service devices, in response to the quality of service policy.
Detailed Description: Part PAC: DESCRIPTION OF SPECIFIC EMBODIMENTS
Part PAR: An embodiment of the present provides integrated network service policies for firewall platforms. 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 for network servers administered utilizing Directory Service services.
Part PAR_2: Network QoS is managed 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.
Part PAC_2: DEFINITIONS
Part PAR_3: Firewall: A type of security mechanism for controlling access between a private trusted network and an untrusted outside network (which might be the public Internet or some other part of the corporate network within an intranet). It typically includes software running on general purpose or specialized hardware.
Part PAR_4: LDAP: Lightweight Directory Access Protocol, a proposed directory protocol standard.
Part PAR_5: DS: Directory Services are global, distributed information databases that provide access to network resources, regardless of physical location. Such directory services are preferably Novell Directory Services, Microsoft's Active Directory Services (AD), LDAP and other directory services provide central points of administration for entire networks of networks. DS typically maintain information about every resource on the network, including users, groups, printers, volumes, and other devices. This information is typically stored on a single logical database, thus, instead of logging onto many individual file servers, users and network administrators log onto the network preferably only once.
Part PAR_6: Trusted network: Users on this network are, by default, deemed to be trustworthy. Users may be physically on a common network, or linked together via a virtual private network (VPN).
Part PAR_7: DMZ: The `Demilitarized Zone` lies outside the perimeter defenses provided by the firewall but contains systems that are owned by a private organization. Common examples would be Web servers and anonymous ftp servers providing information to Internet users.
Part PAR_8: Untrusted network: These are outside networks of various kinds, among the many thousands of networks connected to the Internet, or even untrusted networks that may be part of other departments or divisions within an organization.
Part PAC_3: I. SYSTEM OVERVIEW
Part PAR_9: FIG. 1 illustrates a typical system 100 including 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 is embodied as an TrafficWare.TM. 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.
Part PAR_10: 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.
Part PAR_11: FIG. 2 is a simplified block diagram of a firewall server 300 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. Firewall server 300 typically includes, among other elements, a monitor 310, a computer 320, a keyboard 330, a graphical input device 340, and a network interface 350. Computer 320 includes familiar computer components such as a processor 360, and memory storage devices, such as a random access memory (RAM) 370, a disk drive 380, and a system bus 390 interconnecting the above components. A external network connection 400 and an internal network connection 410 are coupled to network interface 350.
Part PAR_12: A mouse is but one example of graphical input device 340, also known as a pointing device, a trackball is another. RAM 370 and disk drive 380 are examples of tangible media for storage of computer programs such as embodiments of the herein described invention. Other types of tangible media include floppy disks, removable hard disks, optical storage media such as CD-ROMS and bar codes, semiconductor memories such as flash memories, ASICs, read-only-memories (ROMS), battery-backed volatile memories, and the like. External network connection 400 typically provides access to external networks such as LAN 180 or Internet 200, as described in FIG. 1. Internal network connection 410 typically provides access to internal networks such as LAN 160.
Part PAR_13: In a specific embodiment, firewall server 300 includes a IBM PC compatible computer having a '586-class based microprocessor, such a Pentium.TM. from Intel Corporation, running WindowsNT.TM. from Microsoft Corporation, and TrafficWare.TM. software from Ukiah Software, Inc. Network interface 350 is preferably embodied as a hardware firewall server also from Ukiah Software, Inc., but can be others.
Part PAR_14: FIG. 2 is representative of but one type of system for embodying the present invention. It will be readily apparent to one of ordinary skill in the art that many system types and software configurations are suitable for use in conjunction with present invention. The present invention can be in the form of software in one embodiment. Alternatively, the present invention can be a combination of hardware and software, which can be further combined or even separated. Of course, the particular type of system used in the present invention depends highly upon the application.
Part PAC_4: II. OUTBOUND CONTROL
Part PAL: 1. Traffic Classes
Part PAR_15: An embodiment of the present invention discriminates between traffic classes or traffic types. For example, between application/protocol (e.g., HTTP, SMTP, FTP, Telnet), data-type (e.g., MIME type, HTML, JPEG, RealAudio, .WAV, .MOV), source/destination identifier (e.g., IP address, user name, domain, URQ), type (real-time, interactive, throughput-intense), direction (inbound/outbound), and the like. Further traffic classes are based upon specifics user (e.g. President, Shipping Clerk, etc), business group (e.g. Sales, Engineering, Accounting, etc.), priority (e.g. user-determined priority levels), direction (e.g. inbound, outbound, customer, guest, etc.).
Part PAR_16: FIG. 3 illustrates an example of a hierarchical model for determining bandwidth sharing. This model is merely an illustration and should not limit the scope of the claims herein. As illustrated in FIG. 3, a hierarchical model is represented as a tree, with the root representing the total available bandwidth, each branch node representing aggregated traffic (meta-traffic classes), and the leaves representing individual connections (traffic classes). This model gives the user flexibility in defining and implementing a service policy or multiple service policies. For example, the network traffic is first 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.
Part PAR_17: The user typically has competing factors to consider when determining a network QoS policy, including 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.
Part PAR_18: A first 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.
Part PAR_19: 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.
Part PAR_20: A second 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.
Part PAR_21: A third factor is exception control. The system preferably implements exception control when the bandwidth link capacity is being exceeded (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.
Part PAR_22: The user is preferably provided with 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 (&gt;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 (base) classes of traffic.
Part PAR_23: FIG. 4 illustrates a table summarizing some basic TCP/IP traffic classes and typical policies that are applied to them. Traffic classes such as HTTP, HTML, GIF, JPEG, RealAudio, Realtine Video, SMTP, NNTP, FTP, TELNET, DNS, RPC, Novell NCP are shown. To these classes, a base class is given. Applied policy and exception control are also provided, for example. Other combinations or assignments of the above policies may be made in alternative embodiments of the present invention. Further, in FIG. 4, `P` represents dependence upon a specific policy implemented by the user.
Part PAL_2: 2. Packet Scheduling
Part PAR_24: The system allocates output bandwidth per traffic class preferably by using a class of scheduling methods referred to as fair queuing algorithms at the firewall. These algorithms model traffic as weighted flows and attempt to ensure that service is given to all flows (traffic classes) in proportion to their assigned minimum bandwidth. Service typically occurs in a round robin fashion while monitoring the maximum delays. The system preferably combines such methods with priority based schedulers in order to provide latency guarantees. These types of outbound flows systems typically apply localized control over all time intervals, are generally efficient to implement, provide good link utilization, and do not depend on protocol or connection semantics.
Part PAR_25: Outbound flow control as described above is preferably combined with TCP/IP rate control, described below.
Part PAC_5: III. SOURCE CONTROL
Part PAR_26: In an embodiment of the present invention, rate control policies are specified in the form of a bandwidth allocation hierarchy, as described above, that defines aggregates of traffic according to user-specified parameters (e.g., application type, MIME type or source/destination ID). Further, classes are either guaranteed or best-effort.
Part PAR_27: As described above, inbound flows may have guaranteed classes that include a minimum reserved rate per connection and preferably have limits on the total bandwidth used or number of simultaneous guaranteed connections. Preferably, the remainder of the bandwidth, including any excess from the guaranteed classes, is dynamically allocated to `best-effort` classes, and new best-effort connections. The specific allocation and policy are user definable. In the preferred embodiment, classes that flow above their rate limits are subject to rate control preferably if there is demand from siblings, either in the form of new connection requests.
Part PAC_6: IV. TCP/IP FLOW CONTROL
Part PAR_28: Flow control behavior refers to having end-points adjust their transfer rates in response to congestion indicators or under gateway control. This applies to both inbound and outbound traffic. In the preferred embodiment, the end-points implement TCP/IP.
Part PAR_29: TCP flow control uses the concept of "window size" to enable a receiver end-point to indicate how much data the source end-point can send in a burst at any given time. To do this, the receiver transmits a window size limit to the source. TCP utilizes timeouts and duplicate acknowledgment signals (ACKs) to initially determine network congestion, and then utilizes the concept of window size as a tool to prevent and respond to the congestion, To do all this accurately and efficiently, TCP uses a half-dozen subtly intertwined algorithms. Congestion control is done reactively and coarsely and typically involves long delays and retransmitted traffic on the network. ACKs are used to avoid overall network collapse.
Part PAR_30: In an embodiment, a gateway at the route bottleneck (e.g., the Internet access line) is used to invoke this window size flow control mechanism in a proactive manner by screening bandwidth use and updating the sources. Typically, control applies over relatively large time scales (typical Internet round-trip times).
Part PAR_31: In alternative embodiments of the present invention, ICMP Source Quenching can also be used to serve as a flow control mechanism. ICMP Source Quenching is an IP mechanism typically invoked by routers to indicate buffer overflow. BSD based TCP/IP stacks will effect a sharp backing off of TCP data traffic bursts on receipt of such ICMP packets.
Part PAR_32: To achieve control over inbound traffic, the present invention invokes flow control at the source to spoof window size packets. This technique is also applied as a high-level control over the outbound fair scheduler in order to control congestion preferably when traffic is not subject to admission control. Further, a fair scheduler for inbound communications is used to identify which classes may need to be controlled at the source.
Part PAR_33: FIG. 5 illustrates a block diagram of a flow chart according to a preferred embodiment. Initially, a TCP connection request (SYN) is classified into the user-specified class hierarchy, step 500. A connection is fully classified if it can be assigned to a leaf node. The connection is partially classified if it cannot be uniquely assigned to a non-leaf node. A connection may not be fully classified until the arrival of the first request-data packet.
Part PAR_34: Next, during connection setup, the round-trip-time (RTT) of the connection is estimated, step 510. The RTT is typically not reliably measured during windowed data flow at a gateway without probe packets or routing information. Thus, the present method typically does not depend on accurate measures of RTT but rather is driven by a nominal value from the first estimate.
Part PAR_35: At any given time, the available response-data bandwidth is partitioned to all existing connections within a class proportionally. The available bandwidth is updated upon each new admitted connection (SYN or SYN&DATA) and each terminated connection (FIN). If there are guaranteed rates for each connection, the system may disallow new connections during request-data phase or allow new connections as a best-effort class.
Part PAR_36: The source is then allowed to ramp up the source flow according to application requirements and TCP flow control, step 520. This flow is monitored by monitoring ACKs flowing in the return direction. During this phase, the system also estimates the bottleneck link speed for the connection. As a result, the minimum inter-ACK, back-to-back ACKs, or inter-data packet time observed is determined, step 530, which gives a lower bound on link speed. This speed is typically used to adjust and reallocate source bandwidth among sibling connections preferably if the available rate is greater than the link speed.
Part PAR_37: In a preferred embodiment, on each data ACK, the available response bandwidth and actual utilization over the life of the connection is translated into a limit window size for the next RTT, step 540. In an alternative embodiment, fair queuing at all leaf nodes and the use limiting queue lengths are used to calculate window sizes. A limit window increase is scaled to a multiple of the segment size to emulate receiver silly-window avoidance.
Part PAR_38: If the connection ramps above the assigned source flow (or the emulated fair queue grows too large), step 550, the window sizes are preferably modified with each response ACK as follows, step 560: EQU If (wsender&gt;wmax) {w=MAX(wmax, MSS); if (a+w&lt;eprev ) {w=eprev-a} else {eprev=e }; send-ack(a,w)}
Part PAL_3: Where MSS=Max.segment size; eprev=Window right edge sequence# advertised in previous ACK; wsender=Window advertised by the sender; a=ACK sequence #; wmax=Window size limit; and w=sent window.
Part PAR_39: The above rate control method is efficient to implement, follows TCP semantics (including silly window avoidance and window updates), and "guarantees" a minimum bandwidth (MSS/RTT) to a connection without use of any timing or queuing mechanisms. The method is extendable to provide arbitrarily small bandwidth limits using a timing or queuing mechanism to send a window update preferably as follows: EQU If (wmax&lt;MSS) {set.sub.-- timer(RTT*MSS/wmax)} timer: w=MSS; send.sub.-- ack(a,w)
Part PAR_40: The above equations are merely exemplary, it should be understood that many variations in the above equations can be made in light of the teaching above are such variations are contemplated in alternative embodiments of the present invention. In the preferred embodiment, to compensate for the effects of TCP slow-start, a connection sends up to 25% over limit over any RTT.
Part PAR_41: FIG. 6 illustrates a state transition diagram for a preferred embodiment of the present invention. FIG. 6 illustrates the role of traffic class and policy in the preferred embodiment of the present invention. Typically, when a traffic class for a connection is not recognized, when exception conditions are in place, and other situations, a connection is not admitted, state 600. If a connection is admitted, state 610, data can then begin to flow, state 620.
Part PAR_42: FIG. 6 further illustrates how typically TCP flow is not inhibited when the round-trip-time does not exceed the flow limits, state 620, and how typical TCP flow is inhibited when the round-trip-time exceeds the flow limits, state 630. In the former case, the ACK signal is typically not inhibited, whereas in the latter case, the ACK signal is inhibited, or delayed.
Part PAR_43: FIG. 7 illustrates an implementation architecture of a preferred embodiment of the present invention. Other embodiments of the present invention may be applied with other techniques for QOS or bandwidth management.
Part PAC_7: V. APPLICATIONS
Part PAR_44: The embodiments described above are preferably used to address current and future technological changes and requirements.
Part PAR_45: For example, the embodiments of the present invention provide resource management for ever increasing traffic, i.e. scalability. Scaling refers to the growing (and often indeterminate) body of users having widely varying access speeds that compete for the same resources, for example bandwidth. Scaling is adversely affected by the growing volume of available content (e.g. HTML pages), by the falling costs of CPUs, and trends towards network computers. By providing QoS management, as described above, management of increasingly scarce resources (bandwidth) is facilitated.
Part PAR_46: Further, the embodiments of the present invention provide resource management to respond to Business priorities. Business use of the Internet typically ranges from casual use to business critical use. As secure Internet business applications continue to develop, providing service quality for these core business functions over casual use will be a high priority (e.g., the quality of external access of a customer to an order entry web page. By providing QoS management as described above, Business-oriented or other priority traffic is facilitated.
Part PAR_47: Also the embodiments of the present invention provide resource management to respond to different traffic types. As different types of content application increase and standards continue to emerge and evolve, different types of Internet traffic may require specific service guarantee. For example, different applications may require different bandwidth, e.g. intensive, real-time, interactive, and the like. By providing QoS management as described above, bandwidth critical traffic is facilitated.
Part PAR_48: The embodiments of the present invention described above preferably provide a symmetrical, solution for gateway control of inbound and outbound traffic over the Internet, with the basic methods (queuing and source TCP rate control) designed to complement each other.
Part PAC_8: VI. DIRECTORY SERVICES
Part PAR_49: FIG. 8 illustrates a more detailed embodiment of the present invention. FIG. 8 includes a number of firewall/quality of service (QOS) servers 770, each preferably coupled to at least one respective trusted network. The trusted networks include IPX based networks 780, and IP based networks 790. A directory services (DS) server 700, and a plurality of untrusted networks 710 are also illustrated.
Part PAR_50: As shown in FIG. 8, the trusted networks, including IPX based network 780 and IP based network 790 preferably communicate with untrusted networks 710 and each other through respective firewall/QOS servers 700. Typical firewall/QOS servers are based upon servers having operating systems such as WindowsNT from Microsoft Corporation, NetWare or Intranet Ware from Novell Corporation, proprietary hardware boxes, and the like. Other types of platforms, such as UNIX, and others are used in alternative embodiments of the present invention.
Part PAR_51: In the present embodiment firewall/QOS servers 770 are provided with quality of service management features described above and in co-pending application Ser. No. 60/067,857, entitled: Bandwidth Management System and Method, filed Dec. 5, 1997, attorney docket no. 18430-000300 and in co-pending application Ser. No. 60/047,752, entitled: Method and Apparatus for Configuring and Managing Firewalls, filed May 27, 1997, attorney docket no. 18430-000200. Further, firewall/QOS servers 770 are typically provided with firewall management features described in co-pending application Ser. No. 08/998,100, entitled: Method and Apparatus for Configuring and Managing Firewalls and Security Device, filed Dec. 24, 1997, attorney docket no. 18430-000110, although other firewall features are also contemplated. These applications are herein by incorporated by reference for all purposes.
Part PAR_52: The embodiment illustrated in FIG. 8 represents a network of trusted networks representative of a typical configuration. As shown in detail in FIG. 8, DS server 700 is preferably coupled to the trusted networks by, among other possible configurations, firewall/QOS servers 770. DS server 700 typically embodies directory access services such as Novell Directory Services, LDAP, X.500, ADS, and others. Firewall/QOS servers 770 are typically also compatible with the selected directory services. Further information regarding Novell Directory Services (NDS) can be found in documents at the following web site www.novell.com/products/nds/wpnds.html. The documents are incorporated by reference for all purposes.
Part PAR_53: DS server 700 enables the management of firewall/QOS servers 770 from a central administration point. Thus, from the central administration point the user can configure or reconfigure each firewall/QOS server 770. For example the configuration of firewall capabilities within the network can be managed and set by single administrator via the directory services. Further, the QOS capabilities of the trusted networks can also be managed from a single administrator via the directory services. For example, as discussed above and in the referenced applications, QOS parameters can include determination and classification of traffic classes and entities, the determination and configuration of traffic policies, the determination and configuration of traffic rules, and the like. Further the directory services provides back-up or redundant QOS and/or firewall configuration, data, and the like which may be referenced if the information stored within a local firewall/QOS server is compromised or requires updating.
Part PAR_54: By providing a single point of administration for multiple Quality of Service servers, a coherent and uniform quality of service policy can be implemented. Alternatively, a single point of administration provides the determination of quality of service to be determined for multiple QOS servers, although the particular configuration for specific servers may be different. Further, by providing this capability, changes to the QOS classes, policies, rules, and the like can be made in a timely fashion. As opposed to logging into each firewall/QOS server 770 and modifying the configuration information individually, the user logs into one machine, such as DS Server 700 or remotely into DS Server 700, to modify the selected parameters.
Part PAR_55: FIGS. 9a-c illustrate typical firewall/QOS system configurations for embodiments of the present invention. FIG. 9a illustrates the system configured for a pure IPX network; FIG. 9b illustrates the system configured for a pure IP network; and FIG. 9c illustrates the system configured for a mixed IP/IPX network. FIG. 9a includes a network server 800 and a firewall/QOS server 810; FIG. 9b includes a firewall/QOS server 830; and FIG. 9c includes a firewall server 850.
Part PAR_56: In the embodiment in FIG. 9a, network server 800 operates in a pure IPX network and is typically based upon Novell NetWare Server software, In this configuration, firewall/QOS server 810 independently provides the firewall, security, and QOS services and also preferably provides IPX/IP gateway services to the Internet.
Part PAR_57: In one embodiment of the present invention, firewall server 810 and network server 800 are implemented on physically distinct computer systems. Alternatively, firewall/QOS server 810 and network server 800 are implemented upon the same physical computer system, and Netware Server provides the IPX/IP gateway services.
Part PAR_58: In the embodiment in FIG. 9b, a network server for a pure IP network may be based upon UNIX, WindowsNT, Windows95 servers, and the like. In this configuration, firewall server 830 provides the firewall, security and other QOS services, but typically without the IPX/IP gateway services.
Part PAR_59: In the embodiment in FIG. 9c, a mixed protocol network may be based upon both IPX and IP protocols, as illustrated. In this configuration, firewall/QOS server 850 provides the firewall, other security services, QOS services, and preferably provides the IPX/IP gateway services for IPX transmission packets as needed.
Part PAR_60: FIG. 10 is a block diagram of a system 870 for a directory services server according to an embodiment of the present invention. System 870 preferably includes many of the same computer hardware and software components described above for FIG. 2.
Part PAR_61: In FIG. 10, it is preferred that the network interface unit 340 is coupled to internal networks to provide Directory Services between those internal networks. As an example, as illustrated in FIG. 8, DS server 700 is coupled to the trusted networks through firewall/QOS servers 770 and provides directory access to and from trusted network 780 to trusted network 790 that is transparent to the user.
Part PAR_62: To provide cross network directory services, it is preferred that each internal network conform with the same directory services protocol. Several of these protocols were mentioned above (Novell Directory Services, LDAP, and the like.) System 870 thus preferably manages directory services requests between internal networks, and from a central administration point to the internal networks, according to the chosen directory services protocol. Further, in one particular embodiment, System 870 preferably manages requests to modify configuration files within firewalls, security features, and QOS configuration of the attached trusted networks.
Part PAR_63: FIG. 10 is representative of but one type of system for embodying the present invention. It will be readily apparent to one of ordinary skill in the art that many system types and configurations are suitable for use in conjunction with the preferred embodiment of the present invention.
Part PAR_64: It should be understood that coupling of system 870 to the trusted networks need not be a direct connection. As illustrated in the embodiment in FIG. 8, the coupling is performed via firewall/QOS servers 770. Further, it is envisioned that trusted networks may be coupled to system 870 by virtual private networks, or similar system, via a trusted or an untrusted network such as the Internet, or any combination of the above connections, and the like.
Part PAR_65: In the embodiment illustrated in FIG. 8, DS server 700 provides a central database (a directory services database) that stores configuration information of internal networks such as IPX based networks 780 and IP based networks 790, including in the present embodiment, QOS configuration information.
Part PAR_66: FIGS. 11a-c illustrate installation of QOS configuration information according to an embodiment of the present invention. In particular, FIGS. 11a-c illustrate an embodiment implemented using Novell Directory Services. Other directory services standards or protocols may alternatively be used in other embodiments.
Part PAR_67: In order to integrate QOS configuration capability to the Novell Directory Services, a configuration administration tool is implemented as a NetWare Administrator software (NWADMIN) "snap-in." The installation of this snap-in extends the Novell Directory Services schema by adding a firewall/QOS class and associated attributes. The associated attributes include QOS configuration parameters such Classes, Entities, Policies, Rules, and the like are thus preferably administered and enforced through the Directory Services administration software.
Part PAR_68: FIG. 11b illustrates the extension of the Novell Directory Services to include a class of security devices, namely firewall/QOS 980. FIG. 11b illustrates the extension of a Directory Services with a single firewall/QOS, in a configuration such as illustrated in FIG. 8; FIG. 11c illustrates the extension of a Directory Services with multiple firewall/QOS servers. Administration of one or more firewall/QOS servers from a single administration point is thus provided with a typical graphical user interface as shown.
Part PAC_9: CONCLUSION
Part PAR_69: 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).
Part PAR_70: 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.
Part PAR_71: 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.
Part PAR_72: The embodiments described above describe the integration of QOS with a firewall server. In alternative embodiments of the present invention, a QOS server need not be integrated into a firewall but may be a stand-alone server based upon software running on a general purpose computer, or a combination of software running upon a general purpose computer with custom application hardware. In any of the embodiments described, Directory Services may provide support for centralized administration of QOS servers in whatever specific form.
Part PAR_73: Many changes or modifications are readily envisioned. For example, it is envisioned that different directory services protocols or standards can be used such as LDAP, X500, AD (Active Directory), and the like in alternative embodiments of the present invention. Further, it is envisioned that firewall/QOS servers and other security devices may be implemented on different operating system platforms than WindowsNT, NetWare, IntranetWare, UNIX platforms, and the like such as MacOS or even proprietary hardware based firewall solutions. Still further, it is envisioned that in the future, other network protocols other than IP and IPX clients may be used in other embodiments.
Part PAR_74: The specification has been extensively described with regards to firewalls and QOS servers, however it should be understood that firewalls are merely a common term for a class or type of network access or security devices. Thus embodiments of the present invention can be used with other network security devices, Further, a firewall may have capabilities extending outside the reach of traditional firewalls, for example incorporating quality of service monitoring and metering capability. Still further, the present invention may be applied to security devices that include firewall capabilities although not specifically called firewalls.
Part PAR_75: 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.


{'bibliographic_information': "{'Patent Number': '060473223', 'Series Code': '8', 'Application Number': '9990968', 'Application Type': '1', 'Art unit': '273', 'Application Filing Date': '19971229', 'Title of Invention': 'Method and apparatus for quality of service management', 'Issue Date': '20000404', 'Number of Claims': '20', 'Exemplary Claim Number(s)': '1', 'Primary Examiner': 'Pan; Daniel H.', 'Number of Drawing Sheets': '11', 'Number of figures': '15'}", 'source_file': './grant/2000/pftaps20000404_wk14.txt', 'source_data': 'USPTO-Grant'}