Abstract:
One exemplary aspect is to detect the presence of one or more types of faults affecting DSL communications. Upon their detection, a message can be generated that recommends corrective action. Furthermore, another exemplary aspect is to estimate the rate impact of the detected fault in some cases. One exemplary aspect of certain embodiments is to detect the presence of one or more faults that affect DSL communications, and upon their detection, generating, for example, a message that recommends corrective action. In this context, a fault can be one or more metallic faults, malfunctioning modems, or something else that affects the measured attenuation but is not normally attributable to normal DSL transmission lines.

Description:
RELATED APPLICATION DATA 
       [0001]    This application claims the benefit of and priority under 35 U.S.C. §119(e) to U.S. Patent Application No. 61/265,129, filed Nov. 30, 2009, entitled “Methods and Systems for Detecting Metallic Faults Affecting Communications Links,” which is incorporated herein by reference its entirety. 
     
    
     FIELD OF THE INVENTION 
       [0002]    An exemplary aspect of this invention relates to communications systems. More specifically, exemplary methods, systems, means, protocols and instruction bearing computer-readable storage media, are directed toward communications system diagnostics and analysis. 
       SUMMARY 
       [0003]    Some of the most problematic aspects of Digital Subscriber Line (DSL) communications (generally referred to a xDSL) are faults including but not limited to the following:
       Metallic faults such as resistances, capacitances and inductances in excess of the physical properties inherently present in the wires themselves. These electrical properties may be present in any combination. They may appear in series along either of the wires of the twisted pair, in series along both of the wires of the twisted pair, in parallel between the wires of the twisted pair, in parallel between either wire of the twisted pair and ground, in parallel between both wires of the twisted pair and ground, in parallel between either wire of the twisted pair and some other electrical conductor, in parallel between both wires of the twisted pair and some other conductor, or any combinations of these. They may be concentrated at one location or distributed along the length of the wires. The physical cause of metallic faults include but are not limited to bad electrical contacts, water ingress into the insulator, inappropriate electrical connections of conductors to each other or ground, or some other condition that affects the normal behavior of the transmission line between the transceivers.   A malfunctioning modem on either or both ends of the line.       
 
         [0006]    One exemplary aspect is to detect the presence of one of the above types of faults affecting DSL communications. This can be done either with or without necessarily being able to discriminate between them. Upon their detection, a message can be generated that recommends corrective action. 
         [0007]    Another exemplary aspect is to estimate a rate impact of the detected fault. 
         [0008]    One exemplary purpose of certain aspects is to detect the presence of one or more faults that affect DSL communications, and upon their detection, generate, for example, a message that recommends corrective action. In this context, a fault is one or more metallic faults, malfunctioning modems, or something else that affects the measured attenuation but is not normally attributable to normal DSL transmission lines. 
         [0009]    Certain embodiments pertain to multi-carrier communications links such as discrete multi-tone (DMT). One of the exemplary methods may use standard-compliant links (i.e., as specified in published DSL standards such as ITU-T G.992.3/5 and G.993.2, (http://www.itu.int/rec/T-REC-G.992.3/en and http://www.itu.int/rec/T-REC-G.993.2/en, which are incorporated herein by reference in their entirety), but it is not restricted to standard compliant links. Generally, each link is full duplex, comprising both an upstream (US) direction and a downstream (DS) direction. To simplify the following description, it should be understood that all analysis can be performed for upstream signals or subchannels, downstream signals or subchannels, or both. Typically, a Power Spectral Density (PSD) is transmitted in both directions during a communications link to facilitate the analysis. The individual carriers used for the link will be referred to as “subcarriers” or “subchannels.” Generally, each link is full duplex, comprising both an upstream direction and a downstream direction. A Power Spectral Density is transmitted in both directions. For standard compliant DSL as well as some nonstandard xDSL links, these PSDs are configurable, usually by adjusting subcarrier masks, PSD masks, nominal PSD levels, etc. 
         [0010]    For standard compliant DSL links (as well as some nonstandard DSL links), it is possible to observe the attenuation for each of the upstream and/or downstream subchannels used for the link. For recent ITU DSL standards (ADSL2 and beyond), this can be accomplished if the link is performed in the Loop Diagnostics Mode as defined by ITU standards for DSL, or alternatively the attenuation can be read from the MIB by using a messaging channel during Showtime, which is a term used to denote the steady-state data transmission mode for DSL. In some cases it may be possible to measure the attenuation curve if the link is not successful, but the necessary information has already been collected. For recent ITU DSL standards, the parameter HLOG is used to denote the magnitude of the attenuation per subchannel. 
         [0011]    One exemplary embodiment observes whether the per-subchannel attenuation measured by the modems differs significantly from any attenuation curve that corresponds to a topology that could possibly occur in reality across a transmission line that does not contain a metallic fault. If a significant difference exists between the measured attenuation curve and the most similar attenuation curve corresponding to a realistic metallic-fault-free loop, then a fault can be inferred such as one or more of the faults listed above. 
         [0012]    Aspects of the invention are thus directed toward a module capable of detecting the presence of a fault by comparing a measured attenuation curve with a best-fit attenuation curve, wherein the measured attenuation curve is reported by a modem, and the best-fit attenuation curve is derived by considering models of possible attenuation curves that could occur for loops that do not contain metallic faults. 
         [0013]    Another aspect is directed toward a method for detecting the presence of a fault comprising comparing a measured attenuation curve with a best-fit attenuation curve, wherein the measured attenuation curve is reported by a modem, and the best-fit attenuation curve is derived by considering models of possible attenuation curves that could occur for loops that do not contain metallic faults. 
         [0014]    Another aspect is directed toward a system for detecting the presence of a fault comprising one or more means for comparing a measured attenuation curve with a best-fit attenuation curve, wherein the measured attenuation curve is reported by a modem, and the best-fit attenuation curve is derived by considering models of possible attenuation curves that could occur for loops that do not contain metallic faults. 
         [0015]    Yet another aspect is directed toward a non-transitory a computer-readable storage media comprising information or instructions that if executed by a processor causes a comparison between a measured attenuation curve with a best-fit attenuation curve, wherein the measured attenuation curve is reported by a modem, and the best-fit attenuation curve is derived by considering models of possible attenuation curves that could occur for loops that do not contain metallic faults. 
         [0016]    Further defining aspects of the above are directed toward a user being notified of the detection of one or more of a fault, such as a metallic fault, or malfunctioning modem. 
         [0017]    Even further defining aspects of the above are directed toward performing additional links to identify additional faults, such as metallic faults, or malfunctioning modems. 
         [0018]    Even further defining aspects of the above are directed toward the detection of a fault, such as a metallic fault, or malfunctioning modem being reported to a management entity via a management interface. 
         [0019]    Even further defining aspects of the above are directed toward performing one or more of the above steps again after some corrective action to remove or mitigate a fault having been performed, such as a user installing a microfilter. 
         [0020]    Any of the above aspects and further aspects may be located in a network management system and/or network operation device that is located inside or outside the network and/or the transceiver(s). The network operation or management device that is located inside or outside the network may be managed and/or operated by a user, consumer, service provider, utility provider or a governmental entity. 
         [0021]    These and other features and advantages of this invention are described in, or are apparent from, the following detailed description of the exemplary embodiments. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0022]    The exemplary embodiments of the invention will be described in detail, with reference to the following figures, wherein: 
           [0023]      FIG. 1  illustrates an exemplary communications system. 
           [0024]      FIG. 2  is a flowchart outlining an exemplary method for determining whether faults are present on a communications channel. 
       
    
    
     DETAILED DESCRIPTION 
       [0025]    The exemplary embodiments of this invention will be described in relation to communications systems, as well as protocols, techniques, means and methods for performing communication diagnostics, such as in a DSL or multicarrier communications environment, a home network and/or an access network, or in general any communications network operating using any communications protocol(s). Examples of such home or access networks include home powerline networks, access powerline networks, home coaxial cable network, access coaxial cable network, wireless home networks, wireless corporate networks, home telephone networks and access telephone networks. It should be appreciated however that in general, the systems, methods and techniques disclosed herein will work equally well for other types of communications environments, networks and/or protocols. 
         [0026]    The exemplary systems and methods of this invention will also be described in relation to wired or wireless modems/transceivers and/or a software and/or a hardware testing module, a telecommunications test device, or the like, such as a DSL modem, an ADSL modem, and xDSL modem, a VDSL modem, a line card, a G.hn transceiver, a MOCA transceiver, a Homeplug® transceiver, a power line modem, a wired or wireless modem, test equipment, a multicarrier transceiver, a wireless wide/local area network system, a satellite communications system, network-based communications systems, such as an IP, Ethernet or ATM system, a modem equipped with diagnostic capabilities, or the like, or a separate programmed general purpose computer having a communications device that is capable of operating in conjunction with any one or more of the following communications protocols: MOCA, G.hn, Homeplug, IEEE 802.11, IEEE 802.3, or the like. However, to avoid unnecessarily obscuring the present invention, the following description omits well-known structures, operations and devices that may be shown in block diagram form or are otherwise summarized or known. 
         [0027]    For purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the present invention. It should be appreciated however that the present invention may be practiced in a variety of ways beyond the specific details set forth herein. Furthermore, while the exemplary embodiments illustrated herein show various components of this system collocated, it is to be appreciated that the various components of the system can be located at distant portions of a distributed network, such as a communications network, node, within a Domain Master, and/or the Internet, or within a dedicated secured, unsecured, and/or encrypted system and/or within a network operation or management device that is located inside or outside the network. As an example, a Domain Master can also be used to refer to any device, system or module that manages and/or configures or communicates with any one or more aspects of the network or communications environment and/or transceiver(s). 
         [0028]    Thus, it should be appreciated that the components of the system can be combined into one or more devices, or split between devices, such as a modem, a station, a Domain Master, a network operation or management device, a node or collocated on a particular node of a distributed network, such as a communications network. As will be appreciated from the following description, and for reasons of computational efficiency, the components of the system can be arranged at any location within a distributed network without affecting the operation thereof. For example, the various components can be located in a Domain Master, a node, a domain management device, such as a MIB, a network operation or management device, a transceiver(s), or some combination thereof. Similarly, one or more of the functional portions of the system could be distributed between a modem and an associated computing device/system, and/or in a dedicated test and/or measurement device. 
         [0029]    Furthermore, it should be appreciated that the various links  5 , including the communications channel(s) connecting the elements can be wired or wireless links or any combination thereof, or any other known or later developed element(s) capable of supplying and/or communicating data to and from the connected elements. The term module as used herein can refer to any known or later developed hardware, software, firmware, or combination thereof, that is capable of performing the functionality associated with that element. The terms determine, calculate, and compute and variations thereof, as used herein are used interchangeable and include any type of methodology, process, technique, mathematical operational or protocol. The terms transceiver and modem are also used interchangeably herein. The terms transmitting modem and transmitting transceiver as well as receiving modem and receiving transceiver are also used interchangeably herein. 
         [0030]    The term management interface (e.g., MIB  200 ) includes any type of interface between a management entity(ies) and/or technician(s) and a transceiver(s), such as, a CO-MIB or CPE-MIB as described, for example, in ITU Standard G.997.1, which is incorporated herein by reference in its entirety. 
         [0031]    Moreover, while some of the exemplary embodiments described herein are directed toward a transmitter portion of a transceiver performing certain functions, this disclosure is intended to include corresponding receiver-side functionality in both the same transceiver and/or another transceiver, and vice versa. 
         [0032]      FIG. 1  illustrates an exemplary communications environment  1 . The communications environment  1 , in addition to well known componentry, includes transceiver  100 , a second transceiver  200  and MIB  210 , interconnected via one or more communications links  5 . The transceivers  100  and  200  can include comparable componentry including message generation module  110 , rate impact module  120 , fault detection module  130 , PSD (Power Spectral Density) module  140 , attenuation curve library  150 , comparison module  160 , attenuation curve measurement module  170 , best-fit module  180 , a transmitter module  190 , a receiver module  192 , processor/controller  102  and memory  104 . 
         [0033]    In operation, and with the assistance of the attenuation curve measurement module  170 , the best-fit module  180 , and the attenuation curve library  150 , an attenuation curve is found that corresponds to a possible loop without a fault that most closely matches a measured attenuation curve—this match will be referred to as the best-fit attenuation curve. 
         [0034]    The attenuation curve library could be generated by direct measurements of loop attenuations or theoretical modeling of loop attenuations. Theoretical modeling of loop attenuations can be formulated in any of several ways ranging from simplified approximations to more accurate descriptions of the physics. One simplified example of an attenuation curve model is a straight line when attenuation is graphed as a function of frequency, in which case the slope and offset of the line could be stored in a lookup from the best fit to measurements or could also be parameterized as a function of loop topology. This approximation may be appropriate in a network where it is known a priori that there are no bridged taps, but it may not be appropriate if one or more bridged taps may be present on the measured loop. An example of a more accurate formulation of attenuation would be to use a formula such as: 
         [0000]        H   M ( f )=log 10 (4)− L   M ·Re{γ( f )}·log 10 ( e )−log 10 (|2+tan  h ( L   T1 ·γ( f ))|)−log 10 (|2+tan  h ( L   T2 ·γ( f ))|)
 
         [0000]    where H M (f) is given in dB, γ(f) is the complex propagation constant of the wire, L M  is the length of the main loop, L T1  is the length of the first bridged tap, and L T2  is the length of the second bridged tap, where in this example the loop consists of a uniform wire gauge. 
         [0035]    An even more accurate formulation of attenuation would utilize “ABCD” modeling of the electrical networks, which is well established in the field. The aforementioned formulations of attenuation are but a few of the possible approaches. It should also be recognized that there are many possible approaches to finding the attenuation curve that most closely matches the measured attenuation curve. For example, forward modeling methods may be applied to search through the range of all possible topologies sampled at discrete points. Alternatively, inverse modeling techniques may be applied. Alternatively, some combination of forward and inverse modeling may be applied. The aforementioned approaches to finding the best fit attenuation curve are but a few of the possible approaches. 
         [0036]    In cooperation with the processor  102  and attenuation curve measurement module  170 , it may be necessary to first apply a correction to the measured attenuation curve vector to compensate for, for example, systematic biases in the data. This correction can be determined in advance and pre-stored, and/or it can be determined dynamically based upon known behavior of modems. It should also be apparent that the calibration may be applied in reverse to the curves in the attenuation curve library instead of applying calibration to the measurement. This correction factor may be omitted if the modems are known to produce attenuation curves that are accurate to within certain tolerances that are significantly smaller than the thresholds used for determining a fault condition. Sometimes, a simple calibration may need to be applied, such as by multiplying the measured attenuation by a constant scale factor. More often a slightly more complex calibration is needed that multiplies each tone of the measured attenuation by a scale factor that changes for each tone. A more complex yet more accurate calibration changes these tone-dependent scaled factors as a function of the loop topology. In this case, it may be more convenient to apply the calibration to each of the curves in the attenuation library instead of to the measurement, but it also is possible to use decision-directed methods to apply a loop-dependent calibration to the measurement. The aforementioned approaches to applying calibration are but a few of the possible approaches. To pre-determine the calibration curves, the most straight-forward approach is to measure attenuation across a range of known loops, divide the measured attenuation curves per-tone by the theoretical models in the attenuation curve library, and store the resulting corrections in the calibration table. Alternatively, the corrections can be fit to a parametric model, and the model can be stored for later use in dynamically generating the corrections. 
         [0037]    The comparison module  160  then compares the measured attenuation curve and the best-fit attenuation curve over one or more subchannels. The subchannels may be selected base on whether they are known to be sufficiently accurate or on one or more other criteria. The fault detection module  130  then determines, based on the comparison, whether one or more of the detectable fault types listed above are present on the communications channel. This may occur when the measured attenuation curve is significantly different than the best-fit attenuation curve, indicating that something present in the measurement (e.g., a metallic fault or other fault) is not being taken into account by the best-fit attenuation curve. 
         [0038]    One exemplary approach for comparing the measured attenuation curve and the best-fit attenuation curve is to decide whether a fault is present would be to determine whether the following inequality is true: 
         [0000]      MeasuredAttenuation/ModeledAttenuation&lt;AttenuationErrorThreshold, 
         [0039]    where AttenuationErrorThreshold is a ratio that allows for modeling and measurement errors to occur without a tolerable rate of false fault detections and missed fault detections. 
         [0040]    The message generation module  110  can then report whether a fault has been detected, a fault is known not to be present, or whether a determination cannot be made because, for example, the known inaccuracies of the system could alone cause the above inequality to be true. 
         [0041]    This report may be done in a number of ways. For example, and in cooperation with the message generation module  110  and the transmitter module  190 , a message or signal or indication may be sent to a user and/or service provider technician. Alternatively, or in addition, the report regarding fault detection may be reported over a management interface to a management entity, such as service provider MIB  210  (e.g., as defined in ITU G.997.1). A confidence metric may also be reported to a user, service technician and/or the MIB  210  indicating the extent to which the reported outcome is likely to correspond to reality. 
         [0042]    In some cases, and with the cooperation of the rate impact module  120 , the attainable data rate from the measured attenuation curve can be determined and subtracted from the attainable data rate determined from the best-fit attenuation curve, resulting in the rate impact from any fault that was detected. The rate impact estimates can be determined using any one of several link assumptions including the actual link parameters used to obtain the measured attenuation curve. In fact, the actual link data rate could be used directly instead of determining the data rate from the measured data. This rate impact from the fault can be reported to the user, service technician and/or the MIB  210 . 
         [0043]    The above analysis for determining the presence of the fault may also be performed on the attenuation curve values in aggregate optionally using a weighted combination. 
         [0044]    For all links initiated to collect data as an input to the techniques disclosed herein, link settings may be set to maximize or increase the probability that relevant data can be collected. For example, because it may not be necessary to remain in Showtime for any extended period of time, if at all, a required SNR margin often can be set very low. Similarly, it may be advisable to set a minimum data rate requirement beyond any imposed by the standard or modem implementations. By allowing links to occur with fewer constraints, the exemplary techniques disclosed herein can potentially link and acquire data on more “difficult” lines (e.g., longer lines and/or lines that contain high noise). 
         [0045]    Each time that the steps described above are exercised, the presence of a fault can be detected. If the presence of a fault is detected, it may not be possible to determine (using only the above steps) exactly how many faults are present. To accomplish this, and in cooperation with the message generation module  110 , a user may be instructed to first identify, locate and remove at least one fault condition and then repeat the above steps. This process can be iteratively performed until, for example, no more faults are detected. An artifact of this iterative process is that it allows the user to determine how many faults are present on the line. Different approaches may be used to identify and locate the specific fault such as time-domain reflectometry (TDR), single-ended line testing (SELT) techniques, and/or narrow-band electrical measurements such as capacitance and resistance. 
         [0046]    A confidence metric can also be formulated that quantifies the extent to which it is known that a fault is present on the line. This confidence metric can be formulated in terms of a probability given the information that is known, or some other metric that is informative to the user. 
         [0047]    Note that the proposed techniques can also be used as a form of “domain location,” which is to say that the steps can narrow down the probability that a particular problem occurs within some part of a network (e.g., inside the customer premises, inside the central office, in the cables in the field, in some specific portion of a network, etc). Given the situation when a fault is detected, the probability that the fault occurs in a specific domain can be conditioned on information about the prevalence of faults, metallic faults, malfunctioning hardware, etc. 
         [0048]    Furthermore, if the fault is detected only in the downstream data but not in the upstream data, then additional information can be inferred about the type of fault. Similar conclusions could be inferred if the fault is detected only in the upstream data but not in the downstream data, if the fault is detected in both sets of data, or in neither set of data. 
         [0049]      FIG. 2  outlines an exemplary method for detecting faults. In particular, control begins in step S 200  and continues to step S 210 . In step S 210 , the attenuation curve for the communications channel is measured. Next, in step S 220 , a correction can optionally be applied to the measured attenuation curve to compensate for one or more conditions such as systematic biases. As discussed, these corrections can be determined in advance and pre-stored, and/or they can be determined dynamically based upon known behavior of modems. Then, in step S 230 , a best-fit attenuation curve is found. Control then continues to step S 240 . 
         [0050]    In step S 240 , the measured attenuation curve is compared to the best-fit attenuation curve over one or more subchannels. Next, based on the comparison in step S 240 , a determination is made whether fault(s) are present. Then, in step S 260  reporting of the fault can optionally be performed. As discussed, the reporting can include information indicating whether a fault has been detected, whether a fault is known not to be present, or whether a determination cannot be made because, for example, the known inaccuracies of the system could alone cause the disclosed inequality to be true. This report can be sent to one or more of a user, technician and a MIB. Control then continues to step S 270 . 
         [0051]    In step S 270 , a rate impact can optionally be determined. If a rate impact is to be determined, control continues to step S 272  with control otherwise continuing to step S 280 . In step S 272 , the rate impact from the detected fault(s) is determined. Next, in step S 274 , the determined rate impact can optionally be reported to one or more of a user, service technician and the MIB. Control then continues to step S 280 . 
         [0052]    In step S 280 , a determination is made whether the fault has been reported to the user and whether the steps should be repeated. For example, the user could be notified that there are one or more types of fault and that corrective action such as the addition of a microfilter, etc., needs to be installed. After the corrective action, the above steps could be repeated with control jumping back to step S 210  to determine if one or more additional faults exist. Otherwise, control continues to step S 290  where the control sequence ends. 
         [0053]    As used herein the terms network and domain have the same meaning and are used interchangeably. The terms subcarrier, subchannel and tone also have the same meaning and are used interchangeably in the description. Also, the terms receiver, receiving node and receiving transceiver have the same meaning and are used interchangeably. Similarly, the terms transmitter, transmitting node and transmitting transceiver have the same meaning and are used interchangeably. The terms transceiver and modem also have the same meaning and are used interchangeably. While the term home network has been used in this description, the description is not limited to home networks but in fact applies also to any network, such as enterprise networks, business networks, or any network with a plurality of connected nodes. The terms transceiver, node and modem have the same meaning and are used interchangeably in the description. The term frame and packet have the same meaning and may be used interchangeably in the description. The term header and PHY-frame header have the same meaning and may be used interchangeably in the description. 
         [0054]    The terms network and home network have the same meaning and are used interchangeably in the description. While the term home network has been used in this description, the description is not limited to home networks but in fact applies also to any network, such as enterprise networks, business networks, or any network with a plurality of connected nodes. 
         [0055]    While the above-described methods and systems were described in relation to a transceiver, they can also be implemented in a dedicated module such as a test or network optimization module. 
         [0056]    The above-described methods and systems and can be implemented in a software module, a software and/or hardware testing module, a telecommunications test device, a DSL modem, an ADSL modem, an xDSL modem, a VDSL modem, a linecard, a G.hn transceiver, a MOCA transceiver, a Homeplug transceiver, a powerline modem, a wired or wireless modem, test equipment, a multicarrier transceiver, a wired and/or wireless wide/local area network system, a satellite communication system, network-based communication systems, such as an IP, Ethernet or ATM system, a modem equipped with diagnostic capabilities, or the like, or on a separate programmed general purpose computer having a communications device or in conjunction with any of the following communications protocols: CDSL, ADSL2, ADSL2+, VDSL1, VDSL2, HDSL, DSL Lite, IDSL, RADSL, SDSL, UDSL, MOCA, G.hn, Homeplug® or the like. 
         [0057]    Additionally, the systems, methods and protocols of this invention can be implemented on a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a flashable device, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device such as PLD, PLA, FPGA, PAL, a modem, a transmitter/receiver, any comparable means, or the like. In general, any device (or one or more equivalent means) capable of implementing a state machine that is in turn capable of implementing the methodology illustrated herein can be used to implement the various communication/measurement methods, protocols and techniques according to this invention. 
         [0058]    Furthermore, the disclosed methods may be readily implemented in software stored on a non-transitory computer-readable information storage media using, for example, object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this invention is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized. The communication systems, methods and protocols illustrated herein can be readily implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the functional description provided herein and with a general basic knowledge of the computer and telecommunications arts. 
         [0059]    Moreover, the disclosed methods may be readily implemented in software that can be stored on a computer-readable storage medium, executed on programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. The systems and methods of this invention can be implemented as a program embedded on personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated communication system or system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system, such as the hardware and software systems of a test/modem device. 
         [0060]    While the invention is described in terms of exemplary embodiments, it should be appreciated that individual aspects of the invention could be separately claimed and one or more of the features of the various embodiments can be combined. 
         [0061]    While the exemplary embodiments illustrated herein discuss the various components collocated, it is to be appreciated that the various components of the system can be located a distant portions of a distributed network, such as a telecommunications network and/or the Internet or within a dedicated communications network. Thus, it should be appreciated that the components of the system can be combined into one or more devices or collocated on a particular node of a distributed network, such as a telecommunications network. As will be appreciated from the following description, and for reasons of computational efficiency, the components of the communications network can be arranged at any location within the distributed network without affecting the operation of the system. 
         [0062]    It is therefore apparent that there has been provided, in accordance with the present invention, systems and methods for communications diagnostics. While this invention has been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be or are apparent to those of ordinary skill in the applicable arts. Accordingly, it is intended to embrace all such alternatives, modifications, equivalents and variations that are within the spirit and scope of this invention.