Source: http://patents.com/us-20110019751.html
Timestamp: 2018-05-21 22:45:03
Document Index: 691110847

Matched Legal Cases: ['art 150', 'art 180', 'art 150', 'art 150', 'art 150', 'art 210']

Application # 2011/0019751. ADAPTIVE ALLOCATION FOR VARIABLE BANDWIDTH MULTICARRIER COMMUNICATION - Patents.com
United States Patent Application 20110019751
Tzannes; Marcos ; et al. January 27, 2011
Inventors: Tzannes; Marcos; (Orinda, CA) ; Kechriotis; George; (Arlington, MA) ; Wu; Pui; (Chelmsford, CA)
98101-4010
Serial No.: 897522
Current U.S. Class: 375/259
Class at Publication: 375/259
7. A method, comprising:selecting a first allocation of bits to subchannels for first communication by a transceiver of an apparatus with another transceiver of another apparatus;selecting a second allocation of bits to subchannels for second communication by the transceiver with the other transceiver;causing the transceiver to transmit a flag to the other transceiver; andcausing the transceiver to begin transmission to the other transceiver using the second allocation of bits to subchannels after a predetermined number of frames following transmission of the flag.
[0001]This application relates to the field of electronic communication and more particularly to the field of multiband digital signal communication.
[0002]Conventional multicarrier digital communication is a technique for transmitting and receiving digital signals using a plurality carriers (subchannels) having different frequencies. Each of the subchannels is used to communicate a different portion of the signal. The transmitter divides the signal into a number of components, assigns each component to a specific one of the carriers, encodes each of the carriers according to the component assigned thereto, and transmits each of the carriers. The receiver decodes each received carriers and reconstructs the signal.
[0003]The maximum amount of information that can be encoded onto a particular subcarrier is a function of the signal to noise ratio of the communication channel with respect to that subcarrier. The signal to noise ratio of a communication channel can vary according to frequency so that the maximum amount of information that can be encoded onto one carrier may be different than the maximum amount of information that can be encoded onto another carrier.
[0004]Bit loading is a technique for assigning bits to subchannels according to each subchannel's signal to noise ratio. A bit loading algorithm provides a bit allocation table that indicates the amount of information (in bits) that is to be encoded on each of the carriers. That is, for a multicarrier communication system with J carriers, a bit allocation table B[j] indicates, for each j=1 to J, the amount of information that is to be encoded onto each of the J carriers.
[0005]Shaping the transmission to match the channel characteristics is known. For example, a technique known as "water pouring" was introduced by Gallager in 1968 ("Information Theory and Reliable Communication", page 389) and by Wozencraft in 1965 ("Principles of Communication Engineering", pp. 285-357). Water pouring involves distributing the energy of the transmission signal according to the channel frequency response curve (a plot of the signal to noise ratio as a function of frequency). The frequency response curve is inverted and the available signal energy (the "water") is "poured" into the inverted curve so that more of the energy is distributed into those portions of the channel having the highest signal to noise ratio. In a multicarrier system in which the transmission band is divided into numerous subchannels, throughput can be maximized by putting as many bits in each subcarrier as can be supported given the "water pouring" energy and a desired error rate.
[0006]Other techniques for allocating bits among carriers of multicarrier signal are known. U.S. Pat. No. 4,731,816 to Hughes-Hartogs discloses a bit loading scheme where one bit at a time is incrementally added to each subcarrier until a maximum rate is achieved. Subcarriers that require the least amount of additional power to support an additional bit are selected first.
[0007]U.S. Pat. No. 5,479,477 to Chow et al. discloses a bit loading scheme that is capable of either maximizing the throughput or maximizing the margin for a particular target data rate. Unlike Hughes-Hartogs, Chow et al. determines the bit loading table one carrier at a time (rather than one bit at a time). In Chow et al., all the carriers are sorted in descending order according to the measured signal to noise ratio. The initial subchannels that are selected are the ones capable of carrying the most bits. Using the Chow et al. scheme to maximize the data rate provides a bit loading table similar to that provided by the Hughes-Hartogs algorithm.
[0008]In order for the receiver to correctly interpret the received data, both the transmitter and the receiver must use the same bit loading table. When the bit loading algorithm is performed during the initialization phase of communication, the resulting bit allocation table is communicated between the transmitter and receiver to ensure that both the transmitter and the receiver are using the same bit loading table. However, in the event that the communication channel signal to noise ratio characteristics change during communication, it may be necessary to update/change the bit allocation table to more appropriately match the transmission with the channel characteristics. However, when the bit allocation table is changed, it is necessary to synchronize use of the new table with both the transmitter and the receiver. If the transmitter and the receiver use different bit allocation, tables at any time, the communications link will suffer significant errors in those subchannels in which the bit allocation tables do not agree.
[0009]In addition, determining a new bit allocation table can be time consuming, especially if the bit loading algorithm is computationally intensive, such as that disclosed by Hughes-Hartogs where the bit allocation table is constructed one bit at a time. If the bit allocation table is to be calculated many times during communication between the transmitter and receiver, then spending a relatively long amount of time recalculating the bit allocation table (and hence not communicating data) is undesirable.
[0010]One solution is to simply not change the bit loading table after initialization. However, this may be unacceptable in cases where the communication channel signal to noise ratio changes during data transmission. Accordingly, it is desirable to be able to determine a bit loading table relatively quickly and to be able to synchronize use of the new table by the transmitter and the receiver.
[0011]In accordance with the present invention, a pair of bit allocation tables are maintained at both the transmitter and the receiver. These tables are updated as needed, using measurements of the signal to noise ratio performed on known data transmitted to the receiver in a control frame separate from the data frame. The transmitter signals the receiver as to which of the two tables is to be used for subsequent communication. Preferably, this is done by transmitting a flag from the transmitter to the receiver at some point during the data transmission; this causes the receiver to thereafter switch the bit loading table it is using for communication to synchronize with the corresponding table at the transmitter.
[0012]In the preferred embodiment of the invention, although the invention is not restricted thereto, 69 "frames" of 245.5 microseconds duration each are used to form a "superframe" of 16.94 milliseconds. The first frame of each superframe comprises a control frame that is used to transmit a standard (known) data set from the transmitter to the receiver; the remaining frames contain data. The receiver measures the signal to noise ratios of the received data in this frame for each of the channels and uses this to calculate channel bit allocations for subsequent data transmissions. In practice, it has not been found necessary to calculate the signal to noise ratios for each and every superframe, although this can, of course, be done. Rather, we have found it sufficient for most data transmissions to measure the signal to noise ratios of the channels over several frames, average them, update the bit allocation tables based on the resultant values, and use the bit allocations tables so determined over hundreds or thousands of subsequent frames.
[0013]The bit allocation table updating is performed by comparing the measured signal to noise ratio (SNR) in each channel with a constellation signal to noise ratio SNR[c.sub.j], that has been augmented by a trial noise margin M, SNRa[c.sub.j]=SNR[c.sub.j]+M. The constellation signal to noise ratio, SNR[c.sub.j], specifies the number of bits c.sub.j ("constellation size") that can be transmitted over a channel j given a specific signal to noise ratio SNR.sub.j, where c.sub.j may vary, for example, from 1 to 15. The value of the margin M is dependent on the difference between the amount of data (i.e., number of bits) that can be transmitted across the channels in accordance with the augmented constellation signal to noise ratio SNR.sub.a[c.sub.j] and the amount that is desired to be transmitted (the "target data rate"), N. The value of this margin is varied in order to optimize it for the particular communication conditions as manifested by the measured signal to noise ratios, SNR.sub.j.
[0014]In particular, the total number of bits that may be transmitted over J channels, each characterized by signal to noise ratio SNRj, is
N max = j = 1 J c j , ##EQU00001##
where the respective c.sub.j are determined from the measured signal to noise ratios, SNR.sub.J. See, for example, "Digital Communications" by John G. Proakis, pp. 278ff for channel capacity calculations for quadrature amplitude modulation (QAM) systems, the preferred form of trans-mission for this invention. Preferably, the channel capacity calculations are performed in advance and stored in the form of lookup tables for rapid access. In the preferred embodiment described herein, the margin M is determined as M=(10/J)*(N.sub.max-N). The augmented constellation signal to noise ratio is then given by SNR.sub.a[c.sub.j]=SNR[c.sub.j]+M, and this value is used to determine (e.g., by table lookup as described above) the number of bits that can be transmitted over a channel. By augmenting the constellation signal to noise ratio, SNR[c.sub.j], rather than the channel signal to noise ratio, SNR.sub.j, fewer additions are required, since the range of constellation sizes (e.g., c.sub.j=1 . . . 15) is typically smaller than the range of channels (e.g., j=1 . . . 256).
[0015]As long as the amount of data that can be transmitted over the channels in a given interval differs (as determined by the calculations just described) from the amount of data desired to be transmitted in that interval, i.e., N.sub.max.noteq.N, and assuming that certain other exit conditions have not been satisfied, the receiver cycles through a loop that repeatedly adjusts the margin M and recalculates N.sub.max. To do this, the receiver sets a high margin threshold M.sub.H and a low margin threshold M.sub.L. During those superframes in which the bit allocation table is to be recalculated, the high threshold and low threshold margins are initialized to either a first state (M.sub.H=0, M.sub.L=(10/J)*[N.sub.max-N]) or a second state (M.sub.L=0, M.sub.H=(10/J)*[N.sub.max-N]) dependent on whether N.sub.max is greater than N or less than N.
[0016]Thereafter, in each iteration, either the high or the low margin is adjusted in the search for the condition in which N.sub.max=N. Specifically, at the beginning of subsequent (non-initialization) iterations, the margin is set to the average of the high and low margin thresholds, M=(M.sub.H+M.sub.L)/2, and the augmented constellation signal to noise ratio SNR.sub.a[c.sub.j], the bit allocation table B[.sub.j], and the calculated capacity N.sub.max are determined.
[0017]If the calculated capacity exceeds the desired capacity, i.e., N.sub.max>N, the receiver increases the low margin threshold margin to M, i.e., it sets M.sub.L=M. If the calculated capacity is less than the desired capacity, i.e., N.sub.max<N, the receiver decreases the high threshold, i.e., it sets M.sub.H=M. The iteration then repeats.
[0018]The receiver exits from the loop on the occurrence of any of several conditions. A first occurs when it is determined that N.sub.max=N. This is the desired solution, and represents an optimum equal distribution of margin over the communication channels. A second occurs when the test condition (N.sub.max-N) is diverging. A third occurs when the desired equality is not achieved after a defined number of iterations. In one system implemented according to the preferred embodiment described herein, we have found a limit of 16 iterations sufficient.
[0019]FIG. 1 is a schematic diagram of an ADSL communications system showing bit allocation tables in accordance with the present invention;
[0020]FIG. 2 is a diagram of control and data frames as used in connection with the present invention;
[0021]FIG. 3 is a graph illustrating a multicarrier communication system.
[0022]FIG. 4 is a graph illustrating signal-to-noise ratio as a function of frequency.
[0023]FIG. 5 is a graph illustrating bit loading and margin for a multicarrier communication system.
[0024]FIG. 6 is a flow chart illustrating a bit loading algorithm for a multicarrier communication system.
[0025]FIG. 7 is a flowchart illustrating initialization for the bit loading algorithm of FIG. 6.
[0026]FIG. 8 is a flow chart illustrating operation of a receiver software for calculating, modifying, and synchronizing a change in a bit allocation table used in a multicarrier communication system.
[0027]In FIG. 1, a transmitter 10 for use in asynchronous data subscriber loop (ADSL) communications has first and second bit allocation tables 12 and 14 for use in assigning data to a plurality of channels for transmission to a remote receiver 16 which has corresponding bit allocation tables 20 and 22. The tables operate in pairs under control of a table controller 24 at the transmitter. In accordance with ADSL practice, a digital signal s(t) to be transmitted to a receiver is distributed over a plurality of channels f.sub.1, f.sub.2, . . . f.sub.j, in accordance with channel allocation assignments stored in the bit allocation tables. In particular, the tables B[j] define, for each channel j, the number of bits that can reliably be transmitted over a particular channel at a given bit error rate at the specific signal to noise ratio measured for that channel. These tables are determined as described in detail herein, and may vary from time to time during the course of a transmission.
[0028]At any given time, a single table, e.g., table 12, is used for transmission at the transmitter, and a corresponding table, e.g., table 20, is used for reception at the receiver. These tables are images of each other, i.e., contain the same data, and are used in pairs, so that reliable communication can occur. Similarly, tables 14 and 22 are images of each other and are used in pairs.
[0029]A table control unit 24 at the receiver controls the formation of the bit allocation tables 12, 14, 20, and 22. It Measures the signal to noise ratio on each of the channels f.sub.1, f.sub.2, . . . f.sub.j, compares the measured values with predetermined values defining the bit capacity of a channel at given signal to noise values, augmented with noise margins as described herein, and thus determines the bit allocation for each channel. The allocations so defined are stored in the tables 20 and 22 at the receiver. They are also transmitted back to the transmitter, e.g., via a control channel 26, and are there stored as the tables 12 and 14, respectively. After initial loading, the transmission is advantageously arranged such that only updated tables are transmitted back to the transmitter.
[0030]At the transmitter 10, a table switch unit 28 selects which of the two table pairs (12, 20; 14, 22) are to be used in a given transmission and reception. Typically, a given pair will continue in use until the communication conditions change sufficiently that the bit allocations among the channels change. At that time, a new table must be formed at the receiver, and communicated to the transmitter. When this occurs, the table switch unit 28 typically will switch to the new table for subsequent transmissions. When it does so, it transmits a flag to the receiver that indicates that a switch to the alternative pair is to take place. This switch will usually be made effective as of the next superframe, but may, by prearrangement with the receiver, be made effective at some agreed upon point after that.
[0031]FIG. 2 is a diagram of a superframe 30. It is formed from a control frame 32 and a number of data frames 34. During the control frame interval, the transmitter sends to the receiver a known signal from which the receiver can measure the signal to noise ratio of each of the channels in order to calculate the bit allocations. The remaining frames of the superframe comprise data frames for the transmission of the desired data. In a preferred embodiment of the invention, there are one control frame and 68, data frames, each of 245.5 microsecond duration, for a superframe time of 16.94 milliseconds.
[0032]Referring to FIG. 3, a graph 100 illustrates multicarrier signal transmission. The graph 100 has a horizontal axis 102 representing frequency wherein lower frequencies are toward the left side of the axis 102 while higher frequencies are toward the right side of the axis 102. The graph 100 illustrates that a multicarrier signal, incorporating J discrete carrier signals, is transmitted via carriers at frequencies f.sub.1, f.sub.2, . . . f.sub.j.
[0033]Each of the carriers shown in the graph 100 is capable of transmitting a certain number of bits of information. Accordingly, the total number of bits transmitted via the multicarrier signal is the sum of the number of bits that can be transmitted by each of the carriers. For example, if each of the carriers can transmit three bits of information, then the signal shown in the graph 100 can transmit a total of J*3 bits of information.
[0034]In a preferred embodiment, each of the carriers transmits information using quadrature amplitude modulation NANO, a conventional digital signal encoding technique where different combinations of amplitude and phase of each carrier signal represent different digital values. For example, a carrier signal can be encoded using two different possible amplitudes (A1 and A2) and two different possible phases (P1 and P2) so that the carrier can represent one of four possible values: a first value when the carrier signal has amplitude A1 and P1, a second value corresponding to a combination A1 and P2, a third value corresponding to a combination A2 and P1, and a fourth value corresponding to a combination A2 and P2. The various combinations of amplitude and phase for a given carrier signal is called a "constellation". Note that the number of bits that can be transmitted via a particular carrier is a function of the maximum possible constellation size for that carrier.
[0035]For each carrier, the maximum size of the constellation, and hence the maximum number of bits that can be transmitted via that carrier, is a function of the signal to noise ratio (SNR) of the communication channel and is a function of the desired bit error ratio (BER). The BER is the number of single bit transmission/reception errors per the total number of bits transmitted. Increasing the number of discrete amplitudes and/or phases associated with a particular carrier (i.e., increasing the constellation size) increases the likelihood of bit errors. The BER increases with increasing constellation size because, as the number of discrete amplitudes and/or phases increases, the magnitude of the difference between discrete phases and/or amplitudes decreases and hence the ability of the receiver to distinguish between different phase and/or amplitude values decreases.
[0036]The relationship between BER and SNR is well-known in the art of multicarrier communication. Tables are available that show the minimum SNR that can support a BER of a fixed amount or less for a given constellation size. For example, the table shown below, SNR[c.sub.j], a constellation signal to noise ratio, indicates the minimum SNR needed to transmit a constellation having the indicated size in order to obtain an expected BER of 10.sup.-7 (i.e., an error of one bit per every 10.sup.7 bits that are transmitted.) Note that as the constellation size increases, the minimum required SNR also increases.
TABLE-US-00001 Constellation size c (in bits) SNR requirement 2 14 dB 3 19 dB 4 21 dB 5 24 dB
[0037]Referring to FIG. 4, a graph 110 illustrates a relationship between SNR and frequency for a communication channel transmitting a multicarrier signal having carriers between frequencies f.sub.1 and f.sub.j. A vertical axis 112 of the graph 110 represents SNR. A horizontal axis 114 of the graph 110 represents frequency in a manner similar to that illustrated in connection with the horizontal axis 102 of the graph 100 of FIG. 3.
[0038]A plot 116 shows the relationship between SNR and frequency for the frequencies between f.sub.I and f.sub.J, the lowest and highest (respectively) carrier frequencies for the multicarrier frequency signal. The plot 116 illustrates that the SNR varies according to frequency so that, for example, the SNR at frequency f.sub.m is lower than the SNR at frequency f.sub.n. Based on the table shown above, it is possible that, for a given BER, the constellation size supported by the carrier frequency f.sub.m is smaller than the constellation size supported by the carrier frequency f.sub.n.
[0039]Referring to FIG. 5, graph 120 uses a plot 122 to illustrate a hypothetical relationship between SNR and frequency. The graph 120 is similar to the graph 110 of FIG. 4. The vertical axis of the graph 120, which represents SNR, has superimposed thereon the SNR requirement numbers from the table, shown and discussed above, that relates minimum SNR requirements with constellation size for a BER of 10.sup.-7. The graph 120 shows that an SNR of 14 dB is required to support a constellation size of two bits and that SNR's of 19, 21, and 24 are required to support constellation sizes of three, four, and five bits, respectively. Based on this, it is possible to use the plot 122 to determine a maximum constellation size for each of the carrier frequencies between f.sub.1 and f.sub.j. For example, the plot 122 shows that any carrier frequencies between f.sub.1 and f.sub.a can support a maximum constellation size of four bits since all portions of the plot 122 between f.sub.1 and f.sub.a are greater than 21 dB (the minimum required SNR to support a constellation size of four bits), but less than 24 dB (the minimum SNR for five bits). No carrier frequencies between f.sub.1 and f.sub.a can support a constellation size of five bits at the BER used to generate the minimum SNR requirements.
[0040]The portion of the plot 122 between f.sub.a and f.sub.b is shown in FIG. 5 as being greater than 24 dB. Accordingly, carrier frequencies between f.sub.a and f.sub.b can support a maximum constellation size of at least five bits. Similarly, carrier frequencies between f.sub.b and f.sub.c will support a maximum constellation size of four bits; carrier frequencies between f.sub.c and f.sub.d will support a maximum constellation size of three bits; carrier frequencies between f.sub.d and f.sub.e will support a maximum constellation size of two bits, and carrier frequencies between f.sub.e and f.sub.j will support a maximum constellation size of three bits.
[0041]The difference between the minimum required SNR and the actual transmission channel SNR is called the "margin". For example, the plot 122 shows that if four bits are used at the carrier frequency f.sub.1, the carrier frequency at f.sub.1 will have a margin 124 somewhat greater than zero since the SNR at f.sub.1 is shown in FIG. 5 as being greater than the minimum SNR requirement of 21 dB. Similarly, it is possible to use less than the maximum supported constellation size at a particular carrier frequency. For example, although the plot 122 shows that a carrier at the frequency f.sub.a will support a constellation size of five bits (since the SNR at f.sub.a is 24 dB), it is possible to encode the carrier at the frequency f.sub.a with only three bits. In that case, the margin at the frequency f.sub.a is the difference between the transmission channel SNR at f.sub.a (24 dB) and the SNR required to support a constellation of three bits at frequency f.sub.a (19 dB). Accordingly, the margin at frequency f.sub.a is 5 dB.
[0042]In instances where the multicarrier signal is used to transmit the maximum number of data bits, then the SNR of the communication channel is first measured and then each carrier is set to the maximum supported constellation size. However, in many applications, the multicarrier signal is used to transmit less than the maximum possible number of bits. In those cases, it is advantageous to maximize the overall margin of the signal to thus reduce the error rate. This can be illustrated by a simple example:
[0043]Assume a two-channel multicarrier signal has a maximum constellation size of five bits for the first carrier and four bits for the second carrier. Further assume that it is desirable to use the signal to transmit six bits. One way to allocate the bits among the two carriers is to use the first carrier to transmit five bits and the second carrier to transmit one bit. In that case, however, the margin for the first carrier is relatively small while the margin for the second carrier is relatively large. There will be many more errors for bits transmitted via the first carrier than bits transmitted via the second carrier and, since most of the bits are being transmitted via the first carrier anyway, then the overall error rate of the signal, while below the target BER, is still higher than it has to be in this case. A more advantageous way to allocate the bits might be to allocate three bits to each of the two carriers. In that case, both of the carriers operate with a relatively large margin and the overall error rate of the signal is reduced.
[0044]Of course, in many multicarrier communication applications, there are hundreds of carriers and hundreds to thousands of bits that are transmitted. In addition, it is necessary to allocate the bits in a relatively rapid manner since time spent allocating bits is time not spent communicating information. Furthermore, it may be necessary to reallocate the bits during communication if the channel transmission characteristics change dynamically.
[0045]Referring to FIG. 6, a flow chart 150 illustrates a technique for allocating bits among carriers of a multicarrier signal. Processing begins at a first step 152 where various quantities used to allocate the bits are initialized. These quantities include MH, the high-bound for the margin, ML, the low-bound for the margin, and k, an iteration counter which is described in more detail below. Following step 152 is a step 154 where the margin, M, is calculated by averaging M.sub.H and M.sub.L.
[0046]Following step 154 is a step 156 where a table indicating required SNR for various constellation sizes, RSNR[c], is calculated. RSNR[c] is a table having entries equal to the sum of the margin, M, and the minimum SNR requirements that can support a constellation of size c, and thus comprises an augmented constellation signal to noise ratio, SNRa[c.sub.j]=SNR[c.sub.j]+M. Following step 156 is a step 158 where a bit table, B[j], is calculated. B[j] is a table of the maximum number of bits that can be allocated to each of the carriers f.sub.1, . . . f.sub.j, given the values stored in RSNR[c]. The maximum number of bits are allocated for each carrier in a manner similar to that discussed above in connection with FIG. 5.
[0047]Following step 158 is a step 160 where a value N.sub.max is calculated. N.sub.max represents the maximum number of bits that can be transmitted on the channel and is determined by summing all of the values in the table B[j]. Since the table B[j] contains the maximum number of bits that can be transmitted for each carrier based on the minimum required SNR for each constellation size plus the calculated margin, then M.sub.max represents the maximum number of bits that can be transmitted on the channel wherein each of the carriers has a margin of at least M.
[0048]Following the step 160 is a test step 162 which determines if N.sub.max equals N where N is the number of bits that are to be transmitted using the multicarrier signal. If N.sub.max does in fact equal N, then processing is complete and the bit table B[j] represents an allocation of bits among the carriers of the multicarrier signal wherein each carrier will have a margin at least as large as M.
[0049]If it is determined at the test step 162 that N.sub.max does not equal N, then processing transfers from the test step 162 to a test step 164. Note that if N is less than N.sub.max, then the margin can be increased (in order to decrease N.sub.max) in the next iteration. Similarly, if N is not less than N.sub.max, then the margin is too large and needs to be decreased in the next iteration. If it is determined at the test step 164 that N is less than N.sub.max, the control transfers from the test step 164 to a step 166 where M.sub.L, the low-bound on the margin, is set equal to M. Setting M.sub.L equal to M effectively increases M.sub.L, causing an increase in the value of the margin, M, that will be calculated on the next iteration at the step 154.
[0050]Conversely, if it is determined at the step 164 that N is not less than N.sub.max, then control transfers from the step 164 to a step 168 where M.sub.H, the high-bound on the margin is set equal to M. This effectively decreases the value of M.sub.H, thus causing the value of M to decrease when M is calculated at the step 154 on the next iteration.
[0051]Control transfers from either the step 166 or step 168 to a step 170 where the iteration counter, k, is incremented. Following the step 170 is a test step 172 which determines if the iteration counter is less than the maximum allowable value for the iteration counter, K.sub.max. The iteration counter, k, is used to ensure that the algorithm will terminate after a certain number of iterations even if the terminating condition at the step 162 (i.e., N.sub.max=N) is never met. In a preferred embodiment, K.sub.max equals 16.
[0052]If it is determined at the test step 172 that k is not less than K.sub.max, then control transfers from the step 172 to a step 174 where the remaining bits are either removed or added to the bit table, B[j], as appropriate. Bits are added or removed at the step 174 in a random or pseudo random manner so that the sum of all allocated bits in the table B[j], equals N, the number of bits that are to be transmitted via the multichannel signal. Note that in this instance, there is no guarantee that each of the carriers has a margin of at least M. The step 174 is simply executed in order to finalize the allocation process if the algorithm is unable to meet the termination condition at the step 162.
[0053]If it is determined at the test step 172 that the iteration counter, k, is less than the predetermined maximum value for the iteration counter, then control transfers from the step 172 to a test step 176 which determines if the algorithm is diverging, i.e., if (N.sub.max-N) is increasing. It is desirable for the algorithm to converge so that the value of N.sub.max gets closer to the value of N with each iteration because the algorithm terminates when N.sub.max equals N at the test step 162. However, if it is determined at the test step 176 that the value of N.sub.max is actually getting farther from the value of N with each iteration, then control transfers from the step 176 to the step 174 where the remaining bits are distributed randomly among the values in the table B[j], as discussed above, after which processing is complete.
[0054]If it is determined at the test step 176 that the algorithm is not diverging, then control transfers from the step 176 back to the step 154 where the margin is calculated for the next iteration. The margin calculated at the subsequent iteration 154 will either be less than or greater than the margin calculated on the previous iteration, depending upon whether N was less than N.sub.max or not at the test step 164, as discussed above.
[0055]Referring to FIG. 7, a flow chart 180 illustrates in detail the initialization routine for the step 152 of the flow chart 150 shown in FIG. 6. The initialization routine is entered and processing begins at a step 182 where the transmission characteristics of the channel are measured to determine the signal-to-noise ratio at each of the carrier frequencies of the multicarrier signal. As discussed above in connection with FIG.'S 4 and 5, the transmission channel signal-to-noise ratio may be a function of frequency. Measuring the channel transmission characteristics at the step 182 is discussed in more detail hereinafter.
[0056]Following the step 182 is a step 184 where the minimum required signal-to-noise ratio table, SNR[c], is initialized. As discussed above, for a given bit error ratio (BER), the minimum required SNR for each constellation size, c, can be determined via conventional calculations known in the art or by looking up the values in a textbook. Following the step 184 is a step 186 where the bit table, B[j], is calculated. Calculation of the bit table at the step 186 is similar to calculation of the bit table at the step 158 discussed above in connection with the flow chart 150 of FIG. 6, except that the unaugmented SNR table is SNR[c.sub.j] used at the step 186 rather than the RSNR table which is used at the step 158. Using the SNR table at the step 186 effectively calculates the bit table, B[j], with a margin of zero. Following the step 186 is a step 188 where N.sub.max is calculated. The step 188 is similar to the step 160 discussed above in connection with the flow chart 150 of FIG. 6; N.sub.max is simply the sum of all the entries in the bit table, B[j].
[0057]Following the step 188 is a step 190 where it is determined if N.sub.max equals N. If N.sub.max does equal N at the step 190, then processing is complete for the entire algorithm (not just the initialization portion) since the channel will only support N.sub.max bits of transmission. That is, if N.sub.max equals N at the step 190, there is no point in continuing with the algorithm and calculating a margin since, by default, the channel can transmit no more than N bits.
[0058]If it is determined at the test step 190 that N.sub.max does not equal N, then control transfers from the step 190 to a test step 192 where it is determined if N is less than N.sub.max. Note that if N is not less than N.sub.max at the step 192, then the channel will not support transmission of N bits at the BER used to construct the SNR table at the step 184. That is, the bandwidth of the channel is too low. However, in this case, the algorithm can continue by calculating a negative margin and simply proceeding to maximize the negative margin so that, although the BER that will be achieved will exceed the desired BER, it is still minimized given the requested data rate. In another embodiment, the algorithm can terminate at this point and indicate that the bits cannot be allocated. In yet another embodiment, the algorithm can be rerun using a higher BER and (presumable) lower minimum SNR requirements for the various constellation sizes.
[0059]If it is determined at the step 192 that N is not less than N.sub.max (i.e., the system will be operating with a negative margin) then control transfers from the step 192 to a step 198 where the low-bound on the margin M.sub.L, is set to zero. Following the step 198 is a step 200 where the high-bound on the margin is set using the formula M.sub.K=(10/J*)(N.sub.max-N). Note that, however, in this case the high-bound on the margin will be set to a positive value at the step 200 because N.sub.max-N will be a positive number.
[0060]Following either the step 200 or the step 196, control transfers to a step 202 where the iteration counter that is used to terminate the algorithm after a predetermined number of iterations is set to one. Following the step 202, the initialization routine is exited so that the remaining processing, as discussed above in connection with FIG. 6, can continue.
[0061]The formula used to set M.sub.L at the step 196 and to set M.sub.H at the step 200 provides upper and lower bounds of the margin such that the algorithm converges in a reasonable number of iterations while ensuring that the final margin does not fall outside the range between M.sub.L and M.sub.H. Of course, it is possible to practice the invention using other formulas or techniques for calculating initial values for M.sub.L and M.sub.H.
[0062]Referring to FIG. 8, a flow chart 210 illustrates operation of software used by the receiver to allocate bits among the different carriers of the multicarrier signal and synchronize changes in the bit allocation table with the transmitter. Processing begins at a first test step 262 which determines if the receiver has received a reference frame. A reference frame is a predetermined and detectable frame of special data bits that is provided by the transmitter to the receiver to allow the receiver to determine the channel characteristics. In a preferred embodiment, the reference frame is transmitted periodically, although other conventional techniques can be used to determine whether the reference frame should be sent by the transmitter. The reference frame is recognized by the receiver using any one of a variety of conventional techniques such as a special header in a packet indicating that a reference frame is being provided. Use of a reference frame in connection with multicarrier communication is well-known in the art. If a reference frame is not received at the step 262, the software loops back to the test step 262 to poll for receipt of the reference frame.
[0063]If it is determined at the test step 262 that a reference frame has been received, then control transfers from the step 262 to a step 264 where the errors in the reference frame are measured with respect to the brown constellation distances of the first signal. Note that since the reference frame is a predetermined signal, the receiver can know exactly what was sent by the transmitter. Therefore, any differences between the data received by the receiver and the expected values for signal data can be accounted for by errors induced by the transmission channel. These errors are measured at the step 264.
[0064]Following the step 264 is a step 266 where the receiver determines the channel characteristics based on the errors measured at the step 264. This is done in a conventional manner using techniques for determining channel characteristics based on detected transmission errors. Following the step 266 is a step 268 where the receiver allocates various bits among the carriers using, in a preferred embodiment, the technique disclosed above in connection with FIG.'S 6 and 7.
[0065]Following the step 268 is a test step 270 which determines if the bit allocation table provided at the step 268 is different than the previous bit allocation table. That is, it is determined at the step 270 if there is a difference between the recently-calculated bit allocation table and the previous bit allocation table. If it is determined at the test step 270 that there is no difference (i.e., that the bit allocation table has not changed), then control transfers from the step 270 back to the step 262 where the software waits for the transmitter to send another reference frame. Otherwise, if it is determined at the step 270 that the new bit allocation table is different than the old bit allocation table, then control transfers from the step 270 to a step 272 where a flag is sent from the receiver to the transmitter indicating that the bit allocation table has changed. In a preferred embodiment, the flag is sent at the step 272 via a single carrier of the multicarrier signal that is reserved for use by the transmitter and receiver only for the flag. In another embodiment, the reserved carrier can also be used to transmit the new bit allocation table.
[0066]Following the step 272 is a step 274 where the receiver sends the new bit allocation table, determined at the step 268, to the transmitter. Following the step 274, control transfers back to the test step 262 to poll and wait for the transmitter to send another reference frame.
[0067]While the invention has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent tot hose skilled in the art. Accordingly, the spirit and scope of the present invention is to be limited only by the following claims.
Previous Patent US 20,110,019,750 | Next Patent US 20,110,019,752