The disclosure herein is related generally to memory modules, and more particularly to a memory module with local synchronization and method of operation.
With recent advancement of information technology and widespread use of the Internet to store and process information, more and more demands are placed on the acquisition, processing, storage and dissemination of vocal, pictorial, textual and numerical information by microelectronics-based combination of computing and communication means. In a typical computer or server system, memory modules are used to store data or information. A memory module usually includes multiple memory devices, such as dynamic random access memory devices (DRAM) or synchronous dynamic random access memory devices (SDRAM), packaged individually or in groups, and/or mounted on a printed circuit board (PCB). A processor or a memory controller accesses the memory module via a memory bus, which, for a single-in-line memory module (SIMM), can have a 32-bit wide data path, or for a dual-in-line memory module (DIMM), can have a 64-bit wide data path.
The memory devices of a memory module are generally organized in ranks, with each rank of memory devices generally having a bit width. For example, a memory module in which each rank of the memory module is 64 bits wide is described as having an “×64” or “by 64” organization. Similarly, a memory module having 72-bit-wide ranks is described as having an “×72” or “by 72” organization.
The memory capacity or memory density of a memory module increases with the number of memory devices on the memory module. The number of memory devices of a memory module can be increased by increasing the number of memory devices per rank or by increasing the number of ranks.
In certain conventional memory modules, the ranks are selected or activated by control signals from a processor or memory controller during operation. Examples of such control signals include, but are not limited to, rank-select signals, also called chip-select signals. Most computer and server systems support a limited number of ranks per memory module, which limits the memory density of the memory modules that can be used in these computer and server systems.
For memory devices in such a memory module to be properly accessed, distribution of control signals and a control clock signal in the memory module is subject to strict constraints. In some conventional memory modules, control wires are routed so that there is an equal length of signal path to each memory component, in order to eliminate variation of the timing of the control signals and the control clock signal between different memory devices in the memory modules. The balancing of the length of the wires to each memory devices compromises system performance, limits the number of memory devices, and complicates their connections.
In some conventional memory systems, the memory controllers include leveling mechanisms for write and/or read operations to compensate for unbalanced wire lengths and memory device loading on the memory module. As memory operating speed and memory density continue to increase, however, such leveling mechanisms are also insufficient to insure proper timing of the control and/or data signals received and/or transmitted by the memory modules.
A memory module according to one embodiment includes memory devices organized in groups, a module control device, and data buffers (DB). The data buffers are sometimes referred to herein as buffer circuits, isolation circuits, isolation devices or load reduction devices. The memory module is operable to perform memory operations in response to memory commands (e.g., read, write, refresh, precharge, etc.), each of which is represented by a set of control/address (C/A) signals transmitted by the memory controller to the memory module. The C/A signals may include, for example, a row address strobe signal (/RAS), a column address strobe signal (/CAS), a write enable signal (/WE), an output enable signal (/OE), one or more chip select signals, row/column address signals, and bank address signals. The memory controller may also transmit a system clock signal to the memory module. In one embodiment, the C/A signals and the system clock signal are received by the module control device, which generates a set of module control/address (C/A) signals and a set of data buffer control signals in response to each memory command from the memory controller. The module C/A signals are transmitted by the module control device to the memory devices via module C/A signal lines, and the data buffer control signals (referred sometimes herein as DBCS) are transmitted by the module control device to the buffer circuits via data buffer control signal lines.
In certain embodiments, the buffer circuits are associated with respective groups of memory devices and are distributed across the memory module at positions corresponding to the data/strobe signal lines associated with the respective groups of memory devices. Thus, during certain high speed operations, each data buffer control signal may arrive at different buffer circuits at different points of time across more than one clock cycle of the system clock. Also, each buffer circuit associated with a respective group of memory devices is in the data paths between the respective group of memory devices and the memory controller. Thus, the memory controller does not have direct control of the memory devices. In one embodiment, each group of memory devices include at least two subgroups, each subgroup including at least one memory device. Each buffer circuit is configured to enable a selected subgroup in the respective group of memory devices to communicate data with the memory controller in response to the data buffer control signals. The memory module can have more ranks of memory devices than what is supported by the memory controller.
In the context of the present description, a rank refers to a set of memory devices that are selectable by a same chip select signal from the memory controller. The number of ranks of memory devices in a memory module 110 may vary. For example, as shown, each memory module 110 may include four ranks of memory devices 112. In another embodiment, the memory module 110 may include 2 ranks of memory devices. In yet another embodiment, the memory module may include six or more ranks of memory devices 112.
In the context of the present description, a memory controller refers to any device capable of sending instructions or commands, or otherwise controlling the memory devices 112. Additionally, in the context of the present description, a memory bus refers to any component, connection, or groups of components and/or connections, used to provide electrical communication between a memory module and a memory controller. For example, in various embodiments, the memory bus 105 may include printed circuit board (PCB) transmission lines, module connectors, component packages, sockets, and/or any other components or connections that provide connections for signal transmission.
Furthermore, the memory devices 112 may include any type of memory devices. For example, in one embodiment, the memory devices 112 may include dynamic random access memory (DRAM) devices, such as Synchronous dynamic random access memory (SDRAM) devices in compliance with, for example, the Double Data Rate Type 3 (DDR3) or Double Data Rate Type 4 (DDR4) standard. Additionally, in one embodiment, each memory module 110 may include a dual in-line memory module (DIMM).
As shown in
Examples of the system C/A signals include, but are not limited to, Chip Select (or /CS) signal, which is used to select a rank of memory devices to be accessed during a memory (read or write) operation; Row Address Strobe (or /RAS) signal, which is used mostly to latch a row address and to initiate a memory cycle; Column Address Strobe (or /CAS) signal, which is used mostly to latch a column address and to initiate a read or write operation; address signals, including bank address signals and row/column address signals, which are used to select a memory location on a memory device or chip; Write Enable (or /WE) signal, which is used to specify a read operation or a write operation, Output Enable (or /OE) signal, which is used to prevent data from appearing at the output until needed during a read operation, and the system clock signal MCK.
Examples of module C/A signals include, but are not limited to one or more module /CS signals; a module /RAS signal, which can be, for example, a registered version of the system /RAS signal; a module /CAS signal, which can be, for example, a registered version of the system /CAS signal; module address signals, which can be, for example, registered versions of some or all of the address signals; a module /WE signal, which can be, for example, a registered version of the system /WE signal; a module /OE signal, which can be, for example a registered version of the system /OE signal. In certain embodiments, the module C/A signals may also include the module clock signal CK. The one or more module C/S signals can be derived from the system /CS signals and one or more other system C/A signals, such as one or more bank address signals and/or one or more row/column address signals, as exemplified in commonly owned U.S. Pat. No. 7,532,537, entitled “Memory Module with a Circuit Providing Load Isolation and Memory Domain Translation,” issued on May 12, 2009, the entirety of which is incorporated herein by reference.
Examples of data buffer control signals include, but are not limited to, one or more mode signals, which specify a mode of operation (e.g., configuration mode, test mode or normal operation mode) for the data buffers 118, and other data buffer control signals whose definitions depend on the mode of operation. For example, during the normal operation mode the other data buffer control signals may include one or more enable signals, one or more ODT signals, and the module clock signal. In the normal operation mode, the one or more enable signals are used by each data buffer to select one or more memory devices to communicate data with the memory controller; and the one or more ODT signals are used by the data buffers to set up on-die termination for the data/strobe signals. In the configuration mode or test mode, the other data buffer control signals are used to convey configuration or module self-test control information from the module control device 116 to the data buffers 118. In one embodiment, the data buffer control signals are transmitted to the data buffers 118 via respective data buffer control signal lines 230. Alternatively, the data buffer control signals can be packetized before being transmitted to the data buffers 118 via the data buffer control signal lines and decoded/processed at the data buffers.
Module control device 116 transmits the module C/A signals to the memory devices 112 via module C/A signal lines 220. The memory devices 112 operate in response to the module C/A signals to receive write data or output read data as if the module C/A signals were from a memory controller. The module control device transmits the data buffer control signals together with the module clock signal CK to the data buffers 118 via data buffer control signal lines 230. As shown in
As shown n
In certain embodiments, the data buffers 118 are associated with respective groups of memory devices and are coupled between respective groups of system data/strobe signal lines 130 and the respective groups of memory devices. For example, data buffer ID-1 among the data buffers 118 is associated with the first group of memory devices M11, M12, M13, and M14 and is coupled between the group of system data/strobe signal lines 130-1 and the first group of memory devices, data buffers ID-i among the data buffers 118 is associated with the ith group of memory devices Mi1, Mi2, Mi3, and Mi4 and is coupled between the group of system data/strobe signal lines 130-i and the ith group of memory devices, and so on. The association of data buffers with groups of memory devices may not be exclusive, i.e., multiple data buffers may be associated with a same group of memory devices, or vice versa.
In one embodiment, each group or sets of memory devices are coupled to the associated data buffer 118 via a set of module data/strobe lines 210 and one or more clock signal lines 211. Each group or set of memory devices is organized in subgroups or subsets, with each subgroup or subset including at least one memory device. The subgroups in a group of memory devices may be coupled to the associated data buffer 118 via a same set of module data/strobe lines 210 (as shown in
In one embodiment, the data buffers 118 are in the data paths between the MCH 101 and the memory module 110 and include data buffers between the MCH 101 and the respective groups of memory devices. In one embodiment, each data buffer 118 is configured to enable a selected subgroup in the respective group of memory devices to communicate data with the MCH 101 in response to the data buffer control signals. Further, each data buffers 118 is configured to isolate unselected subgroup(s) of memory devices from the MCH 101 during write operations, so that the MCH sees a load on each data line that is less than a load associated with the respective group of memory devices. In one embodiment, the MCH sees only a load associated with one memory device on each data/strobe signal line during write operations.
In one embodiment, the data buffers 118 are distributed across the memory module 110 or the module board 119 in positions corresponding to edge connectors 121 coupled to respective groups of system data/strobe signal lines 130. For example, as shown in
As an option, memory module 110 may further include a serial-presence detect (SPD) device 240, which may include electrically erasable programmable read-only memory (EEPROM) for storing data that characterize various attributes of the memory module 110. Examples of such data include a number of row addresses, a number of column addresses, a data width of the memory devices, a number of ranks on the memory module 110, a memory density per rank, a number of memory device on the memory module 110, and a memory density per memory device, etc. A basic input/output system (BIOS) of system 100 can be informed of these attributes of the memory module 110 by reading from the SPD 240 and can use such data to configure the MCH 101 properly for maximum reliability and performance.
In certain embodiments, the SPD 240 and/or the control circuit 116 store module configuration information, such as: memory space translation code, memory address mapping function code, input and output signals timing control information for the control circuit 116, electrical and logical level control information for input and output signals for the control circuit 116, the data buffers 118, etc. In certain embodiments, the SPD 240 contains a system view of the module 110 which can be different from an actual physical construction of the module 110. For example, the SPD 240 stores at least one memory operation parameter that is different from a correspondng memory operation parameter in a system memory controller setting. The SPD 240 may also store at least on data buffer operation parameter that is different from a corresponding parameter in the system memory controller setting.
Thus, in certain embodiment, in the memory module 110, C/A signals representing a memory command are received and buffered by the module control circuit 116, so that the MCH sees only the module control circuit 116 as far as the C/A signals are concerned. Write data and strobe signals from the controller are received and buffered by the data buffers 118 before being transmitted to the memory devices 112 by the data buffers 118. On the other hand, read data and strobe signals from the memory devices are received and buffered by the data buffers before being transmitted to the MCH via the system data/strobe signal lines 130. Thus, MCH 101 does not directly operate or control the memory devices 112. As far as data/strobe signals are concerned, the MCH 101 mainly sees the data buffers 118, and the system 100 depends on the data buffers 118 to properly time the transmission of the data and strobe signals between the MCH 101 and the memory devices 112.
In certain embodiments, the memory module 110 is a dual in-line memory module (DIMM) and the memory devices are double data rate (DDR) dynamic random access memory devices (DRAM). In certain embodiments, the control circuit 116 includes a DDR register, and logic for memory space translation between a system memory domain and a module level physical memory domain. Such translation may produce address mapping, proper interface timing for the control signals to the module level physical memory domain, and a proper interface electrical and logical level for the control signals to the module level physical memory domain.
As shown in
For example, to offset the skew in the registered C/A signals, certain memory devices (e.g., the DDR3 SDRAM) have a training mode that permits the MCH to effectively zero-out the skew and re-align the data in time by adding delay to the data paths. In certain embodiments, however, load reduction mechanism in the data buffers 118 would provide a single data bus interface for the memory devices, which hides the data interfaces between the memory devices 112 and the data buffers 118 from the system memory controller 101. Thus, a long sequence of interface timing training may be required because the system memory controller 101 has very limited control over the interface between the memory devices 112 and the data buffers 118. Furthermore, interface signal alignment-drift after the initial training would not be easily detected by the system memory controller 101, which may cause silent system failure.
Moreover, clock skew amongst the memory devices 112 and the data buffers 118 can cause synchronization issues. As the speed of memory operation increase, data period can become so short that variation of signal propagation time through I/Os becomes a very significant portion of a data period. As a result, the clock skew issues cannot simply be addressed by pipelining the data paths.
To address at least some of the above issues, in certain embodiments, as shown in
Thus, the memory module 110 in
In certain embodiments, operations of the data buffers 118 are controlled by the data buffer control signals from the module control circuit 116, which generates the data buffer control signals according to the C/A signals received from the MCH. Thus, the data buffer control signals need to be properly received by the data buffers 118 to insure their proper operation. In one embodiment, the data buffer control signals are transmitted together with the registered clock signal, or the module clock signal CK, which is generated by the module control circuit 116 based on the system clock signal MCK. The isolation circuits 118 buffers the module clock signal, which is used to time the sampling of the data buffer control signals. Since the data buffers 118 are distributed across the memory module, the data buffer control signal lines 230 can stretch across the memory module 110, over a distance of several centimeters. As the data buffer control signals travel over such a distance, they can become misaligned with the module clock signal, resulting in metastability in the received data buffer control signals. Therefore, in one embodiment, the isolation circuits 118 includes metastability detection circuits to detect metastability condition in the data buffer control signals and signal adjustment circuits to adjust the data buffer control signals and/or the module clock signal to mitigate any metastability condition in the data buffer control signals, as disclosed in commonly-owned U.S. patent application Ser. No. 13/952,599, filed Jul. 27, 2013, entitled “Memory Module with Distributed Data Buffers and Method Of Operation,” the entirety of which is incorporated herein by reference.
Because the data buffers 118 are distributed across the memory module 110, during high speed operations, it may take more than one clock cycle time of the system clock MCK for the data buffer control signals to travel along the data buffer control signals lines 230 from the module control device 116 to the farthest positioned data buffers 118, such as data buffer ID-1 and data buffer ID-(n−1) in the exemplary configuration shown in
With the data buffers 118 receiving data buffer control signals at different times across more than one clock cycle, the data buffer control signals alone are not sufficient to time the transmission of read data signals to the MCH 101 from the data buffers 118. In one embodiment, the data buffers have programmable control of the timing of read/write data signals and the phase of the locally synchronized clock signal for each group of locally synchronized devices. In certain embodiments, each data buffer can further determine individually, during a write operation, a time interval between a time when one or more data buffer control signals are received from the module control circuit 116 and a time when a write strobe or write data signal is received from the MCH 101. This time interval is used to adjust the timing of the transmission of read data to the MCH 101 during a subsequent read operation, as explained in more detail below.
More illustrative information will now be set forth regarding various optional configurations, architectures, and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described.
In one embodiment, as shown in
Each data buffer 118 includes a set of DQ routing circuits 320 coupled on one side to respective ones of the set of n DQ signal lines 322, and on another side to respective ones of the respective set of n module data lines, or respective ones of the respective subsets of module data lines, such as the first module data lines YA0, YA1, . . . , YAn and the second module data lines YB0, YB1, . . . , YBn. Each data buffer 118 further includes an DB Control circuit 310 coupled on one side to the at least one DQS signal line 324, on another side to the one or more module strobe signal lines YDQS, or the first module strobe signal line YADQS and second module strobe signal line YBDQS.
The DB Control circuit 310 also receives the module clock signal CK and the data buffer control signals via the data buffer control signal lines 230, and outputs datapath control signals 330 to the DQ routing circuits 320, including, for example, one or more enable signals ENA and/or ENB, and some or all of the other received, decoded, and/or otherwise processed data buffer control signals. In certain embodiments, the DB Control circuit 310 also outputs one or more delay signals DS, a read DQS signal RDQS, a write DQS signal WDQS, and a buffer clock signal CK0. Each DQ routing circuit 320 is configured to enable data communication between the respective DQ signal line 322 with a selected subgroup of one or more memory devices in response to the data buffer control signals, as explained in more detail below.
In certain embodiments, the DB Control circuit 310 also provides one or more delay signals DS, which is used by the DQ routing circuits 320 to control the timing of read and/or write data output by the data buffer 118, as explained in further detail below. In certain embodiments, the DB Control circuit 310 regenerates clock signal CK0 from the module clock signal CK. In certain embodiments, the regenerated clock signal CK0 is phase-locked to the module clock signal CK. In certain embodiments, the regenerated clock signal CK0 has a programmable delay from the module clock signal CK. In certain embodiments, the regenerated CK0 is provided to the respective group of memory devices so that the data buffer 118 and the respective group of memory devices form a group of locally synchronized devices on the memory module 110.
The memory devices 112 in each group of locally synchronized devices are coupled to the data buffer 118 in the each group of locally synchronized devices via a same set of module data/strobe signal lines. Or the memory devices 112 in each group of locally synchronized devices include subgroups of memory devices that are coupled to the data buffer 118 via different subsets of module data/strobe signal lines. For example, as shown in
Alternatively, as shown in
Multiple memory devices having a data width that is less than a data width of the data buffers 118 may be used in place of one of the memory devices 112, which has the same data width as that of the data buffers. For example, as shown in
In another embodiment, as shown in
The DB Control circuit 310 further includes a control processing circuit 640 that decodes and/or otherwise processes the data buffer control signals. In the normal operation mode, the decoded/processed data buffer control signals may include, for example, one or more data path enable signals ENA and/or ENB that are used by the DQ routing circuits 320 and the strobe routing circuit 620 to selectively enabling data communication between the MCH 101 and one of the subgroups in the respective group of memory devices, with which the data buffer is associated. In a configuration mode, the decoded/processed data buffer control signals are used to program configuration registers in the control processing circuit 640, which in turn control one or more delay signals DS1, DS2, DS3. The delay signal DS1 is used to control delay circuits in the read paths in the DQ/DQS routing circuits, the delay signal DS2 is used to control delay circuits in the write paths in the DQ/DQS routing circuits the data buffer, and the delay signal DS3 is used to control the phase of the locally synchronized clock CK0.
The strobe routing circuit 620 also buffers strobe signals received from either the MCH 101 or the memory devices 112, and outputs either a write strobe WDQS or read strobe RDQS, respectively, to the DQ routing circuits 320. In one embodiment, the DB Control circuit 310 further includes a dynamic delay control circuit 650 that provide dynamic adjustment of the timing of read data/strobe signals in the DQ routing circuit 320 and the strobe routing circuit 620.
In certain embodiments, as shown in
The programmable registers 671 is coupled via signal lines 69 the dynamic delay control circuit 650, which also takes as input a DQS signal, clock signal CK, and one of the datapath enable signals EN, and output the delay signal DS1. The dynamic delay control circuit 650 is described in further detail below.
Since the module control circuit 116 generates the DBCS based on signals from the MCH 101, the MCH 101 can train the data buffers 118 to properly time the read/write data signals and to properly adjust the phase of the locally synchronized clock signals CK0. In certain embodiments, the module control circuit 116 generates the DBCS for setting the registers in the delay control circuit based on mode register command signals from the MCH 101. As shown in
The DQS routing circuit further includes a plurality of read paths 850 that are selectable in accordance with the one or more of the data buffer control signals. Output from the seleted read path is delayed in a delay circuit 860 by an amount controlled by the delay signal DS1, and sampled by a sampler circuit 870. The sampled read data/strobe is transmitted by transmitter 880 onto the corresponding data/strobe signal line 322/324 via the DQ/DQS pin 801.
The DQS routing circuit further includes a read strobe path coupled between the first DQS pin 901 and a selected one of the second and third DQS pins 902A and 902B. In the read strobe path, a select circuit 950 (e.g., a multiplexor) selects either a read strobe signal received via DQS pin 902A or a read strobe signal received via DQS pin 902B based on one or both of the enable signals ENA or ENB. The selected read strobe signal is delayed in a delay circuit 960 by an amount controlled by the delay signal DS, and sampled by a sampler circuit 970 according to the buffered module clock signal CK0. The sampled read strobe is provided to the DQ routing circuits 320 as the read strobe RDQS and is transmitted by transmitter 980 onto the corresponding strobe signal line 324 via the first DQS pin 901.
The DQ routing circuit further includes a read data path coupled between the first DQ pin 1001 and a selected one of the second and third DQ pins 1002A and 1002B. In the read data path, a select circuit 1050 (e.g., a multiplexor) selects either a read data signal received via DQ pin 1002A or a read data signal received via DQ pin 1002B based on one or both of the enable signals ENA or ENB. The selected read data signal is delayed in a delay circuit 1060 by an amount controlled by the delay signal DS. The delayed read data signal is then sampled by a receiver circuit 1070 according to the read strobe RDQS from the DQS routing circuit 620, and transmitted by transmitter 1080 onto the corresponding data signal line 130 via the first DQ pin 1001.
As stated above, the MCH 101 can control the timing of read/write signals by programming the registeres that control the DS1 and DS2 signals. However, since the data buffers 118 are in the data paths between the MCH 101 and the respective groups of memory devices 112, the MCH 101 does not have direct control of the interface between the data buffers and the memory devices 112. Thus, conventional read/write leveling techniques are not sufficient for managing read/write data timing. In one embodiment, in addition to the data buffers 118 having programmable control of timing of the read/write signals and the phase of the clock signal for each group of locally synchronized components, the data buffers also include signal alignment mechanism to dynamically control the timing of the transmission of read data/strobe signals, as discussed further below.
With knowledge of the time interval between t7 and t5, which should be about the same as the time interval between t3 and t1, i.e., the command-to-enable delay CED, in certain embodiments, the data buffer can add a proper amount of delay to the read data signals and the one or more DQS signal such that the read data signals and the one or more DQS signal are transmitted at time t9 by the data buffer to the MCH 101 via the respective group of data/strobe signal lines 130, with the time interval between t9 and t5 being consistent with a read latency R.L. associated with the system 100.
The time interval between t4 and t3, i.e., the enable to write data delay EWD, is determined by the delay control circuit 650 in the DB Control circuit 310, as shown in
Thus, as shown in
Since the time interval between the arrival of the command signals from the MCH 101 and the arrival of the write data/strobe signal DQ/DQS from the MCH 101 is set according to a write latency parameter associated with the system 100, the time interval EWD can be used to ascertain a time interval CED between the time when a command signal is received by the memory module 110 and the time when the one or more enable signals are received by the data buffer 118. The time interval CED can be used by the data buffer 118 to properly time the transmission of read data to the MCH 101.
As shown in
During a read operation, another set of data buffer control signals including, for example, one or more second enable signals, are received by the data buffer 114 from the module controller 116 (1460). The one or more second enable signals are generated by the module controller 116 in response to read command signals received from the MCH 101, and are used by the data buffer 118 to select a subgroup of memory devices from which to receive read data. Afterwards, a read strobe signal DQS and a set of read data signal DQ are received from the selected subgroup of memory devices (1470). To properly time the transmission of the DQS and DQ signals to the MCH 101, the DQS and DQ signals are adjusted (e.g., delayed) according to the delay signal DS, such that the DQS and DQ signals follow a read command by a time interval consistent with a read latency parameter associated with the system 100.
This application is a continuation of U.S. patent application Ser. No. 16/432,700, filed on Jun. 5, 2019, entitled “Memory Module with Local Synchronization and Method of Operation,” which is a continuation of U.S. patent application Ser. No. 14/445,035, filed on Jul. 28, 2014 (now U.S. Pat. No. 10,324,841), entitled “Memory Module with Local Synchronization,” which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/859,215, filed on Jul. 27, 2013, entitled “Memory Module with Local Synchronization Using Distributed Data Buffers,”, each of which is herein fully incorporated by reference in its respective entirety.
Number | Name | Date | Kind |
---|---|---|---|
5036221 | Brucculeri et al. | Jul 1991 | A |
6072346 | Ghahremani | Jun 2000 | A |
6184701 | Kim et al. | Feb 2001 | B1 |
6530006 | Dodd et al. | Mar 2003 | B1 |
6807077 | Noda et al. | Oct 2004 | B2 |
6877079 | Yoo et al. | Apr 2005 | B2 |
6889300 | Davis et al. | May 2005 | B2 |
6906555 | Ma | Jun 2005 | B2 |
7036053 | Zumkehr | Apr 2006 | B2 |
7275173 | Lindt | Sep 2007 | B2 |
7356639 | Perego et al. | Apr 2008 | B2 |
7562271 | Shaeffer et al. | Jul 2009 | B2 |
7808849 | Swain et al. | Oct 2010 | B2 |
7890732 | Sukegawa | Feb 2011 | B2 |
8020022 | Tokuhiro | Sep 2011 | B2 |
8407441 | Giovannini et al. | Mar 2013 | B2 |
8552779 | Jones et al. | Oct 2013 | B2 |
8565033 | Manohararajah | Oct 2013 | B1 |
8566516 | Schakel et al. | Oct 2013 | B2 |
8599595 | Stephens, Jr. | Dec 2013 | B1 |
8713379 | Takefman et al. | Apr 2014 | B2 |
9153298 | Stephens, Jr. | Oct 2015 | B2 |
9263103 | Giovannini et al. | Feb 2016 | B2 |
9361955 | Muralimanohar et al. | Jun 2016 | B2 |
20040105292 | Matsui | Jun 2004 | A1 |
20060277355 | Ellsberry et al. | Dec 2006 | A1 |
20070008791 | Butt et al. | Jan 2007 | A1 |
20070168781 | Sutardja | Jul 2007 | A1 |
20080025122 | Schakel et al. | Jan 2008 | A1 |
20100309706 | Saito | Dec 2010 | A1 |
20100312925 | Osanai et al. | Dec 2010 | A1 |
20100312956 | Hiraishi et al. | Dec 2010 | A1 |
20110062999 | Nimalyar et al. | Mar 2011 | A1 |
20120106228 | Lee | May 2012 | A1 |
20120296598 | Chafin et al. | Nov 2012 | A1 |
Entry |
---|
Inter Partes Review of U.S. Pat. No. 9,824,035, Case No. IPRIPR2022-00236, IPR Petition re U.S. Pat. No. 9,824,035, filed Dec. 23, 2021. |
Inter Partes Review of U.S. Pat. No. 10,268,608, Case No. IPRIPR2022-00237, IPR Petition re U.S. Pat. No. 10,268,608, filed Dec. 23, 2021. |
Inter Partes Review of U.S. Pat. No. 9,824,035, Case No. IPRIPR2022-00236, ‘Ex. 1003—IPR2022-00236 Declaration of Donald Alpert,’ filed Dec. 23, 2021. |
Inter Partes Review of U.S. Pat. No. 10,268,608, Case No. IPRIPR2022-00237, ‘Ex. 1003—IPR2022-00237 Declaration of Donald Alpert,’ filed Dec. 23, 2021. |
Inter Partes Review of U.S. Pat. No. 9,824,035, Case No. IPRIPR2022-00236, Patent Owner's Preliminary Response, filed Apr. 25, 2022. |
Inter Partes Review of U.S. Pat. No. 10,268,608, Case No. IPRIPR2022-00237, Patent Owner's Preliminary Response, filed Apr. 25, 2022. |
Inter Partes Review of U.S. Pat. No. 9,824,035, Case No. IPRIPR2022-00236, Patent Owner's Exhibit List, filed Apr. 25, 2022. |
Complaint for Patent Infringement, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Apr. 28, 2021), 74 pages. |
Netlist, Inc.'s Disclosure of Asserted Claims and Preliminary Infringement Contentions to Defendants, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA.(W.D. Tex. Sep. 10, 2021), 9 pages. |
Micron's Preliminary Invalidity Contentions in Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Nov. 5, 2021), 38 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on US Patent Application Publication No. 2010/0312925 A1 to Osanai et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 57 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 8,713,379 to Takefman et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 48 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 8,020,022 to Tokuhiro, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 31 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 6,877,079 to Yoo et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 48 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 7,562,271 to Shaeffer et al. Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 50 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 6,530,006 to Dodd et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 51 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 9,361,955 to Muralimanohar et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 63 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on U.S. Pat. No. 2012/0106228 to Lee, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 39 pages. |
Invalidity Chart for U.S. Pat. No. 9,824,035 based on JEDEC Submission entitled “Proposed DDR4 DB BCOM Protocol,” Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 22 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on US Patent Application Publication No. 2010/0312925 A1 to Osanai et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 53 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 8,713,379 to Takefman et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 35 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 8,020,022 to Tokuhiro, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 30 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 6,877,079 to Yoo et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-0043 1 (W.D. Tex. Nov. 5, 2021), 48 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 7,562,271 to Shaeffer et al. Netlist, Incv. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLCCase No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 52 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 6,530,006 to Dodd et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 51 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on U.S. Pat. No. 9,361,955 to Muralimanohar et al., Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 49 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on US Patent No. 2012/0106228 to Lee, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 36 pages. |
Invalidity Chart for U.S. Pat. No. 10,268,608 based on JEDEC Submission entitled “Proposed DDR4 DB BCOM Protocol,” Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 19 pages. |
Obviousness Chart for U.S. Pat. No. 9,824,035, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 14 pages. |
Obviousness Chart for U.S. Pat. No. 10,268,608, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431 (W.D. Tex. Nov. 5, 2021), 9 pages. |
Micron's Preliminary Identification of Proposed Claim Constructions, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Dec. 23, 2021), 14 pages. |
Netlist, Inc.'s Preliminary Proposed Claim Constructions, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Dec. 23, 2021), 7 pages. |
Defendants' Identification of Extrinsic Evidence in Support of Their Preliminary Proposed Constructions, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Jan. 13, 2022), 21 pages. |
Netlist, Inc.'s Preliminary Identification of Extrinsic Evidence, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Jan. 13, 2022), 16 pages. |
Declaration of Harold S. Stone, Ph.D., in Support of Defendants' Claim Construction Positions, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Feb. 3, 2022), 27 pages. |
Declaration of Alan Jay Smith, Ph.D., in Support of Defendants' Claim Construction Positions, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron T echnology Texas LLC, Case No. 6:21-cv-00431-ADA (W.D. Tex. Feb. 3, 2022), 26 pages. |
Micron's Opening Claim Construction Brief, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 6:21-v-00431-ADA (W.D. Tex. Feb. 3, 2022), 40 pages. |
Joint Claim Construction Chart, Netlist, Inc. v. Micron Technology, Inc., Micron Semiconductor Products, Inc., and Micron Technology Texas LLC, Case No. 1.22-cv-0013 6-LY, (W.D. Tex. Apr. 14, 2022), 13 pages. |
Excerpt—Modern Dictionary of Electronics 7E, 1999. |
JEDEC Solid State Technology Association, 1st Showing, Committee: JC-40.4, Committee Item No. 0311.xx, ‘Proposed DDR4 DB BCOM Protocol,’ undated, 10 pages. |
JEDEC Standard Double Data Rate (DDR) SDRAM Specification, JESD79 (Jun. 2000), 78 pages. |
JEDEC Standard No. 21-C, PC2100 and PC1600 DDR SDRAM Registered DIMM Design Specification, Revision 1.3, Jan. 2002, 83 pages. |
Excerpt—JEDEC Standard DDR3 SDRAM JESD79-3, DDR3 SDRAM Standard, Jun. 2007, 12 pages. |
JEDEC Standard JESD79-3F (Revision of JESD79-3E, Jul. 2010), DDR3 SDRAM Standard, Jul. 2012, 226 pages. |
Excerpt—JEDEC Standard DDR3 SDRAM JESD79-3A, DDR3 SDRAM Specification, Sep. 2007, 12 pages. |
Excerpt—JEDEC Standard DDR3 SDRAM JESD79-3C, DDR3 SDRAM, Apr. 2008, 7 pages. |
Excerpt—JEDEC Standard No. 21C, DDR4 SDRAM Load Reduced DIMM Design Specification, Aug. 2015, 2 pages. |
Inter Partes Review of U.S. Pat. No. 10,860,506, Case No. IPR2022-00711, IPR Petition re U.S. Pat. No. 10,860,506, filed Mar. 22, 2022. |
Inter Partes Review of U.S. Pat. No. 10,860,506, Case No. IPR2022-00711, ‘Ex. 1003—IPR2022-00711 Declaration of Robert Wedig,’ filed Mar. 22, 2022. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-00730, IPR Petition re U.S. Pat. No. 9,128,632, filed Jan. 20, 2017. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-007-30, ‘Ex. 1003—IPR2017-00730 Declaration of Trevor Mudge,’ filed Jan. 20, 2017. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-00730, Patent Owner's Preliminary Response, filed Apr. 30, 3017. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-00730, Decision Denying Institution of Inter Partes Review, entered Jul. 21, 2017. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-00730, Petitioners' Request for Rehearing, filed Aug. 21, 2017. |
Inter Partes Review of U.S. Pat. No. 9,128,632, Case No. IPR2017-00730, Decision Denying Petitioner's Request for Rehearing, entered Oct. 30, 2017. |
Inter Partes Review of U.S. Pat. No. 9,606,907, Case No. IPR2018-00362, Final Written Decision, entered Jun. 27, 2019. |
Complaint, Netlist, Inc. v. Samsung Electronics Co., Ltd., Samsung Electronics America, Inc., Samsung Semiconductor, Inc., Case No. 2:21-cv-463 (E.D. Tex. Dec. 20, 2021), 49 pages. |
First Amended Complaint for Declaratory Judgment of Non-Infringement and Unenforceability; Breach of Contract, Samsung Electronics Co., Ltd. and Samsung Semiconductor, Inc. v. Netlist, Inc., C.A. No. 21-1453 (RGA) (USDC, Delaware, Jan. 8, 2022), 122 pages. |
Number | Date | Country | |
---|---|---|---|
20210240620 A1 | Aug 2021 | US |
Number | Date | Country | |
---|---|---|---|
61859215 | Jul 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16432700 | Jun 2019 | US |
Child | 17141978 | US | |
Parent | 14445035 | Jul 2014 | US |
Child | 16432700 | US |