WO2005094000A1 - Fault management in a ethernet based communication system - Google Patents
Fault management in a ethernet based communication system Download PDFInfo
- Publication number
- WO2005094000A1 WO2005094000A1 PCT/IB2004/000817 IB2004000817W WO2005094000A1 WO 2005094000 A1 WO2005094000 A1 WO 2005094000A1 IB 2004000817 W IB2004000817 W IB 2004000817W WO 2005094000 A1 WO2005094000 A1 WO 2005094000A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- fault
- ethernet
- status
- link
- cable
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
- H04L12/40032—Details regarding a bus interface enhancer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/4013—Management of data rate on the bus
- H04L12/40136—Nodes adapting their rate to the physical link properties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/06—Generation of reports
- H04L43/065—Generation of reports related to network devices
Definitions
- Ethernet generally requires multi-pair copper wire (e.g., Category 5 (CAT 5) cable) for 10/100 Base-T interfaces.
- CAT 5 Category 5
- copper-based Ethernet interfaces have distance limitations (approximately 100 meters over CAT 5 cabling) and there is generally no ability to diagnose cable faults for copper-based Ethernet links, hi addition, there are limited carrier-class performance monitoring and diagnostic capabilities on Ethernet links.
- a method and system for detecting and diagnosing a fault in an Ethernet service interface The fault is detected and diagnosed from a first point in a communications link, where the communications link includes the Ethernet service interface and terminates at a second point.
- the method comprises monitoring the link from the first point to detect an occurrence of the fault, where the fault occurs between the first and second points.
- At least one fault attribute is identified when the fault is detected, where the fault attribute is identified from the first point, and one or more potential causes for the fault are categorized based on the identified fault attribute.
- BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a flow chart illustrating a method for establishing, managing, and isolating faults from a single end of an Ethernet connection.
- Fig. 2 is an exemplary network in which the method of Fig. 1 may be implemented.
- Figs. 3 and 4 are a flow chart illustrating another embodiment of a method for establishing, managing, and isolating faults from a single end of an Ethernet connection in the network of Fig. 2.
- Fig. 5 is another exemplary network in which the method of Fig. 1 may be implemented.
- Figs. 6 and 7 are a flow chart illustrating another embodiment of a method for establishing, managing, and isolating faults from a single end of an Ethernet connection in the network of Fig. 5.
- Fig. 8 illustrates one embodiment of a exemplary system for remotely switching a line status between terminated and non-terminated. Figs.
- FIG. 9 and 10 illustrate another embodiment of an exemplary system for remotely switching a line status between terminated and non-terminated DETAILED DESCRIPTION
- the present disclosure relates generally to communication services and, more specifically, to a system and method for deploying and managing Ethernet services. It is understood, however, that the following disclosure provides many different embodiments, or examples, for implementing different features of the invention. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting.
- the present disclosure may repeat reference numerals and or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. Referring to Fig.
- a method 10 is operable to provide pre-service, in- service, and out-of-service Ethernet capabilities from a single end of a network. As will be described later in greater detail, this enables a service provider to provision and monitor an Ethernet service interface, as well as detect and diagnose faults in the Ethernet service interface in a cost-effective manner. Such functionality may be achieved, for example, by using cable-testing equipment to add monitoring and diagnostic capabilities to legacy equipment for end-to-end services.
- an initial state is established. This may include, for example, establishing a link, checking a status of the link, verifying service, testing cable length, obtaining service parameters, and similar actions.
- a determination is made as to whether the link status meets certain predefined performance criteria.
- step 24 If the link status fails, the method 10 jumps to step 24, where an attempt is made to isolate the fault. The method 10 then continues to step 26, where the fault is corrected. The type of correction may depend on the fault, and may range from the activation of automatic correction procedures to initiating a truck roll to send a technician to a location where the fault was diagnosed. The method 10 then returns to step 14. If the link status passes step 14, the method 10 continues to step 16 where an auto-negotiation process occurs. If the auto-negotiation process fails, as determined in step 18, the method 10 jumps to steps 24 and 26 to isolate and correct the fault. If the auto-negotiation is successful, the method 10 continues to step 20, where it monitors the link for faults, service degradation, and other problems.
- the monitoring may include comparing current service conditions (e.g., packet loss) to a predefined set of parameters. If a fault occurs, as determined in step 22, the method 10 continues to steps 24 and 26 to isolate and correct the fault. Accordingly, the method enables a problem in an Ethernet connection to be identified and isolated from a single end of the Ethernet connection (e.g., from a service provider's end).
- an exemplary network 30 provides a framework within which the method 10 of Fig. 1 may be executed to provide Ethernet services from a service provider 32 to a plurality of subscriber devices 34.
- the service provider 32 may be located at a central office or a similar point of presence that is connected to the network 30 through a device 36, such as a Synchronous Optical Network (SONET) add/drop multiplexer (ADM), which forms part of a SONET network 37.
- SONET Synchronous Optical Network
- ADM add/drop multiplexer
- the device 36 is connected via fiber optics to another device 38, which is located relatively close to the subscriber devices 34 due to distance limitations imposed by Ethernet connectivity.
- the device 38 which incorporates SONET ADM technology, is operable to separate data intended for the subscriber devices 34 from other data being transported through the SONET network, as well as to add data from the subscriber devices 34 before passing it to the device 36.
- the device is connected to the subscriber devices 34 through cabling 40 appropriate for Ethernet communications (e.g., Category 5 (CAT 5) cable).
- CA5 Category 5
- Each cable may be connected to a layer 2 (L2) switch 42 that serves to terminate the Ethernet services at each subscriber device 34.
- L2 layer 2
- TDRs time domain reflectometers
- the device 38 includes a plurality of 10/100BaseT Ethernet ports (not shown), which are provided as a module. These Ethernet ports enable the subscriber devices 34 to connect directly to the device 38 via a standard Ethernet cable (lOBaseTX, 100BaseTX).
- a method 50 utilizes steps 52-78 to enable single-ended management of the device 38 and associated components by the service provider 32 to initialize, monitor, and diagnose problems with an Ethernet service interface as follows.
- the method 50 is implemented by extending the capabilities provided by Transaction Language 1 (TL1) commands in data transport services.
- T1 Transaction Language 1
- a link is established and link parameters are determined. This may include provisioning the Ethernet module (e.g., by using an ENT-EQPT command) and provisioning the Ethernet service interface (e.g., by using an ENT-E100 command), with port parameters defaulting to predetermined values.
- An Ethernet service is created by connecting one of the interfaces to a transport facility (e.g., the device 36).
- the method 50 determines a current link status (e.g., good or bad) in step 54. If the link status is bad, the method 50 enters a fault isolation stage, which will be described later with respect to Fig. 4. If the link status if good, the method 50 continues to step 56, where an auto-negotiation procedure is initiated. If the auto-negotiation is not successful, as determined in step 58, the method 50 continues to the fault isolation stage of Fig. 4.
- a current link status e.g., good or bad
- the method 50 enters a fault isolation stage, which will be described later with respect to Fig. 4. If the link status if good, the method 50 continues to step 56, where an auto-negotiation procedure is initiated. If the auto-negotiation is not successful, as determined in step 58, the method 50 continues to the fault isolation stage of Fig. 4.
- step 60 link parameters (e.g., cable status and cable length) are captured.
- the captured parameters may be used for future fault isolation purposes.
- the captured cable length may be used in future fault reports to determine whether to report failures as "near end” (e.g., the end on the service provider's equipment, device 38) or "far end” (e.g., the end on the subscriber devices 34).
- near end e.g., the end on the service provider's equipment, device 38
- far end e.g., the end on the subscriber devices 34.
- the present method 50 incorporates Automatic IN-Service (AINS), which allows an operator to place an Ethernet port in the in-service state prior to a physical cable being attached to the port. Any alarms on the port will be squelched until the method 50 has detected a valid signal on the port for some predefined period of time (e.g., ten seconds). Once the period of time has elapsed, the port will revert to normal operating mode and will report alarms. Once the Ethernet interface is placed in service, the method 50 continues to steps 62, 64 and performs monitoring operations.
- AINS Automatic IN-Service
- the monitoring may check for link failure, loss of carrier and/or signal, low light conditions (for fiber optic interfaces), restart of auto-negotiation, remote fault indication, and faults, such as those generated by incorrect link parameters (e.g., cable status and length).
- the monitoring may also check for other faults and service degradation issues, as well as collect statistics for trend analysis. If a fault is detected in step 64, the method transitions to an out-of-service autonomous state (OOS-AU) and continues to step 66 of Fig. 4 to attempt to isolate the fault. It is understood that some tests may occur while the Ethernet interface is in service, while other tests may require that the interface be removed from service (e.g., disruptive testing).
- OOS-AU out-of-service autonomous state
- in-service testing may occur for testing cable length during regular operation in 100/1000 Mbps modes.
- Out-of-service testing may allow the testing of the device 38 and its associated ports, and cables leading to the device 38.
- out-of-service testing may test equipment output transmitters and input receivers via internal loopback, as well as perform both terminated and non- terminated Ethernet cable problem analysis.
- Non-terminated analysis includes, for example, fault isolation along a cable and, for each cable connected to a port, identifying open circuits, short circuits, and impedance mismatches. Estimation of cable length on a properly terminated cable can be used to identify the location of a subsequent fault.
- step 66 a local loopback test is conducted on the local equipment. If it is determined in step 68 that the local loopback test has failed, then the fault is likely due to a local equipment failure as indicated by step 70. Corrective measures may be taken and the method 50 returns to step 56. If the local loopback test passes, then the fault is not in the local equipment and the method 50 continues to step 72, where a cable status check is made.
- the cable status may be determined using, for example, Ethernet PHYs with integrated TDR capability or standalone TDRs as described with respect to Fig. 2 and may be caused by a number of problems.
- an invalid Ethernet cable length may be caused by an improper termination, while a change in cable length from an initially characterized value (obtained in step 60) may indicate a change to the cable (e.g., the addition of a bad cable segment).
- the cable status is not valid (e.g., the cable is disconnected or broken)
- the fault is likely due to a cable problem, as indicated in step 78.
- the cable status is valid, then the fault is likely due to a remote equipment failure.
- Corrective measures may be taken in step 80 and the method 50 returns to step 52.
- Fig. 4 may be expanded to encompass a variety of failure scenarios, such as auto-negotiation failure. Accordingly, the method 50 of Figs.
- an exemplary network 90 provides a framework within which the method 10 of Fig. 1 may be executed to provide Ethernet services from a service provider 92 to a plurality of subscriber devices 94.
- the service provider 92 is connected to a device 96 through a SONET-based fiber optic connection 98.
- the device 96 is operable to connect the service provider 92 to a device 102 (e.g., a media converter) through a copper wire network 100 using, for example, an Ethernet Media extension (EMX) service in which Ethernet frames are carried over the copper wire network 100.
- the network 100 in the present example is the local loop plant comprised of twisted copper pairs , such as is known in the art.
- the device 102 includes an interface (e.g., a modem) for communicating via digital subscriber line (e.g., DSL, SHDSL, VDSL; which are herein referred to collectively as DSL) with the device 96, and an Ethernet interface for providing Ethernet services to the subscriber devices 94 via Ethernet compatible cabling 104.
- DSL digital subscriber line
- the device 102 presents the subscriber devices 94 with 10/100BaseT interface ports and may use DSL technologies on a wide area network (WAN) interface to extend the reach of an Ethernet link up to several thousand feet. If a WAN interface is provided, the device 102 provides enhanced visibility of loop conditions and performance monitoring on the device's subscriber Ethernet ports, as well as enhanced WAN link management via DSL loop management techniques and embedded management channels. In this manner, problems associated with the WAN extension may be diagnosed and single ended management features may be implemented on the client interface. In the present example, both the Ethernet and DSL interfaces provide their respective ports through modules. The Ethernet ports are modeled as client ports and, to activate the ports, the Ethernet module is first provisioned (either manually or automatically). The Ethernet ports on the module may then be provisioned.
- WAN wide area network
- each of the Ethernet ports may be associated with AINS, which enables the Ethernet port to be preprovisioned in a ready state prior to a physical cable being attached to the port. Any alarms on the Ethernet port will be squelched until a valid signal has been detected on the port for a predetermined period of time (e.g., ten seconds). Once the period of time has elapsed, the Ethernet port will revert to normal operating mode and will report alarms.
- the device 102 may also conduct automatic Ethernet fault isolation upon detection of a failure using cable and equipment diagnostic features, which will be described in greater detail in the following text.
- automatic isolation diagnostics may attempt an equipment port loopback at device 102 to check transmitter and receiver functions. If no transmitter or receiver faults are detected, a loop fault would be reported.
- the device 102 may extend Ethernet services to carrier serving area ranges and hide details of DSL link management from an operator. Accordingly, due to the system automatically provisioning the DSL link, there is no need to manually provision the DSL link when creating "remote" Ethernet ports. The Ethernet ports may raise alarms on detecting predefined conditions or events.
- an alarm may be raised on the basis of a link fault, a jabber (e.g., a condition where a station transmits for a period of time longer than the permissible packet length) receive, or a remote fault.
- a link fault e.g., a jabber (e.g., a condition where a station transmits for a period of time longer than the permissible packet length) receive, or a remote fault.
- These alarms are reported from the device 102 to the device 96 which reports them to the operator 92.
- a DSL link and port implemented via the device 102's DSL interface (and module) may also be the source of faults.
- the device 102 may monitor the DSL interface for alarm conditions such as loss of signal, loss of synchronization, and loop attenuation defects (e.g., where a loop attenuation threshold is exceeded).
- DSL port and equipment failures may raise alarms associated with network termination, loss of power, modem fault, port module removal (e.g., the module terminating the port is removed), and mismatched provisioning (e.g., there is a module provisioning mismatch with the physical module present in a slot).
- Performance monitoring may occur at two points. Firstly, EtherStat performance monitoring may be conducted on the Ethernet ports at device 102 to allow the service provider to monitor the subscriber device's incoming traffic conditions at a predefined demarcation point. Secondly, the DSL link may be monitored at both the device 96 and the device 102 to provide information relating to the condition and performance of the digital local loop between the service provider 96 and the subscriber devices 102. Statistical data may be collected as previously described.
- Performance of the DSL link is monitored for both upstream and downstream directions.
- the modem associated with the device 102 collects performance counts which are forwarded to the device 96.
- the DSL link is monitored at the termination point on the DSL module. Performance monitoring may collect a variety of different statistics, as are disclosed in previously incorporated U.S. Provisional Patent Application Ser. No. (Attorney Docket No. 31873.18).
- the DSL loop may be non-terminated (e.g., the device 102 is not present or not physically connected) or the device 102 may be present and physically connected.
- the loop may be non-terminated in cases where an operator connects a non- terminated loop to a port to perform single-ended loop qualification diagnostics.
- an operator may issue a diagnose command against the device 96, which enables the operator to characterize/test the DSL loop during pre-service activation. If the device 102 is physically connected and provisioned (e.g., a service is or has been running and a diagnostic is required to isolate a fault condition), the operator issues the diagnose command against the device 102 (to diagnose an Ethernet port problem) or against the Ethernet service connected to the device 102 (to diagnose a DSL line problem). As previously described, some diagnostic tests may be executed while a connection is in-service, while others require that the connection be placed out-of-service.
- In-service diagnostics on the Ethernet ports of the device 102 are restricted to testing the Ethernet interface, hi the present example, there are no in-service diagnostics available on the DSL loop other than performance monitoring.
- Out-of-service testing e.g., disruptive testing
- the device 102 and the Ethernet service associated with the device should be out- of-service at the time of testing. This testing enables an operator to test and isolate faults on the Ethernet port and cable associated with a subscriber device 94, as well as faults associated with the DSL port and DSL physical link. If the device 102 is in-service during the test, only cable length (e.g., non-disruptive) testing may be done.
- a number of out-of-service tests may be performed on the device 102. These include a port transmitter and receiver check on the Ethernet ports, which use internal loopback to enable detection of output transmitter or receiver input failures. Ethernet cable problem analysis may be performed for either non-terminated (TDR testing) or terminated cables. DSL equipment port transmitter and receiver diagnostics may be executed using internal loopback to enable detection of output transmitter or receiver input failures.
- DSL link diagnostics may be executed from device 96 using single-ended loop diagnostics to determine certain characteristics of an non-terminated DSL Digital Local Loop (DLL), such as loop length, loop termination (e.g., whether the loop is an open or short circuit), loop gauge, upstream and downstream capacity (in bps), ideal upstream and downstream capacity (in bps) (e.g., capacity without considering effects of implementation loss), and dual ended loop testing.
- DLL Digital Local Loop
- a method 106 utilizes steps 108-156 to enable single-ended management of the device 102 and associated components by the service provider 92 to initialize, monitor, and diagnose problems with an Ethernet interface as follows, the present example, the method 106 is implemented by extending the capabilities provided by DSL commands in data transport services. A more detailed description of specific commands and associated information is disclosed in previously incorporated U.S. Provisional Patent Application Ser. No. (Attorney Docket No. 31873.18). It is understood that corrective measures may be taken after a fault is detected and isolated, but such measures are not explicitly denoted in Figs. 6 and 7. Beginning in step 108, a link is established and link parameters are determined.
- the method 106 determines a current DSL link status (e.g., good or bad) in step 110. If the link status is bad, the method 106 enters a fault isolation stage, which will be described later with respect to Fig. 7. If the link status if good, the method 106 continues to step 112, where DSL parameters are captured. The method 106 then continues to step 114, where it determines whether an Ethernet link status. If the Ethernet link status is not good, then the method 106 enters the fault isolation stage that will be described later with respect to Fig. 7. If the method Ethernet status is good, the method 106 continues to step 116, where it captures Ethernet link parameters (e.g., cable status and cable length).
- Ethernet link parameters e.g., cable status and cable length
- the method 106 then continues to steps 118, 120 and performs monitoring operations.
- the monitoring may check for link failure, loss of carrier and/or signal, low light conditions (for fiber optic interfaces), restart of auto-negotiation, remote fault indication, and a change in link parameters, such as cable status and length.
- the monitoring may also check for other faults and service degradation issues, as well as collect statistics for trend analysis. If a fault is detected in step 120, the method transitions to an out-of-service autonomous state (OOS-AU) and continues to step 122 of Fig. 7 to attempt to isolate the fault.
- OOS-AU out-of-service autonomous state
- step 122 one or more tests are run automatically to determine whether the fault detected in step 120 is due to a local equipment failure, remote equipment failure, or a cable problem.
- step 122 the DSL link status is determined. If the link status is good, the method 106 continues to steps 124, 126, where it conducts an Ethernet local loopback test and determines whether the test passed or failed. If it is determined in step 126 that the test failed, then the fault is likely due to an equipment fault, as indicated in step 128. The method 106 then returns to step 110. If it is determined in step 126 that the test passed, then the method 106 conducts a cable test and determines whether the test passed or failed in steps 130, 132.
- step 132 If it is determined in step 132 that the test failed, then the fault is likely due to a cable problem, as indicated in step 134. The method 106 then returns to step 114. If it is determined in step 132 that the test passed, then the method continues to step 136, where it initiates an auto-negotiation procedure. hi step 138, a determination is made as to whether the auto-negotiation procedure succeeded or failed. If the auto-negotiation procedure failed, the fault is likely due to a remote equipment problem, as indicated in step 140. However, if the auto-negotiation procedure succeeded, the method returns to step 114 and checks the Ethernet link status as previously described. Returning to step 122 of Fig.
- step 142 a DSL loopback test is conducted. If it is determined in step 144 that the test failed, then the fault is likely due to an equipment fault, as indicated in step 128. The method 106 then returns to step 110. If it is determined in step 144 that the test passed, then the method 106 conducts a cable test and determines whether the test passed or failed in steps 146, 148. If it is determined in step 148 that the test failed, then the fault is likely due to a cable problem, as indicated in step 150. The method 106 then returns to step 114.
- step 148 If it is determined in step 148 that the test passed, then the method continues to step 152, where it initiates a DSL link handshake.
- step 154 a determination is made as to whether the handshake succeeded or failed. If the handshake failed, the fault is likely due to a remote equipment problem, as indicated in step 156. However, if the handshake succeeded, the method returns to step 110 and checks the DSL link status as previously described. Accordingly, the method 106 of Figs. 6 and 7 utilizes components of the network 90 of Fig. 5 to provide and manage Ethernet services. Furthermore, the method 106 enables the detection and isolation of faults to enable the service provider 92 to rapidly identify and address disruptions and potential disruptions to the Ethernet service.
- TDR TDR technology
- various fault attributes e.g., type, location
- similar information e.g., type, location
- TDR technology which operates using reflected signals, is generally ineffective on properly terminated lines. Accordingly, to maximize the benefit of the TDR technology, a line that is to be characterized should not be terminated, which frequently means that a technician needs to visit a site and physically disable the connection. Once the connection is removed, tests can be run on the line.
- an exemplary DSL environment includes service provider line side equipment 160 and a DSL modem 164, which may be located on a subscriber's premises.
- the equipment 160 may be associated with a DSL unit 162, which enables the equipment 160 and modem 164 to communicate via a line 166.
- the modem 164 may include an analog front end 170, a DSL processor/digital signal processor 172, a service side interface (e.g., Ethernet), and a microcontroller or processor 176, as well as various connections and interfaces between these components.
- the modem 164 also includes a circuit 168, which is accessible to both the analog front end 170 and processor 176.
- the circuit 168 includes a relay 178 that connects two switches 180, 182 and the processor 176.
- the line 166 may include an out-of-band control channel (e.g., an embedded operation channel or EOC) that enables the equipment 160 to monitor and control the modem 164 via EOC messaging.
- EOC embedded operation channel
- the EOC messaging may be used with the circuit 168 to enable the equipment 160 to disconnect the DSL line termination as follows.
- the service provider would send a command via the EOC of line 166 to the modem 164, instructing the modem 164 to disconnect itself for an amount of time H
- the time t may, for example, be predefined or may be included as a parameter in the command.
- the modem 164 Upon receiving the message, the modem 164 begins a timer and energizes the relay 178 to open the switches 180, 182. This results in a non-terminated line for a period of time defined by time t. During this time, the service provider may run diagnostics to characterize the line. When the timer expires, the processor 176 de- energizes the relay 178, which closes the switches 180, 182 and reestablishes the line.
- an exemplary Ethernet environment includes server provider equipment 184 and a digital device 188.
- the digital device 188 is a computer located on a subscriber's premises, but it is understood that the device 188 may be any kind of digital device applicable to the present disclosure.
- the equipment 184 is associated with an Ethernet unit 186 that enables the equipment 184 and computer 188 to communicate via a line 190.
- the computer 188 may include a circuit 192 as illustrated in Fig. 10.
- the circuit 192 is included on a network interface card (NIC) disposed in the computer 188.
- the NIC is associated with a media access control (MAC) number that identifies the NIC on a network. It is understood that the circuit may be associated with other components in the computer 188 or a device external to the computer 188.
- the circuit 192 includes a control unit 194 that is connected to a data path indicated by lines 196, 198.
- the control unit 194 is also connected to a control register 200 and a timer register 202 via a line 204.
- the registers 200, 202 feed into a gate 206 that contains a relay 208.
- the relay 208 is used to disconnect line 196 from its normal termination circuitry by register 200 for the duration programmed into register 202.
- the service provider may send a command via an inband signaling mechanism to the NIC and associated circuit 192.
- the command includes an instruction that the NIC take itself offline and an amount of time that the NIC should remain offline.
- the control unit 194 loads the control and timer registers 200, 202 with appropriate values to activate the relay and place the NIC offline.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Environmental & Geological Engineering (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Maintenance And Management Of Digital Transmission (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200480042923.8A CN1998185A (en) | 2004-03-18 | 2004-03-18 | Fault management in an Ethernet based communication system |
CA002559565A CA2559565A1 (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system |
PCT/IB2004/000817 WO2005094000A1 (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system |
AU2004317680A AU2004317680A1 (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system |
MXPA06010615A MXPA06010615A (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system. |
JP2007503425A JP2007529806A (en) | 2004-03-18 | 2004-03-18 | Fault management in a management system using Ethernet |
EP04721603A EP1733506B1 (en) | 2004-03-18 | 2004-03-18 | Fault management in an ethernet based communication system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2004/000817 WO2005094000A1 (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005094000A1 true WO2005094000A1 (en) | 2005-10-06 |
Family
ID=34957219
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2004/000817 WO2005094000A1 (en) | 2004-03-18 | 2004-03-18 | Fault management in a ethernet based communication system |
Country Status (7)
Country | Link |
---|---|
EP (1) | EP1733506B1 (en) |
JP (1) | JP2007529806A (en) |
CN (1) | CN1998185A (en) |
AU (1) | AU2004317680A1 (en) |
CA (1) | CA2559565A1 (en) |
MX (1) | MXPA06010615A (en) |
WO (1) | WO2005094000A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1992650B (en) * | 2005-12-30 | 2011-05-11 | 中兴通讯股份有限公司 | Method for detecting calling continuity of IP packet carrying network |
CN103401724A (en) * | 2013-07-08 | 2013-11-20 | 宁波高新区晓圆科技有限公司 | Data communication performance tester and implementation method thereof |
WO2014200721A1 (en) * | 2013-06-14 | 2014-12-18 | Honeywell International Inc. | Displaying fte cable status as ucn cable status |
US9325587B2 (en) | 2011-04-18 | 2016-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for quality of service monitoring of services in a communication network |
US11973640B1 (en) * | 2021-07-14 | 2024-04-30 | Juniper Networks, Inc. | Physical layer issue detection based on client-side behavior assessments |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102035716B (en) * | 2009-09-29 | 2013-04-24 | 中国移动通信集团公司 | Routing updating method and system and router |
CN102148721B (en) * | 2011-01-21 | 2014-02-19 | 华为技术有限公司 | Circuit detection method and device |
US9413893B2 (en) * | 2012-04-05 | 2016-08-09 | Assurant, Inc. | System, method, apparatus, and computer program product for providing mobile device support services |
CN110011869B (en) * | 2012-06-06 | 2022-07-19 | 瞻博网络公司 | Controller apparatus, method, and computer-readable storage medium |
US9191496B1 (en) | 2014-04-22 | 2015-11-17 | Adtran, Inc. | Digital subscriber line fault locating systems and methods |
CN105306272B (en) * | 2015-11-10 | 2019-01-25 | 中国建设银行股份有限公司 | Information system fault scenes formation gathering method and system |
CN108508874B (en) * | 2018-05-08 | 2019-12-31 | 网宿科技股份有限公司 | Method and device for monitoring equipment fault |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5923849A (en) * | 1996-05-07 | 1999-07-13 | International Network Services | Method of auditing communication traffic |
US6393489B1 (en) * | 1997-02-11 | 2002-05-21 | Vitesse Semiconductor Corporation | Media access control architectures and network management systems |
US6694455B1 (en) * | 2000-06-16 | 2004-02-17 | Ciena Corporation | Communications network and method performing distributed processing of fault and alarm objects |
-
2004
- 2004-03-18 JP JP2007503425A patent/JP2007529806A/en active Pending
- 2004-03-18 AU AU2004317680A patent/AU2004317680A1/en not_active Abandoned
- 2004-03-18 CN CN200480042923.8A patent/CN1998185A/en active Pending
- 2004-03-18 EP EP04721603A patent/EP1733506B1/en not_active Expired - Lifetime
- 2004-03-18 WO PCT/IB2004/000817 patent/WO2005094000A1/en active Application Filing
- 2004-03-18 MX MXPA06010615A patent/MXPA06010615A/en not_active Application Discontinuation
- 2004-03-18 CA CA002559565A patent/CA2559565A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5923849A (en) * | 1996-05-07 | 1999-07-13 | International Network Services | Method of auditing communication traffic |
US6393489B1 (en) * | 1997-02-11 | 2002-05-21 | Vitesse Semiconductor Corporation | Media access control architectures and network management systems |
US6694455B1 (en) * | 2000-06-16 | 2004-02-17 | Ciena Corporation | Communications network and method performing distributed processing of fault and alarm objects |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1992650B (en) * | 2005-12-30 | 2011-05-11 | 中兴通讯股份有限公司 | Method for detecting calling continuity of IP packet carrying network |
US9325587B2 (en) | 2011-04-18 | 2016-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for quality of service monitoring of services in a communication network |
WO2014200721A1 (en) * | 2013-06-14 | 2014-12-18 | Honeywell International Inc. | Displaying fte cable status as ucn cable status |
US9306802B2 (en) | 2013-06-14 | 2016-04-05 | Honeywell International Inc. | Displaying FTE cable status as UCN cable status |
CN103401724A (en) * | 2013-07-08 | 2013-11-20 | 宁波高新区晓圆科技有限公司 | Data communication performance tester and implementation method thereof |
US11973640B1 (en) * | 2021-07-14 | 2024-04-30 | Juniper Networks, Inc. | Physical layer issue detection based on client-side behavior assessments |
Also Published As
Publication number | Publication date |
---|---|
AU2004317680A1 (en) | 2005-10-06 |
MXPA06010615A (en) | 2006-12-19 |
EP1733506B1 (en) | 2012-08-15 |
EP1733506A1 (en) | 2006-12-20 |
CN1998185A (en) | 2007-07-11 |
JP2007529806A (en) | 2007-10-25 |
CA2559565A1 (en) | 2005-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20070022331A1 (en) | Single-ended ethernet management system and method | |
US7502328B2 (en) | Method of monitoring link performance and diagnosing active link state in Ethernet passive optical network | |
US8472327B2 (en) | Apparatus and method for testing and fault isolation in a communication network | |
US6938189B2 (en) | High performance digital loop diagnostic technology | |
US9860111B2 (en) | Method and apparatus for diagnosing and configuring a broadband connection via an alternate communication path | |
EP2947793B1 (en) | Link detection method and device for passive optical network | |
EP1733506B1 (en) | Fault management in an ethernet based communication system | |
EP1585299B1 (en) | Providing applets to remote devices in a communications network | |
US9124683B2 (en) | Diagnostic engine | |
CA2504970A1 (en) | Method and system for surveilling a telecommunications network link | |
KR20060126619A (en) | Fault management in a ethernet based communication system | |
US7958386B2 (en) | Method and apparatus for providing a reliable fault management for a network | |
JP2005268889A (en) | Transmission path switching system and operating method of the transmission path switching system | |
JP3794348B2 (en) | Station side transmission apparatus and communication system monitoring method | |
KR100735394B1 (en) | Hindrance diagnose method in asymmetric digital subscriber line system | |
EP3035661B1 (en) | A method for verifying a port synchronisation | |
JP2004260383A (en) | Communication line fault generating test system | |
CN115865742A (en) | Method and system for detecting unidirectional link fault of white box switch | |
CA2613060A1 (en) | Method and apparatus for analyzing a network or a network element fault | |
KR20030053975A (en) | Method and apparatus for measuring the quality of internet service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DPEN | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2559565 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004317680 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007503425 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/2006/010615 Country of ref document: MX |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004721603 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067020165 Country of ref document: KR |
|
ENP | Entry into the national phase |
Ref document number: 2004317680 Country of ref document: AU Date of ref document: 20040318 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200480042923.8 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067020165 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2004721603 Country of ref document: EP |