AUTOMATED NODE LEVEL FIBRE AUDIT

Abstract

A method of automated testing and evaluation of a node of a communications network, the method comprising: a management computer interacting with the node to discover fibre trails within the node that can be safely tested; and the management computer interacting with the node to test at least continuity of each identified fibre trail that can be safely tested.

Claims

1-11. (canceled)

12. A method for automated node-level fiber testing and evaluation, the method comprising: determining, through communication to a node, a fibre trail associated with the node, wherein the node comprises a reconfigurable optical add/drop multiplexer with a plurality of modules associated with the fibre trail; and causing a test of the fibre trail using one or more light sources in the plurality of modules to determine one of continuity and loss of intra- and inter-node fiber connections associated with the fibre trail.

13. The method of claim 12, wherein the fibre trail is safely tested if it is one of i) carrying less than all active wavelengths and ii) dark being connected but not carrying active wavelengths.

14. The method of claim 13, wherein: when the fibre trail is i) carrying less than all active wavelengths, the causing comprises querying inactive components in the plurality of modules associated with inactive wavelengths for the test, and when the fibre trail is ii) dark, the causing comprises using inactive components in the plurality of modules to provide the one or more light sources.

15. The method of claim 12, wherein the one or more light sources comprise sources of Amplified Spontaneous Emission (ASE) in the plurality of modules.

16. The method of claim 12, wherein the one or more light sources comprise amplifiers in the plurality of modules which do not have active wavelengths therethrough and the causing comprises the amplifiers generating Amplified Spontaneous Emission (ASE) at respective outputs.

17. The method of claim 16, wherein the one or more light sources are each turned on separately to map the fibre trail.

18. The method of claim 12, wherein the determining comprises communicating to a database to uniquely identify one of modules and status thereof.

19. The method of claim 12, wherein the loss is determined by comparing detected optical power with expected optical power.

20. The method of claim 12, wherein, during the test, a wavelength selective switch is configured to switch light from the one or more light sources to map the fibre trail.

21. A reconfigurable optical add/drop multiplexer (ROADM) node configured for automated node-level fiber testing and evaluation, the ROADM node comprising: a plurality of modules; and a computer configured to determine a fibre trail associated with the plurality of modules, and cause a test of the fibre trail using one or more light sources in the plurality of modules to determine one of continuity and loss of intra- and inter-node fiber connections associated with the fibre trail.

22. The ROADM node of claim 21, wherein the fibre trail is safely tested if it is one of i) carrying less than all active wavelengths and ii) dark being connected but not carrying active wavelengths.

23. The ROADM node of claim 22, wherein: when the fibre trail is i) carrying less than all active wavelengths, the causing comprises querying inactive components in the plurality of modules associated with inactive wavelengths for the test, and when the fibre trail is ii) dark, the causing comprises using active components in the plurality of modules to provide the one or more light sources.

24. The ROADM node of claim 21, wherein the one or more light sources comprise sources of Amplified Spontaneous Emission (ASE) in the plurality of modules.

25. The ROADM node of claim 21, wherein the one or more light sources comprise amplifiers in the plurality of modules which do not have active wavelengths therethrough and the causing comprises the amplifiers generating Amplified Spontaneous Emission (ASE) at respective outputs.

26. The ROADM node of claim 25, wherein the one or more light sources are each turned on separately to map the fibre trail.

27. The ROADM node of claim 21, wherein the fibre trail is determined through communication to a database to uniquely identify one of modules and status thereof

28. The ROADM node of claim 21, wherein the loss is determined by comparing detected optical power with expected optical power.

29. The ROADM node of claim 21, wherein, during the test, a wavelength selective switch is configured to switch light from the one or more light sources to map the fibre trail.

30. A management computer configured for automated node-level fiber testing and evaluation, the management computer configured to: determine, through communication to a node, a fibre trail associated with the node, wherein the node comprises a reconfigurable optical add/drop multiplexer with a plurality of modules associated with the fibre trail; and cause a test of the fibre trail using one or more light sources in the plurality of modules to determine one of continuity and loss of intra- and inter-node fiber connections associated with the fibre trail.

31. The management computer of claim 30, wherein the fibre trail is safely tested if it is one of i) carrying less than all active wavelengths and ii) dark being connected but not carrying active wavelengths.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Further features and advantages of the present invention will become apparent from the following detailed description, taken in combination with the appended drawings, in which:

[0016] FIG. 1 is a block diagram schematically illustrating a reconfigurable optical add/drop multiplexer (ROADM) known in the art;

[0017] FIG. 2 is a block diagram schematically illustrating a representative network node incorporating the ROADM of FIG. 1;

[0018] FIG. 3 is a flow chart illustrating a representative method in accordance with an aspect of the present invention;

[0019] FIG. 4 is a flow chart illustrating a representative discovery method in accordance with an aspect of the present invention;

[0020] FIG. 5 is a flow chart illustrating a representative testing method in accordance with an aspect of the present invention;

[0021] FIG. 6 is a flow chart illustrating a representative testing method in accordance with an aspect of the present invention; and

[0022] FIG. 7 is a flow chart illustrating a representative testing method in accordance with an aspect of the present invention.

[0023] It will be noted that throughout the appended drawings, like features are identified by like reference numerals.

DETAILED DESCRIPTION

[0024] The present application provides techniques for automated node-level fiber testing and evaluation. The methods described below, may be implemented using a computer executing suitable software (processor executable logic instructions) stored on a memory of the computer. For example, during system layout and test (SLAT), a service technician may connect a management computer to a network node, and trigger execution of software that interacts with the network node to perform the desired testing and evaluation processes. As another example, the node's own management computer may execute software implementing the automated testing and evaluation methods to enable a self-test of the node's internal connectivity and performance. In a still further example, a central management computer operated by a network service provider may execute software implementing the automated testing and evaluation methods to enable remote testing of the node's internal connectivity and performance. Other arrangements are also possible.

[0025] Referring to FIG. 3, in a representative embodiment, network node equipment is examined (at step S2) to discover fiber trails (paths) that can be safely tested. Fibre trails carrying active wavelengths may be safely tested, provided that the active wavelengths themselves are not subject to interference in the course of such testing. So-called dark fibre trails (i.e. fibre trails that are connected but not carrying any active wavelengths) can only be tested by adding light to them. Dark fibre trails may be considered to be safe for testing only if adding a light source to the fibre trail will not impact other in-service wavelengths. That is, the injected light source used for testing must be a distinct wavelength, or if ASE light is used, it must be prevented from multiplexing with in-service wavelengths. For each safe fiber trail, connections through the ROADM and the DIA can be tested (at step S4) for continuity and losses. The test results for each fiber trail can be compiled into a report (at step S6), which may be used (for example by a service technician) to correct any faults found in the node.

[0026] FIG. 4 illustrates a representative process for discovering fiber trails that can be safely tested. At a first step (S6), the network node is queried to obtain a listing of equipment (such as, for example, shelves and cards) installed within the node. This information is commonly stored in a database associated with the network node, and may include information uniquely identifying each piece of equipment, as well as one or more respective codes (such as part and model numbers) associated with each piece of equipment. This information can then be used (at steps S8 and S10) to identify port layout and addresses, photodiode (receiver and/or Optical Performance Monitoring (OPM)) locations and addresses, and sources of Amplified Spontaneous Emission (ASE), (such as for example, optical amplifiers 18, 32, FIG. 1) in each piece of equipment. In some embodiments, this information can be obtained by querying the network node. In other embodiments (cases), this information can be obtained by querying one or more databases which may be accessed through a network such as the internet.

[0027] The network node can also be queried to identify (at step S12) the port trail of any active wavelengths. For example, the status of the DIA WSS 38 (FIG. 2) can be retrieved from the network node and analysed to identify each wavelength that is being switched through the WSS 38. These wavelengths may be considered as active wavelengths, and cannot be disrupted during testing of the network node. The status of the WSS 38 and the known port layout of each piece of equipment can then be used to identify the respective sequence of ports (ie the port trail) traversed by each active wavelength. Any photodiodes (eg receivers 24 or OPM circuits) receiving light of an active wavelength can thus be determined. Conversely, any photodiodes that are not receiving an active wavelength, can also be identified (at step S14). These dark photodiodes may be used during subsequent testing of the network node. It should be noted that photodiodes that terminate light from active wavelengths can be used non-intrusively to calculate fiber loss, by querying the involved photodiodes to obtain the received optical power levels. This information can be readily used to confirm at least the connectivity of the lit fibre trails. In addition, fibre loss can be calculated by comparing the optical power of light detected at a photodiode to an expected power level, which can be determined by retrieving information on the current composition of traffic on the relevant fiber (for example, loss=number of active wavelengths*expected power of each wavelength-power measured at photodiode). The discussion below will focus on the testing of dark fibre trails, since this is generally more complicated.

[0028] The known port layout and addresses, photodiode locations and addresses, and ASE sources can then be used to map the current shelf layout (at step S16), and identify ASE sources upstream of each dark photodiode. Of these ASE sources, any sources that are connected to the known port trail of an active wavelengths cannot be safely used for testing, because such use may disrupt signaling in the active wavelengths. Once these unsafe ASE sources have been identified, any other ASE sources may be identified (at step S18) as being available for use in testing the node.

[0029] The process described above with reference to FIG. 4, yields a map of equipment and fiber trails in the node that can be safely tested without disrupting active wavelengths. Representative testing procedures are described below with reference to FIGS. 5 and 6.

[0030] FIG. 5 illustrates a representative method for automated testing of an OTS 36 within a network node. As may be appreciated, this process may be suitable for testing OTS cards that have been installed in a shelf, but which are currently connected to dark fiber spans 4. At a first step (S20), the OTS amplifiers 40 and 42 (FIG. 2) are set to power mode, so as to generate ASE at their respective outputs. The ASE light emitted from each amplifier can then be used to test (at S22) for faults in the OPM fiber connections. For example, by supplying power to each of the OTS amplifiers 40 and 42 separately, the OPM 44 can be checked to determine that light is being received from each amplifier through the correct port. This allows crossed fiber connections to be detected. In addition, the optical power levels detected by the OPM 44 can be compared to an allowable tolerance value to detect excessive losses in the OPM fiber connections.

[0031] If a crossed fiber connection or excessive fiber losses are detected, then information detailing the problem(s) are added to a test report (at step S26). This information may, for example, include information identifying the OTS card 36 in which the faulty OPM connections are found, as well as information identifying the nature of the fault (such as improper connection or excessive losses, for example).

[0032] Once the OTS OPM fiber connections have been checked, the OTS WSS 46 can be queried (at S28) to obtain the detected optical power levels at the Common-In, and Switch-Out ports. If the WSS returns an alarm condition, then corresponding information is added to the test report (at S32).

[0033] Once the OTS testing is complete, the OTS amplifiers 40 and 42 can be set into a Gain Mode (step S34), so as to minimize ASE at their outputs.

[0034] FIG. 6 illustrates a representative method for automated testing of a DIA 34 within a network node. As may be appreciated, this process may be suitable for testing DIA cards that have been installed in the node, but which are not currently ADDing or DROPing active wavelength channels. At a first step (S36), the optical amplifiers 18 and 32 (FIG. 1) are set to power control mode, so as to generate ASE at their respective outputs. The ASE light emitted from each amplifier can then be used to test (at S38) for faults in the OPM fiber connections. For example, by supplying power to each of the amplifiers 18 and 32 separately, the DIA OPM 46 can be checked to determine that light is being received from each amplifier through the correct port. This allows crossed fiber connections to be detected. In addition, the optical power levels detected by the DIA OPM 46 can be compared to an allowable tolerance value to detect excessive losses in the OPM fiber connections.

[0035] If a crossed fiber connection or excessive fiber losses are detected, then information detailing the problem(s) is added to the test report (at step S42). This information may, for example, include information identifying the DIA card 34 in which the faulty OPM connections are found, as well as information identifying the nature of the fault (such as improper connection or excessive losses, for example).

[0036] Once the DIA OPM fiber connections have been checked, the DROP path of the second-stage MUX/DeMUX module 10 can be opened (at step S44) to enable testing of DIA and ROADM DROP path fiber trails (at step S46) for connectivity and unexpected (or excessive) loss conditions.

[0037] For example, referring to FIG. 1, the ROADM WSS 20 can be queried to obtain the detected optical power levels at the Common-In, and Switch-Out ports. If the WSS 20 does not return any alarm conditions, proper connectivity in the DROP path between the amplifier module 8 and the second-stage MUX/DeMUX module 10 is confirmed. In this case, the WSS 20 can be controlled to switch ASE light to a selected first-stage MUX/DeMUX module 12. Detection of this light by receivers 24 connected to the selected first-stage MUX/DeMUX module 12 confirms proper connectivity in the DROP path. Conversely, failure of the receivers 24 connected to the selected first-stage MUX/DeMUX module 12 to detect ASE light from the DROP path amplifier 18 indicates a crossed or missing fiber connection in the DROP path as detected by the receivers 24 connected to that module. In addition, some of the ASE light from the DROP path amplifier 18 will also be tapped (at 48, FIG. 1) and routed to a 2-port OPM 50 in the second-stage MUX/DeMUX module 10. By this means, the OPM fiber connections between the first and second stage MUX/DeMUX modules 10 and 12 can be tested for continuity. Finally, the receivers 24 and the 2-port OPM 50 can be queried to obtain information indicative of the optical power level of the ASE light received from the received light DROP path amplifier 18. These power levels can then be compared with predetermined tolerance levels to detect an unexpected or excessive loss condition. Any errors or alarm conditions detected during the DROP path continuity and loss checks described above can then be added to the test report (at S50).

[0038] Once the DROP path fiber trails have been tested, the DROP path of the second-stage MUX/DeMUX module 10 can be closed (at step S52) and ADD path connectivity between the DIA and each OTS tested (at step S54), using ASE light emitted by the ADD path amplifier 32. For example, the DIA WSS 38 can be queried to obtain the detected optical power levels at the Common-In, and Switch-Out ports. Similarly, the WSS OPM 46 can be queried to obtain the detected optical power level of light from the amplifier 32. If the DIA WSS 38 and OPM 46 do not return any alarm conditions, proper connectivity in the ADD path between the amplifier module 8 and the DIA WSS 38 is confirmed. In this case, the WSS 38 can be controlled to switch ASE light to a selected OTS 36, and the corresponding WSS queried to obtain the optical power level of the Switch-In port to which the DIA should be connected. If no alarms conditions are detected from the OTS WSS, then proper connectivity in the ADD-path between the DIA and the selected OTS is confirmed. On the other hand, if any alarm conditions are returned from either of the DIA or OTS WSSs, then information regarding these alarms is added (at step 58) to the test report.

[0039] Upon completion of the DIA tests above, the DIA amplifiers 18 and 32 can be set into a Gain Control Mode (step S60), so as to minimize ASE at their outputs.

[0040] FIG. 7 illustrates a representative method for automated testing of the ROADM/DIA ADD-path within a network node. As may be appreciated, this process may be suitable for testing DIA cards that have been installed in the node, but which are not currently ADDing active wavelength channels. A first stage MUX/DeMUX module 12 is selected (step (S62) for testing. If the attached second-stage MUX/DeMUX module 10 contains a LoopBack Path (step S64), the module 10 can be controlled to perform a test (step S66) of that path. Then, the ADD-Path amplifier 52 in a selected first stage MUX/DeMUX module 12 can be set to power control mode (step S68) so as to generate ASE light at its output. This ASE light can then be used to check (step S70) ADD-path continuity through the ROADM 2 and the DIA 34. For example, detection of the ASE light in the 2-port OPM 50 confirms connectivity between the selected first stage MUX/DeMUX module 12 and the second stage MUX/DeMUX module 10. Similarly, detection of the ASE light at the Common-In port of the DIA WSS 38 confirms ADD-path continuity through the ROADM 2 to the DIA 34. Similarly, the optical power levels detected at the 2-port OPM 50, DIA OPM 46 and the Common-In port of the DIA WSS 38 can be used as described above to identify unexpected losses in the ADD-path. If any alarm conditions are found (step S70) during the ADD-path continuity test, information regarding these alarms is inserted (at step S72) into the test report. Upon completion of the ADD-path test for the selected first stage MUX/DeMUX module 12, the module's ADD-path amplifier 52 is placed into the Gain control mode, to minimize ASE at its output.

[0041] The process described above at steps S64-S74 is repeated for each first stage MUX/DeMUX module 12 in the network node. Once all of the first stage MUX/DeMUX modules have been tested (step S76) the test report may be output (at step S78) to a printer, display or storage device, for example. Preferably, this report includes information detailing any errors or alarm states detected during the test operations described above with reference to FIGS. 3-7.

[0042] As will be appreciated, the automated node-level fiber testing and evaluation methods described above, can be run at various times, as desired. For example, during System Layout and Testing (SLAT), the automated node-level fiber testing and evaluation process may be run to validate any new connections being installed. Subsequently, the process may be run (for example on Demand, or in accordance with a predetermined schedule) to verify proper connectivity and optical performance within the node.

[0043] The embodiments of the invention described above are intended to be illustrative only. The scope of the invention is therefore intended to be limited solely by the scope of the appended claims.