The present invention relates generally to a Customer Premises Equipment (CPE) device having its Asynchronous Transfer Mode (ATM) interface automatically configured. More specifically, the present invention relates to a method for configuring a Permanent Virtual Circuit (PVC) and Layer 3 of a CPE device over an ATM interface.
ATM is a packet-switching technology that uses fixed-size packets, referred to as cells, to carry the traffic in a network. The ATM standard allows transmission of intermixed audio, video, and data over high-speed links. As well as being used in wide-area networks, the ATM standard can be used for local-area networks to support multimedia applications.
The unit of transmission used in the ATM standard is a cell. As shown in
Within a switch, each ATM cell is switched based on the information contained in its header; more specifically based on its VPI and VCI as shown in
ADSL Customer Premises Equipment is usually configured with one Permanent Virtual Circuit (PVC) over which PPP or bridged request for comments (RFC) 1483 protocol traffic is supported. The RFC 1483 protocol is dated July 1993 published by Telecom Finland. In a PVC network, such as ATM, when a circuit is established, the route is chosen from source to destination, and all switches (e.g. routers) along the way may take entries so that they can switch any cells on that virtual circuit. When a cell comes along, a switch inspects the cell's header to find out which virtual circuit it belongs to. Then it looks up that virtual circuit in its tables to determine which output communication line to direct cell to. Therefore, there is an agreement between a customer and a service provider that the switches will always hold table entries for a particular destination, even if there has been no traffic for months.
In an end-user network such as the one illustrated in
A need therefore exists for a method and a device that enable a CPE device to automatically configure its PVC and then link it to an interface such as PPP or RFC bridging so that both layer 2 (ATM PVC) and layer 3 (DHCP or IPCP) auto-configuration is achieved. Thus, a customer who buys the CPE device would not need to contact the service provider to find out about the VPI and VPC for the PVC. If the service provider sends RFC 1483 bridged traffic or PPP traffic (assuming that CHAP or PAP is not used), the customer would just need to plug the CPE device in and allow it to auto-configure itself.
The present invention pertains to a method and device for automatically configuring the Permanent Virtual Circuit (PVC) of a Digital Subscriber Line (DSL) Customer Premises Equipment (CPE) and link it to a software interface. The method comprises receiving an ATM cell and checking the ATM cell for an OAM Fault Management (F5) type cell. The OAM type cell allows the PVC to be configured by obtaining a VPI and VCI from the OAM type cell. Otherwise, the CPE configures its new PVC by obtaining a VPI and VCI from a first traffic bearing cell and linking its new PVC to a protocol specific to DSL.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more exemplary embodiments of the present invention and, together with the detailed description, serve to explain the principles and exemplary implementations of the invention.
In the drawings:
Various exemplary embodiments of the present invention are described herein in the context of an ATM permanent virtual circuit and Layer 3 auto-configuration for digital subscriber line customer premises equipment. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to exemplary implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed descriptions to refer to the same or like parts.
In the interest of clarity, not all of the routine features of the exemplary implementations described herein are shown and described. It will of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the specific goals of the developer, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
In accordance with one embodiment of the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, firmware, computer programs, computer languages, and/or general-purpose machines. The method can operate as a programmed process running on processing circuitry. The processing circuitry can take the form of numerous combinations of processors and operating systems or the form of a stand-alone device. The process can be implemented as instructions executed by such hardware, hardware alone, or any combination thereof. The software may be stored on a computer-readable medium.
In addition, one of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable logic devices (FPLDs), including field programmable gate arrays (FPGAs) and complex programmable logic devices (CPLDs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
In accordance with one embodiment of the present invention, the method may be implemented on a data processing computer. The method may also be implemented in a computing environment including various peripherals such as input devices, output devices, displays, pointing devices, memories, storage devices, media interfaces for transferring data to and from the computer, and the like. In addition, the computing environment may be networked.
In the context of the present invention, the term “network” includes local area networks (LANs), wide area networks (WANs), the Internet, cable television systems, telephone systems, wireless telecommunications systems, fiber optic networks, ATM networks, frame relay networks, satellite communications systems, and the like. Such networks are well known in the art and consequently are not further described herein.
At step 600, CPE 400 receives a cell from a DSLAM 402 through a physical transmission path 404. At step 602, CPE 400 examines the received cell. If the received cell is determined to be an Operations and Maintenance (OAM) cell, step 604 is performed. OAM cells are special purpose cells whose function provide a set of diagnostic and alarm reporting mechanisms such as fault management. As illustrated in
At step 608, CPE 400 determines whether the received cell is a first cell of a packet by measuring the elapse time between the received cell and a previous cell on the same PVC.
At step 612, CPE 400 can then grab the VPI and VCI from the received cell because traffic bearing cells contain VPI and VCI in their header as previously illustrated in
When a Service Provider configures an aggregate router, such as aggregator 418, to support protocols such as PPP or bridged RFC 1483 over ATM, CPE 400 receives many messages from the aggregate router. In the case of PPP over ATM protocol, CPE 400 receives regular Link Control Protocol (LCP) configuration requests messages. In the case of bridged RFC 1483, CPE 400 receives regular (Bridge Protocol Data Unit) BPDU spanning tree messages. Instead of discarding the received ATM cells containing these messages because no PVC is configured, CPE 400 can instead look inside these cells and try to determine whether they contain a valid LCP header or a BPDU header.
At step 614, CPE 400 determines whether the received cell contains an LCP header as shown in
At step 618, CPE 400 determines whether the received cell contains a BPDU header as shown in
Another implementation of the present invention may be in the form of a program storage device readable by a machine, embodying a program of instructions, executable by the machine to perform a method for auto-configuring a Permanent Virtual Circuit (PVC) of a customer premises equipment device over an Asynchronous Transfer Mode (ATM) network.
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.
For example,
In addition, the present invention is not limited to protocol such as PPP or RFC 1483 but may be applied to any other protocol specific to DSL that sends periodically cells that are differentiable.
This application is a continuation application based on U.S. patent application Ser. No. 09/629,318, filed on Jul. 31, 2000, now U.S. Pat. No. 6,993,048, issued on Jan. 31, 2006.
Number | Name | Date | Kind |
---|---|---|---|
5237564 | Lespagnol et al. | Aug 1993 | A |
5274643 | Fisk | Dec 1993 | A |
5305311 | Lyles | Apr 1994 | A |
5311509 | Heddes et al. | May 1994 | A |
5313454 | Bustini et al. | May 1994 | A |
5327421 | Hiller et al. | Jul 1994 | A |
5345445 | Hiller et al. | Sep 1994 | A |
5345446 | Hiller et al. | Sep 1994 | A |
5365524 | Hiller et al. | Nov 1994 | A |
5390170 | Sawant et al. | Feb 1995 | A |
5390175 | Hiller et al. | Feb 1995 | A |
5394402 | Ross | Feb 1995 | A |
5400325 | Chatwani et al. | Mar 1995 | A |
5408469 | Opher et al. | Apr 1995 | A |
5422882 | Hiller et al. | Jun 1995 | A |
5426636 | Hiller et al. | Jun 1995 | A |
5428607 | Hiller et al. | Jun 1995 | A |
5430715 | Corbalis et al. | Jul 1995 | A |
5452297 | Hiller et al. | Sep 1995 | A |
5555244 | Gupta et al. | Sep 1996 | A |
5583862 | Callon | Dec 1996 | A |
5610910 | Focsaneanu et al. | Mar 1997 | A |
5740176 | Gupta et al. | Apr 1998 | A |
5742604 | Edsall et al. | Apr 1998 | A |
5799017 | Gupta et al. | Aug 1998 | A |
5864542 | Gupta et al. | Jan 1999 | A |
5883893 | Rumer et al. | Mar 1999 | A |
5953336 | Moore et al. | Sep 1999 | A |
6028867 | Rawson et al. | Feb 2000 | A |
6115380 | Christie et al. | Sep 2000 | A |
6240107 | Glass, III et al. | May 2001 | B1 |
6285671 | Bossemeyer, Jr. et al. | Sep 2001 | B1 |
6411622 | Ohgane | Jun 2002 | B1 |
6430187 | Park | Aug 2002 | B1 |
6480494 | Hawley | Nov 2002 | B1 |
6538998 | Garimella | Mar 2003 | B1 |
6563827 | Brueckheimer et al. | May 2003 | B1 |
6584074 | Vasamsetti et al. | Jun 2003 | B1 |
6597689 | Chiu et al. | Jul 2003 | B1 |
6636505 | Wang et al. | Oct 2003 | B1 |
6671278 | McBride et al. | Dec 2003 | B1 |
6714972 | Lee et al. | Mar 2004 | B1 |
6778505 | Bullman et al. | Aug 2004 | B1 |
6874041 | Burd et al. | Mar 2005 | B1 |
6975597 | Baker et al. | Dec 2005 | B1 |
6993048 | Ah Sue | Jan 2006 | B1 |
7215670 | Karlsson et al. | May 2007 | B1 |
7392301 | Perry, Jr. et al. | Jun 2008 | B1 |
20020101881 | Sundaresan et al. | Aug 2002 | A1 |
20030026273 | Davison et al. | Feb 2003 | A1 |
20050157711 | O'Dell et al. | Jul 2005 | A1 |
Number | Date | Country |
---|---|---|
9520850 | Aug 1995 | WO |
9520850 | Aug 1995 | WO |
9713382 | Apr 1997 | WO |
9713382 | Apr 1997 | WO |
9738511 | Oct 1997 | WO |
9738511 | Oct 1997 | WO |
Number | Date | Country | |
---|---|---|---|
20050213581 A1 | Sep 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09629318 | Jul 2000 | US |
Child | 11136835 | US |