EP1446722A1 - User equipment (ue) having a hybrid parallel/serial bus interface - Google Patents

User equipment (ue) having a hybrid parallel/serial bus interface

Info

Publication number
EP1446722A1
EP1446722A1 EP02789726A EP02789726A EP1446722A1 EP 1446722 A1 EP1446722 A1 EP 1446722A1 EP 02789726 A EP02789726 A EP 02789726A EP 02789726 A EP02789726 A EP 02789726A EP 1446722 A1 EP1446722 A1 EP 1446722A1
Authority
EP
European Patent Office
Prior art keywords
data
data block
interface
bits
nibble
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP02789726A
Other languages
German (de)
French (fr)
Other versions
EP1446722A4 (en
Inventor
Joseph Gredone
Alfred Stufflet
Timothy A. Axness
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Technology Corp
Original Assignee
InterDigital Technology Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/990,060 external-priority patent/US7069464B2/en
Application filed by InterDigital Technology Corp filed Critical InterDigital Technology Corp
Priority to EP05104800A priority Critical patent/EP1575173B1/en
Priority to EP05104801A priority patent/EP1575174B1/en
Publication of EP1446722A1 publication Critical patent/EP1446722A1/en
Publication of EP1446722A4 publication Critical patent/EP1446722A4/en
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M9/00—Parallel/series conversion or vice versa
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/14—Channel dividing arrangements, i.e. in which a single bit stream is divided between several baseband channels and reassembled at the receiver

Definitions

  • the invention relates to bus data transfers.
  • the invention relates to reducing the number of lines used to transfer bus data.
  • Figure 1 One example of a bus used to transfer data is shown in Figure 1.
  • Figure 1 One example of a bus used to transfer data is shown in Figure 1.
  • a communication station such as a base station or user equipment, transmits (TX) and receives (RX) signals.
  • TX transmits
  • RX receives
  • the GCs 30, 32 adjust the gain on the RX and TX signals.
  • a GC controller 38 is used to control the gain parameters for the GCs 30, 32.
  • the GC controller 38 uses a power control bus, such as a sixteen line bus 34, 36, to send a gain value for the TX 36 and RX 34 signals, such as eight lines for each.
  • the power control bus lines 34, 36 allow for a fast data transfer, it requires either many pins on the GCs 30, 32 and the GC controller 38 or many connections between the GCs 30, 32 and GC controller 38 on an integrated circuit (IC), such as an application specific IC (ASIC).
  • IC integrated circuit
  • ASIC application specific IC
  • Increasing the number of pins requires additional circuit board space and connections.
  • Increasing IC connections uses valuable IC space. The large number of pins or connections may increase the cost of a bus depending on the implementation.
  • a hybrid serial/parallel bus interface has a data block demultiplexing device.
  • the data block demultiplexing device has an input configured to receive a data block and demultiplexes the data block into a plurality of nibbles.
  • a parallel to serial converter converts the nibble into serial data.
  • a line transfers each nibble's serial data.
  • a serial to parallel converter converts each nibble's serial data to recover that nibble.
  • a data block reconstruction device combines the recovered nibbles into the data block.
  • Figure 1 is an illustration of a RX and TX GC and a GC controller.
  • Figure 2 is a block diagram of a hybrid parallel/serial bus interface.
  • Figure 3 is a flow chart for transferring data blocks using a hybrid parallel/serial bus interface.
  • Figure 4 illustrates demultiplexing a block into a most significant and least significant nibble.
  • Figure 5 illustrates demultiplexing a block using data interleaving.
  • Figure 6 is a block diagram of a bi-directional hybrid parallel/serial bus interface.
  • Figure 7 is a diagram of an implementation of one bi-directional line.
  • Figure 8 is a timing diagram illustrating start bits.
  • Figure 9 is a block diagram of a function controllable hybrid parallel/serial bus interface.
  • Figure 10 is a timing diagram of start bits for a function controllable hybrid parallel/serial bus interface.
  • Figure 11 is a table of an implementation of start bits indicating functions.
  • Figure 12 is a block diagram of a destination controlling hybrid parallel/serial bus interface.
  • Figure 13 is a table of an implementation of start bits indicating destinations.
  • Figure 14 is a table of an implementation of start bits indicating destinations/functions .
  • Figure 15 is a block diagram of a destinations/functions controlling hybrid parallel/serial bus interface.
  • Figure 16 is a flow chart for start bits indicating destinations/functions.
  • Figure 17 is a block diagram for a positive and negative clock edge hybrid parallel/serial bus interface.
  • Figure 18 is a timing diagram for a positive and negative clock edge hybrid parallel/serial bus interface.
  • Figure 19 is a block diagram of a 2-line GC/GC controller bus.
  • Figure 20 is a block diagram of a 3-line GC/GC controller bus.
  • Figure 2 is a block diagram of a hybrid parallel/serial bus interface
  • Figure 3 is a flow chart of hybrid parallel/serial bus interface data transfer.
  • a data block is to be transferred across the interface i 44 from node 1 50 to node 2 52.
  • a data block demultiplexing device 40 receives the block and demultiplexes it into i nibbles for transfer over i data transfer lines 44, (56).
  • the value for i is based on a tradeoff between number of connections and transfer speed.
  • One approach to determine i is to first determine a maximum latency permitted to transfer the data block. Based on the allowed maximum latency, a minimum number of lines required to transfer the block is determined. Using the minimum number of lines, the lines used to transfer the data is selected to be at least the minimum.
  • the lines 44 may be the pins and their associated connections on a circuit board or connections on an IC.
  • One approach to demultiplex into nibbles divides the block into a most significant to a least significant nibble. To illustrate for an eight bit block transfer over two lines as shown in Figure 4, the block is demultiplexed into a four bit most significant nibble and a four bit least significant nibble. [0032] Another approach interleaves the block across the i nibbles. The first i bits of the block become the first bit in each nibble. The second i bits become the second bit in each nibble and so on until the last i bits. To illustrate for an eight bit block over two connections as shown in Figure 5, the first bit is mapped to the first bit of nibble one. The second bit is mapped to the first bit of nibble two. The third bit is mapped to the second bit of nibble one and so on until the last bit is mapped to the last bit of nibble two.
  • Each nibble is sent to a corresponding one of i parallel to serial (P/S) converters 42, (58), converted from parallel bits to serial bits, and transferred serially across its line, (60).
  • P/S parallel to serial
  • S/P serial to parallel
  • Each S/P converter 46 converts the transmitted serial data into its original nibble, (62).
  • the i recovered nibbles are processed by a data block reconstruction device 48 to reconstruct the original data block, (64).
  • the i connections are used to transfer data in both directions as shown in Figure 6. Information data may be transferred in both directions or information may be sent in one direction and an acknowledgment sent back in the other direction.
  • a data block for transfer from node 1 50 to node 2 52 is received by the data block demultiplexing and reconstruction device 66.
  • the demultiplexing and reconstruction device 66 demultiplexes the block into i nibbles, i P/S converters 68 convert each nibble into serial data.
  • a set of multiplexers (MUXs)/DEMUXs 71 couples each P/S converter 68 to a corresponding one of the i lines 44.
  • another set of MUXs/DEMUXs 75 connects the lines 44 to a set of S/P converters 72.
  • the S/P converters 72 convert the received serial data of each nibble into the originally transmitted nibbles.
  • the received nibbles are reconstructed by a data block demultiplexing and reconstruction device 76 into the original data block and output as the received data block.
  • a data block is received by the data block demultiplexing and reconstruction device 76. That block is demultiplexed into nibbles and the nibbles are sent to a set of P/S converters 74.
  • the P/S converters 74 convert each nibble into serial format for transfer across the i lines 44.
  • a Node 2 set of MUXs/DEMUXs 75 couples the P/S converters 74 to the i lines 44 and a Node 1 set of MUXs/DEMUXs 71 couples the lines 44 to i S/P converters 70.
  • the S/P converters 70 convert the transmitted data into its original nibbles.
  • FIG. 7 is a simplified diagram of one implementation of bidirectional switching circuits.
  • the serial output from the node 1 P/S converter 68 is input into a tri-statable buffer 78.
  • the buffer 78 has another input coupled to a voltage representing a high state.
  • the output of the buffer 78 is the serial data which is sent via the line 85 to a Node 2 tri-statable buffer 84.
  • a resistor 86 is coupled between the line 85 and ground.
  • the Node 2 buffer 84 passes the serial data to a Node 2 S/P converter 72.
  • the serial output from the Node 2 P/S converter 74 is input into a tri- statable buffer 72. That buffer 72 also having another input coupled to a high voltage.
  • the serial output of that buffer 82 is sent via the line 85 to a Node 1 tri-statable buffer 80.
  • the Node 1 buffer 80 passes the serial data to a Node 1 S/P converter 70.
  • some of the i lines 44 may transfer data in one direction and the other i lines 44 transfer data in another direction.
  • a data block is received for transmission to Node 2 52. Based on the data throughput rate required for the block and the traffic demand in the opposite direction, j, being a value from 1 to i, of the connections are used to transfer the block.
  • the block is broken into j nibbles and converted to j sets of serial data using j of the i P/S converters 68.
  • a corresponding number of j Node 2 S/P converters 72 and the Node 2 data block separation and reconstruction device 76 recovers the data block.
  • up to i-j or k lines are used to transfer block data.
  • a synchronous clock is used to synchronize the timing of the various components.
  • a start bit is sent. As shown in Figure 8, each line is at its normal zero level. A start bit is sent indicating the beginning of the block transfer. In this example, all the lines send a start bit, although it is only necessary to send a start bit over one line. If a start bit, such as a one value, is sent over any line, the receiving node realizes that the block data transfer has begun.
  • Each serial nibble is sent through its corresponding line. After transfer of the nibbles, the lines return to their normal state, such as all low.
  • the start bits are also used as an indicator of functions to be performed.
  • An illustration of such an implementation is shown in Figure 9.
  • Figure 10 if any of the connections's first bits are a one, the receiving node realizes block data is to be transferred.
  • Figure 11 for a GC controller implementation, three combinations of start bits are used, "01,” “ 10" and " 11.” "00" indicates a start bit was not sent. Each combination represents a function.
  • "01" indicates that a relative decrease function should be performed, such as decreasing the data block value by 1.
  • a " 10” indicates that a relative increase function should be performed, such as increasing the data block value by 1.
  • a " 11 " indicates an absolute value function, where the block maintains the same value.
  • the start bits indicate a destination device.
  • the combination of start bits relates to a destination device 88-92 for the transferred data block.
  • a "01" represents device 1; a "10” represents device 2; and a "11" represents device 3.
  • the reconstructed block is sent to the corresponding device 88-92.
  • additional start bits may be used. For n starting bits over each of i lines, up to i n + 1 - 1 devices are selected.
  • the start bits may be used to represent both function and destination device.
  • Figure 14 shows a three connection system having two devices, such as a RX and TX GC. Using the start bit for each line, three functions for two devices is shown. In this example, the start bit for line 3 represents the target device, a "0" for device 1 and a “ 1" for device 2.
  • the bits for connections 2 and 3 represent the performed function.
  • a "11” represents an absolute value function; a "10” represents a relative increase function; and a "01” represents a relative decrease. All three start bits as a zero, "000,” is the normal non-data transfer state and "001" is not used. Additional bits may be used to add more functions or devices. For n starting bits over each of i lines, up to i n+ l -1 function/device combinations are possible.
  • Figure 15 is a block diagram for a system implementing the start bits indicating both function and destination device.
  • the recovered nibbles are received by the data block reconstruction device 48.
  • the processing device 86 Based on the received start bits, the processing device 86 performs the indicated function and the processed block is sent to the indicated destination device 88-92.
  • the start bits indicating the function/destination are added to each nibble, (94).
  • the nibbles are sent via the i lines, (96).
  • the proper function is performed on the data block, the data block is sent to the appropriate destination or both, (98).
  • FIG. 17 An odd P/S device set 102, having i P/S devices, has its clock signal inverted by an invertor 118. As a result, the inverted clock signal is half a clock cycle delayed with respect to the system clock.
  • a set of i MUXs 106 select at twice the clock rate between the even P/S device set 104 and the odd P/S device set 102.
  • the resulting data transferred over each connection is at twice the clock rate.
  • At the other end of each connection is a corresponding DEMUX 108.
  • the DEMUXs 108 sequentially couple each line 44 to an even 112 and odd 110 buffer, at twice the clock rate.
  • Each buffer 112, 110 receives a corresponding even and odd bit and holds that value for a full clock cycle.
  • An even 116 and odd 114 set of S/P devices recover the even and odd nibbles.
  • a data block reconstruction device 122 reconstructs the data block from the transferred nibbles.
  • Figure 18 illustrates the data transfer over a line of a system using the positive and negative clock edge. Even data and odd data to be transferred over line 1 is shown. The hatching indicates the negative clock edge data in the combined signal and no hatching the even. As shown, the data transfer rate is increased by two.
  • Figure 19 is a preferred implementation of the hybrid parallel/serial interface used between a GC controller 38 and a GC 124.
  • a data block such as having 16 bits of GC control data (8 bits RX and 8 bits TX), is sent from the GC controller 38 to a data block demultiplexing device 40. The data block is demultiplexed into two nibbles, such as two eight bit nibbles.
  • a start bit is added to each nibble, such as making 9 bits per nibble.
  • the two nibbles are transferred over two lines using two P/S converters 42.
  • the S/P converters 46 1 upon detecting the start bh convert the received nibbles to parallel format.
  • the data block reconstruction device reconstructs the original 16 bits to control the gain of the GC 124. If a function is indicated by the start bits, such as in Figure 11, the AGC 124 performs that function on the received block prior to adjusting the gain.
  • Figure 20 is another preferred implementation for a hybrid parallel/serial converter, using three (3) lines, between a GC controller 38 and a RX GC 30 and TX GC 32.
  • the GC controller 38 sends a data block to the GC 30, 32 with proper RX and TX gain values and start bits, such as per Figure 14. If the start bits per Figure 14 are used, Device 1 is the RX GC 30 and Device 2 is the TX GC 32.
  • the data block demultiplexing device 40 demultiplexes the data block into three nibbles for transfer over the three lines. Using the three P/S converters 42 and three S/P converters 46, the nibbles are transferred serially over the lines and converted into the original nibbles.
  • the data block reconstruction device 48 reconstructs the original data block and performs the function as indicated by the start bits, such as relative increase, relative decrease and absolute value. The resulting data is sent to either the RX or TX GC 30, 32 as indicated by the start bits.

Landscapes

  • Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Systems (AREA)
  • Communication Control (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Dc Digital Transmission (AREA)

Abstract

A hybrid serial/parallel bus interface for a user equipment (UE) has a data block demultiplexing device (40). The data block demultiplexing device has an input configured to receive a data block and demultiplexes the data block into a plurality of nibbles. For each nibble, a parallel to serial converter (42) converts the nibble into serial data. A line (44) transfers each nibble's serial data. A serial to parallel converter (46) converts each nibble's serial data to recover that nibble. A data block reconstruction device (48) combines the recovered nibbles into the data block.

Description

[0001 ] USER EQUIPMENT (UE) HAVING A
HYBRID PARALLEL/SERIAL BUS INTERFACE
[0002] BACKGROUND
[0003] The invention relates to bus data transfers. In particular, the invention relates to reducing the number of lines used to transfer bus data.
[0004] One example of a bus used to transfer data is shown in Figure 1. Figure
1 is an illustration of a receive and transmit gain controllers (GCs) 30, 32 and a GC controller 38 for use in a wireless communication system. A communication station, such as a base station or user equipment, transmits (TX) and receives (RX) signals. To control the gain of these signals, to be within the operating ranges of other reception/transmission components, the GCs 30, 32 adjust the gain on the RX and TX signals.
[0005] To control the gain parameters for the GCs 30, 32, a GC controller 38 is used. As shown in Figure 1, the GC controller 38 uses a power control bus, such as a sixteen line bus 34, 36, to send a gain value for the TX 36 and RX 34 signals, such as eight lines for each. Although the power control bus lines 34, 36 allow for a fast data transfer, it requires either many pins on the GCs 30, 32 and the GC controller 38 or many connections between the GCs 30, 32 and GC controller 38 on an integrated circuit (IC), such as an application specific IC (ASIC). Increasing the number of pins requires additional circuit board space and connections. Increasing IC connections uses valuable IC space. The large number of pins or connections may increase the cost of a bus depending on the implementation.
[0006] Accordingly, it is desirable to have other data transfer approaches.
[0007] SUMMARY
[0008] A hybrid serial/parallel bus interface has a data block demultiplexing device. The data block demultiplexing device has an input configured to receive a data block and demultiplexes the data block into a plurality of nibbles. For each nibble, a parallel to serial converter converts the nibble into serial data. A line transfers each nibble's serial data. A serial to parallel converter converts each nibble's serial data to recover that nibble. A data block reconstruction device combines the recovered nibbles into the data block.
[0009] BRIEF DESCRIPTION OF THE DRAWLNG(S)
[0010] Figure 1 is an illustration of a RX and TX GC and a GC controller.
[0011] Figure 2 is a block diagram of a hybrid parallel/serial bus interface.
[0012] Figure 3 is a flow chart for transferring data blocks using a hybrid parallel/serial bus interface.
[0013] Figure 4 illustrates demultiplexing a block into a most significant and least significant nibble.
[0014] Figure 5 illustrates demultiplexing a block using data interleaving.
[0015] Figure 6 is a block diagram of a bi-directional hybrid parallel/serial bus interface.
[0016] Figure 7 is a diagram of an implementation of one bi-directional line.
[0017] Figure 8 is a timing diagram illustrating start bits.
[0018] Figure 9 is a block diagram of a function controllable hybrid parallel/serial bus interface.
[0019] Figure 10 is a timing diagram of start bits for a function controllable hybrid parallel/serial bus interface.
[0020] Figure 11 is a table of an implementation of start bits indicating functions.
[0021] Figure 12 is a block diagram of a destination controlling hybrid parallel/serial bus interface.
[0022] Figure 13 is a table of an implementation of start bits indicating destinations. [0023] Figure 14 is a table of an implementation of start bits indicating destinations/functions .
[0024] Figure 15 is a block diagram of a destinations/functions controlling hybrid parallel/serial bus interface.
[0025] Figure 16 is a flow chart for start bits indicating destinations/functions.
[0026] Figure 17 is a block diagram for a positive and negative clock edge hybrid parallel/serial bus interface.
[0027] Figure 18 is a timing diagram for a positive and negative clock edge hybrid parallel/serial bus interface.
[0028] Figure 19 is a block diagram of a 2-line GC/GC controller bus.
[0029] Figure 20 is a block diagram of a 3-line GC/GC controller bus.
[0030] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S) [0031 ] Figure 2 is a block diagram of a hybrid parallel/serial bus interface and
Figure 3 is a flow chart of hybrid parallel/serial bus interface data transfer. A data block is to be transferred across the interface i 44 from node 1 50 to node 2 52. A data block demultiplexing device 40 receives the block and demultiplexes it into i nibbles for transfer over i data transfer lines 44, (56). The value for i is based on a tradeoff between number of connections and transfer speed. One approach to determine i is to first determine a maximum latency permitted to transfer the data block. Based on the allowed maximum latency, a minimum number of lines required to transfer the block is determined. Using the minimum number of lines, the lines used to transfer the data is selected to be at least the minimum. The lines 44 may be the pins and their associated connections on a circuit board or connections on an IC. One approach to demultiplex into nibbles divides the block into a most significant to a least significant nibble. To illustrate for an eight bit block transfer over two lines as shown in Figure 4, the block is demultiplexed into a four bit most significant nibble and a four bit least significant nibble. [0032] Another approach interleaves the block across the i nibbles. The first i bits of the block become the first bit in each nibble. The second i bits become the second bit in each nibble and so on until the last i bits. To illustrate for an eight bit block over two connections as shown in Figure 5, the first bit is mapped to the first bit of nibble one. The second bit is mapped to the first bit of nibble two. The third bit is mapped to the second bit of nibble one and so on until the last bit is mapped to the last bit of nibble two.
[0033] Each nibble is sent to a corresponding one of i parallel to serial (P/S) converters 42, (58), converted from parallel bits to serial bits, and transferred serially across its line, (60). On the opposing end of each line is a serial to parallel (S/P) converter 46. Each S/P converter 46 converts the transmitted serial data into its original nibble, (62). The i recovered nibbles are processed by a data block reconstruction device 48 to reconstruct the original data block, (64). [0034] In another, bidirectional, approach, the i connections are used to transfer data in both directions as shown in Figure 6. Information data may be transferred in both directions or information may be sent in one direction and an acknowledgment sent back in the other direction. A data block for transfer from node 1 50 to node 2 52 is received by the data block demultiplexing and reconstruction device 66. The demultiplexing and reconstruction device 66 demultiplexes the block into i nibbles, i P/S converters 68 convert each nibble into serial data. A set of multiplexers (MUXs)/DEMUXs 71 couples each P/S converter 68 to a corresponding one of the i lines 44. At node 2 52, another set of MUXs/DEMUXs 75 connects the lines 44 to a set of S/P converters 72. The S/P converters 72 convert the received serial data of each nibble into the originally transmitted nibbles. The received nibbles are reconstructed by a data block demultiplexing and reconstruction device 76 into the original data block and output as the received data block.
[0035] For blocks transferred from Node 2 52 to Node 1 50, a data block is received by the data block demultiplexing and reconstruction device 76. That block is demultiplexed into nibbles and the nibbles are sent to a set of P/S converters 74. The P/S converters 74 convert each nibble into serial format for transfer across the i lines 44. A Node 2 set of MUXs/DEMUXs 75 couples the P/S converters 74 to the i lines 44 and a Node 1 set of MUXs/DEMUXs 71 couples the lines 44 to i S/P converters 70. The S/P converters 70 convert the transmitted data into its original nibbles. The data block demultiplexing and reconstruction device 66 reconstructs the data block from the received nibbles to output the received data block. Since data is only sent in one direction at a time, this implementation operates in a half duplex mode. [0036] Figure 7 is a simplified diagram of one implementation of bidirectional switching circuits. The serial output from the node 1 P/S converter 68 is input into a tri-statable buffer 78. The buffer 78 has another input coupled to a voltage representing a high state. The output of the buffer 78 is the serial data which is sent via the line 85 to a Node 2 tri-statable buffer 84. A resistor 86 is coupled between the line 85 and ground. The Node 2 buffer 84 passes the serial data to a Node 2 S/P converter 72. Similarly, the serial output from the Node 2 P/S converter 74 is input into a tri- statable buffer 72. That buffer 72 also having another input coupled to a high voltage. The serial output of that buffer 82 is sent via the line 85 to a Node 1 tri-statable buffer 80. The Node 1 buffer 80 passes the serial data to a Node 1 S/P converter 70. [0037] In another implementation, some of the i lines 44 may transfer data in one direction and the other i lines 44 transfer data in another direction. At Node 1 50, a data block is received for transmission to Node 2 52. Based on the data throughput rate required for the block and the traffic demand in the opposite direction, j, being a value from 1 to i, of the connections are used to transfer the block. The block is broken into j nibbles and converted to j sets of serial data using j of the i P/S converters 68. A corresponding number of j Node 2 S/P converters 72 and the Node 2 data block separation and reconstruction device 76 recovers the data block. In the opposite direction, up to i-j or k lines are used to transfer block data. [0038] In a preferred implementation of the bidirectional bus for use in a gain control bus, a gain control value is sent in one direction and an acknowledgment signal is sent back. Alternately, a gain control value is sent in one direction and a status of the gain control device in the other direction.
[0039] One implementation of the hybrid parallel/serial interface is in a synchronous system and is described in conjunction with Figure 8. A synchronous clock is used to synchronize the timing of the various components. To indicate the start of the data block transfer, a start bit is sent. As shown in Figure 8, each line is at its normal zero level. A start bit is sent indicating the beginning of the block transfer. In this example, all the lines send a start bit, although it is only necessary to send a start bit over one line. If a start bit, such as a one value, is sent over any line, the receiving node realizes that the block data transfer has begun. Each serial nibble is sent through its corresponding line. After transfer of the nibbles, the lines return to their normal state, such as all low.
[0040] In another implementation, the start bits are also used as an indicator of functions to be performed. An illustration of such an implementation is shown in Figure 9. As shown in Figure 10, if any of the connections's first bits are a one, the receiving node realizes block data is to be transferred. As shown in the table of Figure 11 for a GC controller implementation, three combinations of start bits are used, "01," " 10" and " 11." "00" indicates a start bit was not sent. Each combination represents a function. In this illustration, "01" indicates that a relative decrease function should be performed, such as decreasing the data block value by 1. A " 10" indicates that a relative increase function should be performed, such as increasing the data block value by 1. A " 11 " indicates an absolute value function, where the block maintains the same value. To increase the number of available functions, additional bits are used. For example, 2 starting bits per line are mapped to up to seven (7) functions or n starting bits for i lines are mapped up to in + 1 - 1 functions. The processing device 86 performs the function on the received data block as indicated by the starting bits. [0041 ] In another implementation as shown in Figure 12, the start bits indicate a destination device. As illustrated in Figure 13 for a two destination device/two line implementation, the combination of start bits relates to a destination device 88-92 for the transferred data block. A "01" represents device 1; a "10" represents device 2; and a "11" represents device 3. After receipt of the start bits of the data block reconstruction device 48, the reconstructed block is sent to the corresponding device 88-92. To increase the number of potential destination devices, additional start bits may be used. For n starting bits over each of i lines, up to in + 1 - 1 devices are selected.
[0042] As illustrated in the table of Figure 14, the start bits may be used to represent both function and destination device. Figure 14 shows a three connection system having two devices, such as a RX and TX GC. Using the start bit for each line, three functions for two devices is shown. In this example, the start bit for line 3 represents the target device, a "0" for device 1 and a " 1" for device 2. The bits for connections 2 and 3 represent the performed function. A "11" represents an absolute value function; a "10" represents a relative increase function; and a "01" represents a relative decrease. All three start bits as a zero, "000," is the normal non-data transfer state and "001" is not used. Additional bits may be used to add more functions or devices. For n starting bits over each of i lines, up to in+l -1 function/device combinations are possible.
[0043] Figure 15 is a block diagram for a system implementing the start bits indicating both function and destination device. The recovered nibbles are received by the data block reconstruction device 48. Based on the received start bits, the processing device 86 performs the indicated function and the processed block is sent to the indicated destination device 88-92.
[0044] As shown in the flow chart of Figure 16, the start bits indicating the function/destination are added to each nibble, (94). The nibbles are sent via the i lines, (96). Using the start bits, the proper function is performed on the data block, the data block is sent to the appropriate destination or both, (98).
[0045] To increase the throughput in a synchronous system, both the positive
(even) and negative (odd) edge of the clock are used to transfer block data. One implementation is shown in Figure 17. The data block is received by a data block demultiplexing device 100 and demultiplexed into two (even and odd) sets of i nibbles. Each set of the i nibbles is sent to a respective set of i P/S devices 102, 104. As shown in Figure 17, an odd P/S device set 102, having i P/S devices, has its clock signal inverted by an invertor 118. As a result, the inverted clock signal is half a clock cycle delayed with respect to the system clock. A set of i MUXs 106 select at twice the clock rate between the even P/S device set 104 and the odd P/S device set 102. The resulting data transferred over each connection is at twice the clock rate. At the other end of each connection is a corresponding DEMUX 108. The DEMUXs 108 sequentially couple each line 44 to an even 112 and odd 110 buffer, at twice the clock rate. Each buffer 112, 110 receives a corresponding even and odd bit and holds that value for a full clock cycle. An even 116 and odd 114 set of S/P devices recover the even and odd nibbles. A data block reconstruction device 122 reconstructs the data block from the transferred nibbles.
[0046] Figure 18 illustrates the data transfer over a line of a system using the positive and negative clock edge. Even data and odd data to be transferred over line 1 is shown. The hatching indicates the negative clock edge data in the combined signal and no hatching the even. As shown, the data transfer rate is increased by two. [0047] Figure 19 is a preferred implementation of the hybrid parallel/serial interface used between a GC controller 38 and a GC 124. A data block, such as having 16 bits of GC control data (8 bits RX and 8 bits TX), is sent from the GC controller 38 to a data block demultiplexing device 40. The data block is demultiplexed into two nibbles, such as two eight bit nibbles. A start bit is added to each nibble, such as making 9 bits per nibble. The two nibbles are transferred over two lines using two P/S converters 42. The S/P converters 461 upon detecting the start bh convert the received nibbles to parallel format. The data block reconstruction device reconstructs the original 16 bits to control the gain of the GC 124. If a function is indicated by the start bits, such as in Figure 11, the AGC 124 performs that function on the received block prior to adjusting the gain.
[0048] Figure 20 is another preferred implementation for a hybrid parallel/serial converter, using three (3) lines, between a GC controller 38 and a RX GC 30 and TX GC 32. The GC controller 38 sends a data block to the GC 30, 32 with proper RX and TX gain values and start bits, such as per Figure 14. If the start bits per Figure 14 are used, Device 1 is the RX GC 30 and Device 2 is the TX GC 32. The data block demultiplexing device 40 demultiplexes the data block into three nibbles for transfer over the three lines. Using the three P/S converters 42 and three S/P converters 46, the nibbles are transferred serially over the lines and converted into the original nibbles. The data block reconstruction device 48 reconstructs the original data block and performs the function as indicated by the start bits, such as relative increase, relative decrease and absolute value. The resulting data is sent to either the RX or TX GC 30, 32 as indicated by the start bits.

Claims

CLAIMS What is claimed is:
1. A hybrid serial/parallel bus interface for a user equipment (UE) comprising: a data block demultiplexing device having an input configured to receive a data block and demultiplexing the data block into a plurality of nibbles, each nibble having a plurality of bits; for each nibble: a parallel to serial converter for converting that nibble into serial data; a line for transferring that nibble serial data; a serial to parallel converter for converting that nibble serial data to recover that nibble; and a data block reconstruction device for combining the recovered nibbles into the data block.
2. The UE interface of claim 1 wherein a number of bits in a data block is N and a number of the lines is i and 1 < i < N.
3. The UE interface of claim 1 wherein a number of bits in a nibble is four and a number of lines is two.
4. A hybrid serial/parallel bus interface for a user equipment (UE) comprising: means having an input configured to receive a data block for demultiplexing the data block into a plurality of nibbles, each nibble having a plurality of bits; for each nibble: means for converting that nibble into serial data; a line for transferring that nibble serial data; and means for converting that nibble serial data to recover that nibble; and means for combining the recovered nibbles into the data block.
5. The UE interface of claim 4 wherein a number of bits in a data block is N and a number of the lines is i and 1 < i < N.
6. The UE interface of claim 4 wherein a number of bits in a nibble is four and a number of lines is two.
7. A user equipment (UE) having a hybrid serial/parallel bus interface for transferring data from a first node to a second node, the interface comprising: a data block demultiplexing device for demultiplexing a data block from the first node into m sets of n bits and for adding a start bit to each of the m sets, the m start bits collectively representing one of a particular function to be performed or a destination; for each of the m sets, a separate line for transferring that set of the m sets from the first node to the second node; a data block reconstruction device for receiving the m sets, for combining the m sets into the data block and for utilizing the m sets in accordance with the m start bits.
8. The UE interface of claim 7 wherein the demultiplexing device sets at least one of the m start bits in a one state when transmitting data and when the interface is not transmitting data, maintains all the separate lines in a zero state.
9. The UE interface of claim 7 wherein the m start bits represent a start of data transfer.
10. The UE interface of claim 7 wherein the m start bits collectively represent a particular function to be performed and not a destination.
11. The UE interface of claim 7 wherein functions that the m start bits collectively represent include a relative increase, a relative decrease and an absolute value function.
12. The UE interface of claim 7 wherein the m start bits collectively represent a particular destination and not a function to be performed.
13. The UE interface of claim 12 wherein destinations that the m start bits collectively represent include an RX and TX gain controller.
14. The UE interface of claim 7 wherein the m start bits collectively represent both a particular function to be performed and a particular destination.
15. A user equipment (UE) having a hybrid serial/parallel bus interface for transferring data from a first node to a second node, the interface comprising: means for demultiplexing a data block into m sets of n bits; means for adding a start bit to each of the m sets, the m start bits collectively representing one of a particular function to be performed or destination; means for transferring from the first node each of the m sets over a separate line; means for receiving at the second node each of the transferred m sets; and means for utilizing the received m sets in accordance with the m start bits.
16. The UE interface of claim 15 wherein the adding means sets at least one of the m start bits to a one state and, when the interface is not transmitting data, all the separate lines to a zero state.
17. The UE interface of claim 15 wherein at least one of the m start bits represents a start of data transfer.
18. The UE interface of claim 15 wherein the m start bits collectively represent a particular function to be performed and not a destination.
19. The UE interface of claim 15 wherein functions that the m start bits collectively represent include a relative increase, a relative decrease and an absolute value function.
20. The UE interface of claim 15 wherein the m start bits collectively represent a particular destination and not a function to be performed.
21. The UE interface of claim 20 wherein destinations that the m start bits collectively represent include an RX and TX gain controller.
22. The UE interface of claim 15 wherein the m start bits collectively represent both a particular function to be performed and a particular destination.
23. A user equipment (UE) hybrid serial/parallel bus interface for use in a synchronous system, the synchronous system having an associated clock, the bus interface, comprising: a data block demultiplexing device having an input for receiving a data block and demultiplexing the data block into a plurality of nibbles, each nibble having a plurality of bits; an even and an odd set of parallel to serial (P/S) converters, each set of P/S converters receiving the nibbles synchronous with a clock rate of the clock, and for converting the nibbles into a serial data; a first set of i multiplexers for serially transferring data from the set of even P/S converters on a positive edge of the clock over i lines and serially transferring data from the set of the odd P/S converters on a negative edge of the clock over i lines; a second set of i demultiplexers for receiving the even and odd serial data and sending the even received serial data to an even buffer and the odd serial data to an odd buffer; an even and an odd set of serial to parallel (S/P) converters, the even set of S/P converters converting the received even serial data to even parallel data and outputting the even parallel data synchronous with the clock; the odd set of S/P converters for converting the odd received serial data to odd parallel data and outputting the odd parallel data synchronous with the clock; and a data block reconstruction device for combining the even and odd parallel data as the data block.
24. The base station interface of claim 23 wherein each data block has N bits
N 1 < < — and 2 .
25. The UE interface of claim 23 wherein the even and the odd buffers respectively buffer the outputs of the even and odd set of P/S converters so that the even and odd set of S/P converters receive the even and odd received serial data synchronous with the clock.
26. A bi-directional serial/parallel bus interface employed by a user equipment (UE) comprising: a plurality of lines for transferring data blocks, the plurality of lines being less than a number of bits in each data block; a first node sending first data blocks to a second node over the plurality of lines, the first node demultiplexing the data block into a plurality of first nibbles, the plurality of first nibbles being equal in number to the plurality of lines, each first nibble having a plurality of bits; and the second node sending second data blocks to the first node over the plurality of lines, the second node demultiplexing the data block into a plurality of second nibbles, the plurality of second nibbles being equal in number to the plurality of lines, each second nibble having a plurality of bits.
27. The UE interface of claim 26 wherein the first node demultiplex the data block into a plurality of third nibbles, a number j of the third nibbles is less than the number N of lines and transferring the third nibbles over j lines.
28. The UE interface of claim 27 wherein the second node demultiplexes fourth data blocks into K bits, where K is less than or equal to N-j lines, and transferring the fourth data block over K lines.
29. The UE interface of claim 26 wherein the first node data blocks include gain control information.
30. The UE interface of claim 29 wherein the second node data blocks include an acknowledgment of receipt of the gain control information.
31. The UE interface of claim 29 wherein the second node data blocks include information of a status associated with the second node.
32. A gain control (GC) employed by a user equipment (UE), comprising: a GC controller for producing a data block having n bits representing a gain value; i lines for transferring the data block from the GC controller to a GC, where l<i<n; and
the GC for receiving the data block and adjusting a gain of the GC using the gain value of the data block.
33. The UE GC of claim 32 further comprising: a data block demultiplexing device for demultiplexing the data block into a plurality of nibbles, each nibble being transferred over a different line of the i lines; and a data block reconstruction device for combining the nibbles into the data block.
34. The UE GC of claim 33 wherein appended to each nibble is a start bit.
35. The UE GC of claim 34 wherein the start bits indicate a function to be performed.
36. The UE GC of claim 35 wherein functions indicated by the start bits include a relative increase, a relative decrease and an absolute value function.
37. The UE GC of claim 34 wherein the GC includes a RX GC and a TX GC and the start bits indicate whether the data block is sent to the RX GC or TX GC.
EP02789726A 2001-11-21 2002-11-18 User equipment (ue) having a hybrid parallel/serial bus interface Withdrawn EP1446722A4 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP05104800A EP1575173B1 (en) 2001-11-21 2002-11-18 User equipment (UE) having a hybrid parallel/serial bus interface
EP05104801A EP1575174B1 (en) 2001-11-21 2002-11-18 User equipment (UE) having a hybrid parallel/serial bus interface

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US80899 1993-06-22
US09/990,060 US7069464B2 (en) 2001-11-21 2001-11-21 Hybrid parallel/serial bus interface
US990060 2001-11-21
US10/080,899 US6823469B2 (en) 2001-11-21 2002-02-22 User equipment (UE) having a hybrid parallel/serial bus interface
PCT/US2002/036954 WO2003046737A1 (en) 2001-11-21 2002-11-18 User equipment (ue) having a hybrid parallel/serial bus interface

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP05104801A Division EP1575174B1 (en) 2001-11-21 2002-11-18 User equipment (UE) having a hybrid parallel/serial bus interface
EP05104800A Division EP1575173B1 (en) 2001-11-21 2002-11-18 User equipment (UE) having a hybrid parallel/serial bus interface

Publications (2)

Publication Number Publication Date
EP1446722A1 true EP1446722A1 (en) 2004-08-18
EP1446722A4 EP1446722A4 (en) 2005-04-20

Family

ID=26764107

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02789726A Withdrawn EP1446722A4 (en) 2001-11-21 2002-11-18 User equipment (ue) having a hybrid parallel/serial bus interface

Country Status (12)

Country Link
EP (1) EP1446722A4 (en)
JP (1) JP2005510800A (en)
CN (1) CN100346327C (en)
AT (2) ATE388525T1 (en)
AU (1) AU2002352773A1 (en)
CA (1) CA2467841C (en)
DE (1) DE60226910D1 (en)
HK (1) HK1069905A1 (en)
MX (1) MXPA04004742A (en)
NO (1) NO20042522L (en)
TW (2) TWI285316B (en)
WO (1) WO2003046737A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1321382C (en) * 2004-01-20 2007-06-13 宏达国际电子股份有限公司 Serial/parallel data converting module and relative computer system
CN1329850C (en) * 2004-01-20 2007-08-01 凌阳科技股份有限公司 Transmission method and system for multiple path bus data

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH056335A (en) * 1991-06-27 1993-01-14 Nec Eng Ltd Inter-device interface system
JPH05160819A (en) * 1991-12-03 1993-06-25 Nec Eng Ltd Data transfer equipment
JPH05250316A (en) * 1992-03-05 1993-09-28 Nec Eng Ltd Inter-device interface system
US5602780A (en) * 1993-10-20 1997-02-11 Texas Instruments Incorporated Serial to parallel and parallel to serial architecture for a RAM based FIFO memory
US5768529A (en) * 1995-05-05 1998-06-16 Silicon Graphics, Inc. System and method for the synchronous transmission of data in a communication network utilizing a source clock signal to latch serial data into first registers and a handshake signal to latch parallel data into second registers
US5812881A (en) * 1997-04-10 1998-09-22 International Business Machines Corporation Handshake minimizing serial to parallel bus interface in a data processing system
US7069464B2 (en) * 2001-11-21 2006-06-27 Interdigital Technology Corporation Hybrid parallel/serial bus interface

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
"3606 - Digitally Controlled Programmable Gain Instrumentation Amplifier" October 1983 (1983-10), BURR-BROWN CORPORATION , TUCSON, ARIZONA, USA , XP002317899 Retrieved from the Internet: URL:http://focus.ti.com/lit/ds/symlink/3606.pdf> * page 8, column 2; figures 1,9 * *
"DS90CR211/DS90CR212 21-Bit Channel Link" July 1997 (1997-07), NATIONAL SEMICONDUCTOR , SANTA CLARA, CALIFORNIA, USA , XP002306540 Retrieved from the Internet: URL:http://www.national.com/ds/DS/DS90CR211.pdf> * pages 1-2; figure 13 * *
HUQ S B ET AL: "An Overview of LVDS Technology" July 1998 (1998-07), NATIONAL SEMICONDUCTOR , SANTA CLARA, CALIFORNIA, USA , XP002317898 Retrieved from the Internet: URL:http://www.national.com/an/AN/AN-971.pdf> * pages 1,4; figure 6 * *
KITANOWSKA S ET AL: "Bus LVDS with Virtex-E Devices" 26 July 2000 (2000-07-26), XILINX INC , SAN JOSE, CALIFORNIA, USA , XP002307032 Retrieved from the Internet: URL:http://direct.xilinx.com/bvdocs/appnotes/xapp243.pdf> * page 1 * *
MAC GETTIGAN E: "Eight Channel, One Clock, One Frame LVDS Transmitter/Receiver" 15 March 2001 (2001-03-15), XILINX INC , SAN JOSE, CALIFORNIA, USA , XP002317897 Retrieved from the Internet: URL:http://direct.xilinx.com/bvdocs/appnotes/xapp245.pdf> * pages 1,4; figure 9 * *
NOVAK T ET AL: "Channel Link - Moving and Shaping Information In Point-toPoint Applications" May 1996 (1996-05), NATIONAL SEMICONDUCTOR , SANTA CLARA, CALIFORNIA, USA , XP002306541 Retrieved from the Internet: URL:http://www.national.com/an/AN/AN-1041.pdf> * pages 1-2; figures 1-5 * *
See also references of WO03046737A1 *
VON HERZEN B ET AL: "Multi-Channel 622 Mb/s LVDS Data Transfer for Virtex-E Devices" 6 January 2001 (2001-01-06), XILINX INC. , SAN JOSE, CALIFORNIA, USA , XP002306542 Retrieved from the Internet: URL:http://direct.xilinx.com/bvdocs/appnotes/xapp233.pdf> * pages 1-5; figures 1-3,6 * *

Also Published As

Publication number Publication date
ATE388525T1 (en) 2008-03-15
MXPA04004742A (en) 2004-08-02
CN100346327C (en) 2007-10-31
NO20042522L (en) 2004-06-16
HK1069905A1 (en) 2005-06-03
JP2005510800A (en) 2005-04-21
WO2003046737A1 (en) 2003-06-05
TWI260172B (en) 2006-08-11
TW200419359A (en) 2004-10-01
TWI285316B (en) 2007-08-11
TW200402240A (en) 2004-02-01
EP1446722A4 (en) 2005-04-20
CN1589437A (en) 2005-03-02
ATE397323T1 (en) 2008-06-15
AU2002352773A1 (en) 2003-06-10
CA2467841A1 (en) 2003-06-05
CA2467841C (en) 2008-05-13
DE60226910D1 (en) 2008-07-10

Similar Documents

Publication Publication Date Title
US7069464B2 (en) Hybrid parallel/serial bus interface
US7240233B2 (en) Hybrid parallel/serial bus interface
EP1446584B1 (en) Base station having a hybrid parallel/serial bus interface
CA2467841C (en) User equipment (ue) having a hybrid parallel/serial bus interface
WO2003047113A1 (en) Method of transferring data

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20040507

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 06F 13/00 B

Ipc: 7H 03M 9/00 A

A4 Supplementary search report drawn up and despatched

Effective date: 20050308

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20111103