Source: http://www.google.com/patents/US20020143939?ie=ISO-8859-1&dq=5,884,271
Timestamp: 2015-07-02 04:54:23
Document Index: 591232339

Matched Legal Cases: ['art 403', 'art 401', 'art 401', 'art 401', 'art 403', 'art 403']

Patent US20020143939 - Method for automatically classifying traffic with enhanced hierarchy in a ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsIn packet communication, a method for automatically classifying packet flows for use in allocating bandwidth resources and the like by a rule of assignment of a service level. By rendering discoverable the attributes of a flow specification for packet flows, a finer grained hierarchy of classification...http://www.google.com/patents/US20020143939?utm_source=gb-gplus-sharePatent US20020143939 - Method for automatically classifying traffic with enhanced hierarchy in a packet communications networkAdvanced Patent SearchPublication numberUS20020143939 A1Publication typeApplicationApplication numberUS 10/155,936Publication dateOct 3, 2002Filing dateMay 24, 2002Priority dateNov 25, 1997Also published asUS6591299Publication number10155936, 155936, US 2002/0143939 A1, US 2002/143939 A1, US 20020143939 A1, US 20020143939A1, US 2002143939 A1, US 2002143939A1, US-A1-20020143939, US-A1-2002143939, US2002/0143939A1, US2002/143939A1, US20020143939 A1, US20020143939A1, US2002143939 A1, US2002143939A1InventorsGuy Riddle, Robert Packer, Mark HillOriginal AssigneePacketeer, Inc.Export CitationBiBTeX, EndNote, RefManReferenced by (40), Classifications (21), Legal Events (8) External Links: USPTO, USPTO Assignment, EspacenetMethod for automatically classifying traffic with enhanced hierarchy in a packet communications network
BRIEF DESCRIPTION OF THE DRAWINGS [0029]FIG. 1A depicts a representative client server relationship in accordance with a particular embodiment of the invention; [0030]FIG. 1B depicts a functional perspective of the representative client server relationship in accordance with a particular embodiment of the invention; [0031]FIG. 1C depicts a representative internetworking environment in accordance with a particular embodiment of the invention; [0032]FIG. 1D depicts a relationship diagram of the layers of the TCP/IP protocol suite; [0033] FIGS. 2A-2B depict representative divisions of bandwidth; [0034]FIG. 3 depicts a component diagram of processes and data structures in accordance with a particular embodiment of the invention; and [0035] FIGS. 4A-4B depict flowcharts of process steps in automatically classifying traffic in accordance with a particular embodiment of the invention.
DESCRIPTION OF SPECIFIC EMBODIMENTS OF THE INVENTION [0036] 1.0 Introduction [0037] The present invention provides techniques to automatically classify a plurality of heterogeneous packets in a packet telecommunications system for management of network bandwidth in systems such as a private area network, a wide area network or an internetwork. Systems according to the present invention enable network managers to: automatically define traffic classes, for which policies may then be created for specifying service levels for the traffic classes and isolating bandwidth resources associated with certain traffic classes. Inbound as well as outbound traffic may be managed. Below is a definitional list of terminology used herein. [0038] LIST OF DEFINITIONAL TERMS [0039] ADMISSIONS CONTROL A policy invoked whenever a system according to the invention detects that a guaranteed information rate cannot be maintained. An admissions control policy is analogous to a busy signal in the telephone world. [0040] CLASS SEARCH ORDER A search method based upon traversal of a N-ary tree data structure containing classes. [0041] COMMITTED INFORMATION RATE (CIR) A rate of data flow allocated to reserved service traffic for rate based bandwidth allocation for a committed bandwidth. Also called a guaranteed information rate (GIR). [0042] EXCEPTION A class of traffic provided by the user which supersedes an automatically determined classification order. [0043] EXCESS INFORMATION RATE (EIR) A rate of data flow allocated to reserved service traffic for rate based bandwidth allocation for uncommitted bandwidth resources. [0044] FLOW A flow is a single instance of a connection or packet-exchange activity.. For example, all packets in a TCP connection belong to the same flow, as do all packets in a UDP session. A flow always is associated with a traffic class. [0045] GUARANTEED INFORMATION RATE (GIR) A rate of data flow allocated to reserved service traffic for rate based bandwidth allocation for a committed bandwidth. Also called a committed information rate (CIR). [0046] INSIDE On the LAN side of the bandwidth management device. [0047] MATCHING RULE A description which is used to determine whether a flow matches a traffic class, e.g., “inside service:http”, which will match any flows which are connected to an HTTP server on the “inside” of the bandwidth management device. Also known as “traffic specifications”. [0048] OUTSIDE On the WAN or Internet side of the bandwidth management device. [0049] PARTITION Partition is an arbitrary unit of network resources. [0050] POLICY A rule assigned to a given class that defines how the traffic associated with the class will be handled during bandwidth management.. [0051] POLICY INHERITANCE A method for assigning policies to flows for which no policy exists in a hierarchical arrangement of policies. For example, if a flow matches the traffic class for FTP traffic to Host A, and no corresponding policy exists, a policy associated with a less specific node, such as the traffic class which matches FTP traffic to any host, may be located and used. [0052] POLICY BASED SCALING An adjustment of a requested data rate for a particular flow based upon the policy associated with the flow and information about the flow's potential rate. [0053] SCALED RATE Assignment of a data rate based upon detected speed. [0054] SERVICE LEVEL A service paradigm having a combination of characteristics defined by a network manager to handle a particular class of traffic. Service levels may be designated as either reserved or unreserved. [0055] TRAFFIC CLASS A logical grouping of traffic flows that share the same characteristics—such as application, protocol, address, or set of addresses. A traffic class is defined with a series of matching rules. [0056] TRAFFIC SPECIFICATION See “matching rule”. [0057] URI A Universal Resource Identifier is the name of the location field in a web reference address. It is also called a URL or Universal Resource Locator [0058] 1.1 Hardware Overview [0059] The method for classifying heterogeneous packets in a packet telecommunications environment of the present invention may be implemented in the C programming language and made operational on a computer system such as shown in FIG. 1A. This invention may be implemented in a client-server environment, but a client-server environment is not essential. This figure shows a conventional client-server computer system which includes a server 20 and numerous clients, one of which is shown as client 25. The use of the term “server” is used in the context of the invention, wherein the server receives queries from (typically remote) clients, does substantially all the processing necessary to formulate responses to the queries, and provides these responses to the clients. However, server 20 may itself act in the capacity of a client when it accesses remote databases located at another node acting as a database server. [0060] The hardware configurations are in general standard and will be described only briefly. In accordance with known practice, server 20 includes one or more processors 30 which communicate with a number of peripheral devices via a bus subsystem 32. These peripheral devices typically include a storage subsystem 35, comprised of a memory subsystem 35 a and a file storage subsystem 35 b holding computer programs (e.g., code or instructions) and data, a set of user interface input and output devices 37, and an interface to outside networks, which may employ Ethernet, Token Ring, ATM, IEEE 802.3, ITU X.25, Serial Link Internet Protocol (SLIP) or the public switched telephone network. This interface is shown schematically as a “Network Interface” block 40. It is coupled to corresponding interface devices in client computers via a network connection 45. [0061] Client 25 has the same general configuration, although typically with less storage and processing capability. Thus, while the client computer could be a terminal or a low-end personal computer, the server computer is generally a high-end workstation or mainframe, such as a SUN SPARC server. Corresponding elements and subsystems in the client computer are shown with corresponding, but primed, reference numerals. [0062] Bus subsystem 32 is shown schematically as a single bus, but a typical system has a number of buses such as a local bus and one or more expansion buses (e.g., ADB, SCSI, ISA, EISA, MCA, NuBus, or PCI), as well as serial and parallel ports. Network connections are usually established through a device such as a network adapter on one of these expansion buses or a modem on a serial port. The client computer may be a desktop system or a portable system. [0063] The user interacts with the system using interface devices 37′ (or devices 37 in a standalone system). For example, client queries are entered via a keyboard, communicated to client processor 30′, and thence to modem or network interface 40′ over bus subsystem 32′. The query is then communicated to server 20 via network connection 45. Similarly, results of the query are communicated from the server to the client via network connection 45 for output on one of devices 37′ (say a display or a printer), or may be stored on storage subsystem 35′. [0064]FIG. 1B is a functional diagram of a computer system such as that of FIG. 1A. FIG. 1B depicts a server 20, and a representative client 25 of a plurality of clients which may interact with the server 20 via the Internet 45 or any other communications method. Blocks to the right of the server are indicative of the processing steps and functions which occur in the server's program and data storage indicated by blocks 35 a and 35 b in FIG. 1A. A TCP/IP “stack” 44 works in conjunction with Operating System 42 to communicate with processes over a network or serial connection attaching Server 20 to Internet 45. Web server software 46 executes concurrently and cooperatively with other processes in server 20 to make data objects 50 and 51 available to requesting clients. A Common Gateway Interface (CGI) script 55 enables information from user clients to be acted upon by web server 46, or other processes within server 20. Responses to client queries may be returned to the clients in the form of a Hypertext Markup Language (HTML) document outputs which are then communicated via Internet 45 back to the user. [0065] Client 25 in FIG. 1B possesses software implementing functional processes operatively disposed in its program and data storage as indicated by block 35 a′ in FIG. 1A. TCP/IP stack 44′, works in conjunction with Operating System 42′ to communicate with processes over a network or serial connection attaching Client 25 to Internet 45. Software implementing the function of a web browser 46′ executes concurrently and cooperatively with other processes in client 25 to make requests of server 20 for data objects 50 and 51. The user of the client may interact via the web browser 46′ to make such queries of the server 20 via Internet 45 and to view responses from the server 20 via Internet 45 on the web browser 46′. [0066] Network Overview [0067]FIG. 1C is illustrative of the internetworking of a plurality of clients such as client 25 of FIGS. 1A and 1B and a plurality of servers such as server 20 of FIGS. 1A and 1B as described herein above. In FIG. 1C, network 60 is an example of a prior art Token Ring or frame oriented network. Network 60 links host 61, such as an IBM RS6000 RISC workstation, which may be running the AIX operating system, to host 62, which is a personal computer, which may be running Windows, IBM OS/2 or a DOS operating system, and host 63, which may be an IBM AS/400 computer, which may be running the OS/400 operating system. Network 60 is internetworked to network 70 via a system gateway which is depicted here as router 75, but which may also be a gateway having a firewall or a network bridge. Network 70 is an example of an Ethernet network that interconnects host 71, which is a SPARC workstation, which may be running SUNOS operating system with host 72, which may be a VAX 6000 computer which may be running the VMS operating system (formerly available from Digital Equipment Corporation). [0068] Router 75 is a network access point (NAP) of network 70 and network 60. Router 75 employs a Token Ring adapter and Ethernet adapter. This enables router 75 to interface with the two heterogeneous networks. Router 75 is also aware of the Inter-network Protocols, such as ICMP and RIP, which are described herein below. [0069]FIG. 1D is illustrative of the constituents of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. The base layer of the TCP/IP protocol suite is the physical layer 80, which defines the mechanical, electrical, functional and procedural standards for the physical transmission of data over communications media, such as, for example, the network connection 45 of FIG. 1A. The physical layer may comprise electrical, mechanical or functional standards such as whether a network is packet switching or frame-switching; or whether a network is based on a Carrier Sense Multiple Access/Collision Detection (CSMA/CD) or a frame relay paradigm. [0070] Overlying the physical layer is the data link layer 82. The data link layer provides the function and protocols to transfer data between network resources and to detect errors that may occur at the physical layer. Operating modes at the datalink layer comprise such standardized network topologies as IEEE 802.3 Ethernet, IEEE 802.5 Token Ring, ITU X.25, or serial (SLIP) protocols. [0071] Network layer protocols 84 overlay the datalink layer and provide the means for establishing connections between networks. The standards of network layer protocols provide operational control procedures for internetworking communications and routing information through multiple heterogenous networks. Examples of network layer protocols are the Internet Protocol (IP) and the Internet Control Message Protocol (ICMP). The Address Resolution Protocol (ARP) is used to correlate an Internet address and a Media Access Address (MAC) for a particular host. The Routing Information Protocol (RIP) is a dynamic routing protocol for passing routing information between hosts on networks. The Internet Control Message Protocol (ICMP) is an internal protocol for passing control messages between hosts on various networks. ICMP messages provide feedback about events in the network environment or can help determine if a path exists to a particular host in the network environment. The latter is called a “Ping”. The Internet Protocol (IP) provides the basic mechanism for routing packets of information in the Internet. IP is a non-reliable communication protocol. It provides a “best efforts” delivery service and does not commit network resources to a particular transaction, nor does it perform retransmissions or give acknowledgments. [0072] The transport layer protocols 86 provide end-to-end transport services across multiple heterogenous networks. The User Datagram Protocol (UDP) provides a connectionless, datagram oriented service which provides a non-reliable delivery mechanism for streams of information. The Transmission Control Protocol (TCP) provides a reliable session-based service for delivery of sequenced packets of information across the Internet. TCP provides a connection oriented reliable mechanism for information delivery. [0073] The session, or application layer 88 provides a list of network applications and utilities, a few of which are illustrated here. For example, File Transfer Protocol (FTP) is a standard TCP/IP protocol for transferring files from one machine to another. FTP clients establish sessions through TCP connections with FTP servers in order to obtain files. Telnet is a standard TCP/IP protocol for remote terminal connection. A Telnet client acts as a terminal emulator and establishes a connection using TCP as the transport mechanism with a Telnet server. The Simple Network Management Protocol (SNMP) is a standard for managing TCP/IP networks. SNMP tasks, called “agents”, monitor network status parameters and transmit these status parameters to SNMP tasks called “managers.” Managers track the status of associated networks. A Remote Procedure Call (RPC) is a programming interface which enables programs to invoke remote functions on server machines. The Hypertext Transfer Protocol (HTTP) facilitates the transfer of data objects across networks via a system of uniform resource indicators (URI). [0074] The Hypertext Transfer Protocol is a simple protocol built on top of Transmission Control Protocol (TCP). It is the mechanism which underlies the function of the World Wide Web. The HTTP provides a method for users to obtain data objects from various hosts acting as servers on the Internet. [0075] 2.0 Traffic Class [0076] A traffic class (or “class”) is broadly defined as a grouping of traffic flows that share the same characteristics. A traffic class is defined with one or more matching rules. Traffic classes may have the property of being directional, i.e. all traffic flowing inbound will belong to different traffic classes and be managed separately from traffic flowing outbound. The directional property enables asymmetric classification and control of traffic, i.e., inbound and outbound flows belong to different classes which may be managed independent of one another. [0077] Traffic classes may be defined at any level of the IP protocol as well as for other non-IP protocols. For example, at the IP level, traffic may be defined as only those flows between a specified set of inside and outside IP addresses or domain names. An example of such a low level traffic class definition would be all traffic between my network and other corporate offices throughout the Internet. At the application level, traffic classes may be defined for specific URIs within a web server. Traffic classes may be defined having “Web aware” class attributes. For example, a traffic class could be created such as all URIs matching “*.html” for all servers, or all URI patterns matching “*.gif” for server X, or for access to server Y with URI pattern “/sales/*” from client Z, wherein ‘*’ is a wildcard character, i.e., a character which matches all other character combinations. Traffic class attributes left unspecified will simply match any value for that attribute. For example, a traffic class that accesses data objects within a certain directory path of a web server is specified by a URI pattern of the directory path to be managed, e.g. “/sales/*”. [0078] 2.1 Classifying Traffic [0079] The present invention provides a method for classifying traffic according to a definable set of classification attributes selectable by the manager, including selecting a subset of traffic of interest to be classified. The invention provides the ability to classify and search traffic based upon multiple orthogonal classification attributes. [0080] Traffic class membership may be hierarchical. Thus, a flow may be classified by a series of steps through a traffic class tree, with the last step (i.e., at the leaves on the classification tree) mapping the flow to a policy. Some applications may be classified by application-specific attributes as well. For example, web traffic may also be classified by HTTP header types such as Content-Type (MIME type) or User-Agent. Citrix traffic may be classified by application name or Citrix client name. (A Citrix client name is the client name used under the Critix (brand) technique of client-server interaction. RTP (real-time protocol) traffic may be classified by encoding name or media type. [0081] A classification tree is a data structure representing the hierarchical aspect of traffic class relationships. Each node of the classification tree represents a class, and has a traffic specification, i.e., a set of attributes or characteristics describing the traffic associated with it. Leaf nodes of the classification tree may contain policies. According to a particular embodiment, the classification process checks at each level if the flow being classified matches the attributes of a given traffic class. If it does, processing continues down to the links associated with that node in the tree. If it does not, the class at the level that matches determines the policy for the flow being classified. If no policy specific match is found, the flow is assigned the default policy. [0082] In a preferred embodiment, the classification tree is an N-ary tree with its nodes ordered by specificity. For example, in classifying a particular flow in a classification tree ordered first by organizational departments, the attributes of the flow are compared with the traffic specification in each successive department node and if no match is found, then processing proceeds to the next subsequent department node. If no match is found, then the final compare is a default “match all” category. If, however, a match is found, then classification moves to the children of this department node. The child nodes may be ordered by an orthogonal paradigm such as, for example, “service type.” Matching proceeds according to the order of specificity in the child nodes. Processing proceeds in this manner, traversing downward and from left to right in FIGS. 2A and 2B, which describe a classification tree, searching the plurality of orthogonal paradigms. Key to implementing this a hierarchy is that the nodes are arranged in decreasing order of specificity. This permits search to find the most specific class for the traffic before more general. [0083] The table below depicts exemplary components from which traffic classes may be built. Note that the orientation of the server (inside or outside) may be specified. As noted above, any traffic class component may be unspecified, i.e., set to match any value. [0084] Components of a Traffic Class Specifier [0085] Inside (Client or Server) Global Outside (Server or Client) [0086] IP Address/Domain Name TCP or UDP Service IP Address/Domain Name [0087] Port Number e.g., WWW, Port Number [0088] MAC Address FTP, RealAudio, etc. MAC Address [0089] URI pattern for [0090] Web Service, [0091] MIME type for [0092] Web Service [0093] IPX Service [0094] SNA Service [0095] LAT Service [0096] IP precedence [0097] Application Specific Attributes [0098] As an example, FIGS. 2A and 2B depict representative classifications of traffic made by a hypothetical network manager in order to accomplish particular allocations of bandwidth. In FIG. 2A, the network manager has decided to divide her network resources first by allocating bandwidth between Departments A and B. FIG. 2A shows the resulting classification tree 201, in which Department A bandwidth resources 202 and Department B bandwidth resources 204 each have their own nodes representing a specific traffic class for that department. Each traffic class may have one or more rules which are used for determining whether a flow matches that traffic class. For example, in FIG. 2A, the Department A resources node 202 has the matching rule Inside Host Subnet A associated with it. Next, the network manager has chosen to divide the bandwidth resources of Department A between two applications. She allocates an FTP traffic class 206 and a World Wide Web server traffic class 208. Each of these nodes may have a separate policy attribute associated with them. For example, in FIG. 2A, the FTP node 206 for has an attribute Outside port 20 associated with it. Similarly, the network manager has chosen to divide network bandwidth resources of Departnent B into an FTP server traffic class 210 and a World Wide Web server traffic class 212. Each may have their own respective policies. [0099]FIG. 2B shows a second example 203, wherein the network manager has chosen to first divide network bandwidth resource between web traffic and TCP traffic. She creates three traffic nodes, a web traffic node 220, a TCP traffic node 224 and a default node 225. Next, she divides the web traffic among two organizational departments by creating a Department A node 226, and a Department B node 228. Each may have its own associated policy. Similarly, she divides TCP network bandwidth into separate traffic classes by creating a Department A node 230 and a Department B node 232. Each represents a separate traffic class which may have its own policy. [0100] All traffic which does not match any user specified traffic class falls into an automatically created default traffic class which has a default policy. In FIG. 2A, the default category is depicted by a default node 205, and in FIG. 2B, the default category is depicted by a default node 225. [0101] 3.1 Traffic Discovery [0102] Network traffic is classified under existing classes, beginning with the broadest classes, in inbound and outbound traffic classes which are protocol layer independent. For example, a particular instance of traffic may be classified according to its transport layer characteristics, e.g., Internet Protocol port number, as well as its application layer information, e.g., SMTP. In addition to application layer information, there may be attributes of the application upon which traffic classification can be based. For example, with SMTP, an attribute might be the length of the message or header information of the message or whether attachments are present. For an end-user application, such as a Lotus Notes database manager, the type of data might also be the basis of traffic classification. The key is that the flow specification must have some of its attributes discoverable in the course of the classification processing. Characteristics such as MIME types may also be discovered. Standard protocols, such as, IPX, SNA, and services, such as, SMTP and FTP are recognized for discovery. Classification is performed to the most specific level determinable. For example, in select embodiments, non-IP traffic, such as SNA, may be classified only by protocol, whereas within Internet Protocol, TCP or UDP traffic may be classified to the service level as indicated in the “/etc/services” file. Classification beyond a determined terminal classification level is not performed. For example, in a select embodiment, a class matching “ipx” or “nntp” will not be further classified. [0103] 3.1.1 Service Aggregates [0104] A service aggregate is provided for certain applications that use more than one connection in a particular conversation between a client and a server. For example, an FTP client in conversation with an FTP server employs a command channel and a data transfer channel, which are distinct TCP sessions on two different ports. In cases where two or three TCP or UDP sessions exist for each conversation between one client and one server, it is useful to provide a common traffic class i.e., the service aggregate, containing the separate conversations. In practice, these types of conversations are often between the same two hosts, but using different ports. According to the invention, a class is created with a plurality of matching rules, each matching various component conversations. [0105] 3.1.2 Classification Under Specified Criterion [0106] Classification of traffic into a tree is performed by traversing the tree of traffic classes, starting at the root and proceeding through each child of the root, comparing the flow being classified against the matching rules associated with each traffic class. The flow is defined as “matching” a class if its characteristics match any one of the matching rules that is used to define the class. When the flow matches a class, then if that traffic class has children, the flow will be compared against each of the children to determine if there is a more specific match—otherwise, the processing stops and the flow is assigned to that traffic class. A marker is placed in match_all default nodes so that when match processing reaches the marker, the classification processing depicted in flowchart 403 terminates, and the flow is assigned to the default class that was reached. [0107] 3.1.3 Default Suggested Policies [0108] A default policy may be suggested or, in select embodiments, automatically applied, to a traffic class which has been discovered. Applying suggested or default policies for a new class at a user's option is described in a copending, commonly owned, U.S. patent application Ser. No. 09/198,051, entitled, “Method for Automatically Determining a Traffic Policy in a Packet Communications Network,” which is incorporated herein by reference in its entirety for all purposes. [0109] 3.1.4 Analysis of Data in Determining Traffic Class [0110] In a preferable embodiment, classification can extend to examination of the data contained in a flow's packets. Certain traffic may be distinguished by a signature even if it originates with a server run on a non-standard port, for example, an HTTP conversation on port 8080 would not be otherwise determinable as HTTP from the port number. Further analysis of the data is conducted in order to determine classification in instances where: 1) FTP commands are used to define server ports, 2) HTTP protocol is used for non-web purposes. The data is examined for indication of push traffic, such as Pointcast Network-type traffic (a type of traffic marketed by InfoGate of San Diego, Calif.), which uses HTTP as a transport mechanism. These uses may be isolated and classified into a separate class. Marimba and Pointcast can be distinguished by looking into the data for a signature content header in the get request. Pointcast has URLs that begin with “/FIDO-1/.” Other applications in which protocol can be inferred from data include Telnet traffic. Both tn3270 and tn3270E (emulation) may be detected by looking into data and given a different class. Telnet traffic has option negotiations which may indicate an appropriate class. [0111] 3.1.5 Identity of Traffic Based Upon Resource Creator's Class [0112] A flow's traffic class may be inferred by observing the existence of other flows that are known to be related, between the same two nodes as the flow being classified. . This method is used to detect Real Time Protocol (RTP) for point-to-point telephony, RTP for broadcast streaming, CCITT/ITU, H323-internet telephony over the Internet (bidirectional) and RTSP real time streaming protocol (unidirectional). [0113] 3.1.6 Dynamic Ports [0114] Some applications establish connections to a well-known port number. Other applications use dynamic ports, by first connecting to a well-known port number, and then being redirected to another port number which is random or dynamically generated. For example, in a database application, a client may connect to the database server's well-known port number. At this location, a load-balancing server may be running which is aware of all of the other port numbers that are listened to by instances of the database application. The load-balancing server will redirect the client to the port number of the least-loaded database server instance. [0115] 3.2 Traffic Discovery Processing [0116]FIG. 3 depicts components of a system for discovering traffic according to the invention. A traffic tree 302 is provided in which new traffic will be discovered under a particular member class node. The traffic tree may have a hierarchy of nodes (Class A, B C) and corresponding subnodes under the nodes. A traffic classifier 304 detects services for incoming traffic. Alternatively, the classifier may start with a service and determine the hosts using it. A knowledge base 306 contains heuristics for determining traffic classes. The knowledge base may be embodied in memory, file, executable code, or a database. In a preferred embodiment, the knowledge is contained within a data structure resident in memory, and in executable code. A plurality of saved lists 308 stores identifying characteristics of classified traffic pending incorporation into traffic tree 302. In select embodiments, entries for each instance of traffic may be kept in one of the plurality of saved lists, each of which is associated with a traffic class which is marked to indicate that discovery is enabled on it. If there are attributes that are specific to an application, the entries may contain such attributes. In alternate embodiments, a copy of an entry and a count of duplicate copies for the entry is maintained. [0117]FIG. 4A depicts a flowchart 401 of processing steps for discovering traffic. In a step 402, a flow specification is parsed from the flow being classified. The flow specification may include attributes of the application associated with the flow. Then in a step 404, the flow specification parsed from the flow in step 402 is compared with the traffic specifications in each node of the classification tree. Rules are checked starting from most specific to least specific. In a decisional step 406, a determination is made if traffic matches one of the classes that are marked for discovery. . If this is so, then in a step 408, an entry is made in a list of identifying characteristics, such as protocol type, IP protocol number, server port, traffic type if known, application-specific attributes, or a time of occurrence of the traffic. In an optional step 410, duplicate instances having the same identifying characteristics are suppressed, in favor of keeping a count of the duplicates and a most recent time traffic with these identifying characteristics was encountered. In an optional step 412, a byte count of traffic of this type has been detected is included. It should be noted that as a result of the traffic classification process, a flow will always match some traffic class. If it does not match anything specific, it will match a match-all (default) class. Also, it should be noted that if a flow matches a class that is marked for discovery, information about the flow will always be recorded in the list of saved characteristics. [0118] In a preferred embodiment, processing according to flowchart 401 may execute on multiple instances of saved list 308. [0119] 3.2.1 Displaying Results to a User [0120] In an optional step 413 (not shown), after the processing of flowchart 401 completes or at periodic intervals or on demand, a list of traffic classes produced in steps 402 through 412 is displayed to a network manager. The list may be sorted by any well-known criteria such as: 1) most “hits” during a recent interval, 2) most recently-seen (most recent time first), 3) most data transferred (bytes/second) during some interval, or a moving average. The user may choose an interval length or display cutoff point (how many items, how recent, at least B bytes per second, or other thresholds). The Network manager may then take some action (e.g. pushing a button) to select the traffic types she wishes to add to the classification tree. The display can be hierarchical, as depicted in lines (3) below: [0121] FTP (3) [0122] FTP-cmd [0123] FTP-data [0124] Lotus [0125] Lotus_database 1 [0126] Lotus_database 2 [0127] Lotus_database 2_video [0128] to-host1 [0129] tcp [0130] FTP [0131] FTP-cmd [0132] FTP-data [0133] HTTP [0134] images [0135] java [0136] text [0137] TCP-port-9999 [0138] wherein the “TCP-port-9999” entry is a traffic class which was discovered as a result of an application which was making repeated or simultaneous connections to TCP port 9999, and for which there was no other information available to allow matching on a specific class for that application (it was not an application known in the knowledge base.) [0139] The italicized terms are examples of sub-nodes with application-specific characteristics. [0140] In a related embodiment, a threshold for display or class creation of well-known traffic types is provided. [0141] 3.2.2 Interval Based Incorporation [0142] In an alternative embodiment, at select intervals of time, items in the saved list of traffic characteristics are analyzed, and either 1) recognized and a corresponding traffic class is added to the tree, or 2) (for repeated attempts to request a server connection port, IP subprotocol type, or ethertype that is not otherwise known in the knowledge base, upon exceeding a certain threshold) a class for the traffic is created and added to the classification tree. [0143]FIG. 4B depicts a flowchart 403 of the processing steps for integrating traffic classes into a classification tree in an embodiment. Processing steps of flowchart 403 create new classes in the classification tree, based upon the information saved in the lists of traffic characteristics. This is done periodically at a defined interval of seconds, such as 30 second in a preferred embodiment. In a step 420, an instance of saved traffic is retrieved from the saved traffic list 308. Thereafter, a test is made to determine if discovery is occurring under a class for which discovery of attributes occurs (that is, a class which corresponds to an application which has application-specific attributes which may be discovered). (step 421). If true, then the process proceeds directly to the step of creating a node for a traffic class for the next attribute that was saved (step 424). Elements on the list of discoverable attributes are assigned a processing priority relative to one another. It is a characteristic of the product that the processing priority (“ordering”) may be pre-defined or may be configurable by the user. (While the characteristic of order is a part of the invention, the mechanism for fixing or for reconfiguring the ordering is not a part of this invention.) If the process is not in a state of discovering attributes, then in an alternative decisional step 422, the instance of saved traffic is examined to determine whether it is well-known (e.g., protocol type, assigned port number) and a name representing its type exists. If this is so then processing continues with a test of whether the saved traffic belongs to a service aggregate in step 426. Otherwise, in a step 423 the instance of saved traffic is examined to determine whether it appears to be a server connection port of an unregistered IP port (or a port that has not been configured). If this is not so then, processing continues with the next traffic class in the saved list in step 420. In decisional step 426, the instance of saved traffic is examined to determine whether it belongs to a service aggregate. For example, an FTP session has one flow that is used to exchange commands and responses and a second flow that is used to transport data files. If the traffic does belong to a service aggregate, then in a step 428, a traffic class is created which will match all components of the service aggregate. In a step 425, a new traffic class is created to match the instance of saved traffic. [0144] In an optional step (not shown), a suggested policy is determined for the traffic class created in step 425. Next, in a decisional step 432, a limit is checked to verify that the total number of traffic classes has not exceeded a specified maximum. If the limit on classes has not been reached, then the traffic is checked to determine if there are still attributes for which classes have not been discovered (step 434) and if so, then the attributes are retained in the list (step 436). In either case, the process is repeated from step 420. [0145] In a related embodiment in place of steps 424, 425 or 428, a display of traffic classes, sorted by most recently used, most hits, number of bytes received during any interval, which is determined by a plurality of time stamps, is available on demand to a network manager. The network manager then manually indicates that the traffic is to be added to the tree. [0146] In a particular embodiment a threshold is employed to determine traffic for which a separate class should be added. A minimum usage threshold indicates whether a particular port has been used at least n times in the last s seconds. (This applies only in those instances where there is an identifiable port.) If traffic is well known, i.e., SMTP, a new traffic class is created immediately, i.e., threshold is equal to one hit per minute; otherwise, the threshold is set equal to a fixed, arbitrarily-configured value, for example, two to ten thousand hits per minute. A new class for traffic is given a generic name, e.g., TCP-Port-99. Entries for traffic over a certain age, for example one minute old, are discarded. [0147] In a related embodiment, another method of identifying an individual traffic class is to detect simultaneous connections to the same host port from different clients. This provides an indication that the port is a well-known connection port. [0148] Traffic classes are created for any combination of the above mentioned categories. A flag is added to all traffic classes so created in order to indicate that it is the product of the auto classifier. [0149] 3.2 Command Language Interface: [0150] In a particular embodiment, function of the classifier 304 is controlled by a command language interface. Below is a plurality of command language interface commands. [0151] setup discover {on|off} To activate autoclassification for various classes to detect well-known protocols and services: [0152] class discover <tclass>{inside/outside/both} To turn on autoclassification (a.k.a. discovery) under a class to detect services with the host on the inside, the outside, or both directions. [0153] class discover <tclass> off To turn off use. [0154] The new classes have names in the format of lines below: [0155] <service> or [0156] <protocol>_Port_<number> or [0157] <service>_<attribute>[_<attribute>_<attribute> . . .]
[0158] where <protocol> is either TCP or UDP. [0159] If a heretofore unknown server-connection port appears to be “well used”, an entry of the second type is created. The threshold for creation is for example 11 hits with no more than 1 minute (granularity of checking is at least 30 seconds between running successive discovery or autoclassification processes) between any two hits. For example: [0160] inbound/inside/ftp [0161] http [0162] sna [0163] TCP_port_505 [0164] Lotus_database2_video [0165] 3.3 Syntax of Traffic Specifications (a.k.a. Matching Rules): [0166] Flow specifications and traffic specifications may have an inside service field and an outside service field. (For some protocols or service types, inside and outside are not distinguished.) Each will have values of SVC_UNKNOWN (0), SVC_CLIENT (1), or a number greater than 1, which is the service index, an index into the global table gServiceTable. If a type of service is known for a connection, the service field at a particular side will be set to SVC_CLIENT and the service field at the opposite side will be the index into gServiceTable. If a type of service is not known for the traffic, both inside service field and outside service field will be SVC_UNKNOWN. A person of reasonable skill in the art will appreciate that other embodiments for the table, such as representing the information contained therein as text strings or by any one of a plurality of possible encoding schemes, are realizable without departing from the present invention. [0167] Therefore, a traffic specification can have “outside service:http” (or just “outside HTTP”) which is different than “outside tcp port:80”. The first will match HTTP on any port while the second will match anything on port 80 (including Pointcast and Marimba). [0168] Specifying an aggregate traffic specification “service:<agg>” identifies the traffic specifications for various traffic belonging to the service. Specifying “class new inbound cdls outside dls” is the same as “class new inbound cdls outside service:dls-wpn” and “class tspec add cdls outside service:dls-rpn”. Most services which are known in the knowledge base will create a class that encompasses all of the members of the aggregate. [0169] Network managers need not be aware of services which are known to be derivative of others, e.g., Pointcast and Marimba are special cases of HTTP and tn3270 is a special case of Telnet, in order to work with the system. [0170] 4.0 Conclusion [0171] In conclusion, the present invention provides for an automatic determination of a policy for a packet telecommunications system wherein bandwidth is allocated to requesting flows according to automatically determined application requirements. An advantage of traffic classification techniques according to the present invention is that network managers need not know the technical aspects of each kind of traffic in order to configure traffic classes. A further advantage of the present invention is that traffic classes may include application-specific attributes such as a MIME type for web traffic. [0172] Other embodiments of the present invention and its individual components will become readily apparent to those skilled in the art from the foregoing detailed description. As will be realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the spirit and the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive. It is therefore not intended that the invention be limited except as indicated by the appended claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7003779 *Feb 17, 2005Feb 21, 2006International Business Machines CorporationHierarchical connected graph model for implementation of event management designUS7050403 *Oct 3, 2001May 23, 2006Nokia CorporationPacket length classificationUS7200684 *Apr 13, 2000Apr 3, 2007International Business Machines CorporationNetwork data packet classification and demultiplexingUS7529249 *Mar 22, 2002May 5, 2009Cisco Technology, IncVoice and dial service level agreement enforcement on universal gatewayUS7543052 *Dec 22, 2003Jun 2, 2009Packeteer, Inc.Automatic network traffic discovery and classification mechanism including dynamic discovery thresholdsUS7580356 *Mar 16, 2006Aug 25, 2009Packeteer, Inc.Method and system for dynamically capturing flow traffic dataUS7639613 *Jun 24, 2005Dec 29, 2009Packeteer, Inc.Adaptive, flow-based network traffic measurement and monitoring systemUS7698403 *Jun 30, 2004Apr 13, 2010Intel CorporationAutomated management system generating network policies based on correlated knowledge to modify operation of a computer networkUS7748002 *Oct 30, 2002Jun 29, 2010Juniper Networks, Inc.Systems and methods for scheduling applicationsUS7769851 *Jan 27, 2005Aug 3, 2010Juniper Networks, Inc.Application-layer monitoring and profiling network trafficUS7809826 *Jan 27, 2005Oct 5, 2010Juniper Networks, Inc.Remote aggregation of network traffic profiling dataUS7813277Jun 29, 2007Oct 12, 2010Packeteer, Inc.Lockless bandwidth management for multiprocessor networking devicesUS7895331 *Aug 10, 2007Feb 22, 2011Bivio Networks, Inc.Method for dynamically configuring network servicesUS7934020Sep 19, 2003Apr 26, 2011Vmware, Inc.Managing network data transfers in a virtual computer systemUS7937755Jan 27, 2005May 3, 2011Juniper Networks, Inc.Identification of network policy violationsUS8059532Jun 21, 2007Nov 15, 2011Packeteer, Inc.Data and control plane architecture including server-side triggered flow policy mechanismUS8086718 *Apr 13, 2010Dec 27, 2011Intel CorporationAutomated process and apparatus for providing integrated management and control of computer networksUS8111707Dec 20, 2007Feb 7, 2012Packeteer, Inc.Compression mechanisms for control plane—data plane processing architecturesUS8140694 *Mar 15, 2004Mar 20, 2012Hewlett-Packard Development Company, L.P.Method and apparatus for effecting secure communicationsUS8204994Feb 22, 2011Jun 19, 2012Bivio Networks, Inc.Method for dynamically configuring network servicesUS8209756Jan 27, 2005Jun 26, 2012Juniper Networks, Inc.Compound attack detection in a computer networkUS8266267Aug 26, 2010Sep 11, 2012Juniper Networks, Inc.Detection and prevention of encapsulated network attacks using an intermediate deviceUS8266275 *May 18, 2009Sep 11, 2012Vmware, Inc.Managing network data transfers in a virtual computer systemUS8279885Sep 25, 2007Oct 2, 2012Packeteer, Inc.Lockless processing of command operations in multiprocessor systemsUS8432848 *Aug 28, 2009Apr 30, 2013Indian Institute of Science (IISc)Queued cooperative wireless networks configuration using rateless codesUS8627320Apr 30, 2010Jan 7, 2014Juniper Networks, Inc.Systems and methods for scheduling applicationsUS8793390May 23, 2006Jul 29, 2014Blue Coat Systems, Inc.Systems and methods for protocol detection in a proxyUS8812714 *Nov 12, 2009Aug 19, 2014Citrix Systems, Inc.Systems and methods for application fluency policiesUS8838753 *Jun 19, 2012Sep 16, 2014Bivio Networks, Inc.Method for dynamically configuring network servicesUS8856926May 20, 2009Oct 7, 2014Juniper Networks, Inc.Dynamic policy provisioning within network security devicesUS8925059 *Jun 8, 2012Dec 30, 2014Lockheed Martin CorporationDynamic trust connectionUS20100296432 *Aug 28, 2009Nov 25, 2010Indian Institute of Science (IISc)Queued Cooperative Wireless Networks Configuration Using Rateless CodesUS20120066487 *Sep 9, 2010Mar 15, 2012Novell, Inc.System and method for providing load balancer visibility in an intelligent workload management systemUS20130124751 *Jan 9, 2013May 16, 2013Hideo AndoInformation reproducing system using information storage mediumUS20130258863 *Mar 12, 2013Oct 3, 2013Fortinet, Inc.Systems and methods for content type classificationUS20140079056 *Nov 22, 2013Mar 20, 2014Fortinet, Inc.Systems and methods for content type classificationEP2501098A1 *Sep 7, 2010Sep 19, 2012ZTE CorporationMethod and device for enhancing quality of service (qos) in wireless local area network (wlan)WO2012010183A1 *Jul 21, 2010Jan 26, 2012Telefonaktiebolaget L M Ericsson (Publ)Technique for packet flow analysisWO2012013238A1 *Jul 29, 2010Feb 2, 2012Telefonaktiebolaget L M Ericsson (Publ)Handling network traffic via a fixed accessWO2014036490A1 *Aug 30, 2013Mar 6, 2014Hughes Network Systems, LlcStaged traffic classification among terminal and aggregation nodes of a broadband communications system* Cited by examinerClassifications U.S. Classification709/224International ClassificationH04L12/24, H04L29/06, H04L12/56Cooperative ClassificationH04L69/18, H04L69/14, H04L41/5022, H04L43/18, H04L29/06, H04L47/2441, H04L47/10, H04L41/0896, H04L41/5058, H04L43/026European ClassificationH04L41/08G, H04L47/10, H04L47/24D, H04L43/02B, H04L41/50B1, H04L43/18, H04L29/06Legal EventsDateCodeEventDescriptionMay 24, 2002ASAssignmentOwner name: PACKETEER, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RIDDLE, GUY;PACKER, ROBERT L.;HILL, MARK;REEL/FRAME:012949/0233;SIGNING DATES FROM 20020502 TO 20020506Owner name: PACKETEER, INC. 10495 N. DEANZA BLVD. CUPERTINO CAOwner name: PACKETEER, INC. 10495 N. DEANZA BLVD. CUPERTINO CAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RIDDLE, GUY;PACKER, ROBERT L.;HILL, MARK;REEL/FRAME:012949/0233;SIGNING DATES FROM 20020502 TO 20020506Owner name: PACKETEER, INC. 10495 N. DEANZA BLVD.CUPERTINO, CAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RIDDLE, GUY /AR;REEL/FRAME:012949/0233;SIGNING DATES FROM 20020502 TO 20020506Dec 28, 2006FPAYFee paymentYear of fee payment: 4Dec 8, 2010FPAYFee paymentYear of fee payment: 8Dec 1, 2011ASAssignmentOwner name: BLUE COAT SYSTEMS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PACKETEER, INC.;REEL/FRAME:027307/0603Effective date: 20111201Feb 16, 2012ASAssignmentOwner name: JEFFERIES FINANCE LLC, NEW YORKFree format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:BLUE COAT SYSTEMS, INC.;REEL/FRAME:027727/0144Effective date: 20120215Owner name: JEFFERIES FINANCE LLC, NEW YORKFree format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:BLUE COAT SYSTEMS, INC.;REEL/FRAME:027727/0178Effective date: 20120215Oct 16, 2012ASAssignmentOwner name: BLUE COAT SYSTEMS, INC., CALIFORNIAFree format text: RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL RECORDED AT R/F 027727/0178;ASSIGNOR:JEFFERIES FINANCE LLC, AS COLLATERAL AGENT;REEL/FRAME:029140/0170Effective date: 20121016Jul 3, 2013ASAssignmentOwner name: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT, NEW YOFree format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:BLUE COAT SYSTEMS, INC.;REEL/FRAME:030740/0181Effective date: 20130628Dec 17, 2014FPAYFee paymentYear of fee payment: 12RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services