This invention relates generally to the field of telecommunications and, in particularly, to gateway systems for voice over broadband. More particularly, the present invention relates to a system and method for using switch fabric to support redundant network ports in a gateway system.
Digital subscriber line (DSL) technology was initially deployed to provide data-only service as a replacement for slower-speed, dial-up modems. Incumbent local exchange carriers (ILECs), competitive local exchange carriers (CLECs), and other telecommunication providers have begun to explore offering voice-over-Digital Subscriber Line (VoDSL) service, and other voice-over-broadband services, to deliver integrated voice and data services.
A central component of a typical VoDSL system is the voice gateway, or simply “gateway.” The gateway receives Voice over Internet Protocol (VoIP) or Voice over ATM (VoATM) information from the customer premises via network ports. The gateway then reformats the telecommunication information and sends it to a public switched telephone network (PSTN) via telecommunication ports. Likewise, telecommunication information from the PSTN is received at the telecommunication ports, packetized, and then transmitted to users via the ATM ports. Thus, the telephones, computers, and other telecommunication equipment at the customer premises are typically connected to the gateway via an ATM network, and the ATM ports in the gateway are wide area network (WAN) ports. The network ports typically reside on cards that plug in to the gateway. The network ports may, for example, connect to an ATM/IP network, a Digital Subscriber Line Access Multiplexor (DSLAM), or a Cable Modern Termination System (CMTS). Regarding specific techniques for encoding telecommunication information, there are several means available for carrying packetized voice over broadband, including the ATM Adaptation Layer Type 2 Broadband Loop Emulation Service (AAL2 BLES) protocol for carrying voice directly over ATM and the Voice over IP over ATM (VoIPoATM) protocol for transporting IP over ATM Adaptation Layer Type 5 (AAL5).
Gateways are now available with the capacity to process, bridge, and/or switch thousands of users. Network designers may also wish to oversubscribe the number of users based on statistical analysis of a network's behavior. In both cases, a large amount of user traffic passes through a typical gateway at any given time. Due to this large concentration of traffic, it is becoming increasingly important to maintain service, despite failure of components such as network ports.
One technique used to increase gateway reliability is to implement network port redundancy with automatic protection switching (APS). For conventional APS, the gateway is generally provided with at least one primary network port, known as the working port, and at least one redundant network port, known as the protection port. If the working port experiences a fault, the working port automatically passes the bearer traffic through to the protection port. Specifically, according to conventional APS, resources residing in the working port utilize a communication path that links the working port and the protection port to forward traffic received by the working port through to the protection port. Resources residing on the protection port receive the forwarded traffic and pass it through to the ATM network.
A disadvantage associated with this technique, however, is that additional resources must be provided on the network ports to support passing bearer traffic from the working port to the protection port. For example, the working port must include logic and hardware for detecting faults and forwarding traffic to the protection port. Thus, this method adds cost to the network ports. Furthermore, it may be necessary to remove the working port to cure the fault. However, removal of the working port will interrupt the bearer traffic that the working port passes through to the protection port unless additional steps are taken to otherwise reroute that traffic. There is therefore a need for improved protection-switching technologies that do not increase the cost of network ports and that allow working ports to be replaced easily without interrupting bearer traffic.
In accordance with the present invention, a system and method for supporting redundant network ports is provided that substantially eliminates or reduces disadvantages or problems associated with previously developed systems and methods. In a method according to the present invention for providing protection switching in a voice-over-broadband (VOB) gateway, egress traffic is multicast from a switch fabric to a working port and to a protection port. The working port forwards the egress traffic to a network in a working mode of operation, and the protection port forwards the egress traffic to the network in a protection mode of operation. Also, the working port forwards ingress traffic to the switch fabric in the working mode of operation, and the protection port forwards the ingress traffic to the switch fabric in the protection mode of operation. In one aspect, ingress traffic is forwarded from the protection port and not from the working port in the protection mode of operation. In another aspect, the working port and the protection port share protection status information, and the protection status information is used to select between the working mode of operation and the protection mode of operation.
A technical advantage of the present invention is the elimination of extra hardware and/or software on the working port and the protection port, which reduces the cost of the network ports. Another technical advantage is that faulty ports can be removed without interrupting a connection that has been rerouted to a protection port, which increases gateway reliability.
Additional features, functions, and technical advantages will become apparent upon review of the following description, claims, and figures, in which:
Gateway 30 also includes two or more network modules 36A–36C, each of which includes at least one network port. Gateway 30 sends and receives traffic to and from a network 16 via the network ports. For example, network 16 may be an IP or ATM network. In the example embodiment, the network port on network module 36A serves as a working port 46A and the network port on network module 36B serves as a protection port 46B, as described in greater detail below with reference to
Also included in gateway 30 are a control module 34 and a backplane 40 that includes communication paths which interconnect network modules 36A–36C and control module 34. Additional communication paths in backplane 40 interconnect control module 34 with telephony modules 38. In the example embodiment, each telephony module 38, each control module 34, and each network module 36A–36C resides on a distinct adapter card.
Control module 34 reformats the voice data from telephony modules 38 into a format suitable for transmission on network 16 and reformats the packets from network modules 36A–36C into a format suitable for transmission on telecommunication system 18. For instance, in the example embodiment, control module 34 encapsulates the voice data into packets for transmission on network 16 and extracts voice data from packets received from network 16 for transmission on telecommunication system 18.
Control module 34 includes a switch fabric 32 that controls how traffic flows between telephony modules 38 and network modules 36A–36C. The traffic flowing from gateway 30 to network 16 is known as egress traffic, and the traffic that gateway 30 receives from network 16 is known as ingress traffic. In the example embodiment, switch fabric 32 is a high-capacity switch fabric 32 capable of IP and/or ATM multicast, and gateway 30 utilizes the multicast functionality to provide protection switching without adding extra components, and hence cost, to the system.
Referring now to
Also, network ports 46A and 46B are shown residing on network modules 36A and 36B, respectively. Network ports 46A and 46B are also referred to as working port 46A and protection port 46B, respectively. For ingress traffic as well as egress traffic, both working port 46A and protection port 46B maintain a copy of the same connection tables. For egress traffic, switch fabric 32 simply multicasts traffic to both working port 46A and protection port 46B. Consequently, in the case of a fault on the working port, no new bearer connections to re-route traffic to protection port 46B are necessary. All traffic entering the switch fabric is simply copied to both ports 46A and 46B.
As
The process of
As indicated at block 202, network ports 46A and 46B then use status ports 50A and 50B and status path 52 to share status information reflecting the results of the monitoring. As depicted at block 210, network ports 46A and 46B then determine whether to switch from working mode to protection mode, based one the status information. For example, gateway 30 may use the Bellcore GR-253-CORE SONET (Synchronous Optical Network) standard for network communications, and network ports 46A and 46B may determine which mode should be used (i.e., working or protection), in accordance with that standard. For instance, network ports 46A and 46B may share bearer and APS status signals, such as loss of service (LOS), signal fail (SF), and signal degrade (SD). Nevertheless, although status signals may be passed between status ports 50A and 50B, the telecommunication information is not passed between status ports 50A and 50B but is instead sent and received directly to and from switch fabric 32 via data paths 54A and 54B.
If it is determined to switch to protection mode, working port 46A opens protection switch 44A and protection port 46B closes protection switch 44B, as depicted at blocks 212 and 214. Consequently, in protection mode, only protection port 46B carries the ingress traffic and egress traffic between network 16 and switch fabric 32. The process then returns to block 202, with network ports 46A and 46B monitoring conditions and sharing status information as described above.
However, the determination depicted at block 210 whether to switch to protection mode may be negative. For example, communications may be flowing in a satisfactory manner through working port 46A, or gateway 30 may already be operating in protection mode. If the determination at block 210 is negative, it is determined whether to revert to working mode, as indicated at block 220. If the current mode is protection mode and it is determined to revert to working mode, working port 46A closes protection switch 44A and protection port 46B opens protection switch 44B, as depicted at blocks 222 and 224. Switch fabric 32 consequently communicates ingress traffic and egress traffic with network 16 only via working port 46A. The process then returns to block 202. Network ports 46A and 46B then continue to monitor conditions and share status information, and gateway 30 continues to provide protection switching in response to changing conditions, as described above.
Thus, in working mode, ingress and egress traffic passes between network 16 and switching fabric 32 through components including working port 46A, protection switch 44A, data interface 56A, and data path 54A. In protection mode, by contrast, ingress and egress traffic passes between network 16 and switching fabric 32 through components including protection port 46B, protection switch 44B, data interface 56B, and data path 54B. Ingress and egress traffic may pass between network ports 46A and 46B and network 16 via a Y cable that includes a junction 42 and a network connector 48. The example embodiment thus provides automatic equipment protection for working port 46A. By filtering ingress traffic before it reaches switch fabric 32, network ports 46A and 46B prevent traffic sequencing errors that might otherwise result because the ingress traffic is routed to the same output port.
In an alternative embodiment, independent working and protection lines exist back to network 16. That is, the working and protection ports have independent connections or lines to network 16, and the egress traffic is not affected by protection switches 44A and 44B. However, the ingress traffic is still filtered at least on the inactive port (e.g., by switches like protection switches 44A and 44B) to avoid sequencing errors at switch fabric 32. Such an alternative embodiment may therefore provide line and equipment protection, in accordance with protection standards such as 1+1 SONET APS.
Among the advantages of the above embodiments is that they make more effective use of the bandwidth between the switch fabric and the network ports, rather than requiring bandwidth for telecommunication information between the working port and the protection port. In addition, since multicast is used for egress traffic, the software or other control logic for the gateway does not need to provision any new bearer connections to re-route traffic to the protection port. Further, the embodiments allow for component cost savings, since no components for bridging traffic between network ports are required. Also, in the described embodiments, faulty ports can be replaced without interrupting traffic flow between the switching fabric and the network. For example, when a gateway is in protection mode, a new working port may be swapped for a defective working port without interrupting traffic flow between the switch fabric and the protection port.
Although an example embodiment of the present invention has been described, myriad changes and variations may be made and used without departing from the scope and spirit of this invention. For example, although the discussion above refers to VoDSL service, alternative embodiments of the invention provide the functionality and advantages described above for gateways that utilize other types of broadband connections. Products that may benefit from the invention include, without limitation, DSLAMs, ATM switches, Routers, Voice Gateways, CMTSs, high-capacity packet transport products, and SONET Add-Drop Multiplexors. Likewise, it should be understood that the number of network modules, telephony modules, and control modules can be varied from that depicted in the example embodiment according to the needs of a particular implementation.
In addition, the example embodiment depicts the working and protection ports as physically residing on separate cards that are each connected to a backplane of a chassis that also houses the control module. In an alternative embodiment, however, the working and protection ports may reside on the same card. Nevertheless, in that alternative embodiment, the switch fabric would still use a first communication path of the backplane to send the telecommunication information to the working port and a second communication path of the backplane to send the telecommunication information to the protection port.
Furthermore, in the illustrated embodiment, the modules and components depicted within the gateway represent functional elements that are reasonably self-contained so that each can be designed, constructed, and updated substantially independently of the others. In a particular embodiment, some or all of those modules and components are implemented on one or more separate printed circuit boards or cards that may be coupled to a backplane in chassis. However, in alternative embodiments, the gateway may include different hardware, software, or combinations of hardware and software for providing the functionality described and illustrated in this application. The invention is therefore not to be limited to the example embodiment, but is to be defined by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4381427 | Cheal et al. | Apr 1983 | A |
4493092 | Adams | Jan 1985 | A |
4504942 | Aro et al. | Mar 1985 | A |
4507793 | Adams | Mar 1985 | A |
4512025 | Frankel et al. | Apr 1985 | A |
4578537 | Faggin et al. | Mar 1986 | A |
4608686 | Barsellotti | Aug 1986 | A |
4627046 | Bellamy | Dec 1986 | A |
4740963 | Eckley | Apr 1988 | A |
4748656 | Gibbs et al. | May 1988 | A |
4757497 | Bierele et al. | Jul 1988 | A |
4843606 | Bux et al. | Jun 1989 | A |
4853949 | Schorr et al. | Aug 1989 | A |
4881226 | Lechner et al. | Nov 1989 | A |
4903292 | Dillon | Feb 1990 | A |
5033062 | Morrow et al. | Jul 1991 | A |
5034948 | Mizutani et al. | Jul 1991 | A |
5127003 | Doll, Jr. et al. | Jun 1992 | A |
5134611 | Steinka et al. | Jul 1992 | A |
5142568 | Ogata et al. | Aug 1992 | A |
5142571 | Suzuki et al. | Aug 1992 | A |
5151923 | Fujuwara | Sep 1992 | A |
5216704 | Williams et al. | Jun 1993 | A |
5220560 | Ogasawara | Jun 1993 | A |
5247347 | Litteral et al. | Sep 1993 | A |
5267300 | Kao et al. | Nov 1993 | A |
5305312 | Fornek et al. | Apr 1994 | A |
5317627 | Richardson, Jr. et al. | May 1994 | A |
5341374 | Lewen et al. | Aug 1994 | A |
5349640 | Dunn et al. | Sep 1994 | A |
5367522 | Otani | Nov 1994 | A |
5410343 | Coddington et al. | Apr 1995 | A |
5426692 | Fujise | Jun 1995 | A |
5448635 | Biehl et al. | Sep 1995 | A |
5473675 | Chapman et al. | Dec 1995 | A |
5479447 | Chow et al. | Dec 1995 | A |
5493609 | Winseck, Jr. et al. | Feb 1996 | A |
5499241 | Thompson et al. | Mar 1996 | A |
5604737 | Iwami et al. | Feb 1997 | A |
5606553 | Christie et al. | Feb 1997 | A |
5610910 | Focsaneanu et al. | Mar 1997 | A |
5610922 | Balatoni | Mar 1997 | A |
5617423 | Li et al. | Apr 1997 | A |
5625404 | Grady et al. | Apr 1997 | A |
5625685 | Allegranza et al. | Apr 1997 | A |
5638363 | Gittins et al. | Jun 1997 | A |
5661785 | Carpenter et al. | Aug 1997 | A |
5668857 | McHale | Sep 1997 | A |
5671251 | Blackwell et al. | Sep 1997 | A |
5673290 | Cioffi | Sep 1997 | A |
5675575 | Wall, Jr. et al. | Oct 1997 | A |
5692035 | O'Mahony et al. | Nov 1997 | A |
5719870 | Baker et al. | Feb 1998 | A |
5737333 | Civaniar et al. | Apr 1998 | A |
5771236 | Sansom et al. | Jun 1998 | A |
5781547 | Wilson | Jul 1998 | A |
5781617 | McHale et al. | Jul 1998 | A |
5787088 | Dagdeviren et al. | Jul 1998 | A |
5793843 | Morris | Aug 1998 | A |
5828666 | Focsaneanu et al. | Oct 1998 | A |
5838682 | Dekelbaum et al. | Nov 1998 | A |
5841840 | Smith et al. | Nov 1998 | A |
5848150 | Bingel | Dec 1998 | A |
5862134 | Deng | Jan 1999 | A |
5864747 | Clark et al. | Jan 1999 | A |
5878120 | O'Mahony | Mar 1999 | A |
5881142 | Frankel et al. | Mar 1999 | A |
5883941 | Akers | Mar 1999 | A |
5889773 | Stevenson, III | Mar 1999 | A |
5889774 | Mirashrafi et al. | Mar 1999 | A |
5889856 | O'Toole et al. | Mar 1999 | A |
5896377 | Boot et al. | Apr 1999 | A |
5898761 | McHale et al. | Apr 1999 | A |
5901205 | Smith et al. | May 1999 | A |
5905781 | McHale et al. | May 1999 | A |
5907548 | Bernstein | May 1999 | A |
5917814 | Balatoni | Jun 1999 | A |
5936952 | Lecomte | Aug 1999 | A |
5940479 | Guy et al. | Aug 1999 | A |
5943404 | Sansom et al. | Aug 1999 | A |
5949763 | Lund | Sep 1999 | A |
5959972 | Hamami | Sep 1999 | A |
5974043 | Solomon | Oct 1999 | A |
5978390 | Balatoni | Nov 1999 | A |
5982767 | McIntosh | Nov 1999 | A |
5991292 | Focsaneanu et al. | Nov 1999 | A |
5999565 | Locklear, Jr. et al. | Dec 1999 | A |
5999598 | Henrick et al. | Dec 1999 | A |
6075784 | Frankel et al. | Jun 2000 | A |
6075796 | Katseff et al. | Jun 2000 | A |
6078580 | Mandalia et al. | Jun 2000 | A |
6081517 | Liu et al. | Jun 2000 | A |
6101182 | Sistanizadeh et al. | Aug 2000 | A |
6112084 | Sicher et al. | Aug 2000 | A |
6118780 | Dunn et al. | Sep 2000 | A |
6125113 | Farris et al. | Sep 2000 | A |
6125117 | Martin et al. | Sep 2000 | A |
6130879 | Liu | Oct 2000 | A |
6130883 | Spear et al. | Oct 2000 | A |
6134235 | Goldman et al. | Oct 2000 | A |
6141339 | Kaplan et al. | Oct 2000 | A |
6144667 | Doshi et al. | Nov 2000 | A |
6144670 | Sponaugle et al. | Nov 2000 | A |
6154445 | Farris et al. | Nov 2000 | A |
6157637 | Galand et al. | Dec 2000 | A |
6167042 | Garland et al. | Dec 2000 | A |
6175562 | Cave | Jan 2001 | B1 |
6175854 | Bretscher | Jan 2001 | B1 |
6181694 | Pickett | Jan 2001 | B1 |
6181715 | Phillips et al. | Jan 2001 | B1 |
6201806 | Moffett | Mar 2001 | B1 |
6208639 | Murai | Mar 2001 | B1 |
6222829 | Karlsson et al. | Apr 2001 | B1 |
6229810 | Gerszberg et al. | May 2001 | B1 |
6236653 | Dalton et al. | May 2001 | B1 |
6240084 | Oran et al. | May 2001 | B1 |
6240085 | Iwami et al. | May 2001 | B1 |
6243377 | Phillips et al. | Jun 2001 | B1 |
6243398 | Kahane et al. | Jun 2001 | B1 |
6259708 | Cheng et al. | Jul 2001 | B1 |
6262979 | Anderson et al. | Jul 2001 | B1 |
6359858 | Smith et al. | Mar 2002 | B1 |
6512762 | Renucci et al. | Jan 2003 | B1 |
20020089925 | Smith et al. | Jul 2002 | A1 |
20020089926 | Kloth | Jul 2002 | A1 |
Number | Date | Country |
---|---|---|
0 841 831 | May 1998 | EP |
2313979 | Dec 1997 | GB |
WO 9723078 | Jun 1997 | WO |
WO 9737458 | Oct 1997 | WO |
WO 9842104 | Sep 1998 | WO |
WO 9949608 | Sep 1999 | WO |
WO 0056050 | Sep 2000 | WO |
WO 0069131 | Nov 2000 | WO |
WO 0105130 | Jan 2001 | WO |
WO 0106720 | Jan 2001 | WO |
WO 0113593 | Feb 2001 | WO |
WO 0113618 | Feb 2001 | WO |