one embodiment of the present invention relates to a method of transferring data in a communication system. In the method, an initial impulse noise protection value is determined. A number of redundancy bits is added to blocks of data to form codewords as a function of the initial impulse noise protection value, where the impulse noise protection value corresponds to a number of consecutive symbols that can be corrected. The number of symbols that can be correctly transmitted is changed by changing only the number of redundancy bits added to each block of data.
|
10. A communication device configured to transfer a block of data over a communication line, comprising:
a forward error correction encoder configured to form a codeword by adding a number of redundancy bits to the block of data; and
an interleaver configured to form an interleaved data stream by dividing the codeword into a plurality of interleaver blocks and interleaving the interleaver blocks;
wherein the communication device is configured to frame the interleaved data stream as a series of symbols over the communication line, wherein one symbol is framed to correspond to an integer number of bytes of one of the plurality of interleaver blocks.
1. A method of selectively modifying impulse noise protection in a communication system, comprising:
adding a number of redundancy bits to blocks of data to form codewords, where the number of redundancy bits is capable of correcting up to a pre-determined number of bit errors within each block of data, and where the number of redundancy bits is selected as a function of an initial impulse noise protection value;
separating the codewords into interleaver blocks and interleaving the interleaver blocks to form an interleaved data stream; and
selecting an interleaver depth such that one symbol corresponds to an integer number of bytes of the interleaved data stream.
16. A communication device comprising:
an analyzer for monitoring impulse noise on a transmission line during communication service;
a signal processor for forming codewords having redundancy bits and for interleaving the codewords to form an interleaved data stream;
wherein the signal processor is adapted to adjust impulse noise protection by changing only the number of redundancy bits associated with codewords; and
wherein the signal processor is adapted to selectively distribute an integer number of bytes of a codeword over one symbol; wherein a byte boundary of the codeword is aligned to a boundary of the symbol, or
wherein the signal processor is adapted to selectively distribute an integer number of bytes of an interleaver block over one symbol; wherein a byte boundary of the interleaver block is aligned to a boundary of the symbol.
2. The method of
3. The method of
4. The method of
seamlessly adjusting impulse noise protection from the initial impulse noise protection value to a modified impulse noise protection value.
5. The method of
selectively adapting only the number of redundancy bits.
6. The method of
altering an effective number of correctable bytes per interleaver block.
7. The method of
altering a number of correctable bytes per codeword.
8. The method of
altering the integer number of bytes of the interleaver block.
9. The method of
11. The communication device of
an analyzer configured to monitor the interleaved data stream during communication service and to determine a number of corrupted symbols within a codeword span associated with the codeword.
12. The communication device of
13. The communication device of
14. The communication device of
|
This application claims priority to U.S. Provisional Application Ser. No. 60/844,833 filed Sep. 15, 2006, entitled “Methods and Systems for Adaptive Communication.”
The present invention relates generally to communication methods and systems, and more specifically to adaptive communication service in a communication system.
In today's business climate, industry fortunes rise and fall on whether information is exchanged in an efficient manner. Cell phones, pagers, and the Internet have thrived because each technology allows businesses to exchange critical market information at a moment's notice. In addition, such technologies allow individuals to keep abreast of recent developments with family and friends. In short, many segments of our modern society require instant access to accurate, up-to-the-minute information.
Companies spend significant resources to develop modern communication systems that provide people with such information. As networked communication systems have matured, data rates have increased from 20 kilobits per second (kb/s) in 1975, to 100 Mb/s with modern VDSL. In other words, customers in today's “information age” can receive data approximately 5,000 times as fast as network customers of thirty years ago. To bring customers into this modern “information age”, developers have spent billions of dollars to develop network technologies such as Digital Subscriber Line (DSL) technology, for example. To continue to increase data rates at such a remarkable pace, communication systems developers will likely be required to spend significant capital resources for many years to come.
The data rate at which data is successfully transferred over a communication system generally decreases as the noise increases. Thus, communication systems strive to minimize the effects of various types of noise, such as continuous noise, impulse noise, or combinations thereof. For example, continuous noise (stationary noise) can have randomly distributed values of noise over time, whereas impulse noise (non-stationary noise) generally comprises short bursts of relatively high levels of noise that affect a relatively narrow frequency. In any event, communication systems employ various mechanisms or techniques to combat continuous and impulse noise and/or to correct noise-related data transfer errors.
While the existing methods and systems for combating noise and for correcting noise-related data transfer errors are sufficient for their stated purpose, the methods and systems are not sufficient to accurately account for changes in impulse noise during communication service. Thus, improved methods and systems are needed.
The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention, and is neither intended to identify key or critical elements of the invention nor to delineate the scope of the invention. Rather, the purpose of the summary is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.
One embodiment of the present invention relates to a method of transferring data in a communication system. In the method, an initial impulse noise protection value is determined. A number of redundancy bits is added to blocks of data to form codewords as a function of the initial impulse noise protection value, where the impulse noise protection value corresponds to a number of consecutive symbols that can be corrected. The number of symbols that can be correctly transmitted is changed by changing only the number of redundancy bits added to each block of data. Other embodiments are also disclosed.
The following description and annexed drawings set forth in detail certain illustrative aspects and implementations of the invention. These are indicative of but a few of the various ways in which the principles of the invention may be employed.
The present invention will now be described with reference to the drawings wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures are not necessarily drawn to scale. Although various illustrated embodiments are described and illustrated as a hardware structure, the functionality and corresponding features of the present system can also be performed by appropriate software routines or a combination of hardware and software. Thus, the present invention should not be limited to any particular implementation and shall be construed to cover any implementation that falls within the spirit and scope of the claims.
In one embodiment, the modems 102 and 104 are DSL modems having suitable circuitry for providing DSL communication service over a twisted copper pair generally in accordance with ANSI T1.413 (ADSL), T1.424 (VDSL), G.993.2 (VDSL2) and other DSL standards, including the performance of the tasks and functions described herein. For example, in the illustrated communication system 100, the first modem 102 may be a provider modem that is located at a DSL service provider premises (e.g., CO), while the second modem 104 may be a subscriber modem that is located, for example, in a residential home that receives DSL service (e.g., CPE).
In one embodiment, one or both of the modems 102 and/or 104 are adapted to monitor impulse noise with respect to data received on the transmission line 106 from the other modem during communication service. The modems can analyze the monitored impulse noise and selectively propose appropriate noise protection parameter changes to the other modem. Further, the modems are adapted to cooperatively adjust impulse noise protection as they transfer data on the line 106 (e.g., by selectively adjusting Forward Error Correction (FEC) and interleaver (IL) parameters) according to the observed impulse noise.
The exemplary first modem 102 comprises a transceiver 108 that is coupleable to the line 106 and operates to support communication service (e.g., DSL service) with the second modem 104, specifically a transceiver 110 thereof. The first modem 102 also comprises an application interface 112 to a host system, wherein the second modem 104 also comprises an application interface 114 with a network node (not shown), such as a service subscriber's home computer, for example.
In one embodiment, each modem 102 and 104 can also include a local management system 116 and 118, respectively, which provides communication parameters and control signals to facilitate communication between the modems 102 and 104. In other non-illustrated embodiments, for example, the management system could be centralized or distributed. For example, each local management system can provide sub-carrier bit allocations, gain settings, forward-error-correction (FEC) parameters, interleaver (IL) parameters, and modulation parameters for communicating data to and from the line. The local management systems 116 and 118 of the first and second modems 102 and 104, respectively, exchange FEC, IL, modulation, and other control parameters to provide matching settings of these parameters in both modems (e.g., FEC parameters of FEC encoder will match the FEC parameters of the FEC decoder, and so on). Control information and communication parameters are exchanged between the two modems via a management channel 120, arranged over one or more of the sub-carriers of the line 106, or as an embedded overhead data channel, using any suitable communication or data exchange protocol, so as to coordinate parameters settings, rate adjustments, timing of changes, etc. Each local management system 116, 118 can be configured to adaptively alter the impulse noise protection parameters.
The modems 102 and 104 also include analyzers 122 and 124, respectively, that can monitor impulse noise on the line 106 and selectively recommend changes in the impulse noise protection to the associated local management system 116, 118, respectively. After receiving such a recommendation, the management system, in turn cooperatively interacts with the corresponding management system of the other modem to coordinate synchronized implementation of such changes of impulse noise protection parameters in the system 100 without interrupting the communication service. The management system, in turn, prompts the other modem to provide time markers for FEC and bit distribution changes to co-ordinate changes in the settings of both modems without interrupting communication service.
The analyzers 122 and 124 analyze received data error information and suitable statistics based thereon. If an analyzer determines the current impulse noise protection is ineffectual based on the current impulse noise situation (e.g., uncorrected errors due to impulse noise), the analyzer can recommend increasing impulse noise protection. Conversely, if the current impulse noise protection is deemed to be excessive for the current impulse noise situation, the analyzer may recommend decreasing impulse noise protection to increase efficiency of the system.
In order to carry out the appropriate noise protection parameter changes, the modems 102 and 104 may undergo a variety of procedures to establish a communication service, in which user data is transferred over the line 106 between the modems 102 and 104.
During data transfer 206 (which may also be referred to as “showtime”), modems 102 and 104 transfer user data, wherein care is taken to provide error-limited or error-free data to the user. For example, Forward Error Correction (FEC) and interleaving are two processes used to combat noise during data transfer 206. In various embodiments, the present invention relates to systems and methods that provide for an optimal setting of an FEC encoder and interleaver that will provide greater noise protection against impulse noise, including impulse noise consisting of randomly distributed short impulses. Further, other aspects of the invention relate to how to derive initial FEC and IL parameters without knowledge of the impulse noise characteristics on the line, and how to seamlessly adjust the modems to operate with new FEC and IL parameters which account for impulse noise on the line.
To provide some context for FEC and interleaving, Table 1 below lists several parameters involved in FEC and interleaving in accordance with the present invention. These parameters are discussed below with reference to
TABLE 1
Parameters of an FEC/interleaver and their relations
Parameter
Description
Value
(1)
Fs
Average Symbol rate (without Synch-
For VDSL/ADSL: 4 or 8 kHz
(2)
symbols)
Ts
Symbol duration (incl. pro-rata Synch-
For VDSL/ADSL: 250 or 125 μsec
(3)
symbols)
L
Number of bits loaded per Symbol
(4)
Lbr
Line bit rate
lbr = fs × L = L/Ts
(5)
I
Interleaver block length in bytes
I is integer
(6)
D
Interleaver depth in bytes
D is co-prime with I
(7)
Q
Number of Interleaver blocks per codeword
Q = integer
(8)
N
Code word length in bytes
N = Q × I
(9)
R
Min. Number of redundant bytes per
R
(10)
codeword
tC
Number of correctable bytes per code word
R/2 ≦ tC ≦ R depending on the
(11)
FEC method
NOTE: If the location of the
errored bytes is random, tC = R/2
and can get up to R if the location
of errored bytes is known on
some extend. In DSL standards
tc = R/2 without erasure
decoding used and is close to R
with erasure decoding used)
tB
Effective Number of correctable bytes per
tB = └tC/Q┘;
(12)
interleaver block
tmax
Max. number of correctable bytes per
tmax
(13)
codeword
DE
Span of Erasure-correction in bytes
DE = D × └tC/Q┘ = D × tB
(14)
INP
Impulse Noise Protection Parameter (Equal to
INP = └DE × 8/L┘ = └D × tB × 8/L┘
(15)
the number of completely erased subsequent
Symbols the system can cope with no errors)
DL
Interleaver delay in bytes (End-to-End)
(D − 1) × (I − 1)
(16)
TL
Interleaver delay in seconds (End-to-End)
(D − 1) × (I − 1) × 8/lbr
(17)
CB
Span of the interleaver block in bytes
(D − 1) × (I − 1) +/= D × (I − 1) + 1
(18)
CC
Span of the codeword in bytes
(D − 1) × (I − 1) + N
(19)
SL
Interleaver delay in Symbols
(20)
In setting up the communication service, the modems may agree on a maximum number of correctable bytes per codeword, tmax, which may be determined by the specific modem design or by settings provided by the management system. In various systems, there may be an upper limit for tmax, given by the FEC method utilized.
Referring now to
As shown in
An FEC encoder 302 generates a certain number of redundancy bytes or bits for each block of data. As shown in
Referring back to
As
The algorithm for segment mixing is intended to place segments belonging to the same FEC codeword (e.g., A1, A2, and A3 belong to codeword 320) remotely from each other in the interleaved data stream 332. Thus, during transmission, adjacent segments of one FEC codeword (e.g., A1 and A2; or A2 and A3) are separated by a time period that is associated with the interleaver depth (not shown), while all interleaver blocks of one FEC codeword (e.g., A1 and A2 and A3) are spread over a time period associated with the latency introduced by the interleaver (also referred to as interleaver delay, DL). Although
Because impulse noise is relatively infrequent and corrupts individual symbols or groups of consecutive symbols in the interleaved data stream 332 during a short period of time, interleaving can effectively “even” the load of error-correcting work among several FEC codewords by distributing the errors caused by a single impulse noise burst over the several FEC codewords. For example, if an impulse burst corrupted consecutive symbols spanning segments A1 and B1 of the interleaved data stream 332, the error correcting work could be spread over codewords 320 and 322; thus redundancy bytes 304 and 306 could allow the system to correct the corrupted data.
After the interleaver 330 processes the data, the system 100 divides the interleaved data stream 332 into so-called data frames 334, wherein each data frame contains a number of bits of interleaved data that could be loaded onto a symbol, for example, via a one-to-one mapping, wherein each symbol is an N-dimensional (possibly complex) vector.
In one embodiment, the symbols are framed in a manner such that a first integer number of symbols corresponds to a second integer number of bytes of an interleaver block or FEC codeword, wherein the first and second integers may be equal or unequal. By framing the symbols in this manner, the impulse noise protection (INP) value (which corresponds to a number of consecutive symbols that can be corrected), can be adjusted solely by changing the number of redundancy bits associated with each block. Previously, reconfiguring the INP value “on the fly” required complex processing and/or hardware due to the fact that adjusting the INP value has hereforeto been achieved by changing the interleaving depth. Thus, by allowing the INP value to change as a function of the redundancy bits (without necessarily changing the interleaver depth) the present invention makes it easier to seamlessly adapt the INP value during a communication session.
For example, in the illustrated embodiment of
Further, the manner in which codeword bytes are distributed over symbols can be characterized by a protection-to-correction ratio (PC), wherein PC can be defined as INPmax/tmax. In one embodiment, the system 100 may set PC=1, such that the interleaver depth, D, is only a little greater than L/8, which corresponds to the number of bytes in a symbol. In such embodiments, the interleaver stretches the bytes within an interleaver block such that the bytes are placed one by one into consecutive symbols. In other embodiments, the system may set PC>1, wherein the depth of the interleaver, D, is selected such that some symbols in the span of the interleaver block don't contain bytes of the interleaver block. In still other embodiments, the system can set PC<1, wherein the depth of the interleaver, D, is selected such that some symbols in the span of the interleaver include more than one byte of the interleaver block.
After the data stream is encoded and the symbols are properly framed, the modulator 340 then modulates the outgoing sub-carrier constellations (e.g., using inverse discrete Fourier transform (IDFT)) onto the sub-carriers according to the set bit distribution, and provides the modulated (analog) signals to the line 106 according to sub-carrier power settings. The process by which data is loaded onto the sub-carriers may also be referred to as bit loading.
After the modulated signals traverse the line 106, the modulated signals are received at the second modem 104, specifically the demodulator 350 thereof, which includes suitable analog circuits for interfacing with the line 106. The demodulator 350 of the second modem 104 demodulates the received signals into individual sub-carrier constellations (e.g., using discrete Fourier transform (DFT)), and decodes the received constellations according to the bit distribution parameters (e.g., framing parameters) agreed upon during the initialization.
As shown in
After the demodulator 350 receives the received data stream 352, the deinterleaver 360 un-mixes (de-interleaves) the received data stream. As shown in
After the deinterleaver 360 reassembles the data, as shown in
After the FEC codewords are processed by FEC decoder 370, the resulting data can be reassembled at the application interface 114 (e.g., message “ABCD”) as shown in
Although the communication system 100 and several of its components has been described above, it will be appreciated that the present invention includes countless other variations that are contemplated as falling within the scope of the invention. For example, to further facilitate accurate data transmission, the communication system could also include a scrambler (e.g., positioned between the application interface 112 and the FEC encoder 302) and descrambler (e.g., positioned between the FEC decoder 370 and the application interface 114). Other variations are could also be included.
As one embodiment of FEC and interleaving has now been discussed with regard to various parameters in
In various embodiments, FEC and IL parameters are set during initialization in a manner that provides equal distribution of codeword bytes over DMT symbols. This equal distribution has several advantages. For example, it facilitates the monitoring process (e.g., monitoring impulse noise) because each corrupted symbol can lead to Q corrupted bytes in a codeword. In addition, changing INP is facilitated because increasing tB by one increases INP by one, because decreasing tB by one decreases INP by one and vice versa. Thus, the FEC and IL parameters can be optimized by minimizing the number of redundant bytes R while providing sufficient latency and impulse noise protection. Thus, the system can minimize the number of correctable bytes that are needed to protect the system and still provide adequate impulse noise protection.
In the method 400 of
In step 404 initial data transfer begins and impulse noise is monitored at 406 during data transfer. It is noted at this point that in the illustrated embodiment, the impulse noise monitoring, analysis, and selective protection parameter adjustment features of the invention are undertaken after the start of data transfer. However, the techniques of the present invention may be employed alone or in combination with pre-data transfer parameter adjustments or initialization routines.
In 406, the impulse noise may be monitored during data transfer by accumulating statistics of data transfer errors and analyzing such statistics with respect to the existence of errors due to impulse noise (e.g., in analyzer system 122 or 124 of
At 408-416, the impulse noise protection is selectively adjusted or adapted according to the monitored impulse noise in the channel without interrupting the communication service. At 408, a determination is made as to whether the current impulse noise protection is adequate or sufficient, based on the monitored impulse noise. If not (NO at 408), the impulse noise protection is selectively increased at 410 without interrupting the DSL service, and the method 400 starts modified data transfer at 416 and returns to 406 to continue impulse noise monitoring. In various embodiments it is acceptable that change of FEC parameters is implemented by re-initializing or re-starting the system. In the detailed examples illustrated and described below with respect to
If the current impulse noise protection is sufficient (YES at 408), a determination is made at 412 as to whether the impulse noise protection can be safely reduced. If so (YES at 412), the impulse noise protection is selectively decreased at 414 without service interruption, and the method 400 begins modified data transfer with the new parameters at 416 and returns to 406 to continue impulse noise monitoring. In the exemplary implementations illustrated and described below with respect to
Referring now to
In step 503, which can be carried out prior to data transfer (e.g., during initialization 204 in
In 504, Based on maximum interleaver delay, and the initial INP value, and the maximum INP value, modem 102 calculates the initial optimum FEC and IL parameters and communicates them to modem 104 via the management channel 120. Because these initial parameters are based on impulse noise during a limited time (e.g., during initialization), the initial optimized FEC and IL settings may not capture the real-time (dynamic) characteristics of impulse noise over the line. In particularly advantageous embodiments, FEC and IL parameters are set in a manner that provides equal distribution of codeword bytes over DMT symbols. Further, in various embodiments (e.g., one embodiment in
Still referring to
More specifically, in steps 508-510, the monitoring process starts. In various embodiments, the monitoring process includes receiving a group of consecutive erased DMT symbols and attempting to identify the largest number of consecutively corrupted symbols that needs to be corrected. In other embodiments, the receiver detects the number of erased (severely corrupted symbols) during a consecutive predefined time intervals, associated with the FEC codeword span. In another embodiment, transceiver 108 or 110 evaluates the FEC decoding itself to determine the number of bytes that needs to be corrected in some or all code words and whether the number of corrupted bytes exceeds the number of correctable bytes.
The management systems 116, 118 may work in conjunction with the analyzers 122, 124 to collect the monitored data and apply various thresholds to determine an updated INP value (e.g., the number of severely corrupted DMT symbols in consecutive time spans). The monitoring process can collect statistics over the number of symbols that have been corrupted during a sequence of I symbols. The management systems may evaluate the statistics to provide an updated INP value, expressed in number of symbols that can be protected per I bytes.
At 512 a determination is made whether the updated INP value is greater than the current INP value. If the updated INP value is greater than the initial INP value (YES at 512), then in step 514 the system may determine whether the updated INP value is greater than the maximum INP for which the FEC and IL parameters were initially optimized. If so (YES at 514), the method proceeds to 516 where the system can increase the maximum INP, which may require a change of parameter I and interleaver parameters. Because the system will likely be reconfigured with the new parameters (e.g., I and D), the system may need to undergo re-initialization, because changing I during data transfer may be complex.
If the updated INP value is not greater than the maximum INP (NO at 514), then the method proceeds to 518 wherein the system may decide to selectively increase the impulse noise protection by adjusting the FEC and IL parameters based on the updated INP value. For example, the initiating modem could increase R to increase INP. This decision could be made by either operator (manually) or by the management system 116. As the management system 116 receives the updated INP value over management communication channels, the management system computes a new set (updated set) of the FEC and IL parameters.
There are various ways in which the FEC and IL parameters can be adjusted to increase the impulse noise protection. In one embodiment, codeword bytes are equally distributed over DMT symbols and, thus, the FEC and IL parameters can be adjusted to increase the minimum number of redundant bytes per codeword (R) and reducing the number of interleaver blocks per codeword (Q). In one embodiment, the FEC and IL parameters can be set during initialization in a way such that, when changes in impulse noise protection are required in data transfer, only the value of tB needs to be adjusted while the values of I and D are kept constant, and while L is kept constant to avoid unnecessary changes in bit rate. The impulse noise protection could also be increased in other ways.
As the new settings of FEC and IL parameters are obtained, the management system of the initiating modem starts the process of reconfiguring the FEC encoders and interleavers in 520-524.
In step 520, the initiating modem communicates a new message that includes the modified FEC and IL parameters to the responding modem over the management channel. As the responding modem receives the new parameters, it acknowledges the message by ending either an “unable to comply” message, if its resources are insufficient for new settings, or a time marker indicating the exact position within the interleaved data stream (e.g. exact FEC codeword) when the reconfiguration is to be initiated.
In step 522, both the initiating side and the responding side simultaneously and seamlessly re-configure their FEC and IL parameters, for example, by starting from the first bytes of the first FEC codeword following the time marker, or any other predefined number of FEC codewords following the time marker. The time marker can identify an FEC code word directly or by marking the symbol this codeword is related. After the reconfiguration is accomplished, the system returns to 508 where it continues the monitoring process using new-assigned thresholds and time interval values based on the adjusted FEC and IL parameters.
Referring back to numeral 512, if the updated INP value is not greater than the initial INP value (NO at 512), then the system determines if the impulse noise protection can be safely reduced at 526. If the impulse noise protection cannot be safely reduced (NO at 526), then the FEC and IL parameters are sufficient and cannot be improved for efficiency in 528. Thus, the method returns to 508 where the impulse noise on the line is monitored and analyzed.
If the impulse noise protection can be safely reduced (YES at 526), then the system may decide to selectively improve the efficiency (e.g., by decreasing the impulse noise protection by adjusting the FEC and IL parameters). This decision could be made by either operator (manually) or by the management system 116.
There are various ways in which the FEC and IL parameters can be adjusted to increase the efficiency. In one embodiment, the efficiency could be increased by increasing the number of interleaver blocks per codeword (Q) and decreasing the minimum number of redundant bytes per codeword (R). The system could also increase the efficiency in other ways. After the system adjusts the FEC and IL parameters to increase the efficiency in step 526, the system undergoes the message exchange and implements the modified parameters as previously discussed in steps 520-524, after which impulse noise on the line is again monitored and characterized.
Referring now to
In this method, during initialization we set:
tB=INP, (34)
wherein INP is the current value for impulse noise protection. Notably, although this expression is set during initialization, it is retained during data transfer. Thus, the range of valid D values becomes independent from the INP parameter. D is limited by equations (15), (17) and (32) of Table 1 as:
L/8≦D≦1+SLmax×(L/8)/(I−1), (35)
Thus, the number of different values of D given by (35) is:
ND=2+└(SLmax/(I−1))×Lmin/8┘−┌Lmin/8┐, (36)
where SLmax=TLmax/Ts is derived from the maximum allowed interleaver delay, and Lmin is the minimum number of bits per symbol. The TLmax (maximum latency allowed for the service deployed) and Lmin/Ts=lbrmin (minimum line bit rate required for the service deployed) are provided by the management system. The next step is to try
I=┌SLmax┐, (37)
It can be seen from (36) that this is the maximum value for I that generally results in one or more possible values for D.
Next the method determines the values of D that are co-prime with I. Depending on the prime factor(s) of 1, there can be a list of subsequent values for D that are not co-prime with 1. Since D is not yet known, ND has to be bigger than the number of elements in this list. Otherwise there can be cases where at a given Lmin no D exists that is co-prime with I. If that can not be established, one embodiment of this invention is to select a smaller value for 1. A solution is for example to decrement the current value of I by 1. This time ND will be larger and the new value of I has other prime factors. If ND is still too small, and I has again to many common prime factors with D, the value of I can be decremented again and so forth.
For example, assume lbrmin=3.2 Mbit/s and SLmax=30 then we have Lmin=800 and I=30. This results in ND=5. After activation the line bit rate results in a value L=910, for which equation (35) requires that D has to be between 114 and 118. But none of these possible values for D is co-prime with I=30. Therefore we have to set I=29 and now this fulfils all requirements.
In the procedure described with reference to
In other embodiments, FEC settings can be optimized to maximize the FEC codeword length N. This would make the system more robust. Such embodiments could use the maximum possible value of Q:
Q=minimum(└tmax/tB┘, └Nmax/I┘) (38)
wherein Nmax is the maximum length of the FEC codeword allowed either by the implementation or by the type of forward error correction used. With that the code word still remains equally distributed over the symbols however here Q Bytes per codeword are transmitted per symbol.
Thus, the method in
Thus, the procedure in
Referring now to
pc=INPmax/tmax (40)
It is a preferred solution that every value of tB fulfils the requirements for another value of the INP parameter and that the full range of tB up to tmax can be used. This may not be achieved when pc<1. as may be the case in (40). However, the following discussion would also give consistent results.
We define the rule for tB in an actual noise scenario, instead of (34), to:
tB=┌INP/pc┐, (44)
where “pc” is a constant throughout the whole Showtime while INP and consequently tB would change according to the noise environment. The VDSL2 standard defines integer values of INP only up to 16. For VDSL2 pc can only be less or equal 2 inclusive. For pc>1 the (35) to (37) have to be changed accordingly:
To make D again independent from the current tB (35) converts into:
pc×L/8≦D≦1+SLmax×(L/8)/(I−1), (45)
The minimum number of possible values of D is then instead of (36):
ND=2+└(SLmax/(I−1))×Lmin/8┘−┌pc×Lmin/8┐, (46)
Now we try I=┌SLmax./pc┐ (47) instead of (37).
The remainder of the procedure is identical as described previously.
Instead of the method given in
Referring now to
pc=INPmax/tm<1 (50)
Where tm is the minimum number of correctable bytes that are needed to protect INPmax symbols with a codeword length that is high enough that doesn't exceed the decoding capabilities of the system.
We define the rule for tB in an actual noise scenario, instead of (34), to:
tB=┌INP/pc┐, (54)
Again “pc” is a constant throughout the whole Showtime while INP and consequently tB would change according to the noise environment. The VDSL2 standard defines integer values of INP only up to 16. For VDSL2 pc can only be between 1 and 2 inclusive. For pc>1 the (35) to (37) have to be changed accordingly:
To make D again independent from the current tB (35) converts into:
pc×L/8≦D≦1+SLmax×(L/8)/(I−1) (55)
The minimum number of possible values of D is then instead of (36):
ND=2+└(SLmax/(I−1))×Lmin/8┘−┌pc×Lmin/8┐ (56)
Now we try I=┌SLmax./pc┐ instead of (37). (57)
The remainder of the procedure is identical as described previously.
Although the invention has been illustrated and described with respect to one or more implementations, alterations and/or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular regard to the various functions performed by the above described components or structures (blocks, units, engines, assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the invention. In addition, while a particular feature of the invention may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising”.
Heise, Bernd, Oksman, Vladimir
Patent | Priority | Assignee | Title |
8027379, | Jan 10 2007 | INTEL GERMANY GMBH & CO KG | Monitoring and adjusting noise parameters |
8027388, | Sep 14 2007 | Maxlinear, Inc | Methods and systems for adaptive communication |
Patent | Priority | Assignee | Title |
5983388, | Aug 25 1997 | Ikanos Communications, Inc | Forward error correction arrangement (FEC) for multipoint to single point communication systems |
7519124, | May 13 2005 | INTEL GERMANY GMBH & CO KG | Method for seamless bit rate adaptation for multicarrier DSL |
7630489, | Sep 16 2004 | INTEL GERMANY GMBH & CO KG | Adaptive communication systems and methods |
7738543, | Jun 05 2006 | Maxlinear, Inc | Methods and systems for determining communication parameters |
20050138524, | |||
20070248181, | |||
20070280339, | |||
20080052609, | |||
20080112472, | |||
20080165905, | |||
20080232444, | |||
20080285510, | |||
20100054150, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Sep 14 2007 | Lantiq Deutschland GmbH | (assignment on the face of the patent) | / | |||
Nov 14 2007 | OKSMAN, VLADIMIR | Infineon Technologies North America Corp | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 020225 | /0918 | |
Nov 15 2007 | HEISE, BERND | Infineon Technologies AG | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 020226 | /0088 | |
Jan 14 2008 | Infineon Technologies North America Corp | Infineon Technologies AG | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 020372 | /0515 | |
Jul 03 2009 | Infineon Technologies AG | INFINEON TECHNOLOGIES WIRELESS SOLUTIONS GMBH | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 024474 | /0937 | |
Nov 06 2009 | INFINEON TECHNOLOGIES WIRELESS SOLUTIONS GMBH | Lantiq Deutschland GmbH | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 024529 | /0656 | |
Nov 16 2010 | Lantiq Deutschland GmbH | DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT | GRANT OF SECURITY INTEREST IN U S PATENTS | 025406 | /0677 | |
Mar 03 2015 | Lantiq Deutschland GmbH | LANTIQ BETEILIGUNGS-GMBH & CO KG | MERGER SEE DOCUMENT FOR DETAILS | 044907 | /0045 | |
Mar 03 2015 | LANTIQ BETEILIGUNGS-GMBH & CO KG | LANTIQ BETEILIGUNGS-GMBH & CO KG | MERGER AND CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 045085 | /0292 | |
Mar 03 2015 | Lantiq Deutschland GmbH | LANTIQ BETEILIGUNGS-GMBH & CO KG | MERGER AND CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 045085 | /0292 | |
Apr 15 2015 | DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT | LANTIQ BETEILIGUNGS-GMBH & CO KG | RELEASE OF SECURITY INTEREST RECORDED AT REEL FRAME 025413 0340 AND 025406 0677 | 035453 | /0712 | |
Jul 10 2020 | LANTIQ BETEILIGUNGS-GMBH & CO KG | Intel Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 053259 | /0678 | |
Jul 31 2020 | Intel Corporation | Maxlinear, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 053626 | /0636 | |
Jul 08 2021 | Exar Corporation | Wells Fargo Bank, National Association | SECURITY AGREEMENT | 056816 | /0089 | |
Jul 08 2021 | MAXLINEAR COMMUNICATIONS, LLC | Wells Fargo Bank, National Association | SECURITY AGREEMENT | 056816 | /0089 | |
Jul 08 2021 | Maxlinear, Inc | Wells Fargo Bank, National Association | SECURITY AGREEMENT | 056816 | /0089 |
Date | Maintenance Fee Events |
Mar 29 2011 | ASPN: Payor Number Assigned. |
Mar 29 2011 | RMPN: Payer Number De-assigned. |
Aug 28 2014 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Aug 23 2018 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Sep 01 2022 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Mar 01 2014 | 4 years fee payment window open |
Sep 01 2014 | 6 months grace period start (w surcharge) |
Mar 01 2015 | patent expiry (for year 4) |
Mar 01 2017 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 01 2018 | 8 years fee payment window open |
Sep 01 2018 | 6 months grace period start (w surcharge) |
Mar 01 2019 | patent expiry (for year 8) |
Mar 01 2021 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 01 2022 | 12 years fee payment window open |
Sep 01 2022 | 6 months grace period start (w surcharge) |
Mar 01 2023 | patent expiry (for year 12) |
Mar 01 2025 | 2 years to revive unintentionally abandoned end. (for year 12) |