Patent Application
20080159155
The present invention relates generally to communication networks and, more particularly, to a method and apparatus for providing trouble isolation for a permanent virtual circuit on networks such as the packet networks, e.g. Internet Protocol (IP) networks, Asynchronous Transfer Mode (ATM) networks, Frame Relay (FR) networks, etc.
An enterprise customer may build a Virtual Private Network (VPN) by connecting multiple sites or users over a network from a telephony service provider. The enterprise VPN and customer premise equipment such as Customer Edge Routers (CER) may be managed by the network service provider. When the network service provider manages the VPNs and CERs, the CERs are connected to the network service provider's Layer 2 network through a Provider Edge Router (PER). The Layer 2 network is typically an Asynchronous Transfer Mode (ATM) and/or Frame Relay (FR) network. The voice and data packets from the customer premise may traverse the Layer 2 network prior to reaching an IP network. For example, a Permanent Virtual Circuit (PVC) may be established for the customer through a Layer 2 network, e.g. an ATM network. However, when a customer or a monitoring system reports trouble for a PVC, the service provider may not be able to determine whether or not the reported trouble is due to a port failure/degradation or a PVC failure/degradation. Improper isolation increases the time and cost associated with handling the trouble. A ticket opened for a customer trouble may be inappropriately closed after testing a non-failed network segment. Trouble escalation and manual intervention add tremendous cost for maintenance of a network.
Therefore, there is a need for a method that provides trouble isolation for permanent virtual circuits.
In one embodiment, the present invention discloses a method and apparatus for providing trouble isolation for a Permanent Virtual Circuit (PVC) on packet networks. For example, the method receives an alert or a ticket for a Permanent Virtual Circuit (PVC) down or a PVC degraded and starts a correlation window for said PVC and port alert or ticket. The method then gathers a plurality of port and PVC alerts for a duration of said correlation window and determines whether or not a port down or a port degraded alert is received along with a PVC down or a PVC degraded alert in said correlation window for one or more ports associated with said PVC.
The teaching of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
The present invention broadly discloses a method and apparatus for providing trouble isolation for a Permanent Virtual Circuit (PVC). Although the present invention is discussed below in the context of packet networks, the present invention is not so limited. Namely, the present invention can be applied for other networks, e.g. Public Switched Telephone Network (PSTN).
In one embodiment, the packet network may comprise a plurality of endpoint devices 102-104 configured for communication with the core packet network 110 (e.g., an IP based core backbone network supported by a service provider) via an access network 101. Similarly, a plurality of endpoint devices 105-107 are configured for communication with the core packet network 110 via an access network 108. The network elements 109 and 111 may serve as gateway servers or edge routers for the network 110.
The endpoint devices 102-107 may comprise customer endpoint devices such as personal computers, laptop computers, Personal Digital Assistants (PDAs), servers, routers, and the like. The access networks 101 and 108 serve as a means to establish a connection between the endpoint devices 102-107 and the NEs 109 and 111 of the IP/MPLS core network 110. The access networks 101 and 108 may each comprise a Digital Subscriber Line (DSL) network, a broadband cable access network, a Local Area Network (LAN), a Wireless Access Network (WAN), and the like.
The access networks 101 and 108 may be either directly connected to NEs 109 and 111 of the IP/MPLS core network 110 or through an Asynchronous Transfer Mode (ATM) and/or Frame Relay (FR) switch network 130. If the connection is through the ATM/FR network 130, the packets from customer endpoint devices 102-104 (traveling towards the IP/MPLS core network 110) traverse the access network 101 and the ATM/FR switch network 130 and reach the border element 109.
The ATM/FR network 130 contains Layer 2 switches functioning as Provider Edge Routers (PER) and/or Provider Routers (PR). The PERs may also contain an additional Route Processing Module (RPM) that converts Layer 2 frames to Layer 3 Internet Protocol (IP) frames. An RPM enables the transfer of packets from a Layer 2 Permanent Virtual Connection (PVC) circuit to an IP network which is connectionless.
Some NEs (e.g., NEs 109 and 111) reside at the edge of the core infrastructure and interface with customer endpoints over various types of access networks. An NE that resides at the edge of a core infrastructure is typically implemented as an edge router, a media gateway, a border element, a firewall, a switch, and the like. An NE may also reside within the network (e.g., NEs 118-120) and may be used as a mail server, honeypot, a router, or like device. The IP/MPLS core network 110 also comprises an application server 112 that contains a database 115. The application server 112 may comprise any server or computer that is well known in the art, and the database 115 may be any type of electronic collection of data that is also well known in the art. Those skilled in the art will realize that although only six endpoint devices, two access networks, and so on are depicted in
The above IP network is described to provide an illustrative environment in which packets for voice and data services are transmitted on networks. An enterprise customer may build a Virtual Private Network (VPN) by connecting multiple sites or users over a network from a telephony service provider. The enterprise VPN may be managed by the network service provider. When the network service provider manages the VPNs, a Customer Edge Router (CER) located at the customer premise is connected to the network service provider's Layer 2 network through a Provider Edge Router (PER). For example, a VPN site for a customer may have a CER connected to a PER in the service provider's Layer 2 network. The Layer 2 network may be an Asynchronous Transfer Mode (ATM) and/or Frame Relay (FR) network. The customer traffic is then transmitted to the IP/MPLS core network through an ATM/FR switch network. The ATM/FR switch (attached to the IP/MPLS core network) converts the packets from Layer 2 ATM/FR cells to IP packets and forwards the IP packets towards a border element for the IP/MPLS core network. A Permanent Virtual Circuit (PVC) may be established over one or more trunks in the ATM/FR network and may be used for enabling traffic to traverse the ATM/FR network from one switch to another. However, when a customer or a monitoring system reports trouble for the PVC, the service provider may not be able to determine whether or not the reported trouble is due to a port failure/degradation or a PVC failure/degradation. Improper isolation increases the time and cost associated with handling the trouble. A ticket opened for a customer trouble may be inappropriately closed after testing a non-failed network component. Trouble escalation and/or manual intervention add tremendous cost for maintenance of a network and also reduce customer satisfaction with the quality of service. Therefore, there is a need for a method that provides trouble isolation for permanent virtual circuits.
In one embodiment, the current invention provides trouble isolation for permanent virtual circuits.
In one embodiment, the method also determines whether or not a customer allows intrusive testing. For example, a customer may subscribe to a service that includes trouble isolation among troubles at customer premise, network, etc. and allow the network to perform intrusive testing. For example, if a PVC down/degraded is reported, the service provider may determine whether or not the facility between the CER and PER is “down/degraded.” If the facility between the CER and PER is down or degraded, the service provider may notify the customer of a CPE problem. Otherwise, the service provider may proceed to perform tests on the ATM, PVC, etc. to sectionalize and refer the trouble to an appropriate work center.
In step 310, method 300 receives an alert or a ticket for a Permanent Virtual Circuit (PVC) “down” or “degraded.” For example, a customer interacts with a ticketing system and reports that a PVC is down or degraded. In another example, an alert collection system receives an alert for a PVC down.
In step 320, method 300 starts a correlation window for PVC and port alerts and/or tickets. For the example above, the PVC and port alert correlation window of 1 minute may be started. The time window for correlation is configured by the network service provider.
In step 330, method 300 gathers port and PVC alerts for the duration of said correlation window. For the example above, the PVC and port alert correlation system gathers PVC and port alerts for 1 minute for ports associated with said PVC.
In step 340, method 300 compares port and PVC alerts gathered over said correlation window. For the above example, the PVC and port alert correlation system compares the alerts for all ports associated with said PVC for the duration of said correlation window. For example, a port down or degraded alert may be received for one or more ports associated with said PVC in the same correlation time window.
In step 350, method 300 determines whether or not a port down or degraded alert is received along with a PVC down/degraded alert in said correlation window for one or more ports associated with said PVC. If at least one said port down or degraded alert is received, the method proceeds to step 360. Otherwise, the method proceeds to step 365.
In step 360, method 300 reports port down or degraded for said one or more ports. For example, the method may report a port on a switch used to establish the PVC is “down” or “degraded.” The method then proceeds to step 310 to continue receiving PVC down or degraded alerts and/or tickets. In one embodiment, the method also proceeds to step 370 to determine whether or not a customer allows intrusive testing.
In step 365, method 300 reports PVC down or degraded for said PVC. The method then proceeds to step 310 to continue receiving PVC down or degraded alerts and/or tickets. In one embodiment, the method also proceeds to step 370 to determine whether or not a customer allows intrusive testing.
In step 370, method 300 determines whether or not a customer allows intrusive testing. For example, a customer contract may include trouble isolation, diagnosis, and/or repair by performing intrusive testing. If the customer allows intrusive testing, the method proceeds to step 380. Otherwise, the method proceeds to step 310 to continue receiving PVC down or degraded alerts and/or tickets.
In step 380, method 300 isolates trouble to either a trouble on a facility between a Customer Edge Router (CER) and Provider Edge Router (PER) or a trouble on the network portion. The method then proceeds to step 390.
In step 390, method 300 reports trouble to customer and/or appropriate work center. For example, if the trouble is associated with the facility between the CER and PER, the method notifies the customer of trouble at the customer premise. If the trouble is on the network portion, the method may perform other tests to sectionalize the particular network portion and report the failure. For example, physical failures may be reported to one work center while failures associated with network congestion, software, etc. are reported to another work center. The method then proceeds to step 310 to continue receiving PVC down or degraded alerts and/or tickets.
It should be noted that the present invention can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the present module or process 405 for providing trouble isolation for a PVC on networks can be loaded into memory 404 and executed by processor 402 to implement the functions as discussed above. As such, the present method 405 for providing trouble isolation for a PVC on networks (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
