|Publication number||US7103007 B2|
|Application number||US 10/187,180|
|Publication date||5 Sep 2006|
|Filing date||27 Jun 2002|
|Priority date||28 Jun 1996|
|Also published as||US6434120, US20020163891|
|Publication number||10187180, 187180, US 7103007 B2, US 7103007B2, US-B2-7103007, US7103007 B2, US7103007B2|
|Inventors||Shankar Natarajan, Gregory A. Fowler|
|Original Assignee||Cisco Technology, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (101), Non-Patent Citations (11), Referenced by (13), Classifications (13), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation, pursuant to 35 U.S.C. Section 120, of prior U.S. Pat. application Ser. No. 09/140,178 entitled “AUTOSENSING LMI PROTOCOLS IN FRAME RELAY NETWORKS,” by Fowler et al., filed on Aug. 25, 1998, now U.S. Pat. No. 6,434,120 which is a continuation of U.S. Pat. Application Ser. No. 08/672,674 entitled “AUTOSENSING LMI PROTOCOLS IN FRAME RELAY NETWORKS,” by Fowler et al., filed on Jun. 28, 1996 now U.S. Pat. No. 5,802,042.
1. Field of the Invention
This invention relates to autosensing LMI protocols in frame relay networks.
2. Description of Related Art
Frame relay networks include a number of remote stations, each coupled to another; one node may be designated as a server node. When the number of remote stations is large, or if the remote station is geographically remote, it can be difficult to assure that remote stations are properly configured for use with the network, due in part to lack of technical resources. One aspect of properly configuring the remote station is to assure that it uses the correct one of multiple possible protocols for the local management interface (LMI) for the connection between the remote station and an edge of the frame relay network at a frame relay switch; these possible protocols are called LMI protocols.
In one system for automated configuration of a remote station, the remote station attempts to communicate with frame relay network equipment using a series of LMI protocols, each tested in sequence. While this technique achieves the goal of sensing LMI protocols, it has the drawbacks of taking more time than necessary, and of predetermining an order for selection of an LMI protocol which may not ultimately be preferred.
Accordingly, it would be advantageous to provide an improved technique for autosensing LMI protocols in frame relay networks.
The invention provides a method and system for auto-sensing LMI protocols in frame relay networks. When a router (or other client process) is first coupled to a frame relay network, it automatically configures the local management interface (LMI) to use one of a selected set of possible LMI protocols, by generating a set of protocol requests for a plurality of protocols, and by thereafter simultaneously listening for protocol responses from the frame relay network equipment or switch. In a preferred embodiment, multiple valid responses from the frame relay network equipment are assigned priority in response to which valid response is last to arrive.
In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. However, those skilled in the art would recognize, after perusal of this application, that embodiments of the invention may be implemented using a computer at each site operating under program control, and that modification of a set of general purpose computers to implement the process steps and data structures described herein would not require undue invention.
A method 100 of autosensing LMI protocols is performed in a frame relay network.
At a flow point 110, a new router has been added to a frame relay network.
In a preferred embodiment this method is performed for a new router being added to a frame relay network and downloading configuration information from a configuration server on the frame relay network. However, in alternative embodiments, the method may be performed for any client process which is establishing or re-establishing contact with a server process.
At a step 121, the router is powered up and attempts to contact the frame relay network equipment or switch.
At a step 122, the router transmits a “STATUS ENQUIRY” message using a first LMI (local management interface) protocol. In a preferred embodiment, this first LMI protocol is the “ANSI” protocol, as described in “Integrated Services Digital Network (ISDN)—Signaling Specification for Frame Relay Bearer Service for Digital Subscriber Signaling System Number 1 (DSS1)”, ANSI Document T1.617-1991, Annex D, hereby incorporated by reference as if fully set forth herein.
At a step 123, after transmitting the message, the router sets a timeout for a response to that message, and starts a timer interrupt to occur on that timeout. This timeout is preferably set for T391 seconds; the T391 timeout is described on page 75, table D.2, of ANSI Document T1.617-1991, and is preferably between about 5 to about 30 seconds, such as about 10 seconds. The router listens on LMI management channel number zero (0) for a response.
At a step 124, the router transmits a “STATUS ENQUIRY” message using a second LMI (local management interface) protocol. In a preferred embodiment, this second LMI protocol is the “ITU” protocol, as described in “International Telegraph and Telephone Consultative Committee—Digital Subscriber Signaling System No. 1 (DSS1). Signaling Specification for Frame Mode Basic Call Control, CCITT Document Q.933, 1992, hereby incorporated by reference as if fully set forth herein.
At a step 125, after transmitting the message, the router sets a timeout for a response to that message, and starts a timer interrupt to occur on that timeout. This timeout is preferably set for T391 seconds. The router listens on LMI management channel number zero (0) for a response.
At a step 126, the router transmits a “STATUS ENQUIRY” message using a third LMI (local management interface) protocol. In a preferred embodiment, this third LMI protocol is the LMI protocol described in “Frame Relay Specification with Extensions—Based on Proposed T1S1 Standards”, Document Number 001-208966, Revision 1.0 (Sep. 18, 1990), sometimes called the “gang of four” protocol and herein called the “LMI” protocol, hereby incorporated by reference as if fully set forth herein.
At a step 127, after transmitting the message, the router sets a timeout for a response to that message, and starts a timer interrupt to occur on that timeout. This timeout is preferably set for nT1 seconds; the nT1 timeout is described on page 6–12 of Document Number 001-208966, and is preferably between about 5 to about 30 seconds, such as about 10 seconds. The router listens on LMI management channel number 1023 for a response.
Although in a preferred embodiment the router transmits the “STATUS ENQUIRY” message using LMI protocols in the order described for the steps 122, 124, and 126, in alternative embodiments it would be possible to use a different order in which the messages are sent, a different number of LMI protocols to test, or a different set of LMI protocols for test.
Although in a preferred embodiment the timeouts are set for the values described for the steps 123, 125, and 127, in alternative embodiments it would be possible to use a different set of values for the timeouts. Moreover, although in a preferred embodiment the timeouts are set using multiple timer interrupts, in alternative embodiments it would be possible to use other techniques for setting and catching timeouts, such as a single timeout for all three messages, or a non-interrupt-based technique.
At a flow point 130, the frame relay network equipment is ready to receive a “STATUS ENQUIRY” message, and the router is listening for responses to one or more of the “STATUS ENQUIRY” messages.
At a step 131, the frame relay network equipment listens for a “STATUS ENQUIRY” message. The frame relay network equipment sets a timeout for receiving that message, and starts a timer interrupt to occur on that timeout. This timeout is preferably set for nT2 or T392 seconds (from the frame relay network equipment's perspective), such as about 15 seconds, as described in ANSI Document T1.617-1991 and in Document Number 001-208966. When the timeout occurs, the method continues at the flow point 140.
At a step 132, the frame relay network equipment receives one of the “STATUS ENQUIRY” messages.
At a step 133, the frame relay network equipment determines if the received “STATUS ENQUIRY” message is for an LMI protocol it recognizes. If not, the frame relay network equipment continues to listen for a “STATUS ENQUIRY” message at the step 131. In a preferred embodiment, the frame relay network equipment logs an error event if the received “STATUS ENQUIRY” message is for an LMI protocol which it does not recognize.
At a step 134, the frame relay network equipment responds to the “STATUS ENQUIRY” message by transmitting a “STATUS” message on the appropriate LMI management channel. If the “STATUS ENQUIRY” message was for the ANSI protocol, the frame relay network equipment transmits the “STATUS” message on LMI management channel zero; if the “STATUS ENQUIRY” message was for the ITU protocol, the frame relay network equipment transmits the “STATUS” message on LMI management channel zero; if the “STATUS ENQUIRY” message was for the LMI protocol, the frame relay network equipment transmits the “STATUS” message on LMI management channel 1023.
At a step 135, the frame relay network equipment should further respond to the “STATUS ENQUIRY” message by configuring itself to use the LMI protocol associated with that message. In a preferred embodiment, the frame relay network equipment will so configure itself, but in the event it does not, the process begins again in an attempt to deliver the “STATUS ENQUIRY” message and cause the frame relay network equipment to so configure itself.
The frame relay network equipment then continues with the step 131 to receive any further “STATUS ENQUIRY” messages.
The steps 131 through 135 are performed in parallel with the steps 141 through 142.
At a step 141, the router receives a “STATUS” message for one of the LMI protocols.
At a step 142, the router determines which LMI protocol the “STATUS” message is for, and configures itself for that LMI protocol.
The router then continues with the step 141 to receive any further “STATUS” messages. The router catches any timeout interrupts for the “STATUS ENQUIRY” messages transmitted in the steps 122, 124, and 126, until all “STATUS ENQUIRY” messages have been responded to or have timed out. Thereafter, the method proceeds at the flow point 150.
At a flow point 150, the frame relay network equipment has received at least one “STATUS ENQUIRY” message from the router, and the router has received at least one “STATUS” message in response thereto.
If the frame relay network equipment has only recognized one LMI protocol, it has responded to the “STATUS ENQUIRY” message for that LMI protocol only, and the router has therefore received only one “STATUS” message. The router and frame relay network equipment have therefore configured themselves for that one LMI protocol only.
If the frame relay network equipment has recognized more than one LMI protocol, it has responded to the “STATUS ENQUIRY” message for each of those LMI protocols, and has configured itself for each such LMI protocol in turn. Similarly, the router has received one “STATUS” message for each such LMI protocol, and has configured itself for each such LMI protocol in turn. The router and frame relay network equipment have therefore configured themselves for each LMI protocol seriatum; at the flow point 150 they are therefore configured for the same LMI protocol.
Although in a preferred embodiment, the router and frame relay network equipment mutually configure to the last LMI protocol which is mutually recognized, in alternative embodiments it would be possible for the router and frame relay network equipment to mutually configure to another mutually recognized. For example, the frame relay network equipment could respond to the first “STATUS ENQUIRY” message only, and reject all others; the router would then receive only one “STATUS” message in response, and the router and frame relay network equipment would mutually configure to the LMI protocol for that first “STATUS ENQUIRY” message.
The router and frame relay network equipment thereafter communicate using the selected LMI protocol.
Although preferred embodiments are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4131767||22 Feb 1978||26 Dec 1978||Bell Telephone Laboratories, Incorporated||Echo cancellation in two-wire, two-way data transmission systems|
|US4161719||4 Oct 1977||17 Jul 1979||Ncr Corporation||System for controlling synchronization in a digital communication system|
|US4316284||11 Sep 1980||16 Feb 1982||Bell Telephone Laboratories, Incorporated||Frame resynchronization circuit for digital receiver|
|US4397020||13 Oct 1981||2 Aug 1983||Bell Telephone Laboratories, Incorporated||Error monitoring in digital transmission systems|
|US4419728||22 Jun 1981||6 Dec 1983||Bell Telephone Laboratories, Incorporated||Channel interface circuit providing virtual channel number translation and direct memory access|
|US4424565||22 Jun 1981||3 Jan 1984||Bell Telephone Laboratories, Incorporated||Channel interface circuit with high speed data message header field translation and direct memory access|
|US4437087||27 Jan 1982||13 Mar 1984||Bell Telephone Laboratories, Incorporated||Adaptive differential PCM coding|
|US4438511||10 Nov 1980||20 Mar 1984||Telebit Corporation||Packetized ensemble modem|
|US4439763||3 Sep 1981||27 Mar 1984||Bell Telephone Laboratories, Incorporated||Collision avoiding system and protocol for a multiple access digital communications system|
|US4445213||22 Jan 1982||24 Apr 1984||Bell Telephone Laboratories, Incorporated||Communication line interface for controlling data information having differing transmission characteristics|
|US4446555||22 Feb 1982||1 May 1984||Michel Devault||Time division multiplex switching network for multiservice digital networks|
|US4456957||28 Sep 1981||26 Jun 1984||Ncr Corporation||Apparatus using a decision table for routing data among terminals and a host system|
|US4464658||5 Mar 1982||7 Aug 1984||At&T Laboratories||Multipoint data communication system with collision detection|
|US4499576||13 Aug 1982||12 Feb 1985||At&T Bell Laboratories||Multiplexed first-in, first-out queues|
|US4506358||25 Jun 1982||19 Mar 1985||At&T Bell Laboratories||Time stamping for a packet switching system|
|US4507760||13 Aug 1982||26 Mar 1985||At&T Bell Laboratories||First-in, first-out (FIFO) memory configuration for queue storage|
|US4532626||19 Jul 1982||30 Jul 1985||At&T Bell Laboratories||Collision avoiding system and protocol for a two path multiple access digital communications system|
|US4644532||10 Jun 1985||17 Feb 1987||International Business Machines Corporation||Automatic update of topology in a hybrid network|
|US4646287||7 Dec 1984||24 Feb 1987||At&T Bell Laboratories||Idle period signalling in a packet switching system|
|US4677423||6 Jan 1986||30 Jun 1987||American Telephone & Telegraph, At&T Bell Laboratories||ADPCM coder-decoder including partial band energy transition detection|
|US4679189||27 Nov 1985||7 Jul 1987||American Telephone And Telegraph Company||Alternate routing arrangement|
|US4679227||20 May 1985||7 Jul 1987||Telebit Corporation||Ensemble modem structure for imperfect transmission media|
|US4723267||17 Jun 1985||2 Feb 1988||Octocom Systems, Inc.||Telephone line interface and dialer circuitry for telecommunications equipment|
|US4731816||12 Jan 1987||15 Mar 1988||Telebit Corporation||Ensemble modem structure for imperfect transmission media|
|US4750136||10 Jan 1986||7 Jun 1988||American Telephone And Telegraph, At&T Information Systems Inc.||Communication system having automatic circuit board initialization capability|
|US4757495||5 Mar 1986||12 Jul 1988||Telebit Corporation||Speech and data multiplexor optimized for use over impaired and bandwidth restricted analog channels|
|US4763191||17 Mar 1986||9 Aug 1988||American Telephone And Telegraph Company, At&T Bell Laboratories||Dial-up telephone network equipment for requesting an identified selection|
|US4769810||31 Dec 1986||6 Sep 1988||American Telephone And Telegraph Company, At&T Bell Laboratories||Packet switching system arranged for congestion control through bandwidth management|
|US4769811||31 Dec 1986||6 Sep 1988||American Telephone And Telegraph Company, At&T Bell Laboratories||Packet switching system arranged for congestion control|
|US4771425||29 Oct 1984||13 Sep 1988||Stratacom, Inc.||Synchoronous packet voice/data communication system|
|US4819228||15 Oct 1987||4 Apr 1989||Stratacom Inc.||Synchronous packet voice/data communication system|
|US4827411||15 Jun 1987||2 May 1989||International Business Machines Corporation||Method of maintaining a topology database|
|US4833706||5 Jan 1988||23 May 1989||Telebit Corporation||Ensemble modem structure for imperfect transmission media|
|US4835737||21 Jul 1986||30 May 1989||American Telephone And Telegraph Company, At&T Bell Laboratories||Method and apparatus for controlled removal and insertion of circuit modules|
|US4879551||26 Apr 1985||7 Nov 1989||International Business Machines Corporation||Switching array with concurrent marking capability|
|US4893306||10 Nov 1987||9 Jan 1990||Bell Communications Research, Inc.||Method and apparatus for multiplexing circuit and packet traffic|
|US4903261||9 Mar 1988||20 Feb 1990||Stratacom, Inc.||Synchronous packet voice/data communication system|
|US4922486||31 Mar 1988||1 May 1990||American Telephone And Telegraph Company||User to network interface protocol for packet communications networks|
|US4933937||23 Nov 1987||12 Jun 1990||Kabushiki Kaisha Toshiba||Network adapter for connecting local area network to backbone network|
|US4960310||4 Aug 1989||2 Oct 1990||Optical Corporation Of America||Broad band nonreflective neutral density filter|
|US4962497||21 Sep 1989||9 Oct 1990||At&T Bell Laboratories||Building-block architecture of a multi-node circuit-and packet-switching system|
|US4962532||22 Dec 1988||9 Oct 1990||Ibm Corporation||Method for providing notification of classified electronic message delivery restriction|
|US4965767||17 Jul 1989||23 Oct 1990||Mitsubishi Denki Kabushiki Kaisha||Associative memory having simplified memory cell circuitry|
|US4965772||15 Jun 1987||23 Oct 1990||International Business Machines Corporation||Method and apparatus for communication network alert message construction|
|US4970678||28 Jun 1988||13 Nov 1990||International Business Machines Corporation||System for providing context-sensitive on-line documentation in a data processor|
|US4979118||10 Mar 1989||18 Dec 1990||Gte Laboratories Incorporated||Predictive access-control and routing system for integrated services telecommunication networks|
|US4980897||12 Aug 1988||25 Dec 1990||Telebit Corporation||Multi-channel trellis encoder/decoder|
|US4991169||2 Aug 1988||5 Feb 1991||International Business Machines Corporation||Real-time digital signal processing relative to multiple digital communication channels|
|US5003595||29 Aug 1989||26 Mar 1991||At&T Bell Laboratories||Secure dial access to computer systems|
|US5014265||30 Nov 1989||7 May 1991||At&T Bell Laboratories||Method and apparatus for congestion control in a data network|
|US5020058||23 Jan 1989||28 May 1991||Stratacom, Inc.||Packet voice/data communication system having protocol independent repetitive packet suppression|
|US5033076||31 Jan 1990||16 Jul 1991||At&T Bell Laboratories||Enhanced privacy feature for telephone systems|
|US5034919||22 May 1990||23 Jul 1991||Kabushiki Kaisha Toshiba||Content addressable memory|
|US5054034||15 Jun 1989||1 Oct 1991||Telebit Corporation||Ensemble modem structure for imperfect transmission media|
|US5059925||28 Sep 1990||22 Oct 1991||Stratacom, Inc.||Method and apparatus for transparently switching clock sources|
|US5072449||15 Feb 1990||10 Dec 1991||Stratacom, Inc.||Packet framing using cyclic redundancy checking|
|US5088032||29 Jan 1988||11 Feb 1992||Cisco Systems, Inc.||Method and apparatus for routing communications among computer networks|
|US5095480||16 Jun 1989||10 Mar 1992||Fenner Peter R||Message routing system for shared communication media networks|
|US5115431||28 Sep 1990||19 May 1992||Stratacom, Inc.||Method and apparatus for packet communications signaling|
|US5128945||31 Oct 1991||7 Jul 1992||Stratacom, Inc.||Packet framing using cyclic redundancy checking|
|US5136580||16 May 1990||4 Aug 1992||Microcom Systems, Inc.||Apparatus and method for learning and filtering destination and source addresses in a local area network system|
|US5166930||17 Dec 1990||24 Nov 1992||At&T Bell Laboratories||Data channel scheduling discipline arrangement and method|
|US5199049||27 Apr 1990||30 Mar 1993||At&T Bell Laboratories||Circuit and method of digital carrier detection for burst mode communication systems|
|US5206886||16 Apr 1990||27 Apr 1993||Telebit Corporation||Method and apparatus for correcting for clock and carrier frequency offset, and phase jitter in mulicarrier modems|
|US5208811||1 Nov 1990||4 May 1993||Hitachi, Ltd.||Interconnection system and method for heterogeneous networks|
|US5212686||29 Sep 1989||18 May 1993||Plessey Overseas Limited||Asynchronous time division switching arrangement and a method of operating same|
|US5224099||17 May 1991||29 Jun 1993||Stratacom, Inc.||Circuitry and method for fair queuing and servicing cell traffic using hopcounts and traffic classes|
|US5226120||21 May 1990||6 Jul 1993||Synoptics Communications, Inc.||Apparatus and method of monitoring the status of a local area network|
|US5228062||27 May 1992||13 Jul 1993||Telebit Corporation||Method and apparatus for correcting for clock and carrier frequency offset, and phase jitter in multicarrier modems|
|US5229994||27 Sep 1991||20 Jul 1993||Alcatel Cit||Bridge for connecting an ieee 802.3 local area network to an asynchronous time-division multiplex telecommunication network|
|US5237564||5 Apr 1991||17 Aug 1993||France Telecom||Frame switching relay for asynchronous digital network|
|US5241682||18 Apr 1991||31 Aug 1993||International Business Machines Corporation||Border node having routing and functional capability in a first network and only local address capability in a second network|
|US5243342||22 Jul 1992||7 Sep 1993||Stratacom, Inc.||Integrated PCM level control and conversion using a lookup table|
|US5243596||18 Mar 1992||7 Sep 1993||Fischer & Porter Company||Network architecture suitable for multicasting and resource locking|
|US5247516||28 Mar 1991||21 Sep 1993||Sprint International Communications Corp.||Configurable composite data frame|
|US5249178||26 Jul 1991||28 Sep 1993||Nec Corporation||Routing system capable of effectively processing routing information|
|US5253251||8 Jan 1992||12 Oct 1993||Nec Corporation||Switching system with time-stamped packet distribution input stage and packet sequencing output stage|
|US5255291||14 Nov 1988||19 Oct 1993||Stratacom, Inc.||Microprocessor based packet isochronous clocking transmission system and method|
|US5260933||15 May 1992||9 Nov 1993||International Business Machines Corporation||Acknowledgement protocol for serial data network with out-of-order delivery|
|US5260978||30 Oct 1992||9 Nov 1993||Bell Communications Research, Inc.||Synchronous residual time stamp for timing recovery in a broadband network|
|US5268592||26 Feb 1991||7 Dec 1993||International Business Machines Corporation||Sequential connector|
|US5268900||5 Jul 1991||7 Dec 1993||Codex Corporation||Device and method for implementing queueing disciplines at high speeds|
|US5271004||27 Aug 1991||14 Dec 1993||Gpt Limited||Asynchronous transfer mode switching arrangement providing broadcast transmission|
|US5274631||11 Mar 1991||28 Dec 1993||Kalpana, Inc.||Computer network switching system|
|US5274635||18 Nov 1992||28 Dec 1993||Stratacom, Inc.||Method and apparatus for aligning a digital communication data stream across a cell network|
|US5280470||3 Feb 1993||18 Jan 1994||At&T Bell Laboratories||Bandwidth and congestion management in accessing broadband ISDN networks|
|US5280480||21 Feb 1991||18 Jan 1994||International Business Machines Corporation||Source routing transparent bridge|
|US5280500||10 Oct 1991||18 Jan 1994||Crescendo Communications, Inc.||Method and apparatus for multilevel encoding for a local area network|
|US5283783||28 Jan 1993||1 Feb 1994||Synoptics Communications, Inc.||Apparatus and method of token ring beacon station removal for a communication network|
|US5287103||30 Dec 1991||15 Feb 1994||At&T Bell Laboratories||Method and apparatus for providing local area network clients with internetwork identification data|
|US5287453||18 Sep 1990||15 Feb 1994||Bull Hn Information Systems, Inc.||Fast remote file access facility for distributing file access requests in a closely coupled computer system|
|US5291482||24 Jul 1992||1 Mar 1994||At&T Bell Laboratories||High bandwidth packet switch|
|US5305311||20 May 1992||19 Apr 1994||Xerox Corporation||Copy network providing multicast capabilities in a broadband ISDN fast packet switch suitable for use in a local area network|
|US5307343||27 Nov 1990||26 Apr 1994||Italtel Societa Italiana Telecommunicazioni S.P.A.||Basic element for the connection network of a fast packet switching node|
|US5309437||29 Jun 1990||3 May 1994||Digital Equipment Corporation||Bridge-like internet protocol router|
|US5311509||6 Feb 1992||10 May 1994||International Business Machines Corporation||Configurable gigabits switch adapter|
|US5313454||1 Apr 1992||17 May 1994||Stratacom, Inc.||Congestion control for cell networks|
|US5313582||30 Apr 1991||17 May 1994||Standard Microsystems Corporation||Method and apparatus for buffering data within stations of a communication network|
|US5802042 *||28 Jun 1996||1 Sep 1998||Cisco Systems, Inc.||Autosensing LMI protocols in frame relay networks|
|US6434120 *||25 Aug 1998||13 Aug 2002||Cisco Technology, Inc.||Autosensing LMI protocols in frame relay networks|
|USRE33900||31 Jul 1989||28 Apr 1992||At&T Bell Laboratories||Error monitoring in digital transmission systems|
|1||Allen, M., "Novell IPX Over Various WAN Media (IPXW AN)," Network Working Group, RFC 1551, Dec. 1993, pp. 1-22.|
|2||Becker, D., "3c589.c: A 3c589 EtherLink3 Ethernet driver for Linux" becker@CESDIS.gsfc.nasa.gov, May 3, 1994, pp. 1-13.|
|3||Chowdhury, et al., "Alternative Bandwidth Allocation Algorithms for Packet Video in ATM Networks," INFOCOM 1992, pp. 1061-1068.|
|4||Doeringer, W., "Routing on Longest-Matching Prefixes)," IEEE/ACM Transactions in Networking, vol. 4, No. 1, Feb. 1996, pp. 86-97.|
|5||Esaki, et al., "Datagram Delivery in an ATM-Internet," 2334b IEICE Transactions on Communications, Mar. 1994, No. 3, Tokyo, Japan.|
|6||IBM Corporation, "Method and Apparatus for the Statistical Multiplexing of Voice, Data and Image Signals," IBM Technical Disclosure Bulletin, No. 6, Nov. 1992, pp. 409-411.|
|7||Pei, et al., "Putting Routing Tables in Silicon," IEEE Network Magazine, Jan. 1992, pp. 42-50.|
|8||Perkins, D., "Requirements for an Internet Standard Point-to-Point Protocol," Network Working Group, RFC 1547, Dec. 1993, pp. 1-19.|
|9||Simpson, W., "The Point-to-Point Protocol (PPP)," Network Working Group, RFC 1548, Dec. 1993, pp. 1-53.|
|10||Tsuchiya, P.F., "A Search Algorithm for Table Entries with Non-Contiguous Wildcarding," Abstract, Bellcore.|
|11||Zhang, et al., "Rate-Controlled Static-Priority Queuing," INFOCOM 1993, pp. 227-236.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8316129||20 Nov 2012||Microsoft Corporation||Data communication coordination with sequence numbers|
|US8332526 *||15 Jul 2005||11 Dec 2012||Microsoft Corporation||Data communication protocol including negotiation and command compounding|
|US8631277||10 Dec 2010||14 Jan 2014||Microsoft Corporation||Providing transparent failover in a file system|
|US8788579||9 Sep 2011||22 Jul 2014||Microsoft Corporation||Clustered client failover|
|US8825885||30 Oct 2012||2 Sep 2014||Microsoft Corporation||Data communication protocol|
|US8850025||30 Oct 2012||30 Sep 2014||Microsoft Corporation||Data communication coordination with sequence numbers|
|US8856582||30 Jun 2011||7 Oct 2014||Microsoft Corporation||Transparent failover|
|US9071661||29 Aug 2014||30 Jun 2015||Microsoft Technology Licensing, Llc||Data communication coordination with sequence numbers|
|US9331955||29 Jun 2011||3 May 2016||Microsoft Technology Licensing, Llc||Transporting operations of arbitrary size over remote direct memory access|
|US9332089||22 May 2015||3 May 2016||Microsoft Technology Licensing, Llc||Data communication coordination with sequence numbers|
|US9438696||19 Jul 2013||6 Sep 2016||Microsoft Technology Licensing, Llc||Data communication protocol|
|US9462039||2 Sep 2014||4 Oct 2016||Microsoft Technology Licensing, Llc||Transparent failover|
|US20060271692 *||15 Jul 2005||30 Nov 2006||Microsoft Corporation||Data communication coordination with sequence numbers|
|U.S. Classification||370/255, 709/220, 370/401, 370/465|
|International Classification||H04L12/28, H04J3/16, H04L12/24|
|Cooperative Classification||H04L41/0806, H04L12/2854, H04L41/0886|
|European Classification||H04L12/28P, H04L41/08A1, H04L41/08D3|
|19 Feb 2010||FPAY||Fee payment|
Year of fee payment: 4
|5 Mar 2014||FPAY||Fee payment|
Year of fee payment: 8