TREA

Autosensing LMI protocols in frame relay networks

Follow

Information

  • Patent Grant
  • 7103007
  • Patent Number
    7,103,007
  • Date Filed
    Thursday, June 27, 2002
    22 years ago
  • Date Issued
    Tuesday, September 5, 2006
    18 years ago
Information
Abstract
The invention provides a method and system for auto-sensing LMI protocols in frame relay networks. When a router 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 configuration server. Multiple valid responses from the configuration server are assigned priority in response to which valid response is last to arrive.
Description
BACKGROUND OF THE INVENTION

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.


SUMMARY OF THE INVENTION

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.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a method of autosensing LMI protocols in frame relay networks.





DESCRIPTION OF THE PREFERRED EMBODIMENT

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.


Autosensing LMI Protocols in Frame Relay Networks


FIG. 1 shows a method of autosensing LMI protocols in frame relay networks.


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.


ALTERNATIVE EMBODIMENTS

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.

Claims
  • 1. A method for performing auto-sensing of protocols used for communicating between entities of a data network, the method comprising: transmitting, from a first router, a plurality of requests, one for each of a set of LMI protocols, to at least one other network device;receiving at least one response to at least one of said plurality of requests;identifying at least one LMI protocol associated with the at least one response; andautomatically configuring the router to utilize said at least one LMI protocol in response to said at least one response.
  • 2. The method of claim 1 wherein the at least one other network device includes a network device coupled to a frame relay network.
  • 3. The method of claim 1 further comprising: identifying a first LMI protocol associated with a first response of said at least one response; automatically configuring the router to utilize said first LMI protocol;identifying a second LMI protocol associated with a second response of said at least one response; andautomatically configuring the router to utilize said second LMI protocol.
  • 4. The method of claim 1 wherein the transmitting of the plurality of requests occurs substantially simultaneously.
  • 5. The method as in claim 1, further comprising initialing a timeout for at least one of said plurality of requests.
  • 6. The method as in claim 1, further comprising initiating a separate timeout for each one of said plurality of requests.
  • 7. The method as in claim 1, wherein said set of LMI protocols comprise an ANSI protocol, an ITU protocol, and an LMI protocol.
  • 8. The method as in claim 1 further comprising listening on a plurality of LIVE management channels for said at least one response; and receiving at least one response on at least one of said plurality of LMI management channels.
  • 9. The method as in claim 8, wherein said plurality of LMI management channels comprises LMI management channels zero and 1023.
Parent Case Info

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.

US Referenced Citations (186)
Number Name Date Kind
4131767 Weinstein Dec 1978 A
4161719 Parikh et al. Jul 1979 A
4316284 Howson Feb 1982 A
4397020 Howson Aug 1983 A
4419728 Larson Dec 1983 A
4424565 Larson Jan 1984 A
4437087 Petr Mar 1984 A
4438511 Baran Mar 1984 A
4439763 Limb Mar 1984 A
4445213 Baugh et al. Apr 1984 A
4446555 Devault et al. May 1984 A
4456957 Schieltz Jun 1984 A
4464658 Thelen Aug 1984 A
4499576 Fraser Feb 1985 A
4506358 Montgomery Mar 1985 A
4507760 Fraser Mar 1985 A
4532626 Flores et al. Jul 1985 A
4644532 George et al. Feb 1987 A
4646287 Larson et al. Feb 1987 A
4677423 Benvenuto et al. Jun 1987 A
4679189 Olson et al. Jul 1987 A
4679227 Hughes-Hartogs Jul 1987 A
4723267 Jones et al. Feb 1988 A
4731816 Hughes-Hartogs Mar 1988 A
4750136 Arpin et al. Jun 1988 A
4757495 Decker et al. Jul 1988 A
4763191 Gordon et al. Aug 1988 A
4769810 Eckberg, Jr. et al. Sep 1988 A
4769811 Eckberg, Jr. et al. Sep 1988 A
4771425 Baran et al. Sep 1988 A
4819228 Baran et al. Apr 1989 A
4827411 Arrowood et al. May 1989 A
4833706 Hughes-Hartogs May 1989 A
4835737 Herrig et al. May 1989 A
4879551 Georgiou et al. Nov 1989 A
4893306 Chao et al. Jan 1990 A
4903261 Baran et al. Feb 1990 A
4922486 Lidinsky et al. May 1990 A
4933937 Konishi Jun 1990 A
4960310 Cushing Oct 1990 A
4962497 Ferenc et al. Oct 1990 A
4962532 Kasirai et al. Oct 1990 A
4965767 Kinoshita et al. Oct 1990 A
4965772 Daniel et al. Oct 1990 A
4970678 Sladowski et al. Nov 1990 A
4979118 Kheradpir Dec 1990 A
4980897 Decker et al. Dec 1990 A
4991169 Davis et al. Feb 1991 A
5003595 Collins et al. Mar 1991 A
5014265 Hahne et al. May 1991 A
5020058 Holden et al. May 1991 A
5033076 Jones et al. Jul 1991 A
5034919 Sasai et al. Jul 1991 A
5054034 Hughes-Hartogs Oct 1991 A
5059925 Weisbloom Oct 1991 A
5072449 Enns et al. Dec 1991 A
5088032 Bosack Feb 1992 A
5095480 Fenner Mar 1992 A
RE33900 Howson Apr 1992 E
5115431 Williams May 1992 A
5128945 Enns et al. Jul 1992 A
5136580 Videlock et al. Aug 1992 A
5166930 Braff et al. Nov 1992 A
5199049 Wilson Mar 1993 A
5206886 Bingham Apr 1993 A
5208811 Kashio et al. May 1993 A
5212686 Joy et al. May 1993 A
5224099 Corbalis et al. Jun 1993 A
5226120 Brown et al. Jul 1993 A
5228062 Bingham Jul 1993 A
5229994 Balzano et al. Jul 1993 A
5237564 Lespagnol et al. Aug 1993 A
5241682 Bryant et al. Aug 1993 A
5243342 Kattemalalayadi et al. Sep 1993 A
5243596 Port et al. Sep 1993 A
5247516 Bernstein et al. Sep 1993 A
5249178 Kurano et al. Sep 1993 A
5253251 Aramaki Oct 1993 A
5255291 Holden et al. Oct 1993 A
5260933 Rouse Nov 1993 A
5260978 Fleischer et al. Nov 1993 A
5268592 Bellamy et al. Dec 1993 A
5268900 Hluchyj et al. Dec 1993 A
5271004 Proctor et al. Dec 1993 A
5274631 Bhardwaj Dec 1993 A
5274635 Rahman et al. Dec 1993 A
5280470 Buhrke et al. Jan 1994 A
5280480 Pitt et al. Jan 1994 A
5280500 Mazzola et al. Jan 1994 A
5283783 Nguyen et al. Feb 1994 A
5287103 Kasprzyk et al. Feb 1994 A
5287453 Roberts Feb 1994 A
5291482 McHarg et al. Mar 1994 A
5305311 Lyles Apr 1994 A
5307343 Bostica et al. Apr 1994 A
5309437 Perlman et al. May 1994 A
5311509 Heddes et al. May 1994 A
5313454 Bustini et al. May 1994 A
5313582 Hendel et al. May 1994 A
5317562 Nardin et al. May 1994 A
5319644 Liang Jun 1994 A
5327421 Hiller et al. Jul 1994 A
5331637 Francis et al. Jul 1994 A
5345445 Hiller et al. Sep 1994 A
5359592 Corbalis et al. Oct 1994 A
5361250 Nguyen et al. Nov 1994 A
5361256 Doeringer et al. Nov 1994 A
5361259 Hunt et al. Nov 1994 A
5365524 Hiller et al. Nov 1994 A
5367517 Cidon et al. Nov 1994 A
5371852 Attanasio et al. Dec 1994 A
5386567 Lien et al. Jan 1995 A
5390170 Sawant et al. Feb 1995 A
5390175 Hiller et al. Feb 1995 A
5394394 Crowther et al. Feb 1995 A
5394402 Ross Feb 1995 A
5400325 Chatwani et al. Mar 1995 A
5408469 Opher et al. Apr 1995 A
5416842 Aziz May 1995 A
5422880 Heitkamp et al. Jun 1995 A
5422882 Hiller et al. Jun 1995 A
5423002 Hart Jun 1995 A
5426636 Hiller et al. Jun 1995 A
5428607 Hiller et al. Jun 1995 A
5430715 Corbalis et al. Jul 1995 A
5430729 Rahnema Jul 1995 A
5442457 Najafi Aug 1995 A
5442630 Gagliardi et al. Aug 1995 A
5452297 Hiller et al. Sep 1995 A
5473599 Li et al. Dec 1995 A
5473607 Hausman et al. Dec 1995 A
5477541 White et al. Dec 1995 A
5485455 Dobbins et al. Jan 1996 A
5490140 Abensour et al. Feb 1996 A
5490258 Fenner Feb 1996 A
5491687 Christensen et al. Feb 1996 A
5491804 Heath et al. Feb 1996 A
5509006 Wilford et al. Apr 1996 A
5519704 Farinacci et al. May 1996 A
5519858 Walton et al. May 1996 A
5526489 Nilakantan et al. Jun 1996 A
5530963 Moore et al. Jun 1996 A
5535195 Lee Jul 1996 A
5539734 Burwell et al. Jul 1996 A
5541911 Nilakantan et al. Jul 1996 A
5546370 Ishikawa Aug 1996 A
5555244 Gupta et al. Sep 1996 A
5561669 Lenney et al. Oct 1996 A
5583862 Callon Dec 1996 A
5592470 Rudrapatna et al. Jan 1997 A
5598581 Daines et al. Jan 1997 A
5600798 Cherukuri et al. Feb 1997 A
5602770 Ohira Feb 1997 A
5604868 Komine et al. Feb 1997 A
5617417 Sathe et al. Apr 1997 A
5617421 Chin et al. Apr 1997 A
5630125 Zellweger et al. May 1997 A
5631908 Saxe May 1997 A
5632021 Jennings et al. May 1997 A
5634010 Ciscon et al. May 1997 A
5638359 Peltola et al. Jun 1997 A
5644718 Belove et al. Jul 1997 A
5659684 Giovannoni et al. Aug 1997 A
5666353 Klausmeier et al. Sep 1997 A
5673265 Gupta et al. Sep 1997 A
5678006 Valizadeh et al. Oct 1997 A
5680116 Hashimoto et al. Oct 1997 A
5684797 Aznar et al. Nov 1997 A
5687324 Green et al. Nov 1997 A
5689506 Chiussi et al. Nov 1997 A
5694390 Yamato et al. Dec 1997 A
5724351 Chao et al. Mar 1998 A
5740097 Satoh Apr 1998 A
5748186 Raman May 1998 A
5748617 McLain, Jr. May 1998 A
5754547 Nakazawa et al. May 1998 A
5802042 Natarajan et al. Sep 1998 A
5802054 Bellenger Sep 1998 A
5835710 Nagami et al. Nov 1998 A
5841874 Kempke et al. Nov 1998 A
5854903 Morrison et al. Dec 1998 A
5856981 Voelker Jan 1999 A
5892924 Lyon et al. Apr 1999 A
5898686 Virgile Apr 1999 A
5903559 Acharya et al. May 1999 A
6434120 Natarajan et al. Aug 2002 B1
Foreign Referenced Citations (6)
Number Date Country
0384758 Aug 1990 EP
0431751 Jun 1991 EP
0567217 Oct 1993 EP
WO9401828 Jan 1993 WO
WO9307569 Apr 1993 WO
WO9307692 Apr 1993 WO
Related Publications (1)
Number Date Country
20020163891 A1 Nov 2002 US
Continuations (2)
Number Date Country
Parent 09140178 Aug 1998 US
Child 10187180 US
Parent 08672674 Jun 1996 US
Child 09140178 US