US20080232444A1 - Impulse Noise Management - Google Patents
Impulse Noise Management Download PDFInfo
- Publication number
- US20080232444A1 US20080232444A1 US10/597,482 US59748205A US2008232444A1 US 20080232444 A1 US20080232444 A1 US 20080232444A1 US 59748205 A US59748205 A US 59748205A US 2008232444 A1 US2008232444 A1 US 2008232444A1
- Authority
- US
- United States
- Prior art keywords
- impulse noise
- length
- fip
- setting
- inp
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B15/00—Suppression or limitation of noise or interference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
- H04L1/0025—Transmission of mode-switching indication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0075—Transmission of coding parameters to receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0071—Use of interleaving
Definitions
- This invention generally relates to communication systems.
- 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.
- Impulse noise is a short-term burst of noise that is higher than the normal noise that typically exists in a communication channel.
- DSL systems operate on telephone lines and experience impulse noise from many external sources including telephones, AM radio, HAM radio, other DSL services on the same line or in the same bundle, other equipment in the home, etc.
- FEC Forward Error Correction
- Standard initialization procedures in ADSL and VDSL systems are designed to optimize performance (data rate/reach) in the presence “stationary” crosstalk or noise.
- Impulse noise protection is handled with interleaving and FEC, but the current xDSL procedure at least does not provide specific states to enable training for the selection of the appropriate interleaving and FEC parameters.
- SNR Signal to Noise Ratio
- INP 1 ⁇ 2*( S*D )* R/N
- Latency (or delay) S*D/ 4
- N is the codeword size in bytes
- R is the number of parity (or redundancy) bytes in a codeword
- D is the interleaver depth in number of codewords
- L is the number of bits in a DMT symbol.
- DSL systems such as the one defined in ADSL G.992.x or VDSL G.993.x
- EEC and Interleaving Parameters characterized by the set of parameters (N, K, R, D).
- BECC Burst Error Correction Capability
- the proposal further recommends that the higher INP values are achieved by increasing the amount of FEC redundancy while keeping the same system latency and the same interleaver memory at the expense of user data rate or excess margin. Since, on phone lines without excess margin, there is clearly a trade-off between high impulse noise protection values and user data rate, it would be advantageous to try to maximize the user data rate by finding the minimum impulse noise protection value that can provide adequate impulse noise protection.
- the current technique includes the steps of an operator, or service provider, configuring the ADSL connection with a specific noise protection value, the ADSL connection is initialized and the transceivers enter into steady state data transmission (i.e., Showtime), and if the connection is stable, i.e., error-free, then the service is acceptable and the process ends. If there are bit errors, then the process is repeated with the operator, or service provider, configuring the ADSL connection with another specific INP value.
- the related systems do not have the ability to actually measure the length or repetition period of impulse noise which can both be used to determine an appropriate impulse noise protection setting.
- Exemplary aspects of this invention relate to determining the impact of impulse noise on a communication system and the capability to determine how the system should be configured to handle the impulse noise event.
- An exemplary aspect of this invention determines the impact of impulse noise by transmitting and receiving using a plurality of different FEC and interleaving parameter settings. For each FEC and Interleaving Parameter (FIP) setting, the received signal quality is determined by, for example, detecting if there are bit errors after the receiver performs the FEC decoding and deinterleaving. Based on this, the appropriate FIP setting is selected and used for transmission and reception.
- FIP Interleaving Parameter
- a plurality of FIP settings can be used for transmission and reception.
- the system can transition from one FIP setting to another FIP setting without going through the startup initialization procedure such as the startup initialization sequence utilized in traditional xDSL systems.
- the first FIP setting has less FEC parity (overhead) which results in a higher information (net) data rate for the user during Showtime. This is also illustrated by the fact that K, the number of information bytes per code word, is higher for the first FIP setting.
- the receiver detects whether there are bit errors after the decoding and deinterleaving process.
- This detection can be done by, for example, by performing a cyclic redundancy check (CRC) after the decoding and deinterleaving process is complete as defined in the ITU standard G.992.x.
- CRC cyclic redundancy check
- the CRC is a well-known method for detecting bit errors. Since impulse noise occurs at random times, this system can operate using a particular FIP setting for a period of time that is sufficient to encounter the impulse noise. In the simple example illustrated above, only the K and R values were modified. It should be appreciated however, that the systems and methods of this invention are not limited thereto but rather can be extended to include the modification of any one or more FIP parameter(s).
- the process of determining the impact of impulse noise by transmitting and receiving using a plurality of FIP settings can be done while in steady-state transmission, i.e., Showtime for DSL systems, when user information bits are being transmitted.
- the process of determining the impact of impulse noise by transmitting and receiving using a plurality of FIP settings can be done during a special impulse noise training period during which the system is not actually transmitting user data.
- the standard xDSL procedure is modified to include the capability of measuring the effectiveness of a chosen impulse noise protection (INP) setting during initialization and having receiver-controlled updates of transmission parameters that control the INP setting, e.g., FEC parameters and interleaving parameters, during initialization.
- INP impulse noise protection
- a new initialization state is included in the xDSL initialization procedure that provides the capability to measure the effectiveness of the current INP settings.
- the new initialization state will be referred to as the INPTraining state and it can, for example, follow the exchange of the Showtime transmission parameters such as the bi/gi table, trellis coding, tone reordering, FEC/interleaving parameters, etc.
- Showtime steady-state transmission during which user information is transmitted is known as “Showtime” in XDSL systems and that standard ITU G.992.3 ADSL systems and ITU VDSL G.993.3 systems include an exchange phase in initialization during which the Showtime parameters are exchanged, see, for example, G.992.3 and G.993.1.
- the transceivers transmit and receive using at least one of the standard Showtime functions using the Showtime parameters, e.g., bi/gi table, FEC/interleaving parameters, etc., that are exchanged during the previous exchange phase.
- Showtime PMD functions e.g., bi/gi table, trellis coding, tone reordering, etc.
- PMS-TC functions such as framing and FEC/interleaving
- TPS-TC can transmit idle ATM cells, HDLC flags, or 64/65 idle packets depending on the TPS-TC type.
- the CRC, the FEC, the TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the IP setting is adequate for the current impulse noise conditions on the line.
- the receiver can also use these receiver functions to automatically and dynamically determine what the correct INP setting should be. If the current INP setting is not adequate, a new set of Showtime transmission parameters can be exchanged and the process repeated by reentering the INPTraining state using the newly exchanged Showtime transmission parameters. If, on the other hand, the current INP setting is adequate, the transceivers can enter into Showtime.
- An exemplary advantage associated with this aspect of the invention is that the receiver can measure the effectiveness of the current INP setting and can make updates to the INP setting based on these measurements during initialization. This is important because the receiver generally has the most knowledge of channel conditions, receiver functionality, and processing capability. In general, the receiver has the best capability to make the necessary trade offs between data rate, latency, excess margin, FEC redundancy, coding gain, and the like. Current related ADSL systems have the operator servicing lines that are experiencing high impulse noise by trying various INP settings in an attempt to find an error-free operating mode. However, since the operator is not capable of making the receiver trade offs stated above, such as the data rate, latency, and the like, the process will often lead to a sub-optimum result.
- Another exemplary aspect of this invention relates to determining the length and/or repetition period of impulse noise events in order to select an appropriate INP setting.
- the transceivers can transmit and receive using at least one of the standard Showtime functions and parameters such as the bi/gi table, FEC/interleaving parameters, and the like.
- These functions include the Showtime PMD functions, such as the bi/gi table, trellis coding, tone reordering and the like, PMS-TC functions (such as framing and FEC interleaving) and TPS-TC functions.
- the TPS-TC may transmit ATM cells, HDLC packets, or 64/65 packets depending on, for example, the TPS-TC type.
- the CRC, the FEC, the TPS-TC error detection capabilities, and other receiver functions can be used to determine the length and the period of the impulse noise and whether an INP setting is adequate for the current impulse noise conditions on the line.
- the receiver can determine the length of an impulse noise event.
- the length of impulse noise events can be determined in a number of ways. For example, they can be determined as:
- the FEC correction capability and interleaving is turned off when trying to determine the length of the impulse noise.
- the exemplary techniques discussed herein that are used to determine the length of the impulse event can also be extended to determining the repetition period of the impulse noise event, i.e., how often is impulse noise occurring.
- the repetition period can be important, because the period has an effect on the FIP setting that is used. For example, if the interleaving spreads an impulse noise event over a period of time that exceeds the impulse period, then the interleaver could combine multiple impulse noise events together. As a result, the FEC correction capability may have to be increased.
- the receiver can first detect the impulse noise event as discussed above and then determine how often the impulse noise events occur. For example, periodic impulse noise due to AC power lines occurs at a 120 Hz reception rate, or approximately every 8 ms.
- the receiver can attempt to determine the maximum impulse noise length. This involves measuring several impulse noise events and determining the impulse noise event with the maximum length. In practice, it is likely that the impulse noise will have varying length and it is important that the FEC/interleaving settings be configured to handle the maximum, e.g., worst case, impulse noise event.
- this information can be sent to the transmitting modem.
- the receiving modem such as a Customer-Premises (CPE) modem determines the (maximum) length of the impulse and/or the repetition period of the impulse
- the CPE modem could send the information to a Central Office (CO) modem in a message.
- the length of the impulse length event can be defined and specified in the message in terms of time, received bits, ATM cells, 64/65 packets, DMT symbols, or the like.
- the CO modem could then, for example, provide this information to the CO-MIB, which is the management interface that is used by the operator or service provider to configure the modems.
- the operator may configure the modems to a different INP value, data rate, latency, or the like.
- This process could also be automated such that the message received by the CO modem allows automatic reconfiguration to adjust, for example, INP values, data rate, latency, or the like.
- the exemplary aspects of the invention that are used to determine the length and/or repetition period of the impulse noise event can be performed during initialization and/or Showtime.
- the method can perform during an INPTraining state such as the one described herein.
- the method can be performed, for example, during a Showtime INP adaptation phase as described herein.
- FIG. 1 is a functional block diagram illustrating an exemplary impulse noise adaptation system according to this invention
- FIG. 2 illustrates an exemplary initialization state machine that includes an INPTraining state according to this invention
- FIG. 3 is a flowchart outlining an exemplary method for impulse noise protection adaptation during Showtime according to this invention
- FIG. 4 is a flowchart illustrating an exemplary receiver optimized method for impulse noise protection adaptation according to this invention
- FIG. 5 is a flowchart illustrating an exemplary method for forward error correction synchronization according to this invention.
- FIG. 6 is a flowchart illustrating an exemplary method for flag signal synchronization according to this invention.
- FIG. 7 is a flowchart illustrating an exemplary method for determining impulse noise length and period according to this invention.
- the various components of the system can be located or relocated at distant portions of a distributed network, such as a telecommunications network and/or the Internet, or within a dedicated secure, unsecured and/or encrypted system.
- a distributed network such as a telecommunications network and/or the Internet
- the components of the system can be combined into one or more devices, such as a modem, or collocated on a particular node of a distributed network, such as a telecommunications network.
- the components of the system can be arranged at any location within a distributed network without effecting the operation of the system.
- the various components can be located in a central office (CO or ATU-C) modem, a customer premises modem (CPE or ATU-R), or some combination thereof.
- CO central office
- CPE customer premises modem
- the functionality of the system could be distributed between one or more of the modems and an associated computing device.
- the various links, including communications link 20 , connecting the elements can be wired or wireless links, or any combination thereof or any other known or later-developed element(s) that is capable of supplying and/or communicating data to and from the connected elements.
- module as used herein can refer to any known or later-developed hardware, software, or combination of hardware and software that is capable of performing the functionality associated with that element.
- the term “transmitter” has the same meaning as the term “transmitting modem” of “transmitting transceiver” and the term “receiver” has the same meaning as “receiving modem” or “receiving transceiver.”
- FIG. 1 illustrates an exemplary embodiment of an impulse noise adaptation system 100 according to an exemplary embodiment of this invention.
- the system 100 comprises a receiving modem 200 and a transmitting modem 300 .
- the exemplary receiving modem 200 comprises a decoder/deinterleaver 210 , a bit error rate (BER) detection module 220 , a forward error correction and interleaving parameter (FIP) module 230 , an impulse noise length determination module 240 , an impulse noise period determination module 250 , an impulse noise parameter management module 260 , an impulse noise protection adaptation module 270 , a synchronization module 280 , a message module 290 and a controller and memory (not shown) all interconnected by a link 5 .
- the exemplary transmitting modem 300 comprises a management module 310 , a synchronization module 320 , a message module 330 , and may optionally include an impulse noise parameter management module 340 .
- the exemplary communication system adapts the impulse noise parameters on-line by operating using a series of different FIP settings. For each FIP setting, the system can dynamically determine if the appropriate amount of impulse noise protection is being provided. Based on these determinations, the system can select a particular FIP setting for regular, i.e., Showtime, operation. As will be discussed in greater-detail hereinafter, this impulse noise protection adaptation can be performed during Showtime and/or during initialization.
- Impulse noise protection adaptation during Showtime includes the following exemplary steps.
- the DSL system i.e., the transmitting and receiving modems, completes regular initialization and commences transmission and reception using a first FIP setting.
- this first FIP setting is selected by the receiver 200 and is based on the minimum/maximum data rate, maximum latency, and minimum INP parameters as configured by, for example, the service provider via the management module 310 .
- G.992.3 A detailed explanation of this procedure can be seen in G.992.3.
- the system will use this first FIP setting for a period of time T 1 .
- the receiver 200 detects if bit errors have occurred using this first FIP setting for the decoding and deinterleaving performed by the decoder/deinterleaver 210 .
- the receiver 200 can use a CRC to detect bit errors. If there are no bit errors, then the current INP setting is adequate and there is no need to modify the INP setting and Showtime communication can continue as normal.
- bit errors have been detected by the BER detection module 220
- an adjustment to the INP setting may be appropriate.
- a service provider, a user, or the system can choose an updated INP setting. Since bit errors have been detected, the INP setting could be increased by an on-line modification to the FIP parameters.
- the transmitter 300 and for example the management module 310 , in response to an indication from the receiver 200 that bit errors have been detected, can send a message to the receiver 200 to initiate a change in the INP settings.
- the receiver 200 in cooperation with the message module 290 , the FIP module 230 , the impulse noise parameter management module 260 and impulse noise protection adaptation module 270 , can return a message to the transmitter 300 that specifies a newly determined FIP setting that satisfies the new INP requirement.
- the transmitter 300 and receiver 200 can then transition to the new INP setting by starting to use the new FIP parameters for transmission and reception, respectively, at a synchronized point in time.
- This synchronization can be done in accordance with a number of exemplary methods that are discussed hereinafter.
- the system 100 Upon synchronization, the system 100 continues communication using the updated FIP settings for a second period of time T 2 . If the receiver detects that bit errors are occurring using this updated FIP setting during the decoding and deinterleaving performed by the decoder/deinterleaver 210 the steps can be repeated with the selection of another updated INP setting. However, if there are no bit errors detected by the receiver 200 during the time period T 2 , then the new INP setting is adequate and there is no need for further change at which point the INP adaptation procedure can end.
- This Showtime-based INP adaptation process can be repeated as many times as necessary until an INP setting is obtained that provides the required impulse noise immunity and/or bit error rate.
- transition between different FIP settings can be accomplished without reinitializing the transceivers using the lengthy standard initialization procedure that is typically used in ADSL and VDSL systems.
- the transition can occur without the standard initialization since the transition between FIP settings can be synchronized between the transmitter and the receiver such that the receiver 200 can determine when to start FEC decoding using the new FIP settings for K and R.
- this transition/can be synchronized using a number of different exemplary methods.
- the transition can also be accomplished without synchronization in which case the receiver 200 will determine when the new FIP settings are used by some alternative means.
- the receiver could determine when the new FIP settings are being used by FEC decoding using both the old and updated FIP settings and determining which one is currently being utilized by the transmitter by determining with which FIP setting the codeword is correct.
- Other receiver functions such as CRCs, ATM HEC errors and the like could also be used.
- This impulse noise protection adaptation procedure can be performed during regular steady-state transmission, i.e., Showtime in ADSL, using actual user data or, for example, idle ATM cells.
- This methodology can also be performed during a special impulse noise training period during which the system is not actually transmitting user data.
- this impulse noise training period could utilize transmitted predefined pseudorandom bit streams or, for example, idle ATM cells or HDLC flags for determining an appropriate INP value.
- the length of the time periods T 1 , T 2 , . . . can be controlled by, for example, the receiving modem 200 .
- the receiving modem 200 could control the length of these time periods by, for example, sending a message that specifies how long the transmitter should transmit using a particular FIP setting.
- This length can be defined, for example, in terms of the number of DMT symbols or the number of FEC codewords.
- a message could indicate that 200 DMT symbols should be sent for all HP settings or 300 FEC code words should be sent for all FIP settings. Alternately, the message can indicate a different number of DMT symbols or FEC code words for each FIP setting.
- This technique could further be used to aid in determining an appropriate INP setting by forwarding a predetermined number of DMT symbols at a first FIP value, followed by a second number of DMT symbols at a second FIP value, and so on.
- the receiver could determine the bit error rate, with the cooperation of the BER detection module 220 , and then forward a message, with the cooperation of the message module 290 , to the transmitter 300 specifying which FIP setting provided the appropriate impulse noise protection.
- the transmitting modem 300 and receiving modem 200 could cooperate such that an optimum impulse noise protection value is converged upon.
- the transmitting modem 300 with the cooperation of the message module 330 , could forward a message to the receiving modem 200 specifying a first INP setting. If there are no bit errors, a message could be sent via the message module 290 to the transmitting modem 300 indicating that there are no bit errors and a lower INP value could be attempted.
- the impulse noise parameter management module 260 and FIP module 230 could then determine an appropriate lower INP setting and forward it to the transmitter 300 .
- a lower INP value is inversely proportional to the user data rate, it is advantageous to optimize the INP value based on detected errors.
- the transmitting modem 300 in cooperation with the message module 330 , could then send another message to the receiving modem 200 indicating that the lower INP value will be transitioned to at which point the procedure repeats itself through detection of bit errors in cooperation with the bit error rate detection module 220 and the decoder/deinterleaver 210 .
- This reduction in the INP parameters can continue until bit errors are detected at which point a message is sent, with the cooperation of the message module 290 , to the transmitting modem 300 indicating a higher INP value is required since bit errors were detected.
- an optimum INP value can be determined and transitioned to by the receiver 300 and transmitter 200 . This procedure could also be used to increase the INP parameters in a similar fashion.
- the length of the time periods T 1 , T 2 , . . . can also be controlled by the transmitter 300 .
- the transmitter 300 could control the length of these time periods, by, for example, sending a message to the receiver 200 that specifies the length of time the transmitter will transmit using a particular FIP setting.
- This length could be defined in terms of the number of DMT symbols or, for example, the number of FEC codewords.
- the exemplary message could indicate that, for example, 200 DMT symbols would be sent for all FIP settings or 300 FEC codewords will be sent for all FIP settings.
- the message could also indicate a different number of DMT symbols or FEC codewords for each FIP setting.
- the message could contain any type of information relating to how long the transmitter will be using a specific FIP setting(s).
- the length of the time periods T 1 , T 2 . . . can also be controlled by, for example, a service provider or a user.
- the service provider could use the knowledge of the nature of the impulse noise, such as how often impulse noise event occurs, to determine the times.
- the length of the time periods could be configured to be any length of time as appropriate.
- the receiving modem 200 can determine the new INP settings.
- the transmitting modem 300 in cooperation with the impulse noise parameter management module 340 could also determine updated INP settings. For example, either modem could continually adapt the INP values as discussed above until no bit errors that are the result of impulse noise are detected by the BER detection module 220 .
- the receiver and transmitter can synchronize the modification of the FEC and interleaving parameters such that the both the transmitter and receiver start using the parameters at the same instant in time.
- This synchronization can be based on, for example, a synchronization using FEC codeword counters or a flag signal.
- the receiver 200 and transmitter 300 can synchronize the change in cooperation with the sync modules 280 and 320 , by counting the FEC codewords from the beginning of Showtime and the transition would occur when a specific FEC codeword counter value that is known by both the transmitter 300 and the receiver 200 is reached.
- the transmitter 300 or receiver 200 in cooperation with the message module 290 and message module 330 , would send a message indicating the FEC codeword count value on which the FIP parameters will be updated.
- the transmitting modem 300 can enter into Showtime and the synchronization module 320 commences counting the number of transmitted FEC codewords.
- the first codeword transmitted has a count value of 0
- the second transmitted codeword has a count value of 1 . . . .
- the counter can optionally be defined as having a finite length, for example, 0 to 1023 (10 bits) such that when the value of 1023 is reached, on the next FEC code word that is transmitted, the counter restarts at the value of 0.
- the receiving modem 200 upon entering Showtime starts a counter in cooperation with the synchronization module 280 that counts the number of received FEC codewords.
- the first received FEC codeword has a count value of 0, the second received FEC codeword to the count value of 1 . . . .
- the synchronization module 280 can have a counter with a finite length, for example 0-1023, such that when the value of 1023 is reached, on the next FEC codeword the counter restarts at 0.
- the receiving modem 200 can send a message, via the message module 290 , to the transmitting modem 300 , and in particular the message module 330 and impulse noise parameter management module 340 .
- the updated FIP setting can alternatively be sent from the transmitting modem to the receiving modem.
- the synchronization module 280 and message module 290 then cooperate to send a message to the transmitting modem 300 specifying the FEC codeword counter value on which the new FIP settings are to be used for transmission and reception.
- the transmitting modem in cooperation with the message module 330 , can send a message to the receiving modem indicating the FEC codeword counter value on which the FIP settings are to be used for transmission and reception.
- the message can indicate that when the code word counter equals 501, the new FIP setting will be used for transmission and reception.
- the synchronization module 220 instructs the transmitting modem 300 to transition to the new FIP settings.
- the synchronization module 280 in the receiving modem 200 counts the FEC codeword that equals the value indicated in the message, the receiving modem 200 transitions to using the new FIP settings for reception.
- Synchronization can also be performed through the use of a flag signal (sync flag).
- a flag signal sekunder flag
- the receiving modem 200 and transmitting modem 300 in cooperation with the synchronization module 280 and synchronization module 320 , synchronize the change in FIP settings using a flag or marker signal that is similar to that used in the ADSL2 G.992.3 ORL protocol. This protocol may be more desirable than using an FEC codeword counter because, for example, it has greater impulse noise immunity.
- the receiver and transmitter would start using updated FEC and interleaving parameters on a pre-defined FEC codeword boundary following the sync flag. For example, while transmitting using a first INP setting, a determination is made by, for example, the BER detection module 220 that a new FIP setting is needed due to the presence of impulse noise on the line. This determination can be performed by the receiving modem, in cooperation with the FIP module 230 , the transmitting modem, a user, a service provider, or the like. The receiving modem 220 , in cooperation with the message module 290 , sends a message to the transmitting modem 300 indicating the new FIP settings to be used for transmission and reception. Alternatively, the transmitting modem, in cooperation with the message module 330 , prepares and sends a message to the receiving modem indicating the updated FIP settings to be used for transmission and reception.
- the transmitting modem then sends a flag or marker signal to the receiving modem 200 indicating that the new FIP settings are to be used on a predetermined number of DMT symbols following the transmission of the flag or marker signal.
- the flag signal could be an inverted sync symbol, or sync FLAG, as used in the ADSL2 G.992.3 OLR protocol.
- the transmitting modem 300 then starts using the new FIP settings for transmission on the predetermined number of DMT symbols following the transmission of the flag or marker signal.
- the receiving modem starts using the new FIP settings for reception once the predetermined number of DMT symbols following the receipt of the flag or marker signal have been received.
- This section describes an example of FIP settings for On-Line INP adaptation for DSL.
- K codeword
- R parity bytes in a codeword
- N Codeword Size
- D Interleaver Depth
- the On-line INP adaptation process is restricted to only modify the number of information bytes in a codeword (K) and the number of parity bytes in a codeword (R).
- This section describes an example of FIP settings for On-Line INP adaptation for DSL.
- N Codeword Size
- R number of parity bytes in a codeword
- D Interleaver Depth
- FIG. 2 illustrates an exemplary modified initialization state machine that includes the INPTraining state prior to Showtime.
- This state machine is based on the VDSL G.993.1 ITU standard.
- VTU-O is the VDSL Transceiver Unit at the Optical Network Unit (ONU)
- VTU-R is the VDSL Transceiver Unit at the Remote terminal.
- the Initialization state machine in FIG. 2 is an example of how INPTraining states could be included in a modified VDSL initialization procedure. While exemplary FIG. 1 includes the Training state at a specific time in the initialization sequence, the INPTraining state can be included at any time during initialization provided that it is preceded by a state during which Showtime parameters are exchanged between the transceivers.
- the VTU-O transmitter transmits DMT Symbols using the standard PMD, PMS-TC and TPS-TC SHOWTIME functions with parameters exchanged during the previous Exchange Phase.
- the TPS-TC transmits idle ATM cells, HDLC flags or 64/65 idle packets. SOC is inactive during this state.
- This state is used by the VTU-R to determine the correct DS INP setting based on Impulse Noise conditions on the line.
- the downstream CRC, FEC error detection, TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the INP setting is adequate.
- the receiver can also use these receiver functions to determine the correct INP setting.
- the VTU-R determines that the current INP setting is not adequate, the VTU-R transmits the R-P-ISYNCHRO2 signal to indicate the need to transition back to the Exchange Phase in order to exchange new transmission parameters.
- the VTU-R determines that the current INP setting is not adequate, the VTU-R transmits the R-P-SYNCHRO2 signal to indicate that it is OK to transition to Showtime with the current transmission parameters.
- the VTU-R transmitter transmits DMT Symbols using the standard PMD, PMS-TC and TPS-TC Showtime functions with parameters exchanged during the previous Exchange Phase.
- the TPS-TC transmits idle ATM cells, HDLS flags or 64/65 idle packets. SOC is inactive during this state.
- This state is used by the VTU-O to determine the correct US INP setting based on Impulse Noise conditions on the line.
- the upstream (US) CRC, FEC error detection, TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the INP setting is adequate.
- the receiver can also use these receiver functions to determine the correct INP setting.
- the VTU-O determines that the current INP setting is not adequate, the VTU-O transmits the O-P-ISYNCHRO2 signal to indicate the need to transition back to the Exchange Phase in order to exchange new transmission parameters.
- the VTU-O determines that the current INP setting is not adequate, the VTU-O transmits the O-P-SYNCHRO2 signal to indicate that it is OK to transition to Showtime with the current transmission parameters.
- the O-P-SYNCHRO2 is the same as defined in the current VDSL 1 .
- the VTU-O transmitter enters Showtime after transmitting the O-P-SYNCHRO2 signal.
- the VTU-O waits for receipt of the R-P-SYNCHRO2 or R-P-ISYNCHRO2. If the VTU-O receives the R-P-SYNCHRO2 it continues in Showtime. If the VTU-O receives the R-P-ISYNCHRO2, the VTU-O transmitter transitions back to the beginning of the O-P-MEDLEY state.
- the O-P-SYNCHRO2 is the same as defined in the current VDSL 1 .
- the VTU-R transmitter enters Showtime after transmitting the R-P-SYNCHRO2 signal.
- the VTU-R waits for receipt of the O-P-SYNCHRO2 or O-P-ISYNCHRO2. If the VTU-R receives the O-P-SYNCHRO2 it continues in Showtime. If the VTU-R receives the O-P-ISYNCHRO2, the VTU-R transmitter transitions back to the beginning of the R-P-MEDLEY state.
- the O-P-ISYNCHRO2 is phase-inverted version of the O-P-SYNCHRO2, i.e., a subcarrier-by-subcarrier 180 degrees phase reversal.
- the VTU-O transmitter transitions to the beginning of the O-P-MEDLEY state after transmitting the O-P-ISYNCHRO2 signal.
- the R-P-ISYNCHRO2 is phase-inverted version of the R-P-SYNCHRO2, i.e., a subcarrier-by-subcarrier 180 degrees phase reversal.
- the VTU-R transmitter transitions to the beginning of the R-P-MEDLEY state after transmitting the R-P-ISYNCHRO2 signal
- the receiver can measure the efficiency of the plurality of INP settings without completing a new initialization procedure such as is used in ADSL and VDSL systems.
- the length of the time of the O-P-INPTrain and R-P-INPTrain states can be controlled by the VTU-R and VTU-O respectively. In this way the receivers have adequate time to determine if the current INP setting is correct.
- the VTU-O can transmit a message to the VTU-R indicating the minimum length of the R-P-INPTrain state.
- the VTU-R can transmit a message to the VTU-O indicating the minimum length of the O-P-INPTrain state.
- the message could indicate that a minimum of 20000 DMT symbols should be sent during the O-P-INPTrain state.
- the length of the time of the O-P-INPTrain and R-P-INPTrain states could be set by the DSL service provider in order to make sure that the initialization does not take too long or because the service provider may have some knowledge of the statistics of the impulse noise which require setting the length of the INPTrain states.
- a message could be sent from the VTU-O to the VTU-R indicating the minimum and/or maximum length of the O-P-INPTrain and/or the R-P-INPTrain states.
- the message could indicate that a minimum of 20000 DMT symbols should be sent during the R-P-INPTrain state.
- the message could indicate that a maximum of 40000 DMT symbols should be sent during the R-P-INPTrain state.
- the length of the time of the O-P-INPTrain and R-P-INPTrain states could also be controlled by the VTU-O and VTU-R respectively.
- the transmitters will have control of the state lengths.
- the VTU-R can transmit a message to the VTU-O indicating the minimum length of the R-P-INPTrain state.
- the VTU-O can transmit a message to the VTU-R indicating the minimum length of the O-P-INPTrain state.
- the message could indicate that a minimum of 20000 DMT symbols should be sent during the O-P-INPTrain state.
- another exemplary aspect of this invention relates to determining the length and/or repetition period of impulse noise events in order to select an appropriate INP setting.
- the INP length can be determined using any one of a plurality of metrics.
- the INP length can be determined based on one or more of:
- the determination of the IP length with the number of received bits that are affected by impulse noise can be performed in accordance with the following procedure.
- the transmitting modem 300 transmits data using at least one of the Showtime functions.
- at least the bit allocation table is used.
- the trellis coder, framer, and TPS-TC functions may also be used.
- the interleaving and FEC may also be used.
- the receiving modem 200 receives data using at least one of the Showtime functions, such as the bit allocation table as discussed above.
- the trellis coder, framer, TPS-TC and/or interleaving and FEC can be used.
- the transmitter 300 then transmits a predefined bit pattern that is used for determining or measuring the impulse noise length based on detected erroneous bits.
- the receiving modem 200 compares, with the assistance of the impulse noise length determination module 240 , the predefined bit pattern to the received bit pattern in order to detect bit errors. Since impulse noise events typically cause a burst of errors in a bit stream, the receiving modem 200 determines the length of the impulse noise event by detecting and determining the length of the error burst.
- the receiving modem 200 in cooperation with the message module 290 , sends a message to the transmitter 300 that indicates the determined length of the impulse noise.
- the exemplary methodology discussed above can also be used to determine the length of the impulse event using other metrics.
- a predefined bit pattern could be used in the payload of the ATM cells or the 64/65 packets. Idle packets or cells, which carry a predefined pattern, could also be used. In these cases, the receiver would compare the received data to the predefined data to determine the length of the impulse or to determine if an INP setting is adequate.
- the CRC of the ATM cell or 64/65 packet could be used to determine the length of the impulse noise. This would provide a courser measurement of the impulse noise length since it would be an integer number of packets or cells.
- a 700 bit impulse would cause CRC errors in two ATM cells so the length of the impulse noise would be two ATM cells, as opposed to the more precise measurement of 1.64 above.
- a 700 bit impulse would cause CRC errors in two 64/65 packets so the length of the impulse noise would be two packets, as opposed to the more precise measure of 1.35 above.
- a predefined bit pattern could also be used to modulate the carriers in the DMT symbols so that the receiver would know what DMT symbols were transmitted. In this case, the receiver 200 would determine how many DMT symbols were corrupted by comparing the received signal with a known transmitted signal.
- the exemplary techniques used to determine the length of the impulse noise event could also be extended to determine the repetition rate of the impulse noise event in cooperation with the impulse noise period determination module 250 .
- the receiver 200 detects the impulse noise event as discussed above and then determines how often they occur. For example, periodic impulse noise due to AC power lines occur at 120 Hz reception rates or approximately every 8 ms.
- the receiver 200 could, for example, also store information about past impulse noise events and compare detected impulse noise events to historical events.
- the impulse noise period determination module 250 could then determine which events of a similar duration are occurring at what interval. This information could then be used in determining an appropriate INP setting.
- the information can be sent to the transmitting modem.
- the impulse noise period determination module 250 in cooperation with the message module 290 can forward information to the transmitting modem that quantifies this period.
- the transmitting modem 300 could provide this information to, for example, the management module 310 , that would allow, for example, an operator or service provider to configure the modems. For example, based on the period information contained in the message, the operator may configure the modems to different INP values, data rates, latency, or the like.
- the receiver 200 could also test a specific INP setting by detecting how many received bits are errored in a specific time period. For example, if the specific INP setting enables the correction of 100 bits in an 8 msec. time period then the receiver 200 could detect how many bits are errored in a sliding 8 msec. window. If less than 100 bits are detected in error in the 8 ms sliding window, then the IP setting is adequate.
- the receiver could test a specific INP setting by detecting how many received ATM cells, 64/65 packets, DMT symbols, and/or FEC corrections are affected in a specific time period.
- FIG. 3 outlines an exemplary method for performing impulse noise protection adaptation during Showtime according to this invention.
- control begins in step S 300 and continues to step S 310 .
- step S 310 traditional DSL initialization occurs.
- step S 320 Showtime is entered between the two modems using the first FIP setting that was determined during the initialization in step S 310 .
- step S 330 a determination is made whether bit errors are occurring using the first FIP setting. If bit errors are not occurring, control continues to step S 340 where the control sequence ends. Otherwise, control jumps to step S 350 .
- step S 350 a determination is made that an increase of the INP setting is required that requires modification of the FIP parameters.
- step S 360 updated INP parameter is determined and a message forwarded to the receiver specifying the new INP setting. Then, in step S 370 , the receiver forwards to the transmitter updated FIP parameters for the new impulse noise protection requirements. Control then continues to step S 380 .
- step S 380 the transmitter and receiver transition to using the updated INP parameters at a synchronization point.
- step S 390 Showtime operation continues. Control then continues back to step S 330 .
- FIG. 4 outlines an exemplary method for receiver optimized impulse noise protection adaptation during Showtime.
- control begins in step S 400 and continues to step S 410 .
- step S 410 the DSL system completes regular initialization.
- control begins in step S 400 and continues to step S 410 .
- step S 410 the DSL system completes startup initialization and continues into Showtime in step S 420 using a first FIP setting.
- step S 430 a determination is made whether bit errors are occurring using the first FIP setting. If bit errors are not occurring, control continues to step S 440 where the control sequence ends.
- step S 450 control jumps to step S 450 where the receiver increases the impulse noise protection by modifying the FIP parameters.
- step S 460 a synchronization point is determined between the transmitter and receiver, and when the synchronization point is reached both the transmitter and the receiver transition to the updated FIP setting in step S 470 and Showtime communications continue and control returns back to step S 430 .
- FIG. 5 illustrates an exemplary method for synchronization of the modified FEC and interleaving parameters according to this invention.
- control begins in step S 500 and continues to step S 510 .
- step S 510 the transmitter enters Showtime and counts the number of transmitted FEC codewords.
- step S 520 the receiver enters Showtime and counts the number of received FEC codewords.
- step S 530 after a determination is made that an updated FP setting is needed, the receiving modem sends a message to the transmitting modem indicating a new FIP setting that is to be used for transmitting and reception or, alternatively, the transmitting modem sends a message to the receiving modem indicating the new FIP setting to be used for transmission and reception.
- step S 540 the transmitting modem indicating a new FIP setting that is to be used for transmitting and reception.
- step S 540 a message with the FEC codeword counter value on which the new FP values are to be used is exchanged.
- step S 550 a determination is made whether the counter value has been reached at the transmitter. If the counter value has not been reached, the next codeword is counted in step S 560 and control continues back to step S 550 .
- step S 570 the transmitter transitions to the new FIP setting.
- step S 580 a determination is made whether the counter value has been reached at the receiving modem. If the counter value has not been reached, the next received FEC codeword is counted in step S 585 and control continues back to step S 580 . However, when the counter value has been reached in the receiving modem, control jumps to step S 590 where the receiving modem switches to the new FIP value. Control then continues to step S 595 where the modems continue Showtime communication and control continues to step S 597 where the control sequence ends.
- FIG. 6 illustrates an exemplary method of synchronization using a flag signal according to this invention.
- control begins in step S 600 and continues to step S 610 .
- step S 610 the modems enter Showtime using the first FIP parameters.
- step S 620 a message is exchanged indicating the new FIP settings.
- step S 630 the transmitter forwards to the receiver a flag signal indicating when the new FIP settings are to be used.
- step S 640 and at a predefined change time following the transmission of the flag signal, the transmitter begins transmission using the new FP parameters.
- step S 650 at the predefined change time following the reception of the flag signal, the receiver commences reception utilizing the new FIP parameters. Control then continues to step S 660 where Showtime communication continues with the control sequence ending at step S 670 .
- FIG. 7 illustrates an exemplary method of impulse noise length and period determination.
- control begins in step S 700 and continues to step S 710 .
- the transmitter transmits data using at least one Showtime function.
- the receiver receives data using at least one Showtime function.
- the transmitter transmits predefined information to the receiver. Control then continues to step S 740 .
- step S 740 the receiver receives the predefined information from the transmitter.
- step S 750 the receiver compares the received predefined information to the predefined information and determines the differences (i.e., errors) between the two. Then, in step S 760 , and based on the detected errors, the length of the burst error is determined.
- step S 770 a message is forwarded to the transmitter indicating the length of the impulse noise event. Control then continues to step S 780 where a determination is made whether the period of the impulse noise event is also to be determined. If the period is not to be determined, control continues to step S 790 where the control sequence ends. Otherwise, control jumps to step S 800 .
- step S 800 the receiver detects how often the impulse noise events occur. For example, historical information regarding the length and timing of previous impulse noise events can be stored in a memory (not shown). Then, a comparison can be made with the aid of a processor (not shown) to compare an impulse noise event to the historical information to determine the period of repetition (if any) of similar impulse noise events and, for example, a message indicating the period as well as the timing forwarded to, for example, another transceiver, the CO, or in general any destination as appropriate. Thus, in a similar manner, this information can be forwarded in step S 810 to, for example, the transmitter in a message specifying the repetition frequency of the impulse noise event. Control then continues to step S 820 where the control sequence ends.
- the above-described system can be implemented on wired and/or wireless telecommunications device(s), such a modem, a multicarrier modem, a DSL modem, an ADSL modem, an xDSL modem, a VDSL modem, a linecard, test equipment, a multicarrier transceiver, a wired and/or wireless wide/local area network system, a satellite communication system, a modem equipped with diagnostic capabilities, or the like, or on a separate programmed general purpose computer having a communications device.
- wired and/or wireless telecommunications device(s) such a modem, a multicarrier modem, a DSL modem, an ADSL modem, an xDSL modem, a VDSL modem, a linecard, test equipment, a multicarrier transceiver, a wired and/or wireless wide/local area network system, a satellite communication system, a modem equipped with diagnostic capabilities, or the like, or on a separate programmed general
- 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 hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device such as PLD, PLA, FPGA, PAL, modem, transmitter/receiver, or the like.
- a programmable logic device such as PLD, PLA, FPGA, PAL, modem, transmitter/receiver, or the like.
- any device 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 methods, protocols and techniques according to this invention.
- the disclosed methods may be readily implemented in software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms.
- 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, or any means, 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.
- the disclosed methods may be readily implemented in software, that can be stored on a storage medium, and executed on programmed general-purpose computer, 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 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 communications transceiver.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Telephonic Communication Services (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Cable Transmission Systems, Equalization Of Radio And Reduction Of Echo (AREA)
Abstract
Description
- 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.
- 1. Field of the Invention
- 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.
- 2. Description of Related Art
- 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 that typically exists in a communication channel. For example, DSL systems operate on telephone lines and experience impulse noise from many external sources including telephones, AM radio, HAM radio, other DSL services on the same line or in the same bundle, other equipment in the home, etc. It is standard practice for communications systems to use interleaving in combination with Forward Error Correction (FEC) to correct the errors caused by impulse noise. Standard initialization procedures in ADSL and VDSL systems are designed to optimize performance (data rate/reach) in the presence “stationary” crosstalk or noise. Impulse noise protection is handled with interleaving and FEC, but the current xDSL procedure at least does not provide specific states to enable training for the selection of the appropriate interleaving and FEC parameters.
- An exemplary problem associated with traditional communication systems is that they use traditional Signal to Noise Ratio (SNR) measurement techniques to determine the SNR of the channel. These traditional techniques assume that the noise is stationary and does not contain non-stationary components such as impulse noise. The most common method for measuring the SNR is to calculate the mean-square error of the received signal based on a known transmitted signal, which is described in the ADSL series of ITU G.992.x standards and the VDSL series of ITU G.993.x standards, which are incorporated herein by reference in their entirety. These traditional methods for measuring SNR do not correctly measure the impact of impulse noise and do not have the noise capability to determine how the system should be configured to handle impulse noise.
- There has been proposed that there is a need in ADSL and VDSL systems to provide robust error-free performance in the presence of high, real-world impulse noise. A specific proposal recommends that the standard impulse noise protection (IP) values are extended to values of 4, 8, 16 and 32 in order to handle high levels of impulse noise. Impulse noise protection is defined in the ADSL2 Standard G.992.3, which is incorporated herein by reference in its entirety, as the number of impulse noise corrupted DMT symbols that can be corrected by the FEC and interleaving configuration. Specifically, G.992.3 defines the following variables:
-
INP=½*(S*D)*R/N -
S=8*N/L -
Latency (or delay)=S*D/4 -
Line Rate (in kbps)=L*4 - where N is the codeword size in bytes, R is the number of parity (or redundancy) bytes in a codeword, D is the interleaver depth in number of codewords, and L is the number of bits in a DMT symbol.
- If K is the number of information bytes in a codeword then:
-
N=K+R - and the user data rate is approximately equal to:
-
L*4*K/N. - In general, DSL systems (such as the one defined in ADSL G.992.x or VDSL G.993.x) use the EEC and Interleaving Parameters (FIP) characterized by the set of parameters (N, K, R, D). Using these parameters, the Burst Error Correction Capability (BECC) in bytes can be simply calculated as:
-
BECC=D*R/2 bytes - where BECC is defined as the number of consecutive byte errors that can be corrected by the receiver. Note that if the receiver uses more intelligent decoding schemes, such as erasure detection, it is possible to correct even more than D*R/2 bytes. It also follows from above that INP=BECC/L.
- The proposal further recommends that the higher INP values are achieved by increasing the amount of FEC redundancy while keeping the same system latency and the same interleaver memory at the expense of user data rate or excess margin. Since, on phone lines without excess margin, there is clearly a trade-off between high impulse noise protection values and user data rate, it would be advantageous to try to maximize the user data rate by finding the minimum impulse noise protection value that can provide adequate impulse noise protection. The current technique includes the steps of an operator, or service provider, configuring the ADSL connection with a specific noise protection value, the ADSL connection is initialized and the transceivers enter into steady state data transmission (i.e., Showtime), and if the connection is stable, i.e., error-free, then the service is acceptable and the process ends. If there are bit errors, then the process is repeated with the operator, or service provider, configuring the ADSL connection with another specific INP value.
- One exemplary problem with this approach is that it is time consuming and can result in sub-optimum user rates. This is illustrated with reference to the following examples:
- Assume that for a particular DSL connection there is high impulse noise and the required INP is 8. As a result, if the service provider uses a first INP configuration of 2, the DSL connection will not be error free. Therefore, the service provider needs to configure a higher INP value and reinitialize the connection. If a value of 4 is used as a second INP value, it still will not provide adequate impulse noise protection and bit errors will occur. Again, the service provider will need to configure a higher INP value until the correct value of 8 is configured. Clearly, the connection needs to be re-initialized every time there is a new INP configuration chosen and this trial and error technique proves to be very time consuming.
- Assume that for a particular DSL connection there is high-impulse noise and the required INP is 4. As a result, if the service provider uses a first INP configuration of 2, the connection will not be error free. Therefore, the service provider needs to configure a higher INP value and reinitialize the connection. In order to save time and not go through the number of initializations has occurred in Example 1, the service provider simply configures the system to the maximum INP value of 32. Obviously, there will be no bit errors with INP=32 since this connection needs only an INP value of 4. As a result, user data throughput is greatly degraded since the additional FEC redundancy will be three times higher than what is actually needed. For example, if the INP of 4 requires 10 percent FEC redundancy, an INP of 32 requires 40 percent FEC redundancy which results in a 30 percent decrease in user data rate.
- In additional to the above drawbacks, the related systems do not have the ability to actually measure the length or repetition period of impulse noise which can both be used to determine an appropriate impulse noise protection setting.
- Exemplary aspects of this invention relate to determining the impact of impulse noise on a communication system and the capability to determine how the system should be configured to handle the impulse noise event.
- An exemplary aspect of this invention determines the impact of impulse noise by transmitting and receiving using a plurality of different FEC and interleaving parameter settings. For each FEC and Interleaving Parameter (FIP) setting, the received signal quality is determined by, for example, detecting if there are bit errors after the receiver performs the FEC decoding and deinterleaving. Based on this, the appropriate FIP setting is selected and used for transmission and reception.
- A plurality of FIP settings can be used for transmission and reception. In accordance with one particular aspect of this invention, the system can transition from one FIP setting to another FIP setting without going through the startup initialization procedure such as the startup initialization sequence utilized in traditional xDSL systems. For example, an xDSL system that implements the systems and methods described herein could start using an FIP setting of (N=255, K=247, R=8, D=64) and then transition to an FIP setting of (N=255, K=239, R=16, D=64) without re-executing the startup initialization procedure.
- Knowing that the first FIP setting has a BECC=256 bytes and the second setting has a BECC=512 bytes, means, for example, that the second setting can correct an impulse that causes twice as many bit errors as the first FIP setting. On the other hand, the first FIP setting has less FEC parity (overhead) which results in a higher information (net) data rate for the user during Showtime. This is also illustrated by the fact that K, the number of information bytes per code word, is higher for the first FIP setting. For each of the FIP settings, the receiver detects whether there are bit errors after the decoding and deinterleaving process. This detection can be done by, for example, by performing a cyclic redundancy check (CRC) after the decoding and deinterleaving process is complete as defined in the ITU standard G.992.x. In general, the CRC is a well-known method for detecting bit errors. Since impulse noise occurs at random times, this system can operate using a particular FIP setting for a period of time that is sufficient to encounter the impulse noise. In the simple example illustrated above, only the K and R values were modified. It should be appreciated however, that the systems and methods of this invention are not limited thereto but rather can be extended to include the modification of any one or more FIP parameter(s).
- The process of determining the impact of impulse noise by transmitting and receiving using a plurality of FIP settings can be done while in steady-state transmission, i.e., Showtime for DSL systems, when user information bits are being transmitted.
- The process of determining the impact of impulse noise by transmitting and receiving using a plurality of FIP settings, can be done during a special impulse noise training period during which the system is not actually transmitting user data. In accordance with this exemplary aspect of the invention, the standard xDSL procedure is modified to include the capability of measuring the effectiveness of a chosen impulse noise protection (INP) setting during initialization and having receiver-controlled updates of transmission parameters that control the INP setting, e.g., FEC parameters and interleaving parameters, during initialization.
- A new initialization state is included in the xDSL initialization procedure that provides the capability to measure the effectiveness of the current INP settings. The new initialization state will be referred to as the INPTraining state and it can, for example, follow the exchange of the Showtime transmission parameters such as the bi/gi table, trellis coding, tone reordering, FEC/interleaving parameters, etc. It is important to note that steady-state transmission during which user information is transmitted is known as “Showtime” in XDSL systems and that standard ITU G.992.3 ADSL systems and ITU VDSL G.993.3 systems include an exchange phase in initialization during which the Showtime parameters are exchanged, see, for example, G.992.3 and G.993.1.
- During this INPTraining state, the transceivers transmit and receive using at least one of the standard Showtime functions using the Showtime parameters, e.g., bi/gi table, FEC/interleaving parameters, etc., that are exchanged during the previous exchange phase. These functions include at least one of Showtime PMD functions, e.g., bi/gi table, trellis coding, tone reordering, etc., PMS-TC functions, such as framing and FEC/interleaving, and TPS-TC functions. During the INPTraining state, the TPS-TC can transmit idle ATM cells, HDLC flags, or 64/65 idle packets depending on the TPS-TC type.
- At the receiver, the CRC, the FEC, the TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the IP setting is adequate for the current impulse noise conditions on the line. The receiver can also use these receiver functions to automatically and dynamically determine what the correct INP setting should be. If the current INP setting is not adequate, a new set of Showtime transmission parameters can be exchanged and the process repeated by reentering the INPTraining state using the newly exchanged Showtime transmission parameters. If, on the other hand, the current INP setting is adequate, the transceivers can enter into Showtime.
- An exemplary advantage associated with this aspect of the invention is that the receiver can measure the effectiveness of the current INP setting and can make updates to the INP setting based on these measurements during initialization. This is important because the receiver generally has the most knowledge of channel conditions, receiver functionality, and processing capability. In general, the receiver has the best capability to make the necessary trade offs between data rate, latency, excess margin, FEC redundancy, coding gain, and the like. Current related ADSL systems have the operator servicing lines that are experiencing high impulse noise by trying various INP settings in an attempt to find an error-free operating mode. However, since the operator is not capable of making the receiver trade offs stated above, such as the data rate, latency, and the like, the process will often lead to a sub-optimum result.
- Another exemplary aspect of this invention relates to determining the length and/or repetition period of impulse noise events in order to select an appropriate INP setting.
- For example, the transceivers can transmit and receive using at least one of the standard Showtime functions and parameters such as the bi/gi table, FEC/interleaving parameters, and the like. These functions include the Showtime PMD functions, such as the bi/gi table, trellis coding, tone reordering and the like, PMS-TC functions (such as framing and FEC interleaving) and TPS-TC functions. The TPS-TC may transmit ATM cells, HDLC packets, or 64/65 packets depending on, for example, the TPS-TC type.
- At the receiver, the CRC, the FEC, the TPS-TC error detection capabilities, and other receiver functions can be used to determine the length and the period of the impulse noise and whether an INP setting is adequate for the current impulse noise conditions on the line.
- For example, the receiver can determine the length of an impulse noise event. The length of impulse noise events can be determined in a number of ways. For example, they can be determined as:
-
- 1. The length of the impulse in time, e.g., how many microseconds the impulse power is above a specific noise level (e.g. the above the stationary channel noise)
- 2. The number received bits that are affected by the impulse noise, e.g. how many received bits are in error in a specific sliding time window or how many consecutive bits are in error in a stream
- 3. The number of received ATM cells that are affected by the impulse noise, e.g. how many ATM cells contain bits that are in error. This may be detected using a standard ATM HEC, which is a CRC that covers the ATM header bits. Alternatively this may detected by checking the ATM payload bits by, for example, transmitting a predefined bit pattern that is known by the receiver
- 4. The number of 64/65 packets that are affected by the impulse noise, e.g. how many packets contain bits that are in error (the 64/65 CRC can be used for this)
- 5. The number of received DMT symbols that are affected by the impulse noise, e.g., the measured noise in a DMT symbol is above a predefined threshold which results in most (if not all) the bits in that DMT symbol being in error
- 6. The number of FEC codewords that are affected by the impulse noise, e.g., how many codewords have an uncorrectable number of bit errors, i.e., the number of bit errors in a codeword exceeds the number of bit that are correctable by the FEC code
- In accordance with one exemplary aspect, the FEC correction capability and interleaving is turned off when trying to determine the length of the impulse noise. For example, the FEC may be configured so that there are no parity bits (i.e., R=0) or the FEC may be disabled altogether (i.e., no codewords are sent). Additionally, for example, the interleaving may be disabled by setting the interleaver depth to 1 (i.e., D=1). Disabling the FEC and interleaving is beneficial when trying to determine the length of the impulse noise based on affected bits, affected code words and/or affected packets. This is true since when the FEC/interleaving is enabled, the impulse noise event will be spread over a large time period and it will be more difficult to determine the length of the original impulse.
- The exemplary techniques discussed herein that are used to determine the length of the impulse event can also be extended to determining the repetition period of the impulse noise event, i.e., how often is impulse noise occurring. The repetition period can be important, because the period has an effect on the FIP setting that is used. For example, if the interleaving spreads an impulse noise event over a period of time that exceeds the impulse period, then the interleaver could combine multiple impulse noise events together. As a result, the FEC correction capability may have to be increased. In order to determine the repetition period of an impulse noise event, the receiver can first detect the impulse noise event as discussed above and then determine how often the impulse noise events occur. For example, periodic impulse noise due to AC power lines occurs at a 120 Hz reception rate, or approximately every 8 ms.
- In the case where the impulse noise does not have a fixed length, i.e., where the impulse noise varies over time, the receiver can attempt to determine the maximum impulse noise length. This involves measuring several impulse noise events and determining the impulse noise event with the maximum length. In practice, it is likely that the impulse noise will have varying length and it is important that the FEC/interleaving settings be configured to handle the maximum, e.g., worst case, impulse noise event.
- Once the receiver determines the (maximum) length of the impulse noise and/or the repetition period of the impulse noise, this information can be sent to the transmitting modem. In particular, when the receiving modem, such as a Customer-Premises (CPE) modem determines the (maximum) length of the impulse and/or the repetition period of the impulse, the CPE modem could send the information to a Central Office (CO) modem in a message. The length of the impulse length event can be defined and specified in the message in terms of time, received bits, ATM cells, 64/65 packets, DMT symbols, or the like. The CO modem could then, for example, provide this information to the CO-MIB, which is the management interface that is used by the operator or service provider to configure the modems. For example, based on this information, the operator may configure the modems to a different INP value, data rate, latency, or the like. This process could also be automated such that the message received by the CO modem allows automatic reconfiguration to adjust, for example, INP values, data rate, latency, or the like.
- The exemplary aspects of the invention that are used to determine the length and/or repetition period of the impulse noise event can be performed during initialization and/or Showtime. During initialization, the method can perform during an INPTraining state such as the one described herein. During Showtime the method can be performed, for example, during a Showtime INP adaptation phase as described herein.
- These and other features and advantages of this invention are described in, or are apparent from, the following description of the embodiments.
- The features of this invention will be described in relation to the figures, wherein:
-
FIG. 1 is a functional block diagram illustrating an exemplary impulse noise adaptation system according to this invention; -
FIG. 2 illustrates an exemplary initialization state machine that includes an INPTraining state according to this invention; -
FIG. 3 is a flowchart outlining an exemplary method for impulse noise protection adaptation during Showtime according to this invention; -
FIG. 4 is a flowchart illustrating an exemplary receiver optimized method for impulse noise protection adaptation according to this invention; -
FIG. 5 is a flowchart illustrating an exemplary method for forward error correction synchronization according to this invention; -
FIG. 6 is a flowchart illustrating an exemplary method for flag signal synchronization according to this invention; and -
FIG. 7 is a flowchart illustrating an exemplary method for determining impulse noise length and period according to this invention. - The exemplary embodiments of this invention will be described in relation to adapting impulse noise parameters as well as measuring impulse noise length and repetition period within an xDSL environment. However, it should be appreciated that, in general, the systems and methods of this invention can be applied and will work equally well with any type of communication system in any environment.
- The exemplary systems and methods of this invention will be described in relation to xDSL modems and associated communication hardware, software, and communication channels. However, to avoid unnecessarily obscuring the present invention, the following description omits well-known structures and devices that may be shown in block diagram form or otherwise summarized.
- 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. For example, the systems and methods of this invention can generally be applied to any type of system within any environment in which the impulse noise length and/or period is desired, or for which impulse noise adaptation is desired.
- Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated in specific locations, it is to be appreciated that the various components of the system can be located or relocated at distant portions of a distributed network, such as a telecommunications network and/or the Internet, or within a dedicated secure, unsecured and/or encrypted system. Thus, it should be appreciated that the components of the system can be combined into one or more devices, such as a modem, 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 system can be arranged at any location within a distributed network without effecting the operation of the system. For example, the various components can be located in a central office (CO or ATU-C) modem, a customer premises modem (CPE or ATU-R), or some combination thereof. Similarly, the functionality of the system could be distributed between one or more of the modems and an associated computing device.
- Furthermore, it should be appreciated that the various links, including communications link 20, connecting the elements can be wired or wireless links, or any combination thereof or any other known or later-developed element(s) that is 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, or combination of hardware and software that is capable of performing the functionality associated with that element. Furthermore, as used herein, the term “transmitter” has the same meaning as the term “transmitting modem” of “transmitting transceiver” and the term “receiver” has the same meaning as “receiving modem” or “receiving transceiver.”
-
FIG. 1 illustrates an exemplary embodiment of an impulsenoise adaptation system 100 according to an exemplary embodiment of this invention. In particular, thesystem 100 comprises a receivingmodem 200 and atransmitting modem 300. Theexemplary receiving modem 200 comprises a decoder/deinterleaver 210, a bit error rate (BER)detection module 220, a forward error correction and interleaving parameter (FIP)module 230, an impulse noiselength determination module 240, an impulse noiseperiod determination module 250, an impulse noiseparameter management module 260, an impulse noiseprotection adaptation module 270, asynchronization module 280, amessage module 290 and a controller and memory (not shown) all interconnected by alink 5. Theexemplary transmitting modem 300 comprises amanagement module 310, asynchronization module 320, amessage module 330, and may optionally include an impulse noiseparameter management module 340. - In operation, the exemplary communication system adapts the impulse noise parameters on-line by operating using a series of different FIP settings. For each FIP setting, the system can dynamically determine if the appropriate amount of impulse noise protection is being provided. Based on these determinations, the system can select a particular FIP setting for regular, i.e., Showtime, operation. As will be discussed in greater-detail hereinafter, this impulse noise protection adaptation can be performed during Showtime and/or during initialization.
- Impulse noise protection adaptation during Showtime includes the following exemplary steps. First, the DSL system, i.e., the transmitting and receiving modems, completes regular initialization and commences transmission and reception using a first FIP setting. For DSL systems, this first FIP setting is selected by the
receiver 200 and is based on the minimum/maximum data rate, maximum latency, and minimum INP parameters as configured by, for example, the service provider via themanagement module 310. A detailed explanation of this procedure can be seen in G.992.3. - The system will use this first FIP setting for a period of time T1. During this period, and in conjunction with the
BER detection module 220, thereceiver 200 detects if bit errors have occurred using this first FIP setting for the decoding and deinterleaving performed by the decoder/deinterleaver 210. For example, thereceiver 200 can use a CRC to detect bit errors. If there are no bit errors, then the current INP setting is adequate and there is no need to modify the INP setting and Showtime communication can continue as normal. - However, if bit errors have been detected by the
BER detection module 220, an adjustment to the INP setting may be appropriate. For example, a service provider, a user, or the system can choose an updated INP setting. Since bit errors have been detected, the INP setting could be increased by an on-line modification to the FIP parameters. Specifically, thetransmitter 300, and for example themanagement module 310, in response to an indication from thereceiver 200 that bit errors have been detected, can send a message to thereceiver 200 to initiate a change in the INP settings. Thereceiver 200, in cooperation with themessage module 290, theFIP module 230, the impulse noiseparameter management module 260 and impulse noiseprotection adaptation module 270, can return a message to thetransmitter 300 that specifies a newly determined FIP setting that satisfies the new INP requirement. - The
transmitter 300 andreceiver 200 can then transition to the new INP setting by starting to use the new FIP parameters for transmission and reception, respectively, at a synchronized point in time. This synchronization can be done in accordance with a number of exemplary methods that are discussed hereinafter. - Upon synchronization, the
system 100 continues communication using the updated FIP settings for a second period of time T2. If the receiver detects that bit errors are occurring using this updated FIP setting during the decoding and deinterleaving performed by the decoder/deinterleaver 210 the steps can be repeated with the selection of another updated INP setting. However, if there are no bit errors detected by thereceiver 200 during the time period T2, then the new INP setting is adequate and there is no need for further change at which point the INP adaptation procedure can end. - This Showtime-based INP adaptation process can be repeated as many times as necessary until an INP setting is obtained that provides the required impulse noise immunity and/or bit error rate.
- One advantage of this technique is that the transition between different FIP settings can be accomplished without reinitializing the transceivers using the lengthy standard initialization procedure that is typically used in ADSL and VDSL systems. In contrast, the transition can occur without the standard initialization since the transition between FIP settings can be synchronized between the transmitter and the receiver such that the
receiver 200 can determine when to start FEC decoding using the new FIP settings for K and R. As will be discussed hereinafter, this transition/can be synchronized using a number of different exemplary methods. - The transition can also be accomplished without synchronization in which case the
receiver 200 will determine when the new FIP settings are used by some alternative means. For example, the receiver could determine when the new FIP settings are being used by FEC decoding using both the old and updated FIP settings and determining which one is currently being utilized by the transmitter by determining with which FIP setting the codeword is correct. Other receiver functions such as CRCs, ATM HEC errors and the like could also be used. - This impulse noise protection adaptation procedure can be performed during regular steady-state transmission, i.e., Showtime in ADSL, using actual user data or, for example, idle ATM cells. This methodology can also be performed during a special impulse noise training period during which the system is not actually transmitting user data. For example, this impulse noise training period could utilize transmitted predefined pseudorandom bit streams or, for example, idle ATM cells or HDLC flags for determining an appropriate INP value.
- The length of the time periods T1, T2, . . . can be controlled by, for example, the receiving
modem 200. The receivingmodem 200 could control the length of these time periods by, for example, sending a message that specifies how long the transmitter should transmit using a particular FIP setting. This length can be defined, for example, in terms of the number of DMT symbols or the number of FEC codewords. For example, a message could indicate that 200 DMT symbols should be sent for all HP settings or 300 FEC code words should be sent for all FIP settings. Alternately, the message can indicate a different number of DMT symbols or FEC code words for each FIP setting. This technique could further be used to aid in determining an appropriate INP setting by forwarding a predetermined number of DMT symbols at a first FIP value, followed by a second number of DMT symbols at a second FIP value, and so on. For each of these sets of DMT symbols and associated FIP values, the receiver could determine the bit error rate, with the cooperation of theBER detection module 220, and then forward a message, with the cooperation of themessage module 290, to thetransmitter 300 specifying which FIP setting provided the appropriate impulse noise protection. - Similarly, the transmitting
modem 300 and receivingmodem 200 could cooperate such that an optimum impulse noise protection value is converged upon. For example, the transmittingmodem 300, with the cooperation of themessage module 330, could forward a message to the receivingmodem 200 specifying a first INP setting. If there are no bit errors, a message could be sent via themessage module 290 to thetransmitting modem 300 indicating that there are no bit errors and a lower INP value could be attempted. The impulse noiseparameter management module 260 andFIP module 230 could then determine an appropriate lower INP setting and forward it to thetransmitter 300. As discussed above, since a lower INP value is inversely proportional to the user data rate, it is advantageous to optimize the INP value based on detected errors. The transmittingmodem 300, in cooperation with themessage module 330, could then send another message to the receivingmodem 200 indicating that the lower INP value will be transitioned to at which point the procedure repeats itself through detection of bit errors in cooperation with the bit errorrate detection module 220 and the decoder/deinterleaver 210. This reduction in the INP parameters can continue until bit errors are detected at which point a message is sent, with the cooperation of themessage module 290, to thetransmitting modem 300 indicating a higher INP value is required since bit errors were detected. Then, for example, based on an evaluation of a convergence of bit errors vs. impulse noise protection parameters, an optimum INP value can be determined and transitioned to by thereceiver 300 andtransmitter 200. This procedure could also be used to increase the INP parameters in a similar fashion. - The length of the time periods T1, T2, . . . can also be controlled by the
transmitter 300. For example, thetransmitter 300 could control the length of these time periods, by, for example, sending a message to thereceiver 200 that specifies the length of time the transmitter will transmit using a particular FIP setting. This length could be defined in terms of the number of DMT symbols or, for example, the number of FEC codewords. The exemplary message could indicate that, for example, 200 DMT symbols would be sent for all FIP settings or 300 FEC codewords will be sent for all FIP settings. The message could also indicate a different number of DMT symbols or FEC codewords for each FIP setting. In general, the message could contain any type of information relating to how long the transmitter will be using a specific FIP setting(s). - The length of the time periods T1, T2 . . . can also be controlled by, for example, a service provider or a user. For example, the service provider could configure through the management module 310 a minimum time X=10 seconds to be used for testing each FIP setting. The service provider could use the knowledge of the nature of the impulse noise, such as how often impulse noise event occurs, to determine the times. However, and in general, the length of the time periods could be configured to be any length of time as appropriate.
- As discussed above, when a determination is made that there are bit errors and an increase in the INP setting is desirable, the receiving
modem 200 can determine the new INP settings. However, it should be appreciated that the transmittingmodem 300, in cooperation with the impulse noiseparameter management module 340 could also determine updated INP settings. For example, either modem could continually adapt the INP values as discussed above until no bit errors that are the result of impulse noise are detected by theBER detection module 220. - As alluded to above, the receiver and transmitter can synchronize the modification of the FEC and interleaving parameters such that the both the transmitter and receiver start using the parameters at the same instant in time. This synchronization can be based on, for example, a synchronization using FEC codeword counters or a flag signal.
- For synchronization using FEC codeword counters, the
receiver 200 andtransmitter 300 can synchronize the change in cooperation with thesync modules transmitter 300 and thereceiver 200 is reached. Prior to the transition point, thetransmitter 300 orreceiver 200 in cooperation with themessage module 290 andmessage module 330, would send a message indicating the FEC codeword count value on which the FIP parameters will be updated. For example, the transmittingmodem 300 can enter into Showtime and thesynchronization module 320 commences counting the number of transmitted FEC codewords. For example, the first codeword transmitted has a count value of 0, the second transmitted codeword has a count value of 1 . . . . The counter can optionally be defined as having a finite length, for example, 0 to 1023 (10 bits) such that when the value of 1023 is reached, on the next FEC code word that is transmitted, the counter restarts at the value of 0. - Similarly, the receiving
modem 200 upon entering Showtime starts a counter in cooperation with thesynchronization module 280 that counts the number of received FEC codewords. The first received FEC codeword has a count value of 0, the second received FEC codeword to the count value of 1 . . . . As with thesynchronization module 320, thesynchronization module 280 can have a counter with a finite length, for example 0-1023, such that when the value of 1023 is reached, on the next FEC codeword the counter restarts at 0. - At some point, for example, based on detected bit errors, the user, a service provider, or the like, it is determined that an updated FP setting is needed. The receiving
modem 200 can send a message, via themessage module 290, to thetransmitting modem 300, and in particular themessage module 330 and impulse noiseparameter management module 340. The updated FIP setting can alternatively be sent from the transmitting modem to the receiving modem. - The
synchronization module 280 andmessage module 290 then cooperate to send a message to thetransmitting modem 300 specifying the FEC codeword counter value on which the new FIP settings are to be used for transmission and reception. Alternatively, the transmitting modem, in cooperation with themessage module 330, can send a message to the receiving modem indicating the FEC codeword counter value on which the FIP settings are to be used for transmission and reception. For example, the message can indicate that when the code word counter equals 501, the new FIP setting will be used for transmission and reception. - When the transmitter FEC codeword counter equals the value indicated in the message, the
synchronization module 220 instructs the transmittingmodem 300 to transition to the new FIP settings. Similarly, when thesynchronization module 280 in thereceiving modem 200 counts the FEC codeword that equals the value indicated in the message, the receivingmodem 200 transitions to using the new FIP settings for reception. - Synchronization can also be performed through the use of a flag signal (sync flag). For this exemplary embodiment, the receiving
modem 200 and transmittingmodem 300, in cooperation with thesynchronization module 280 andsynchronization module 320, synchronize the change in FIP settings using a flag or marker signal that is similar to that used in the ADSL2 G.992.3 ORL protocol. This protocol may be more desirable than using an FEC codeword counter because, for example, it has greater impulse noise immunity. - For synchronization using a flag signal, the receiver and transmitter would start using updated FEC and interleaving parameters on a pre-defined FEC codeword boundary following the sync flag. For example, while transmitting using a first INP setting, a determination is made by, for example, the
BER detection module 220 that a new FIP setting is needed due to the presence of impulse noise on the line. This determination can be performed by the receiving modem, in cooperation with theFIP module 230, the transmitting modem, a user, a service provider, or the like. The receivingmodem 220, in cooperation with themessage module 290, sends a message to thetransmitting modem 300 indicating the new FIP settings to be used for transmission and reception. Alternatively, the transmitting modem, in cooperation with themessage module 330, prepares and sends a message to the receiving modem indicating the updated FIP settings to be used for transmission and reception. - The transmitting modem then sends a flag or marker signal to the receiving
modem 200 indicating that the new FIP settings are to be used on a predetermined number of DMT symbols following the transmission of the flag or marker signal. For example, the flag signal could be an inverted sync symbol, or sync FLAG, as used in the ADSL2 G.992.3 OLR protocol. The transmittingmodem 300 then starts using the new FIP settings for transmission on the predetermined number of DMT symbols following the transmission of the flag or marker signal. Similarly, the receiving modem starts using the new FIP settings for reception once the predetermined number of DMT symbols following the receipt of the flag or marker signal have been received. - 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} - The On-line INP adaptation process is restricted to only modify the number of information bytes in a codeword (K) and the number of parity bytes in a codeword (R). The FEC Codeword Size (N=K+R) and Interleaver Depth (D) are not changed. This means that the latency (or interleaver memory size) and the line rate are not modified on-line. However the user data rate will change during the process since K is being modified. Also since the line rate and the FEC codeword size are not modified, the S value does not change in the process. It is important to note that with these constraints, the On-line INP adaptation process can be done in as seamless manner (no bit errors and service interruption). This means provided that the modification if the FIP setting is restricted to K and R, the transition between FIP settings can be done in a seamless manner. This is the case because if the codeword size N and the interleaver depth D are not modified, the transition can happen without the problem of “interleaving memory flushing.” Interleaver memory flushing is a well-known problem in which errors occur because interleaver and deinterleaver memory locations are overwritten due to on-line changes in the codeword size (N) and or interleaver depth (D).
- 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} - In this example the Line Rate is modified on-line. For this reason it is necessary to also complete a rate adaptation process in order to complete this On-Line INP adaptation. A method for Seamless Rate Adaptation is described in U.S. Pat. No. 6,498,808, which is incorporated herein in its entirety.
- While these examples restrict the changes to a subset of the FIP parameters, they can obviously be extended to cover any combination of the FIP parameters (N, K, R and D). For example, the value of D could also be modified in addition to the values of K, R and N. This could result in a change in the required interleaver memory and latency. In order to keep the memory and latency constant it is necessary to change the codeword size (N) accordingly when changing the interleaver depth (D). For example, if the interleaver depths is changed from D=64 to D=128, the Codeword size would have to be decreased by a factor of 2 so that overall latency is constant.
-
FIG. 2 illustrates an exemplary modified initialization state machine that includes the INPTraining state prior to Showtime. This state machine is based on the VDSL G.993.1 ITU standard. As defined in G.993.1, VTU-O is the VDSL Transceiver Unit at the Optical Network Unit (ONU) and VTU-R is the VDSL Transceiver Unit at the Remote terminal. The Initialization state machine inFIG. 2 is an example of how INPTraining states could be included in a modified VDSL initialization procedure. While exemplaryFIG. 1 includes the Training state at a specific time in the initialization sequence, the INPTraining state can be included at any time during initialization provided that it is preceded by a state during which Showtime parameters are exchanged between the transceivers. - O-P-INPTrain
- During the O-P-INPTrain State the VTU-O transmitter transmits DMT Symbols using the standard PMD, PMS-TC and TPS-TC SHOWTIME functions with parameters exchanged during the previous Exchange Phase. During this state, the TPS-TC transmits idle ATM cells, HDLC flags or 64/65 idle packets. SOC is inactive during this state.
- This state is used by the VTU-R to determine the correct DS INP setting based on Impulse Noise conditions on the line. For example, the downstream CRC, FEC error detection, TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the INP setting is adequate. The receiver can also use these receiver functions to determine the correct INP setting.
- If the VTU-R determines that the current INP setting is not adequate, the VTU-R transmits the R-P-ISYNCHRO2 signal to indicate the need to transition back to the Exchange Phase in order to exchange new transmission parameters.
- If the VTU-R determines that the current INP setting is not adequate, the VTU-R transmits the R-P-SYNCHRO2 signal to indicate that it is OK to transition to Showtime with the current transmission parameters.
- R-P-INPTrain
- During the R-P-INPTrain State the VTU-R transmitter transmits DMT Symbols using the standard PMD, PMS-TC and TPS-TC Showtime functions with parameters exchanged during the previous Exchange Phase. During this state, the TPS-TC transmits idle ATM cells, HDLS flags or 64/65 idle packets. SOC is inactive during this state.
- This state is used by the VTU-O to determine the correct US INP setting based on Impulse Noise conditions on the line. For example, the upstream (US) CRC, FEC error detection, TPS-TC error detection capabilities, and other receiver functions can be used to determine whether the INP setting is adequate. The receiver can also use these receiver functions to determine the correct INP setting.
- If the VTU-O determines that the current INP setting is not adequate, the VTU-O transmits the O-P-ISYNCHRO2 signal to indicate the need to transition back to the Exchange Phase in order to exchange new transmission parameters.
- If the VTU-O determines that the current INP setting is not adequate, the VTU-O transmits the O-P-SYNCHRO2 signal to indicate that it is OK to transition to Showtime with the current transmission parameters.
- O-P-SYNCHRO2
- The O-P-SYNCHRO2 is the same as defined in the current VDSL1. As in VDSL1, the VTU-O transmitter enters Showtime after transmitting the O-P-SYNCHRO2 signal.
- But, if the VTU-R has not also entered into Showtime, the VTU-O waits for receipt of the R-P-SYNCHRO2 or R-P-ISYNCHRO2. If the VTU-O receives the R-P-SYNCHRO2 it continues in Showtime. If the VTU-O receives the R-P-ISYNCHRO2, the VTU-O transmitter transitions back to the beginning of the O-P-MEDLEY state.
- R-P-SYNCHRO2
- The O-P-SYNCHRO2 is the same as defined in the current VDSL1. As in VDSL1, the VTU-R transmitter enters Showtime after transmitting the R-P-SYNCHRO2 signal.
- But, if the VTU-O has not also entered into Showtime, the VTU-R waits for receipt of the O-P-SYNCHRO2 or O-P-ISYNCHRO2. If the VTU-R receives the O-P-SYNCHRO2 it continues in Showtime. If the VTU-R receives the O-P-ISYNCHRO2, the VTU-R transmitter transitions back to the beginning of the R-P-MEDLEY state.
- O-P-ISYNCHRO2
- The O-P-ISYNCHRO2 is phase-inverted version of the O-P-SYNCHRO2, i.e., a subcarrier-by-subcarrier 180 degrees phase reversal. The VTU-O transmitter transitions to the beginning of the O-P-MEDLEY state after transmitting the O-P-ISYNCHRO2 signal.
- R-P-ISYNCHRO2
- The R-P-ISYNCHRO2 is phase-inverted version of the R-P-SYNCHRO2, i.e., a subcarrier-by-subcarrier 180 degrees phase reversal. The VTU-R transmitter transitions to the beginning of the R-P-MEDLEY state after transmitting the R-P-ISYNCHRO2 signal
- Exemplary Overview State Transition Rules Based on SYNCHRO2 and the ISYNCHRO2 signals:
-
- If either the VTU-O or the VTU-R transmits the ISYNCHRO2 signal then both VTU-R and VTU-O transition back to beginning of the MEDLEY state.
- If both the VTU-O and the VTU-R transmit the SYNCHRO2 signal then both the VTU-R and the VTU-O transition into Showtime.
- There are several important points regarding this exemplary embodiment. First, the receiver can measure the efficiency of the plurality of INP settings without completing a new initialization procedure such as is used in ADSL and VDSL systems. Second, the length of the time of the O-P-INPTrain and R-P-INPTrain states can be controlled by the VTU-R and VTU-O respectively. In this way the receivers have adequate time to determine if the current INP setting is correct. In order to accomplish this, prior to entering the R-P-INPTrain state, the VTU-O can transmit a message to the VTU-R indicating the minimum length of the R-P-INPTrain state. Likewise, prior to entering the O-P-INPTrain state, the VTU-R can transmit a message to the VTU-O indicating the minimum length of the O-P-INPTrain state. For example, the message could indicate that a minimum of 20000 DMT symbols should be sent during the O-P-INPTrain state. Additionally, the length of the time of the O-P-INPTrain and R-P-INPTrain states could be set by the DSL service provider in order to make sure that the initialization does not take too long or because the service provider may have some knowledge of the statistics of the impulse noise which require setting the length of the INPTrain states. In this exemplary case a message could be sent from the VTU-O to the VTU-R indicating the minimum and/or maximum length of the O-P-INPTrain and/or the R-P-INPTrain states. For example, the message could indicate that a minimum of 20000 DMT symbols should be sent during the R-P-INPTrain state. Also, for example, the message could indicate that a maximum of 40000 DMT symbols should be sent during the R-P-INPTrain state.
- The length of the time of the O-P-INPTrain and R-P-INPTrain states could also be controlled by the VTU-O and VTU-R respectively. In this case, the transmitters will have control of the state lengths. In order to accomplish this, prior to entering the R-P-NPTrain state, the VTU-R can transmit a message to the VTU-O indicating the minimum length of the R-P-INPTrain state. Likewise, prior to entering the O-P-INPTrain state, the VTU-O can transmit a message to the VTU-R indicating the minimum length of the O-P-INPTrain state. For example, the message could indicate that a minimum of 20000 DMT symbols should be sent during the O-P-INPTrain state.
- As discussed above, another exemplary aspect of this invention relates to determining the length and/or repetition period of impulse noise events in order to select an appropriate INP setting.
- The INP length can be determined using any one of a plurality of metrics. For example, the INP length can be determined based on one or more of:
-
- 1) The length of the impulse in time
- 2) The number of received bits that are affected by the impulse noise
- 3) The number of received ATM cells that are affected by the impulse noise
- 4) The number of 64/65 packets that are affected by the impulse noise
- 5) The number of received DMT symbols that are affected by the impulse noise
- 6) The number of FEC codewords that are affected by the impulse noise
- As an example, assume that length of the impulse noise is 700 microseconds (Example 1). At a data rate of 1 Mbps this could correspond to an impulse noise length of 700 bits (Example 2) assuming that all impulse noise was high enough to affect all 700 bits in the 700 microsecond period. This also could correspond to a impulse noise length of 700/(53*8)=1.65 ATM cells since there are 53 bytes in a ATM cell (Example 3). This also could correspond to an impulse noise length of 700/(65*8)=1.35 64/65 packets since there are 65 bytes in a 64/65 packet (Example 4). This also could correspond to an impulse noise length of 700/(250)=2.8 DMT symbols (INP=2.8) assuming the DMT symbol rate is 4 kHz (250 microseconds DMT symbol length) (Example 5).
- As an example, the determination of the IP length with the number of received bits that are affected by impulse noise can be performed in accordance with the following procedure. Initially, the transmitting
modem 300 transmits data using at least one of the Showtime functions. In accordance with a first exemplary embodiment, at least the bit allocation table is used. In addition, or alternatively, the trellis coder, framer, and TPS-TC functions may also be used. Additionally, or alternatively still, the interleaving and FEC may also be used. - The receiving
modem 200 receives data using at least one of the Showtime functions, such as the bit allocation table as discussed above. Similarly, the trellis coder, framer, TPS-TC and/or interleaving and FEC can be used. - The
transmitter 300 then transmits a predefined bit pattern that is used for determining or measuring the impulse noise length based on detected erroneous bits. The receivingmodem 200 compares, with the assistance of the impulse noiselength determination module 240, the predefined bit pattern to the received bit pattern in order to detect bit errors. Since impulse noise events typically cause a burst of errors in a bit stream, the receivingmodem 200 determines the length of the impulse noise event by detecting and determining the length of the error burst. - Once the
receiver 200 determines the length of the impulse noise, the receivingmodem 200, in cooperation with themessage module 290, sends a message to thetransmitter 300 that indicates the determined length of the impulse noise. - In accordance with an exemplary embodiment, the FEC correction capability and interleaving is turned off when trying to determine the length of the impulse noise, e.g., R=0 and D=1. Disabling the FEC and interleaving is beneficial when trying to determine the length of the impulse noise based on affected bits, affected code words, or affected packets. This is the case because if the FEC/interleaving is enabled, the impulse event can be spread over a large time period which makes it more difficult to determine the length of the original impulse.
- The exemplary methodology discussed above can also be used to determine the length of the impulse event using other metrics. For example, a predefined bit pattern could be used in the payload of the ATM cells or the 64/65 packets. Idle packets or cells, which carry a predefined pattern, could also be used. In these cases, the receiver would compare the received data to the predefined data to determine the length of the impulse or to determine if an INP setting is adequate. Alternatively, the CRC of the ATM cell or 64/65 packet could be used to determine the length of the impulse noise. This would provide a courser measurement of the impulse noise length since it would be an integer number of packets or cells. In this example, a 700 bit impulse would cause CRC errors in two ATM cells so the length of the impulse noise would be two ATM cells, as opposed to the more precise measurement of 1.64 above. Likewise, in this example, a 700 bit impulse would cause CRC errors in two 64/65 packets so the length of the impulse noise would be two packets, as opposed to the more precise measure of 1.35 above.
- Likewise, a predefined bit pattern could also be used to modulate the carriers in the DMT symbols so that the receiver would know what DMT symbols were transmitted. In this case, the
receiver 200 would determine how many DMT symbols were corrupted by comparing the received signal with a known transmitted signal. - The exemplary techniques used to determine the length of the impulse noise event could also be extended to determine the repetition rate of the impulse noise event in cooperation with the impulse noise
period determination module 250. In order to determine the repetition period of an impulse noise event, thereceiver 200 detects the impulse noise event as discussed above and then determines how often they occur. For example, periodic impulse noise due to AC power lines occur at 120 Hz reception rates or approximately every 8 ms. Thereceiver 200 could, for example, also store information about past impulse noise events and compare detected impulse noise events to historical events. The impulse noiseperiod determination module 250 could then determine which events of a similar duration are occurring at what interval. This information could then be used in determining an appropriate INP setting. - Once the
receiver 200 determines the (maximum) length of the impulse and/or the repetition period of the impulse, the information, with the cooperation of themessage module 290 can be sent to the transmitting modem. For example, when the receivingmodem 200 determines the (maximum) length of the impulse and/or the repetition period of the impulse, the impulse noiseperiod determination module 250, in cooperation with themessage module 290 can forward information to the transmitting modem that quantifies this period. The transmittingmodem 300 could provide this information to, for example, themanagement module 310, that would allow, for example, an operator or service provider to configure the modems. For example, based on the period information contained in the message, the operator may configure the modems to different INP values, data rates, latency, or the like. - The
receiver 200 could also test a specific INP setting by detecting how many received bits are errored in a specific time period. For example, if the specific INP setting enables the correction of 100 bits in an 8 msec. time period then thereceiver 200 could detect how many bits are errored in a sliding 8 msec. window. If less than 100 bits are detected in error in the 8 ms sliding window, then the IP setting is adequate. - If more than 100 bits are detected in error in a sliding window, then the INP setting is not adequate, and the FEC/interleaving needs to be changed to provide more error correction capability.
- Likewise, instead of using the received number of bits that are effected by the impulse noise, the receiver could test a specific INP setting by detecting how many received ATM cells, 64/65 packets, DMT symbols, and/or FEC corrections are affected in a specific time period.
-
FIG. 3 outlines an exemplary method for performing impulse noise protection adaptation during Showtime according to this invention. In particular, control begins in step S300 and continues to step S310. In step S310, traditional DSL initialization occurs. Next, in step S320, Showtime is entered between the two modems using the first FIP setting that was determined during the initialization in step S310. Then, in step S330, a determination is made whether bit errors are occurring using the first FIP setting. If bit errors are not occurring, control continues to step S340 where the control sequence ends. Otherwise, control jumps to step S350. - In step S350, a determination is made that an increase of the INP setting is required that requires modification of the FIP parameters. Next, in step S360, updated INP parameter is determined and a message forwarded to the receiver specifying the new INP setting. Then, in step S370, the receiver forwards to the transmitter updated FIP parameters for the new impulse noise protection requirements. Control then continues to step S380.
- In step S380, the transmitter and receiver transition to using the updated INP parameters at a synchronization point. Next, in step S390 Showtime operation continues. Control then continues back to step S330.
-
FIG. 4 outlines an exemplary method for receiver optimized impulse noise protection adaptation during Showtime. In particular, control begins in step S400 and continues to step S410. In step S410, the DSL system completes regular initialization. In particular, control begins in step S400 and continues to step S410. In step S410, the DSL system completes startup initialization and continues into Showtime in step S420 using a first FIP setting. Control then continues to step S430 where a determination is made whether bit errors are occurring using the first FIP setting. If bit errors are not occurring, control continues to step S440 where the control sequence ends. - Otherwise, control jumps to step S450 where the receiver increases the impulse noise protection by modifying the FIP parameters. Next, in step S460, a synchronization point is determined between the transmitter and receiver, and when the synchronization point is reached both the transmitter and the receiver transition to the updated FIP setting in step S470 and Showtime communications continue and control returns back to step S430.
-
FIG. 5 illustrates an exemplary method for synchronization of the modified FEC and interleaving parameters according to this invention. In particular, control begins in step S500 and continues to step S510. In step S510, the transmitter enters Showtime and counts the number of transmitted FEC codewords. Next, in step S520, the receiver enters Showtime and counts the number of received FEC codewords. Then, in step S530, after a determination is made that an updated FP setting is needed, the receiving modem sends a message to the transmitting modem indicating a new FIP setting that is to be used for transmitting and reception or, alternatively, the transmitting modem sends a message to the receiving modem indicating the new FIP setting to be used for transmission and reception. Control then continues to step S540. - In step S540, a message with the FEC codeword counter value on which the new FP values are to be used is exchanged. Next, in step S550, a determination is made whether the counter value has been reached at the transmitter. If the counter value has not been reached, the next codeword is counted in step S560 and control continues back to step S550.
- Otherwise, if the counter value has been reached, control jumps to step S570. In step S570, the transmitter transitions to the new FIP setting. Next, in step S580, a determination is made whether the counter value has been reached at the receiving modem. If the counter value has not been reached, the next received FEC codeword is counted in step S585 and control continues back to step S580. However, when the counter value has been reached in the receiving modem, control jumps to step S590 where the receiving modem switches to the new FIP value. Control then continues to step S595 where the modems continue Showtime communication and control continues to step S597 where the control sequence ends.
-
FIG. 6 illustrates an exemplary method of synchronization using a flag signal according to this invention. In particular, control begins in step S600 and continues to step S610. In step S610, the modems enter Showtime using the first FIP parameters. Next, in step S620, a message is exchanged indicating the new FIP settings. Then, in step S630, the transmitter forwards to the receiver a flag signal indicating when the new FIP settings are to be used. - At step S640, and at a predefined change time following the transmission of the flag signal, the transmitter begins transmission using the new FP parameters. Next, at step S650, at the predefined change time following the reception of the flag signal, the receiver commences reception utilizing the new FIP parameters. Control then continues to step S660 where Showtime communication continues with the control sequence ending at step S670.
-
FIG. 7 illustrates an exemplary method of impulse noise length and period determination. In particular, control begins in step S700 and continues to step S710. In step S710, the transmitter transmits data using at least one Showtime function. Next, in step S720, the receiver receives data using at least one Showtime function. Then, in step S730, the transmitter transmits predefined information to the receiver. Control then continues to step S740. - In step S740, the receiver receives the predefined information from the transmitter. Next, in step S750, the receiver compares the received predefined information to the predefined information and determines the differences (i.e., errors) between the two. Then, in step S760, and based on the detected errors, the length of the burst error is determined. Next, in step S770, a message is forwarded to the transmitter indicating the length of the impulse noise event. Control then continues to step S780 where a determination is made whether the period of the impulse noise event is also to be determined. If the period is not to be determined, control continues to step S790 where the control sequence ends. Otherwise, control jumps to step S800.
- In step S800, and once the length of the impulse noise event is know, the receiver detects how often the impulse noise events occur. For example, historical information regarding the length and timing of previous impulse noise events can be stored in a memory (not shown). Then, a comparison can be made with the aid of a processor (not shown) to compare an impulse noise event to the historical information to determine the period of repetition (if any) of similar impulse noise events and, for example, a message indicating the period as well as the timing forwarded to, for example, another transceiver, the CO, or in general any destination as appropriate. Thus, in a similar manner, this information can be forwarded in step S810 to, for example, the transmitter in a message specifying the repetition frequency of the impulse noise event. Control then continues to step S820 where the control sequence ends.
- The above-described system can be implemented on wired and/or wireless telecommunications device(s), such a modem, a multicarrier modem, a DSL modem, an ADSL modem, an xDSL modem, a VDSL modem, a linecard, test equipment, a multicarrier transceiver, a wired and/or wireless wide/local area network system, a satellite communication system, a modem equipped with diagnostic capabilities, or the like, or on a separate programmed general purpose computer having a communications device.
- 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 hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device such as PLD, PLA, FPGA, PAL, modem, transmitter/receiver, or the like. In general, any device 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 methods, protocols and techniques according to this invention.
- Furthermore, the disclosed methods may be readily implemented in software using 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 however can be readily implemented in hardware and/or software, or any means, 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.
- Moreover, the disclosed methods may be readily implemented in software, that can be stored on a storage medium, and executed on programmed general-purpose computer, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this invention can be implemented as a program embedded on personal computer such as 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 communications transceiver.
- It is therefore apparent that there has been provided, in accordance with the present invention, systems and methods for impulse noise adaptation. 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.
Claims (16)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/597,482 US20080232444A1 (en) | 2004-03-03 | 2005-03-03 | Impulse Noise Management |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US54980404P | 2004-03-03 | 2004-03-03 | |
US55598204P | 2004-03-24 | 2004-03-24 | |
US10/597,482 US20080232444A1 (en) | 2004-03-03 | 2005-03-03 | Impulse Noise Management |
PCT/US2005/006842 WO2005086405A2 (en) | 2004-03-03 | 2005-03-03 | Impulse noise management |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US55598204P Continuation | 2004-03-03 | 2004-03-24 | |
PCT/US2005/006842 A-371-Of-International WO2005086405A2 (en) | 2004-03-03 | 2005-03-03 | Impulse noise management |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/769,193 Continuation US8462835B2 (en) | 2004-03-03 | 2010-04-28 | Impulse noise management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080232444A1 true US20080232444A1 (en) | 2008-09-25 |
Family
ID=34922724
Family Applications (10)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/597,482 Abandoned US20080232444A1 (en) | 2004-03-03 | 2005-03-03 | Impulse Noise Management |
US12/769,193 Active US8462835B2 (en) | 2004-03-03 | 2010-04-28 | Impulse noise management |
US13/914,852 Active US8594162B2 (en) | 2004-03-03 | 2013-06-11 | Impulse noise management |
US14/075,077 Active US8743932B2 (en) | 2004-03-03 | 2013-11-08 | Impulse noise management |
US14/285,911 Abandoned US20140254643A1 (en) | 2004-03-03 | 2014-05-23 | Impulse noise management |
US14/757,630 Abandoned US20160127079A1 (en) | 2004-03-03 | 2015-12-23 | Impulse noise management |
US16/126,027 Expired - Fee Related US10567112B2 (en) | 2004-03-03 | 2018-09-10 | Impulse noise management |
US16/448,939 Active US10805040B2 (en) | 2004-03-03 | 2019-06-21 | Impulse noise management |
US16/781,802 Active US11005591B2 (en) | 2004-03-03 | 2020-02-04 | Impulse noise management |
US17/235,558 Abandoned US20210242961A1 (en) | 2004-03-03 | 2021-04-20 | Impulse noise management |
Family Applications After (9)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/769,193 Active US8462835B2 (en) | 2004-03-03 | 2010-04-28 | Impulse noise management |
US13/914,852 Active US8594162B2 (en) | 2004-03-03 | 2013-06-11 | Impulse noise management |
US14/075,077 Active US8743932B2 (en) | 2004-03-03 | 2013-11-08 | Impulse noise management |
US14/285,911 Abandoned US20140254643A1 (en) | 2004-03-03 | 2014-05-23 | Impulse noise management |
US14/757,630 Abandoned US20160127079A1 (en) | 2004-03-03 | 2015-12-23 | Impulse noise management |
US16/126,027 Expired - Fee Related US10567112B2 (en) | 2004-03-03 | 2018-09-10 | Impulse noise management |
US16/448,939 Active US10805040B2 (en) | 2004-03-03 | 2019-06-21 | Impulse noise management |
US16/781,802 Active US11005591B2 (en) | 2004-03-03 | 2020-02-04 | Impulse noise management |
US17/235,558 Abandoned US20210242961A1 (en) | 2004-03-03 | 2021-04-20 | Impulse noise management |
Country Status (4)
Country | Link |
---|---|
US (10) | US20080232444A1 (en) |
EP (2) | EP1721403A2 (en) |
CA (1) | CA2555757C (en) |
WO (1) | WO2005086405A2 (en) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060107170A1 (en) * | 2004-10-12 | 2006-05-18 | Ciena Corporation | Methods for the determination of FEC parameters in DMT based xDSL systems in the presence of system imposed constraints |
US20060215742A1 (en) * | 2005-03-23 | 2006-09-28 | Texas Instruments Incorporated | Optimizing for impulse noise protection in a DSL system |
US20070143498A1 (en) * | 2005-12-20 | 2007-06-21 | Stefan Uhlemann | Method and apparatus for transmitting data |
US20070195871A1 (en) * | 2006-02-22 | 2007-08-23 | Texas Instruments Incorporated | Performance of DSL modem under impulse noise |
US20070248181A1 (en) * | 2006-04-20 | 2007-10-25 | Axel Clausen | Protection of communication systems against repetitive electrical impulse noise |
US20070280339A1 (en) * | 2006-06-05 | 2007-12-06 | Vladimir Oksman | Methods and systems for determining communication parameters |
US20080069248A1 (en) * | 2006-09-15 | 2008-03-20 | Bernd Heise | Methods and systems for adaptive communication |
US20080112472A1 (en) * | 2006-11-14 | 2008-05-15 | Vladimir Oksman | Methods and systems for adaptive communication |
US20080167838A1 (en) * | 2007-01-10 | 2008-07-10 | Futurewei Technologies, Inc. | Bivariate histogram for impulse noise monitor |
US20090031197A1 (en) * | 2007-07-26 | 2009-01-29 | Texas Instruments Incorporated | Erasure decoding for receivers |
US20090323903A1 (en) * | 2006-07-31 | 2009-12-31 | Cioffi John M | Method and apparatus for analyzing and mitigating noise in a digital subscriber line |
US20100061437A1 (en) * | 2008-09-07 | 2010-03-11 | Conexant Systems, Inc. | Systems and Methods for Impulse Noise Characterization |
US20100088569A1 (en) * | 2008-10-05 | 2010-04-08 | Ikanos Communications, Inc. | Packet Retransmission |
US20100115374A1 (en) * | 2007-04-02 | 2010-05-06 | Kirkby Robert H | Data recovery scheme |
US20100220771A1 (en) * | 2004-03-03 | 2010-09-02 | Aware, Inc. | Impulse noise management |
US20100228508A1 (en) * | 2009-03-09 | 2010-09-09 | Tektronix, Inc. | Apparatus and method for performing burst triggering in a test and measurement instrument |
US8194722B2 (en) * | 2004-10-11 | 2012-06-05 | Broadcom Corporation | Various methods and apparatuses for impulse noise mitigation |
US8472533B2 (en) | 2008-10-10 | 2013-06-25 | Broadcom Corporation | Reduced-complexity common-mode noise cancellation system for DSL |
US20130182752A1 (en) * | 2012-01-17 | 2013-07-18 | Casa Systems, Inc. | System and Method for Detecting Burst Noise During Quadrature Amplitude Modulation Communications |
US20130215940A1 (en) * | 2009-07-10 | 2013-08-22 | Futurewei Technologies, Inc. | Method for Robust Crosstalk Precoder Training in Channels with Impulse Noise |
US8638809B1 (en) * | 2005-08-09 | 2014-01-28 | Adtran, Inc. | Systems and methods for compensating for repetitive impulse noise |
US20140119462A1 (en) * | 2010-07-02 | 2014-05-01 | Futurewei Technologies, Inc. | Method for Accurate Distribution of Time to a Receiver Node in an Access Network |
US9374257B2 (en) | 2005-03-18 | 2016-06-21 | Broadcom Corporation | Methods and apparatuses of measuring impulse noise parameters in multi-carrier communication systems |
US20160233921A1 (en) * | 2013-09-23 | 2016-08-11 | Mithat Dogan | Apparatus, systems and methods for implementing impulse noise mitigation via soft switching |
US20190288782A1 (en) * | 2016-06-13 | 2019-09-19 | Intel Corporation | Method of impulse noise monitoring for time division duplexing systems |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1816776A1 (en) * | 2006-02-07 | 2007-08-08 | Alcatel Lucent | Device and method for mitigating effects of impulse noise on data packet transfer |
EP1944902B1 (en) * | 2007-01-10 | 2012-11-21 | Alcatel Lucent | A method for impulse noise monitoring, related network terminal, network node and network manager |
CN101601195B (en) | 2007-02-01 | 2012-11-14 | 艾利森电话股份有限公司 | Arrangement and method relating to digital subscribe lines |
EP1978668B1 (en) * | 2007-04-02 | 2012-10-24 | Alcatel Lucent | Method for monitoring impulse noise |
EP2001153B1 (en) * | 2007-06-08 | 2015-01-14 | Alcatel Lucent | Autonomous impulse noise mitigation in communication systems |
JP5693734B2 (en) * | 2011-08-25 | 2015-04-01 | 三菱電機株式会社 | Signal transmission device |
EP2893645B1 (en) * | 2012-09-10 | 2018-06-13 | Sony Corporation | Device for power line communication, power line communications system, method for operating a device for power line communication and for adapting plc transmissions to noise |
US9413423B1 (en) * | 2015-08-18 | 2016-08-09 | Texas Instruments Incorporated | SNR calculation in impulsive noise and erasure channels |
US10439761B1 (en) * | 2018-07-24 | 2019-10-08 | Nxp B.V. | Physical layer device and method for performing physical layer operations in a communications network |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3699457A (en) * | 1971-08-11 | 1972-10-17 | Motorola Inc | Noise blanker circuit including rate bias and rate shutoff circuitry and audio blanking |
US4845466A (en) * | 1987-08-17 | 1989-07-04 | Signetics Corporation | System for high speed digital transmission in repetitive noise environment |
US5537437A (en) * | 1993-02-19 | 1996-07-16 | Fujitsu Limited | Initialization equalization for modulation and demodulation using special training pattern |
US5794136A (en) * | 1996-09-24 | 1998-08-11 | Motorola, Inc. | Noise blanker and a radio receiver and method employing same |
US20020069038A1 (en) * | 2000-12-06 | 2002-06-06 | Motorola, Inc. | Apparatus and method for providing adaptive forward error correction utilizing the error vector magnitude metric |
US20020140991A1 (en) * | 2000-10-26 | 2002-10-03 | Catena Networks, Inc. | Optimal bit allocation system for reed-solomon coded data |
US20020150167A1 (en) * | 2001-02-17 | 2002-10-17 | Victor Demjanenko | Methods and apparatus for configurable or assymetric forward error correction |
US6647070B1 (en) * | 1998-09-10 | 2003-11-11 | Texas Instruments Incorporated | Method and apparatus for combating impulse noise in digital communications channels |
US6654410B2 (en) * | 2001-01-16 | 2003-11-25 | Aware, Inc. | Fast initialization using seamless rate adaptation |
US6683855B1 (en) * | 1998-08-31 | 2004-01-27 | Lucent Technologies Inc. | Forward error correction for high speed optical transmission systems |
US6788923B2 (en) * | 2000-02-23 | 2004-09-07 | Mitsubishi Denki Kabushiki Kaisha | Receiver noise reduction with expanding gated pulses |
US6920194B2 (en) * | 2001-05-29 | 2005-07-19 | Tioga Technologies, Ltd. | Method and system for detecting, timing, and correcting impulse noise |
US20060078044A1 (en) * | 2004-10-11 | 2006-04-13 | Norrell Andrew L | Various methods and apparatuses for imulse noise mitigation |
US7050419B2 (en) * | 2001-02-23 | 2006-05-23 | Terayon Communicaion Systems, Inc. | Head end receiver for digital data delivery systems using mixed mode SCDMA and TDMA multiplexing |
US7162676B2 (en) * | 2003-09-22 | 2007-01-09 | Adtran, Inc. | Data communication system and method for selectively implementing forward error correction |
US7428669B2 (en) * | 2003-12-07 | 2008-09-23 | Adaptive Spectrum And Signal Alignment, Inc. | Adaptive FEC codeword management |
US20100229075A1 (en) * | 2001-06-08 | 2010-09-09 | Broadcom Corporation | Chip blanking and processing in scdma to mitigate impulse and burst noise and/or distortion |
Family Cites Families (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1080504A (en) | 1913-12-02 | Elmer A Vary | Gravity-feed can-marking machine. | |
US1056711A (en) | 1908-07-09 | 1913-03-18 | Ferdinand Schaub | Crossover-insulator for electrical conductors. |
US4541091A (en) | 1982-06-11 | 1985-09-10 | Hitachi, Ltd. | Code error detection and correction method and apparatus |
WO1984003808A1 (en) | 1983-03-12 | 1984-09-27 | Sony Corp | Error-correcting apparatus |
DE3483375D1 (en) | 1983-06-22 | 1990-11-15 | Hitachi Ltd | METHOD AND SYSTEM FOR ERROR CORRECTION. |
US4581746A (en) * | 1983-12-27 | 1986-04-08 | At&T Bell Laboratories | Technique for insertion of digital data bursts into an adaptively encoded information bit stream |
JPH061605B2 (en) | 1985-02-08 | 1994-01-05 | 株式会社日立製作所 | Digital signal recording and transmission method |
JPS62120670A (en) * | 1985-11-20 | 1987-06-01 | Sony Corp | Method for correcting error of data |
US20010050943A1 (en) | 1989-08-03 | 2001-12-13 | Mahany Ronald L. | Radio frequency communication network having adaptive communication parameters |
US5214501A (en) | 1988-10-03 | 1993-05-25 | North American Philips Corporation | Method and apparatus for the transmission and reception of a multicarrier high definition television signal |
US4979174A (en) | 1988-12-29 | 1990-12-18 | At&T Bell Laboratories | Error correction and detection apparatus and method |
GB9010637D0 (en) | 1990-05-11 | 1990-07-04 | Secr Defence | A high frequency multichannel diversity differential phase shift(dpsk)communications system |
US5392299A (en) | 1992-01-15 | 1995-02-21 | E-Systems, Inc. | Triple orthogonally interleaed error correction system |
US5765127A (en) * | 1992-03-18 | 1998-06-09 | Sony Corp | High efficiency encoding method |
EP0571096B1 (en) * | 1992-05-18 | 1999-06-23 | Canon Kabushiki Kaisha | Data processing apparatus |
US5287384A (en) | 1992-10-15 | 1994-02-15 | Lxe Inc. | Frequency hopping spread spectrum data communications system |
EP0606016B1 (en) | 1993-01-07 | 2002-10-09 | Kabushiki Kaisha Toshiba | Data communication system using an adaptive hybrid ARQ scheme |
US5995539A (en) | 1993-03-17 | 1999-11-30 | Miller; William J. | Method and apparatus for signal transmission and reception |
US5351016A (en) | 1993-05-28 | 1994-09-27 | Ericsson Ge Mobile Communications Inc. | Adaptively self-correcting modulation system and method |
US5596604A (en) | 1993-08-17 | 1997-01-21 | Amati Communications Corporation | Multicarrier modulation transmission system with variable delay |
US5420640A (en) | 1993-12-03 | 1995-05-30 | Scientific-Atlanta, Inc. | Memory efficient method and apparatus for sync detection |
US5490168A (en) * | 1994-07-08 | 1996-02-06 | Motorola, Inc. | Method and system for automatic optimization of data throughput using variable packet length and code parameters |
KR960006313A (en) | 1994-07-15 | 1996-02-23 | 사또오 후미오 | Transmission mode and transmission device |
FR2723282B1 (en) | 1994-07-29 | 1996-09-13 | Alcatel Telspace | METHOD FOR INTERLEAVING AND DE-INTERLACING SDH FRAMES AND SYSTEM THEREOF |
US5764693A (en) | 1994-11-14 | 1998-06-09 | Research In Motion Limited | Wireless radio modem with minimal inter-device RF interference |
US6421323B1 (en) | 1994-12-23 | 2002-07-16 | Applied Digital Access, Inc. | Method and apparatus for analyzing events in a telecommunications system |
US5751338A (en) | 1994-12-30 | 1998-05-12 | Visionary Corporate Technologies | Methods and systems for multimedia communications via public telephone networks |
US5574747A (en) | 1995-01-04 | 1996-11-12 | Interdigital Technology Corporation | Spread spectrum adaptive power control system and method |
US5546411A (en) | 1995-02-28 | 1996-08-13 | Motorola, Inc. | Method and apparatus for adaptively selecting a communication strategy in a selective call radio communication system |
US5717715A (en) | 1995-06-07 | 1998-02-10 | Discovision Associates | Signal processing apparatus and method |
US5793759A (en) | 1995-08-25 | 1998-08-11 | Terayon Corporation | Apparatus and method for digital data transmission over video cable using orthogonal cyclic codes |
EP0794631A3 (en) | 1996-03-07 | 2001-04-04 | Kokusai Denshin Denwa Co., Ltd | Error control method and apparatus for wireless data communication |
US5828677A (en) | 1996-03-20 | 1998-10-27 | Lucent Technologies Inc. | Adaptive hybrid ARQ coding schemes for slow fading channels in mobile radio systems |
US5699365A (en) | 1996-03-27 | 1997-12-16 | Motorola, Inc. | Apparatus and method for adaptive forward error correction in data communications |
US5764649A (en) | 1996-03-29 | 1998-06-09 | Amati Communications Corporation | Efficient address generation for convolutional interleaving using a minimal amount of memory |
US5764896A (en) | 1996-06-28 | 1998-06-09 | Compaq Computer Corporation | Method and system for reducing transfer latency when transferring data from a network to a computer system |
EP0923821B1 (en) | 1996-09-02 | 2003-09-03 | STMicroelectronics N.V. | Improvements in, or relating to, multi-carrier transmission systems |
US5745275A (en) | 1996-10-15 | 1998-04-28 | Lucent Technologies Inc. | Multi-channel stabilization of a multi-channel transmitter through correlation feedback |
US5903612A (en) | 1996-11-08 | 1999-05-11 | Alcatel Alsthom Compagnie Generale D'electricite | Method to synchronize data and a transmitter and a receiver realizing said method |
US6041057A (en) | 1997-03-24 | 2000-03-21 | Xylan Corporation | Self-configuring ATM network |
AU6969598A (en) | 1997-04-14 | 1998-11-11 | Northern Telecom Limited | Method and system for avoiding communication failure in cdma systems |
US6477669B1 (en) | 1997-07-15 | 2002-11-05 | Comsat Corporation | Method and apparatus for adaptive control of forward error correction codes |
US5917340A (en) | 1997-10-08 | 1999-06-29 | Pericom Semiconductor Corp. | Twisted-pair driver with staggered differential drivers and glitch free binary to multi level transmit encoder |
DK1021901T3 (en) | 1997-10-10 | 2010-03-08 | Daphimo Co B V Llc | Splitless multi-carrier modem |
US6308278B1 (en) | 1997-12-29 | 2001-10-23 | Intel Corporation | Supplying standby voltage to memory and wakeup circuitry to wake a computer from a low power mode |
US6700881B1 (en) | 1998-03-02 | 2004-03-02 | Samsung Electronics Co., Ltd. | Rate control device and method for CDMA communication system |
US6226322B1 (en) | 1998-03-30 | 2001-05-01 | Texas Instruments Incorporated | Analog receive equalizer for digital-subscriber-line communications system |
US6067646A (en) | 1998-04-17 | 2000-05-23 | Ameritech Corporation | Method and system for adaptive interleaving |
US6243369B1 (en) * | 1998-05-06 | 2001-06-05 | Terayon Communication Systems, Inc. | Apparatus and method for synchronizing an SCDMA upstream or any other type upstream to an MCNS downstream or any other type downstream with a different clock rate than the upstream |
WO2000041397A1 (en) | 1999-01-06 | 2000-07-13 | Sarnoff Corporation | Computer system for statistical multiplexing of bitstreams |
US6578162B1 (en) | 1999-01-20 | 2003-06-10 | Skyworks Solutions, Inc. | Error recovery method and apparatus for ADPCM encoded speech |
US7133441B1 (en) * | 1999-02-23 | 2006-11-07 | Actelis Networks Inc. | High speed access system over copper cable plant |
US6473418B1 (en) | 1999-03-11 | 2002-10-29 | Flarion Technologies, Inc. | Orthogonal frequency division multiplexing based spread spectrum multiple access |
EP1161820B1 (en) | 1999-03-12 | 2006-04-19 | Aware, Inc. | Seamless rate adaptive multicarrier modulation system and protocols |
US6754290B1 (en) | 1999-03-31 | 2004-06-22 | Qualcomm Incorporated | Highly parallel map decoder |
US6598188B1 (en) * | 1999-05-10 | 2003-07-22 | Texas Instruments Incorporated | Error-corrected codeword configuration and method |
US6657949B1 (en) | 1999-07-06 | 2003-12-02 | Cisco Technology, Inc. | Efficient request access for OFDM systems |
WO2001011833A1 (en) | 1999-08-06 | 2001-02-15 | Berkeley Concept Research Corporation | High-speed wireless network with a reliable wireless low bit-rate channel |
US6640239B1 (en) | 1999-11-10 | 2003-10-28 | Garuda Network Corporation | Apparatus and method for intelligent scalable switching network |
US6397368B1 (en) * | 1999-12-06 | 2002-05-28 | Intellon Corporation | Forward error correction with channel adaptation |
US6965960B2 (en) | 2000-03-01 | 2005-11-15 | Realtek Semiconductor Corporation | xDSL symbol processor and method of operating same |
KR100360400B1 (en) | 2000-03-16 | 2002-11-13 | 삼성전자 주식회사 | Discrete multitone processor in asymmetric digital subscriber line modem |
US6882634B2 (en) | 2000-04-07 | 2005-04-19 | Broadcom Corporation | Method for selecting frame encoding parameters to improve transmission performance in a frame-based communications network |
US6865190B2 (en) * | 2000-05-01 | 2005-03-08 | Centillium Communications, Inc. | Framing techniques for ADSL systems |
US6742154B1 (en) * | 2000-05-25 | 2004-05-25 | Ciena Corporation | Forward error correction codes for digital optical network optimization |
EP1176765A1 (en) * | 2000-07-24 | 2002-01-30 | Lucent Technologies Inc. | Method and system for providing end-to-end protection in point-to-multipoint access networks |
DE60137657D1 (en) | 2000-08-03 | 2009-03-26 | Infineon Technologies Ag | Flexible tdma systemarchitektur |
US7024592B1 (en) | 2000-08-07 | 2006-04-04 | Cigital | Method for reducing catastrophic failures in continuously operating software systems |
WO2002017043A2 (en) | 2000-08-23 | 2002-02-28 | Novatel Wireless, Inc. | Method and apparatus for a distributed data transfer over multiple independent wireless networks |
US8521142B2 (en) * | 2000-08-23 | 2013-08-27 | Novatel Wireless, Inc. | Method and apparatus for distributed data transfer over multiple independent wireless networks |
WO2002026018A2 (en) * | 2000-09-25 | 2002-04-04 | Centillium Communications, Inc. | Robust signaling techniques in multicarrier systems |
US6732323B1 (en) | 2000-10-12 | 2004-05-04 | 3Com Corporation | Method of selecting initialization parameters for multi-channel data communication with forward error correction |
US6772388B2 (en) | 2000-12-06 | 2004-08-03 | Motorola, Inc | Apparatus and method for providing optimal adaptive forward error correction in data communications |
US7203206B2 (en) | 2001-02-06 | 2007-04-10 | Tioga Technologies Inc. | Data partitioning for multi-link transmission |
US6983414B1 (en) | 2001-03-30 | 2006-01-03 | Cisco Technology, Inc. | Error insertion circuit for SONET forward error correction |
WO2002101341A2 (en) * | 2001-06-08 | 2002-12-19 | Broadcom Corporation | Receiver having integrated spectral analysis capability |
US6928603B1 (en) * | 2001-07-19 | 2005-08-09 | Adaptix, Inc. | System and method for interference mitigation using adaptive forward error correction in a wireless RF data transmission system |
CA2354285A1 (en) | 2001-07-27 | 2003-01-27 | Ramesh Mantha | Method, system and apparatus for transmitting interleaved data between stations |
EP1282245A1 (en) | 2001-07-30 | 2003-02-05 | Telefonaktiebolaget L M Ericsson (Publ) | Channel estimation in a multi carrier transmit diversity system |
AUPR679201A0 (en) | 2001-08-03 | 2001-08-30 | Lucent Technologies Inc. | Path metric normalization of add-compare-select processing |
US6904537B1 (en) | 2001-08-27 | 2005-06-07 | Network Elements, Inc. | Data transmission across asynchronous time domains using phase-shifted data packet |
US6982964B2 (en) | 2001-10-15 | 2006-01-03 | Beering David R | High performance ECL-to-ATM protocol network gateway |
US7024596B2 (en) | 2001-11-12 | 2006-04-04 | Broadcom Corporation | Efficient address generation for interleaver and de-interleaver |
KR100724438B1 (en) | 2001-12-26 | 2007-06-04 | 엘지전자 주식회사 | Memory control apparatus for bsae station modem |
US7197067B2 (en) * | 2002-02-28 | 2007-03-27 | Texas Instruments Incorporated | Parameter selection in a communication system |
US20030193889A1 (en) * | 2002-04-11 | 2003-10-16 | Intel Corporation | Wireless device and method for interference and channel adaptation in an OFDM communication system |
US7418240B2 (en) | 2002-05-03 | 2008-08-26 | Broadcom Corporation | Dynamic adaptation of impaired RF communication channels in a communication system |
JP2003338878A (en) | 2002-05-22 | 2003-11-28 | Nec Corp | Communication system, multiplexer included therein, and method and program for testing line transmission characteristic |
US7278081B1 (en) * | 2002-06-13 | 2007-10-02 | Applied Micro Circuits Corporation | Optical transport network frame structure with in-band data channel and forward error correction |
US6992503B2 (en) * | 2002-07-08 | 2006-01-31 | Viciciv Technology | Programmable devices with convertibility to customizable devices |
EP1429488B1 (en) | 2002-12-09 | 2016-03-09 | Broadcom Corporation | Incremental redundancy support in an EDGE cellular wireless terminal |
EP1576735B1 (en) | 2002-12-16 | 2016-04-06 | Telecom Italia S.p.A. | Address generation for interleavers in turbo encoders and decoders |
US7372901B2 (en) | 2003-04-30 | 2008-05-13 | Harris Corporation | Method and apparatus for modem rate adaptation |
GB2402307A (en) | 2003-05-30 | 2004-12-01 | Nokia Corp | Encapsulating irregular burst transmissions with overhead information specifying the timing interval to the next burst |
US7103828B2 (en) * | 2003-07-24 | 2006-09-05 | Adiran, Inc. | System and method for interleaving and transmitting forward error correction code words |
US7103820B2 (en) * | 2003-09-22 | 2006-09-05 | Adtran, Inc. | System and method for interleaving forward error correction code words across multiple communication connections |
GB2406488A (en) | 2003-09-29 | 2005-03-30 | Nokia Corp | Sigalling in a communications network |
US7623894B2 (en) | 2003-10-09 | 2009-11-24 | Freescale Semiconductor, Inc. | Cellular modem processing |
DE602004011445T2 (en) | 2003-11-03 | 2009-01-15 | Broadcom Corp., Irvine | FEC decoding with dynamic parameters |
US7418644B2 (en) * | 2004-03-01 | 2008-08-26 | Hewlett-Packard Development Company, L.P. | System for error correction coding and decoding |
WO2005086405A2 (en) | 2004-03-03 | 2005-09-15 | Aware, Inc. | Impulse noise management |
-
2005
- 2005-03-03 WO PCT/US2005/006842 patent/WO2005086405A2/en not_active Application Discontinuation
- 2005-03-03 US US10/597,482 patent/US20080232444A1/en not_active Abandoned
- 2005-03-03 EP EP05724394A patent/EP1721403A2/en not_active Withdrawn
- 2005-03-03 EP EP10006702A patent/EP2228936A1/en not_active Withdrawn
- 2005-03-03 CA CA2555757A patent/CA2555757C/en active Active
-
2010
- 2010-04-28 US US12/769,193 patent/US8462835B2/en active Active
-
2013
- 2013-06-11 US US13/914,852 patent/US8594162B2/en active Active
- 2013-11-08 US US14/075,077 patent/US8743932B2/en active Active
-
2014
- 2014-05-23 US US14/285,911 patent/US20140254643A1/en not_active Abandoned
-
2015
- 2015-12-23 US US14/757,630 patent/US20160127079A1/en not_active Abandoned
-
2018
- 2018-09-10 US US16/126,027 patent/US10567112B2/en not_active Expired - Fee Related
-
2019
- 2019-06-21 US US16/448,939 patent/US10805040B2/en active Active
-
2020
- 2020-02-04 US US16/781,802 patent/US11005591B2/en active Active
-
2021
- 2021-04-20 US US17/235,558 patent/US20210242961A1/en not_active Abandoned
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3699457A (en) * | 1971-08-11 | 1972-10-17 | Motorola Inc | Noise blanker circuit including rate bias and rate shutoff circuitry and audio blanking |
US4845466A (en) * | 1987-08-17 | 1989-07-04 | Signetics Corporation | System for high speed digital transmission in repetitive noise environment |
US5537437A (en) * | 1993-02-19 | 1996-07-16 | Fujitsu Limited | Initialization equalization for modulation and demodulation using special training pattern |
US5794136A (en) * | 1996-09-24 | 1998-08-11 | Motorola, Inc. | Noise blanker and a radio receiver and method employing same |
US6683855B1 (en) * | 1998-08-31 | 2004-01-27 | Lucent Technologies Inc. | Forward error correction for high speed optical transmission systems |
US6647070B1 (en) * | 1998-09-10 | 2003-11-11 | Texas Instruments Incorporated | Method and apparatus for combating impulse noise in digital communications channels |
US6788923B2 (en) * | 2000-02-23 | 2004-09-07 | Mitsubishi Denki Kabushiki Kaisha | Receiver noise reduction with expanding gated pulses |
US20020140991A1 (en) * | 2000-10-26 | 2002-10-03 | Catena Networks, Inc. | Optimal bit allocation system for reed-solomon coded data |
US20020069038A1 (en) * | 2000-12-06 | 2002-06-06 | Motorola, Inc. | Apparatus and method for providing adaptive forward error correction utilizing the error vector magnitude metric |
US6654410B2 (en) * | 2001-01-16 | 2003-11-25 | Aware, Inc. | Fast initialization using seamless rate adaptation |
US20020150167A1 (en) * | 2001-02-17 | 2002-10-17 | Victor Demjanenko | Methods and apparatus for configurable or assymetric forward error correction |
US7050419B2 (en) * | 2001-02-23 | 2006-05-23 | Terayon Communicaion Systems, Inc. | Head end receiver for digital data delivery systems using mixed mode SCDMA and TDMA multiplexing |
US6920194B2 (en) * | 2001-05-29 | 2005-07-19 | Tioga Technologies, Ltd. | Method and system for detecting, timing, and correcting impulse noise |
US20100229075A1 (en) * | 2001-06-08 | 2010-09-09 | Broadcom Corporation | Chip blanking and processing in scdma to mitigate impulse and burst noise and/or distortion |
US7162676B2 (en) * | 2003-09-22 | 2007-01-09 | Adtran, Inc. | Data communication system and method for selectively implementing forward error correction |
US7428669B2 (en) * | 2003-12-07 | 2008-09-23 | Adaptive Spectrum And Signal Alignment, Inc. | Adaptive FEC codeword management |
US20090086800A1 (en) * | 2003-12-07 | 2009-04-02 | Cioffi John M | Adaptive fec codeword management |
US20060078044A1 (en) * | 2004-10-11 | 2006-04-13 | Norrell Andrew L | Various methods and apparatuses for imulse noise mitigation |
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10805040B2 (en) | 2004-03-03 | 2020-10-13 | Tq Delta, Llc | Impulse noise management |
US8594162B2 (en) | 2004-03-03 | 2013-11-26 | Tq Delta, Llc | Impulse noise management |
US10567112B2 (en) | 2004-03-03 | 2020-02-18 | Tq Delta, Llc | Impulse noise management |
US11005591B2 (en) | 2004-03-03 | 2021-05-11 | Tq Delta, Llc | Impulse noise management |
US20100220771A1 (en) * | 2004-03-03 | 2010-09-02 | Aware, Inc. | Impulse noise management |
US8743932B2 (en) | 2004-03-03 | 2014-06-03 | Tq Delta, Llc | Impulse noise management |
US8462835B2 (en) | 2004-03-03 | 2013-06-11 | Tq Delta, Llc | Impulse noise management |
US8194722B2 (en) * | 2004-10-11 | 2012-06-05 | Broadcom Corporation | Various methods and apparatuses for impulse noise mitigation |
US7600178B2 (en) * | 2004-10-12 | 2009-10-06 | Ciena Corporation | Methods for the determination of FEC parameters in DMT based xDSL systems in the presence of system imposed constraints |
US20060107170A1 (en) * | 2004-10-12 | 2006-05-18 | Ciena Corporation | Methods for the determination of FEC parameters in DMT based xDSL systems in the presence of system imposed constraints |
US9374257B2 (en) | 2005-03-18 | 2016-06-21 | Broadcom Corporation | Methods and apparatuses of measuring impulse noise parameters in multi-carrier communication systems |
US20060215742A1 (en) * | 2005-03-23 | 2006-09-28 | Texas Instruments Incorporated | Optimizing for impulse noise protection in a DSL system |
US8638809B1 (en) * | 2005-08-09 | 2014-01-28 | Adtran, Inc. | Systems and methods for compensating for repetitive impulse noise |
US8005977B2 (en) * | 2005-12-20 | 2011-08-23 | Lantiq Deutschland Gmbh | Method and apparatus for transmitting data |
US20070143498A1 (en) * | 2005-12-20 | 2007-06-21 | Stefan Uhlemann | Method and apparatus for transmitting data |
US20070195871A1 (en) * | 2006-02-22 | 2007-08-23 | Texas Instruments Incorporated | Performance of DSL modem under impulse noise |
US8064504B2 (en) | 2006-04-20 | 2011-11-22 | Lantiq Deutschland Gmbh | Protection of communication systems against repetitive electrical impulse noise |
US8457218B2 (en) | 2006-04-20 | 2013-06-04 | Lantiq Deutschland Gmbh | Protection of communication systems against repetitive electrical impulse noise |
US20070248181A1 (en) * | 2006-04-20 | 2007-10-25 | Axel Clausen | Protection of communication systems against repetitive electrical impulse noise |
US7738543B2 (en) * | 2006-06-05 | 2010-06-15 | Lantiq Deutschland Gmbh | Methods and systems for determining communication parameters |
US20070280339A1 (en) * | 2006-06-05 | 2007-12-06 | Vladimir Oksman | Methods and systems for determining communication parameters |
US9391744B2 (en) | 2006-07-31 | 2016-07-12 | Adaptive Spectrum And Signal Alignment, Inc. | Method and apparatus for analyzing and mitigating noise in a digital subscriber line |
US8428225B2 (en) * | 2006-07-31 | 2013-04-23 | Adaptive Spectrum And Signal Alignment, Inc. | Method and apparatus for analyzing and mitigating noise in a digital subscriber line |
US20090323903A1 (en) * | 2006-07-31 | 2009-12-31 | Cioffi John M | Method and apparatus for analyzing and mitigating noise in a digital subscriber line |
US8027388B2 (en) | 2006-09-15 | 2011-09-27 | Lantiq Deutschland, GmbH | Methods and systems for adaptive communication |
US20110116573A1 (en) * | 2006-09-15 | 2011-05-19 | Lantiq Deutschland Gmbh | Methods and Systems for Adaptive Communication |
US7899124B2 (en) * | 2006-09-15 | 2011-03-01 | Lantiq Deutschland Gmbh | Methods and systems for adaptive communication |
US20080069248A1 (en) * | 2006-09-15 | 2008-03-20 | Bernd Heise | Methods and systems for adaptive communication |
US7856033B2 (en) * | 2006-11-14 | 2010-12-21 | Lantiq Deutschland Gmbh | Methods and systems for adaptive communication |
US20080112472A1 (en) * | 2006-11-14 | 2008-05-15 | Vladimir Oksman | Methods and systems for adaptive communication |
US7720633B2 (en) * | 2007-01-10 | 2010-05-18 | Futurewei Technologies, Inc. | Bivariate histogram for impulse noise monitor |
US20080167838A1 (en) * | 2007-01-10 | 2008-07-10 | Futurewei Technologies, Inc. | Bivariate histogram for impulse noise monitor |
US8271852B2 (en) * | 2007-02-04 | 2012-09-18 | British Telecommunications Plc | Data recovery scheme |
US20100115374A1 (en) * | 2007-04-02 | 2010-05-06 | Kirkby Robert H | Data recovery scheme |
US8015475B2 (en) * | 2007-07-26 | 2011-09-06 | Texas Instruments Incorporated | Erasure decoding for receivers |
US20090031197A1 (en) * | 2007-07-26 | 2009-01-29 | Texas Instruments Incorporated | Erasure decoding for receivers |
US20100061437A1 (en) * | 2008-09-07 | 2010-03-11 | Conexant Systems, Inc. | Systems and Methods for Impulse Noise Characterization |
US8396688B2 (en) * | 2008-09-07 | 2013-03-12 | Ikanos Communications, Inc. | Systems and methods for impulse noise characterization |
US20100088569A1 (en) * | 2008-10-05 | 2010-04-08 | Ikanos Communications, Inc. | Packet Retransmission |
US8472533B2 (en) | 2008-10-10 | 2013-06-25 | Broadcom Corporation | Reduced-complexity common-mode noise cancellation system for DSL |
US9160381B2 (en) | 2008-10-10 | 2015-10-13 | Broadcom Corporation | Adaptive frequency-domain reference noise canceller for multicarrier communications systems |
US8605837B2 (en) | 2008-10-10 | 2013-12-10 | Broadcom Corporation | Adaptive frequency-domain reference noise canceller for multicarrier communications systems |
US9075696B2 (en) * | 2009-03-09 | 2015-07-07 | Tektronix, Inc. | Apparatus and method for performing burst triggering in a test and measurement instrument |
US20100228508A1 (en) * | 2009-03-09 | 2010-09-09 | Tektronix, Inc. | Apparatus and method for performing burst triggering in a test and measurement instrument |
US8774256B2 (en) * | 2009-07-10 | 2014-07-08 | Futurewei Technologies, Inc. | Method for robust crosstalk precoder training in channels with impulse noise |
US20130215940A1 (en) * | 2009-07-10 | 2013-08-22 | Futurewei Technologies, Inc. | Method for Robust Crosstalk Precoder Training in Channels with Impulse Noise |
US9231754B2 (en) * | 2010-07-02 | 2016-01-05 | Futurewei Technologies, Inc. | Method for accurate distribution of time to a receiver node in an access network |
US20140119462A1 (en) * | 2010-07-02 | 2014-05-01 | Futurewei Technologies, Inc. | Method for Accurate Distribution of Time to a Receiver Node in an Access Network |
US8885781B2 (en) * | 2012-01-17 | 2014-11-11 | Casa Systems, Inc. | System and method for detecting burst noise during quadrature amplitude modulation communications |
US20130182752A1 (en) * | 2012-01-17 | 2013-07-18 | Casa Systems, Inc. | System and Method for Detecting Burst Noise During Quadrature Amplitude Modulation Communications |
US20160233921A1 (en) * | 2013-09-23 | 2016-08-11 | Mithat Dogan | Apparatus, systems and methods for implementing impulse noise mitigation via soft switching |
US20190288782A1 (en) * | 2016-06-13 | 2019-09-19 | Intel Corporation | Method of impulse noise monitoring for time division duplexing systems |
Also Published As
Publication number | Publication date |
---|---|
US10805040B2 (en) | 2020-10-13 |
US20140064343A1 (en) | 2014-03-06 |
WO2005086405A3 (en) | 2005-12-01 |
US10567112B2 (en) | 2020-02-18 |
US8743932B2 (en) | 2014-06-03 |
EP2228936A1 (en) | 2010-09-15 |
US8594162B2 (en) | 2013-11-26 |
EP1721403A2 (en) | 2006-11-15 |
CA2555757C (en) | 2015-01-20 |
CA2555757A1 (en) | 2005-09-15 |
US20210242961A1 (en) | 2021-08-05 |
US20200177304A1 (en) | 2020-06-04 |
US20160127079A1 (en) | 2016-05-05 |
US20130272355A1 (en) | 2013-10-17 |
US20140254643A1 (en) | 2014-09-11 |
US20190312667A1 (en) | 2019-10-10 |
US11005591B2 (en) | 2021-05-11 |
WO2005086405A2 (en) | 2005-09-15 |
US8462835B2 (en) | 2013-06-11 |
US20100220771A1 (en) | 2010-09-02 |
CA2555757E (en) | 2005-09-15 |
US20190007164A1 (en) | 2019-01-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10805040B2 (en) | Impulse noise management | |
CA2548743C (en) | Adaptive fec codeword management | |
US8064592B2 (en) | Adaptive communication systems and methods | |
US20210200628A1 (en) | Crc counter normalization | |
US9258411B2 (en) | Forensic diagnostic capability including G.inp | |
EP1805927A1 (en) | Periodic impulse noise mitigation in a dsl system | |
US7899124B2 (en) | Methods and systems for adaptive communication | |
US7738543B2 (en) | Methods and systems for determining communication parameters |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AWARE, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TZANNES, MR. MARCOS C.;REEL/FRAME:018010/0431 Effective date: 20060725 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: DLI LENDING AGENT, LLC, CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:TQ DELTA, LLC;REEL/FRAME:047212/0551 Effective date: 20181005 |
|
AS | Assignment |
Owner name: ALTER DOMUS (US) LLC, ILLINOIS Free format text: AMENDED AND RESTATED INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:TQ DELTA LLC;REEL/FRAME:054898/0408 Effective date: 20201231 Owner name: ALTER DOMUS (US) LLC, ILLINOIS Free format text: AMENDED AND RESTATED INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:TQ DELTA LLC;REEL/FRAME:054898/0850 Effective date: 20201231 |