Embodiments of the invention are generally related to the field of data networking and, in particular, to a dynamically adaptable communications processor and associated methods.
Data networking is a term colloquially applied to any architecture wherein electronic devices (e.g., computer systems, communication devices) are communicatively coupled to one another through a network architecture. The network architecture is typically comprised of a number of network devices, e.g., routers, switches, and hubs, which serve to route data packets (sometimes colloquially referred to as datagrams) between electronic devices.
Those skilled in the art will appreciate that there are many different types of networks and an associated number of communication protocols through which such devices communicate. Typically, a network device is designed to operate in one of the number of networking environments and, in this regard, will include a communications processor dedicated to processing data packets in accordance with a single communication protocol. With the acceptance and proliferation of multiple network types and associated protocols, it has become desirable to create a network device that functions in multiple network architectures and, in this regard, with multiple network protocols.
A conventional approach to such multi-network networking devices generally requires that the network device be endowed with multiple communications processors, i.e., one each for each of the communication protocols to be supported by the network device. Employing multiple communication devices within such a network device can, however, greatly increase the cost of the network device. Moreover, such a solution, which is fundamentally based in hardware, is not extensible to accommodate future network architectures and/or communication protocols.
Another, more recent, approach to such a multi-network networking device is to fabricate a communications processor with the circuitry necessary to support a predetermined number of communication protocols. Again, such an approach is rather costly, as the fabricated device does not really reduce the amount of circuitry necessary to support the pre-determined number of communication protocols, but merely integrates it within a single package. Moreover, as above, inasmuch as the solution is fundamentally based on hardware, it is not extensible to accommodate newly developed networking architectures or communication protocols.
Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements and in which:
A dynamically adaptable communications processor (DACP) and associated methods are described. In the following description, for purposes of explanation, numerous specific details are set forth. It will be apparent, however, to one skilled in the art that embodiments of the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the understanding of this description.
Reference in the foregoing specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
According to one aspect of the invention, the DACP dynamically reconfigures itself to process data packets in accordance with any of a number of communication protocols. In this regard, a host device integrated with the DACP may well be used in any of a number of disparate network architectures. Moreover, the DACP is extensible to support communication protocols and network architectures not yet developed.
Example Operating Environment and Network Device
As used herein, each of network type 1 element 110, network type 2 element 120 through network type N element 130 may represent a wide variety of network elements known in the art such as, e.g., a desktop computing platform, a notebook computing platform, a handheld device (e.g., a personal digital assistant), a mobile communications device, and the like. In addition, each of network type 1 element 210, network type 2 element 120 through network type N element 130 may represent a wide variety of network devices known in the art such as, e.g., hubs, routers, switches, and the like, that may or may not include the teachings of the embodiments of the invention. Network type 1 element 110, network type 2 element 120 through network type N element 130 are intended to represent such conventional devices currently known in the art. Accordingly, the architectural details of network type 1 element 110, network type 2 element 120 through network type N element 130 need not be described further.
As used herein, but for the integration of ENI 104 incorporating a DACP as described more fully below, network device 102 is intended to represent any of a number of network management devices (hub, switch, router, etc.). Accordingly, the architectural details of network device 102, other than ENI 104, need not be described further.
Example Network Interface with Dynamically Adaptable Communications Processor
I/O interface(s) 202 are intended to represent a wide variety of hardware and software used to connect a network device with a communication channel. I/O buffer(s) 204 are intended to represent any of a wide variety of memory systems known in the art. According to one implementation, I/O buffer(s) 204 include receive data structure(s), or queues, and transmit data structure(s). According to one example implementation, network device 102 receives data packets from network type 1 element 110, network type 2 element 120 through network type N element 130 via I/O interface(s) 202, and such data packets are stored in receive queues of I/O buffer(s) 204. DACP 206 receives data packets from the receive queues, processes the data packets, and transmits processed data packets to the transmit queues for transmission to another network type 1 element 110, network type 2 element 120 through network type N element 130. It will be appreciated by those skilled in the art that I/O buffer(s) 204 may be comprised of any of a number of many different types of physical memory/storage devices.
DACP 206 is depicted comprising control logic 210, memory system 220 and algorithm-based processing engine 230. Those skilled in the art will appreciate that memory system 220 may be located outside of DACP 206, and that memory system 220 may be coupled with ENI 200 or network device 102. Although depicted as a number of disparate functional items, those skilled in the art will appreciate that one or more of such elements may well be combined into single functional entities. Alternatively, certain elements may be split into multiple functional elements.
Control logic 210 controls the dynamic adaptability aspect of DACP 206. In this regard, control logic 210 determines a communication protocol associated with a selected one of a number of channels coupled with ENI 200 supplying a data packet. In accordance with one aspect of the invention, developed more fully below, having identified the communication protocol, control logic 210 retrieves configuration information corresponding to the communication protocol and configures DACP 206 to process the received data packet in accordance with the identified channel.
In connection with processing the data packet, control logic 210 invokes an instance of algorithm-based processing engine 230. According to one aspect of the invention, developed more fully below, algorithm-based processing engine 230 performs operations on the content of data packets and selects outputs from the operations in order to generate a processing parameter in accordance with the configuration of DACP 206.
Control logic 210 is intended to represent any of a wide variety of control logic known in the art such as, for example, microprocessor(s), microcontroller(s), programmable logic device(s) (PLD), field programmable gate arrays (FPGA), state machine(s) and the like. Alternatively, control logic 210 may well be content (e.g., executable instructions) which, when executed by a computing appliance, implement the control features described herein.
Memory system 220 is depicted comprising configuration memory 222, context memory 224 and operation output memory 226. As used herein, memory system 220 is intended to represent any of a wide variety of memory systems known in the art. Those skilled in the art will appreciate that memory system 220 may well be comprised of any of a number of many different types of physical memory/storage devices.
Configuration memory 222 includes configuration information for a wide variety of disparate communication protocols, including, e.g., asynchronous transfer mode (ATM), packet over synchronous optical network (POS) and generic framing procedure (GFP). While the details of such communication protocols are not required to appreciate the teachings of embodiments of the invention, for a more complete understanding of such communication protocols, the reader is directed to, e.g., International Telecommunications Union Telecommunication Standardization Sector (ITU-T), Recommendation I.432.5, “B-ISDN User-Network Interface—Physical Layer Specification: 25 600 Kbit/s Operation,” June 1997; Internet Engineering Task Force, Network Working Group Request for Comments 2615, “PPP over SONET and SDH,” June 1999; ITU-T, Recommendation G.7041/Y.1303, “Generic Framing Procedure (GFP),” December 2001. Such references are incorporated herein by reference for all purposes.
According to one example implementation, each entry of configuration memory 222 is associated with a particular communication protocol. As will be discussed more fully below, control logic 210, having determined the communication protocol associated with a channel supplying a data packet, accesses configuration memory 222, retrieves configuration information corresponding to the communication protocol and configures DACP 206 to process the data packet.
Context memory 224 includes data corresponding to previously processed portions of a data packet. According to one example implementation, each entry of context memory 224 is associated with a portion of a previously processed data packet received from a channel. As will be discussed more fully below, control logic 210 reads context data from context memory 224 in connection with processing a data packet, part of which has been previously processed. In addition, as will be discussed more fully below, control logic 210 stores processed portions of a data packet in context memory 224 when control logic 210 reconfigures DACP 206 in connection with receiving a new data packet from a different channel.
Operation output memory 226 includes output from operations performed on the content (e.g., bits, bytes, words, etc.) of data packets. According to one example implementation, each entry of operation output memory 226 comprises the output of an operation, such as an XOR operation. As will be discussed more fully below, algorithm-based processing engine 230 retrieves from operation output memory 226 outputs associated with an algorithm for generating a processing parameter, in accordance with the configuration of DACP 206.
Example Data Structure(s)
According to one example implementation, one of the entries 300 represents POS, another represents ATM and another represents GFP. In accordance with the teachings of an embodiment of the invention, when receiving a data packet from a channel, control logic 210 retrieves from an entry 300 configuration information corresponding to the communication protocol associated with the channel supplying the data packet. As will be developed more fully below, control logic 210 uses the configuration information to reconfigure DACP 206 into a communications processor of the type associated with the communication protocol.
As will be developed more fully below, when DACP 206 receives a data packet from a channel via I/O interface(s) 202 and I/O buffer(s) 204, control logic 210 reads an entry 400 comprising previously processed portions of the data packet. When DACP 206 receives a new data packet from a different channel, control logic 210 stores processed portions of the data packet in an entry 400 and retrieves context data regarding the new data packet. Context data determines the point at which control logic 210 previously stopped processing the data packet, only a portion of which was processed during the processing time (e.g., the amount of bandwidth) assigned to one or more channels providing the portions of the data packet.
Example Operation and Implementation
Having introduced the operating environment and architectural elements of the invention above, attention is now directed to
According to the illustrated example implementation of
At block 606, control logic 210 retrieves configuration information corresponding to the communication protocol associated with the channel. According to one example implementation, control logic 210 retrieves configuration information from configuration memory 222. At block 608, control logic 210 utilizes the configuration information to configure DACP 206 to process data packets in accordance with the communication protocol associated with the channel from which the data packet is received.
At block 610, control logic 210 reads context data corresponding to the previously processed portion of the data packet. According to one example implementation, control logic 210 reads context data from context memory 224. Those skilled in the art will appreciate that if no part of the data packet has been previously processed, control logic 210 does not read context data in connection with processing the data packet.
At block 612, control logic 210 processes the data packet in accordance with the configuration of DACP 206. According to one example implementation, control logic 210 processes the data packet by adding the network addresses of a transmitting network element and of a destination network element, and by inserting idlers in the data packet. Those skilled in the art will appreciate that processing a data packet may involve different, fewer or additional processing operations. In an example embodiment, control logic 210 processes the data packet for a period corresponding to the amount of bandwidth assigned to the channel supplying the data packet.
In accordance with one example embodiment, control logic 210 invokes an instance of algorithm-based processing engine 230 in connection with processing the data packet. Algorithm-based processing engine 230 generates a processing parameter based an algorithm associated with the communication protocol for which DACP 206 is configured to process data packets. In one example implementation, algorithm-based processing engine 230 generates a processing parameter comprising a cyclic redundancy check (CRC). As is known in the art, a CRC determines whether a data packet contains errors. In another example implementation, algorithm-based processing engine 230 generates a processing parameter comprising a scrambling parameter. As is known in the art, a scrambling parameter provides density of transmission of a data packet. Those skilled in the art will appreciate that the processing parameter may comprise any of a plurality of parameters generated in connection with processing a packet.
In accordance with one aspect of an example embodiment, algorithm-based processing engine 230 performs operations on the content of the data packet, e.g., an XOR operation. As is readily understood by one of ordinary skill in the art, algorithm-based processing engine 230 may perform the operations on the content either in series or in parallel without deviating from the spirit and scope of embodiments of the invention. According to another aspect of the example embodiment, algorithm-based processing engine 230 stores the output resulting from each operation in operation output memory 226.
According to another aspect of the example embodiment, algorithm-based processing engine 230 retrieves selected outputs from operation output memory 226 in accordance with the algorithm associated with the processing parameter being generated and the communication protocol for which DACP 206 is configured to process data packets. For example, if algorithm-based processing engine 230 is generating a CRC when DACP 206 is configured to process data packets received from a POS channel, the algorithm for generating the CRC is x43+1. Having performed an XOR operation by passing the content of the data packet through flip-flop gates and having stored the outputs, algorithm-based processing engine 230 retrieves from operation output memory 226 the output of the 43rd flip-flop gate in order to generate the CRC. Similarly, for example, if algorithm-based processing engine 230 is generating a CRC when DACP 206 is configured to process data packets received from a GFP channel, the algorithm is x16+x12+x5+1. Accordingly, in order to generate the CRC, algorithm-based processing engine 230 retrieves from operation output memory 226 the outputs of the 16th, 12th and 5th flip-flop gates.
Continuing with method 600, at block 614, control logic 210 transmits the processed data packet to a transmit buffer of I/O buffers 204. At block 616, DACP 206 receives a new data packet from a different channel. At block 618, control logic 210 determines the communication protocol associated with the channel supplying the new data packet. At block 620, control logic 210 determines whether the communication protocol associated with channel supplying the new data packet is the same as the communication protocol associated with the channel that supplied the most recently processed data packet.
If control logic 210 determines that the communication protocol associated with the channel supplying the new data packet is the same as the communication protocol associated with the channel that supplied the most recently processed data packet, method 600 continues in accordance with blocks 610 through 620.
Conversely, if control logic 210 determines that the communication protocol associated with the channel supplying the new data packet is different, at block 622, control logic 210 stores in configuration memory 222 configuration information associated with the channel that supplied the most recently processed data packet. At block 624, control logic 210 stores in context memory 224 any context data corresponding to processed portions of the most recently processed data packet. At block 626, control logic 210 retrieves configuration information corresponding to the communication protocol associated with the channel supplying the new data packet. At block 628, method 600 repeats blocks 608 through 620, as necessary.
Alternate Embodiment(s)
In the description above, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the invention. It will be apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
Embodiments of the 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 an electronic device (such as a personal computer) to perform a process according to the embodiments of the invention. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnet or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions. Moreover, the embodiments of the 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).
In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes can be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, are to be regarded in an illustrative rather than a restrictive sense. i.e., the particular embodiments are not provided to limit the invention but to illustrate it. The scope of the embodiments of the invention is not to be determined by the specific examples provided above but only by the claims below.
Number | Name | Date | Kind |
---|---|---|---|
4003033 | O'Keefe et al. | Jan 1977 | A |
4713806 | Oberlander et al. | Dec 1987 | A |
5202964 | Crouch | Apr 1993 | A |
5490252 | Macera et al. | Feb 1996 | A |
5581790 | Sefidvash | Dec 1996 | A |
5699350 | Kraslavsky | Dec 1997 | A |
5726984 | Kubler et al. | Mar 1998 | A |
5828655 | Moura et al. | Oct 1998 | A |
5926501 | Souissi et al. | Jul 1999 | A |
5954796 | McCarty et al. | Sep 1999 | A |
6049826 | Beser | Apr 2000 | A |
6108350 | Araujo et al. | Aug 2000 | A |
6118796 | Best et al. | Sep 2000 | A |
6145024 | Maezawa et al. | Nov 2000 | A |
6151632 | Chaddha et al. | Nov 2000 | A |
6219706 | Fan et al. | Apr 2001 | B1 |
6236647 | Amalfitano | May 2001 | B1 |
6237029 | Master et al. | May 2001 | B1 |
6295532 | Hawkinson | Sep 2001 | B1 |
6343313 | Salesky et al. | Jan 2002 | B1 |
6347091 | Wallentin et al. | Feb 2002 | B1 |
6351469 | Otani et al. | Feb 2002 | B1 |
6356951 | Gentry, Jr. | Mar 2002 | B1 |
6377578 | Waller | Apr 2002 | B1 |
6381227 | Fielding et al. | Apr 2002 | B1 |
6466986 | Sawyer et al. | Oct 2002 | B1 |
6571291 | Chow | May 2003 | B1 |
6640101 | Daniel | Oct 2003 | B1 |
6640239 | Gidwani | Oct 2003 | B1 |
6647428 | Bannai et al. | Nov 2003 | B1 |
6651099 | Dietz et al. | Nov 2003 | B1 |
6687765 | Surugucchi et al. | Feb 2004 | B2 |
6691192 | Ajanovic et al. | Feb 2004 | B2 |
6760772 | Zou et al. | Jul 2004 | B2 |
6834298 | Singer et al. | Dec 2004 | B1 |
6839349 | Ambe et al. | Jan 2005 | B2 |
6842429 | Shridhar et al. | Jan 2005 | B1 |
6842454 | Metcalf, III | Jan 2005 | B2 |
6850521 | Kadambi et al. | Feb 2005 | B1 |
6888830 | Snyder, II et al. | May 2005 | B1 |
6934756 | Maes | Aug 2005 | B2 |
6975597 | Baker et al. | Dec 2005 | B1 |
7099584 | Narvaez et al. | Aug 2006 | B1 |
20010047434 | Liu | Nov 2001 | A1 |
20020083190 | Kamiya et al. | Jun 2002 | A1 |
20020152305 | Jackson et al. | Oct 2002 | A1 |
20020176418 | Hunt et al. | Nov 2002 | A1 |
20030039234 | Sharma et al. | Feb 2003 | A1 |
20030063562 | Sarkinen et al. | Apr 2003 | A1 |
20030120799 | Lahav et al. | Jun 2003 | A1 |
20030208561 | Hoang et al. | Nov 2003 | A1 |
20030227906 | Hallman | Dec 2003 | A1 |
Number | Date | Country | |
---|---|---|---|
20040003100 A1 | Jan 2004 | US |