METHOD AND DEVICE FOR DETECTING A CROSSTALK ISSUE ON A DIGITAL SUBSCRIBER LINE

Abstract

Embodiments relate to a method for detecting a crosstalk issue on a Digital Subscriber Line (4) of a vectoring group (3), executed by a monitoring device (7), comprising: receiving (S1) operational data representative of the Quiet Line Noise and the Active Line Noise of said Digital Subscriber Line (4), and detecting a crosstalk issue in function of said Quiet Line Noise and/or the Active Line Noise.

Claims

1. Method for detecting a crosstalk issue on a Digital Subscriber Line of a vectoring group, executed by a monitoring device, comprising: receiving operational data representative of the Quiet Line Noise and the Active Line Noise of said Digital Subscriber Line, and detecting a crosstalk issue based on of said Quiet Line Noise and/or the Active Line Noise.

2. Method according to claim 1, wherein said Quiet Line Noise and Active Line Noise are as specified in Amendment 1 to Recommendation ITU-T G.9701.

3. Method according to claim 1, wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative of an average difference, for respective tones, between the Quiet Line Noise and the Active Line Noise, in response to determining that the first metric is below a first threshold for a period of time, determining that said Digital Subscriber Line is affected by cross-talk.

4. Method according to claim 1, wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative the average Quiet Line Noise, for respective tones, in response to determining that the first metric is above a first threshold for a period of time, determining that said Digital Subscriber Line is affected by alien crosstalk.

5. Method according to claim 1, wherein said operational data are representative of the Quiet Line Noise of respective Digital Subscriber Lines of a vectoring group, and wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative an average Quiet Line Noise of the vectoring group, in response to determining that the first metric is above a first threshold for a period of time, determining that said vectoring group is affected by alien crosstalk.

6. A non-transitory computer-readable medium storing instructions which when executed by a computer, cause the computer to perform the method of claim 1.

7. Monitoring device for detecting a crosstalk issue on a Digital Subscriber Line of a vectoring group, comprising: means for receiving operational data representative of the Quiet Line Noise and the Active Line Noise of said Digital Subscriber Line, and means for detecting a crosstalk issue based on said Quiet Line Noise and/or the Active Line Noise.

8. Monitoring device to claim 7, wherein said Quiet Line Noise and Active Line Noise are as specified in Amendment 1 to Recommendation ITU-T G.9701.

9. Monitoring device according to claim 7, wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative of an average difference, for respective tones, between the Quiet Line Noise and the Active Line Noise, in response to determining that the first metric is below a first threshold for a period of time, determining that said Digital Subscriber Line is affected by cross-talk.

10. Monitoring device according to claim 7, wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative the average Quiet Line Noise, for respective tones, in response to determining that the first metric is above a first threshold for a period of time, determining that said Digital Subscriber Line is affected by alien crosstalk.

11. Monitoring device according to claim 7, wherein said operational data are representative of the Quiet Line Noise of respective Digital Subscriber Lines of a vectoring group, and wherein detecting a crosstalk issue comprises: determining successive values of a first metric representative an average Quiet Line Noise of the vectoring group, in response to determining that the first metric is above a first threshold for a period of time, determining that said vectoring group is affected by alien crosstalk.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and other objects and features of the invention will become more apparent and the invention itself will be best understood by referring to the following description of embodiments taken in conjunction with the accompanying drawings wherein:

[0027] FIG. 1 is a bloc diagram of a telecommunication network,

[0028] FIG. 2 is a flowchart of a method for detecting a crosstalk issue on a Digital Subscriber Line, in the network of FIG. 1, and

[0029] FIG. 3 is structural view of a monitoring device for detecting a crosstalk issue on a Digital Subscriber Line.

DESCRIPTION OF EMBODIMENTS

[0030] FIG. 1 is a bloc diagram of a telecommunication network 1. The telecommunication network 1 comprises an access node 2 connected to user nodes 5 by respective Digital Subscriber Lines 4, and a monitoring device 7. The Digital Subscriber Lines 4 are grouped in respective binders 6. Not all user nodes 5 are showed for simplicity.

[0031] The access node 2 and the user nodes 5 use a Digital Subscriber Line (DSL) technology with a crosstalk cancellation mechanism, for example G.Fast, for communication over the Digital Subscriber Lines 4. For example, the access node 2 is or comprises a DSLAM and a user node 5 is a customer premises equipment (CPE) including a DSL modem.

[0032] Vectoring comprises jointly-processing a plurality of lines together in a vectoring group 3. In the example of FIG. 1, the access node 2 comprises three vectoring groups 3, denoted VG1, VG2 and VG3. The vectoring group VG3 illustrates an ideal situation, wherein the Digital Subscriber Lines 4 of the vectoring group VG3 match the Digital Subscriber Lines 4 of a binder 6. In contrast, the vectoring groups VG1 and VG2 illustrate a cross-wired line, shown in dashed line. The cross-wired line belongs to the vectoring group VG2 but is located in the same binder 6 as the Digital Subscriber Lines 4 of the vectoring group VG1. Accordingly, the cross-talk from the cross-wired line into the other Digital Subscriber Lines 4 of the vectoring group VG1 is not correctly cancelled. Likewise, the crosstalk from the other Digital Subscriber Lines 4 of the vectoring group VG1 into the cross-wired line is not correctly cancelled. Moreover, processing the signals of the cross-wired line in vectoring group VG2 is unnecessary.

[0033] The monitoring device 7 may obtain operational data relating to the functioning of the access node 2, the vectoring groups 3, the Digital Subscriber Lines 4 and/or the user nodes 5. For example, the access node 2 and/or the user nodes 5 send operational data to the monitoring device 7 on a regular basis or in response to a request. In particular, the operational data specify the Quiet Line Noise (QNL) and the Active Line Noise (ANL) for respective Digital Subscriber Lines 4. Based on the obtained Quiet Line Noise and the Active Line Noise, the monitoring device 7 detects a crosstalk issue, for example a cross-wired line or alien crosstalk, on a Digital Subscriber Line 4. The monitoring device 7 may be a network analyzer which, in addition to the detection of crosstalk issues, performs other monitoring, troubleshooting and management tasks related to the access node 2, the vectoring groups 3, the Digital Subscriber Lines 4 and/or the user nodes 5.

[0034] For the G.Fast technology, the QLN (Quiet Line Noise) and ALN (Active Line Noise) are defined in Amendment 1 to Recommendation ITU-T G.9701.

[0035] The QLN represents the noise present on the loop expressed in dBm/Hz when all lines of a vectored group are either transmitting QUIET symbols or are turned off. The QLN shall be measured by the VCE (Vector Controller Entity) during showtime, and shall be updated during showtime. The reported QLN values shall be represented by sub-carrier groups.

[0036] The ALN represents the total noise which includes the extrinsic noise present on the loop, all FTU receiver internal noises and residual crosstalk. It is defined for downstream only and measured and by FTU-R during showtime and during L0 state only (when the line is in full data rate, and not in low power state L2.1, in standby state L2.2 or in L3 state when the line is silent). The line state of other lines served by the same DPU may stay in whatever line state they are in.

[0037] The analysis of the difference between QLN and ALN of the different lines in the same vectoring groups and the correlation of this difference with the current states (silent or showtime) of these lines can be used to detect the presence of cross-wired lines and/or alien crosstalk.

[0038] For example, the QLN and ALN should be very close if the line is cross-wired, because even if all lines of the same vectoring group are silent, the total self-crosstalk comes from the lines sharing the same physical binder which are not connected to the same vectoring group. Then, the QLN of this cross-wired line is abnormally high compared with QLN of other lines. It can happen that the other disturbers are down, and in this case QLN and ALN are also close to one another. In that case, and in order to distinguish between the cross-wired line and the case where all other disturbers are down, the monitoring device 7 monitors the evolution in time of the difference between QLN and ALN. In cross-wired case, this difference is constant in the time, and time limited for the other case.

[0039] Also, if the line is impacted by an alien crosstalk, the corresponding QLN should be higher than the lines which are not impacted.

[0040] Finally, if the vectoring group is impacted by an alien crosstalk, the corresponding average of QLNs should be higher than the vectoring groups which are not impacted.

[0041] FIG. 2 is a flowchart of a method for detecting a crosstalk issue on a Digital Subscriber Line 4, executed by the monitoring device 7.

[0042] The monitoring device 7 obtains operational data representative of the Quiet Line Noise and the Active Line Noise of respective Digital Subscriber Lines 4 (Step S1).

[0043] For respective Digital Subscribers Lines 4, the monitoring device 7 determines a metric d.sup.t representative of differences between QLN and ALN (Step S2). For example, the monitoring device 7 determines an average of differences between QLN and ALN:

[00001]$\begin{array}{cc}{d}^t=\frac{\underset{n=1}{\overset{N}{.Math.}}.Math.\left({\mathrm{ALN}}_n^t-{\mathrm{QLN}}_n^t\right)}{N}& \left(\mathrm{Eq}..Math.1\right)\end{array}$

wherein ALN.sub.n.sup.t is the measured ALN at time tin tone n, QLN.sub.n.sup.t is the measured QLN at time t in tone n and N is the total number of tones. The metric d.sup.t is determined for successive time t, for example based on period P comprised between every day and every fifteen minutes. In order to reduce the complexity of storing data in database, in some embodiments, the monitoring device 7 stores successive values of this metric d.sup.t without storing successive values of QLN and ALN.

[0044] If the Digital Subscriber Line 4 is cross-wired (wired to the wrong vectoring group), the corresponding metric d.sup.t should be small and constant in time compared with other lines because even if all lines of the same vectoring group are silent, the total self-crosstalk comes from the lines sharing the same physical binder which are not connected to the same vectoring group. So, we can define a threshold th.sub.d that when the metric d.sup.t is below this threshold during a predefined time (for example a few days), a cross-wired line can be suspected.

[0045] Thus, the monitoring device 7 compares successive values of the metric d.sup.t with a predetermined threshold th.sub.d (Step S3) and, in response to determining that the metric d.sup.t is below the threshold th.sub.d during a predefined time period, the monitoring device 7 determines that the Digital Subscriber Line 4 is cross-wired (Step S4). In that case, the monitoring device 7 may display information and/or send a message specifying that the Digital Subscriber Line 4 has been determined to be cross-wired. This may trigger various corrective actions, such as rewiring by a technician.

[0046] If a Digital Subscriber Line 4 is impacted by an alien crosstalk which cannot be removed by vectoring, the level of corresponding QLN should be higher than the other lines in the same vectoring group. The monitoring device 7 determines a metric q.sup.t which represents the average of QLN of a Digital Subscriber Line 4 (Step S5):

[00002]$\begin{array}{cc}{q}^t=\frac{\underset{n=1}{\overset{N}{.Math.}}.Math.\left({\mathrm{QLN}}_n^t\right)}{N}& \left(\mathrm{Eq}..Math.2\right)\end{array}$

wherein QLN.sub.n.sup.t is the measured QLN at time t in tone n and N is the total number of tones. Successive values of q.sup.t are determined and stored, for example based on a period P comprised between 24 hours and 15 minutes. A threshold th.sub.q can be predefined such that when the metric q.sup.t is above this threshold th.sub.q during a predefined time (for example, a few days), an alien crosstalk can be suspected on a given line.

[0047] Thus, the monitoring device 7 compares successive values of the metric q.sup.t with a predetermined threshold th.sub.q (Step S6) and, in response to determining that the metric q.sup.t is above this threshold th.sub.q during a predefined time period, the monitoring device 7 determines that the Digital Subscriber Line 4 is affected by alien crosstalk (Step S7). In that case, the monitoring device 7 may display information and/or send a message specifying that the Digital Subscriber Line 4 has been determined to be affected by alien crosstalk. This may trigger various corrective actions, such as a troubleshooting by a technician.

[0048] All the Digital Subscriber Lines 4 of a vectoring group can be impacted by alien crosstalk. In this case the average of QLN of all lines of the vectoring group should be high compared with others vectoring groups. The monitoring device 7 determines a metric Q.sup.t which represents the average of QLN of a vectoring group (Step S8):

[00003]$\begin{array}{cc}{Q}^t=\frac{\underset{i=1}{\overset{P}{.Math.}}.Math.\left(q_i^t\right)}{P}& \left(\mathrm{Eq}..Math.3\right)\end{array}$

wherein q.sub.i.sup.t is the average of QLN for line i at time t and P is the total number of lines in the vectoring group. Successive values of Q.sup.t are determined and stored, for example based on a period P comprised between 24 hours and 15 minutes. A threshold th.sub.Q can be predefined such that when the metric Q.sup.t is above this threshold during a predefined time (for examples, a few days), the monitoring device 7 determines that the vectoring group is affected by alien crosstalk.

[0049] Thus, the monitoring device 7 compares successive values of the metric Q.sup.t with a predetermined threshold th.sub.Q (Step S9) and, in response to determining that the metric Q.sup.t is above this threshold th.sub.Q during a predefined time period, the monitoring device 7 determines that the vectoring group is affected by alien crosstalk (Step S10). In that case, the monitoring device 7 may display information and/or send a message specifying that the vectoring group has been determined to be affected by alien crosstalk. This may trigger various corrective actions, such as a troubleshooting by a technician.

[0050] Although steps S1 to S10 are described as successive steps, they may be executed in another order, in parallel and/or iterated.

[0051] In the network 1, the monitoring device 7 may detect a cross-wired line, a line affected by alien crosstalk and/or a vectoring group affected by alien crosstalk, in function of the QLN and ALN of Digital Subscriber Lines 4. Since the QNL and ANL are specified by an ITU Recommendation, interoperability is improved and the use of proprietary solutions may be avoided or limited. Moreover, since the detection relies on successive values for metrics d.sup.t, q.sup.t and Q.sup.t, the amount of data to be stored and the complexity are reduced in comparison with the use of crosstalk matrix.

[0052] FIG. 3 is a structural view of the monitoring device 7, which comprises a processor 8 and a memory 9. The memory 9 stores a computer program P which, when executed by the processor 7, causes the monitoring device 7 to execute the method described above with reference to FIG. 2.

[0053] It is to be remarked that the functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared, for example in a cloud computing architecture. Moreover, explicit use of the term processor should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage. Other hardware, conventional and/or custom, may also be included. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.

[0054] It should be further appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the invention. Similarly, it will be appreciated that any flow charts represents various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0055] Embodiments of the method can be performed by means of dedicated hardware and/of software or any combination of both.

[0056] While the principles of the invention have been described above in connection with specific embodiments, it is to be clearly understood that this description is made only by way of example and not as a limitation on the scope of the invention, as defined in the appended claims.