US 8,710,862 B2Grant
Programming of DIMM termination resistance values
Issue Date:2014-04-29
•27 Claims
•9 Drawing Sheets
Abstract
Systems, methods, and apparatus, including computer program products, for providing termination resistance in a memory module are provided. An apparatus is provided that includes a plurality of memory circuits; an interface circuit operable to communicate with the plurality of memory circuits and to communicate with a memory controller; and a transmission line electrically coupling the interface circuit to a memory controller, wherein the interface circuit is operable to terminate the transmission line with a single termination resistance that is selected based on a plurality of resistance-setting commands received from the memory controller.
Metadata
Assignee
- Google Inc.
Inventors
- Philip Arnold Ferolito
- Daniel L. Rosenband
- David T. Wang
- Michael John Smith
Application Information
Application Number:US 13/455,691
Filing Date:2012-04-25
Priority Date:2009-06-09
Art Unit:2819
Classifications
IPC:
H03K17/16H03K19/003G11C7/10G11C8/00G06F13/00G06F13/28
Patent Drawings (9 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 12/797,557 filed Jun. 9, 2010 which claims the benefit under 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/185,585, filed on Jun. 9, 2009, which is hereby incorporated by reference in its entirety.
Background
[0002] This specification relates to controlling of termination resistance values in memory modules.
[0003] A typical memory system includes memory modules that are arranged in slots. Each memory module includes a number of memory chips. For example, the memory module can be a dual inline memory module (DIMM) and the memory chips can be dynamic random access memory chips (DRAMs). Memory modules are physically placed in slot connectors and are electrically coupled to other components, e.g., one or more memory controllers, through channels and buses. These channels and buses form transmission lines that are electrically terminated at the connected DIMMs. A memory controller can select any of the DIMMs in a channel for reading or writing, but it will only access one DIMM at a time. The slot in which the DIMM accessed for reading or writing is located is referred to as the “active” slot, while slots in which the other non-accessed DIMMs are located are referred to as the “standby” slots.
[0004] A typical DIMM can have a single rank or multiple ranks. A rank is an independent set of DRAMs within the DIMM that can be simultaneously accessed for the full data bit-width of the DIMM, such as 72 bits. The rank to which data is being written is called the target rank for writes. The rank from which data is being read is called the target rank for reads.
Summary
[0005] This specification describes technologies relating to controlling of termination resistance values in memory modules.
[0006] In general, one aspect of the subject matter described in this specification can be embodied in an apparatus for providing termination resistance in a memory module that includes a plurality of memory circuits; an interface circuit operable to communicate with the plurality of memory circuits and to communicate with a memory controller; and a transmission line electrically coupling the interface circuit to a memory controller, wherein the interface circuit is operable to terminate the transmission line with a single termination resistance that is selected based on a plurality of resistance-setting commands received from the memory controller. Other embodiments of this aspect include corresponding systems, method, computer readable media, and computer program products.
[0007] These and other embodiments can optionally include one or more of the following features. The apparatus provides single termination resistance with an on-die termination (ODT) resistor. The interface circuit selects a value of the single termination resistance from a look-up table. The plurality of resistance-setting commands received from the memory controller include a first mode register set (MRS) command and a second MRS command. A value of the single termination resistance during read operations is different from a value of the single termination resistance during write operations. The plurality of memory circuits is a plurality of dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM). The single termination resistance has a value that is different from values specified by the resistance-setting commands received from the memory controller.
[0008] In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving a plurality of resistance-setting commands from a memory controller at an interface circuit, wherein the interface circuit is operable to communicate with a plurality of memory circuits and with the memory controller; selecting a resistance value based on the received plurality of resistance-setting commands; and terminating a transmission line between the interface circuit and the memory controller with a resistor of the selected resistance value. Other embodiments of this aspect include corresponding systems, apparatus, computer readable media, and computer program products.
[0009] In general, one aspect of the subject matter described in this specification can be embodied in an apparatus for providing termination resistance in a memory module that includes a first memory circuit having a first termination resistor with a selectable value; a second memory circuit having a second termination resistor with a selectable value; and an interface circuit operable to communicate with the first and the second memory circuits and a memory controller, wherein the interface circuit is operable to select a single value for the first and the second termination resistors that is chosen based on a plurality of resistance-setting commands received from the memory controller. Other embodiments of this aspect include corresponding systems, method, computer readable media, and computer program products.
[0010] These and other embodiments can optionally include one or more of the following features. The first and the second termination resistors are ODT resistors. The interface circuit selects a single value for the first and the second termination resistors from a look-up table. The plurality of resistance-setting commands received from the memory controller includes an MRS command and a second MRS command. Values of the first and the second termination resistors during read operations are different from values of the first and the second termination resistors during write operations. The first and the second memory circuits are DRAM integrated circuits in a DIMM. The single value selected by the interface circuit for the first and the second termination resistors is different from values indicated by the plurality of resistance-setting commands received from the memory controller.
[0011] Particular embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. The use of the interface circuit for transmission line termination allows for the creation of a single point of termination for a DIMM. This can improve performance, reduce cost, and provide other benefits for a memory module design. An interface circuit for transmission line termination can be used to tune termination values specifically for a DIMM. Standard termination values, for example the termination values mandated by Joint Electron Devices Engineering Council (JEDEC), might not always be optimal for a given DIMM, leading to sub-optimal performance.
[0012] The use of an interface circuit for transmission line termination can provide optimal ODT resistance for a given DIMM, which preserves signal integrity and minimizes noise on the transmission line. Furthermore, the use of the interface circuit can also provide termination resistance for a DIMM that is higher than the resistance mandated by a standard. If higher resistance is used while signal integrity is maintained, power dissipation will be reduced because the amount of dissipated power is inversely proportional to the value of termination resistance. As a result, the use of an interface circuit for transmission line termination can improve electrical performance and signal quality within a memory system using one or more DIMMs.
[0013] The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.
Brief Description of the Drawings
[0014] FIGS. 1A-F are block diagrams of example computer systems.
[0015] FIG. 2 is an example timing diagram for a 3-DIMMs per channel (3DPC) configuration.
[0016] FIGS. 3A-C are block diagrams of an example memory module using an interface circuit to provide DIMM termination.
[0017] FIG. 4 is a block diagram illustrating a slice of an example 2-rank DIMM using two interface circuits for DIMM termination per slice.
[0018] FIG. 5 is a block diagram illustrating a slice of an example 2-rank DIMM with one interface circuit per slice.
[0019] FIG. 6 illustrates a physical layout of an example printed circuit board (PCB) of a DIMM with an interface circuit.
[0020] FIG. 7 is a flowchart illustrating an example method for providing termination resistance in a memory module.
[0021] Like reference numbers and designations in the various drawings indicate like elements.
Detailed Description
[0022] Electrical termination of a transmission line involves placing a termination resistor at the end of the transmission line to prevent the signal from being reflected back from the end of the line, causing interference. In some memory systems, transmission lines that carry data signals are terminated using on-die termination (ODT). ODT is a technology that places an impedance matched termination resistor in transmission lines inside a semiconductor chip. During system initialization, values of ODT resistors used by DRAMs can be set by the memory controller using mode register set (MRS) commands. In addition, the memory controller can turn a given ODT resistor on or turn off at the DRAM with an ODT control signal. When the ODT resistor is turned on with an ODT control signal, it begins to terminate the associated transmission line. For example, a memory controller in a double-data-rate three (DDR3) system can select two static termination resistor values during initialization for all DRAMs within a DIMM using MRS commands. During system operation, the first ODT value (Rtt_Nom) is applied to non-target ranks when the corresponding rank's ODT signal is asserted for both reads and writes. The second ODT value (Rtt_WR) is applied only to the target rank of a write when that rank's ODT signal is asserted.
[0023] FIGS. 1A-F are block diagrams of example computer systems. FIG. 1A is a block diagram of an example computer system 100A. Computer system 100A includes a platform chassis 110, which includes at least one motherboard 120. In some implementations, the example computer system 100A includes a single case, a single power supply, and a single motherboard/blade. In other implementations, computer system 100A can include multiple cases, power supplies, and motherboards/blades.
[0024] The motherboard 120 includes a processor section 126 and a memory section 128. In some implementations, the motherboard 120 includes multiple processor sections 126 and/or multiple memory sections 128. The processor section 126 includes at least one processor 125 and at least one memory controller 124. The memory section 128 includes one or more memory modules 130 that can communicate with the processor section 126 using the memory bus 134 (e.g., when the memory section 128 is coupled to the processor section 126). The memory controller 124 can be located in a variety of places. For example, the memory controller 124 can be implemented in one or more of the physical devices associated with the processor section 126, or it can be implemented in one or more of the physical devices associated with the memory section 128.
[0025] FIG. 1B is a block diagram that illustrates a more detailed view of the processor section 126 and the memory section 128, which includes one or more memory modules 130. Each memory module 130 communicates with the processor section 126 over the memory bus 134. In some implementations, the example memory module 130 includes one or more interface circuits 150 and one or more memory chips 142. While the following discussion generally references a single interface circuit 150, more than one interface circuit 150 can be used. In addition, though the computer systems are described with reference to memory chips as DRAMs, the memory chip 142 can be, but is not limited to, DRAM, synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, DDR4 SDRAM, etc.), graphics double data rate synchronous DRAM (GDDR SDRAM, GDDR2 SDRAM, GDDR3 SDRAM, etc.), quad data rate DRAM (QDR DRAM), RAMBUS XDR DRAM (XDR DRAM), fast page mode DRAM (FPM DRAM), video DRAM (VDRAM), extended data out DRAM (EDO DRAM), burst EDO RAM (BEDO DRAM), multibank DRAM (MDRAM), synchronous graphics RAM (SGRAM), phase-change memory, flash memory, and/or any other type of volatile or non-volatile memory.
[0026] Each of the one or more interface circuits 150 can be, for example, a data buffer, a data buffer chip, a buffer chip, or an interface chip. The location of the interface circuit 150 is not fixed to a particular module or section of the computer system. For example, the interface circuit 150 can be positioned between the processor section 126 and the memory module 130 (FIG. 1C ). In some implementations, the interface circuit 150 is located in the memory controller 124, as shown in FIG. 1D . In yet some other implementations, each memory chip 142 is coupled to its own interface circuit 150 within memory module 130 (FIG. 1E ). And in another implementation, the interface circuit 150 is located in the processor section 126 or in processor 125, as shown in FIG. 1F .
[0027] The interface circuit 150 can act as an interface between the memory chips 142 and the memory controller 124. In some implementations, the interface circuit 150 accepts signals and commands from the memory controller 124 and relays or transmits commands or signals to the memory chips 142. These could be the same or different signals or commands. Each of the one or more interface circuits 150 can also emulate a virtual memory module, presenting the memory controller 124 with an appearance of one or more virtual memory circuits. In the emulation mode, the memory controller 124 interacts with the interface circuit 150 as it would with a physical DRAM or multiple physical DRAMs on a memory module, depending on the configuration of the interface circuit 150. Therefore, in emulation mode, the memory controller 124 could see a single-rank memory module or a multiple-rank memory module in the place of the interface circuit 150, depending on the configuration of the interface circuit 150. In case multiple interface circuits 150 are used for emulation, each interface circuit 150 can emulate a portion (i.e., a slice) of the virtual memory module that is presented to the memory controller 124.
[0028] An interface circuit 150 that is located on a memory module can also act as a data buffer for multiple memory chips 142. In particular, the interface circuit 150 can buffer one or more ranks and present a single controllable point of termination for a transmission line. The interface circuit 150 can be connected to memory chips 142 or to the memory controller 124 with one or more transmission lines. The interface circuit 150 can therefore provide a more flexible memory module (e.g., DIMM) termination instead of, or in addition to, the memory chips (e.g., DRAM) located on the memory module.
[0029] The interface circuit 150 can terminate all transmission lines or just a portion of the transmission lines of the DIMM. In case when multiple interface circuits 150 are used, each interface circuit 150 can terminate a portion of the transmission lines of the DIMM. For example, the interface circuit 150 can be used to terminate 8 bits of data. If there are 72 bits of data provided by a DIMM, then nine interface circuits are needed to terminate the entire DIMM. In another example, the interface circuit 150 can be used to terminate 72 bits of data, in which case one interface circuit 150 would be needed to terminate the entire 72-bit DIMM. Additionally, the interface circuit 150 can terminate various transmission lines. For example, the interface circuit 150 can terminate a transmission line between the memory controller 124 and the interface circuit 150. In addition or alternatively, the interface circuit 150 can terminate a transmission line between the interface circuit 150 and one or more of the memory chips 142.
[0030] Each of one or more interface circuits 150 can respond to a plurality of ODT signals or MRS commands received from the memory controller 124. In some implementations, the memory controller 124 sends one ODT signal or MRS command per physical rank. In some other implementations, the memory controller 124 sends more than one ODT signal or MRS command per physical rank. Regardless, because the interface circuit 150 is used as a point of termination, the interface circuit 150 can apply different or asymmetric termination values for non-target ranks during reads and writes. Using different non-target DIMM termination values for reads and writes allows for improved signal quality of the channel and reduced power dissipation due to the inherent asymmetry of a termination line.
[0031] Moreover, because the interface circuit 150 can be aware of the state of other signals/commands to a DIMM, the interface circuit 150 can choose a single termination value that is optimal for the entire DIMM. For example, the interface circuit 150 can use a lookup table filled with termination values to select a single termination value based on the MRS commands it receives from the memory controller 124. The lookup table can be stored within interface circuit 150 or in other memory locations, e.g., memory controller 124, processor 125, or a memory module 130. In another example, the interface circuit 150 can compute a single termination based on one or more stored formula. The formula can accept input parameters associated with MRS commands from the memory controller 124 and output a single termination value. Other techniques of choosing termination values can be used, e.g., applying specific voltages to specific pins of the interface circuit 150 or programming one or more registers in the interface circuit 150. The register can be, for example, a flip-flop or a storage element.
[0032] Tables 1A and 1B show example lookup tables that can be used by the interface circuit 150 to select termination values in a memory system with a two-rank DIMM.
[0033]
| TABLE 1A | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Termination values expressed in terms of resistance RZQ. | |||||||||
| term_b | |||||||||
| disabled | RZQ/4 | RZQ/2 | RZQ/6 | RZQ/12 | RZQ/8 | reserved | reserved | ||
| term_a | disabled | disabled | RZQ/4 | RZQ/2 | RZQ/6 | RZQ/12 | RZQ/8 | TBD | TBD |
| RZQ/4 | RZQ/8 | RZQ/6 | RZQ/12 | RZQ/12 | RZQ/12 | TBD | TBD | ||
| RZQ/2 | RZQ/4 | RZQ/8 | RZQ/12 | RZQ/12 | TBD | TBD | |||
| RZQ/6 | RZQ/12 | RZQ/12 | RZQ/12 | TBD | TBD | ||||
| RZQ/12 | RZQ/12 | RZQ/12 | TBD | TBD | |||||
| RZQ/8 | RZQ/12 | TBD | TBD | ||||||
| reserved | TBD | TBD | |||||||
| reserved | TBD | ||||||||
[0034]
| TABLE 1B | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Termination values of Table 1A with RZQ = 240 ohm | |||||||||
| term_b | |||||||||
| inf | 60 | 120 | 40 | 20 | 30 | reserved | reserved | ||
| term_a | inf | inf | 60 | 120 | 40 | 20 | 30 | TBD | TBD |
| 60 | 30 | 40 | 20 | 20 | 20 | TBD | TBD | ||
| 120 | 60 | 30 | 20 | 20 | TBD | TBD | |||
| 40 | 20 | 20 | 20 | TBD | TBD | ||||
| 20 | 20 | 20 | TBD | TBD | |||||
| 30 | 20 | TBD | TBD | ||||||
| reserved | TBD | TBD | |||||||
| reserved | TBD | ||||||||
[0035] Because the example memory system has two ranks, it would normally require two MRS commands from the memory controller 124 to set ODT values in each of the ranks. In particular, memory controller 124 would issue an MRS0 command that would set the ODT resistor values in DRAMs of the first rank (e.g., as shown by term_a in Tables 1A-B) and would also issue an ODT0 command signal that would activate corresponding ODT resistors in the first rank. Memory controller 124 would also issue an MRS1 command that would set the ODT resistor values in DRAMs of the second rank (e.g., as shown by term_b in Tables 1A-B) and would also issue an ODT1 command signal that would enable the corresponding ODT resistors in the second rank.
[0036] However, because the interface circuit 150 is aware of signals/commands transmitted by the memory controller 124 to both ranks of the DIMM, it can select a single ODT resistor value for both ranks using a lookup table, for example, the resistor value shown in Tables 1A-B. The interface circuit 150 can then terminate the transmission line with the ODT resistor having the single selected termination value.
[0037] In addition or alternatively, the interface circuit 150 can also issue signals/commands to DRAMs in each rank to set their internal ODTs to the selected termination value. This single termination value may be optimized for multiple ranks to improve electrical performance and signal quality.
[0038] For example, if the memory controller 124 specifies the first rank's ODT value equal to RZQ/6 and the second rank's ODT value equal to RZQ/12, the interface circuit 150 will signal or apply an ODT resistance value of RZQ/12. The resulting value can be found in the lookup table at the intersection of a row and a column for given resistance values for rank 0 (term_a) and rank 1 (term_b), which are received from the memory controller 124 in the form of MRS commands. In case the RZQ variable is set to 240 ohm, the single value signaled or applied by the interface circuit 150 will be 240/12=20 ohm. A similar lookup table approach can be applied to Rtt_Nom values, Rtt_WR values, or termination values for other types of signals.
[0039] In some implementations, the size of the lookup table is reduced by ‘folding’ the lookup table due to symmetry of the entry values (Rtt). In some other implementations, an asymmetric lookup table is used in which the entry values are not diagonally symmetric. In addition, the resulting lookup table entries do not need to correspond to the parallel resistor equivalent of Joint Electron Devices Engineering Council (JEDEC) standard termination values. For example, the table entry corresponding to 40 ohm for the first rank in parallel with 40 ohm for the second rank (40/40) does not have to result in a 20 ohm termination setting. In addition, in some implementations, the lookup table entries are different from Rtt_Nom or Rtt_WR values required by the JEDEC standards.
[0040] While the above discussion focused on a scenario with a single interface circuit 150, the same techniques can be applied to a scenario with multiple interface circuits 150. For example, in case multiple interface circuits 150 are used, each interface circuit 150 can select a termination value for the portion of the DIMM that is being terminated by that interface circuit 150 using the techniques discussed above.
[0041] FIG. 2 is an example timing diagram 200 for a 3-DIMMs per channel (3DPC) configuration, where each DIMM is a two-rank DIMM. The timing diagram 200 shows timing waveforms for each of the DIMMs in three slots: DIMM A 220, DIMM B 222, and DIMM C 224. In FIG. 2 , each DIMM receives two ODT signal waveforms for ranks 0 and 1 (ODT0, ODT1), thus showing a total of six ODT signals: signals 230 and 232 for DIMM A, signals 234 and 236 for DIMM B, and signals 238 and 240 for DIMM C. In addition, the timing diagram 200 shows a Read signal 250 applied to DIMM A either at rank 0 (R0) or rank 1 (R1). The timing diagram 200 also shows a Write signal 252 applied to DIMM A at rank 0 (R0).
[0042] The values stored in the lookup table can be different from the ODT values mandated by JEDEC. For example, in the 40//40 scenario (R0 Rtt_Nom=ZQ/6=40 ohm, R1 Rtt_Nom=ZQ/6=40 ohm, with ZQ=240 ohm), a traditional two-rank DIMM system relying on JEDEC standard will have its memory controller set DIMM termination values of either INF (infinity or open circuit), 40 ohm (assert either ODT0 or ODT1), or 20 ohm (assert ODT0 and ODT1). On the other hand, the interface circuit 150 relying on the lookup table can set the ODT resistance value differently from memory controller relying on JEDEC-mandated values. For example, for the same values of R0 Rtt_Nom and R1 Rtt_Nom, the interface circuit 150 can select a resistance value that is equal to ZQ/12 (20 ohm) or ZQ/8 (30 ohm) or some other termination value. Therefore, even though the timing diagram 200 shows a 20 ohm termination value for the 40 I/40 scenario, the selected ODT value could correspond to any other value specified in the lookup table for the specified pair of R0 and R1 values.
[0043] When the interface circuit 150 is used with one-rank DIMMs, the memory controller can continue to provide ODT0 and ODT1 signals to distinguish between reads and writes even though ODT1 signal might not have any effect in a traditional memory channel. This allows single and multiple rank DIMMs to have the same electrical performance. In some other implementations, various encodings of the ODT signals are used. For example, the interface circuit 150 can assert ODT0 signal for non-target DIMMs for reads and ODT1 signal for non-target DIMMs for writes.
[0044] In some implementations, termination resistance values in multi-rank DIMM configurations are selected in a similar manner. For example, an interface circuit provides a multi-rank DIMM termination resistance using a look-up table. In another example, an interface circuit can also provide a multi-rank DIMM termination resistance that is different from the JEDEC standard termination value. Additionally, an interface circuit can provide a multi-rank DIMM with a single termination resistance. An interface circuit can also provide a multi-rank DIMM with a termination resistance that optimizes electrical performance. The termination resistance can be different for reads and writes.
[0045] In some implementations, a DIMM is configured with a single load on the data lines but receives multiple ODT input signals or commands. This means that while the DIMM can terminate the data line with a single termination resistance, the DIMM will appear to the memory controller as though it has two termination resistances that can be configured by the memory controller with multiple ODT signals and MRS commands. In some other implementations a DIMM has an ODT value that is a programmable function of the of ODT input signals that are asserted by the system or memory controller.
[0046] FIGS. 3A-C are block diagrams of an example memory module using an interface circuit to provide DIMM termination. In some implementations, FIGS. 3A-C include an interface circuit similar to interface circuit 150 described in the context of the computer systems in FIGS. 1A-F . In particular, DRAMs 316, 318, 320, and 324 can have attributes comparable to those described with respect to memory chips 142, respectively. Likewise, the interface circuit 314 can have attributes comparable to, and illustrative of, the interface circuits 150 shown in FIGS. 1A-F . Similarly, other elements within FIGS. 3A-C have attributes comparable to, and illustrative of, corresponding elements in FIGS. 1A-F .
[0047] Referring to FIG. 3A , the interface circuit 314 is coupled to DRAMs 316, 318, 320, and 324. The interface circuit 314 is coupled to the memory controller using memory bus signals DQ[3:0], DQ[7:4], DQS1—t, DQS1—c, DQS0—t, DQS0—c, VSS. Additionally, other bus signals (not shown) can be included. FIG. 3A shows only a partial view of the DIMM, which provides 8 bits of data to the system through DQ[7:4] bus signal. For an ECC DIMM with 72 bits of data, there would be a total of 36 DRAM devices and there would be 9 instances of interface circuit 314. In FIG. 3A , the interface circuit combines two virtual ranks to present a single physical rank to the system (e.g., to a memory controller). DRAMs 316 and 320 belong to a virtual rank 0 and DRAMs 318 and 324 are parts of virtual rank 1. As shown, DRAMs devices 316 and 318 together with interface circuit 314 operate to form a single larger virtual DRAM device 312. In a similar fashion, DRAM devices 320 and 324 together with interface circuit 314 operate to form a virtual DRAM device 310.
[0048] The virtual DRAM device 310 represents a “slice” of the DIMM, as it provides a “nibble” (e.g., 4 bits) of data to the memory system. DRAM devices 316 and 318 also represent a slice that emulates a single virtual DRAM 312. The interface circuit 314 thus provides termination for two slices of DIMM comprising virtual DRAM devices 310 and 312. Additionally, as a result of emulation, the system sees a single-rank DIMM.
[0049] In some implementations, the interface circuit 314 is used to provide termination of transmission lines coupled to DIMM. FIG. 3A shows resistors 333, 334, 336, 337 that can be used, either alone or in various combinations with each other, for transmission line termination. First, the interface circuit 314 can include one or more ODT resistors 334 (annotated as T2). For example, ODT resistor 334 may be used to terminate DQ[7:4] channel. It is noted that DQ[7:4] is a bus having four pins: DQ7, DQ6, DQ5, DQ4 and thus may require four different ODT resistors. In addition, DRAMs 316, 318, 320, and 324 can also include their own ODT resistors 336 (annotated as T).
[0050] In some implementations, the circuit of FIG. 3A also includes one or more resistors 333 that provide series stub termination of the DQ signals. These resistors are used in addition to any parallel DIMM termination, for example, provided by ODT resistors 334 and 336. Other similar value stub resistors can also be used with transmission lines associated with other data signals. For example, in FIG. 3A , resistor 337 is a calibration resistor connected to pin ZQ.
[0051] FIG. 3A also shows that the interface circuit 314 can receive ODT control signals though pins ODT0 326 and ODT1 328. As described above, the ODT signal turns on or turns off a given ODT resistor at the DRAM. As shown in FIG. 3A , the ODT signal to DRAM devices in virtual rank 0 is ODT0 326 and the ODT signal to the DRAM devices in virtual rank 1 is ODT1 328.
[0052] Because the interface circuit 314 provides for flexibility pins for signals ODT 330, ODT 332, ODT0 326, and ODT1 328 may be connected in a number of different configurations.
[0053] In one example, ODT0 326 and ODT1 328 are connected directly to the system (e.g., memory controller); ODT 330 and ODT 332 are hard-wired; and interface circuit 314 performs the function determine the value of DIMM termination based on the values of ODT0 and ODT1 (e.g., using a lookup table as describe above with respect to Tables 1A-B). In this manner, the DIMM can use the flexibility provided by using two ODT signals, yet provide the appearance of a single physical rank to the system.
[0054] For example, if the memory controller instructs rank 0 on the DIMM to terminate to 40 ohm and rank 1 to terminate to 40 ohm, without the interface circuit, a standard DIMM would then set termination of 40 ohm on each of two DRAM devices. The resulting parallel combination of two nets each terminated to 40 ohm would then appear electrically to be terminated to 20 ohm. However, the presence of interface circuit provides for additional flexibility in setting ODT termination values. For example, a system designer may determine, through simulation, that a single termination value of 15 ohm (different from the normal, standard-mandated value of 20 ohm) is electrically better for a DIMM embodiment using interface circuits. The interface circuit 314, using a lookup table as described, may therefore present a single termination value of 15 ohm to the memory controller.
[0055] In another example, ODT0 326 and ODT1 328 are connected to a logic circuit (not shown) that can derive values for ODT0 326 and ODT1 328 not just from one or more ODT signals received from the system, but also from any of the control, address, or other signals present on the DIMM. The signals ODT 330 and ODT 332 can be hard-wired or can be wired to the logic circuit. Additionally, there can be fewer or more than two ODT signals between the logic circuit and interface circuit 314. The one or more logic circuits can be a CPLD, ASIC, FPGA, or part of an intelligent register (on an R-DIMM or registered-DIMM for example), or a combination of such components.
[0056] In some implementations, the function of the logic circuit is performed by a modified JEDEC register with a number of additional pins added. The function of the logic circuit can also be performed by one or more interface circuits and shared between the interface circuits using signals (e.g., ODT 330 and ODT 332) as a bus to communicate the termination values that are to be used by each interface circuit.
[0057] In some implementations, the logic circuit determines the target rank and non-target ranks for reads or writes and then communicates this information to each of the interface circuits so that termination values can be set appropriately. The lookup table or tables for termination values can be located in the interface circuits, in one or more logic circuit, or shared/partitioned between components. The exact partitioning of the lookup table function to determine termination values between the interface circuits and any logic circuit depends, for example, on the economics of package size, logic function and speed, or number of pins.
[0058] In another implementation, signals ODT 330 and ODT 332 are used in combination with dynamic termination of the DRAM (i.e., termination that can vary between read and write operations and also between target and non-target ranks) in addition to termination of the DIMM provided by interface circuit 314. For example, the system can operate as though the DIMM is a single-rank DIMM and send termination commands to the DIMM as though it were a single-rank DIMM. However, in reality, there are two virtual ranks and two DRAM devices (such as DRAM 316 and DRAM 318) that each have their own termination in addition to the interface circuit. A system designer has an ability to vary or tune the logical and timing behavior as well as the values of termination in three places: (a) DRAM 316; (b) DRAM 318; and (c) interface circuit 314, to improve signal quality of the channel and reduce power dissipation.
[0059] A DIMM with four physical ranks and two logical ranks can be created in a similar fashion to the one described above. A computer system using 2-rank DIMMs would have two ODT signals provided to each DIMM. In some implementations, these two ODT signals are used, with or without an additional logic circuit(s) to adjust the value of DIMM termination at the interface circuits and/or at any or all of the DRAM devices in the four physical ranks behind the interface circuits.
[0060] FIG. 3B is a block diagram illustrating the example structure of an ODT block within a DIMM. The structure illustrated in FIG. 3B embodies the ODT resistor 336 (box T in DRAMs 316, 318, 320, and 324) described with respect to FIG. 3A . In particular, ODT block 342 includes an ODT resistor 346 that is coupled to ground/reference voltage 344 on one side and a switch 348 on the other side. The switch 348 is controlled with ODT signal 352, which can turn the switch either on or off. When the switch 348 is turned on, it connects the ODT resistor 346 to transmission line 340, permitting ODT resistor 346 to terminate the transmission line 340. When the switch 348 is turned off, it disconnects the ODT resistor 346 from the transmission line 340. In addition, transmission line 340 can be coupled to other circuitry 350 within DIMM. The value of the ODT resistor 346 can be selected using MRS command 354.
[0061] FIG. 3C is a block diagram illustrating the exemplary structure of ODT block within an interface circuit. The structure illustrated in FIG. 3B embodies the ODT resistor 366 (box T2 in DRAMs 316, 318, 320, and 324) described above with respect to FIG. 3A . In particular, ODT block 360 includes an ODT resistor 366 that is coupled to ground/reference voltage 362 on one side and a switch 368 on the other side. In addition, the ODT block 360 can be controlled by circuit 372, which can receive ODT signals and MRS commands from a memory controller. Circuit 372 is a part of the interface circuit 314 in FIG. 3A and is responsible for controlling the ODT. The switch 368 can be controlled with either ODT0 signal 376 or ODT1 signal 378, which are supplied by the circuit 372.
[0062] In some implementations, circuit 372 transmits the same MRS commands or ODT signals to the ODT resistor 366 that it receives from the memory controller. In some other implementations, circuit 372 generates its own commands or signals that are different from the commands/signals it receives from the memory controller. Circuit 372 can generate these MRS commands or ODT signals based on a lookup table and the input commands/signals from the memory controller. When the switch 368 receives an ODT signal from the circuit 372, it can either turn on or turn off. When the switch 368 is turned on, it connects the ODT resistor 366 to the transmission line 370, permitting ODT resistor 366 to terminate the transmission line 370. When the switch 368 is turned off, it disconnects the ODT resistor 366 from the transmission line 370. In addition, transmission line 370 can be coupled to other circuitry 380 within the interface circuit. The value of the ODT resistor 366 can be selected using MRS command 374.
[0063] FIG. 4 is a block diagram illustrating one slice of an example 2-rank DIMM using two interface circuits for DIMM termination per slice. In some implementations, FIG. 4 includes an interface circuit similar to those previously described in FIGS. 1A-F and 3A-C. Elements within FIG. 4 can have attributes comparable to and illustrative of corresponding elements in FIGS. 1A-F and 3A-C.
[0064] FIG. 4 shows a DIMM 400 that has two virtual ranks and four physical ranks. DRAM 410 is in physical rank number zero, DRAM 412 is in the first physical rank, DRAM 414 is in the second physical rank, DRAM 416 is in the third physical rank. DRAM 410 and DRAM 412 are in virtual rank 0 440. DRAM 414 and DRAM 416 are in virtual rank 1 442. In general, DRAMs 410, 412, 414, and 416 have attributes comparable to and illustrative to DRAMs discussed with respect to FIGS. 1A-F and 3A-C. For example, DRAMs 410, 412, 414, and 416 can include ODT resistors 464, which were discussed with respect to FIG. 3B .
[0065] In addition, FIG. 4 shows an interface circuit 420 and an interface circuit 422. In some implementations, interface circuits 420 and 422 have attributes similar to the interface circuits described with respect to FIGS. 1A-F and 3A-C. For example, interface circuits 420 and 422 can include ODT resistors 460 and 462, which function similarly to ODT resistor 366 discussed above with respect to FIG. 3C .
[0066] FIG. 4 also shows one instance of a logic circuit 424. DIMM 400 can include other components, for example, a register, smart (i.e. modified or enhanced) register device or register circuit for R-DIMMs, a discrete PLL and/or DLL, voltage regulators, SPD, other non-volatile memory devices, bypass capacitors, resistors, and other components. In addition or alternatively, some of the above components can be integrated with each other or with other components.
[0067] In some implementation, DIMM 400 is connected to the system (e.g., memory controller) through conducting fingers 430 of the DIMM PCB. Some, but not all, of these fingers are illustrated in FIG. 4 , for example, the finger for DQS0—t, shown as finger 430. Each finger receives a signal and corresponds to a signal name, e.g., DQS0—t 432. DQ0 434 is an output (or pin) of the interface circuits 420 and 422. In some implementations, these two outputs are tied, dotted or connected to an electrical network. Any termination applied to any pin on this electrical network thus applies to the entire electrical network (and the same is true for other similar signals and electrical networks). Furthermore, interface circuits 420 and 422 are shown as containing multiple instances of switch 436. Net DQ0 434 is connected through switches 436 to signal pin DQ[0] of DRAM 410, DRAM 412, DRAM 414, and DRAM 416.
[0068] In some implementations, switch 436 is a single-pole single-throw (SPST) switch. In some other implementations, switch 436 is mechanical or non-mechanical. Regardless, the switch 436 can be one of various switch types, for example, SPST, DPDT, or SPDT, a two-way or bidirectional switch or circuit element, a parallel combination of one-way, uni-directional switches or circuit elements, a CMOS switch, a multiplexor (MUX), a de-multiplexer (de-MUX), a CMOS bidirectional buffer; a CMOS pass gate, or any other type of switch.
[0069] The function of the switches 436 is to allow the physical DRAM devices behind the interface circuit to be connected together to emulate a virtual DRAM. These switches prevent such factors as bus contention, logic contention or other factors that may prevent or present unwanted problems from such a connection. Any logic function or switching element that achieves this purpose can be used. Any logical or electrical delay introduced by such a switch or logic can be compensated for. For example, the address and/or command signals can be modified through controlled delay or other logical devices.
[0070] Switch 436 is controlled by signals from logic circuit 424 coupled to the interface circuits, including interface circuit 420 and interface circuit 422. In some implementations, switches 436 in the interface circuits are controlled so that only one of the DRAM devices is connected to any given signal net at one time. Thus, for example, if the switch connecting net DQ0 434 to DRAM 410 is closed, then switches connecting net DQ0 434 to DRAMs 412, 414, 416 are open.
[0071] In some implementations, the termination of nets, such as DQ0 434, by interface circuits 420 and 422 is controlled by inputs ODT0i 444 (where “i” stands for internal) and ODT1i 446. While the term ODT has been used in the context of DRAM devices, the on-die termination used by an interface circuit can be different from the on-die termination used by a DRAM device. Since ODT0i 444 and ODT1i 446 are internal signals, the interface circuit termination circuits can be different from standard DRAM devices. Additionally, the signal levels, protocol, and timing can also be different from standard DRAM devices.
[0072] The ability to adjust the interface circuit's ODT behavior provides the system designer with an ability to vary or tune the values and timing of ODT, which may improve signal quality of the channel and reduce power dissipation. In one example, as part of the target rank, interface circuit 420 provides termination when DRAM 410 is connected to net DQ0 434. In this example, the interface circuit 420 can be controlled by ODT0i 444 and ODT1i 446. As part of the non-target rank, interface circuit 422 can also provide a different value of termination (including no termination at all) as controlled by signals ODT0i 444 and ODT1i 446.
[0073] In some implementations, the ODT control signals or commands from the system are ODT0 448 and ODT1 450. The ODT input signals or commands to the DRAM devices are shown by ODT signals 452, 454, 456, 458. In some implementations, the ODT signals 452, 454, 456, 458 are not connected. In some other implementations, ODT signals 452, 454, 456, 458 are connected, for example, as: (a) hardwired (i.e. to VSS or VDD or other fixed voltage); (b) connected to logic circuit 424; (c) directly connected to the system; or (d) a combination of (a), (b), and (c).
[0074] As shown in FIG. 4 , transmission line termination can be placed in a number of locations, for example, (a) at the output of interface circuit 420; (b) the output of interface circuit 422; (c) the output of DRAM 410; (d) the output of DRAM 412; (e) the output of DRAM 414; (f) the output of DRAM 416; or may use any combination of these. By choosing location for termination, the system designer can vary or tune the values and timing of termination to improve signal quality of the channel and reduce power dissipation.
[0075] Furthermore, in some implementations, a memory controller in a DDR3 system sets termination values to different values than used in normal operation during different DRAM modes or during other DRAM, DIMM and system modes, phases, or steps of operation. DRAM modes can include initialization, wear-leveling, initial calibration, periodic calibration, DLL off, DLL disabled, DLL frozen, or various power-down modes.
[0076] In some implementations, the logic circuit 424 may also be programmed (by design as part of its logic or caused by control or other signals or means) to operate differently during different modes/phases of operation so that a DIMM with one or more interface circuits can appear, respond to, and communicate with the system as if it were a standard or traditional DIMM without interface circuits. Thus, for example, logic circuit 424 can use different termination values during different phases of operation (e.g., memory reads and memory writes) either by pre-programmed design or by external command or control, or the logic timing may operate differently. For example, logic circuit 424 can use a termination value during read operations that is different from a termination value during write operations.
[0077] As a result, in some implementations, no changes to a standard computer system (motherboard, CPU, BIOS, chipset, component values, etc.) need to be made to accommodate DIMM 400 with one or more interface circuits. Therefore, while in some implementations the DIMM 400 with the interface circuit(s) may operate differently from a standard or traditional DIMM (for example, by using different termination values or different timing than a standard DIMM), the modified DIMM would appear to the computer system/memory controller as if it were operating as a standard DIMM.
[0078] In some implementations, there are two ODT signals internal to the DIMM 400. FIG. 4 shows these internal ODT signals between logic circuit 424 and the interface circuits 420 and 422 as ODT0i 444 and ODT1i 446. Depending on the flexibility of termination required, the size and complexity of the lookup table, and the type of signaling interface used, there may be any number of signals between logic circuit 424 and the interface circuits 420 and 422. For example, the number of internal ODT signals can be same, fewer, or greater than the number of ODT signals from the system/memory controller.
[0079] In some implementations, there are two interface circuits per slice of a DIMM 400. Consequently, an ECC DIMM with 72 bits would include 2×72/4=36 interface circuits. Similarly, a 64-bit DIMM would include 2×64/4=32 interface circuits.
[0080] In some implementations, interface circuit 420 and interface circuit 422 are combined into a single interface circuit, resulting in one interface circuit per slice. In these implementations, a DIMM would include 72/4=18 interface circuits. Other number (8, 9, 16, 18, etc.), arrangement, or integration of interface circuits may be used depending on a type of DIMM, cost, power, physical space on the DIMM, layout restrictions and other factors.
[0081] In some alternative implementations, logic circuit 424 is shared by all of the interface circuits on the DIMM 400. In these implementations, there would be one logic circuit per DIMM 400. In yet other implementations, a logic circuit or several logic circuits are positioned on each side of a DIMM 400 (or side of a PCB, board, card, package that is part of a module or DIMM, etc.) to simplify PCB routing. Any number of logic circuits may be used depending on the type of DIMM, the number of PCBs used, or other factors.
[0082] Other arrangements and levels of integration are also possible. There arrangements can depend, for example, on silicon die area and cost, package size and cost, board area, layout complexity as well as other engineering and economic factors. For example, all of the interface circuits and logic circuits can be integrated together into a single interface circuit. In another example, an interface circuit and/or logic circuit can be used on each side of a PCB or PCBs to improve board routing. In yet another example, some or all of the interface circuits and/or logic circuits can be integrated with one or more register circuits or any of the other DIMM components on an R-DIMM.
[0083] FIG. 5 is a block diagram illustrating a slice of an example 2-rank DIMM 500 with one interface circuit per slice. In some implementations, DIMM 500 includes on or more interface circuit as described above in FIGS. 1A-F , 3A-C, and 4. Additionally, elements within DIMM 500 can have attributes similar to corresponding elements in FIGS. 1A-F , 3A-C, and 4. For example, interface circuit 520 can include ODT resistor 560, which can be similar to ODT resister 366, discussed with respect to FIG. 3C . Likewise, DRAM devices 510, 512, 514, and 516 can include ODT resistors 580, which can be similar to ODT resistor 346 discussed with respect to FIG. 3B .
[0084] DIMM 500 has virtual rank 0 540, with DRAM devices 510 and 512 and virtual rank 1 542, with DRAM devices 514 and 516. Interface circuit 520 uses switches 562 and 564 to either couple or isolate data signals such as DQ0 534 to the DRAM devices. Signals, for example, DQ0 534 are received from the system through connectors e.g., finger 530. A register circuit 524 provides ODT control signals on bus 566 and switch control signals on bus 568 to interface circuit 520 and/or other interface circuits. Register circuit 524 can also provide standard JEDEC register functions. For example, register circuit 524 can receive inputs 572 that include command, address, control, and other signals from the system through connectors, e.g., finger 578. In some implementations, other signals are not directly connected to the register circuit 524, as shown in FIG. 5 by finger 576. The register circuit 524 can transmit command, address, control and other signals (possibly modified in timing and values) through bus 574 to the DRAM devices, for example, DRAM device 516. Not all the connections of command, address, control and other signals between DRAM devices are shown in FIG. 5 .
[0085] The register circuit 524 can receive inputs ODT0 548 and ODT1 550 from a system (e.g., a memory controller of a host system). The register circuit 524 can also alter timing and behavior of ODT control before passing this information to interface circuit 520 through bus 566. The interface circuit 520 can then provide DIMM termination at DQ pin with ODT resistor 560. In some implementations, the timing of termination signals (including when and how they are applied, changed, removed) and determination of termination values are split between register circuit 524 and interface circuit 520.
[0086] Furthermore, in some implementations, the register circuit 524 also creates ODT control signals 570: R0_ODT0, R0_ODT1, R1_ODT0, R1_ODT1. These signals can be coupled to DRAM device signals 552, 554, 556 and 558. In some alternative implementations, (a) some or all of signals 552, 554, 556 and 558 may be hard-wired (to VSS, VDD or other potential); (b) some or all of signals 570 are created by interface circuit 520; (c) some or all of signals 570 are based on ODT0 548 and ODT1 550; (d) some or all of signals 570 are altered in timing and value from ODT0 548 and ODT1 550; or (e) any combination of implementations (a)-(d).
[0087] FIG. 6 illustrates an physical layout of an example printed circuit board (PCB) 600 of a DIMM with an interface circuit. In particular, PCB 600 includes an ECC R-DIMM with nine interface circuits and thirty six DRAMs 621. Additionally, FIG. 6 shows the two sides of a single DIMM 610. The DIMM 610 includes fingers 612 that permit the DIMM 610 to be electrically coupled to a system. Furthermore, as shown in FIG. 6 , PCB 600 includes 36 DRAM (621-629, front/bottom; 631-639 front/top; 641-649 back/top; 651-659 back/bottom).
[0088] FIG. 6 also shows nine interface circuits 661-669, located in the front/middle. In addition, FIG. 6 shows one register circuit 670 located in front/center of the PCB 600. The register circuit 670 can have attributes comparable to those described with respect to interface circuit 150. DIMMs with a different number of DRAMs, interface circuits, or layouts can be used.
[0089] In some implementations, interface circuits can be located at the bottom of the DIMM PCB, so as to place termination electrically close to fingers 612. In some other implementations, DRAMs can be arranged on the PCB 600 with different orientations. For example, their longer sides can be arranged parallel to the longer edge of the PCB 600. DRAMs can also be arranged with their longer sides being perpendicular to the longer edge of the PCB 600. Alternatively, the DRAMs can be arranged such that some have long sides parallel to the longer edge of the PCB 600 and others have longer sides perpendicular to the longer edge of the PCB 600. Such arrangement may be useful to optimize high-speed PCB routing. In some other implementations, PCB 600 can include more than one register circuit. Additionally, PCB 600 can include more than one PCB sandwiched to form a DIMM. Furthermore, PCB 600 can include interface circuits placed on both side of the PCB.
[0090] FIG. 7 is a flowchart illustrating an example method 700 for providing termination resistance in a memory module. For convenience, the method 700 will be described with reference to an interface circuit that performs the method (e.g., interface circuit 150). It should be noted, however, that some or all steps of method 700 can be performed by other components within computer systems 100A-F.
[0091] The interface circuit communicates with memory circuits and with a memory controller (step 702). The memory circuits are, for example, dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM).
[0092] The interface circuit receives resistance-setting commands from the memory controller (step 704). The resistance-setting commands can be mode register set (MRS) commands directed to on-die termination (ODT) resistors within the memory circuits.
[0093] The interface circuit selects a resistance value based on the received resistance-setting commands (step 706). The interface circuit can select a resistance value from a look-up table. In addition, the selected resistance value can depend on the type of operation performed by the system. For example, the selected resistance value during read operations can be different from the selected resistance value during write operations. In some implementations, the selected resistance value is different from the values specified by the resistance-setting commands. For example, the selected resistance value can be different from a value prescribed by JEDEC standard for DDR3 DRAM.
[0094] The interface circuit terminates a transmission line with a resistor of the selected resistance value (step 708). The resistor can be an on-die termination (ODT) resistor. The transmission line can be, for example, a transmission line between the interface circuit and the memory controller.
[0095] While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. Therefore, the scope of the present invention is determined by the claims that follow. In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. It will be apparent, however, to one skilled in the art that implementations can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the disclosure.
[0096] In particular, one skilled in the art will recognize that other architectures can be used. Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
[0097] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
[0098] An apparatus for performing the operations herein can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
[0099] The algorithms and modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description. In addition, the present examples are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present description is in no way limited to implementation in any specific operating system or environment.
[0100] While this specification contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular implementations of the subject matter. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0101] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
[0102] The subject matter of this specification has been described in terms of particular embodiments, but other embodiments can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims.
Claims
What is claimed is:
1. A memory subsystem comprising:
a memory module comprising:
a first rank of memory circuits comprising a first plurality of memory circuits; and
a second rank of memory circuits comprising a second plurality of memory circuits;
an interface circuit;
a first transmission line electrically coupling the interface circuit to a first memory circuit of the first plurality of memory circuits of the first rank; and
a second transmission line electrically coupling the interface circuit to a second memory circuit of the second plurality of memory circuits of the second rank;
wherein the interface circuit is operable to:
present the first and the second ranks of memory circuits to a memory controller as a single rank of emulated memory circuits;
terminate one or more of the first transmission line with the first termination resistance or the second transmission line with the second termination resistance, wherein the first termination resistance and the second termination resistance are each selected based on at least a resistance-setting command for the single rank of emulated memory circuits received from the memory controller, and
wherein the first termination resistance or the second termination resistance is different from a termination resistance indicated by the resistance-setting command received from the memory controller.
2. The memory subsystem of claim 1, further comprising:
a third transmission line electrically coupling the interface circuit to the memory controller;
the interface circuit further comprising a third termination resistor with a third termination resistance;
wherein the interface circuit is further operable to terminate the third transmission line with the third termination resistance, wherein the third termination resistance is selected based on one or more resistance-setting commands received from the memory controller.
3. The memory subsystem of claim 1, wherein one or more of the first termination resistor or the second termination resistor is activated in response to one or more transmission line termination control signals issued by the interface circuit.
4. The memory subsystem of claim 1, wherein the first and the second termination resistors are on-die termination (ODT) resistors.
5. The memory subsystem of claim 2, wherein the third termination resistance is different from a termination resistance indicated by the plurality of resistance-setting commands received from the memory controller.
6. The memory subsystem of claim 1, wherein the interface circuit selects the first termination resistance and the second termination resistance from one or more look-up tables.
7. The memory subsystem of claim 1, wherein the resistance-setting command received from the memory controller comprises a mode register set (MRS) command.
8. The memory subsystem of claim 1, wherein resistance values of the first and the second termination resistors during read operations are different from resistance values of the first and the second termination resistors during write operations.
9. The memory subsystem of claim 1, wherein the interface circuit is located on the memory module.
10. A memory subsystem comprising:
a memory module comprising:
a first rank of memory circuits comprising a first plurality of memory circuits; and
a second rank of memory circuits comprising a second plurality of memory circuits;
an interface circuit;
a first transmission line electrically coupling the interface circuit to a first memory circuit of the first plurality of memory circuits of the first rank; and
a second transmission line electrically coupling the interface circuit to a second memory circuit of the second plurality of memory circuits of the second rank;
wherein the interface circuit is operable to:
present the first and the second ranks of memory circuits to a memory controller as a single rank of emulated memory circuits;
terminate one or more of the first transmission line with the first termination resistance or the second transmission line with the second termination resistance, wherein the first termination resistance and the second termination resistance are each selected based on at least a resistance-setting command for the single rank of emulated memory circuits received from the memory controller; and
select the first termination resistance and the second termination resistance from one or more look-up tables.
11. The memory subsystem of claim 10, further comprising:
a third transmission line electrically coupling the interface circuit to the memory controller;
the interface circuit further comprising a third termination resistor with a third termination resistance;
wherein the interface circuit is further operable to terminate the third transmission line with the third termination resistance, wherein the third termination resistance is selected based on one or more resistance-setting commands received from the memory controller.
12. The memory subsystem of claim 11, wherein the third termination resistance is different from a termination resistance indicated by the plurality of resistance-setting commands received from the memory controller.
13. The memory subsystem of claim 10, wherein one or more of the first termination resistor or the second termination resistor is activated in response to one or more transmission line termination control signals issued by the interface circuit.
14. The memory subsystem of claim 10, wherein the first and the second termination resistors are on-die termination (ODT) resistors.
15. The memory subsystem of claim 10, wherein the resistance-setting command received from the memory controller comprises a mode register set (MRS) command.
16. The memory subsystem of claim 10, wherein the interface circuit is located on the memory module.
17. The memory subsystem of claim 10, wherein the first termination resistance or the second termination resistance is different from a termination resistance indicated by the resistance-setting command received from the memory controller.
18. The memory subsystem of claim 10, wherein resistance values of the first and the second termination resistors during read operations are different from resistance values of the first and the second termination resistors during write operations.
19. A memory subsystem comprising:
a memory module comprising:
a first rank of memory circuits comprising a first plurality of memory circuits; and
a second rank of memory circuits comprising a second plurality of memory circuits;
an interface circuit;
a first transmission line electrically coupling the interface circuit to a first memory circuit of the first plurality of memory circuits of the first rank; and
a second transmission line electrically coupling the interface circuit to a second memory circuit of the second plurality of memory circuits of the second rank;
wherein the interface circuit is operable to:
present the first and the second ranks of memory circuits to a memory controller as a single rank of emulated memory circuits;
terminate one or more of the first transmission line with the first termination resistance or the second transmission line with the second termination resistance, wherein the first termination resistance and the second termination resistance are each selected based on at least a resistance-setting command for the single rank of emulated memory circuits received from the memory controller;
select first resistance values of the first and the second termination resistors for read operations; and
select second, different resistance values of the first and the second termination resistors for write operations.
20. The memory subsystem of claim 19, further comprising:
a third transmission line electrically coupling the interface circuit to the memory controller;
the interface circuit further comprising a third termination resistor with a third termination resistance;
wherein the interface circuit is further operable to terminate the third transmission line with the third termination resistance, wherein the third termination resistance is selected based on one or more resistance-setting commands received from the memory controller.
21. The memory subsystem of claim 20, wherein the third termination resistance is different from a termination resistance indicated by the plurality of resistance-setting commands received from the memory controller.
22. The memory subsystem of claim 19, wherein one or more of the first termination resistor or the second termination resistor is activated in response to one or more transmission line termination control signals issued by the interface circuit.
23. The memory subsystem of claim 19, wherein the first and the second termination resistors are on-die termination (ODT) resistors.
24. The memory subsystem of claim 19, wherein the resistance-setting command received from the memory controller comprises a mode register set (MRS) command.
25. The memory subsystem of claim 19, wherein the interface circuit is located on the memory module.
26. The memory subsystem of claim 19, wherein the first termination resistance or the second termination resistance is different from a termination resistance indicated by the resistance-setting command received from the memory controller.
27. The memory subsystem of claim 19, wherein the interface circuit selects the first termination resistance and the second termination resistance from one or more look-up tables.
Patent Citations (168)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4500958(A) | 1985-02-01 | Manton et al. | Applicant |
| US4628407(A) | 1986-12-01 | August et al. | Applicant |
| US4807191(A) | 1989-02-01 | Flannagan | Applicant |
| US4916575(A) | 1990-04-01 | Van Asten | Applicant |
| US5193072(A) | 1993-03-01 | Frenkil et al. | Applicant |
| US5212666(A) | 1993-05-01 | Takeda | Applicant |
| US5222014(A) | 1993-06-01 | Lin | Applicant |
| US5369749(A) | 1994-11-01 | Baker et al. | Applicant |
| US5390078(A) | 1995-02-01 | Taylor | Applicant |
| US5392251(A) | 1995-02-01 | Manning | Applicant |
| US5550781(A) | 1996-08-01 | Sugawara et al. | Applicant |
| US5696929(A) | 1997-12-01 | Hasbun et al. | Applicant |
| US5765203(A) | 1998-06-01 | Sangha | Applicant |
| US5818788(A) | 1998-10-01 | Kimura et al. | Applicant |
| US5819065(A) | 1998-10-01 | Chilton et al. | Applicant |
| US5913072(A) | 1999-06-01 | Wieringa | Applicant |
| US5960468(A) | 1999-09-01 | Paluch | Applicant |
| US5978304(A) | 1999-11-01 | Crafts | Applicant |
| US6026027(A) | 2000-02-01 | Terrell, II et al. | Applicant |
| US6044028(A) | 2000-03-01 | Kumagai et al. | Applicant |
| US6047361(A) | 2000-04-01 | Ingenio et al. | Applicant |
| US6065092(A) | 2000-05-01 | Roy | Applicant |
| US6125072(A) | 2000-09-01 | Wu | Applicant |
| US6181640(B1) | 2001-01-01 | Kang | Applicant |
| US6226730(B1) | 2001-05-01 | Murdoch et al. | Applicant |
| US6253278(B1) | 2001-06-01 | Ryan | Applicant |
| US6297966(B1) | 2001-10-01 | Lee et al. | Applicant |
| US6434660(B1) | 2002-08-01 | Lambert et al. | Applicant |
| US6476476(B1) | 2002-11-01 | Glenn | Applicant |
| US6490161(B1) | 2002-12-01 | Johnson | Applicant |
| US6492726(B1) | 2002-12-01 | Quek et al. | Applicant |
| US6618267(B1) | 2003-09-01 | Dalal et al. | Applicant |
| US6628538(B2) | 2003-09-01 | Funaba et al. | Applicant |
| US6659512(B1) | 2003-12-01 | Harper et al. | Applicant |
| US6664625(B2) | 2003-12-01 | Hiruma | Applicant |
| US6690191(B2) | 2004-02-01 | Wu et al. | Applicant |
| US6711043(B2) | 2004-03-01 | Friedman et al. | Applicant |
| US6714433(B2) | 2004-03-01 | Doblar et al. | Applicant |
| US6730540(B2) | 2004-05-01 | Siniaguine | Applicant |
| US6731009(B1) | 2004-05-01 | Jones et al. | Applicant |
| US6807650(B2) | 2004-10-01 | Lamb et al. | Applicant |
| US6810475(B1) | 2004-10-01 | Tardieux | Applicant |
| US6844754(B2) | 2005-01-01 | Yamagata | Applicant |
| US6854043(B2) | 2005-02-01 | Hargis et al. | Applicant |
| US7043611(B2) | 2006-05-01 | McClannahan et al. | Applicant |
| US7110322(B2) | 2006-09-01 | Farmwald et al. | Applicant |
| US7111143(B2) | 2006-09-01 | Walker | Applicant |
| US7117309(B2) | 2006-10-01 | Bearden | Applicant |
| US7138823(B2) | 2006-11-01 | Janzen et al. | Applicant |
| US7277333(B2) | 2007-10-01 | Schaefer | Applicant |
| US7289386(B2) | 2007-10-01 | Bhakta et al. | Examiner |
| US7327613(B2) | 2008-02-01 | Lee | Applicant |
| US7336490(B2) | 2008-02-01 | Harris et al. | Applicant |
| US7337293(B2) | 2008-02-01 | Brittain et al. | Applicant |
| US7414917(B2) | 2008-08-01 | Ruckerbauer et al. | Applicant |
| US7499281(B2) | 2009-03-01 | Harris et al. | Applicant |
| US7539800(B2) | 2009-05-01 | Dell et al. | Examiner |
| US7619912(B2) | 2009-11-01 | Bhakta et al. | Applicant |
| US7738252(B2) | 2010-06-01 | Schuette et al. | Applicant |
| US7791889(B2) | 2010-09-01 | Belady et al. | Applicant |
| US7911798(B2) | 2011-03-01 | Chang et al. | Applicant |
| US7934070(B2) | 2011-04-01 | Brittain et al. | Applicant |
| US7990797(B2) | 2011-08-01 | Moshayedi et al. | Applicant |
| US8116144(B2) | 2012-02-01 | Shaw et al. | Applicant |
| US2001/0019509(A1) | 2001-09-01 | Aho et al. | Applicant |
| US2001/0046129(A1) | 2001-11-01 | Broglia et al. | Applicant |
| US2001/0052062(A1) | 2001-12-01 | Lipovski | Applicant |
| US2002/0002662(A1) | 2002-01-01 | Olarig et al. | Applicant |
| US2002/0040416(A1) | 2002-04-01 | Tsern et al. | Applicant |
| US2002/0060948(A1) | 2002-05-01 | Chang et al. | Applicant |
| US2002/0094671(A1) | 2002-07-01 | Distefano et al. | Applicant |
| US2002/0165706(A1) | 2002-11-01 | Raynham | Examiner |
| US2002/0167092(A1) | 2002-11-01 | Fee et al. | Applicant |
| US2002/0172024(A1) | 2002-11-01 | Hui et al. | Applicant |
| US2003/0016550(A1) | 2003-01-01 | Yoo et al. | Applicant |
| US2003/0083855(A1) | 2003-05-01 | Fukuyama | Applicant |
| US2003/0088743(A1) | 2003-05-01 | Rader | Applicant |
| US2003/0110339(A1) | 2003-06-01 | Calvignac et al. | Applicant |
| US2003/0127737(A1) | 2003-07-01 | Takahashi | Applicant |
| US2003/0164543(A1) | 2003-09-01 | Kheng Lee | Applicant |
| US2003/0174569(A1) | 2003-09-01 | Amidi | Applicant |
| US2003/0230801(A1) | 2003-12-01 | Jiang et al. | Applicant |
| US2003/0234664(A1) | 2003-12-01 | Yamagata | Applicant |
| US2004/0000708(A1) | 2004-01-01 | Rapport et al. | Applicant |
| US2004/0042503(A1) | 2004-03-01 | Shaeffer et al. | Applicant |
| US2004/0049624(A1) | 2004-03-01 | Salmonsen | Applicant |
| US2004/0100837(A1) | 2004-05-01 | Lee | Applicant |
| US2004/0195682(A1) | 2004-10-01 | Kimura | Applicant |
| US2004/0228196(A1) | 2004-11-01 | Kwak et al. | Applicant |
| US2005/0034004(A1) | 2005-02-01 | Bunker et al. | Applicant |
| US2005/0044302(A1) | 2005-02-01 | Pauley et al. | Applicant |
| US2005/0086548(A1) | 2005-04-01 | Haid et al. | Applicant |
| US2005/0127531(A1) | 2005-06-01 | Tay et al. | Applicant |
| US2005/0139977(A1) | 2005-06-01 | Nishio et al. | Applicant |
| US2005/0193183(A1) | 2005-09-01 | Barth et al. | Applicant |
| US2005/0243635(A1) | 2005-11-01 | Schaefer | Applicant |
| US2005/0246558(A1) | 2005-11-01 | Ku | Applicant |
| US2005/0263312(A1) | 2005-12-01 | Bolken et al. | Applicant |
| US2005/0286334(A1) | 2005-12-01 | Saito et al. | Applicant |
| US2005/0289292(A1) | 2005-12-01 | Morrow et al. | Examiner |
| US2006/0041730(A1) | 2006-02-01 | Larson | Applicant |
| US2006/0117152(A1) | 2006-06-01 | Amidi et al. | Examiner |
| US2006/0149857(A1) | 2006-07-01 | Holman | Applicant |
| US2006/0179262(A1) | 2006-08-01 | Brittain et al. | Applicant |
| US2006/0262587(A1) | 2006-11-01 | Matsui et al. | Applicant |
| US2006/0277355(A1) | 2006-12-01 | Ellsberry et al. | Examiner |
| US2007/0088995(A1) | 2007-04-01 | Tsern et al. | Applicant |
| US2007/0152313(A1) | 2007-07-01 | Periaman et al. | Applicant |
| US2007/0279084(A1) | 2007-12-01 | Oh et al. | Applicant |
| US2007/0285895(A1) | 2007-12-01 | Gruendler et al. | Applicant |
| US2007/0290333(A1) | 2007-12-01 | Saini et al. | Applicant |
| US2008/0034130(A1) | 2008-02-01 | Perego et al. | Applicant |
| US2008/0098277(A1) | 2008-04-01 | Hazelzet | Applicant |
| US2008/0120443(A1) | 2008-05-01 | Rajan et al. | Applicant |
| US2008/0126624(A1) | 2008-05-01 | Prete et al. | Applicant |
| US2008/0126692(A1) | 2008-05-01 | Rajan et al. | Examiner |
| US2008/0130364(A1) | 2008-06-01 | Guterman et al. | Applicant |
| US2008/0155136(A1) | 2008-06-01 | Hishino | Applicant |
| US2008/0195894(A1) | 2008-08-01 | Schreck et al. | Applicant |
| US2008/0215832(A1) | 2008-09-01 | Allen et al. | Applicant |
| US2008/0256282(A1) | 2008-10-01 | Guo et al. | Applicant |
| US2008/0282084(A1) | 2008-11-01 | Hatakeyama | Applicant |
| US2008/0282341(A1) | 2008-11-01 | Hatakeyama | Applicant |
| US2009/0049266(A1) | 2009-02-01 | Kuhne | Applicant |
| US2009/0063865(A1) | 2009-03-01 | Berenbaum et al. | Applicant |
| US2009/0063896(A1) | 2009-03-01 | Lastras-Montano et al. | Applicant |
| US2009/0070520(A1) | 2009-03-01 | Mizushima | Applicant |
| US2009/0089480(A1) | 2009-04-01 | Wah et al. | Applicant |
| US2009/0180926(A1) | 2009-07-01 | Petruno et al. | Applicant |
| DE102004051345 | 2006-05-01 | Applicant | |
| DE102004053316 | 2006-05-01 | Applicant | |
| DE102005036528 | 2007-02-01 | Applicant | |
| EP132129 | 1985-01-01 | Applicant | |
| EP644547 | 1995-03-01 | Applicant | |
| JP62121978 | 1987-06-01 | Applicant | |
| JP1-171047 | 1989-07-01 | Applicant | |
| JP3-29357 | 1991-02-01 | Applicant | |
| JP3-276487(B2) | 1991-12-01 | Applicant | |
| JP3-286234 | 1991-12-01 | Applicant | |
| JP5-298192 | 1993-11-01 | Applicant | |
| JP7-141870 | 1995-06-01 | Applicant | |
| JP8-77097 | 1996-03-01 | Applicant | |
| JP10233091 | 1998-10-01 | Applicant | |
| JP11-149775 | 1999-06-01 | Applicant | |
| JP22025255(A2) | 2002-01-01 | Applicant | |
| JP3304893(B2) | 2002-05-01 | Applicant | |
| JP2002288037 | 2002-10-01 | Applicant | |
| JP4-327474 | 2004-11-01 | Applicant | |
| JP2005062914 | 2005-03-01 | Applicant | |
| JP2006236388 | 2006-09-01 | Applicant | |
| KR1999-0076659 | 1999-10-01 | Applicant | |
| KR1020040062717 | 2004-07-01 | Applicant | |
| KR2005120344 | 2005-12-01 | Applicant | |
| WO95/05676 | 1995-02-01 | Applicant | |
| WO97/25674 | 1997-07-01 | Applicant | |
| WO9900734 | 1999-01-01 | Applicant | |
| WO/45270 | 2000-08-01 | Applicant | |
| WO1/37090 | 2001-05-01 | Applicant | |
| WO1/90900 | 2001-11-01 | Applicant | |
| WO1/97160 | 2001-12-01 | Applicant | |
| WO2004/044754 | 2004-05-01 | Applicant | |
| WO2004/051645 | 2004-06-01 | Applicant | |
| WO2006/072040 | 2006-07-01 | Applicant | |
| WO2007/002324 | 2007-01-01 | Applicant | |
| WO2007/028109 | 2007-03-01 | Applicant | |
| WO2007/038225 | 2007-04-01 | Applicant | |
| WO2007/095080 | 2007-08-01 | Applicant | |
| WO2008/063251 | 2008-05-01 | Applicant |
Non-Patent Literature (291)
- Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jul. 31, 2012.Applicant
- Final Office Action from U.S. Appl. No. 13/315,933, Dated Aug. 24, 2012.Applicant
- Final Office Action from U.S. Appl. No. 13/276,212, Dated Aug. 30, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 31, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 11/461,420, Dated Sep. 5, 2012.Applicant
- Final Office Action from U.S. Appl. No. 13/280,251, Dated Sep. 12, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,225, Dated Sep. 17, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 12/508,496, Dated Sep. 17, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/672,921, Dated Oct. 1, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 12/057,306, Dated Oct. 10, 2012.Applicant
- Notice Allowance from U.S. Appl. No. 12/144,396, Dated Oct. 11, 2012.Applicant
- Office Action for U.S. Appl. No. 12/797,557 dated Jun. 21, 2011. 46 pages.Applicant
- BIOS and Kernel Developer's Guide (BKDG) Family 10h Processor, Sep. 7, 2007, Published for Processor Family Purchasers.Applicant
- Skerlj et al. “Buffer Device for Memory Modules”. 2006, p. 1.Applicant
- Fang et al., W. Power Complexicity Analysis of Adiabatic SRAM, 6th Int. Conference on ASIC, vol. 1, Oct. 2005, pp. 334-337.Applicant
- Kellerbauer, R. “Die Schnelle Million,” with translation, “The Quick Million: Memory Expansion for 1040 ST and Mega ST 1,” Dec. 1991.Applicant
- Pavan et al., P. A Complete Model of E2PROM Memory Cells for Circuit Simulations, IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 22, No. 8, Aug. 2003, pp. 1072-1079.Applicant
- Supplemental European Search Report and Search Opinion issued Sep. 21, 2009 in European Application No. 07870726.2, 8 pp.Applicant
- Wu et al., “eNVy: A Non-Volatile, Main Memory Storage System”, ASPLOS-VI Proceedings, Oct. 4-7, 1994, pp. 86-97.Applicant
- Using Two Chip Selects to Enable Quad Rank, From IP.COM #000132468D, Feb. 26, 2008.Applicant
- Buffer Device for Memory Modules (DIMM),IP.com Prior Art Database, <URL:http://ip.com/IPCOM/000144850>, Feb. 10, 2007, 1 pg.Applicant
- German Office Action from German Patent Application No. 11 2006 001 810.8-55 Dated Feb. 18, 2009 (With Translation).Applicant
- German Office Action from German Patent Application No. 11 2006 002 300.4-55 Dated May 11, 2009 (With Translation).Applicant
- Great Britain Office Action from GB Patent Application No. GB0800734.6 Dated Mar. 1, 2010.Applicant
- Great Britain Office Action from GB Patent Application No. GB0803913.3 Dated Mar. 1, 2010.Applicant
- Preliminary Report on Patentability From PCT Application No. PCT/US06/24360 Dated on Jan. 10, 2008.Applicant
- Written Opinion From PCT Application No. PCT/US06/24360 Dated on Jan. 8, 2007.Applicant
- International Search Report From PCT Application No. PCT/US06/34390 Dated on Nov. 21, 2007.Applicant
- Written Opinion From PCT Application No. PCT/US06/34390 Dated on Nov. 21, 2007.Applicant
- International Preliminary Examination Report From PCT Application No. PCT/US07/016385 Dated Feb. 3, 2009.Applicant
- Search Report and Written Opinion From PCT Application No. PCT/US07/03460 Dated on Feb. 14, 2008.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,420 Dated Jul. 23, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/461,420 Dated Apr. 28, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,427 Dated Sep. 5, 2008.Applicant
- Final Office Action from U.S. Appl. No. 11/461,430 Dated Sep. 8, 2008.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,430 Dated Feb. 19, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/461,430 Dated Sep. 9, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/461,435 Dated Jan. 28, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,435 Dated Aug. 5, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/461,435 Dated May 13, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,437 Dated Jan. 26, 2009.Applicant
- Final Rejection From U.S. Appl. No. 11/463,437 Dated Nov. 10, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,441 Dated Apr. 2, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/474,075 Dated Nov. 26, 2008.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/474,076 Dated Nov. 3, 2008.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/515,167 Dated Sep. 25, 2009.Applicant
- Final Action from U.S. Appl. No. 11/515,167 Dated Jun. 3, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/515,223 Dated Sep. 22, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Jul. 30, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/524,811 Dated Sep. 17, 2008.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/538,041 Dated Jun. 10, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Jun. 25, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,372 Dated Sep. 30, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,372 Dated Mar. 12, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,372 Dated Aug. 4, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/553,390 Dated Sep. 9, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/553,390 Dated Jun. 24, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/553,399 Dated Jul. 7, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Oct. 13, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Mar. 22, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Dec. 3, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/588,739 Dated Dec. 29, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/611,374 Dated Mar. 23, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Sep. 15, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Nov. 30, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Apr. 5, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Jul. 19, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Oct. 29, 2010.Applicant
- Non-Final Rejection From U.S. Appl. No. 11/672,921 Dated Dec. 8, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/672,921 Dated Jul. 23, 2010.Applicant
- Non-Final Rejection From U.S. Appl. No. 11/672,924 Dated Dec. 14, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/672,924 Dated Sep. 7, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/702,960 Dated Sep. 25, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/702,960 Dated Jun. 21, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/702,981 Dated Mar. 11, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/702,981 Dated Aug. 19, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/762,010 Dated Mar. 20, 2009.Applicant
- Final Rejection From U.S. Appl. No. 11/762,010 Dated Dec. 4, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Jul. 2, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Oct. 22, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/762,013 Dated Jun. 5, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Aug. 17, 2010.Applicant
- Notice of Allowanee from U.S. Appl. No. 11/762,013 Dated Dec. 7, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/763,365 Dated Oct. 28, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Jun. 29, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Oct. 20, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/828,181 Dated Mar. 2, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/828,182 Dated Mar. 29, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/855,805 Dated Sep. 21, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Aug. 14, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/858,518 Dated Apr. 21, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Sep. 8, 2010.Applicant
- Non-Final Rejection From U.S. Appl. No. 11/929,225 Dated Dec. 14, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/929,225 Dated Aug. 27, 2010.Applicant
- Non-Final Rejection From U.S. Appl. No. 11/929,261 Dated Dec. 14, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/929,261 Dated Sep. 7, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,286 Dated Aug. 20, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,320 Dated Sep. 29, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,403 Dated Aug. 31, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,417 Dated Aug. 31, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,432 Dated Jan. 14, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,432 Dated Aug. 20, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,450 Dated Aug. 20, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Oct. 7, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,500 Dated Oct. 13, 2009.Applicant
- Final Office Action from U.S. Appl. No. 11/929,500 Dated Jun. 24, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,571 Dated Mar. 3, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,631 Dated Mar. 3, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,631 Dated Nov. 18, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,636 Dated Mar. 9, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,655 Dated Mar. 3, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/929,655 Dated Nov. 22, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Sep. 24, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Dec. 1, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/939,432 Dated Apr. 12, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/939,440 Dated Sep. 17, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/941,589 Dated Oct. 1, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Oct. 25, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/057,306 Dated Oct. 8, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/111,819 Dated Apr. 27, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 12/111,819 Dated Nov. 20, 2009.Applicant
- Notice Of Allowance from U.S. Appl. No. 12/111,819 Dated Mar. 10, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/111,828 Dated Apr. 17, 2009.Applicant
- Notice of Allowance from U.S. Appl. No. 12/111,828 Dated Dec. 15, 2009.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/203,100 Dated Dec. 1, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/507,682 Dated Mar. 8, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/574,628 Dated Jun. 10, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/769,428 Dated Nov. 8, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/838,896 Dated Sep. 3, 2010.Applicant
- Search Report From PCT Application No. PCT/US10/038041 Dated Aug. 23, 2010.Applicant
- Final Office Action from U.S. Appl. No. 11/588,739 Dated Dec. 15, 2010.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Feb. 18, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/828,182 Dated Dec. 22, 2010.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/855,826 Dated Jan. 13, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Feb. 18, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/144,396 Dated Feb. 1, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/816,756 Dated Feb. 7, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Feb. 23, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Feb. 24, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Mar. 1, 2011.Applicant
- Final Office Action from U.S. Appl. No. 12/574,628 Dated Mar. 3, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/929,571 Dated Mar. 3, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Mar. 4, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Mar. 4, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Mar. 18, 2011.Applicant
- Final Office Action from U.S. Appl. No. 12/507,682 Dated Mar. 29, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,403 Dated Mar. 31, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/838,896 Dated Apr. 19, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Apr. 25, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,320 Dated May 5, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/939,440 Dated May 19, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/855,805, Dated May 26, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/672,921 Dated May 27, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Jun. 8, 2011.Applicant
- European Search Report from co-pending European application No. 11194876.6-2212/2450798, Dated Apr. 12, 2012.Applicant
- European Search Report from co-pending European application No. 11194862.6-2212/2450800, Dated Apr. 12, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/411,489, Dated Oct. 17, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/471,283, Dated Dec. 7, 2012.Applicant
- English translation of Office Action from co-pending Korean patent application No. KR1020087005172, dated Dec. 20, 2012.Applicant
- Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Dec. 27, 2012.Applicant
- Office Action from co-pending European patent application No. EP12150798, Dated Jan. 3, 2013.Applicant
- Final Office Action from U.S. Appl. No. 11/672,924, Dated Feb. 1, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/260,650, Dated Feb. 1, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/141,844, Dated Feb. 5, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/473,827, Dated Feb. 15, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 12/378,328, Dated Feb. 27, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/536,093, Dated Mar. 1, 2013.Applicant
- Office Action from co-pending Japanese patent application No. 2012-132119, Dated Mar. 6, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 11/461,435, Dated Mar. 6, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Mar. 18, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Mar. 21, 2013.Applicant
- Extended European Search Report for co-pending European patent application No. EP12150807.1, dated Feb. 1, 2013, mailed Mar. 22, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Apr. 3, 2013.Applicant
- English translation of Office Action from co-pending Korean patent application No. KR1020087019582, Dated Mar. 13, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/618,246, Dated Apr. 23, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/182,234, Dated May 1, 2013.Applicant
- Final Office Action from U.S. Appl. No. 13/315,933, Dated May 3, 2013.Applicant
- English Translation of Office Action from co-pending Korean patent application No. 10-2013-7004006, Dated Apr. 12, 2013.Applicant
- EPO Communication for Co-pending European patent application No. EP11194862.6, dated May 5, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,793, Dated May 6, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,565, Dated May 24, 2013.Applicant
- Final Office Action from U.S. Appl. No. 11/929,225, Dated May 24, 2013.Applicant
- Final Office Action from U.S. Appl. No. 11/672,921, Dated May 24, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 28, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,424, Dated May 29, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/341,844, Dated May 30, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,199, Dated Jun. 17, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,207, Dated Jun. 20, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/828,182, Dated Jun. 20, 2013.Applicant
- Final Office Action from U.S. Appl. No. 11/828,181, Dated Jun. 20, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,655, Dated Jun. 21, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/597,895, Dated Jun. 25, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,645, Dated Jun. 26, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Jun. 28, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/181,747, Dated Jul. 9, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Jul. 18, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/182,234, Dated Jul. 22, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Jul. 22, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,233, Dated Aug. 2, 2013.Applicant
- Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 8, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/615,008, Dated Aug. 15, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,425, Dated Aug. 20, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,601, Dated Aug. 23, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/507,683, Dated Aug. 27, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/315,933, Dated Aug. 27, 2013.Applicant
- Final Office Action from U.S. Appl. No. 13/620,650, Dated Aug. 30, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,424, Dated Sep. 11, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/620,291, Dated Sep. 12, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/341,844, Dated Sep. 17, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,412, dated Sep. 25, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/343,852, dated Sep. 27, 2013.Applicant
- English Translation of Office Action from co-pending Korean patent application No. 10-2008-7019582, dated Sep. 16, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,565, dated Sep. 27, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/279,068, dated Sep. 30, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,207, dated Oct. 9, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/898,002, dated Oct. 10, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/471,283, dated Oct. 15, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 11/515,223, dated Oct. 24, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/181,747, dated Oct. 28, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/597,895, dated Oct. 29, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/620,199, dated Nov. 13, 2013.Applicant
- Final Office Action from U.S. Appl. No. 13/620,793, dated Nov. 13, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/618,246, dated Nov. 14, 2013.Applicant
- Notice of Allowance from U.S. Appl. No. 13/473,827, dated Nov. 20, 2013.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/672,924 Dated Jun. 8, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,225 Dated Jun. 8, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Jun. 13, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Jun. 15, 2011.Applicant
- Final Office Action from U.S. Appl. No. 12/057,306 Dated Jun. 15, 2011.Applicant
- Final Office Action from U.S. Appl. No. 12/769,428 Dated Jun. 16, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/203,100 Dated Jun. 17, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Jun. 20, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/797,557 Dated Jun. 21, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Jun. 23, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/702,960 Dated Jun. 23, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,655 Dated Jun. 24, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Jun. 24, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Jun. 24, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/828,182 Dated Jun. 27, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/828,181 Dated Jun. 27, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/378,328 Dated Jul. 15, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/461,420 Dated Jul. 20, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/461,437 Dated Jul. 25, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Aug. 5, 2011.Applicant
- Notice of Allowability from U.S. Appl. No. 11/855,826 Dated Aug. 15, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/574,628 Dated Sep. 20, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Sep. 27, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,571 Dated Sep. 27, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Sep. 27, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Sep. 30, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/816,756 Dated Oct. 3, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/508,496 Dated Oct. 11, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/588,739 Dated Oct. 13, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Oct. 24, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/929,631 Dated Nov. 1, 2011.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Nov. 14, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Nov. 29, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/769,428 Dated Nov. 28, 2011.Applicant
- Final Office Action from U.S. Appl. No. 11/939,440 Dated Dec. 12, 2011.Applicant
- Notice of Allowance from U.S. Appl. No. 12/797,557 Dated Dec. 28, 2011.Applicant
- Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jan. 10, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 12/838,896 Dated Jan. 18, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/929,655 Dated Jan. 19, 2012.Applicant
- Final Office Action from U.S. Appl. No. 12/378,328 Dated Feb. 3, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/672,921 Dated Feb. 16, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/672,924 Dated Feb. 16, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/929,225 Dated Feb. 16, 2012.Applicant
- International Search Report for Application No. EP12150807 Dated Feb. 16, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/828,181 Dated Feb. 23, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/461,520 Dated Feb. 29, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 12/574,628 Dated Mar. 6, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/276,212 Dated Mar. 15, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/343,612 Dated Mar. 29, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 11/939,440 Dated Mar. 30, 2012.Applicant
- European Search Report from co-pending European application No. 11194876.6- 2212/2450798, Dated Apr. 12, 2012.Applicant
- European Search Report from co-pending European application No. 11194862.6- 2212/2450800, Dated Apr. 12, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,636, Dated Apr. 17, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/858,518, Dated Apr. 17, 2012.Applicant
- European Search Report from co-pending European application No. 11194883.2-2212, Dated Apr. 27, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 11/553,372, Dated May 3, 2012.Applicant
- Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 3, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 22, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 12/144,396, Dated May 29, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 31, 2012.Applicant
- Non-Final Office Action from U.S. Appl. No. 13/280,251, Dated Jun. 12, 2012.Applicant
- Final Office Action from U.S. Appl. No. 11/855,805, Dated Jun. 14, 2012.Applicant
- English Translation of Office Action from co-pending Japanese patent application No. P2012-197675, Dec. 3, 2013.Applicant
- English Translation of Office Action from co-pending Japanese patent application No. P2012-197678, Dec. 3, 2013.Applicant
- English Translation of Office Action from co-pending Korean patent application No. 10-2013-7004006, dated Dec. 26, 2013.Applicant
- Search Report from co-pending European Patent Application No. 13191794, dated Dec. 12, 2013.Applicant
- Search Report from co-pending European Patent Application No. 13191796, dated Feb. 10, 2014.Applicant