Impulse Noise Management

US20080232444A1Inactive Publication Date: 2008-09-25AWARE INC
18 Cites 52 Cited by

Patent Information

Authority / Receiving Office
US · United States
Current Assignee / Owner
Publication Date
2008-09-25
Estimated Expiration
Not applicable · inactive patent

Smart Images

  • Figure 1
    Figure 1
  • Figure 2
    Figure 2
  • Figure 3
    Figure 3
Patent Text Reader

Abstract

Evaluation of the impact of impulse noise on a communication system can be utilized to determine how the system should be configured to adapt to impulse noise events. Moreover, the system allows for information regarding impulse noise events, such as length of the event, repetition period of the event and timing of the event, to be collected and forwarded to a destination. The adaptation can be performed during one or more of Showtime and initialization, and can be initiated and determined at either one or more of a transmitter and a receiver.
Need to check novelty before this filing date? Find Prior Art

Description

RELATED APPLICATION DATA

[0001] This application claims the benefit of and priority under 35 U.S.C. §119(e) to U.S. Provisional Application No. 60 / 549,804, entitled “On-Line Impulse Noise Protection (INP) Adaptation,” filed Mar. 3, 2004, and U.S. Provisional Application No. 60 / 555,982, entitled “Impulse Noise Protection (INP) Training,” filed Mar. 24, 2004, both of which are incorporated herein by reference in their entirety.BACKGROUND

[0002] 1. Field of the Invention

[0003] This invention generally relates to communication systems. In particular, an exemplary aspect of this invention relates to impulse noise protection adaptation. Another exemplary aspect of this invention relates to impulse noise length and period determination and use thereof for impulse noise protection adaptation.

[0004] 2. Description of Related Art

[0005] Communications systems often operate in environments that produce impulse noise. Impulse noise is a short-term burst of noise that is higher than the normal noise tha...

Examples

example 1

On-Line INP Adaptation FIP Setting

[0079]This section describes an example of FIP settings for On-Line INP adaptation for DSL. In this example only the number of information bytes in a codeword (K) and the number of parity bytes in a codeword (R) are updated on-line. The Codeword Size (N) and Interleaver Depth (D) are not changed. This means that the latency (and interleaver memory size) and the line rate are not modified on-line. Since N=K+R this places restrictions on the allowed values for K and R.

1st Setting—{Approximate User Data Rate=3.968 Mbps, Line Rate=4.096 Mbps, N=128, K=124, R=4, S=1, D=64, Latency=16 msec, INP=1}

2nd Setting—{Approximate User Data Rate=3.840 Mbps, Line Rate=4.096 Mbps, N=128, K=120, R=8, S=1, D=64, Latency=16 msec, INP=2}

3nd Setting—{Approximate User Data Rate=3.584 Mbps, Line Rate=4.096 Mbps, N=128, K=112, R=16, S=1, D=64, Latency=16 msec, INP=4}

[0080]The On-line INP adaptation process is restricted to only modify the number of information bytes in a cod...

example 2

On-Line INP Adaptation FIP Setting

[0081]This section describes an example of FIP settings for On-Line INP adaptation for DSL. In this example only the Codeword Size (N) and the number of parity bytes in a codeword (R) are updated on line. The number of information bytes in a codeword (K) and Interleaver Depth (D) are not changed and therefore the user data rate does not change. This means that the latency (and interleaver memory size) and the line rate are modified on-line. Since N=K+R this places restrictions on the allowed values for K and R.

1st Setting—{Approximate User Data Rate=3.968 Mbps, Line Rate=4.096 Mbps, N=128, K=124, R=4, S=1, D=64, Latency=16 msec, INP=1}

2nd Setting—{Approximate User Data Rate=3.968 Mbps, Line Rate=4.224 Mbps, N=132, K=124, R=8, S=1, D=64, Latency=16 msec, INP=2}

3nd Setting—{Approximate User Data Rate=3.968 Mbps, Line Rate=4.480 N=128, K=124, R=16, S=1, D=64, Latency=16 msec, INP=4}

[0082]In this example the Line Rate is modified on-line. For this reaso...