Not applicable.
Not applicable.
Digital subscriber line (DSL) technologies provide a large bandwidth for digital communications over existing subscriber lines (e.g., copper pairs). When transmitting data over the subscriber lines, crosstalk interference can occur between the transmitted signals over adjacent lines, for example in a same or nearby bundle of lines. Crosstalk, including near-end crosstalk (NEXT) and far-end crosstalk (FEXT), may limit the performance of various DSL systems, such as those defined by standards including asymmetric DSL 2 (ADSL2), very high speed DSL (VDSL), very high speed DSL 2 (VDSL2), and G.fast (a proposed standard).
Many current DSL systems, including ADSL2, ADSL2+, VDSL, and VDSL2, and future DSL systems, including G.fast, may employ discrete multitone (DMT) modulation. In systems that employ DMT, a small number of subcarriers may be dedicated as pilot tones to facilitate timing recovery. In systems that employ frequency division duplexing (FDD), such as ADSL2 and VDSL2, pilot tones may be transmitted continuously from operator side modems, which facilitates timing recovery and timing tracking at subscriber side modems. Initial timing may be acquired during an initialization state. During a showtime state, after initialization, the pilot tones may be continuously transmitted, which allows a receiver's clock to stay locked to the transmitter clock by tracking any changes in a transmitter clock frequency and/or phase or any drift in its own oscillator.
However, unlike FDD systems, time-division duplex (TDD) systems may have separate time intervals for upstream (US) and downstream (DS) transmission. During US transmission from a remote side modem, for example, there may be no DS transmission from a corresponding modem at a central office (CO), remote terminal (RT), or distribution point unit (DPU), in cases of ADSL(2/2+), VDSL(2), and G.fast, respectively, if a TDD system is used. Therefore, pilot tones may not be transmitted on the DS during an US transmission. With no DS transmission, there will be no timing tracking. The situation gets worse if discontinuous mode power saving is used in G.fast standard, LPLS for example, where there is no or minimal DS transmission when there is no user traffic. As a result, timing may drift between the operator and remote side modems to a value large enough to make communication unsatisfactory or difficult. As a result, there is a need for improving timing correction in TDD systems.
In one embodiment, the disclosure includes a method in a TDD transceiver coupled to a subscriber line, the method comprising receiving a DMT signal from a second transceiver after a period of inactivity on the subscriber line, wherein the DMT signal comprises a plurality of pilot tones, and determining a timing offset between the transceiver and the second transceiver based on the plurality of pilot tones.
In another embodiment, the disclosure includes a TDD transceiver configured to couple to a subscriber line, the transceiver comprising a receiver configured to receive a DMT signal from a second transceiver after a period of inactivity on the subscriber line, wherein the DMT signal comprises a plurality of pilot tones, and a processor coupled to the receiver and configured to determine a timing offset between the transceiver and a second transceiver based on the plurality of pilot tones.
In yet another embodiment, the disclosure includes a TDD DSL transceiver for compensating for a timing offset, wherein the timing offset comprises an integer part and a fractional part, the transceiver comprising a processor configured to adjust a phase of each tone of a DMT signal based on the fractional part to generate an adjusted DMT signal, perform an IFFT on the adjusted DMT signal to generate a time-domain signal, and adjust the time-domain signal in time based on the integer part.
In yet another embodiment, the disclosure includes a method of reacquiring loop timing after a period of inactivity between a first transceiver and a second transceiver in a TDD DSL system, the method comprising determining a timing offset between the first transceiver and the second transceiver, generating a transmitted DMT signal, in the first transceiver, based on the timing offset, and adjusting a received DMT signal, in the first transceiver, based on the timing offset.
For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
It should be understood at the outset that, although an illustrative implementation of one or more embodiments are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
Depending on the supported standard, a DSL system may be denoted as an xDSL system, where ‘x’ may indicate any DSL standard. For instance, ‘x’ stands for ‘A’ in ADSL2 or ADSL2+systems, ‘V’ in VDSL or VDSL2 systems, and ‘F’ in G.fast systems. When a transceiver is located in at an operator end of the DSL system, including a central office (CO), DSL access multiplexer (DSLAM), cabinet, or a DPU, the transceiver may be referred to as an xTU-O. On the other hand, when a transceiver is located at a remote or user end such as a customer premise equipment (CPE), the transceiver may be referred to as an xTU-R. For example, if the DSL system is a G.fast system, a transceiver at an operator side may be referred to as a G.fast transceiver unit at an operator side (FTU-O). Similarly, in the G.fast system, a CPE transceiver may be referred to as a FTU at a remote terminal (FTU-R), i.e., at a subscriber side.
DSL systems ADSL2 and VDSL2 may use loop timing where timing recovery is used at an ATU-R and VTU-R, respectively, to recover timing and synchronize to the ATU-O or VTU-O clocks, respectively. The recovered clock may be used by the remote modem to both receive signals in DS direction and transmit signals in the upstream direction. Therefore no timing recovery may be performed at ATU-O or VTU-O.
Some DSL systems, such as G.fast, adopt TDD to allow signal transmission in the DS and US directions. See, for example, ITU—Telecommunication Standardization Sector, Study Group 15, Temporary Document 2012-11-4A-R20, entitled “Updated draft text for G.fast—version 3.0,” November 2012, which is hereby incorporated by reference as if reproduced in its entirety. TDD duplexing may be combined with large bandwidths and low transmit powers in G.fast. Such configurations may make discontinuous mode power saving a viable choice in G.fast. The G.fast standard has adopted this mode for power saving with details to be specified. In this mode a link may be said to be in low-power link state (LPLS). In LPLS there may be no activity for a long period of time, which means that there may be no signal on the link. A long period of inactivity may result in a large timing drift bewteen FTU-R and FTU-O clocks. The timing drift may need to be corrected before communication resumes.
Unlike VDSL2, G.fast standard adopted time-division-duplexing (TDD) to allow signal transmission in down- and up-stream directions. The entire available band may be used in both directions, however, there is no overlap in time between the transmitted signals in down- and up-stream directions and signal transmission in time domain in each direction may be discontinuous. Because there is no overlap in time between the down- and up-stream signals on the line, there is no echo added to the received signal and once the transmission in down- and up-stream directions is synchronized among multiple lines, there will be no near-end crosstalk (NEXT) added to the received signal either. However, FEXT will be present.
DSL access technologies such as ADSL and VDSL use loop timing where timing recovery is used at ATU-R and VTU-R, respectively, to recover timing and synchronize to ATU-O or VTU-O clocks, resepctively. The recovered clock is used at remote modem to transmit signal at upstream direction; therefore no timing recovery is performed at ATU-O/VTU-O. ATU-O/VTU-O receivers completely rely on FTU-R transmitter to transmit signal with correct timing. Similar to ADSL and VDSL standards, G.fast will also use loop timing to synchronize the FTU-O and FTU-R modems.
Note that timing clock is recovered at xTU-R from the xTU-R's received signal by the Timing Recovery block and the recovered clock is used to drive both the ADC and the transmit DAC at xTU-R. xTU-O receiver relies on the timing recovery at xTU-R as its ADC clock is driven by a fixed oscilator clock (“Osc” in the figure); the same clock that drives its DAC. In
All the three standards of ADSL/ADSL2/ADSL2+ and VDSL/VDSL2 and G.fast use discrete multi-tone (DMT) modulation. In DMT modulation, the TX-DSP block receives the TX data bits and encodes them by forward error correction (FEC). FEC output are mapped to QAM (Quadrature Amplitude-Phase Modulation) constellations. QAM constellations are input to an inverse fast Fourier transform (IFFT) modulator that converts the frequency-domain QAM signals to time-domain and writes them into a DAC buffer after adding cyclic prefix and cyclic suffix and windowing operation, as described for ADSL in “Asymmetric digital subscriber line (ADSL) transceivers—Extended bandwidth ADSL2 (ADSL2+),” ITU-T G.992.5, 2003, and as described for VDSL in “Very-high speed Digital Subscriber Line Transceivers 2 (VDSL2 draft),” ITU-T G.993.2, July 2005. DAC reads the data inside the DAC buffer and converts them into analog signal that will further be amplified by the power amplifier LD (Line Driver). In DMT modulation, the RX-DSP after finding the symbol frame boundary, discarding cyclic prefix (CP), possibly performing operation called RX-windowing, takes fast fourier transform (FFT) of the processed samples of a symbol. At its output, FFT produces demodulated complex samples of the DMT symbol that will be multiplied by complex frequency-domain equalizers (FDQs) sample by sample. FDQ coefficients are usually single-tap complex values per FFT output (also called FFT output tone or subcarrier.) After multiplying each FFT output by its corresponding FDQ coefficient the result contains demodulated and equalized signals that will go through FEC decoder to produce RX data bits. See, for example, “Asymmetric digital subscriber line (ADSL) transceivers—Extended bandwidth ADSL2 (ADSL2+)”, ITU-T G.992.5, 2003; “Very-high speed Digital Subscriber Line Transceivers 2 (VDSL2 draft)”, ITU-T G.993.2, July 2005; and “Multicarrier Modulation for Data Transmission: An Idea Whose Time Has Come,” by J.A.C. Bingham, IEEE Communications Magazine, May 1990, which are incorporated by references as if reproduced in their entirety.
In DMT modulation one or more sub-carriers are dedicated as pilot tones to facilitate timing recovery. Because in FDD systems, the pilot tones are continuously transmitted there is usually no issue with timing recovery and timing tracking. Because in showtime, after initialization, the pilot tones are continuously transmitted, the receiver continuously tracks any changes in the transmitter clock frequency and/or phase or any drift in its own oscillator. Unlike FDD system, in a TDD system during upstream (US) transmission there is no downstream (DS) transmission and the pilot tones may not be transmitted in DS. In fact it is very desirable not to transmit pilot tone(s) in DS during US transmisison opportunities to save power as in this case the entire transmit path of the FTU-O maybe powered down. If the length of the US transmission opportunities, during which there is no timing tracking at FTU-R, within a TDD frame becomes too long, the timing drift between the FTU-O and FTU-R VCXOs may become large enough to cause communication problem.
By transmitting multiple pilot tones across the used frequency band after a long inactivity period from an FTU-O to an FTU-R, the FTU-R may estimate an amount of timing drift that may have occurred during a long inactivity period that the timing recovery/tracking block was not able to track due to a lack of pilot tones. This timing offset Tos may become larger than one analog-to-digital sample interval at the receiver. In this case the timing drift may be split into integer and fractional parts. To correct for the phase of the received signal, the frame boundary alignment may be adjusted based on this integer number, and a frequency-domain equalizer (FDQ) phase may be rotated based on the fractional part as will be described subsequently.
This scheme may correct a receive signal offset for an FTU-R. However, this scheme may not correct the phase of the US signal from FTU-R because the phase of the sampler clock that samples the digital-to-analog converter (DAC) and transmits a signal to the FTU-O may not have been corrected. If FTU-R transmits signal after a long inactivity, the FTU-O receiver will experience the same amount of timing offset Tos but with an opposite sign. To correct for the accumulated timing offset at the US direction the same method described above may be implemented at FTU-O receiver after transmitting multiple pilot tones in US direction. However, doing so may not correct for the accumulated phase offset of the crosstalk channels. Note that FTU-R modems may not be collocated and may be from different vendors with different oscillator accuracy and jitter. Therefore, without a physical timing correction, US FEXT channels among various lines may change after a long inactivity period. If timing offsets are not corrected sufficiently, US vectoring and FEXT cancellation may collapse. FEXT channels may have to be re-estimated before a data transmission in the US can resume, which may be costly in terms of time and performance.
When the US signal is transmitted with a timing offset, both the direct channel and FEXT created to other lines will experience this offset, therefore relative phase between them is unchanged. If the Tos is smaller than one sample and canceller is placed prior to the FDQs (as shown in
Disclosed herein are systems, methods, and apparatuses for timing offset correction in TDD vectored systems. Timing offset estimates for both FTU-R transmitters and receivers may be derived from pilot tones received on the DS in FTU-R receivers after long periods of inactivity in TDD systems. Timing offset estimates may be used in FTU-R transmitters and receivers to correct transmitter and received signals' phase, respectively, with respect to timing offset. Methods are proposed to correct for the accumulated phase offset at each FTU-R transmitter that may keep the US FEXT channels essentially unchanged after a long period of inactivity in a TDD frame. Timing offset correction on US signals may be implemented in FTU-R transmitters, rather than in the FTU-O receivers. If all FTU-Rs implement timing offset correction in their transmitters, a US precoder matrix may remain intact and the FTU-O receivers may not need to make changes to received symbol frame boundaries, frequency-domain equalizers, or crosstalk canceller coefficients.
That is, there may be a different channel matrix for each tone, and there may be different channel matrices for the DS FEXT channel as seen at the xTU-Rs and for the US FEXT channel as seen at the xTU-Os. The solid lines in
Vectoring is a technique that may synchronize a plurality of copper-pairs within a cable to facilitate crosstalk mitigation/cancellation. G.fast may comprise a procedure to estimate a channel matrix and perform vectoring. In one embodiment, the channel matrix H may be used in precoding for the DS direction. In another embodiment, the channel matrix H may be used in cancellation for the US direction. A person having ordinary skill in the art is skilled in methods for estimating the channel matrix H.
In the US direction, a channel matrix may be extracted for each US tone. The channel matrix may be used in a crosstalk cancellation module (or crosstalk canceller) 520 in an FTU-O receiver to cancel or mitigate FEXT in the US. As understood by a person of ordinary skill in the art, each US transmitter at a customer premises, i.e., at each xTU-R, may comprise a symbol mapper and an IFFT module as shown in
Vectoring maybe more challenging for systems, such as G.fast, that may use a TDD duplexing method and a long inactivity described earlier that can cause timing synchronization problems. While the FTU-O transmitters are collocated and may use the same clock to drive their transmitters and are therefore synchronized, the FTU-R transmitters are not collocated and their oscillators may experience different timing drift due to inactivity that has to be corrected at each transmitter to maintain US channel matrix complex-valued components. So long as the inactivity period is short there may be no problem, but a problem may arise when the inactivity period becomes long. After a long inactivity period, if multiple pilot tones are transmitted in DS, the timing offset Tos can be estimated as described herein. The estimated timing drift Tos value at FTU-R can be used to correct for the timing offset of the received signal as described herein. The same timing offset Tos can be used to correct for the timing offset of the transmitted signal at each FTU-R transmitter. By doing so the US channel matrix from FTU-O receivers' point of view is maintained. Note that if the timing offset is not corrected at each FTU-R transmitter and instead each FTU-O estimates the timing offset at its receiver and corrects for its own received signal timing offset, the US direct channel may be maintained. However, the US FEXT channel may not be maintained and have to be updated which requires a long time and special procedures. Therefore, it may be beneficial to correct for the timing offset at FTU-R transmitters. Note that from the moment that Tos is specified until the timing offset is corrected for a transmitted signal, there should not be a long elapsed time. Otherwise, the specified Tos value may not be valid. For example, the usage profile of channel 2 in
Table 1 includes data on accumulated timing offset (drift) in samples for different inactivity periods in a TDD system and different frequency offsets between local and remote oscillators. In the case of G.fast, the local and remote oscillators may reside at FTU-O and FTU-R, respectively. The symbol period corresponds to the example described in paragraph 49 and is 20.531 ps. Note that by tightening the oscillator design specs at FTU-O and FTU-R thereby keeping the frequency offset spec to a very small value, such as 0.001 PPM, the accumulated timing drift may be reduced even when there is large inactivity. However, a frequency offset much smaller than 0.1 PPM may not be practical. The timing drift may therefore be substantial for even relatively small inactivity periods. A period of inactivity may be determined as to be too long for loop timing maintenance based on a combination of PPM, number of tones, and constellation size. We showed in
The slope of the phase response can be determined using conventional signal processing techniques, such as a moving average technique. In one embodiment, after a period of inactivity, a reference symbol comprising a plurality of pilot tones may be transmitted from the FTU-O to an FTU-R. As understood by a person having ordinary skill in the art, the slope of the phase response can be used to determine the timing offset Tos. Below are equations that present one technique for determining the timing offset.
where D is timing offset (delay) in seconds, T0 is the sampling period in seconds, f0 is sampling frequency in Hz, “FT” stands for Fourier Transform, X(f) is the reference symbol in frequency domain, Y(f) is the received symbol, and Re(z) and Im(z) are real and imaginary parts of z, respectively. The equations may be evaluated at different values of frequency f corresponding to the pilot tones, and the Fourier transform may be implemented as a FFT. In equation (1), X(f) represents the FFT of a reference symbol x(t). In equation (2), the FFT of the received symbol x(t-D) is computed, where D is the timing offset (delay) in seconds.
The fractional part of the timing offset may be alternatively corrected on the digital data samples inside an ADC buffer using interpolation methods. However, this method may be more computationally intensive (i.e., may require more processing). In this case, no FDQ coefficient change may be needed. For timing offset correction using interpolation method and interpolation techniques, see Gabriel Watkins, “Optimal Farrows Coefficients for Symbol Timing Recovery,” IEEE Communications Letters, September 2001, which is hereby incorporated by reference as if reproduced in its entirety.
The timing offset may be corrected for the upstream at a corresponding FTU-O receiver in a manner similar to the timing offset correction at an FTU-R receiver. While this method may work for each individual received signal, it may not be able to correct for upstream FEXT offset created among different lines due to different FTU-R's having different offset values. To maintain the relative phase of the FEXT and direct channels of the vectored group in an US direction, the timing offset may be corrected in an US direction at FTU-R transmitters rather than in FTU-O receivers.
Once the timing offset is corrected according to the above rules at each FTU-R transmitter output, there may be no need to correct for any more timing offset at the corresponding receivers of the FTU-Os. The timing offset correction in flowchart 1100 may maintain the relative phase of the US channel matrix if performed in each FTU-R.
Alternatively, the fractional part of the timing offset may be corrected on the digital data samples inside the DAC buffer using interpolation methods. However, this method may be more costly in terms of processing. In this case, no multiplication of IFFT input by the above phase function may be needed. For timing offset correction using interpolation method and interpolation techniques please see Gabriel Watkins, “Optimal Farrows Coefficients for Symbol Timing Recovery,” IEEE Communications Letters, September 2001.
The RX-DSP 1260 may be configured to perform an FFT, crosstalk cancellation, frequency domain equalization, and symbol demapping, as shown in
The processor 1330 may be implemented as one or more CPU chips, cores (e.g., a multi-core processor), field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and/or digital signal processors (DSPs), and/or may be part of one or more ASICs. The processor 1330 may include the receiver logic (e.g., RX-DSP 1332) for demodulating a DMT signal (including FFT and frequency-domain equalization as shown in
The memory 1340 may comprise a combination of secondary storage, read-only memory (ROM), and/or random access memory (RAM). The secondary storage is typically comprised of one or more disk drives or tape drives and may be used for non-volatile storage of data and as an over-flow data storage device if the RAM is not large enough to hold all working data. Secondary storage may be used to store programs that are loaded into RAM when such programs are selected for execution. The ROM is used to store instructions and perhaps data that are read during program execution. ROM is a non-volatile memory device that typically has a small memory capacity relative to the larger memory capacity of secondary storage. The RAM is used to store volatile data and perhaps to store instructions. Access to both ROM and RAM is typically faster than to secondary storage. Data or program instructions stored in the memory 1340 may be loaded into processor 1330 to convert a general-purpose processor into a special-purpose processor for implementing the schemes described herein.
It is understood that by programming and/or loading executable instructions onto transceiver 1300, at least one of the processor 1330 and/or the memory 1340 are changed, transforming the transceiver 1300 in part into a particular machine or apparatus, e.g., DSL modem, having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an ASIC, because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an ASIC that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.
The systems, methods, and apparatuses for loop timing reacquisition after it is lost due to long inactivity; i.e., timing correction in downstream reception and timing correction in upstream transmission for a TDD vectored system, may provide synchronized timing between multiple transceivers. The timing offset between FTU-O and FTU-R clocks may be dynamically estimated after a long inactivity period and corrected both for the received and transmitted signals at an FTU-R. A method of timing offset correction comprises frame boundary alignment for an integer part of the timing offset and phase correction in frequency domain, or interpolation method in time domain, for a fractional part of timing offset.
At least one embodiment is disclosed and variations, combinations, and/or modifications of the embodiment(s) and/or features of the embodiment(s) made by a person having ordinary skill in the art are within the scope of the disclosure. Alternative embodiments that result from combining, integrating, and/or omitting features of the embodiment(s) are also within the scope of the disclosure. Where numerical ranges or limitations are expressly stated, such express ranges or limitations should be understood to include iterative ranges or limitations of like magnitude falling within the expressly stated ranges or limitations (e.g., from about 1 to about 10 includes, 2, 5, 4, etc.; greater than 0.10 includes 0.11, 0.12, 0.15, etc.). For example, whenever a numerical range with a lower limit, R1, and an upper limit, Ru, is disclosed, any number falling within the range is specifically disclosed. In particular, the following numbers within the range are specifically disclosed: R=R1+k*(Ru−R1), wherein k is a variable ranging from 1 percent to 100 percent with a 1 percent increment, i.e., k is 1 percent, 2 percent, 5 percent, 4 percent, 5 percent, . . . , 50 percent, 51 percent, 52 percent, . . . , 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent. Moreover, any numerical range defined by two R numbers as defined in the above is also specifically disclosed. The use of the term about means ±10% of the subsequent number, unless otherwise stated. Use of the term “optionally” with respect to any element of a claim means that the element is required, or alternatively, the element is not required, both alternatives being within the scope of the claim. Use of broader terms such as comprises, includes, and having should be understood to provide support for narrower terms such as consisting of, consisting essentially of, and comprised substantially of Accordingly, the scope of protection is not limited by the description set out above but is defined by the claims that follow, that scope including all equivalents of the subject matter of the claims. Each and every claim is incorporated as further disclosure into the specification and the claims are embodiment(s) of the present disclosure. The discussion of a reference in the disclosure is not an admission that it is prior art, especially any reference that has a publication date after the priority date of this application. The disclosure of all patents, patent applications, and publications cited in the disclosure are hereby incorporated by reference, to the extent that they provide exemplary, procedural, or other details supplementary to the disclosure.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods might be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.
In addition, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
The present application claims priority to U.S. Provisional Patent Application No. 61/735,118 filed Dec. 10, 2012 by Amir H. Fazlollahi and Haixiang Liang and entitled “Timing Offset Correction In Upstream Transmission For A TDD Vectored System”, which is incorporated herein by reference as if reproduced in its entirety.
Number | Date | Country | |
---|---|---|---|
61735118 | Dec 2012 | US |