This disclosure relates generally to digital subscriber line (DSL) communications, and, more particularly, to methods and apparatus to determine DSL configuration parameters based on current and historical DSL performance characteristics.
When a customer requests DSL service (e.g., Asymmetric DSL (ADSL), Symmetric DSL (SDSL), High-speed DSL (HDSL), etc.) it can be difficult for the service provider to determine the highest DSL data rate that the telephone line between the central office and the customer's location can reliably achieve (e.g., with sufficiently low receiver error rates) (i.e., the maximum capable DSL speed). Often, the service provider determines, and offers, a DSL data rate (i.e., a DSL configuration parameter) that is determined based on an estimate of the length of the telephone line. For instance, consider an example customer site that is 12,000 feet from a central office (CO). The service provider knows that most telephone lines of that length can reliably attain 1.5 Million bits per second (Mbps) and, thus, offers that DSL data rate to the customer. However, some customers at that distance can reliably achieve 3 Mbps. Thus, the customer is not offered the highest possible DSL data rate (possibly causing the customer to select a broadband service from an alternative service provider), and/or the service provider loses potential revenue from not being able to sell a higher DSL data rate.
A similar difficulty arises in situations where: a) a customer already has DSL service and now has interest in a higher data rate; or b) a service provider wishes to determine which customers could be offered a higher data rate, in an effort to increase revenues from DSL services. In general, there is a difference between the estimated DSL data rate and the maximum DSL data rate that a telephone line is capable of reliably supporting (i.e., the maximum capable DSL speed).
In typical central offices, a plurality of CO DSL modems (i.e., DSL modems co-located at the CO) are integrated together to form a well-known prior-art DSL Access Multiplexer (DSLAM). Thus, a DSLAM supports simultaneous DSL communications with a plurality of customer premise equipment (CPE) DSL modems (i.e., DSL modems located at a plurality of customer locations) across a plurality of telephone lines.
A pair of CPE and CO DSL modems can measure and report statistics concerning the performance of DSL communications currently active between them (i.e., DSL performance characteristics). For example, the pair of modems can measure the maximum attainable bit rate (MABR) that the pair of modems could currently achieve on the telephone line, a count of receiver errors over fixed intervals of time (e.g., 15 minutes, 24 hours, etc.), etc. Typically, the MABR will be larger than the maximum capable DSL speed that represents the DSL data rate that the telephone line is capable of reliably supporting. A large count of receiver errors in a fixed interval of time can indicate the presence of impulse noise on the telephone line.
DSL performance characteristics (e.g., the current MABR, the count of receiver errors, etc.) can be measured and reported using a variety of well know techniques. For example, they can be measured based on the International Telecommunications Union (ITU) G.992.1 standard for ADSL and/or the ITU G.997.1 standard for management of DSL modems. In particular, DSL modems can monitor forward error correction (FEC) errors to detect and count receiver errors, and can accumulate the number of FEC errors that occurred in a sliding interval of time (e.g., 15 minutes, 24 hours, etc.). However, as discussed above, the current MABR reported by the CO or CPE DSL modem may be different (e.g., higher or lower) from the current DSL data rate being sold to the customer.
As discussed above, the length of a telephone line is not always a good indication of the maximum capable DSL speed for that telephone line. Relying on current DSL performance characteristics (e.g., MABR, count of receiver errors, etc.) as an indication of appropriate DSL configuration parameters (e.g., DSL data rate) ignores conditions on the telephone line (e.g., varying noise, temperature, moisture, etc.) that may cause variations in DSL performance (e.g., varying MABR, or bursts of receiver errors due to impulse noise). For example, current DSL performance characteristics (e.g., MABR) could indicate that the telephone line can support 2 Mbps, while past (i.e., historical) DSL performance characteristics could indicate that the telephone line can reliably only support 1.5 Mbps. Thus, using both current and historical DSL performance characteristics provides a more accurate and consistent measure of the maximum capable DSL speed for a telephone line.
In the illustrated example of
It will be readily apparent to persons of ordinary skill in the art that the DMD 125 could collect and record additional DSL performance characteristics into the database 130. For example, interleaved data stream anomalies, current noise margin, etc. It will also be readily apparent to persons of ordinary skill in the art that the DMD 125 and the database 130 could be implemented using any suitable computing platform. For example, a personal computer or computer server could be used to implement the DMD 125, and a non-volatile memory device (e.g., a hard-disk drive) associated with the personal computer or computer server could be used to implement the database 130.
In the illustrated example of
It will be readily appreciated by persons of ordinary skill in the art that the DMD 125 can interact with the DSLAM 105 on a periodic or occasional basis. For example, once a week the DMD 125 could record a current MABR and 15-minute error count for each active DSL line into the database 130. The DMD 125 could also identify underperforming DSL lines (e.g., DSL lines whose current DSL data rate is below a previously determined maximum capable DSL speed). For such DSL lines, MABR and 15-minute error count values could be collected more frequently (e.g., once an hour). Telephone lines on which to collect data more frequently could also be determined by a marketing or sales organization. For example, the marketing and sales organization might select, based on demographics, past service orders, etc., customers (i.e., DSL lines) who might be interested in a higher DSL data rate. Gathering data more frequently facilitates an even more accurate determination of DSL configuration parameters (e.g., the maximum capable DSL speed) for a telephone line.
To determine DSL configuration parameters for a telephone line (e.g., a maximum capable speed, a need for interleaving, etc.) based on the current and historical DSL performance characteristics, the illustrated example of
In a marketing example (i.e., “batch”), the client device 140 identifies a plurality of telephone lines for which a user desires DSL configuration parameters (e.g., maximum capable DSL speeds). For efficiency, processing may be performed in a “batch” mode. That is, the client device 140 provides to the DSCD 135 a list containing the identified telephone lines. The DSCD 135 then determines (e.g., using an iterative process) one or more DSL configuration parameters (e.g., a maximum capable DSL speed) for each of the identified telephone lines, and reports a list of the determined DSL configuration parameters to the client device 140.
It will be readily apparent to persons of ordinary skill in the art that the client device 140 may be implemented using any one of a variety of well known devices. In an example, the client device 140 could be a computer display or terminal (or equivalent user interface device or software), connected to the DSCD 135 via any one of a variety of well known techniques (e.g., serial cable, Ethernet, video cable), capable to allow a user (e.g., a customer service representative) to specify a telephone line for which the user desires the maximum capable DSL speed (i.e., a DSL configuration parameter). In another example, the client device 140 could be a personal computer, computer server, or other suitable computing platform, connected to the DSCD 135 via any one of a variety of well known techniques (e.g., serial cable, Ethernet, Internet, etc.), capable of communicating with the DSCD 135. In particular, the client device 140 may execute software to: a) allow a user (e.g., a marketing or salesperson) to select a list of one or more telephone lines; b) send the list of telephone lines to the DSCD 135; c) receive from the DSCD 135 DSL configuration parameters (e.g., a maximum capable DSL speed) for each of the selected telephone lines; and d) provide a display or report of the reported DSL configuration parameters to the user.
To determine a maximum capable DSL speed for a telephone line (i.e., a DSL configuration parameter), the DSCD 135 of
Max_capable=scale_factor*min{current, historical},
where Max_capable is the maximum capable DSL speed, {current, historical} represents the set of current and historical MABR values for the telephone line, and scale_factor is any appropriate numerical value.
It will be readily apparent to persons of ordinary skill in the art that the scale factor can be chosen using any of a variety of techniques. In the illustrated example of
The DSCD 135 of
By having the DSCD 135 provide, for example, to the client device 140, determined DSL configuration parameters, the client device 140 can ensure that a service plan (e.g., a DSL data rate) sold to and configured for a customer will operate reliably (e.g., not experience a large numbers of receiver errors that might interfere with the customer's use of the DSL service). In an example, a customer contacts customer service to inquire about a higher data rate DSL service, the customer service representative (via the client device 140) obtains from the DSCD 135 DSL configuration parameters (e.g., the maximum capable DSL speed that the customer's DSL line can reliably support and whether interleaving is required). Based upon the information obtained from the DSCD 135 via the client device 140, the customer service representative can inform the customer of the highest DSL data rate the service provider can reliably provide. If, based upon that information (i.e., the maximum capable DSL speed), the customer requests a higher data rate (not exceeding the maximum capable DSL speed), the customer service representative can create an appropriate work order (e.g., a request to re-configure the customer's DSL service) that includes the selected DSL data rate, and the enabling of interleaving (as determined and reported by the DSCD 135) as appropriate.
It will be readily apparent to persons of ordinary skill in the art that the DMD 125, the database 130, the DSCD 135, and/or the client device 140 may be integrated together using a single computing platform. For example, the example processor platform 300 of
The example machine readable instructions of
Returning to block 206, if the telephone line does not have DSL trouble reported, the DSCD 135 determines (as discussed above) if applicable historical data is available (block 212). If applicable historical data is available (block 212), the DSCD 135 sets the flag equal to YES to indicate that applicable historical data is available (block 214), and sets the value of the scale factor based on the number of applicable historical data points (block 216). For example, the scale factor is chosen to be 80% (i.e., 0.8) if at least 4 applicable historical data points are available, 75% if 3 applicable historical data points are available, 70% if 2 applicable historical data points are available, and 60% (i.e., 0.6) otherwise.
Returning to block 212, if no applicable historical data is available, the DSCD 135 sets the flag equal to NO to indicate that there is no applicable historical data available (block 222). The DSCD 135 then sets the value of the scale factor to a low value (e.g., 60%) (block 224).
Continuing at block 226, the DSCD 135 determines (as described above) a maximum capable DSL speed (block 226), and determines (as described above) whether or not interleaving should be enabled for the DSL service on the telephone line (block 228). In blocks 226 and 228, the DSCD 135 uses the value of the flag to determine if historical data is used in the determination of the minimum MABR or the maximum 15-minute error count. For example, if the flag is NO, historical data is not used.
The DSCD 135 then stores into the database 130, or reports to the client device 140, the determined DSL configuration parameters (e.g., the maximum capable DSL speed and whether or not interleaving should be enabled) (block 230). For example, if the client device 140 is interacting with the DSCD 135 in a transactional mode, the DSCD 135 could immediately report the determined DSL configuration parameters. Alternatively, the DSCD 135 could store the results for later reporting to the client device 140 (i.e., “batch” mode). If all selected telephone lines have been processed (block 232), the example machine readable instructions of
It will be readily apparent to persons of ordinary skill in the art that the DSCD 135 could determine other DSL configuration parameters (e.g., minimum noise margin, Reed Solomon coding parameters, etc.) based on additional current and historical DSL performance characteristics (e.g., interleaved data stream anomalies, current noise margin, etc.)
The processor platform 300 of the example of
The processor 310 is in communication with the main memory (including a read only memory (ROM) 320 and a RAM 325) via a bus 305. The RAM 325 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic DRAM, and/or any other type of RAM device. The ROM 320 may be implemented by flash memory and/or any other desired type of memory device. Access to the memory 320 and 325 is typically controlled by a memory controller (not shown) in a conventional manner. The RAM 325 could be used to implement the database 130 of
The processor platform 300 also includes a conventional interface circuit 330. The interface circuit 330 may be implemented by any type of well known interface standard, such as an external memory interface, serial port, general purpose input/output, etc.
One or more input devices 335 and one or more output devices 340 are connected to the interface circuit 330. The input devices 335 and output devices 340 may be used to implement interfaces between the DSCD 135 and the database 130, and/or between the DMD 125 and the database 130.
Of course, persons of ordinary skill in the art will recognize that the order, size, and proportions of the memory illustrated in the example systems may vary. Additionally, although this patent discloses example systems including, among other components, software or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. Accordingly, persons of ordinary skill in the art will readily appreciate that the above described examples are not the only way to implement such systems.
Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.
Number | Name | Date | Kind |
---|---|---|---|
5751338 | Ludwig, Jr. | May 1998 | A |
5974139 | McNamara et al. | Oct 1999 | A |
5987061 | Chen | Nov 1999 | A |
6044107 | Gatherer et al. | Mar 2000 | A |
6055268 | Timm et al. | Apr 2000 | A |
6081291 | Ludwig, Jr. | Jun 2000 | A |
6246694 | Chen | Jun 2001 | B1 |
6292559 | Gaikwad et al. | Sep 2001 | B1 |
6317495 | Gaikwad et al. | Nov 2001 | B1 |
6424636 | Seazholtz et al. | Jul 2002 | B1 |
6424657 | Voit et al. | Jul 2002 | B1 |
6430219 | Zuranski et al. | Aug 2002 | B1 |
6445733 | Zuranski et al. | Sep 2002 | B1 |
6466088 | Rezvani et al. | Oct 2002 | B1 |
6467092 | Geile et al. | Oct 2002 | B1 |
6477238 | Schneider et al. | Nov 2002 | B1 |
6480475 | Modlin et al. | Nov 2002 | B1 |
6498791 | Pickett et al. | Dec 2002 | B2 |
6507606 | Shenoi et al. | Jan 2003 | B2 |
6532277 | Ulanskas et al. | Mar 2003 | B2 |
6538451 | Galli et al. | Mar 2003 | B1 |
6549568 | Bingel | Apr 2003 | B1 |
6567464 | Hamdi | May 2003 | B2 |
6570855 | Kung et al. | May 2003 | B1 |
6597689 | Chiu et al. | Jul 2003 | B1 |
6608835 | Geile et al. | Aug 2003 | B2 |
6614781 | Elliott et al. | Sep 2003 | B1 |
6625255 | Green et al. | Sep 2003 | B1 |
6636525 | Davis | Oct 2003 | B1 |
6640239 | Gidwani | Oct 2003 | B1 |
6643266 | Pugaczewski | Nov 2003 | B1 |
6658052 | Krinsky et al. | Dec 2003 | B2 |
6667971 | Modarressi et al. | Dec 2003 | B1 |
6668041 | Kamali et al. | Dec 2003 | B2 |
6674725 | Nabkel et al. | Jan 2004 | B2 |
6674749 | Mattathil | Jan 2004 | B1 |
6680940 | Lewin et al. | Jan 2004 | B1 |
6697768 | Jones et al. | Feb 2004 | B2 |
6700927 | Esliger et al. | Mar 2004 | B1 |
6704351 | Ott et al. | Mar 2004 | B1 |
6724859 | Galli | Apr 2004 | B1 |
6728238 | Long et al. | Apr 2004 | B1 |
6731678 | White et al. | May 2004 | B1 |
6735601 | Subrahmanyam | May 2004 | B1 |
6751218 | Hagirahim et al. | Jun 2004 | B1 |
6751315 | Liu et al. | Jun 2004 | B1 |
6751662 | Natarajan et al. | Jun 2004 | B1 |
6754283 | Li | Jun 2004 | B1 |
6762992 | Lemieux | Jul 2004 | B1 |
6763025 | Leatherbury et al. | Jul 2004 | B2 |
6765864 | Natarajan et al. | Jul 2004 | B1 |
6765918 | Dixon et al. | Jul 2004 | B1 |
6769000 | Akhtar et al. | Jul 2004 | B1 |
6769024 | Natarajan et al. | Jul 2004 | B1 |
6771673 | Baum et al. | Aug 2004 | B1 |
6775232 | Ah Sue et al. | Aug 2004 | B1 |
6775267 | Kung et al. | Aug 2004 | B1 |
6775268 | Wang et al. | Aug 2004 | B1 |
6775273 | Kung et al. | Aug 2004 | B1 |
6778525 | Baum et al. | Aug 2004 | B1 |
6782082 | Rahamim | Aug 2004 | B2 |
6785288 | Enns et al. | Aug 2004 | B1 |
6801570 | Yong | Oct 2004 | B2 |
6819746 | Schneider et al. | Nov 2004 | B1 |
6914961 | Holeva | Jul 2005 | B2 |
6985444 | Rosen | Jan 2006 | B1 |
7106833 | Kerpez | Sep 2006 | B2 |
7162011 | Kolligs et al. | Jan 2007 | B2 |
7272209 | Jiang et al. | Sep 2007 | B2 |
20020057763 | Sisk et al. | May 2002 | A1 |
20020141443 | Christensen et al. | Oct 2002 | A1 |
20030086514 | Ginis et al. | May 2003 | A1 |
20040095921 | Kerpez | May 2004 | A1 |
20050141673 | Lunt et al. | Jun 2005 | A1 |
20050163286 | Jiang et al. | Jul 2005 | A1 |
20060268733 | Rhee et al. | Nov 2006 | A1 |
20070274458 | Jiang et al. | Nov 2007 | A1 |
Number | Date | Country |
---|---|---|
0205529 | Jan 2002 | WO |
2005072102 | Aug 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20070002758 A1 | Jan 2007 | US |