Network packet steering via configurable association of processing resources and netmods or line interface ports
Summary by NHIP
Dynamic packet steering system
The system assigns processing resources to network interfaces via a configurable mapping stored as a table data structure in volatile memory. Assigned interfaces steer incoming packets to specific resources and perform filter operations based on this unique identifier before forwarding.
Claim Score by NHIP
Abstract
Methods and systems are provided for steering network packets. According to one embodiment, a mapping associates a processing resource with a network interface module (netmod) and/or a number of line interface ports included within the netmod. In one embodiment, the mapping is configurable within the processing resource and pushed to the netmod. The netmod uses the mapping to steer network packets to the processing resource when the packets conform to the mapping. The mapping may be additionally used to identify a specific process that is to be performed against the packets once the processing resource receives the steered packets from the netmod.

Term
Term ended
Expired 11 December 2023, 2.8 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
31 claims: 5 independent, 26 dependent
- 1A network packet steering system, comprising:a plurality of processing resources provided by a network routing/switching device, each of the processing resources comprising a network packet forwarding resource, a network packet routing resource, a network packet encryption/decryption resource or a network packet authentication resource;a plurality of network interfaces of the network routing/switching device;wherein the one or more processing resources are configurable, uniquely identified within the network routing/switching device, and dynamically assigned to one or more of the plurality of network interfaces or to one or more line interface ports associated with the plurality of network interfaces, and wherein those of the one or more network interfaces that have been assigned a processing resource of the plurality of processing resources steer subsequently received incoming network packets to the assigned processing resource of the plurality of processing resources based on the dynamically configured assignment;wherein one or more of the network interfaces that has been assigned a processing resource of the plurality of processing resources uses the dynamically configured assignment to perform one or more filter operations on the incoming network packets before steering the incoming network packets;and wherein the dynamically configured assignment is stored within a volatile memory associated with one or more of the plurality of network interfaces in the form of a table data structure containing a unique identifier/address of the assigned processing resource of the plurality of processing resources.
- 5A network interface steering table data structure tangibly embodied on a computer-readable medium within a network routing/switching device, comprising:a plurality of interface identifiers corresponding to network interfaces of the network routing/switching device;a plurality of sub-interface identifiers associated with each interface identifier of the plurality of interface identifiers;an address and a pointer corresponding to each sub-interface identifier of the plurality of sub-interface identifiers, the address being associated with a processing resource of a plurality of processing resources of the network routing/switching device to which packets arriving on the sub-interface are to be steered, the pointer being associated with a specific process within the processing resource that is to be used to process the packets, and both the address and the pointer are dynamically associated with the sub-interface, each of the plurality of processing resources comprising a network packet forwarding resource, a network packet routing resource, a network packet encryption/decryption resource or a network packet authentication resource;wherein when a packet is received by a network interface of the network routing/switching device, the network interface steering table data structure is indexed based on one or more of an interface identifier of the network interface receiving the packet and a sub-interface identifier associated with a line interface port of the network interface on which the packet was received, and the network interface steering table data structure provides the corresponding address and the corresponding pointer to facilitate steering of the received packet within the network routing/switching device;and wherein the corresponding address and corresponding pointer are dynamically reconfigured responsive to network traffic changes, to facilitate throughput by a networking device or to load balance received network traffic among a plurality of processing resources of a networking device.
- 11A method comprising:providing a dynamically configurable mapping that associates each of a plurality of network interfaces of a network routing/switching device or each of one or more components of the plurality of network interfaces with one or more processing resources of a plurality of processing resources of the network routing/switching device, each of the plurality of processing resources comprising a network packet forwarding resource, a network packet routing resource, a network packet encryption/decryption resource or a network packet authentication resource, wherein the dynamically configured mapping is stored within a volatile memory associated with one or more of the plurality of network interfaces in the form of a table data structure containing a unique identifier/address of the associated processing resource of the plurality of processing resources;responsive to receiving a packet on a particular network interface of the plurality of network interfaces, determining an appropriate processing resource of the plurality of processing resources to which the received packet is to be steered by retrieving information indicative of the associated processing resource from the dynamically configurable mapping based on one or more of the particular network interface upon which the received packet arrived and a component of the network interface upon which the received packet arrived;and wherein the dynamically configurable mapping is used to have one or more of the plurality of network interfaces perform one or more filter operations on packets received on the one or more network interfaces prior to steering the packets to a processing resource of the plurality of processing resources.
- 18A method comprising:providing a dynamically configurable mapping that associates each of a plurality of network interfaces of a network routing/switching device or each of one or more components of the plurality of network interfaces with one or more processing resources of a plurality of processing resources of the network routing/switching device, each of the plurality of processing resources comprising a network packet forwarding resource, a network packet routing resource, a network packet encryption/decryption resource or a network packet authentication resource, wherein the dynamically configured mapping is stored within a volatile memory associated with one or more of the plurality of network interfaces in the form of a table data structure containing a unique identifier/address of the associated processing resource of the plurality of processing resources;responsive to receiving a packet on a particular network interface of the plurality of network interfaces, determining an appropriate processing resource of the plurality of processing resources to which the received packet is to be steered by retrieving information indicative of the associated processing resource from the dynamically configurable mapping based on one or more of the particular network interface upon which the received packet arrived and a component of the network interface upon which the received packet arrived;and reconfiguring the dynamically configurable mapping responsive to processing and memory capabilities of the plurality of processing resources or responsive to operational status of the plurality of processing resources.
- 25Broadest claimClaim Score 34, narrow(NHIP)A method comprising:providing a dynamically configurable mapping that associates each of a plurality of network interfaces of a network routing/switching device or each of one or more components of the plurality of network interfaces with one or more processing resources of a plurality of processing resources of the network routing/switching device, each of the plurality of processing resources comprising a network packet forwarding resource, a network packet routing resource, a network packet encryption/decryption resource or a network packet authentication resource, wherein the dynamically configured mapping is stored within a volatile memory associated with one or more of the plurality of network interfaces in the form of a table data structure containing a unique identifier/address of the associated processing resource of the plurality of processing resources;responsive to receiving a packet on a particular network interface of the plurality of network interfaces, determining an appropriate processing resource of the plurality of processing resources to which the received packet is to be steered by retrieving information indicative of the associated processing resource from the dynamically configurable mapping based on one or more of the particular network interface upon which the received packet arrived and a component of the network interface upon which the received packet arrived;and load balancing network traffic among the plurality of processing resources.
Independent claims5
62 paragraphs in 7 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application is a continuation of U.S. application Ser. No. 10/163,261 filed on Jun. 4, 2002, now U.S. Pat. No. 7,203,192, which is hereby incorporated by reference for all purposes.
COPYRIGHT NOTICE
0002Contained herein is material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent disclosure by any person as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to the copyright whatsoever. Copyright© 2002-2007, Fortinet, Inc.
BACKGROUND
00031. Field
0004Embodiments of the present invention generally relate to network packet steering, and more particularly to network packet steering from a network interface module to a processing resource, which is used to further route the network packet.
00052. Description of the Related Art
0006In today's highly wired and connected computing environments, networks are often taken for granted by end-users. Yet, heterogeneous networks are often seamlessly and transparently interconnected and made available to the end-users. It is only when a network fails or is degraded that the end-users take notice of the importance associated with having efficient networks.
0007A network can be configured in many different manners. A Local Area Network (LAN) is a group of computing devices that share a common communications line. Computing and storage resources can be shared within a LAN. Moreover, a LAN can be as small as a few computing devices or as large as an entire enterprise (e.g., office building, office complex, and the like). Another network configuration is a Wide Area Network (WAN). A WAN is a geographically dispersed telecommunications network. A classic example of a well known WAN is the Internet. A third network configuration is a Metropolitan Area Network (MAN), where computing devices are connected in a geographic region or specific area that is larger than a LAN and smaller than the typical WAN. Also, in recent years a new type of Virtual Private Network (VPN) has emerged in the industry. A VPN is a private network that takes advantage of public telecommunications and maintains privacy through use of tunneling protocols and security procedures.
0008Moreover, networks can be characterized by the type of data transmission technology in use on the networks (e.g., Transmission Control Protocol/Internet Protocol (TCP/IP), and others). Furthermore, the type of data (e.g., voice versus data) that a network can carry can also distinguish the network. Networks are also classified as public or private, by the usual connection techniques used to access the networks (e.g., switched, dial-up, non-switched, dedicated, virtual, and the like), and by the type of physical links used to interface on the networks (fibre optic, coaxial cable, untwisted shielded pair, and the like).
0009Networks of different types can be interconnected through the use of backbones. A backbone is generally a larger transmission line that carries data gathered from smaller lines that interconnect with it. For example, a LAN may use a backbone to connect with a WAN or to span distances within a single LAN. Further, a WAN may use a backbone as a set of paths that local or regional networks connect to for long-distance interconnections.
0010When networks are interfaced with one another a number of issues arise. One such issue is how to properly route a received data packet between the networks, since each network may be associated with a different media transmission (e.g., Gigabit Ethernet (GigE), Frame Relay (FR), Time-Division Multiplexing (TDM), Asynchronous Transfer Mode (ATM), and others) and/or a different local data packet-addressing schemes or requirements. Another issue is how to maintain data packet throughput at the point where networks are interfaced with one another. For example, the data packet routing can quickly become a bottleneck in the performance of the network if conversion between disparate media transmissions or addressing schemes is not efficient, especially when a high volume of network traffic is occurring at the point where networks are interfaced together.
0011Accordingly, a number of software and/or hardware solutions have sought to increase network traffic throughput at the point where networks are interfaced together. Some of these solutions include routers that determine the next network point that a data packet should be forwarded to within a plurality of networks. Similarly, gateways act as network node that serves as an entrance into another network. Additionally, proxy servers and firewalls act as intermediaries between network connections. Hub devices and bridge devices are also used to collect and route data packets between networks.
0012Networks desiring better security and increased throughput of operation will often dedicate computing resources to house, process, and interconnect external and internal network connections. These computing resources use the solutions discussed above (e.g., routers, gateways, firewalls, proxy servers, hub devices, bridge devices and the like). Moreover, often a plurality of solutions is deployed within the dedicated computing resources.
0013Some networks that receive a high volume of network traffic often deploy or have computing devices custom developed and installed within the networks to increase operational throughput. For example, Internet Service Providers (ISPs) can have a large number of dedicated and custom developed hardware and software resources to process and route network traffic within the ISP's network. One such hardware and software resource is a high-density server or a blade server that includes physical network interface modules that receive packets from a network. The blade server also includes a switching fabric that passes any received network data packet along to a processing resource within the blade server. The processing resource then properly translates, routes, and/or forwards the received network packet to its destination. In some cases, the destination can be another processing resource within the system.
0014Conventionally, the dedicated hardware and software resources are hardwired or statically coded by vendors to meet the needs of a particular customer. Yet, when network traffic patterns for a customer's network change (e.g., decreases or increases), the customer cannot efficiently configure the dedicated hardware and software resources provided by the vendors. As a result, to solve network traffic problems, customers purchase additional hardware and software resources to better meet their then-existing needs. As one of ordinary skill in the art readily appreciates, this is inefficient since many times existing hardware and software resources may be underutilized by the customer in another area of the customer's network.
0015Therefore, there is a need for techniques that provide improved custom configurations of hardware and software resources, which are used to facilitate the throughput and to load balance network traffic.
SUMMARY
0016Methods and systems are described for steering network packets. According to one embodiment, a unique identifier for a processing resource is received along with a mapping that associates the unique identifier with a network interface or with one or more components of the network interface. The mapping is provided to the network interface. Furthermore, the mapping is used by the network interface to steer the network packet when the network packet conforms to the mapping.
0017According to another embodiment, a network interface steering table data structure residing on a computer-readable medium is provided. The steering table data structure includes a plurality of interface identifiers, a plurality of sub-interface identifiers associated with each interface identifier. Furthermore, when a packet is received by a network interface, the packet is indexed into the data structure based on the interface identifier of the network interface receiving the packet and the sub-interface identifier associated with the line interface port of the network interface providing the packet. The indexed data structure provides an address to a processing resource where the packet is to be steered and a pointer to a specific process within the processing resource that is used to process the packet.
0018Other features of embodiments of the present invention will be apparent from the accompanying drawings and from the detailed description that follows.
BRIEF DESCRIPTION OF THE DRAWINGS
0019Embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
0020<figref idref="DRAWINGS">FIG. 1</figref> shows a diagram of a network packet steering system, according to one embodiment of the present invention;
0021<figref idref="DRAWINGS">FIG. 2</figref> shows a flow diagram of a method for steering a network packet, according to one embodiment of the present invention; and
0022<figref idref="DRAWINGS">FIG. 3</figref> shows a diagram of network packet steering system, according to an alternative embodiment of the present invention.
DETAILED DESCRIPTION
0023Methods and systems are described for steering network packets. In various embodiments of the present invention, conventional network interfaces (netmods) may be used in connection with the novel teachings, such as the load balancing architecture described herein and/or the more general configurable association of processing resources and netmods and/or line interface ports of the netmods. While embodiments of the present invention are described in the context of netmods that connect to telecommunications lines associated with network feeds, in various embodiments, the netmods may also be connected on the backend (e.g., the side opposite the network feed) to a switching fabric that is used to forward a network data packet received from the netmod to one or more processing resources. The processing resources include one or more processing elements and memory. Additionally, the processing resources may be used to translate, encrypt/decrypt, authenticate, forward and/or route any network data packets received from the switching fabric.
0024In one embodiment of the present invention, a plurality of netmods, a switching fabric, and a plurality of processing resources are assembled as a network routing/switching device, such as a blade server. The blade server is configured and distributed by Cosine Communications, Inc. of Redwood City, Calif. The system can be assembled with a plurality of additional blade servers that interface with one another. Of course as one of ordinary skill in the art readily appreciates, any hardware, firmware, and/or software configuration designed to achieve the tenets of the present disclosure can be used. Thus, all such configurations are intended to fall within the scope of the present invention.
0025Reference is made herein to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.
0026In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
0027Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software, firmware and/or by human operators.
0028Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable medium having stored thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto-optical disks, ROMs, random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions. Moreover, embodiments of the present invention may also be downloaded as a computer program product, wherein the program may be transferred from a remote computer to a requesting computer by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem or network connection).
0000Terminology
0029Brief definitions of terms used throughout this application are given below.
0030The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct connection or coupling.
0031The phrases “in one embodiment,” “according to one embodiment,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one embodiment of the present invention, and may be included in more than one embodiment of the present invention. Importantly, such phases do not necessarily refer to the same embodiment.
0032If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
0033As used herein, a “network interface” or “netmod” generally refers to a hardware and/or software computing device that connects to telecommunications lines associated with network feeds. Netmods are well known to one of ordinary skill in the art. Netmods come in a variety of configurations and are usually distinguished by the type and number of telecommunication lines that can physically connect to line interface ports of the netmod. Netmods may include firmware and/or software to process raw data being received on a line interface port. Furthermore, some software instructions may be processed within a volatile memory of the netmod. For example, some software instructions permit the recognition and separation of network data packets from a data stream being received over a line interface port.
0034The term “responsive” includes completely or partially responsive.
0035<figref idref="DRAWINGS">FIG. 1</figref> illustrates a diagram of a network packet steering system <b>100</b>, according to one embodiment of the present invention. According to the present example, the steering system <b>100</b> includes a plurality of netmods (e.g., <b>110</b> and <b>120</b>), a switching fabric <b>112</b>, and a plurality of processing resources (e.g., <b>124</b> and <b>126</b>). The netmods (e.g., <b>110</b> and <b>120</b>) are connected to telecommunication lines associated with other networks (e.g., <b>130</b> and <b>140</b>). Connections to the telecommunications lines are made via line interface ports included within the netmods (e.g., <b>110</b> and <b>120</b>).
0036The netmods (e.g., <b>110</b> and <b>120</b>) include memory and processing elements for receiving network data packets from the line interface ports or for sending network data packets out over the line interface ports. In some cases, the memory included within the netmods (e.g., <b>110</b> and <b>120</b>) is Static Random Access Memory (SRAM), which is volatile memory permitting fast access to data. Moreover, the netmods (e.g., <b>110</b> and <b>120</b>) are usually associated with a specific type of media channel (e.g., ATM, GigE, TDM, FR, and the like). Additionally, a netmod (e.g., <b>110</b> or <b>120</b>) can be wireless. Thus, netmods (e.g., <b>110</b> and <b>120</b>) need not be physically connected to a telecommunications line, but, rather, can be a transceiver for transmitting and receiving wireless (e.g., Radio Frequency (RF), Infrared (IR), Satellite, and the like) network data packets.
0037The switching fabric <b>112</b> may be hardware, firmware, and, in some instances, software instructions that receive forwarded network data packets from the netmods (e.g., <b>110</b> and <b>120</b>) and rapidly transfer the packet to an appropriate processing resource. Conventionally, switching fabric is hardwired from a specific netmod to a processing resource. The switching fabric <b>112</b> can also receive network data packets from a processing resource (e.g., <b>124</b> and <b>126</b>) and forward the network packets along to the appropriate netmod (e.g., <b>110</b> and <b>120</b>).
0038The processing resources (e.g., <b>124</b> and <b>126</b>) receive network data packets and perform a variety of translations/operations on the network data packets, such as forwarding, routing, encryption/decryption, authentication, and the like.
0039In one embodiment, the processing resources (e.g., <b>124</b> and <b>126</b>) can be configured through a Graphical User Interface (GUI) application using a configuring software application. The GUI application permits an end-user to assign a unique identifier to a processing resource (e.g., <b>124</b> or <b>126</b>). Moreover, the GUI application permits the end-user to visualize each netmod (e.g., <b>110</b> and <b>120</b>) and each line interface port assigned to each of the netmods (e.g., <b>110</b> and <b>120</b>). The GUI application then permits the end-user to make an association between a uniquely identified processing resource (e.g., <b>124</b> or <b>126</b>) and a netmod (e.g., <b>110</b> or <b>120</b>) or a particular line interface port or a sub-interface associated with a particular netmod module (e.g., <b>110</b> or <b>120</b>).
0040In one embodiment, the GUI application also permits the end-user to visually inspect the processing and memory capabilities of a particular processing resource (e.g., <b>124</b> or <b>126</b>). Thus, the end-user can intelligently make associations between processing resources (e.g., <b>124</b> and <b>126</b>) and netmods (e.g., <b>110</b> and <b>120</b>) or line interface ports. Moreover, associations can be altered as the network traffic changes to accommodate future needs of the end-user's network. Unlike conventional techniques, the associations between the processing resources (e.g., <b>124</b> and <b>126</b>) and the netmods (e.g., <b>110</b> and <b>120</b>) or line interface ports are not static and hardwired. Rather, with the present invention the associations are dynamic, virtual, and configurable.
0041Once the associations are made, the processing resource (e.g., <b>124</b> or <b>126</b>) that is being assigned pushes the association as a data structure to the volatile memory (e.g., SRAM) of the appropriate netmod (e.g., <b>110</b> or <b>120</b>). In some embodiments, the data structure is a steering table that includes the identifiers or addresses for the assigned processing resource (e.g., <b>124</b> or <b>126</b>), the assigned netmod (e.g., <b>110</b> or <b>120</b>), and any assigned line interface port identifiers or sub-interface identifiers associated with each netmod (e.g., <b>110</b> or <b>120</b>). When a network data packet is then received on the assigned netmod (e.g., <b>110</b> or <b>120</b>), the table is indexed to determine the assigned processing resource (e.g., <b>124</b> or <b>126</b>) and the processing resource's (e.g., <b>124</b> or <b>126</b>) identifier/address is provided to the switching fabric <b>112</b> in order to rapidly steer the network data packet along to the assigned processing resource (e.g., <b>124</b> or <b>126</b>).
0042In one embodiment, the table also includes a pointer or identifier to a specific process residing on the processing resource (e.g., <b>124</b> or <b>126</b>). The pointer is then automatically used by the processing resource (e.g., <b>124</b> or <b>126</b>) when the network data packet is steered to the processing resource (e.g., <b>124</b> or <b>126</b>) to cause the network data packet to be processed by the specific resource.
0043In some embodiments, a single processing resource (e.g., <b>124</b> or <b>126</b>) can push multiple associations to multiple netmods (e.g., <b>110</b> and <b>120</b>). Therefore, a single processing resource (e.g., <b>124</b> or <b>126</b>) is capable of receiving and processing network data packets from a plurality of disparate netmods (e.g., <b>124</b> and <b>126</b>) that are associated with disparate media channels (e.g., ATM, GigE, TDM, FR, wireless, and the like).
0044As one of ordinary skill in the art readily appreciates, this provides tremendous flexibility to a network design since with the teachings of the present disclosure, processing resources (e.g., <b>124</b> and <b>126</b>) can be fully utilized and processing can be more easily load balanced. Therefore, an enterprise can dynamically configure or alter the steering system <b>100</b> of the present invention to accommodate changes in the enterprise's network traffic without the need to purchase additional expensive hardware and software solutions.
0045In some embodiments of the present disclosure, the steering table can be more complex and used to have the netmods (e.g., <b>110</b> and <b>120</b>) perform filter operations on any received network data packet. These filter operations can be used to determine the context (e.g., state) of a netmod (e.g., <b>110</b> or <b>120</b>) when a network data packet is received, determine the present volume of traffic on a netmod (e.g., <b>110</b> or <b>120</b>), and determine the content (e.g., media type) of a network packet. Of course a variety of additional filter operations can be identified in the steering table and processed by the netmods (e.g., <b>110</b> and <b>120</b>). All such filter operations are intended to fall within the broad scope of the present disclosure.
0046The steering system <b>100</b> depicted in <figref idref="DRAWINGS">FIG. 1</figref> is presented for purposes of illustration only, and as one of ordinary skill in the art appreciates, a variety of additional configurations are permissible within the scope of the present invention. Furthermore, it is readily apparent to one of ordinary skill in the art that the steering table included within the netmods (e.g., <b>110</b> and <b>120</b>) permits the netmods (e.g., <b>110</b> and <b>120</b>) to dynamically acquire intelligence about an incoming network data packet in order to more efficiently steer the incoming data packet. This is a significant improvement over what has been conventionally done, which is statically and rigidly defined in the hardware of the routing/switching computing devices.
0047<figref idref="DRAWINGS">FIG. 2</figref> illustrates a flow diagram of a method <b>200</b> for steering a network packet, according to the present invention. In one embodiment, of <figref idref="DRAWINGS">FIG. 2</figref> the method <b>200</b> is implemented within a high-density server or blade server having a plurality of netmods, a switching fabric, and a plurality of processing resources. Of course, any configuration of computing devices implementing method <b>200</b> is intended to fall within the scope of the present disclosure.
0048In <b>210</b>, a unique identifier is received by a processing resource. The unique identifier is used to distinguish the processing resource from other processing resources. The processing resource is used to route, forward, authenticate, encrypt/decrypt, or perform other operations against a network packet. In one embodiment, the unique identifier is received from a GUI application interfaced with the processing resource. Moreover, the unique identifier is modifiable and configurable by the GUI application. Of course any software application, including command line interfaces, can be used to provide the processing resource with the unique identifier.
0049Additionally, a mapping, in <b>220</b>, is received by the processing resource. The mapping logically associates the unique identifier of the processing resource with a netmod or with one or more components of the netmod. In one embodiment, the components represent line interface ports embodied in the netmod. The netmod receives and transmits network packets from and to other computing devices.
0050The mapping, in one embodiment, is received from the GUI application. Further, as depicted in <b>222</b>, and in some cases, the mapping is represented as a table data structure (e.g., steering table) in the memory of the processing resource. The mapping, mapping in some embodiments, includes an identifier/address of the processing resource, an identifier for the netmod, a plurality of identifiers for line interface ports or sub-interfaces included on the netmod, and a pointer to a specific process that resides on the processing resource and is used to process any steered network packets. Additionally, the GUI application can be used to publish to an end-user the processing and memory capabilities of the processing resource. Therefore, the end-user can intelligently create and dynamically alter the mapping based on the end-user's network traffic patterns.
0051In <b>230</b>, the mapping is provided by the processing resource to the netmod. In one instance, the mapping is provided as an in RAM (e.g., SRAM, depicted in <b>232</b>) table data structure to the netmod for more efficient processing by the netmod. Moreover, the mapping can be dynamically pushed to the netmod from the processing resource. In this way, the mapping is configurable and easily altered as network traffic patterns change.
0052Once the netmod has the mapping, then, in <b>240</b>, when the netmod receives a network packet, the mapping can be accessed or inspected in <b>250</b>. Upon inspecting the mapping, the netmod associates the unique identifier/address of the assigned processing resource and any process pointer with the network packet and passes the information off to the switching fabric, which rapidly steers the network packet to the processing resource in <b>260</b> and automatically performs any process against the network packet, which was identified by any process pointer.
0053Therefore, unlike conventional hardwired network switches, the mapping of the present invention represents a virtual switch that permits the netmod to perform Layer 1 and Layer 2 steering on incoming network packets. Moreover, the virtual switch is easily altered and configured to meet the needs of changing network traffic patterns.
0054<figref idref="DRAWINGS">FIG. 3</figref> illustrates a diagram of another network packet steering system <b>300</b>, according to the present invention. The steering system <b>300</b> includes one or more netmods (e.g., <b>310</b> and <b>320</b>), one or more processing resources (e.g., <b>330</b> and <b>340</b>). Each netmod (e.g., <b>310</b> or <b>320</b>) includes a plurality of line interface ports (e.g., <b>312</b>, <b>314</b>, <b>322</b>, and <b>324</b>). Also, in some embodiments, a switching fabric is interposed between the netmods (e.g., <b>310</b> and <b>320</b>) and the processing resources (e.g., <b>330</b> and <b>340</b>) (not depicted in <figref idref="DRAWINGS">FIG. 3</figref>).
0055The processing resources (e.g., <b>330</b> and <b>340</b>) are configurable, uniquely identified, and assigned to a number of the netmods (e.g., <b>310</b> and <b>320</b>) or to a number of the line interface ports (e.g., <b>312</b>, <b>314</b>, <b>322</b>, and <b>324</b>). In one embodiment, configuration of the processing resources (e.g., <b>330</b> and <b>340</b>) occurs through a GUI application communicating with the processing resources (e.g., <b>330</b> and <b>340</b>). The GUI application permits dynamic modification to the configured assignment. Moreover, the configured assignment can be intelligently made by an end-user of the GUI application when the processing and memory capabilities of the processing resources (e.g., <b>330</b> and <b>340</b>) are visualized and published through the GUI application to the end-user.
0056Configured assignments made within the processing resources (e.g., <b>330</b> and <b>340</b>) are pushed from the respective processing resources (e.g., <b>330</b> and <b>340</b>) to the corresponding netmods (e.g., <b>310</b> and <b>320</b>). The configured assignments can be represented as a steering table inside the netmod's (e.g., <b>310</b> and <b>320</b>) volatile memory (e.g., SRAM). The netmods (e.g., <b>310</b> and <b>320</b>) use the configured assignments when receiving an incoming network packet and the unique identifier associated with the appropriate processing resource (e.g., <b>330</b> or <b>340</b>) in order to steer the incoming network packet to the designated processing resource (e.g., <b>330</b> or <b>340</b>).
0057One technique to access the steering table is to index the incoming network packet into the table by the incoming network packet's channel identifier to acquire the appropriate unique identifier for the processing resource (e.g., <b>330</b> or <b>340</b>). Once the unique identifier is associated with the incoming packet it is readily steered to the designated processing resource (e.g., <b>330</b> or <b>340</b>). Corresponding, the identifier, in some embodiments, is an address for the appropriate processing resource (e.g., <b>330</b> or <b>340</b>). Moreover, in one embodiment, the configured assignment also identifies a pointer to a specific process on the appropriate processing resource (e.g., <b>330</b> or <b>340</b>), which is used to automatically process the incoming packet on the appropriate processing resource (e.g., <b>330</b> or <b>340</b>).
0058In some instances, the configured assignments can also be used to identify one or more filter operations that the processing resource (e.g., <b>330</b> or <b>340</b>) wants the netmods (e.g., <b>310</b> and <b>320</b>) to perform on the incoming network packet before steering the incoming network packet. Some example filter operations can include, detecting and communicating a current volume of network traffic, detecting and communicating a content format (e.g., media format) of the incoming packet, and detecting and communicating a context (e.g., processing state) associated with the netmods (e.g., <b>310</b> and <b>320</b>) when the incoming network packet is received.
CONCLUSION
0059Methods and systems detailed above permit improved network packet steering. In various embodiments, these methods and systems facilitate the creation of virtual switches. In contrast, traditional approaches have relied on hardwired and static implementations of switches. Accordingly, embodiments of the present invention permits better utilization and load balancing of an enterprise's network resources.
0060Furthermore, the virtual switches of embodiments of the present invention are dynamically configurable to meet the changing needs of an enterprise's network traffic. In some embodiments, the configuration of the virtual switches can be altered using a GUI application in communication with a processing resource. Moreover, the processing and memory capabilities of the processing resource can be published and made available within the GUI application. In this way, an enterprise can monitor and alter network traffic as needed in accordance with the teachings of various embodiments of the present invention, without the need to acquire additional hardware and software resources.
0061The foregoing description of specific embodiments reveals the general nature of the invention sufficiently that others can, by applying current knowledge, readily modify and/or adapt it for various applications without departing from the generic concept. Therefore such adaptations and modifications are within the meaning and range of equivalents of the disclosed embodiments. The phraseology or terminology employed herein is for the purpose of description and not of limitation. Accordingly, the invention embraces all such alternatives, modifications, equivalents and variations as fall within the spirit and scope of the appended claims.
Contents7
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9967200B2 | Cited by | United States of America | Applicant |
| US9853917B2 | Cited by | United States of America | Applicant |
| WO2013101024A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8601110B2 | Cited by | United States of America | Applicant |
| US9667604B2 | Cited by | United States of America | Applicant |
| US9853948B2 | Cited by | United States of America | Applicant |
| US9509588B2 | Cited by | United States of America | Applicant |
| US2011122872A1 | Cited by | United States of America | Pre-grant |
| US2011235649A1 | Cited by | United States of America | Pre-grant |
| US9036629B2 | Cited by | United States of America | Applicant |
| US2001000194A1 | Cites | United States of America | Search report |
| US2003074388A1 | Cites | United States of America | Search report |
| US2003084219A1 | Cites | United States of America | Search report |
| US2004160900A1 | Cites | United States of America | Search report |
| US2004199567A1 | Cites | United States of America | Search report |
| US2004199568A1 | Cites | United States of America | Search report |
| US2004199569A1 | Cites | United States of America | Search report |
| US4590468A | Cites | United States of America | Applicant |
| US4667287A | Cites | United States of America | Applicant |
| US5201049A | Cites | United States of America | Search report |
| US5371852A | Cites | United States of America | Applicant |
| US5473599A | Cites | United States of America | Applicant |
| US5490252A | Cites | United States of America | Applicant |
| US5550816A | Cites | United States of America | Applicant |
| US5581705A | Cites | United States of America | Applicant |
| US5633866A | Cites | United States of America | Applicant |
| US5745778A | Cites | United States of America | Applicant |
| US5825772A | Cites | United States of America | Applicant |
| US5841973A | Cites | United States of America | Applicant |
| US5841990A | Cites | United States of America | Applicant |
| US5875290A | Cites | United States of America | Applicant |
| US5892924A | Cites | United States of America | Applicant |
| US5920705A | Cites | United States of America | Applicant |
| US5963555A | Cites | United States of America | Applicant |
| US5964847A | Cites | United States of America | Applicant |
| US5987521A | Cites | United States of America | Applicant |
| US6014382A | Cites | United States of America | Applicant |
| US6014669A | Cites | United States of America | Applicant |
| US6032193A | Cites | United States of America | Applicant |
| US6047330A | Cites | United States of America | Applicant |
| US6069895A | Cites | United States of America | Applicant |
| US6085238A | Cites | United States of America | Applicant |
| US6098110A | Cites | United States of America | Applicant |
| US6108699A | Cites | United States of America | Applicant |
| US6118791A | Cites | United States of America | Applicant |
| US6137777A | Cites | United States of America | Applicant |
| US6169739B1 | Cites | United States of America | Applicant |
| US6169793B1 | Cites | United States of America | Applicant |
| US6175867B1 | Cites | United States of America | Applicant |
| US6192051B1 | Cites | United States of America | Applicant |
| US6220768B1 | Cites | United States of America | Applicant |
| US6226788B1 | Cites | United States of America | Applicant |
| US6243580B1 | Cites | United States of America | Applicant |
| US6246682B1 | Cites | United States of America | Applicant |
| US6249519B1 | Cites | United States of America | Applicant |
| US6256295B1 | Cites | United States of America | Applicant |
| US6260072B1 | Cites | United States of America | Applicant |
| US6260073B1 | Cites | United States of America | Applicant |
| US6266695B1 | Cites | United States of America | Applicant |
| US6278708B1 | Cites | United States of America | Applicant |
| US6286038B1 | Cites | United States of America | Applicant |
| US6295297B1 | Cites | United States of America | Applicant |
| US6298130B1 | Cites | United States of America | Applicant |
| US6330602B1 | Cites | United States of America | Applicant |
| US6338092B1 | Cites | United States of America | Applicant |
| US6343083B1 | Cites | United States of America | Applicant |
| US6405262B1 | Cites | United States of America | Applicant |
| US6414595B1 | Cites | United States of America | Applicant |
| US6434619B1 | Cites | United States of America | Applicant |
| US6438612B1 | Cites | United States of America | Applicant |
| US6449650B1 | Cites | United States of America | Applicant |
| US6453406B1 | Cites | United States of America | Applicant |
| US6463061B1 | Cites | United States of America | Applicant |
| US6466976B1 | Cites | United States of America | Applicant |
| US6493349B1 | Cites | United States of America | Applicant |
| US6496935B1 | Cites | United States of America | Applicant |
| US6526056B1 | Cites | United States of America | Applicant |
| US6532088B1 | Cites | United States of America | Applicant |
| US6542466B1 | Cites | United States of America | Applicant |
| US6542502B1 | Cites | United States of America | Applicant |
| US6542515B1 | Cites | United States of America | Applicant |
| US6553423B1 | Cites | United States of America | Applicant |
| US6556544B1 | Cites | United States of America | Applicant |
| US6608816B1 | Cites | United States of America | Applicant |
| US6609153B1 | Cites | United States of America | Applicant |
| US6611498B1 | Cites | United States of America | Applicant |
| US6611522B1 | Cites | United States of America | Applicant |
| US6625169B1 | Cites | United States of America | Applicant |
| US6633571B1 | Cites | United States of America | Applicant |
| US6636516B1 | Cites | United States of America | Applicant |
| US6639897B1 | Cites | United States of America | Applicant |
| US6640248B1 | Cites | United States of America | Applicant |
| US6654787B1 | Cites | United States of America | Applicant |
| US6658013B1 | Cites | United States of America | Applicant |
| US6668282B1 | Cites | United States of America | Applicant |
| US6680922B1 | Cites | United States of America | Applicant |
| US6694437B1 | Cites | United States of America | Applicant |
| US6697359B1 | Cites | United States of America | Applicant |
| US6697360B1 | Cites | United States of America | Applicant |
| US6732314B1 | Cites | United States of America | Applicant |
10 members in 1 office
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 16326102 | United States of America | A |
Members10
| Document | Office | Kind | |
|---|---|---|---|
| US2003223418A1 | United States of America | A1 | |
| US7203192B2 | United States of America | B2 | |
| US2007147368A1 | United States of America | A1 | |
| US2009238181A1 | United States of America | A1 | |
| US8068503B2This record | United States of America | B2 | |
| US2012069850A1 | United States of America | A1 | |
| US8306040B2 | United States of America | B2 | |
| US8638802B2 | United States of America | B2 | |
| US2014161136A1 | United States of America | A1 | |
| US9215178B2 | United States of America | B2 |
111 transactions on the USPTO file
Allowed after 3 non-final rejections, 1 final rejection and 2 appeals.
- Non-final rejections
- 3
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 2
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Appeal Brief FiledAP.B | AP.B | |
| Terminal Disclaimer FiledDIST | DIST | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Notice of Appeal FiledN/AP | N/AP | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Appeal Brief FiledAP.B | AP.B | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Notice of Appeal FiledN/AP | N/AP | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Preliminary AmendmentA.PE | A.PE | |
| Withdraw Flagged for 5/25W525 | W525 | |
| Flagged for 5/25F525 | F525 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF |
Numbers
- Publication
- 8068503
- Application
- 11684614
Titles
- English
- Network packet steering via configurable association of processing resources and netmods or line interface ports
Patent term adjustment
- A delay
- +369 daysthe office missed an examination deadline
- B delay
- +308 dayspendency past three years
- Applicant delay
- −122 days
- Net adjustment
- 555 days
Classification
- CPC, 8
- H04L12/4625
- H04L47/2441
- H04L47/2491
- H04L49/65
- H04L49/254
- H04L49/30
- H04L47/10
- H04L47/22
- IPC, 5
- H04L12 28
- H04L47 22
- H04L12 46
- H04L12 56
- H04L47 2491