Patent Grant
7894327
1. Field of the Invention
The present invention relates to (wireless) receivers, and, in particular, to buffer-based methods for generating Orthogonal Variable Spreading Factor (OVSF) codes for the spreading and despreading of data.
2. Description of the Related Art
When a signal travels through a real-world environment, it often reaches a receiver by multiple paths. These paths occur as a result of the signal reflecting, diffracting, and scattering from various elements in the environment, e.g., mountains, trees, and buildings. Multi-path components are essentially time-delayed variants of a single signal. While, in some applications, these multiple components may result in interference, e.g., ghosting on the display of an analog television receiver, Code Division Multiple Access (CDMA) systems intentionally make use of these multiple components.
The basic principle of CDMA systems is orthogonal coding, whereby, instead of assigning specific frequencies or time slots to each user of a system, the users are distinguished from one another by assigning codes. The codes fulfill the same role as frequency or time in frequency- or time-division systems, i.e., to keep the signals for different users from interfering with one another. In orthogonal spreading, a symbol is XOR-multiplied by a defined sequence of bits called a “code sequence” (also called a “code pattern” or simply a “code”). If the code sequence length is n bits, then each symbol is transformed to n so-called chips. The resulting chip rate, i.e., the number of chips per second (e.g., bits per second), is n times the original symbol rate (number of symbols per second). For example, the spreading code sequence 1111 has a length, also called a spreading or spread factor (SF) or Orthogonal Variable Spreading Factor (OVSF), of four. A single 1 will be spread to the sequence 0000 (1 XOR'ed with 1 gives 0), and a single 0 will be spread to the sequence 1111. In general, code sequences are not arbitrarily chosen, but rather, selected according to certain mathematical rules that provide sets of code sequences that are orthogonal to each other. Orthogonal code sequences have no correlation. Consequently, signals spread with code sequences that are orthogonal to each other do not interfere with one another. For a single connection, input data is spread with a particular code sequence at the transmitter end. To recover the data, the same orthogonal code sequence is used at the receiver end to despread the signal.
Implementation of OVSF spreading and/or despreading operations in a transmitter and/or receiver requires the generation of OVSF codes. The most common and widely used solution requires a chip-rate counter to drive an OVSF generation circuit. The OVSF generation circuit performs an XOR operation between the current count from the chip-rate counter and the OVSF code index in reverse order to produce an OVSF sequence bit every cycle.
However, there is a need for an OVSF code generator that is not limited by the constraints imposed by the use of a chip-rate counter (where count values are used in an algorithm for generating OVSF code sequences), e.g., to be able to generate OVSF codes asynchronously with respect to a chip counter.
The present invention provides buffer-based methods for generating OVSF code sequences without using a chip-rate counter.
In one embodiment, the present invention provides a method of generating a code sequence. The method comprises populating at least one buffer with initial values based on a received spreading factor and desired code index; receiving a timing strobe; changing the values in the at least one buffer upon receipt of the timing strobe based on an algorithm that is independent of any count value associated with the timing strobe; and outputting at least one code sequence value based on the values in the at least one buffer.
In another embodiment, the present invention provides an apparatus for generating a code sequence. The apparatus comprises means for populating at least one buffer with initial values based on a received spreading factor and desired code index; means for receiving a timing strobe; means for changing the values in the at least one buffer upon receipt of the timing strobe based on an algorithm that is independent of any count value associated with the timing strobe; and means for outputting at least one code sequence value based on the values in the at least one buffer.
Other aspects, features, and advantages of the present invention will become more fully apparent from the following detailed description, the appended claims, and the accompanying drawings in which like reference numerals identify similar or identical elements.
At step 203, an initial timing strobe is received. The timing strobe can be a pulse or other time interval identifier that may include an associated counter value (e.g., as may supplied by a chip-rate counter). However, the timing strobe is not required by the present invention to include an associated counter value (e.g., as may be supplied by a global clock), since the algorithms of the various embodiments of the present invention do not require that the timing strobe include count values. Alternatively, in various embodiments of the present invention, the output of a counter may be used merely for timing purposes, such that the algorithm does not employ the count value itself in generating code sequences.
At step 204, at least one buffer is populated with certain initial values based on the values of SF and k. At step 205, another timing strobe is received. At step 206, the values in the buffer change based on an algorithm, such as the First Algorithm or Second Algorithm described below. At step 207, a determination is made whether the change in the buffer values results in the generation of an OVSF code sequence value (i.e., a−1 or a+1), in which case the method proceeds to step 208 so that the OVSF code sequence value can be read out of the buffer. If, at step 207, it is determined that no OVSF code sequence value is generated, then the method returns to step 205 for another timing strobe to be received. At step 209, a determination is made whether the last OVSF code sequence value in the sequence has been generated, in which case the method ends at step 210. If, at step 209, it is determined that the last OVSF code sequence value has not been generated, then the method returns to step 205 for another timing strobe to be received.
Further details of two exemplary algorithms for generating OVSF code patterns without a chip-rate counter, as well as an exemplary time-multiplexed code generator for generating multiple codes at a time using only a single OVSF code generator consistent with the present invention, will now be provided.
In a first exemplary algorithm consistent with the present invention, OVSF code patterns are generated using a recursive function, such as the function ssf provided in the following pseudo-code:
In the above pseudo-code, n is equal to log2 of the spread factor (where n=0 . . . 9), and k is the desired OVSF code index (where k=0 . . . 2n−1). The unary operation “−” in the above pseudo-code describes the negation of each element of the entire sequence generated by the second recursive call of the ssf function (in square brackets). The ssf function may be coded in C as follows:
In the above C code, the sign s of an element in an OVSF sequence is passed on recursively as the third parameter, to offer the same functionality as the unary operator in the above pseudo-code, but in a more convenient fashion for a practical implementation. The value of s in the initial function call is always 0. The operator “˜” describes the inversion of s, i.e., if s is 0, it becomes 1, and if s is 1, it becomes 0.
Turning now to
n is the log2 of the spread factor, n=0 . . . 9;
k is the code index of the desired OVSF code, k=0 . . . [(2n)−1], if k=0 then the OVSF code sequence contains all “1”s;
s is the sign of an element in the spreading code sequence, s=+1 or −1;
c is a recursive function call tag indicating the level of recursion, c=0 or 1, for operations corresponding to the first or second recursive ssf call, respectively; and
SP is the stack pointer, SP=0 . . . 9, which points to the top of the stack that holds n, s, and c.
The stack holds parameters n (4 bits), s (1 bit), and c (1 bit) for operations corresponding to each recursive call of the ssf function. In the algorithm shown in flowchart 300, parameter k (9 bits) is stored on the stack. However, in an alternative embodiment of the algorithm, parameter k could be stored separately from the stack to increase efficiency. For example, the operations of recursively computing k=k/2 (using integer division), storing k on the stack and testing top-of-stack k for being even could be replaced with a single operation of testing the (SP−1) position bit (from the right) of initial k for being “0”. This single operation would replace testing k for being even in step 311 of the flowchart, and the k assignment step k=(k@(SP−1))/2 in step 304 would be removed. The assert operation of step 305 outputs an element of OVSF code sequence, i.e., either +1 or −1, based on whether s is 0 or 1. The coding of s is mapped as follows: +1 is coded as 0, and −1 is coded as 1, to be consistent with the ssf function above.
The method of flowchart 300 begins at step 301, wherein a stack containing variables n, k, s, c, and SP is initialized, and s, c, and SP are set to 0. The values for variables n (log2 of spread factor SF) and k (the OVSF code index of the desired sequence) are received and stored on the top of the stack. At step 302, a determination is made whether top-of-stack n is equal to 0. If top-of-stack n is not equal to 0, then the method proceeds to step 303, wherein SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, n at stack location SP−1 is decremented by 1 and the result stored as top-of-stack n, k at stack location SP−1 is divided by 2 and the result stored as top-of-stack k, top-of-stack c is set to 0, and top-of-stack s is set to the value of s at stack location SP−1, after which the method returns to step 302. If, at step 302, it is determined that top-of-stack n is equal to 0, then the method proceeds to step 305, wherein the assert function is called for top-of-stack s to output a +1 if top-of-stack s is equal to 0, or a −1 if top-of-stack s is equal to 1. Next, at step 306, a determination is made whether SP is equal to 0, in which case the code generation is complete, and the method terminates at step 307. If, at step 306, it is determined that SP is not equal to 0, then the method proceeds to step 308. At step 308, a determination is made whether top-of-stack c is equal to 0. If top-of-stack c is not equal to 0, then the method proceeds to step 309, wherein SP is decremented by 1, after which the method returns to step 306. If, at step 308, it is determined that top-of-stack c is not equal to 0, then the method proceeds to step 310, wherein top-of-stack c is set to 1. Next, at step 311, a determination is made whether k at stack location SP−1 is even, in which case the method proceeds to step 312. At step 312, top-of-stack s is set to the value of s at stack location SP−1, after which the method returns to step 302. If, at step 311, it is determined that k at stack location SP−1 is not even, then the method proceeds to step 213. At step 213, top-of-stack s is set to the inverse of the value of s at stack location SP−1, after which the method proceeds to step 302.
The desired OVSF sequence in this example is the one corresponding to OVSF code index 9, which is: {1, −1, 1, −1, 1, −1, 1, −1, −1, 1, −1, 1, −1, 1, −1, 1}. To arrive at this sequence, the following steps take place (the “iterations” set forth below are provided for ease of reference and merely refer to instances of updating one or more stack variables; the “iterations” do not necessarily correspond to any particular steps or substeps within flowchart 300):
At iteration 1, the stack containing variables n, k, s, c, and SP is initialized at step 301, and s, c, and SP are set to 0. The value for n is set to 4 (for a spread factor SF=16) and the value fork is set to 9 for OVSF code index 9. It is determined at step 302 that top-of-stack n is not equal to 0, and so the method proceeds to step 303.
At iteration 2, the value 0 of SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, the value 4 for n at stack location SP−1 is decremented by 1, and the result 3 is stored as top-of-stack n. The value 9 for k at stack location SP−1 is divided by 2, and the result 4 is stored as top-of-stack k. The value for top-of-stack c is set to 0. The value for top-of-stack s is set to 0, i.e., the value of s at stack location SP−1, and the method returns to step 302. It is determined at step 302 that top-of-stack n is not equal to 0, and so the method proceeds to step 303.
At iteration 3, the value 1 of SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, the value 3 for n at stack location SP−1 is decremented by 1, and the result 2 is stored as top-of-stack n. The value 4 for k at stack location SP−1 is divided by 2, and the result 2 is stored as top-of-stack k. The value for top-of-stack c is set to 0. The value for top-of-stack s is set to 0, i.e., the value of s at stack location SP−1, and the method returns to step 302. It is determined at step 302 that top-of-stack n is not equal to 0, and so the method proceeds to step 303.
At iteration 4, the value 2 of SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, the value 2 for n at stack location SP−1 is decremented by 1, and the result 1 is stored as top-of-stack n. The value 2 for k at stack location SP−1 is divided by 2, and the result 1 is stored as top-of-stack k. The value for top-of-stack c is set to 0. The value for top-of-stack s is set to 0, i.e., the value of s at stack location SP−1, and the method returns to step 302. It is determined at step 302 that top-of-stack n is not equal to 0, and so the method proceeds to step 303.
At iteration 5, the value 3 of SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, the value 1 for n at stack location SP−1 is decremented by 1, and the result 0 is stored as top-of-stack n. The value 1 for k at stack location SP−1 is divided by 2, and the result 0 is stored as top-of-stack k. The value for top-of-stack c is set to 0. The value for top-of-stack s is set to 0, i.e., the value of s at stack location SP−1, and the method returns to step 302. Since top-of-stack n is equal to 0, the method proceeds to step 305, wherein the assert function is called. The assert function outputs a value of +1 because top-of-stack s is equal to 0. At step 306, it is determined that SP is not equal to 0, and the method proceeds to step 308. At step 308, it is determined that top-of-stack c is equal to 0.
At iteration 6, the value for top-of-stack c is set to 1 at step 310. At step 311, it is determined that the value 1 for k at stack location SP−1 is not even. At step 213, the value for top-of-stack s is set to 1, which is the inverse of the value 1 of s at stack location SP−1. The method proceeds to step 302.
At iteration 7, since top-of-stack n is equal to 0, the method proceeds to step 305, wherein the assert function is called. The assert function outputs a value of −1 because top-of-stack s is equal to 1. At step 306, it is determined that SP is not equal to 0, and the method proceeds to step 308.
At iteration 8, at step 308, it is determined that top-of-stack c is not equal to 0, and so, at step 309, SP is decremented by 1, removing the top row from the stack. At step 306, it is determined that SP is not equal to 0, and the method proceeds to step 308. At step 308, it is determined that top-of-stack c is equal to 0, and the method proceeds to step 310, wherein top-of-stack c is set to 1. It is determined at step 311 that the value 2 for k at stack location SP−1 is even. At step 312, the value for top-of-stack s is set to 0, which is the value of s at stack location SP-1.
At iteration 9, the method proceeds to step 302. Since top-of-stack n is not equal to 0, the method proceeds to step 303, wherein the value 3 of SP is incremented by 1, creating a new, empty top-of-stack row. Next, at step 304, the value 1 for n at stack location SP−1 is decremented by 1, and the result 0 is stored as top-of-stack n. The value 1 for k at stack location SP−1 is divided by 2, and the result 0 is stored as top-of-stack k. The value for top-of-stack c is set to 0. The value for top-of-stack s is set to 0, i.e., the value of s at stack location SP−1, and the method returns to step 302. Since top-of-stack n is equal to 0, the method proceeds to step 305, wherein the assert function is called. The assert function outputs a value of +1 because top-of-stack s is equal to 0. At step 306, it is determined that SP is not equal to 0, and the method proceeds to step 308.
The method continues to follow flowchart 300 until step 307 is reached and the method ends, as shown in Iterations 10 through 64 of
In a second exemplary algorithm consistent with the present invention, the OVSF codes are generated using a look-up table (LUT), such as the following Table II, which provides the OVSF codes for a spread factor of 4:
In Table II and in the description below, the set of possible code values {−1,1} is mapped to {1,0} to simplify calculations, as in the first algorithm described above.
With reference now to
As shown in
Desired OVSF code register 502 is a 9-bit register with memory locations N[8:0]. Initially, controller 501 stores the desired OVSF code sequence corresponding to code index k in register 502 by populating the MSB bits of memory locations N[8:0] with the binary representation of the desired OVSF code index k (received from an external source), with the LSB bits of memory locations N[8:0] filled with zero values, i.e., k[MSB], k[MSB-1], . . . , k[LSB], 0, . . . , 0. For example, if k is 9, then desired OVSF code register 502 is filled with the following values: 100100000. While in the example of
LUT 503 is a 4×4 look-up table populated with the OVSF codes shown in Table II above. The values in LUT 503 remain constant and can either be stored permanently in LUT 503 or initialized (e.g., using controller 501) at the beginning of the code generation process to contain the correct values.
As shown in
For each level of pattern buffer 504, controller 501 looks up content in LUT 503 using a specified two-bit sequence and stores in the level of pattern buffer 504 the values read from LUT 503 (i.e., the 4-bit row contents) that correspond to the two-bit sequence provided by desired OVSF code register 502, as follows: The values stored in memory locations N[8:7] are used to look up content for level P0 (bits b0-b3) in LUT 503 to populate pattern buffer 504. The values stored in memory locations N[6:5] are used to look up content for level P1 (bits b4-b7) in LUT 503 to populate pattern buffer 504. The values stored in memory locations N[4:3] are used to look up content for level P2 (bits b8-b11) in LUT 503 to populate pattern buffer 504. The values stored in memory locations N[2:1] are used to look up content for level P3 (bits b12-b15) in LUT 503 to populate pattern buffer 504. The value stored in memory location N[0] concatenated with the value “0” are used to look up content for level P4 (bits b 16 and b 17) in LUT 503 to populate pattern buffer 504.
For example, given a spread factor of SF=256, if the desired OVSF code index is k=169, then controller 501 fills desired OVSF code register 502 with the sequence 10101001;0, which sequence will be used as the LUT index. Next, controller 501 fills pattern buffer 504 with the content shown in the following Table III:
Path buffer 505 has 5 levels, which permits code generator 500 to support a spread factor of up to SF=512. As with pattern buffer 504, the bottom four levels each have 4 bits, and the top level has 2 bits. Controller 501 initializes path buffer 505 to contain the values in the following Table IV:
At each assertion of the timing strobe (i.e., each clock cycle) during the code generation process, controller 501 performs a “walking ones” operation to right-shift circularly (i.e., from left to right in a circular manner) the position of one or more of the “1” bits in path buffer 505, as follows: Level L0 will be shifted one bit to the right, such that the LSB bit is shifted to become the MSB. Level L1 will be shifted one bit to the right only when the LSB of Level L0 turns to “0” from “1”. Similarly, Level L2 has dependency on Level L1 so as to shift one bit to the right only when the LSB of Level L1 turns from “0” to “1”; Level L3 has dependency on Level L2 so as to shift one bit to the right only when the LSB of Level L2 turns from “0” to “1”; and Level L4 has dependency on Level L3 so as to shift one bit to the right only when the LSB of Level L3 turns from “0” to “1”.
Next, for each level of path buffer 505, controller 501 selects a bit in the corresponding level of pattern buffer 504 to send to decision block 506. Controller 501 determines this bit selection by the position of the “1” bit in the corresponding level of path buffer 505. In other words, one bit from each level of pattern buffer 504 at a time is sent to decision block 506, for a total of 5 bits: p0[i], p1[j], p2[k], p3[m], and p4[n].
Decision block 506 performs an XOR operation (or other decision method) among the 5 selected bits p0[i], p1[j], p2[k], p3[m], and p4[n] from pattern buffer 504 to decide the OVSF code. Following the XOR operation, controller 501 performs another “walking ones” operation on the bits of path buffer 505, controller 501 selects another bit from each of the five levels of pattern buffer 504 to send to decision block 506, and decision block 506 performs another XOR operation, and so forth. This process continues until the entire OVSF code sequence has been generated and may be repeated subsequently for one or more additional OVSF code sequences.
With reference to the following Tables V-VIII, the steps of an exemplary code sequence generation will now be provided to illustrate the operation of code generator 500. In this example, the spread factor is SF=16, and the sequence for OVSF code index 9 is requested. Thus, the values SF=16 and k=9 will be provided to controller 501. The corresponding OVSF codes for SF=16 are shown in Table I above. The desired OVSF sequence in this example is the one corresponding to OVSF code index 9, which is: {1, −1, 1, −1, 1, −1, 1, −1, −1, 1, −1, 1, −1, 1, −1, 1}. Mapping the code values {−1,1} to {1,0}, the desired OVSF sequence becomes {0, 1, 0, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 0}. To arrive at this sequence, the following steps take place:
Controller 501 receives the spread factor of 16 and assigns this value to SF. Controller 501 receives the value of the desired OVSF code index, i.e., 9, or {1001} and assigns this value to k. Controller 501 fills desired OVSF code register 502 with the following values: {k[3], k[2], k[1], k[0], k[0], 0, 0, 0, 0}, i.e. {10, 01, 00, 00, 0}.
Pattern buffer 504 is initialized based on the contents of register 502, as follows: For Level P0 of pattern buffer 504, controller 501 looks up content in LUT 503 using the specified two-bit sequence N[8:7] stored in desired OVSF code register 502 (which contains the values “10”), and reads the 4-bit row contents in LUT 503 that correspond to the sequence “10”, i.e., “0101”. Controller 501 then stores the retrieved sequence “0101” in level P0 of pattern buffer 504. For Level P1 of pattern buffer 504, controller 501 looks up content in LUT 503 using the specified two-bit sequence N[6:5] stored in desired OVSF code register 502 (which contains the values “01”), and reads the 4-bit row contents in LUT 503 that correspond to the sequence “01”, i.e., “0011”. Controller 501 then stores the retrieved sequence “0011” in level P1 of pattern buffer 504. For Level P2 of pattern buffer 504, controller 501 looks up content in LUT 503 using the specified two-bit sequence N[4:3] stored in desired OVSF code register 502 (which contains the values “00”), and reads the 4-bit row contents in LUT 503 that correspond to the sequence “00”, i.e., “0000”. Controller 501 then stores the retrieved sequence “0000” in level P2 of pattern buffer 504. For Level P3 of pattern buffer 504, controller 501 looks up content in LUT 503 using the specified two-bit sequence N[2:1] stored in desired OVSF code register 502 (which contains the values “00”), and reads the 4-bit row contents in LUT 503 that correspond to the sequence “00”, i.e., “0000”. Controller 501 then stores the retrieved sequence “0000” in level P3 of pattern buffer 504. For Level P4 of pattern buffer 504, controller 501 looks up content in LUT 503 using the specified one-bit value N[0] stored in desired OVSF code register 502 and concatenates the value of N[0] (which contains the value “0”) with the value “0”. Controller 501 then reads the 4-bit row contents in LUT 503 that correspond to the sequence “00”, i.e., “0000”. Controller 501 then stores the retrieved sequence “00” in level P4 of pattern buffer 504. It is noted that the last two bits of the sequence “0000” are simply ignored, since Level P4 of pattern buffer 504 has storage for only 2 bits. After the foregoing steps for populating pattern buffer 504, the contents of pattern buffer 504 are as shown in the following Table V:
Path buffer 505 has already been prepopulated with the values shown in the following Table VI:
Now, generation of the first bit of the OVSF sequence begins. Controller 501 reads the position of the “1” in Level L0 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P0 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L1 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P1 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L2 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P2 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L3 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P3 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L4 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P4 of pattern buffer 504, which is a “0”. Controller 501 causes the 5-bit sequence p0[i], p1[j], p2[k], p3[m], and p4[n] containing the values read from pattern buffer 504, i.e., “00000”, to be provided to decision block 506.
Decision block 506 performs an XOR operation on the values p0[i], p1[j], p2[k], p3[m], and p4[n] ({0, 0, 0, 0, 0}) of the received sequence “00000” and returns a “0”, which is the first OVSF code bit in the desired sequence corresponding to OVSF code index 9.
After completing the generation of the first OVSF code bit, the contents of Level L0 of path buffer 505 are circularly right-shifted by one bit, so that path buffer 505 now contains the values shown in the following Table VII:
Now, generation of the second bit of the OVSF sequence begins. Controller 501 reads the position of the “1” in Level L0 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P0 of pattern buffer 504, which is a “1”. Next, controller 501 reads the position of the “1” in Level L1 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P1 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L2 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P2 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L3 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P3 of pattern buffer 504, which is a “0”. Next, controller 501 reads the position of the “1” in Level L4 of path buffer 505 and uses this position as an index to read the value that has the same position in Level P4 of pattern buffer 504, which is a “0”. Controller 501 causes the 5-bit sequence p0[i], p1[j], p2[k], p3[m], and p4[n] containing the values read from pattern buffer 504, i.e., “10000”, to be provided to decision block 506.
Decision block 506 performs an XOR operation on the values p0[i], p1[j], p2[k], p3[m], and p4[n] ({1, 0, 0, 0, 0}) of the received sequence “10000” and returns a “1”, which is the second OVSF code bit in the desired sequence corresponding to OVSF code index 9.
After completing the generation of the second OVSF code bit, the contents of Level L0 of path buffer 505 are circularly right-shifted by one bit, so that path buffer 505 now contains the values shown in the following Table VIII:
Generation of the third bit of the OVSF sequence now takes place, and the foregoing process continues in this manner, until the “1” in Level L0 is shifted back into its initial position, at which point the “1” in Level L1 starts to right-shift circularly by one bit. Once the “1” in Level 1 is shifted back into its initial position, the “1” in Level L2 starts to right-shift circularly by one bit, and so forth. When this process is complete, the entire OVSF sequence for OVSF code index 9 {0, 1, 0, 1, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 1, 0}, i.e., {1, −1, 1, −1, 1, −1, 1, −1, −1, 1, −1, 1, −1, 1, −1, 1}, will have been generated efficiently, without the use of a chip-rate counter.
It is noted that the contents of pattern buffer 504 remain unchanged during this entire process and only change if a new OVSF code sequence with a different OVSF code index is requested.
FIG. D illustrates the processing flow and timing of an exemplary time-multiplexed code generator for generating four codes at a time using only a single OVSF code generator consistent with the present invention. In this embodiment, the code generator contains similar hardware components as code generator 500 of
Path buffer 505 is reset to its initial values when a reset signal is asserted. As shown, desired OVSF code register 502 (reg_N) is loaded serially with the corresponding desired OVSF code indices k1, k2, k3, and k4, respectively, at a plurality of instances at which a load_k signal is asserted. Pattern buffer 504 is filled serially with the patterns from LUT 503 based on the current contents of the desired OVSF code register, first with the pattern corresponding to OVSF code index k1, then with the pattern corresponding to OVSF code index k2, then with the pattern corresponding to OVSF code index k3, and then with the pattern corresponding to OVSF code index k4.
Based on the pattern buffer contents corresponding to code index k1 and the contents of the path buffer (which will remain the same for all four code indices), a 5-bit sequence p0[i], p1[j], p2[k], p3[m], and p4[n] containing the values read from the pattern buffer is provided to decision block 506 to obtain the first bit for code index k1. Next, based on the pattern buffer contents corresponding to code index k2 and the contents of the path buffer, a 5-bit sequence p0[i], p1[j], p2 [k], p3[m], and p4[n] containing the values read from the pattern buffer is provided to the decision block to obtain the first bit for code index k2. Next, based on the pattern buffer contents corresponding to code index k3 and the contents of the path buffer, a 5-bit sequence p0[i], p1[j], p2[k], p3[m], and p4[n] containing the values read from the pattern buffer is provided to the decision block to obtain the first bit for code index k3. Next, based on the pattern buffer contents corresponding to code index k4 and the contents of the path buffer, a 5-bit sequence p0[i], p1[j], p2[k], p3[m], and p4[n] containing the values read from the pattern buffer is provided to the decision block to obtain the first bit for code index k4. Additional temporary storage for the 5-bit sequence values p0[i], p1[j], p2[k], p3[m], and p4[n] may be provided but is not necessary if the OVSF bits are being generated on the fly.
Once a first bit has been obtained for each of OVSF code indices k1, k2, k3, and k4, a path_shift signal is asserted to cause a “walking ones” shift in the values in the path buffer. The foregoing process then repeats for the remaining bits for OVSF code indices k1, k2, k3, and k4, until the entire OVSF sequence for OVSF code indices k1, k2, k3, and k4 have been generated. Thus, by time-multiplexing a single OVSF code generator, multiple OVSF codes can be generated at the same time without the use of a plurality of OVSF code generators.
It should be recognized that the process steps of the embodiments described herein may be implemented using many different hardware and/or software devices, and that the hardware configurations described herein are merely exemplary.
While certain embodiments of the present invention disclosed herein relate to 3GPP and UMTS applications, the present invention may have utility in other non-3GPP and non-UMTS contexts, as well.
It should also be recognized that the present invention may be implemented in code generation for despreading in contexts other than OVSF, as well as for descrambling, and that code sequences other than those described herein, consistent with various embodiments of the present invention, are possible.
While the exemplary embodiments of the present invention have been described with respect to processes of circuits, including possible implementation as a single integrated circuit, a multi-chip module, a single card, or a multi-card circuit pack, the present invention is not so limited. As would be apparent to one skilled in the art, various functions of circuit elements may also be implemented as processing steps in a software program. Such software may be employed in, for example, a digital signal processor, micro-controller, or general purpose computer.
The present invention can be embodied in the form of methods and apparatuses for practicing those methods. The present invention can also be embodied in the form of program code embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of program code, for example, whether stored in a storage medium, loaded into and/or executed by a machine, or transmitted over some transmission medium or carrier, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code segments combine with the processor to provide a unique device that operates analogously to specific logic circuits.
It will be further understood that various changes in the details, materials, and arrangements of the parts which have been described and illustrated in order to explain the nature of this invention may be made by those skilled in the art without departing from the scope of the invention as expressed in the following claims.
Although the steps in the following method claims, if any, are recited in a particular sequence with corresponding labeling, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those steps, those steps are not necessarily intended to be limited to being implemented in that particular sequence.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6041034 | Fukumasa et al. | Mar 2000 | A |
| 6222875 | Dahlman et al. | Apr 2001 | B1 |
| 6526065 | Cheng | Feb 2003 | B1 |
| 6552996 | Kim et al. | Apr 2003 | B2 |
| 6646579 | Doetsch et al. | Nov 2003 | B2 |
| 6747947 | Kim et al. | Jun 2004 | B2 |
| 6956948 | Hwang et al. | Oct 2005 | B1 |
| 7239604 | Kim et al. | Jul 2007 | B2 |
| 7289426 | Pappalardo et al. | Oct 2007 | B2 |
| 7586835 | Lee et al. | Sep 2009 | B2 |
| 7765456 | Lilliott et al. | Jul 2010 | B1 |
| 20020006156 | Belaiche | Jan 2002 | A1 |
| 20030105532 | Doetsch et al. | Jun 2003 | A1 |
| 20030108024 | Kang | Jun 2003 | A1 |
| 20050237919 | Pettendorf et al. | Oct 2005 | A1 |
| 20070171812 | Kim et al. | Jul 2007 | A1 |
| 20090135788 | Zuniga et al. | May 2009 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20070064590 A1 | Mar 2007 | US |
